Contents x
    [SO/URSA-CORE] Home Health Care Visit Document-Encounter Pairs
    • 28 Jun 2025
    • 12 Minutes to read
    • Print
    • Dark
      Light
    Contents

    [SO/URSA-CORE] Home Health Care Visit Document-Encounter Pairs

    • Updated on 28 Jun 2025
    • 12 Minutes to read
    • Print
    • Dark
      Light
    Article summary

    Object Description

    Collects information about home health care visits; contains documents uniquely related to one or more home health care visits. (Note that when a single institutional claim or bill header covers multiple visits, the header and associated diagnosis documents appear multiple times, once each for each encounter they are associated with.)

    Metadata

    • Table Name: ursa.so_ursa_core_enc_110
    • Layer: SYNTHETIC_OBJECT
    • Object Type: Integrator
    • Temporal Class: Event
    • Case ID: Document ID, Encounter ID
    • Event Date: Encounter Date
    • Primary Key: Document ID, Encounter ID

    Published Fields

    • Data Model Keys

      • Document ID -- The internal database identifier (used, e.g., for joins and primary keys) for the document. (See also [URSA-CORE] Document)
      • 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)
      • Parent Document ID -- The document ID for the document one level above the current document in the object hierarchy, (See also [URSA-CORE] Document ID)
      • Grandparent Document ID -- The document ID for the document two levels above the current document in the object hierarchy, (See also [URSA-CORE] Document ID)
      • Claim ID -- The internal database identifier (used, e.g., for joins and primary keys) for the claim. (See also [URSA-CORE] Claim)
      • Institutional Claim ID
      • Institutional Claim Service Line Item ID -- The identifier for a service line item on an institutional or professional claim.
      • Professional Claim ID
      • Professional Claim Service Line Item ID
      • Pharmacy Claim ID
      • Bill ID -- The identifier for a professional or institutional bill header record; Bill ID values are consistent over the lifetime of a bill, including when a bill is adjusted. On a claim record, this field refers to the bill sent to the plan that originated the claim record.
      • Institutional Bill ID
      • Institutional Bill Service Line Item ID -- The identifier for a service line item on an institutional or professional bill.
      • Professional Bill ID
      • Professional Bill Service Line Item ID
      • EMR Encounter ID -- The internal database identifier (used, e.g., for joins and primary keys) for the EMR encounter. (See also [URSA-CORE] EMR Encounter)
      • EMR Encounter Service Line Item ID -- The identifier for the instance of a performed service during an EMR Encounter.
      • EMR Encounter Diagnosis ID -- The identifier for the instance of documented diagnosis associated with an EMR Encounter.
      • Patient Observation ID -- The internal database identifier (used, e.g., for joins and primary keys) for the Patient Observation (See also [URSA-CORE] Patient Observation)
      • Order ID
      • Medication Dispense ID
      • Service Line Number -- The integer-valued ordinal representing the position of a service line item in a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record.
      • Diagnosis Line Number -- The integer-valued ordinal representing the position of a diagnosis on a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record. Typically, the diagnosis in the first position is considered the principal diagnosis, though this is not an absolute rule, and the Is Principal Diagnosis field should be used to identify the principal diagnosis.
      • Procedure Line Number -- The integer-valued ordinal representing the position of a procedure on a claim, bill, encounter, or other master record. May not necessarily match the analogous value in the source data for the same record.
      • Billing Provider ID -- The internal database identifier (used, e.g., for joins and primary keys) for the billing provider. (See also [URSA-CORE] Billing 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)
      • 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)
      • 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)
      • 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)
      • Dispensing Provider ID
      • Plan ID -- The identifier for a particular health insurance plan product offered by a payor.
      • Payor ID -- The identifier for the health insurance organization associated with the current record.
      • Source ID -- The identifier for the original source data system from which the current record originated.

    • Date Fields

      • Encounter Date
      • Document Effective Date -- The most appropriate single date that events associated with the document occurred. For documents spanning multiple calendar days, the earliest date is typically used; Document Effective Start Date and Document Effective End Date can be used for a more precise range of dates, if necessary.
      • Document Effective Start Date -- The date that the events associated with the document began.
      • Document Effective End Date -- The last date on which events associated with the document occurred or continued until.
      • Parent Document Effective Start Date -- The date that the events associated with the current document's parent document began.
      • Parent Document Effective End Date -- The last date on which events associated with the current document's parent document occurred or continued until.

    • Encounter Fields

      • EMR Encounter Type Operational ID
      • EMR Encounter Type Description

    • Clinical Services Fields

      • ICD-9-CM Procedure Code
      • ICD-9-CM Procedure Description
      • ICD-10-PCS Code
      • ICD-10-PCS Description
      • HCPCS Code -- The Healthcare Common Procedure Coding System (HCPCS) code associated with a service. Includes both HCPCS Level I codes (commonly called CPT codes) and Level II codes (which includes products, supplies, and services not included in CPT). Level II codes consist of a letter followed by four numeric digits. Current Dental Terminology codes are included in the Level II codes as HCDT. (See also [URSA-CORE] HCPCS Description)
      • HCPCS Description -- The natural language description of a HCPCS code. (See also [URSA-CORE] HCPCS Code)
      • HCPCS Modifier 1 Code -- The 2-character code modifying a HCPCS code.
      • HCPCS Modifier 1 Description -- The natural language description of a HCPCS code modifier. (See also [URSA-CORE] HCPCS Modifier Code)
      • HCPCS Modifier 2 Code
      • HCPCS Modifier 2 Description
      • HCPCS Modifier 3 Code
      • HCPCS Modifier 3 Description
      • HCPCS Modifier 4 Code
      • HCPCS Modifier 4 Description
      • HCPCS Modifier 5 Code
      • HCPCS Modifier 5 Description
      • Service Operational ID
      • Service Description -- The natural language description of the service. (See also [URSA-CORE] Service)
      • Service LOINC Code
      • Service SNOMED CT Code
      • CMS Revenue Center Code -- The standard CMS 4-digit Revenue Center code; e.g., 0001 = Total charge, etc. CMS Revenue Center codes should include leading zeros.
      • CMS Revenue Center Description -- The natural language description of a CMS Revenue Center code (See also [URSA-CORE] CMS Revenue Center Code)
      • 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)
      • CMS Admission Type Code -- The standard CMS 1-digit Admission Type code; 1 = Emergency, 2 = Urgent, etc.
      • CMS Admission Type Description -- The natural language description of a CMS Admission Type code (See also [URSA-CORE] CMS Admission Type Code)
      • CMS Admit Source Code -- The standard 1-character CMS Admit Source code; e.g., 1 = Physician Referral, 2 = Clinic Referral, etc.
      • CMS Admit Source Description -- The natural language description of a standard CMS Admit Source code. (See also [URSA-CORE] CMS Admit Source Code)
      • CMS Patient Discharge Status Code -- The standard 2-digit CMS Patient Discharge Status code; 01 = Discharged to Home or Self Care, etc. Patient Discharge Status codes should include leading zeros.
      • CMS Patient Discharge Status Description -- The natural language description of a standard CMS Patient Discharge Status code. (See also [URSA-CORE] CMS Patient Discharge Status Code)

    • Medication Fields

      • NDC Code -- The standard 11-digit National Drug Code; e.g., 00045012400 = Tylenol 500 mg.
      • RxNorm Code -- The standard RxNorm code for medications; e.g., 315253 = acetaminophen 160 MG.
      • Medication SNOMED CT Code
      • CDC CVX Code -- The standard 2- or 3-digit CVX code developed and maintained by the CDC, identifying administered vaccine substances; e.g., 05 = Measles; 62 = HPV, quadrivalent; 118 = HPV, bivalent. CVX codes below 10 should include a leading zero.
      • 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.
      • 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 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)
      • 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.
      • 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)

    • Diagnosis Fields

      • MS-DRG Code -- The standard 3-digit Medicare Severity Diagnosis Related Group code; MS-DRG codes should include leading zeros.
      • MS-DRG Description -- The natural language description of a standard 3-digit Medicare Severity Diagnosis Related Group code.
      • APR-DRG Code -- The standard 3-digit All Patient Refined Diagnosis Related Group code; APR-DRG codes should include leading zeros, and do not include the Severity of Illness or Risk of Mortality modifiers.
      • APR-DRG Description -- The natural language description of a standard 3-digit All Patient Refined Diagnosis Related Group code. (See also [URSA-CORE] APR-DRG Code)
      • APR-DRG Severity of Illness Code -- The standard 1-digit Severity of Illness modifier for an All Patient Refined Diagnosis Related Group code; sometimes abbreviated as SOI.
      • APR-DRG Risk of Mortality Code -- The standard 1-digit Risk of Mortality modifier for an All Patient Refined Diagnosis Related Group code; sometimes abbreviated as ROM.
      • ICD-9-CM Diagnosis Code
      • ICD-9-CM Diagnosis Description
      • ICD-10-CM Code
      • ICD-10-CM Description
      • Diagnosis SNOMED CT Code
      • Diagnosis SNOMED CT Description
      • Is Admitting Diagnosis -- Indicates that a diagnosis was the admitting diagnosis for an encounter.
      • Is Principal Diagnosis -- Indicates that a diagnosis was documented as the principal diagnosis for the claim, bill, encounter, etc.

    • Billing and Claims Fields

      • CMS Type of Bill Code -- The standard CMS 3-digit Type of Bill (TOB) Code; 111 = Hospital Inpatient Admit Through Discharge, etc.
      • CMS Type of Bill Description -- The natural language description of a standard CMS Type of Bill (TOB) code. (See also [URSA-CORE] CMS Type of Bill Code)

    • Financial Fields

      • Document Allowed Amount
      • Document Plan Paid Amount
      • Document Patient Responsibility Amount
      • Document Patient Paid Amount

    • Metadata Fields

      • Is Qualifying Document
      • Document Type Description
      • Is Document Type Institutional Claim Header
      • Is Document Type Institutional Claim Service Line Item
      • Is Document Type Institutional Claim Diagnosis
      • Is Document Type Institutional Claim Procedure
      • Is Document Type Professional Claim Header
      • Is Document Type Professional Claim Service Line Item
      • Is Document Type Professional Claim Diagnosis
      • Is Document Type Pharmacy Claim
      • Is Document Type Institutional Bill Header
      • Is Document Type Institutional Bill Service Line Item
      • Is Document Type Institutional Bill Diagnosis
      • Is Document Type Institutional Bill Procedure
      • Is Document Type Professional Bill Header
      • Is Document Type Professional Bill Service Line Item
      • Is Document Type Professional Bill Diagnosis
      • Is Document Type EMR Encounter
      • Is Document Type EMR Encounter Service Line Item
      • Is Document Type EMR Encounter Diagnosis
      • Is Document Type Patient Observation
      • Is Document Type Medication Dispense
      • Document Count of Encounters
      • Encounter Rank Within Document
      • 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)

    • Patient Observation Fields

      • Result Type Operational ID
      • Result Type Description
      • Result Type LOINC Code
      • Result Type SNOMED CT Code
      • Result Operational ID
      • Result Description
      • Result Numeric

    Foreign Keys

    • document_id → ursa.so_ursa_core_pat_001.document_id
    • enc_id → ursa.so_ursa_core_enc_002.enc_id
    • enc_prov_group_prov_id → ursa.no_ursa_core_prov_001.prov_id
    • parent_document_id → ursa.so_ursa_core_pat_001.document_id
    • grandparent_document_id → ursa.so_ursa_core_pat_001.document_id
    • pat_id → ursa.no_ursa_core_pat_001.pat_id
    • i_claim_id → ursa.no_ursa_core_fin_001.claim_id
    • i_claim_service_line_item_id → ursa.no_ursa_core_fin_002.claim_service_line_item_id
    • p_claim_id → ursa.no_ursa_core_fin_003.claim_id
    • p_claim_service_line_item_id → ursa.no_ursa_core_fin_003.claim_service_line_item_id
    • rx_claim_id → ursa.no_ursa_core_fin_004.claim_id
    • i_bill_id → ursa.no_ursa_core_fin_011.bill_id
    • i_bill_service_line_item_id → ursa.no_ursa_core_fin_012.bill_service_line_item_id
    • p_bill_id → ursa.no_ursa_core_fin_013.bill_id
    • p_bill_service_line_item_id → ursa.no_ursa_core_fin_013.bill_service_line_item_id
    • emr_enc_id → ursa.no_ursa_core_enc_001.emr_enc_id
    • emr_enc_service_id → ursa.no_ursa_core_enc_002.emr_enc_service_line_item_id
    • billing_prov_id → ursa.no_ursa_core_prov_001.prov_id
    • service_prov_id → ursa.no_ursa_core_prov_001.prov_id
    • facility_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
    • plan_id → ursa.no_ursa_core_struct_005.plan_id
    • payor_id → ursa.no_ursa_core_struct_004.payor_id

    Dedicated Precursors

    • [SO/URSA-CORE] Home Health Care Visit Document-Encounter Pairs, Precursor 1 (Qualifying Documents): One record per professional claim or bill service line item, institutional claim or bill service line item, or EMR encounter record providing qualifying evidence that a home health visit took place.
    • [SO/URSA-CORE] Home Health Care Visit Document-Encounter Pairs, Precursor 2 (All Master Documents): One record per document associated with a home health visit encounter as a master document; additionally includes records that would not alone qualify for an encounter of this type, but which match to one that does.
    • [SO/URSA-CORE] Home Health Care Visit Document-Encounter Pairs, Precursor 3 (Non-Master Institutional Bill or Claim Headers): One record per institutional bill or claim header record that is the parent to a qualifying institutional bill or claim service line item but not identified as a master document for this encounter; used to augment the final set of document-encounter pairs with institutional bill or claim header and discharge diagnosis records; these would otherwise be omitted because they are not masters nor descendants of a master document in the encounter (because the header and diagnosis records are associated with multiple home health encounters).
    Was this article helpful?
    What's Next