|
Name |
Type |
Discontinued? |
|
1 |
COVERAGE_ID |
NUMERIC |
No |
|
|
|
The unique ID assigned to the coverage record. This ID may be encrypted if you have elected to use enterprise reporting’s encryption utility. |
|
|
2 |
LINE |
INTEGER |
No |
|
|
|
The line count for the coverage record's patient bucket history. |
|
|
3 |
PAT_BKT_PAT_ID |
VARCHAR |
No |
|
|
|
The unique ID of the patient for the coverage's patient bucket history. |
|
|
4 |
PAT_BKT_DATE |
DATETIME |
No |
|
|
|
The date of service for the patient level bucket update. |
|
|
5 |
PAT_BKT_SRC_C_NAME |
VARCHAR |
No |
|
|
|
The source of the patient-level bucket update. |
May contain organization-specific values: No |
Category Entries: |
Conversion |
Manual Adjustment |
Charge |
Claim |
Pharmacy Confirmation |
Pro-Ration Adjustment |
Benefit Bucket Import |
HB Charge |
System Adjustment |
HRA Funding |
Adjustment Reversal |
|
|
6 |
PAT_BKT_CLAIM_ID |
NUMERIC |
No |
|
|
|
If the source is a claim then this field will have the unique identifier of the accounts payable claim record. |
|
|
7 |
PAT_BKT_AMT |
NUMERIC |
No |
|
|
|
The amount by which the patient level bucket was adjusted. |
|
|
8 |
PAT_BKT_CVG_ID |
NUMERIC |
No |
|
|
|
If this patient level update is due to carryover over from another coverage, this item will store the unique coverage ID of the source. |
|
|
9 |
PAT_BKT_RFL_ID |
NUMERIC |
No |
|
|
|
If the source is pharmacy confirmation (ACCT_BKT_SRC_C = 4), then the unique identifier of the relevant referral. |
|
|
10 |
PAT_BKT_CMT |
VARCHAR |
No |
|
|
|
The free text comment about the patient level bucket update. |
|
|
11 |
PAT_BKT_USER_ID |
VARCHAR |
No |
|
|
|
The unique ID of the user associated with the patient-level bucket update. |
|
|
12 |
PAT_BKT_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
13 |
PAT_BKT_ETR_ID |
NUMERIC |
No |
|
|
|
If the source was a claim, this field will store the procedure that updated the patient level bucket. |
|
|
14 |
PAT_IN_OUT_C |
VARCHAR |
No |
|
|
|
Stores in/out of network category ID for the bucket update, as calculated by the system. |
|
|
15 |
PAT_IN_OUT_OVRD_C |
VARCHAR |
No |
|
|
|
Stores in/out of network category ID for the bucket update, if the system calculated value was overridden. |
|
|
16 |
PAT_BKT_HB_CHRG_ID |
NUMERIC |
No |
|
|
|
If an accumulation amount was due to Hospital Billing, this column stores the transaction ID that caused the accumulation. |
|
|
17 |
PAT_BKT_BKT_ID |
NUMERIC |
No |
|
|
|
The ID of the coverage's patient level bucket. |
|
|
18 |
PAT_BKT_BKT_ID_BUCKET_NAME |
VARCHAR |
No |
|
|
|
|
19 |
PAT_BKT_CHARGE_ID |
NUMERIC |
No |
|
|
|
If the source is a charge, then this field will have the unique ID of the charge. |
|
|
20 |
PAT_BKT_INSTANT |
DATETIME (UTC) |
No |
|
|
|
Contains the instant at which this patient bucket update was made. |
|
|
21 |
PAT_BKT_Q4_FLAG |
VARCHAR |
No |
|
|
|
A Y/N flag that indicates whether or not fourth quarter carryover was performed for this bucket line. |
May contain organization-specific values: Yes |
Category Entries: |
No |
Yes |
|
|
22 |
PAT_BKT_Q4_FROM_LN |
INTEGER |
No |
|
|
|
The line number of the bucket that fourth quarter accumulations were carried from. |
|
|
23 |
PAT_BKT_Q4_RLPD_YR |
INTEGER |
No |
|
|
|
Stores the roll period year of the bucket the current row corresponds to, if this bucket was carried to or from due to fourth quarter carryover. |
|
|
24 |
PAT_BKT_ORG_SVC_DT |
DATETIME |
No |
|
|
|
The original service date for the patient level bucket update. This will only be different from PAT_BKT_DATE if the bucket update was the result of carryover. |
|
|
25 |
PAT_BKT_Q4_CAND |
VARCHAR |
No |
|
|
|
This column stores a Y/N flag. It will only be Y if the bucket is configured for fourth quarter carryover and the service date was in the last quarter of the year, but fourth quarter carryover was not performed because the member was not effective on the target bucket date. |
May contain organization-specific values: Yes |
Category Entries: |
No |
Yes |
|
|
26 |
PAT_BKT_Q4_CVG_YN |
VARCHAR |
No |
|
|
|
Stores a Y/N flag that indicates whether or not this bucket update was carried from another coverage by fourth quarter carryover rule. The ID of the source coverage is stored in column PAT_BKT_CVG_ID. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
27 |
PAT_BKT_IDNT |
VARCHAR |
No |
|
|
|
The user-entered identifier for a manual patient bucket entry. This is a free text field that could include a value that references an ID number, such as a claim or user ID. |
|
|
28 |
PAT_BKT_EDIT_TYP_C_NAME |
VARCHAR |
No |
|
|
|
The edit type category ID for the patient bucket. |
May contain organization-specific values: Yes |
Category Entries: |
Accrual |
Payout |
Correction |
|
|
29 |
PAT_BKT_ENTRY_TTL |
NUMERIC |
No |
|
|
|
Contains the total amount in the bucket before this update. This column is only populated for rows corresponding to manual adjustments. |
|
|
30 |
PAT_BKT_PROV_ID_PROV_NAME |
VARCHAR |
No |
|
|
|
The name of the service provider. This item may be hidden in a public view of the CLARITY_SER table. |
|
|
31 |
PAT_BKT_VEN_ID_VENDOR_NAME |
VARCHAR |
No |
|
|
|
|
32 |
PAT_BKT_ADMSN_DATE |
DATETIME |
No |
|
|
|
Benefit buckets that use an admission roll period use the admission start and discharge dates from the claim to determine the roll period. Each individual accumulation stores these dates from the claim. This column stores the admission date that accumulated this particular amount to the bucket. |
|
|
33 |
PAT_BKT_DISCHRG_DATE |
DATETIME |
No |
|
|
|
Benefit buckets that use an admission roll period use the admission start and discharge dates from the claim to determine the roll period. Each individual accumulation stores these dates from the claim. This column stores the discharge date that accumulated this particular amount to the bucket. |
|
|
34 |
PAT_BKT_EXCLCAROV_YN |
VARCHAR |
No |
|
|
|
Stores a Y/N flag indicating whether or not this account level accumulation was excluded from carryover to other coverages. Y means this accumulation was not carried over to other coverages. N or NULL means this accumulation was not excluded from carryover. |
The category values for this column were already listed for column: PAT_BKT_Q4_CVG_YN |
|
|
35 |
PAT_BKT_CRYOVR_AMT |
NUMERIC |
No |
|
|
|
Stores the original amount that we attempted to carryover to this coverage. This is only set if the original amount is different than the actual amount. |
|
|
36 |
PAT_BKT_CAT_OR_ID |
VARCHAR |
No |
|
|
|
Stores the unique identifier of the record or category value used by the bucket if it is of type per extension per day. If BEN_ACCUMULATION_HX_PAT.PAT_BKT_ITEM is NULL, this column stores the unique identifier of a record in the INI specified by BEN_ACCUMULATION_HX_PAT.PAT_BKT_INI. Otherwise, this column stores the category value corresponding to the master file and item specified in those columns. If translation to community IDs (CIDs) is enabled for this deployment (e.g. in an IntraConnect setting), this column stores the category or record CID. |
|
|
37 |
PAT_BKT_INI |
VARCHAR |
No |
|
|
|
Stores the INI of the master file networked to by the bucket if it is of type per extension per day. |
|
|
38 |
PAT_BKT_ITEM |
INTEGER |
No |
|
|
|
Stores the item number networked to by the bucket if it is of type per extension per day and counts against categories. |
|
|
39 |
PAT_BKT_COMBINED_START_DATE |
DATETIME |
No |
|
|
|
Stores the combined start date used if the bucket is of type per extension per day and is using an extension to combine accumulations from two contiguous days to determine whether a bucket exceeds the limit. |
|
|
40 |
PAT_BKT_ACCUM_ID |
VARCHAR |
No |
|
|
|
Unique identifier for a single bucket accumulation. This is a machine generated value and cannot be edited. The ID is made up of three pieces: The coverage ID, the accumulation line number, and 1170. If this accumulation is carried through fourth quarter carryover a Q will be appended. |
|
|
41 |
PAT_BKT_ORG_CVG_ID |
NUMERIC |
No |
|
|
|
If the patient-level accumulation was carried over from another coverage, then this column contains the accumulation's original source coverage ID. Otherwise, this column is blank. |
|
|
42 |
PAT_HRA_ACC_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
The type of accumulation for the Health Reimbursement Arrangement (HRA) bucket |
May contain organization-specific values: Yes |
Category Entries: |
Deposit |
Rollover |
Withdrawal |
Proration |
|
|
43 |
PAT_ROLLOVER_FROM_LINE |
INTEGER |
No |
|
|
|
The line that a rollover accumulation originated on. This will not be set when the source is Health Reimbursement Arrangement (HRA) deposit. |
|
|
44 |
PAT_REVERSAL_OF_LN |
INTEGER |
No |
|
|
|
If a value is present, then this accumulation line is a reversal of the accumulation on the line number stored in this item. Note that if no value is present, then this accumulation line may or may not be a reversal of another accumulation line. |
|
|
45 |
PAT_BKT_CROSS_ACCUM_BUCKET_ID |
NUMERIC |
No |
|
|
|
Indicates the source bucket if the accumulation was the result of cross-accumulation. |
|
|
46 |
PAT_BKT_CROSS_ACCUM_BUCKET_ID_BUCKET_NAME |
VARCHAR |
No |
|
|
|
|
47 |
PAT_BKT_RUNNING_TOTAL |
NUMERIC |
No |
|
|
|
Stores the running total of the patient and bucket this line accumulated to. Roll periods are accounted for, so the amount returned is the current accumulation plus the total of previous accumulations to the same patient, bucket, and roll period. |
|
|
48 |
PAT_BKT_TX_TOTAL_KEY |
VARCHAR |
No |
|
|
|
Stores a string that uniquely identifies the coverage, patient, bucket, and roll period this transaction applies to. This simplifies joins to other accumulation data model components, such as V_BEN_ACCUMULATION_TOTALS. COVERAGE_ID must still be included in the join. |
|
|
49 |
PAT_BKT_SEQ_NUM |
INTEGER |
No |
|
|
|
Stores a sequence number that indicates the order accumulation lines were added to the coverage. When accumulations are carried over, this number is not reset. For example, if accumulation 1 occurs on coverage A before accumulation 2 on coverage B, then carryover occurs from coverage A to B, the sequence number for accumulation 1 will still be before accumulation 2. This sequence number is not guaranteed to be dense/continuous, and may be NULL for accumulations that occurred before its implementation. |
|
|