|
Name |
Type |
Discontinued? |
|
1 |
PAT_ID |
VARCHAR |
No |
|
|
|
The unique ID assigned to the patient record. This ID may be encrypted if you have elected to use enterprise reporting’s encryption utility. |
|
|
2 |
PAT_ENC_DATE_REAL |
FLOAT |
No |
|
|
|
A unique contact date in decimal format. The integer portion of the number indicates the date of contact. The digits after the decimal distinguish different contacts on the same date and are unique for each contact on that date. For example, .00 is the first/only contact, .01 is the second contact, etc. |
|
|
3 |
PAT_ENC_CSN_ID |
NUMERIC |
No |
|
|
|
A unique serial number for this encounter. This number is unique across all patients and encounters in the system. |
|
|
4 |
CONTACT_DATE |
DATETIME |
No |
|
|
|
The date of this contact in calendar format. |
|
|
5 |
PCP_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. |
|
|
6 |
FIN_CLASS_C_NAME |
VARCHAR |
No |
|
|
|
The category value associated with the Financial Class of the encounter. Note: This item is only populated through an interface. It is not populated if you have billing system installed. |
May contain organization-specific values: Yes |
Category Entries: |
Commercial |
Medicare |
Medicaid |
Self-Pay |
Worker's Comp |
Tricare |
Champva |
Group Health Plan |
FECA Black Lung |
Blue Shield |
Medigap |
Other |
DK Regional |
Client |
Received Self-Pay |
Sent to Consolidated Self-Pay |
Patient Assistance Program |
|
|
7 |
VISIT_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. |
|
|
8 |
VISIT_PROV_TITLE_NAME |
VARCHAR |
No |
|
|
|
The visit provider’s provider title (SER 5). See VISIT_PROV_ID above for the definition of visit provider. |
May contain organization-specific values: Yes |
|
|
9 |
DEPARTMENT_ID_EXTERNAL_NAME |
VARCHAR |
No |
|
|
|
The external name of the department record. This is often used in patient correspondence such as reminder letters. |
|
|
10 |
LMP_DATE |
DATETIME |
No |
|
|
|
The date of the patient’s Last Menstrual Period. Only contains data for encounters with female patients. |
|
|
11 |
ENC_CLOSED_YN |
VARCHAR |
No |
|
|
|
A flag that signifies if this encounter is closed as of the time of the enterprise reporting extract. This column will have the value Y, N or null. Null indicates that closing the encounter does not apply, such as a future appointment. |
May contain organization-specific values: No |
Category Entries: |
Yes |
No |
|
|
12 |
ENC_CLOSED_USER_ID |
VARCHAR |
No |
|
|
|
The unique ID of the system user who closed the patient encounter. This ID may be encrypted. |
|
|
13 |
ENC_CLOSED_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
14 |
ENC_CLOSE_DATE |
DATETIME |
No |
|
|
|
The date on which the patient encounter was closed. |
|
|
15 |
LOS_MODIFIER1_ID |
VARCHAR |
No |
|
|
|
The first Level of Service modifier applied to the encounter. This item will appear empty if no modifier is present. |
|
|
16 |
LOS_MODIFIER1_ID_MODIFIER_NAME |
VARCHAR |
No |
|
|
|
The name of the modifier record. |
|
|
17 |
LOS_MODIFIER2_ID |
VARCHAR |
No |
|
|
|
The second Level of Service modifier applied to the encounter. This item will appear empty if no modifier is present. |
|
|
18 |
LOS_MODIFIER2_ID_MODIFIER_NAME |
VARCHAR |
No |
|
|
|
The name of the modifier record. |
|
|
19 |
LOS_MODIFIER3_ID |
VARCHAR |
No |
|
|
|
The third Level of Service modifier applied to the encounter. This item will appear empty if no modifier is present. |
|
|
20 |
LOS_MODIFIER3_ID_MODIFIER_NAME |
VARCHAR |
No |
|
|
|
The name of the modifier record. |
|
|
21 |
LOS_MODIFIER4_ID |
VARCHAR |
No |
|
|
|
The fourth Level of Service modifier applied to the encounter. This item will appear empty if no modifier is present. |
|
|
22 |
LOS_MODIFIER4_ID_MODIFIER_NAME |
VARCHAR |
No |
|
|
|
The name of the modifier record. |
|
|
23 |
APPT_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
The category value associated with the appointment status of the encounter as of the most recent enterprise reporting extract, such as 1 – Scheduled, 2 – Completed, 3 – Canceled, etc. |
May contain organization-specific values: Yes |
Category Entries: |
Scheduled |
Completed |
Canceled |
No Show |
Left without seen |
Arrived |
|
|
24 |
APPT_CANC_USER_ID |
VARCHAR |
No |
|
|
|
The unique ID of the user who canceled the appointment. |
|
|
25 |
APPT_CANC_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
26 |
CHECKIN_USER_ID |
VARCHAR |
No |
|
|
|
The unique ID of the system user who checked in the patient for this encounter. If the encounter has not been through the Check In process this field will be NULL. This ID may be encrypted. |
|
|
27 |
CHECKIN_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
28 |
HOSP_ADMSN_TIME |
DATETIME (Local) |
No |
|
|
|
The date and time that the patient was first admitted to the facility, bedded in the ED, or confirmed for an HOV for this contact, regardless of patient's base patient class. |
|
|
29 |
HOSP_DISCHRG_TIME |
DATETIME (Local) |
No |
|
|
|
The hospital discharge date and time for this patient contact. |
|
|
30 |
HOSP_ADMSN_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
The category value for the type of admission for this encounter. |
May contain organization-specific values: Yes |
|
|
31 |
NONCVRED_SERVICE_YN |
VARCHAR |
No |
|
|
|
A flag used to indicate whether the appointment is scheduled in a service not covered by the patient's coverage benefits. The flag is set to "Y" when the service is not covered and an "N" when it is covered. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
32 |
REFERRAL_REQ_YN |
VARCHAR |
No |
|
|
|
A flag used to indicate whether an appointment requires a referral as determined by the visit coverage. This flag is set to “Y” when the appointment requires a referral. If the appointment does not require a referral, it is set to “N." |
The category values for this column were already listed for column: NONCVRED_SERVICE_YN |
|
|
33 |
REFERRAL_ID |
NUMERIC |
No |
|
|
|
The unique ID of the referral record linked to this appointment. |
|
|
34 |
ACCOUNT_ID |
NUMERIC |
No |
|
|
|
The ID number of the guarantor account assigned to the visit at the time it is scheduled or when it is checked in. This ID may be encrypted. |
|
|
35 |
COVERAGE_ID |
NUMERIC |
No |
|
|
|
The ID number of the coverage record assigned to the visit at the time it is scheduled or when it is checked in. This ID may be encrypted. |
|
|
36 |
CLAIM_ID |
NUMERIC |
No |
|
|
|
The unique ID of the billing system Claim record (CLM record) linked to charges associated with this visit. |
|
|
37 |
PRIMARY_LOC_ID_LOC_NAME |
VARCHAR |
No |
|
|
|
The name of the revenue location. |
|
|
38 |
CHARGE_SLIP_NUMBER |
VARCHAR |
No |
|
|
|
The encounter form number or charge slip number assigned to this encounter. Note: The charge slip number is also stored in the financial table CLARITY_TDL. You can use this field to link to CLARITY_TDL to identify financial transactions associated with the encounter. |
|
|
39 |
COPAY_DUE |
NUMERIC |
No |
|
|
|
The dollar amount shown in the Copay Due field of the scheduling system's Check In Patient activity. This amount may be calculated by the system using the patient's coverage benefit information or be manually entered by a user. This field may also be empty if no copay amount was entered when the patient's appointment was checked in. |
|
|
40 |
UPDATE_DATE |
DATETIME (Local) |
No |
|
|
|
The time this patient encounter was pulled into enterprise reporting. |
|
|
41 |
HSP_ACCOUNT_ID |
NUMERIC |
No |
|
|
|
The ID number of the hospital billing account assigned to the encounter. |
|
|
42 |
ADM_FOR_SURG_YN |
VARCHAR |
No |
|
|
|
Indicates whether the patient is being admitted for surgery. |
May contain organization-specific values: No |
Category Entries: |
Yes |
No |
|
|
43 |
SURGICAL_SVC_C_NAME |
VARCHAR |
No |
|
|
|
The category value corresponding to the surgical service for this patient contact. |
May contain organization-specific values: Yes |
|
|
44 |
INPATIENT_DATA_ID |
VARCHAR |
No |
|
|
|
The ID number of the record used to determine how inpatient data is stored for the encounter. |
|
|
45 |
IP_EPISODE_ID |
NUMERIC |
No |
|
|
|
The ID number of the inpatient episode of care. This includes discharges from the ED. |
|
|
46 |
EXTERNAL_VISIT_ID |
VARCHAR |
No |
|
|
|
The ID for the contact as assigned by a non-system. Usually populated by an interface. |
|
|
47 |
CONTACT_COMMENT |
VARCHAR |
No |
|
|
|
Comments entered by the provider for the contact. |
|
|
48 |
OUTGOING_CALL_YN |
VARCHAR |
No |
|
|
|
Indicates whether a call associated with a telephone encounter was initiated by the patient or by the clinic / hospital. A "Y" indicates an outgoing call placed by the clinic / hospital while an "N" indicates and incoming call from the patient. |
The category values for this column were already listed for column: ENC_CLOSED_YN |
|
|
49 |
DATA_ENTRY_PERSON |
VARCHAR |
No |
|
|
|
This is the name of the user who created the encounter. |
|
|
50 |
REFERRAL_SOURCE_ID |
VARCHAR |
No |
|
|
|
The referral ID number of the referring physician. This physician may be from an external organization. |
|
|
51 |
REFERRAL_SOURCE_ID_REFERRING_PROV_NAM |
VARCHAR |
No |
|
|
|
The name of the referral source. |
|
|
52 |
WC_TPL_VISIT_C_NAME |
VARCHAR |
No |
|
|
|
A field used to indicate whether the patient's contact is related to workers compensation or third party liability situation. |
May contain organization-specific values: Yes |
|
|
53 |
CONSENT_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
This item describes the type of consent that was filed for a given encounter. It is a single-response customer-defined category. |
May contain organization-specific values: Yes |
|
|
54 |
BMI |
NUMERIC |
No |
|
|
|
This is the patient's Body Mass Index, which is calculated based on the recorded height and weight. |
|
|
55 |
BSA |
NUMERIC |
No |
|
|
|
This is the patient's Body Surface Area, which is calculated based on the recorded height and weight. |
|
|
56 |
AVS_PRINT_TM |
DATETIME (Local) |
No |
|
|
|
The instant that the After Visit Summary (AVS) was printed for this encounter. |
|
|
57 |
AVS_FIRST_USER_ID |
VARCHAR |
No |
|
|
|
Unique ID of the user who first prints out the After Visit Summary (AVS) for the encounter. |
|
|
58 |
AVS_FIRST_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
59 |
ENC_MED_FRZ_RSN_C_NAME |
VARCHAR |
No |
|
|
|
The encounter medication freeze reason's category value. |
May contain organization-specific values: No |
Category Entries: |
Dirty flag |
Mark Taking |
New Order |
Change or Reorder |
Review Meds |
Enter Vital Sign |
Discontinue Med |
Patient Arrival |
Medication Refused |
Close Encounter |
End of Day |
Mark Long-Term |
Create CAM |
|
|
60 |
EFFECTIVE_DATE_DT |
DATETIME |
No |
|
|
|
The date of the encounter. The returned date is handled differently depending on the contact type of the encounter: If it is a surgery encounter, the date of the surgery will be returned. If it is a Hospital encounter, Admission/Discharge/Transfer (ADT) info will be used to return an appropriate date. If ADT info cannot be found, then the Hospital Admission date (I EPT 18850) will be returned. If the Hospital Admission Date cannot be found, the temporary admission date (I EPT 18846) will be returned.. |
|
|
61 |
DISCHARGE_DATE_DT |
DATETIME |
No |
|
|
|
The discharge date for the encounter. |
|
|
62 |
COPAY_PD_THRU_NAME |
VARCHAR |
No |
|
|
|
The method by which the copay for an appointment was paid (e.g., via MyChart, a kiosk). |
May contain organization-specific values: Yes |
Category Entries: |
Mychart |
Welcome |
|
|
63 |
INTERPRETER_NEED_YN |
VARCHAR |
No |
|
|
|
A flag used to indicate whether a patient requires an interpreter for an encounter. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
64 |
VST_SPECIAL_NEEDS_C_NAME |
VARCHAR |
No |
|
|
|
This field captures any special needs for a visit. |
May contain organization-specific values: Yes |
|
|
65 |
BEN_ENG_SP_AMT |
NUMERIC |
No |
|
|
|
Stores the adjudicated self-pay amount (the amount required to be paid by the patient) when determining the copay amount for the visit. |
|
|
66 |
BEN_ADJ_COPAY_AMT |
NUMERIC |
No |
|
|
|
Stores the adjudicated copy amount for the visit according to the patient's coverage benefits. |
|
|
67 |
BEN_ADJ_METHOD_C_NAME |
VARCHAR |
No |
|
|
|
Flag to indicate if and how the adjudicated copay was overridden |
May contain organization-specific values: No |
Category Entries: |
Benefit Package Adjudication Formula |
Coverage Level Override |
Plan Level Override |
Copay Suppressed |
Payor Level Override Programming Point |
Service Area Level Override Programming Point |
Waived - Secondary Coverage Available |
Copay Computation Function Programming Point |
|
|
68 |
ENC_CREATE_USER_ID |
VARCHAR |
No |
|
|
|
The ID number of the user who create the patient or encounter record. |
|
|
69 |
ENC_CREATE_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
70 |
ENC_INSTANT |
DATETIME (Local) |
No |
|
|
|
The instant an encounter was created |
|
|
71 |
EFFECTIVE_DATE_DTTM |
DATETIME (Local) |
No |
|
|
|
The start date and time of an encounter. The start date is pulled from the date stored in the EFFECTIVE_DATE_DT column. The time references the first populated time in the following fields: hospital admission time (EPT 18851), hospital temporary admission time (EPT 18847), ADT arrival time (EPT 10815), and expected admission time (EPT 10300). The SlicerDicer reporting application uses this column to determine the EffectiveStartDate of encounters. |
|
|
72 |
CALCULATED_ENC_STAT_C_NAME |
VARCHAR |
No |
|
|
|
A status flag used to determine whether to include data from the encounter in the SlicerDicer reporting application. Statuses includes 1-Possible (e.g., the encounter is a scheduled outpatient appointment or the admission is pending) or 2-Complete (e.g., the appointment is complete, the admission is discharged). |
May contain organization-specific values: No |
Category Entries: |
Possible |
Complete |
Invalid |
In Progress |
|
|