|
Name |
Type |
Discontinued? |
|
1 |
EVENT_ID |
VARCHAR |
No |
|
|
|
The unique ID of the event record. |
|
|
2 |
LINE |
INTEGER |
No |
|
|
|
The line number for the information associated with this event. Multiple pieces of information can be associated with this record. |
|
|
3 |
EVENT_DISPLAY_NAME |
VARCHAR |
No |
|
|
|
The display name of the event. |
|
|
4 |
EVENT_TIME |
DATETIME (Local) |
No |
|
|
|
The instant when the event occurred. |
|
|
5 |
EVENT_RECORD_TIME |
DATETIME (Local) |
No |
|
|
|
The instant when the event was recorded. |
|
|
6 |
EVENT_USER_ID |
VARCHAR |
No |
|
|
|
The unique ID of the user who initiated the event. This column is frequently used to link to the CLARITY_EMP table. |
|
|
7 |
EVENT_USER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
8 |
EVENT_CMT |
VARCHAR |
No |
|
|
|
The comments entered for the event. |
|
|
9 |
EVENT_DEPT_ID_EXTERNAL_NAME |
VARCHAR |
No |
|
|
|
The external name of the department record. This is often used in patient correspondence such as reminder letters. |
|
|
10 |
ADT_EVENT_ID |
NUMERIC |
No |
|
|
|
The unique ID of the Admission, Transfer, Discharge, or Leave of Absence (ADT) event record link that is associated with this event. The following ED events have linked ADT evens: ED Roomed (A) ED Transfer (T) ED Admit to Hospital (T) |
|
|
11 |
STAFFED_BEDS |
NUMERIC |
No |
|
|
|
The number of staffed beds for a department at the time of the event. This item is populated only if you are using the Staffed Beds activity. |
|
|
12 |
EVENT_KEY |
VARCHAR |
No |
|
|
|
A unique key associated with this event. The key is stored in other master files in order to reference this event. |
|
|
13 |
EVENT_NOTE_ID |
VARCHAR |
No |
|
|
|
The unique ID of the note that is associated with this event. |
|
|
14 |
EVENT_FINDING_ID |
NUMERIC |
No |
|
|
|
The unique ID of the result that is associated with this event. This column is frequently used to link to the ORDER_RES table. |
|
|
15 |
EVENT_IMPLANT_ID |
VARCHAR |
No |
|
|
|
The unique ID of the implant that is associated with this event. This column is frequently used to link to the OR_IMP table. |
|
|
16 |
EVENT_LINE_DATA_ID |
VARCHAR |
No |
|
|
|
The line number of the associated data stored for this event in OpTime's Log Entry activity. This column can be used to link to the OR_LNLG_GENERAL table. |
|
|
17 |
EVENT_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. |
|
|
18 |
LOCATION_ID |
NUMERIC |
No |
|
|
|
The unique ID of the patient location record that is associated with this event. This link is available only for emergency department contacts and for any location definition in the patient location facility master file that is associated with an event template master file. This column can be used to link to the CL_PLC table. |
|
|
19 |
EVENT_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
The category number for the event's status. |
May contain organization-specific values: No |
Category Entries: |
Active |
Inactive |
Deleted |
Inactive and Deleted |
Hidden |
Inactive and Hidden |
Deleted and Hidden |
Inactive Deleted and Hidden |
|
|
20 |
REC_VERB_ORD_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
The Inpatient reconciliation verbal order type flag category number for the event. |
May contain organization-specific values: Yes |
Category Entries: |
Ordering |
Cosign |
Discontinuing |
Pending Discontinue |
Edit |
Delete |
Continue on Transfer |
Discontinue on Transfer |
New on Transfer |
Unreview on Transfer |
Holding |
Unholding |
Order and Hold |
Assigning Administration Responsibility |
Cancel Hold |
Discontinue on Admission |
Discontinue on Discharge |
Sign on Admission |
Sign on Discharge |
Modify for Admission |
Modify for Discharge |
Modify for Transfer |
Continue on Admission |
Continue on Discharge |
Do Not Order on Admission |
Do Not Prescribe on Discharge |
Do Not Order on Transfer |
Sign on Inter-Facility Transfer |
Modify for Inter-Facility Transfer |
Discontinue on Inter-Facility Transfer |
Continue on Inter-Facility Transfer |
Do Not Order on Inter-Facility Transfer |
Pause on Discharge |
Resume from Pause on Discharge |
|
|
21 |
REC_VRB_ORD_COMM_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. |
|
|
22 |
REC_VRB_SIGNER_ID |
VARCHAR |
No |
|
|
|
The unique ID of the provider who is the Inpatient reconciliation verbal order signer for this event. This column is frequently used to link to the CLARITY_SER table. |
|
|
23 |
REC_VRB_SIGNER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
24 |
REC_VRB_ORD_MODE_C_NAME |
VARCHAR |
No |
|
|
|
The Inpatient reconciliation verbal order mode category number for the event. |
May contain organization-specific values: Yes |
Category Entries: |
Verbal |
Standard |
|
|
25 |
REC_ORD_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. |
|
|
26 |
REC_PROC_AUTH_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. |
|
|
27 |
REC_MED_AUTH_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. |
|
|
28 |
REC_PROC_MSG_RCP_ID |
VARCHAR |
No |
|
|
|
The unique ID of the provider who is the Inpatient reconciliation procedure cosign message recipient for this event. This column is frequently used to link to the CLARITY_SER table. |
|
|
29 |
REC_PROC_MSG_RCP_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
30 |
REC_MED_MSG_RCP_ID |
VARCHAR |
No |
|
|
|
The unique ID of the provider who is the Inpatient reconciliation medication cosign message recipient for this event. This column is frequently used to link to the CLARITY_SER table. |
|
|
31 |
REC_MED_MSG_RCP_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
32 |
REC_IS_PROC_HOSP_YN |
VARCHAR |
No |
|
|
|
Indicates whether the Inpatient reconciliation procedure hospitalist flag is set for this event. |
May contain organization-specific values: No |
Category Entries: |
Yes |
No |
|
|
33 |
REC_IS_MED_HOSP_YN |
VARCHAR |
No |
|
|
|
Indicates whether the Inpatient reconciliation medication hospitalist flag is set for this event. |
The category values for this column were already listed for column: REC_IS_PROC_HOSP_YN |
|
|
34 |
REC_VERB_ORD_CMT |
VARCHAR |
No |
|
|
|
The comments entered by the user who placed the Inpatient reconciliation verbal order associated with the event. |
|
|
35 |
REC_ADMIT_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
The category number for the status of the Inpatient order reconciliation associated with this event. |
May contain organization-specific values: Yes |
|
|
36 |
IP_REC_NOTE_ID |
VARCHAR |
No |
|
|
|
The unique ID of the order reconciliation (process of reviewing a orders when the patient moves to another level or area of care) note that is the associated with this event. |
|
|
37 |
EVENT_LOG_ID |
VARCHAR |
No |
|
|
|
The unique ID of the surgical log that is associated with this event. This column is frequently used to link to the OR_LOG table. |
|
|
38 |
EVENT_SUPPLY_ID |
VARCHAR |
No |
|
|
|
The unique ID of the supply that is associated with "supply used" events generated in Cupid "add supply" workflows. This column should be used to link to the OR_SPLY table. |
|
|
39 |
EVENT_SUPPLY_ID_SUPPLY_NAME |
VARCHAR |
No |
|
|
|
The name of the inventory item. |
|
|
40 |
EVENT_INI_RECORD_ID |
VARCHAR |
No |
|
|
|
The master file and ID of the source of a duplicate procedure alert event. For example, this item usually holds LDG-ID (the ID of the procedure duplicate group used) or EAP-ID (the ID of the procedure used). |
|
|
41 |
EVENT_CONTEXT |
VARCHAR |
No |
|
|
|
For some events, this column holds the context of the event. Lab Ordered events might store the order ID here. Duplicate procedure alert events might store information on specific user actions in response to the alert. |
|
|
42 |
SOURCE_PX_ID_PROC_NAME |
VARCHAR |
No |
|
|
|
The name of each procedure. |
|
|
43 |
SOURCE_PX_INFO |
VARCHAR |
No |
|
|
|
Detailed information about the duplicate procedure checked in SOURCE_PX_ID. |
|
|
44 |
MATCH_PX_ID_PROC_NAME |
VARCHAR |
No |
|
|
|
The name of each procedure. |
|
|
45 |
MATCH_PX_INFO |
VARCHAR |
No |
|
|
|
Detailed information about the duplicate procedure checked in MATCH_PX_ID. |
|
|
46 |
EVENT_SIGN_OFF_ID |
NUMERIC |
No |
|
|
|
The record that contains all the sign off information for this event. |
|
|
47 |
DEPT_SCORE |
NUMERIC |
No |
|
|
|
Stores the numeric department score for department-specific events records. When a department scoring system is coordinated with a department event, the score calculated is saved in this item. It groups the score to the specific event instant, type, etc. from which the score was calculated. |
|
|
48 |
STAFF_ROLE_C_NAME |
VARCHAR |
No |
|
|
|
For a staff sign-in or sign-out event, this item holds what their role was when they signed in. |
May contain organization-specific values: Yes |
|
|
49 |
STAFF_IS_ATTN_YN |
VARCHAR |
No |
|
|
|
For a staff sign-in or sign-out event, this item holds whether or not the user signed in as an attending provider. |
May contain organization-specific values: No |
Category Entries: |
No |
Yes |
|
|
50 |
LINKED_IEV_REC_ID |
VARCHAR |
No |
|
|
|
When linking two events, this item holds the record ID of the linked event. Use this in combination with the line number. |
|
|
51 |
LINKED_IEV_LINE |
INTEGER |
No |
|
|
|
When linking two events, this item holds the line number of the linked event within its respective record. Use this in combination with the record ID. |
|
|
52 |
EVENT_TYPE_VERSION |
NUMERIC |
No |
|
|
|
If the data model for a particular event type changes, this item can be used to say which version of the data model is being used. Assume that blank is version 1. The version number only has meaning in relation to EVENT_TYPE. |
|
|
53 |
EVENT_OWNER_ID |
VARCHAR |
No |
|
|
|
Stores the owner of the event. |
|
|
54 |
EVENT_OWNER_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
55 |
PEND_ACTIVE_C_NAME |
VARCHAR |
No |
|
|
|
This column shows the current pend (group of pended orders) status. Each pend type has a separate active status. A pend can also have a status of cleanup needed. A null status is used for pends that are no longer in use. |
May contain organization-specific values: No |
Category Entries: |
Active Public |
Active Private |
Cleanup Needed |
|
|
56 |
PEND_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
The status of the pended orders. |
May contain organization-specific values: No |
Category Entries: |
Active Public |
Active Private |
Restored |
Deleted |
Expired |
Replaced |
|
|
57 |
PEND_RESTORED_BY_ID |
VARCHAR |
No |
|
|
|
Unique ID of the user who restored the pended orders. |
|
|
58 |
PEND_RESTORED_BY_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
59 |
PEND_RESTORED_DTTM |
DATETIME (UTC) |
No |
|
|
|
Instant the pended orders were restored. |
|
|
60 |
PEND_DELETED_BY_ID |
VARCHAR |
No |
|
|
|
Unique ID of the user who deleted pended orders. |
|
|
61 |
PEND_DELETED_BY_ID_NAME |
VARCHAR |
No |
|
|
|
The name of the user record. This name may be hidden. |
|
|
62 |
PEND_DELETED_I_DTTM |
DATETIME (UTC) |
No |
|
|
|
The instant pended orders were deleted. |
|
|
63 |
PEND_COMMENT |
VARCHAR |
No |
|
|
|
User or autogenerated comment about the pended orders. |
|
|
64 |
PEND_CHANGE_COUNT |
INTEGER |
No |
|
|
|
Count of number of changes from a user perspective (some actions will not count as changes) |
|
|
65 |
PEND_INSTANT_DTTM |
DATETIME (UTC) |
No |
|
|
|
Instant that the pended orders were created. |
|
|
66 |
PEND_CREATE_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
Category indicating how these orders were pended such as automatically on timeout. |
May contain organization-specific values: No |
Category Entries: |
Normal/Default |
Automatically Saved |
Automatically Saved When Another User Logged In |
Saved on Closing Chart |
Automatically Saved on Timeout |
Context Changed |
Automatically Saved on Encounter Department Change |
|
|
67 |
EVENT_OVRIDE_RSN_C_NAME |
VARCHAR |
No |
|
|
|
Stores override reason for not scanning patient to verify the event. |
May contain organization-specific values: Yes |
|
|
68 |
EVENT_LABEL |
VARCHAR |
No |
|
|
|
The label for the value associated with an event. |
|
|
69 |
EVENT_VALUE |
VARCHAR |
No |
|
|
|
The value associated with an event. |
|
|
70 |
NOTIFY_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
Store the current status for a bed planning notification |
May contain organization-specific values: No |
Category Entries: |
Active |
Resolved |
Resolved Through Notification |
Dismissed |
No Longer Valid |
|
|
71 |
NOTIFY_PND_STATUS_C_NAME |
VARCHAR |
No |
|
|
|
Store the status of why a bed request is being escalated |
May contain organization-specific values: No |
Category Entries: |
Ready to Plan |
Assigned |
Rejected |
Approved |
Requested |
Preassigned |
Bed Ready |
|
|
72 |
AN_LINKED_EVENT_ID |
VARCHAR |
No |
|
|
|
Stores the record ID of an event that is linked to another Anesthesia event. |
|
|
73 |
AN_LINKED_EVENT_LINE |
INTEGER |
No |
|
|
|
When linking an Anesthesia event to another event, this item holds the line number of the linked event within its respective record. |
|
|
74 |
ED_C_CLIENT_SRC_C_NAME |
VARCHAR |
No |
|
|
|
This tracks from what client the user filed an ED Course event. |
May contain organization-specific values: No |
Category Entries: |
Hyperspace |
Limerick |
Haiku |
Canto |
|
|
75 |
CT_EVENT_FILED_BY_C_NAME |
VARCHAR |
No |
|
|
|
If an event was filed automatically by a Case Tracking Event, this item holds the category ID of the case tracking event that did it |
May contain organization-specific values: Yes |
|
|
76 |
TRANSPORT_ID |
NUMERIC |
No |
|
|
|
This item stores the ID of the transport request that triggered the event, if applicable. |
|
|
77 |
TXPORT_HLR_ID |
NUMERIC |
No |
|
|
|
The unique ID of the logistics patient transport request (HLR) that triggered the event. |
|
|
78 |
EVENT_ORIGIN_C_NAME |
VARCHAR |
No |
|
|
|
This indicates whether the event came from an internal or external source. If blank, the event came from an internal source. |
May contain organization-specific values: No |
Category Entries: |
Internal |
External |
|
|
79 |
RX_REQUEST_TYPE_C_NAME |
VARCHAR |
No |
|
|
|
If this event represents orders created from an incoming Rx request, this indicates the type of the request (New Rx, Renewal, etc.). |
May contain organization-specific values: No |
Category Entries: |
Refill Request |
Therapeutic Change |
Generic Substitution |
Other Change |
Medication Unavailable at Selected Pharmacy |
Drug Use Evaluation Conflict |
Script Clarification |
Prescriber Authorization |
NewRx Request |
|
|
80 |
RX_REQUEST_PHARMACY_ID |
NUMERIC |
No |
|
|
|
If this event represents orders created from an incoming Rx request, this indicates the pharmacy that requested the medications. |
|
|
81 |
RX_REQUEST_PHARMACY_ID_PHARMACY_NAME |
VARCHAR |
No |
|
|
|
The name of the pharmacy. |
|
|
82 |
RX_REQUEST_VIEWED_YN |
VARCHAR |
No |
|
|
|
If this event represents orders created from an incoming Rx request, this indicates whether any user has viewed the requested medications. Once the request has been viewed, no more orders can be added to it. |
The category values for this column were already listed for column: STAFF_IS_ATTN_YN |
|
|
83 |
TRANSFER_DEST_DEPT_ID_EXTERNAL_NAME |
VARCHAR |
No |
|
|
|
The external name of the department record. This is often used in patient correspondence such as reminder letters. |
|
|