[NO/URSA-CORE] Medication List Entries
- 28 Jun 2025
- 4 Minutes to read
- Print
- DarkLight
[NO/URSA-CORE] Medication List Entries
- Updated on 28 Jun 2025
- 4 Minutes to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback!
Object Description
One record per medication list entry.
Metadata
- Table Name: ursa.no_ursa_core_meds_003
- Layer: NATURAL_OBJECT
- Object Type: Single Stack
- Temporal Class: Interval
- Case ID: Medication List Entry ID
- Interval Start Date: Active Period Start Date
- Interval End Date: Active Period End Date
- Primary Key: Medication List Entry ID
Published Fields
Data Model Keys
- 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)
- 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)
- 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)
- 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)
- Document ID
- Source ID -- The identifier for the original source data system from which the current record originated.
Source Local Keys
- Source Local Medication List Entry ID -- The internal database identifier for the medication list entry in the source data system this record originated from. (See also [URSA-CORE] Medication List Entry)
- 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 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)
Operations Support Fields
- Is Immunization Record
- 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)
- Is Active Medication -- Indicates the medication is in active use by the patient as of the current source data effective date.
Date Fields
- Active Period Start Date
- Active Period Start Datetime
- Active Period End Date
- Active Period End Datetime
- Documented Date
- Ordered Date -- The calendar date the order was entered into the EMR or otherwise created.
- Administered Date
- Administered Datetime
Provider Fields
- Ordering Provider Description
- Ordering Provider NPI
Medication Fields
- Medication Description
- NDC Code 11-Digit
- SNOMED CT Code
- RxNorm Code
- CDC CVX Code
- 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).
- Series Dose Number
- Is Adverse Reaction
- Adverse Reaction Description
- Adverse Reaction Operational ID
- 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
- 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
- medication_order_id → ursa.no_ursa_core_meds_002.medication_order_id
- ordering_prov_id → ursa.no_ursa_core_prov_001.prov_id
Dedicated Precursors
- [NO/URSA-CORE] Medication List Entries, Precursor 1 (All Source Records): One record per medication list entry
Was this article helpful?