|
Name |
Type |
Discontinued? |
|
1 |
PAT_ENC_CSN_ID |
NUMERIC |
No |
|
|
|
The unique contact serial number for this contact. This number is unique across all patient encounters in your system. If you use IntraConnect, this is the Unique Contact Identifier (UCI). |
|
|
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 |
CONTACT_DATE |
DATETIME |
No |
|
|
|
The date of this contact in calendar format. |
|
|
4 |
EX_DIS_DT_ENTR_DTTM |
DATETIME (Local) |
No |
|
|
|
The instant of entry of expected discharge date. |
|
|
5 |
EX_DIS_TM_ENTR_DTTM |
DATETIME (Local) |
No |
|
|
|
The instant of entry of expected discharge time. |
|
|
6 |
CONTRACT_REG_FLAG |
VARCHAR |
No |
|
|
|
Indicates whether an HOV contact was registered using the Contract Registration workflow. If this workflow was not used, this column is null. |
|
|
7 |
CONTRACT_CODE_C_NAME |
VARCHAR |
No |
|
|
|
The contract code category for the encounter. |
May contain organization-specific values: Yes |
|
|
8 |
ACCEPTS_BLOOD_C_NAME |
VARCHAR |
No |
|
|
|
The category ID that indicates whether this patient accepts blood. |
May contain organization-specific values: Yes |
|
|
9 |
ED_ARRIVAL_DETAILS |
VARCHAR |
No |
|
|
|
Free text information holding any details regarding the ED Arrival. |
|
|
10 |
CONS_SEDATION_C_NAME |
VARCHAR |
No |
|
|
|
The category ID of the conscious sedation status for the patient encounter. |
May contain organization-specific values: Yes |
No Entries Defined |
|
|
11 |
RESTRAINT_SECLUS_C_NAME |
VARCHAR |
No |
|
|
|
The restraint or seclusion status category ID for this patient encounter. |
May contain organization-specific values: Yes |
No Entries Defined |
|
|
12 |
MULTI_PREG_YN |
VARCHAR |
No |
|
|
|
Indicates whether the mother has a multiple pregnancy for this L&D encounter. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
13 |
DISASTER_NUM |
VARCHAR |
No |
|
|
|
This column stores the disaster number, which is a number given by the ambulance company to patients during catastrophes that cause massive patient influxes to the hospital. |
|
|
14 |
SRC_PATTERN_CSN_ID |
NUMERIC |
No |
|
|
|
The Contact Serial Number (CSN) of the Admission Pattern record associated with the projected bed usage for this patient encounter. If this projection is manually modified an end user, the column stores null. |
|
|
15 |
ENC_CLOSED_OR_COMPLETED_DATE |
DATETIME |
No |
|
|
|
The date that the encounter was closed or completed. |
|
|
16 |
ED_DISPO_PAT_COND_C_NAME |
VARCHAR |
No |
|
|
|
The category ID of the patient condition at time of disposition in the ED. |
May contain organization-specific values: Yes |
Category Entries: |
Good |
Stable |
Fair |
Serious |
Critical |
Expired |
|
|
17 |
ADOPTION_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
Item to store what type of adoption is related to the current L&D contact. |
May contain organization-specific values: Yes |
Category Entries: |
Open Adoption |
Closed Adoption |
Surrogate |
Safe Surrender |
Gestational Carrier |
Traditional Surrogate |
Hide Mother's Info |
Not Applicable |
|
|
18 |
PRI_PROBLEM_ID |
NUMERIC |
No |
|
|
|
The unique ID of the principal problem for a patient's hospitalization. |
|
|
19 |
EXPECTED_DISCHRG_APPROX_TIME_C_NAME |
VARCHAR |
No |
|
|
|
Current approximate expected discharge time. Each value represents a time range (e.g. Morning, Midday, Afternoon, Evening). |
May contain organization-specific values: Yes |
Category Entries: |
Morning |
Midday |
Afternoon |
Evening |
|
|
20 |
DISCH_MILEST_KICKOFF_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
Displays the date and time that discharge milestones were initiated. |
|
|
21 |
DISCH_MILEST_AUTO_MANAGED_YN |
VARCHAR |
No |
|
|
|
Determines if discharge milestones have had any manual intervention. Discharge Milestones are considered auto-managed if the discharge order is the sole driver for kicking off and discontinuing milestones. |
The category values for this column were already listed for column: MULTI_PREG_YN |
|
|
22 |
PREDICTED_LOS |
NUMERIC |
No |
|
|
|
The Length of Stay value determined by the Predictive Model run. |
|
|
23 |
EXP_LOS_UPD_SRC_C_NAME |
VARCHAR |
No |
|
|
|
The source (e.g. Predictive Model, User Entered) from which the Expected Length of Stay was updated. |
May contain organization-specific values: Yes |
Category Entries: |
User Entered |
Model Prediction |
Expected Discharge Date Update |
Expected Length of Stay Update |
Admission Planning Reservation Updated |
Discharge Order Filed |
|
|
24 |
ED_ENC_SRC_C_NAME |
VARCHAR |
No |
|
|
|
This column stores how an ED encounter was created (e.g. via interface, user workflows) |
May contain organization-specific values: No |
Category Entries: |
Standard |
Interface |
Kiosk |
Online |
Call Center / Clinic Referral |
Scheduling |
|
|
25 |
ED_DEPART_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The ED Departure date and time in UTC. |
|
|
26 |
ADT_ARRIVAL_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The arrival date and time in UTC. |
|
|
27 |
HOSP_DISCH_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The hospital discharge date and time in UTC. |
|
|
28 |
HOSP_ADMSN_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The hospital admission date and time in UTC. |
|
|
29 |
INP_ADMSN_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The date and time that the patient first reached a patient class of Inpatient in UTC. |
|
|
30 |
ED_HISTORICAL_YN |
VARCHAR |
No |
|
|
|
ED Historical Encounter is set by cutover and historical encounter interfaces when patient encounters are created for emergency patients. |
May contain organization-specific values: No |
Category Entries: |
Yes |
No |
|
|
31 |
PATIENT_TASK_COMPLETION_RATE |
INTEGER |
No |
|
|
|
Aggregated task progression rates across all active tasks currently assigned to the patient. |
|
|
32 |
START_MED_REM_DISCHG_YN |
VARCHAR |
No |
|
|
|
If set to 1-Yes, medication reminders will start automatically after discharge. If set to 0-No or empty, medication reminders will not start automatically after discharge. |
The category values for this column were already listed for column: MULTI_PREG_YN |
|
|
33 |
EXPECTED_DISCHARGE_UNKNOWN_YN |
VARCHAR |
No |
|
|
|
Indicates whether the expected discharge date is unknown for this patient. 'Y' indicates that the expected discharge date is unknown and documented. 'N' indicates that the expected discharge date is known and documented. NULL indicates that no expected discharge info has been saved for this contact. |
The category values for this column were already listed for column: MULTI_PREG_YN |
|
|
34 |
DUAL_ADMISSION_CSN |
NUMERIC |
No |
|
|
|
In a dual admission scenario this will point from the encounter on leave to the admitted encounter. |
|
|
35 |
LOA_PAT_ENC_CSN_ID |
NUMERIC |
No |
|
|
|
This column is only populated when the encounter for this row is admitted and the patient currently has an encounter on a leave of absence. This column displays the unique contact serial number of the patient encounter that is on a leave of absence. |
|
|
36 |
INITIAL_ADT_PAT_STAT_C_NAME |
VARCHAR |
No |
|
|
|
The ADT type of encounter category ID initially assigned for the encounter. |
May contain organization-specific values: No |
Category Entries: |
Preadmission |
Admission |
Discharged |
Leave of Absence |
Hospital Outpatient Visit |
|
|
37 |
NOTIFICATION_SENT_FIRST_IP_YN |
VARCHAR |
No |
|
|
|
Indicates whether the Event Notification message was sent when the patient was upgraded to an IP class. 'Y' indicates that the message was sent. 'N' or NULL indicate that the message was not sent. Note that this message is only sent once, even though the date and time the patient became IP can be changed. |
The category values for this column were already listed for column: MULTI_PREG_YN |
|
|
38 |
NOTIFICATION_SENT_OBS_ADMSN_YN |
VARCHAR |
No |
|
|
|
Indicates whether the Event Notification message was sent when the patient was upgraded to an observation patient class. 'Y' indicates that the message was sent. 'N' or NULL indicate that the message was not sent. Note that this message is only sent once, even though the date and time the patient became observation can be changed. |
The category values for this column were already listed for column: MULTI_PREG_YN |
|
|
39 |
IB_ALERT_LENGTH_OF_STAY_MSG_ID |
VARCHAR |
No |
|
|
|
The unique ID of the In Basket Message that was sent to alert that a patient has gone past the approved length of stay. |
|
|
40 |
INITIAL_ADMIT_CONF_STAT_C_NAME |
VARCHAR |
No |
|
|
|
The encounter status category ID initially assigned to this encounter. |
May contain organization-specific values: No |
Category Entries: |
Confirmed |
Pending |
Canceled |
Completed |
|
|
41 |
TRANSFER_COMMENTS |
VARCHAR |
No |
|
|
|
The transfer comments entered by the user during the most recent transfer. |
|
|
42 |
MED_READINESS_DTTM |
DATETIME (Local) |
No |
|
|
|
The medical readiness date and time for this patient encounter. This date and time may be expected or confirmed, depending on whether the patient is medically ready or not. |
|
|
43 |
MED_READINESS_TIMEFRAM_C_NAME |
VARCHAR |
No |
|
|
|
The medical readiness timeframe category ID for the patient encounter |
May contain organization-specific values: No |
Category Entries: |
Now |
Anticipated Today |
Anticipated Tomorrow |
Anticipated in 2-4 Days |
Anticipated in 5+ Days |
|
|
44 |
MED_READINESS_YN |
VARCHAR |
No |
|
|
|
Indicates whether this patient encounter is medically ready for discharge. 'Y' indicates that this encounter has been marked medically ready for discharge. 'N' or NULL indicates that it has not been marked medically ready for discharge. |
The category values for this column were already listed for column: MULTI_PREG_YN |
|
|
45 |
MED_READINESS_INST_ENTRY_DTTM |
DATETIME (UTC) |
No |
|
|
|
The instant at which this patient's medical readiness information was last updated |
|
|
46 |
MED_READINESS_USER_ID |
VARCHAR |
No |
|
|
|
The unique ID of the user who last updated medical readiness information for this patient encounter |
|
|
47 |
MED_READINESS_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
48 |
MED_READINESS_SOURCE_C_NAME |
VARCHAR |
No |
|
|
|
The medical readiness source category ID for this patient encounter |
May contain organization-specific values: No |
Category Entries: |
SmartList |
Expected Discharge Date Section |
Update Order |
Discharge Order |
Automatic Update |
Reviewed |
|
|
49 |
EXPECTED_DISCH_DISP_C_NAME |
VARCHAR |
No |
|
|
|
The patient's expected discharge disposition. |
May contain organization-specific values: Yes |
Category Entries: |
Home or Self Care |
Home Health Services |
Assisted Living Facility |
Behavioral Health Facility |
Hospice - Home |
Hospice - Residential |
Inpatient Rehab Facility |
Long Term Acute Care Hospital |
Skilled Nursing Facility |
Transfer to Other Acute Facility |
Other (Comment) |
|
|
50 |
EXP_DISCH_DISP_USER_ID |
VARCHAR |
No |
|
|
|
This item logs the last user that changed the expected discharge disposition. |
|
|
51 |
EXP_DISCH_DISP_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
52 |
EXP_DISCH_DISP_ENTRY_UTC_DTTM |
DATETIME (UTC) |
No |
|
|
|
The instant of entry of expected discharge disposition. |
|
|
53 |
PRIMARY_LINKED_PAT_ENC_CSN_ID |
NUMERIC |
No |
|
|
|
The unique contact serial number of the primary linked hospital encounter. Encounters are considered linked if the start of encounter B occurs after the start of encounter A, but within 6 hours after the discharge of encounter A (including before the discharge of encounter A). Any encounters that would be linked to encounter B by that definition are instead linked to encounter A. This means that there is exactly one primary encounter for every series of linked encounters and that the primary linked encounter is the one within a series that has the earliest start time. |
|
|