[SO/URSA-CKD] Document Aggregator for URSA-CKD Concepts

Object Description

One row per patient document related to an URSA-CKD module concept.

Metadata

• Table Name: ursa.so_ursa_ckd_pat_001
• Layer: SYNTHETIC_OBJECT
• Object Type: Single Stack
• Temporal Class: Event
• Case ID: Document ID
• Event Date: Document Effective Date
• Primary Key: Document 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)
  • 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)
  • 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)
  • 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)
  • 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)
  • 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

  • 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.
  • Label Description -- Supplies the name given to the product by the manufacturer.

• 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 Paid Amount

• Metadata Fields

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

• Validation Only Fields

  • Is GFR Lab for Black Patients
  • Is GFR Lab for Non-Black or Unspecified Race Patients

• 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

• Module Fields

  • Race-Adjusted GFR Result Numeric
  • Is CKD Stage 1 GFR
  • Is CKD Stage 2 GFR
  • Is CKD Stage 3 GFR
  • Is CKD Stage 3a GFR
  • Is CKD Stage 3b GFR
  • Is CKD Stage 4 GFR
  • Is CKD Stage 5 GFR
  • Is CKD Stage 1 Diagnosis Code
  • Is CKD Stage 2 Diagnosis Code
  • Is CKD Stage 3 Diagnosis Code
  • Is CKD Stage 4 Diagnosis Code
  • Is CKD Stage 5 Diagnosis Code
  • Is ESRD Diagnosis Code
  • Is Performed Dialysis Code
  • Is Chronic Dialysis Status Code
  • Is Document Dialysis Setting Outpatient Dialysis Facility
  • Is Document Dialysis Setting Home
  • Is Document Dialysis Setting Inpatient
  • Is Document Dialysis Setting Outpatient Non-Dialysis Facility
  • Is Document Dialysis Modality Hemodialysis
  • Is Document Dialysis Modality Peritoneal Dialysis
  • Is Document Vascular Access Type Any Catheter
  • Is Document Vascular Access Type Graft Without Catheter
  • Is Document Vascular Access Type Fistula Only
  • Is Kidney Transplantation Code
  • Is History of Kidney Transplant Code
  • Is DNR Status Code
  • Is ACP Discussion Code
  • Is History of ACP Discussion Code
  • Is Performed HbA1c Code
  • Is Last HbA1C <= 9 Code
  • Is Last HbA1C > 9 Code
  • Is Last SBP < 140 Code
  • Is Last DBP < 90 Code
  • Is Pneumococcal Vaccine

Foreign Keys

• document_id → ursa.so_ursa_core_pat_001.document_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_line_item_id → ursa.no_ursa_core_enc_002.emr_enc_service_line_item_id
• emr_enc_dx_id → ursa.no_ursa_core_cond_005.emr_enc_dx_id
• pat_obs_id → ursa.no_ursa_core_pat_003.pat_obs_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