Object Description
One row per outpatient fill for one of the medication classes targeted by the URSA-PQA module with multiple records for fills that qualify for more than one of the PQA medication classes; Diabetes medications, RAS Antagonists (RASA), Statins, Opioids, Benzodiazepines, and Anticholinergics.
Metadata
- Table Name: ursa.dm_ursa_pqa_meds_001
- Layer: DATA_MART
- Object Type: Single Stack
- Temporal Class: Event
- Case ID: Document Medication Class ID
- Event Date: Filled Date
- Primary Key: Document Medication Class ID
Published Fields
-
Data Model Keys
- Document Medication Class ID
- 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)
- Measure ID
- Document ID -- The internal database identifier (used, e.g., for joins and primary keys) for the document. (See also [URSA-CORE] Document)
- Claim ID -- The internal database identifier (used, e.g., for joins and primary keys) for the claim. (See also [URSA-CORE] Claim)
- Filling Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the filling provider.
- Prescribing Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the prescribing provider. (See also [URSA-CORE] Prescribing Provider)
- Fill Payor ID
- Fill Plan ID
- Source ID -- The identifier for the original source data system from which the current record originated.
-
Date Fields
- Filled Date -- The date a prescription or medication order was filled, with medications dispensed.
- Filled Date Year
- Prescribed Date -- The date the prescription or medication order was signed.
- Claim Received Date -- The date the claim was originally received for processing by the payor.
- Claim Paid Date -- The date the claim was paid by the payor.
- Payor Incurred Date -- The date the payor considers the services associated with the record to be incurred for accounting purposes.
-
Provider Fields
- Prescribing Provider NPI -- The 10-digit National Provider Identifier for the prescribing provider. (See also [URSA-CORE] Prescribing Provider)
- Prescribing Provider Description -- The natural language description of the prescribing provider. (See also [URSA-CORE] Prescribing Provider)
- Filling Provider NPI -- The 10-digit National Provider Identifier for the filling provider. (See also [URSA-CORE] Filling Provider)
- Filling Provider Description -- The natural language description of the filling provider. (See also [URSA-CORE] Filling Provider)
- Filling Provider Primary NUCC Provider Taxonomy Code -- The primary NUCC Provider Taxonomy code for the filling provider. (See also [URSA-CORE] Filling Provider, [URSA-CORE] Primary NUCC Provider Taxonomy Code)
- Filling Provider Primary NUCC Provider Taxonomy Description -- The primary NUCC Provider Taxonomy description for the filling provider. (See also [URSA-CORE] Filling Provider, [URSA-CORE] Primary NUCC Provider Taxonomy Description)
- Is Filling Provider Mail Order Pharmacy -- Indicates the filling provider is a mail-order pharmacy. (See also [URSA-CORE] Filling Provider)
-
Insurance Fields
- Is Medicare Part B -- Indicates that the coverage for this claim or bill is provided by Medicare Part B. Note that some institutional claims and pharmacy claims may be designated Part B.
- Is Medicare Part D -- Indicates that the coverage for this claim or bill is provided by Medicare Part D.
-
Medication Fields
- NDC Code -- The standard 11-digit National Drug Code; e.g., 00045012400 = Tylenol 500 mg.
- Label Description -- Supplies the name given to the product by the manufacturer.
- Active Ingredients Description -- A natural language description of the medication's biologically active ingredient(s). For medications with multiple active ingredients, the active ingredients should be listed in alphabetical order.
- Days Supply -- The number of calendar days, including the date the medication was dispensed, the dispensed medication will last at the patient's intended dosage as defined in their prescription.
- Medication Group
- AHFS Therapeutic Class Code 6-Digit -- The standard 6-digit AHFS Pharmacologic-Therapeutic Class Code, representing the first 3 tiers of the AHFS Pharmacologic-Therapeutic Classification system. The code is expressed as 6 numbers, without special characters delimiting the tiers, with leading and trailing zeros as needed. (See also [URSA-CORE] AHFS Pharmacologic-Therapeutic Classification System)
- AHFS Therapeutic Class Tier 1 Description -- The natural language description of the first-tier category within the AHFS Therapeutic Classification System that the medication is assigned to. (See also [URSA-CORE] AHFS Pharmacologic-Therapeutic Classification System)
- AHFS Therapeutic Class Tier 2 Description -- The natural language description of the second-tier category within the AHFS Therapeutic Classification System that the medication is assigned to. (See also [URSA-CORE] AHFS Pharmacologic-Therapeutic Classification System)
- AHFS Therapeutic Class Tier 3 Description -- The natural language description of the third-tier category within the AHFS Therapeutic Classification System that the medication is assigned to. (See also [URSA-CORE] AHFS Pharmacologic-Therapeutic Classification System)
- Red Book Generic Cross Reference Code -- A unique 6-digit code assigned to all products that contain the same set of active ingredients. By extracting all records containing this code, users can identify comparable products regardless of trade or generic name. (See also [URSA-CORE] Red Book Generic Formulation Code)
- Red Book Generic Formulation Code -- A unique 6-digit code identifying drugs with common active ingredients, master dosage form, strength, and route of administration. The GFC is not manufacturer or package size specific, and can therefore be used in preparation of drug utilization reports and analysis of generic alternatives for substitution and formulary development. The GFC may also be used within pharmacy and claims administration systems as an efficient means of linking NDC numbers to clinical screening functions. (See also [URSA-CORE] Red Book Generic Cross Reference Code)
- Medi-Span GPI Code 14-Digit -- The 14-digit Medi-Span Generic Product Identifier (GPI) for the medication. The GPI is a 7-level hierarchical classification, with each level represented by two digits in the GPI. The full 14-digit GPI describes a medication's class, ingredients, dosage form, and strength. GPI values should include leading and trailing zeros and should not include hyphens or other special characters.
- Is Specialty Drug According to Plan -- Indicates the medication is considered by the plan to be a specialty drug.
- Is Generic According to Plan -- Indicates the medication is considered by the plan to be a generic drug.
- Is Brand According to Plan -- Indicates the medication is considered by the plan to be a brand name drug.
- Is Generic According to Reference -- Indicates that the medication is considered to be a generic in the relevant reference dataset.
- Is Brand According to Reference -- Indicates that the medication is considered to be a brand medication in the relevant reference dataset.
-
Billing and Claims Fields
- Is Claim Processed Status Open -- Indicates that the claim has been received but not yet paid or denied.
- Is Claim Processed Status Paid -- Indicates that the claim has completed processing without denial, with any outstanding balance paid.
- Is Claim Processed Status Denied -- Indicates the claim has been denied.
-
Financial Fields
- Claim Plan Paid Amount -- The amount paid by an insurance plan for all services on a claim.
- Claim Patient Paid Amount -- The amount paid by the patient for all services on a claim.
-
Metadata Fields
- 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)