[DM/URSA-CORE] Data Mart for Clinician Office Visits
- 28 Jun 2025
- 4 Minutes to read
- Print
- DarkLight
[DM/URSA-CORE] Data Mart for Clinician Office Visits
- 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 clinician office visit.
Metadata
- Table Name: ursa.dm_ursa_core_003
- Layer: DATA_MART
- Object Type: Single Stack
- Temporal Class: Event
- Case ID: Encounter ID
- Event Date: Encounter Date
- Primary Key: Encounter ID
Published Fields
Data Model Keys
- Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the encounter. (See also [URSA-CORE] Encounter)
- 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)
- Encounter Primary Payor ID -- Data model key for the primary payor documented in the billing for an encounter.
- Encounter Primary Plan ID -- Data model key for the primary plan documented in the billing for an encounter.
- Facility Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the facility provider. (See also [URSA-CORE] Facility Provider)
- Service Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the service provider. (See also [URSA-CORE] Service Provider)
- Attending Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the attending provider. (See also [URSA-CORE] Attending Provider)
- Provider Group Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the provider group. (See also [URSA-CORE] Provider Group)
Date Fields
- Encounter Date
Encounter Fields
- Ursa Clinician Office Visit Type Tier 1 Category
- Ursa Clinician Office Visit Type Tier 2 Category
- Is Primary Care Clinician Office Visit
- Is Specialist Clinician Office Visit
- Is Encounter with Qualifying Preventive Primary Care Service
- Is Preventive Care Visit from Non-Primary Care Specialist
- Is Annual Wellness Visit Encounter
- Is Urgent Care Visit -- Indicates the encounter had one or more claim document with a HCPCS, Revenue Center Code, or Place of Service Code specific to Urgent Care Facility claim filing.
Provider Fields
- Is Any Provider Qualifying Primary Care Provider
- Service Provider NPI
- Service Provider Description
- Service Provider Primary NUCC Provider Taxonomy Description
- Provider Group Provider NPI
- Provider Group Description
- Provider Group Primary NUCC Provider Taxonomy Description
- Attending Provider Provider NPI
- Attending Provider Description
- Facility Provider Provider NPI
- Facility Provider Description
- Ursa Physician Specialty Type Description
Diagnosis Fields
- Principal Discharge Diagnosis ICD-10-CM Code
- Principal Discharge Diagnosis ICD-10-CM Description
- Principal Discharge Diagnosis AHRQ CCS Single-Level Diagnosis Category Code
- Principal Discharge Diagnosis AHRQ CCS Single-Level Diagnosis Category Description
- Principal Discharge Diagnosis AHRQ CCS Multi-Level Diagnosis Category Tier 1 Code
- Principal Discharge Diagnosis AHRQ CCS Multi-Level Diagnosis Category Tier 1 Description
- Principal Discharge Diagnosis AHRQ CCS Multi-Level Diagnosis Category Tier 2 Code
- Principal Discharge Diagnosis AHRQ CCS Multi-Level Diagnosis Category Tier 2 Description
- Principal Discharge Diagnosis WHO ICD-10 Chapter Description
- Principal Discharge Diagnosis WHO ICD-10 Block Description
Clinical Services Fields
- Qualifying Document HCPCS Code
- Qualifying Document HCPCS Short Description
- Qualifying Document HCPCS AHRQ CCS Single-Level Procedure Category Code
- Qualifying Document HCPCS AHRQ CCS Single-Level Procedure Category Description
- Qualifying Preventive Primary Care HCPCS Code
- Qualifying Preventive Primary Care HCPCS Code Description
Billing and Claims Fields
- Qualifying Document CMS Revenue Center Code
- Qualifying Document CMS Revenue Center Description
- CMS Place of Service Code -- The standard CMS 2-digit Place of Service code; e.g., 01 = Pharmacy, 02 = Telehealth, etc.
- CMS Place of Service Description -- The natural language description of a standard CMS Place of Service code (See also [URSA-CORE] CMS Place of Service Code)
Financial Fields
- Encounter Total Plan Paid Amount from All Plans Category
- Primary Plan Allowed Amount -- The maximum amount that the payor agrees to pay the provider for a service or product, typically governed by a contract. The Allowed Amount for a claim or billing record is calculated by adding the Contractual Adjustment Amount (which is typically negative) to the Charge Amount. Adding the total Non-Contractual Adjustment Amount to the Allowed Amount yields the Total Due Amount. On billing records, which may identify up to three plans responsible for payment, the Primary Plan Allowed Amount, Secondary Plan Allowed Amount, and Tertiary Plan Allowed Amount fields identify the amounts paid by the primary, secondary, and tertiary plans listed on the bill, respectively. (See also [URSA-CORE] Charge Amount, [URSA-CORE] Contractual Adjustment Amount, [URSA-CORE] Non-Contractual Adjustment Amount, [URSA-CORE] Total Due Amount)
- Primary Plan Paid Amount -- The amount actually paid by the health plan to the provider for a service or product. Subtracting the plan paid amount from the total due amount typically yields the patient responsibility amount. On billing records, which may identify up to three plans responsible for payment, the Primary Plan Paid Amount, Secondary Plan Paid Amount, and Tertiary Plan Paid Amount fields identify the amounts paid by the primary, secondary, and tertiary plans listed on the bill, respectively; the total paid by any and all plans on a bill is identified by the Any Plan Paid Amount field.
- Total Plan Paid Amount from All Plans
- Patient Paid Amount -- The amount paid by the patient to the provider for health care services or products.
Metadata Fields
- Qualifying Document EMR Encounter Type Description
Foreign Keys
- pat_id → ursa.no_ursa_core_pat_001.pat_id
- enc_primary_payor_id → ursa.no_ursa_core_struct_004.payor_id
- enc_primary_plan_id → ursa.no_ursa_core_struct_005.plan_id
- facility_prov_id → ursa.no_ursa_core_prov_001.prov_id
- service_prov_id → ursa.no_ursa_core_prov_001.prov_id
- attending_prov_id → ursa.no_ursa_core_prov_001.prov_id
- prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id
- enc_id → ursa.so_ursa_core_enc_002.enc_id
Was this article helpful?