[NO/URSA-CORE] Medication Orders

Object Description

One record per medication order.

Metadata

• Table Name: ursa.no_ursa_core_meds_002
• Layer: NATURAL_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Medication Order ID
• Event Date: Ordered Date
• Primary Key: Medication Order ID

Published Fields

• Data Model Keys

  • Medication Order ID -- The internal database identifier (used, e.g., for joins and primary keys) for the medication order. (See also [URSA-CORE] Medication Order)
  • Patient ID -- The internal database identifier (used, e.g., for joins and primary keys) for the patient. This value is typically mastered, i.e., all records for the same patient, regardless of the source data system from which that record originated, should have the same Patient ID value. (Note that while the mastered Patient ID value might resemble a local identifier used in one of the upstream data sources, this does not indicate any special priority of that source system in determining the characteristics of the patient.) (See also [URSA-CORE] Patient)
  • Medication ID -- The internal database identifier (used, e.g., for joins and primary keys) for the medication. (See also [URSA-CORE] Medication)
  • Ordering Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the ordering provider. (See also [URSA-CORE] Ordering Provider)
  • Receiving Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the receiving provider. (See also [URSA-CORE] Receiving Provider)
  • Originating EMR Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the EMR encounter that is the originating encounter of the given document. (See also [URSA-CORE] EMR Encounter, [URSA-CORE] Originating EMR Encounter)
  • Medication List Entry ID -- The internal database identifier (used, e.g., for joins and primary keys) for the medication list entry. (See also [URSA-CORE] Medication List Entry)
  • Replaced Medication Order ID -- The internal database identifier (used, e.g., for joins and primary keys) for the original medication order that the current order replaced. (See also [URSA-CORE] Replaced Medication Order)
  • Renewed Medication Order ID -- The internal database identifier (used, e.g., for joins and primary keys) for the original medication order that the current order has renewed. (See also [URSA-CORE] Renewed Medication Order)
  • Document ID
  • Source ID -- The identifier for the original source data system from which the current record originated.

• Source Local Keys

  • Source Local Medication Order ID -- The internal database identifier for the medication order in the source data system this record originated from. (See also [URSA-CORE] Medication Order)
  • Source Local Patient ID -- The internal database identifier for the patient in the source data system this record originated from. (See also [URSA-CORE] Patient)
  • Source Local Medication ID -- The internal database identifier for the medication in the source data system this record originated from. (See also [URSA-CORE] Medication)
  • Source Local Ordering Provider ID -- The internal database identifier for the ordering provider in the source data system this record originated from. (See also [URSA-CORE] Ordering Provider)
  • Source Local Receiving Provider ID -- The internal database identifier for the receiving provider in the source data system this record originated from. (See also [URSA-CORE] Receiving Provider)

• Operations Support Fields

  • Is Order for Provider Administration -- Indicates that the medication order represents a request to administer the medication to the patient, not merely to dispense the medication. (See also [URSA-CORE] Medication Order)
  • Is Order for Pharmacy Fill -- Indicates that the medication order represents a traditional prescription to be filled by the patient in a pharmacy, rather than an order for a provider to administer the medication to the patient directly. (See also [URSA-CORE] Medication Order)
  • Prescription Number -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the medication order. (See also [URSA-CORE] Medication Order)

• Date Fields

  • Ordered Date -- The calendar date the order was entered into the EMR or otherwise created.
  • Ordered Datetime -- The date and time the order was entered into the EMR or otherwise created.
  • Order Expiration Date -- The calendar date on which the order is considered to have expired.
  • Medication Order First Closing Datetime
  • Medication Order Final Closing Datetime

• Provider Fields

  • Ordering Provider Description
  • Ordering Provider NPI
  • Receiving Provider Description
  • Receiving Provider NPI
  • Filling Setting Description -- The natural language description of the filling setting. (See also [URSA-CORE] Filling Setting)
  • Is Filling Setting Inpatient -- Indicates that the order is to be filled in an inpatient setting. (See also [URSA-CORE] Filling Setting)
  • Is Filling Setting Outpatient -- Indicates that the order is to be filled in an outpatient setting, including emergency department and hospital observation settings; does not include community pharmacies or other filling settings where the intent is for the patient to consume or be administered the medications in their residence. (See also [URSA-CORE] Filling Setting)
  • Is Filling Setting Community -- Indicates that the order is to be filled in a community setting, including pharmacies or other filling settings where the intent is for the patient to consume or be administered the medications in their residence. (See also [URSA-CORE] Filling Setting)

