Table Detail Report
ORDERS
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | ORDERS |
Definition: | The table storing all orders within HNA |
Table Type: | ACTIVITY |
Column Detail - ORDERS
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTIVE_IND | DOUBLE | Y | The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
ACTIVE_STATUS_CD | DOUBLE | N | Indicates the status of the row itself (not the data in the row) such as active, inactive, combined away, pending purge, etc. |
ACTIVE_STATUS_DT_TM | DATETIME | Y | The date and time that the active_status_cd was set. |
ACTIVE_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the active_status_cd to be set or change. |
ACTIVITY_TYPE_CD | DOUBLE | N | A grouping mechanism within catalog type code |
AD_HOC_ORDER_FLAG | DOUBLE | N | Flag to indicate an order is ad hoc in nature. 0 - the order is not ad hoc, 1 - the order is ad hoc via Bridge Interface, 2 - Ad hoc Order with completed order and task via Cerner Solutions, 3 - Ad hoc Order with pending task and order in ordered status via UBC (Unit-Based Cabinet). |
CATALOG_CD | DOUBLE | N | The coded value for the order catalog for this order. |
CATALOG_TYPE_CD | DOUBLE | N | A grouping mechanism to bring order catalogs together. |
CKI | VARCHAR(255) | Y | This field is based on the order_catalog table and is used for meds processing. The field is truncated and will contain a maximum of 254 characters. |
CLINICAL_DISPLAY_LINE | VARCHAR(255) | Y | A formatted display line of user selected order details. The field is truncated and will contain a maximum of 254 characters. When the field is truncated, it will be terminated with ellipsis. |
CLIN_RELEVANT_UPDT_DT_TM | DATETIME | N | The date and time when a change that is relavant to care providers was made to the order. For example, during a modify action, if the frequency is changed, then this field will get updated with the date and time when the modify was performed. |
CLIN_RELEVANT_UPDT_TZ | DOUBLE | N | The time zone associated with the clin_relavant_upt_dt_tm column. This is a patient centric time zone. |
COMMENT_TYPE_MASK | DOUBLE | Y | This is a mask of comment types so that we can tell what kind of comments are being used per order. |
CONSTANT_IND | DOUBLE | Y | If this indicator is set, the order is applied constantly for a period of time. Ex IV, heating pad. |
CONTRIBUTOR_SYSTEM_CD | DOUBLE | N | Contributor system identifies the source feed of data from which a row was populated. This is mainly used to determine how to update a set of data that may have originated from more than one source feed. |
CS_FLAG | DOUBLE | Y | Bit mask on whether this order is a parent or member of a Care Set. |
CS_ORDER_ID | DOUBLE | N | The order of the parent of this Care Set. |
CURRENT_START_DT_TM | DATETIME | Y | The start date/time of this order. |
CURRENT_START_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
DAY_OF_TREATMENT_SEQUENCE | DOUBLE | Y | The sequence of a day of treatment order. This field will be valued when the order relates to a protocol (protocol_order_id). This field will be unique across all day of treatment orders for a given protocol order ID. There is no standard pattern of sequence (i.e. increment by one) across day of treatments. |
DCP_CLIN_CAT_CD | DOUBLE | N | The clinical category the order is part of. |
DEPT_MISC_LINE | VARCHAR(1000) | Y | Text filled in by the department. The field is truncated and will contain a maximum of 254 characters. Ellipses are not appended if the field is truncated. |
DEPT_STATUS_CD | DOUBLE | N | The departmental status of the order. |
DISCONTINUE_EFFECTIVE_DT_TM | DATETIME | Y | The date and time the discontinue action should become effective. |
DISCONTINUE_EFFECTIVE_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
DISCONTINUE_IND | DOUBLE | Y | Indicator on whether this order has been discontinued. |
DISCONTINUE_TYPE_CD | DOUBLE | N | Indicates by what method the order was discontinued. |
DOSING_METHOD_FLAG | DOUBLE | N | Indicates the type of dosing that is applied to the order. Values: 0 - no special dosing applies to this order, 1 - variable dosing exists for the ingredients of this order (which is only applicable for medication orders). |
ENCNTR_FINANCIAL_ID | DOUBLE | N | The financial id for the encounter id. |
ENCNTR_ID | DOUBLE | N | Encounter which the order is associated with. |
ESO_NEW_ORDER_IND | DOUBLE | Y | This tells the ESO server whether they have sent it outbound before or not. |
FORMULARY_STATUS_CD | DOUBLE | Y | The latest formulary status for the order's ingredients. Formulary status denotes whether an ingredient is recommended in a specific facility due to cost/availability. Formulary status will only be populated for pharmacy orders. For all non-pharmacy orders or orders for which formulary status cannot be determined, a value of 0 will be populated. All orders that exist before the concept of formulary status was introduced will have a NULL formulary status. |
FREQUENCY_ID | DOUBLE | N | Frequency from the frequency_schedule table associated with this order. This id is used to calculate the schedule for the order. |
FREQ_TYPE_FLAG | DOUBLE | Y | Type of frequency associated with the order. |
FUTURE_LOCATION_FACILITY_CD | DOUBLE | N | The future facility location that is proposed to be used for this order. The facility can change while the order is in a Future status; however, once the order is activated on an encounter, this field will retain its value and will not be altered. |
FUTURE_LOCATION_NURSE_UNIT_CD | DOUBLE | N | The future nurse unit location that is proposed to be used for this order. The nurse unit can change while the order is in a Future status; however, once the order is activated on an encounter, this field will retain its value and will not be altered. |
GROUP_ORDER_FLAG | DOUBLE | Y | A flag to note whether this order is part of a larger group. |
GROUP_ORDER_ID | DOUBLE | N | The order id for the parent of the group of orders. |
HIDE_FLAG | DOUBLE | Y | The order is cancelled because its parent is modified. Don't show it to the user if it's 1. |
HNA_ORDER_MNEMONIC | VARCHAR(1000) | Y | The primary mnemonic of the orderable item from which the order is created. This is the common name recognized by all clinicians who provide services to patients. For Pharmacy orders, this is the legal generic name. It normally is carried forward from primary_mnemonic field in order_catalog table. The field is truncated and will contain a maximum of 99 characters. Ellipses are not appended if the field is truncated. |
INCOMPLETE_ORDER_IND | DOUBLE | Y | When an order is in an incomplete status or would be if it weren't in an on-hold status. |
INGREDIENT_IND | DOUBLE | Y | An indicator on whether this order has multiple ingredients. |
INTEREST_DT_TM | DATETIME | Y | Currently not being used. If populated, contains the date/time for which this order should no longer appear on various reports. |
INTERVAL_IND | DOUBLE | Y | Indicates if the order is part of interval test or not. |
IV_IND | DOUBLE | Y | An indicator on whether this order is an IV. |
IV_SET_SYNONYM_ID | DOUBLE | N | The ID that uniquely identifies the IV set used to place the order. This field is only valued for IV orders that start with an IV set, and cannot be altered during subsequent order actions. |
LAST_ACTION_SEQUENCE | DOUBLE | Y | The sequence number of the last action. |
LAST_CORE_ACTION_SEQUENCE | DOUBLE | Y | Shows the last action that changed details. |
LAST_INGRED_ACTION_SEQUENCE | DOUBLE | Y | Last action sequence that contained an ingredient. |
LAST_UPDATE_PROVIDER_ID | DOUBLE | N | The id representing the provider on the last action of the order where it was present. For example, on initial ordering if a provider id "123" is populated and then a modify action is performed on the order without populating the provider id, then this field will have a provider id of "123" which is the last valued provider id. To obtain values for each action, the provider_id from the order_action table should be read. |
LATEST_COMMUNICATION_TYPE_CD | DOUBLE | Y | CODE SET: 6006.The code value identifying the communication type of the order on the last action where it was present. For example, on initial ordering if a communication type of "FAX" is populated and then a modify action is performed on the order without populating the communication type, then this field will have a communication type of "FAX", which is the last valued communication type cd. To obtain values for each action, the communication_type_cd from the order_action should be read. |
LINK_NBR | DOUBLE | Y | Identifies a unique link and associates the orders that are members of the link. |
LINK_ORDER_FLAG | DOUBLE | Y | Flag on whether this order is linked to another. 0 - Order is not linked, 1 - Order is linked |
LINK_ORDER_ID | DOUBLE | N | The id of the linked order. |
LINK_TYPE_FLAG | DOUBLE | Y | Describes the kind of link the order was placed with. 0 - Not linked. 1 - AND linked. |
MED_ORDER_TYPE_CD | DOUBLE | N | The type of medication order. An example would be dialysis, IV, irrigation, etc. |
MODIFIED_START_DT_TM | DATETIME | Y | Date that the duration was modified. |
NEED_DOCTOR_COSIGN_IND | DOUBLE | Y | Indicator on whether a doctor needs to cosign this order. 0 - Does not need doctor cosign, 1 - Needs doctor cosign, 2 - Cosign notification is refused by doctor. |
NEED_NURSE_REVIEW_IND | DOUBLE | Y | Indicator on whether the nurse needs to cosign this order. |
NEED_PHYSICIAN_VALIDATE_IND | DOUBLE | Y | When = 0 it doesn't need a physician validation, and when = 1 needs physician validation. |
NEED_RX_CLIN_REVIEW_FLAG | DOUBLE | N | Indicates the clinical review status of the order. 0 - Unset, 1 - Needs Review, 2 - Review Completed, 3 - Rejected, 4 - Does Not Apply. |
NEED_RX_VERIFY_IND | DOUBLE | Y | Indicates if Pharmacy verification is needed: 0 - Does not need verification; 1 - Needs verification; 2 - Rejected or Halted. Not applicable for continuing child orders ( TEMPLATE_ORDER_FLAG of 2, 3, 4, or 6) |
OE_FORMAT_ID | DOUBLE | N | Id for the order entry format |
ORDERABLE_TYPE_FLAG | DOUBLE | Y | Used to store the flag that indicates what type of orderable procedure the item has been assigned. |
ORDERED_AS_MNEMONIC | VARCHAR(1000) | Y | The mnemonic used by direct care providers (physicians, nurses, etc.) when they place orders in applications such as PowerOrders. This field is important for free text orderables, since hna_order_mnemonic is a generic name and ordered_as_mnemonic carries specific information about the order. The field is truncated and will contain a maximum of 99 characters. Ellipses are not appended if the field is truncated. |
ORDER_COMMENT_IND | DOUBLE | Y | Indicator on whether this order has a comment associated with it. |
ORDER_DETAIL_DISPLAY_LINE | VARCHAR(255) | Y | The department display line for the order based on the user selected order entry fields. The field is truncated and will contain a maximum of 254 characters. Ellipses are not appended if the field is truncated. |
ORDER_ID | DOUBLE | N | Order ID to which this transfer record is associated. |
ORDER_MNEMONIC | VARCHAR(1000) | Y | The mnemonic mostly used by department personnel, for example, Lab Technicians, Pharmacists. For Pharmacy orders, this field is not populated until product is assigned by Pharmacy Technician or Pharmacist. The field is truncated and will contain a maximum of 99 characters. Ellipses are not appended if the field is truncated. |
ORDER_REVIEW_STATUS_REASON_BIT | DOUBLE | Y | Indicates the reasons for the review status of the order. The first bit (2^0) indicates that the Rx verify review was removed because of the user endstate action. The second bit (2^1) indicates that the Rx verify review was removed because of the system endstate action. |
ORDER_SCHEDULE_PRECISION_BIT | DOUBLE | N | A bitmask which indicates the precision of the order schedule (start and stop date/times). If this mask is 0, the start and stop date/time are precise. If the mask is valued, it indicates aspects of the order schedule are estimated (not precise). The 1st bit (2^0) indicates if the start date/time is estimated. The 2nd bit (2^1) indicates if the stop date/time is estimated. |
ORDER_STATUS_CD | DOUBLE | N | The code for the status the order is in. |
ORDER_STATUS_REASON_BIT | DOUBLE | Y | A bitmask which indicates additional reason details about the order status. If null, there are no additional details about the status. 1-3: Incomplete to pharmacy. 4-5: Administrations. |
ORIGINATING_ENCNTR_ID | DOUBLE | Y | For future orders (used for requests for consultation), Meaningful Use requires documentation of the encounter that created the future order. Since encntr_id is null for future orders (because the order will be assigned to a future encounter), a new field to track the originating encounter is needed. |
ORIG_ORDER_CONVS_SEQ | DOUBLE | Y | Stores the conversation sequence number for the new order action. This allows programs to sort by order date/time and this field to display orders to the user in the same order they were entered into the system. |
ORIG_ORDER_DT_TM | DATETIME | Y | The original order date and time for this order. |
ORIG_ORDER_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
ORIG_ORD_AS_FLAG | DOUBLE | Y | This flag shows how the order was processed by the system. This does not directly relate to the order's venue. There are cases where values of (0.0 Normal Order) and (5.0 Satellite) can be interchanged. https://wiki.cerner.com/display/public/reference/Configure+Additional+Orders+Features |
OVERRIDE_FLAG | DOUBLE | Y | Controls whether to call shareable or not. 0 - Normal process, 1 - Don't call below-the-line shareable. |
PATHWAY_CATALOG_ID | DOUBLE | N | Unique id from the pathway_catalog table that identifies the catalog pathway from which the order originated. |
PERSON_ID | DOUBLE | N | Person whom the order is placed for. |
PRESCRIPTION_GROUP_VALUE | DOUBLE | Y | System generated ID that groups prescriptions orders belonging to the same course of treatment. |
PRESCRIPTION_ORDER_ID | DOUBLE | N | This field applies to retail orders. It contains the order_id of the related prescription order. e.g. When a retail order is placed then the order_id of the prescription order that was used to create the retail order will be stored. |
PRN_IND | DOUBLE | Y | If this indicator is set, the order is to be be given "As needed". At the time this action occurred. |
PRODUCT_ID | DOUBLE | N | The product id for this order. A unique number that is system-assigned. The primary key to the product table. This column identifies the product for which the order was placed. If this column is filled out, then there is no person or encounter for this order. The product pertains to a blood product or derivative .within the PathNet Blood Bank Transfusion system. An example of an order placed. |
PROJECTED_STOP_DT_TM | DATETIME | Y | The projected stop and time for this order. |
PROJECTED_STOP_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
PROTOCOL_ORDER_ID | DOUBLE | N | Order_id of the protocol order that generates the Day of Treatment order. 0 for protocol orders and regular (non-protocol, non-DayOfTreatment) orders. The value is decided when the order is created and cannot be changed through the life time of the order. |
REF_TEXT_MASK | DOUBLE | Y | The reference text mask showing what online reference manual components have been associated with the order. NOTE: This column does NOT support multi-facility logic. It always comes from the Order_catalog table. 1 - Policies and Procedures, 2 - Nurse Prep, 4 - Patient Education, 8 - Scheduling Info, 16 - Careplan Info, 32 - Charting Guidelines, 64 - Multum. |
REMAINING_DOSE_CNT | DOUBLE | Y | Number of doses need to be completed before the order can be completed. Currently, it is only usedwhen projected_stop_dt_tm is left empty because it can not be calculated correctly. For example, PRN orders with dose-based duration. When projected_stop_dt_tm is populated (whether in Order action,or in subsequence actions), remaining_doses is reset to 0. When remaining_doses is set to a non-zero. |
RESUME_EFFECTIVE_DT_TM | DATETIME | Y | The effective date of the resume action. |
RESUME_EFFECTIVE_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
RESUME_IND | DOUBLE | Y | Indicator on whether this order is resumed. |
RX_MASK | DOUBLE | Y | The pharmacy mask showing how this order was placed (e.g. TPN order, Sliding Scale, Tapering Dose,etc.) 1 - Diluent (LVP), 2 - Additive (IVP), 4 - Med, 8 - TPN , 16 - Sliding Scale, 32 - Tapering Dose, 64 - PCA. |
SCH_STATE_CD | DOUBLE | N | Scheduling status of the order. |
SIMPLIFIED_DISPLAY_LINE | VARCHAR(1000) | Y | A simplified display line of user selected order details. The information in this field will be hard coded and only written for pharmacy orders. The field is truncated and will contain a maximum of 999 characters. When the field is truncated, it will be terminated with ellipsis. |
SOFT_STOP_DT_TM | DATETIME | Y | Filled out if an order has a stop type of hard on the order catalog. |
SOFT_STOP_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
SOURCE_CD | DOUBLE | N | This is a codified value which identifies the source of the order. |
STATUS_DT_TM | DATETIME | Y | The date and time of the last order status change. |
STATUS_PRSNL_ID | DOUBLE | N | The personnel id of the person changing the status. |
STOP_TYPE_CD | DOUBLE | N | Codified value based on codeset 4009 indicating what type of stop is associated with this order. Ex: Physician Stop, Hard Stop, Soft Stop. |
SUSPEND_EFFECTIVE_DT_TM | DATETIME | Y | The effective suspended date time. |
SUSPEND_EFFECTIVE_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
SUSPEND_IND | DOUBLE | Y | Indicator on whether the order is suspended. |
SYNONYM_ID | DOUBLE | N | Id of the synonym for this order. |
TEMPLATE_CORE_ACTION_SEQUENCE | DOUBLE | Y | Last core action sequence of the template order. |
TEMPLATE_DOSE_SEQUENCE | DOUBLE | N | Relates to the template order ingredient dose from which this order was spawned. This field is only applicable for pharmacy child orders which have a variable dose (dosing_method_flag = 1). For all other orders, this field will be 0. |
TEMPLATE_ORDER_FLAG | DOUBLE | Y | Illustrates how the order relates to template orders. Valid values are: 0 - None, 1 - Template, 2 - Order Based Instance, 3 - Task Based Instance, 4 - Rx Based Instance, 5- Future Recurring Template, 6 - Future Recurring Instance, 7 - Protocol. |
TEMPLATE_ORDER_ID | DOUBLE | N | Order id for the template order. |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
VALID_DOSE_DT_TM | DATETIME | Y | Used to capture a valid dose time of an order according its current frequency schedule. It is changed when order schedule is altered by certain actions, such as Modify and Reschedule. The field is not significant for floating schedules; however, it is populated with the time of the last action that alters the schedule. |
WARNING_LEVEL_BIT | DOUBLE | N | A bitmask which indicates if the order has a warning associated to it. If the bitmask is 0, no warning is associated to the order. If the mask is valued, it indicates that a warning is associated to the order. The lowest three bits indicate different level of warnings associated to the order. The 0th bit = Severe level, 1st bit = Audit level, and 2nd bit = Information level. The remaining bits will represent custom meanings (3rd bit and above). |
Relationship Detail - ORDERS
Child Column in ORDERS(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ENCNTR_FINANCIAL_ID | ENCNTR_FINANCIAL | ENCNTR_FINANCIAL_ID |
ENCNTR_ID | ENCOUNTER | ENCNTR_ID | |
ORIGINATING_ENCNTR_ID | ENCOUNTER | ENCNTR_ID | |
FREQUENCY_ID | FREQUENCY_SCHEDULE | FREQUENCY_ID | |
PRESCRIPTION_ORDER_ID | ORDERS | ORDER_ID | |
PROTOCOL_ORDER_ID | ORDERS | ORDER_ID | |
IV_SET_SYNONYM_ID | ORDER_CATALOG_SYNONYM | SYNONYM_ID | |
SYNONYM_ID | ORDER_CATALOG_SYNONYM | SYNONYM_ID | |
OE_FORMAT_ID | ORDER_ENTRY_FORMAT_PARENT | OE_FORMAT_ID | |
PATHWAY_CATALOG_ID | PATHWAY_CATALOG | PATHWAY_CATALOG_ID | |
PERSON_ID | PERSON | PERSON_ID | |
PRODUCT_ID | PRODUCT | PRODUCT_ID | |
LAST_UPDATE_PROVIDER_ID | PRSNL | PERSON_ID | |
STATUS_PRSNL_ID | PRSNL | PERSON_ID |
ORDER_ACTION
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Order Action |
Definition: | Stores all the actions associated with an order. |
Table Type: | ACTIVITY |
Column Detail - ORDER_ACTION
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTION_DT_TM | DATETIME | Y | The date and time of the action. |
ACTION_INITIATED_DT_TM | DATETIME | Y | The date/time at which the user initiated the action. |
ACTION_PERSONNEL_ID | DOUBLE | N | The id of the personnel that generated this action. |
ACTION_QUALIFIER_CD | DOUBLE | N | A codified value that helps further describe the order action. An example would be Product Assign. |
ACTION_REJECTED_IND | DOUBLE | Y | Indicator on whether the action was rejected. |
ACTION_SEQUENCE | DOUBLE | N | A sequence number used to identify the order of the actions. |
ACTION_TYPE_CD | DOUBLE | N | Code value to identify the action that was performed. |
ACTION_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
BILLING_PROVIDER_FLAG | DOUBLE | Y | Flag indicating which provider was specified as the billing provider. 0 - Not specified. 1 - Order provider. 2 - Supervising provider. |
CLINICAL_DISPLAY_LINE | VARCHAR(255) | Y | A formatted display line as of this particular order action, which is constructed from the selected order details by the user. |
COMMUNICATION_TYPE_CD | DOUBLE | N | The code value identify the communication type of the order. |
CONSTANT_IND | DOUBLE | N | If this indicator is set, the order is applied constantly for a period of time. Ex IV, heating pad. The value in this field is as of this action. |
CONTRIBUTOR_SYSTEM_CD | DOUBLE | N | Contributor system identifies the source feed of data from which a row was populated. This is mainly used to determine how to update a set of data that may have originated from more than one source feed. |
CORE_IND | DOUBLE | Y | Indicator field to mark if an action is core action or not. Order, Activate, Renew, Reschedule, Collection, Future DC are Core actions. If Modify action changes comment or core field, it's core action. Otherwise, it's non-core. |
CURRENT_START_DT_TM | DATETIME | Y | The current start/date time that was established for this action. This value will match the related ORDERS table record at the time of recording. This field may be null for previous activity data which existed before the service change to support recording this information. Activity data recorded after the creation of this field will always be populated with a date/time value. |
CURRENT_START_TZ | DOUBLE | Y | The time zone associated to the current_start_dt_tm field (time zone of the patient's encounter). This field may be null for previous activity data which existed before the service change to support recording this information. Activity data recorded after the creation of this field will always be populated with a value. If UTC is off in a domain, the value is guaranteed to be 0. If UTC is on in a domain, the value is guaranteed to be populated with a valid time zone index. |
DEPT_STATUS_CD | DOUBLE | N | Provides a more-detailed order status. Used to track the order status within a department. For example, a laboratory order may go through several different states before being completed, e.g. Collected, In-lab, Performed, Verified, etc. |
DIGITAL_SIGNATURE_IDENT | VARCHAR(64) | Y | Generated by the DMS interface, this identifier uniquely associates the order action taken by a caregiver with the recorded digitally-signed data. |
EFFECTIVE_DT_TM | DATETIME | Y | The effective date and time of the action. |
EFFECTIVE_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
ESO_ACTION_CD | DOUBLE | N | Identifies the action that was performed on ESO (External Systems Outbound) orders. Example, Modify, Cancel, Discontinue etc. |
FORMULARY_STATUS_CD | DOUBLE | Y | The formulary status for the order referenced by the given action at the time the action occurred. Formulary status denotes whether an ingredient is recommended in a specific facility due to cost/availability. Formulary status will only be populated for pharmacy orders. For all non-pharmacy orders or orders for which formulary status cannot be determined, a value of 0 will be populated. All orders that exist before the concept of formulary status was introduced will have a NULL formulary sta |
FREQUENCY_ID | DOUBLE | N | This id is used to calculate the schedule for the order. The value is as of this action. |
INACTIVE_FLAG | DOUBLE | Y | Unused. |
INCOMPLETE_ORDER_IND | DOUBLE | Y | Indicator on whether this action is incomplete, i.e. missing required order details. |
MEDSTUDENT_ACTION_IND | DOUBLE | Y | Show the actions that were done by a med student. |
NEEDS_VERIFY_IND | DOUBLE | Y | Indicator on whether this action needs to be verified. 0 No Verify Needed 1 Verify Needed 2 Superseded 3 Verified 4 Rejected 5 Reviewed. |
NEED_CLIN_REVIEW_FLAG | DOUBLE | N | A flag indicating whether this action needs to be clinically reviewed. |
NEXT_DOSE_DT_TM | DATETIME | Y | This is the date and time of the first dose that is generated for the current action. This field is not filled out for end-stating actions. |
ORDER_ACTION_ID | DOUBLE | N | The unique key for this order action. |
ORDER_APP_NBR | DOUBLE | Y | The application number for the ordering program. |
ORDER_CONVERSATION_ID | DOUBLE | N | The id for the conversation this action was done in. While this column is populated from sequence ORDER_SEQ, it is not related to a primary key column. |
ORDER_CONVS_SEQ | DOUBLE | Y | The sequence of the actions within a conversation. |
ORDER_DETAIL_DISPLAY_LINE | VARCHAR(255) | Y | The department display line as of this particular order action, which is constructed from the selected order details by the user. |
ORDER_DT_TM | DATETIME | Y | The date and time of the order. |
ORDER_ID | DOUBLE | N | The id of the order. |
ORDER_LOCN_CD | DOUBLE | N | Identifies the location of the patient when the action is performed. |
ORDER_PROVIDER_ID | DOUBLE | N | The id of the ordering provider. |
ORDER_REVIEW_STATUS_REASON_BIT | DOUBLE | Y | Indicates the reasons for the review status of the order. The first bit (2^0) indicates that the Rx verify review was removed because of the user endstate action. The second bit (2^1) indicates that the Rx verify review was removed because of the system endstate action. |
ORDER_SCHEDULE_PRECISION_BIT | DOUBLE | N | A bitmask which indicates the precision of the order schedule (start and stop date/times). If this mask is 0, the start and stop date/time are precise. If the mask is valued, it indicates aspects of the order schedule are estimated (not precise). The 1st bit (2^0) indicates if the start date/time is estimated. The 2nd bit (2^1) indicates if the stop date/time is estimated. |
ORDER_STATUS_CD | DOUBLE | N | The order status of the order after this action was posted to the database. Example, Ordered, Pending, Suspended, Canceled, Completed etc. |
ORDER_STATUS_REASON_BIT | DOUBLE | Y | A bitmask which indicates additional reason details about the order status. If null, there are no additional details about the status. 1-3: Incomplete to pharmacy. 4-5: Administrations. |
ORDER_TZ | DOUBLE | Y | Time zone associated with the corresponding DT_TM column. |
PRN_IND | DOUBLE | N | If this indicator is set, the order is to be given "As needed". At the time this action occurred. The value in this field is as of this action. |
PROJECTED_STOP_DT_TM | DATETIME | Y | The projected stop date and time for the order associated with this particular action. |
PROJECTED_STOP_TZ | DOUBLE | Y | The time zone associated with column Projected_Stop_Dt_Tm. |
SCH_STATE_CD | DOUBLE | N | The scheduling state of the order after this action was posted to the database. Example, Appointment, Noshow, Rescheduled etc. |
SIMPLIFIED_DISPLAY_LINE | VARCHAR(1000) | Y | A simplified display line of user selected order details. The information in this field will be hard coded and only written for pharmacy orders. |
SOURCE_DOT_ACTION_SEQ | DOUBLE | Y | The action sequence of the day of treatment order which caused the action on the protocol. This field will only be populated for protocol orders; for any other order, it will be 0. For order actions existing in the system before the introduction of this field, the value will be null. |
SOURCE_DOT_ORDER_ID | DOUBLE | Y | The identifier of the day of treatment order which caused the action on the protocol order. Actions taken on a day of treatment can result in adjusting its related protocol order which will result in the population of this field. This field will only be populated for protocol orders; for any other order, it will be 0. For order actions existing in the system before the introduction of this field, the value will be null. |
SOURCE_PROTOCOL_ACTION_SEQ | DOUBLE | Y | The action sequence of the related protocol order which was applied to this day of treatment. This field will be populated only when an action is taken on a day of treatment which is spawned from an action on the protocol. This field will only be populated for day of treatment orders; any other order it will be 0. For order actions existing in the system before the introduction of this field, the value will be null. |
START_RANGE_NBR | DOUBLE | Y | The amount of time applied to the start of the order to determine the start range. Will be NULL or greater than 0. If populated, start_range_unit_flag will be populated. Will never be fractional, if needed use the next granular unit. |
START_RANGE_UNIT_FLAG | DOUBLE | Y | The unit of time applied to the start of the order to determine the start range. If valued, start_range_nbr will also be valued. NULL: Order does not have start range, 1: days, 2: weeks, 3: months |
STOP_TYPE_CD | DOUBLE | N | Codified value based on codeset 4009 indicating what type of stop is associated with this order. Ex: Physician Stop, Hard Stop, Soft Stop. The value in this field is as of this action. |
SUPERVISING_PROVIDER_ID | DOUBLE | N | In addition to action personnel and order provider, the system could capture supervising provider per action. For example, when mid level providers (nurse practitioners) place orders in Easy Script, they're required to enter supervising provider. Cosign requests will be routed to supervising provider if order requires cosign and supervising provider is entered. |
SYNONYM_ID | DOUBLE | Y | The Id of the order synonym of the action. When null, the value is guaranteed to be equal to that on the orders table. |
TEMPLATE_ORDER_FLAG | DOUBLE | N | This flag identifies what type of template parent or a template instance this order is, or if this is a template order at all. The value in this field is as of this action. |
UNDO_ACTION_TYPE_CD | DOUBLE | N | Action type that you want to undo. |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
VALID_DOSE_DT_TM | DATETIME | Y | Used to capture a valid dose date and time of an order according to the frequency schedule for the action. |
Relationship Detail - ORDER_ACTION
Child Column in ORDER_ACTION(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | FREQUENCY_ID | FREQUENCY_SCHEDULE | FREQUENCY_ID |
ORDER_ID | ORDERS | ORDER_ID | |
SOURCE_DOT_ACTION_SEQ | ORDER_ACTION | ACTION_SEQUENCE | |
SOURCE_DOT_ORDER_ID | ORDER_ACTION | ORDER_ID | |
SYNONYM_ID | ORDER_CATALOG_SYNONYM | SYNONYM_ID | |
ACTION_PERSONNEL_ID | PRSNL | PERSON_ID | |
ORDER_PROVIDER_ID | PRSNL | PERSON_ID | |
SUPERVISING_PROVIDER_ID | PRSNL | PERSON_ID |
Parent Column in ORDER_ACTION (PK) | Child Table Name | Child Column Name | |
---|---|---|---|
Children: | ACTION_SEQUENCE | ORDER_ACTION | SOURCE_DOT_ACTION_SEQ |
ORDER_ID | ORDER_ACTION | SOURCE_DOT_ORDER_ID | |
ACTION_SEQUENCE | ORDER_EXT_CALL_TRACKING | ACTION_SEQUENCE | |
ORDER_ID | ORDER_EXT_CALL_TRACKING | ORDER_ID | |
ACTION_SEQUENCE | ORDER_INGREDIENT_HISTORY | ACTION_SEQUENCE | |
ORDER_ID | ORDER_INGREDIENT_HISTORY | ORDER_ID | |
ACTION_SEQUENCE | ORDER_INTERNAL_INFO | ACTION_SEQUENCE | |
ORDER_ID | ORDER_INTERNAL_INFO | ORDER_ID | |
ACTION_SEQUENCE | ORDER_REVIEW_DECISION | ACTION_SEQUENCE | |
ORDER_ID | ORDER_REVIEW_DECISION | ORDER_ID | |
ACTION_SEQUENCE | ORM_ORD_HIST_SNAPSHOT_COMP | ACTION_SEQUENCE | |
ORDER_ID | ORM_ORD_HIST_SNAPSHOT_COMP | ORDER_ID | |
ACTION_SEQUENCE | PHARMACY_NOTES | ACTION_SEQUENCE | |
ORDER_ID | PHARMACY_NOTES | ORDER_ID | |
ACTION_SEQUENCE | RX_INPT_CLAIM_HX | OP_ACTION_SEQUENCE | |
ORDER_ID | RX_INPT_CLAIM_HX | OP_ORDER_ID | |
ACTION_SEQUENCE | RX_PENDING_CHARGE | ACTION_SEQUENCE | |
ORDER_ID | RX_PENDING_CHARGE | ORDER_ID | |
ACTION_SEQUENCE | RX_PENDING_CHARGE_DELETED | ACTION_SEQUENCE | |
ORDER_ID | RX_PENDING_CHARGE_DELETED | ORDER_ID | |
ACTION_SEQUENCE | RX_PENDING_CREDIT | ACTION_SEQUENCE | |
ORDER_ID | RX_PENDING_CREDIT | ORDER_ID |
ORDER_ALIAS
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | This table holds alias numbers to an order within the systems. |
Definition: | This table holds aliases to an order within the system. |
Table Type: | ACTIVITY |
Column Detail - ORDER_ALIAS
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTIVE_IND | DOUBLE | Y | The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
ACTIVE_STATUS_CD | DOUBLE | N | Indicates the status of the row itself (not the data in the row) such as active, inactive, combined away, pending purge, etc. |
ACTIVE_STATUS_DT_TM | DATETIME | Y | The date and time that the active_status_cd was set. |
ACTIVE_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the active_status_cd to be set or change. |
ALIAS | VARCHAR(200) | Y | The alias is an identifier for an order. The alias may be unique or non-unique depending on the type of alias. |
ALIAS_POOL_CD | DOUBLE | N | The alias pool code identifies a unique set or list of order identifiers. |
ASSIGN_AUTHORITY_SYS_CD | DOUBLE | N | This field determines whether the ESI Server received an order alias that was configured for Hold. |
BEG_EFFECTIVE_DT_TM | DATETIME | N | The date and time for which this table row becomes effective. Normally, this will be the date and time the row is added, but could be a past or future date and time. |
BILL_ORD_NBR_IND | DOUBLE | Y | Identifies the alias that can be sent with outbound charges. |
CHECK_DIGIT | DOUBLE | Y | The check digit of the alias. |
CHECK_DIGIT_METHOD_CD | DOUBLE | N | the check digit method code identifies a specific routine, using the alias field, to calculate a check digit. |
CONTRIBUTOR_SYSTEM_CD | DOUBLE | N | Contributor system identifies the source feed of data from which a row was populated. This is mainly used to determine how to update a set of data that may have originated from more than one source feed. |
DATA_STATUS_CD | DOUBLE | N | Data status indicates a level of authenticity of the row data. Typically this will either be AUTHENTICATED or UNAUTHENTICATED. |
DATA_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the data_status_cd to be set or change. |
END_EFFECTIVE_DT_TM | DATETIME | N | The date/time after which the row is no longer valid as active current data. This may be valued with the date that the row became inactive. |
ORDER_ALIAS_ID | DOUBLE | N | The id for this order alias. The primary key of the table. |
ORDER_ALIAS_SUB_TYPE_CD | DOUBLE | N | The order alias subtype code further defines the type of alias. |
ORDER_ALIAS_TYPE_CD | DOUBLE | N | The order alias type code identifies a kind or type of alias. |
ORDER_ID | DOUBLE | N | The id of the order. |
PRIMARY_DISPLAY_IND | DOUBLE | Y | Indicator for Primary Display |
SYSTEM_TXT | VARCHAR(4000) | Y | The system text identifies the external system the order alias belongs to. |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
VERSION_TXT | VARCHAR(4000) | Y | The version text identifies the version of the alias in the external system. |
Relationship Detail - ORDER_ALIAS
Child Column in ORDER_ALIAS(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ORDER_ID | ORDERS | ORDER_ID |
ORDER_ATC_CODE
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Order Anatomical Therapeutic Chemical Code Details |
Definition: | Store the Anatomical Therapeutic Chemical (ATC) codes of an order. |
Table Type: | ACTIVITY |
Column Detail - ORDER_ATC_CODE
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTIVE_IND | DOUBLE | Y | The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
ATC_DESCRIPTION_TXT | VARCHAR(255) | Y | The description of the ATC code. |
ATC_VALUE_TXT | VARCHAR(255) | Y | The ATC code of an order. At a medication order level the structure should always be 7 characters (based on current codification). These values are stored in Multum's Clinical Server. Example ATC values: B01AA03, H01BA02, J01EE01. |
ORDER_ATC_CODE_ID | DOUBLE | N | Unique generated number that identifies a single row on the ORDER_ATC_CODE table. |
ORDER_ID | DOUBLE | Y | The ID of the associated order. |
UPDT_APPLCTX | DOUBLE | Y | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_CNT | DOUBLE | Y | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_ID | DOUBLE | Y | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
UPDT_TASK | DOUBLE | Y | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
Relationship Detail - ORDER_ATC_CODE
Child Column in ORDER_ATC_CODE(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ORDER_ID | ORDERS | ORDER_ID |
ORDER_COMMENT
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | ORDER COMMENT |
Definition: | Stores comments associated with an order |
Table Type: | ACTIVITY |
Column Detail - ORDER_COMMENT
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTION_SEQUENCE | DOUBLE | N | which action sequence the comment goes with |
COMMENT_DT_TM | DATETIME | Y | when the comment was written |
COMMENT_PRSNL_ID | DOUBLE | N | **Obsolete Column - Column was never used** who wrote the comment |
COMMENT_TYPE_CD | DOUBLE | N | type of comment |
DISPLAY_MASK | DOUBLE | Y | Display bit mask to tell who needs to show the comment |
LONG_TEXT_ID | DOUBLE | N | the long text id for the long text table |
ORDER_ID | DOUBLE | N | Order Id from the orders table |
UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. |
UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. |
UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
Relationship Detail - ORDER_COMMENT
Child Column in ORDER_COMMENT(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ORDER_ID | ORDERS | ORDER_ID |