[SO/URSA-QUALITY] Inpatient Stay Episode Readmission Encounters for Exclusion in FUH Measure
  • 18 Jul 2025
  • 2 Minutes to read
  • Dark
    Light

[SO/URSA-QUALITY] Inpatient Stay Episode Readmission Encounters for Exclusion in FUH Measure

  • Dark
    Light

Article summary

Object Description

None

Metadata

  • Table Name: ursa.so_ursa_quality_enc_003
  • Layer: SYNTHETIC_OBJECT
  • Object Type: Simple Episode
  • Temporal Class: Interval
  • Case ID: Document ID
  • Interval Start Date: Parent Document Effective Start Date
  • Interval End Date: Parent Document Effective End Date
  • Primary Key: Ursa Serial 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)
    • Master Document 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)
    • Claim ID -- The internal database identifier (used, e.g., for joins and primary keys) for the claim. (See also [URSA-CORE] Claim)
  • Date Fields

    • 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.
  • Clinical Services Fields

    • 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)
  • Module Fields

    • Is Inpatient Stay Except Psychiatric Residential Document
  • [No Field Group]

    • Document Effective End Date +1 Day
    • Is Shared Lineage with Inpatient Stay Document
    • Is Shared Lineage with Non-Acute Inpatient Stay Document
    • Is Shared Lineage with Inpatient Stay Except Psychiatric Residential Document
    • Is Any Fracture Document
    • Is Shared Lineage with Mental Health Principal Dx Document
    • Is Shared Lineage with Intentional Self Harm Document
    • Is Encounter that Meets Acute Readmission Criteria
    • Is Encounter that Meets Nonacute Readmission Criteria
    • Rank for Readmission Selection
    • Episode ID
    • Episode Start Date
    • Episode End Date
    • Episode Length Days
    • Episode Count Components
    • Is First Component In Episode
    • Is Last Component In Episode
    • Ursa Serial ID

Was this article helpful?