• Medication Fields

  • Medication Description
  • Dosage Description -- The natural language description of the medication order dosage. Also called the Sig. (See also [URSA-CORE] Dosage)
  • Dose Quantity Description -- The natural language description of the dose quantity. (See also [URSA-CORE] Dose Quantity)
  • Dose Quantity Numeric -- The numeric component of a dose quantity, expressed as a number, including non-integer values, if applicable.
  • Dose Quantity Unit Description -- The natural language description of the unit component of dose quantity. (See also [URSA-CORE] Dose Quantity)
  • Dose Frequency Description -- The natural language description of dose frequency. (See also [URSA-CORE] Dose Frequency)
  • Doses per Day -- The dose frequency expressed as a number of doses per day. (See also [URSA-CORE] Dose Frequency)
  • Is Dose Frequency PRN -- Indicates a dose frequency of PRN (guidance to take the medication as needed).
  • Quantity per Fill -- The quantity of medication (e.g., number of tablets) to be dispensed per fill of this medication order.
  • Days Supply per Fill -- The days supply of medication to be dispensed per fill of this medication order.
  • Count Refills Allowed -- The number of refills (in addition to the initial fill) allowed on this medication order. (E.g., a value of 2 would allow a total of 3 fills from the order.)
  • Is Dispense as Written -- Indicates that the medication order should be filled as written, without any substitutions allowed.
  • NDC Code 11-Digit
  • SNOMED CT Code
  • RxNorm Code
  • Strength Description
  • Strength Numeric
  • Strength Unit Description
  • Active Ingredients Description
  • Primary Agent Description
  • AHFS Therapeutic Class Code 6-Digit
  • AHFS Therapeutic Class Code 8-Digit
  • AHFS Therapeutic Class Tier 1 Description
  • AHFS Therapeutic Class Tier 2 Description
  • AHFS Therapeutic Class Tier 3 Description
  • Red Book Generic Cross Reference Code
  • Red Book Generic Formulation Code
  • Medi-Span GPI Code 14-Digit
  • Form Description
  • FDA Dosage Form Code
  • Route of Administration Description
  • Is Generic According to Provider
  • Is Specialty Drug According to Provider
  • Is Brand According to Provider
  • Is Generic According to Reference
  • Is Brand According to Reference
  • Is Single Source According to Reference
  • Is OTC
  • Is Compound Drug

• Diagnosis Fields

  • Primary Indication Description
  • Primary Indication ICD-10-CM Code -- The standard ICD-10-CM code for the order's primary indication. (See also [URSA-CORE] Primary Indication)
  • Primary Indication SNOMED CT Code -- The standard SNOMED CT code for the order's primary indication. (See also [URSA-CORE] Primary Indication)

• Metadata Fields

  • Is Replacement Medication Order -- Indicates that the current medication order is meant to replace a prior order. (See also [URSA-CORE] Replaced Medication Order)
  • Is Renewal Medication Order -- Indicates that the current medication order renews a prior order. (See also [URSA-CORE] Renewed Medication Order)
  • Order Status Description -- The natural language description of the order status. (See also [URSA-CORE] Order Status)
  • Order Status Operational ID -- The unique, user-facing (“real-world”) identifier used by operational systems or staff to identify the order status. (See also [URSA-CORE] Order Status)
  • Is Order Status Draft -- Indicates that the order is in draft form, and not yet issued. (See also [URSA-CORE] Order Status)
  • Is Order Status Issued Only -- Indicates that the order has been finalized and sent to the receiving provider but not yet accepted; nor suspended or cancelled. (See also [URSA-CORE] Order Status)
  • Is Order Status Active -- Indicates that the order has been issued and accepted by the receiving provider, but not completed, cancelled, or suspended. (See also [URSA-CORE] Order Status)
  • Is Order Status Suspended -- Indicates that activities to complete the order have been temporarily stopped, either by request of the ordering provider or some other authority. (See also [URSA-CORE] Order Status)
  • Is Order Status Cancelled -- Indicates that activities to complete the order have been permanently stopped, either by request of the ordering provider or some other authority. In most cases, an order that has been replaced should be considered cancelled. (See also [URSA-CORE] Order Status)
  • Is Order Status Completed -- Indicates that the order has been completed by the receiving provider. (See also [URSA-CORE] Order Status)
  • Is Order Ever Order Status Active -- Indicates that the order reached an order status of active at any point, whether or not it was subsequently accepted, completed, cancelled, or suspended. (See also [URSA-CORE] Is Order Status Active)
  • Other EMR Comments -- Any other annotations or comments associated with the current record entered into the EMR.
  • Record Last Updated Datetime -- The date and time the current record was last updated in the original data source.
  • Source Data Effective Datetime -- The "as of" date and time of the original source data system at the moment the current record was extracted. For example, if a snapshot of the data in a production system is taken at 12:05 AM on the first of each month and used to generate a package of flat files that are eventually loaded into the Ursa Studio client database later that month, the Source Data Effective Datetime of all records in that month's package will be 12:05 AM on the first. Not to be confused with Record Last Updated Datetime. (See also [URSA-CORE] Record Last Updated Datetime)

Foreign Keys

• pat_id → ursa.no_ursa_core_pat_001.pat_id
• medication_id → ursa.no_ursa_core_meds_001.medication_id
• prescribing_prov_id → ursa.no_ursa_core_prov_001.prov_id
• ordering_prov_id → ursa.no_ursa_core_prov_001.prov_id
• receiving_prov_id → ursa.no_ursa_core_prov_001.prov_id
• originating_emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id
• medication_list_entry_id → ursa.no_ursa_core_meds_003.medication_list_entry_id

Dedicated Precursors

• [NO/URSA-CORE] Medication Orders, Precursor 1 (All Source Records): One record per medication order