xCaliber healthCare Data Mesh

Cardiac Order

Cardiac Order

Source Object: Cardiac Order

The Cardiac Order source object represents orders and records related to cardiac procedures, tests, and treatments within the healthcare system.

Overview

In the context of healthcare, cardiac orders are vital for the diagnosis, treatment, and monitoring of cardiac conditions. These orders encompass various aspects of patient care in the cardiology department, including diagnostic tests, procedures, and prescriptions related to heart health.

Usage

The Cardiac Order source object serves several essential purposes in healthcare systems:

  1. Diagnosis and Monitoring: Cardiac orders are used for diagnostic tests like electrocardiograms (ECG or EKG), echocardiograms, and other procedures to diagnose and monitor heart conditions.
  2. Prescriptions: They may include orders for cardiac medications, specifying dosage, frequency, and duration of use.
  3. Follow-Up: Cardiac orders can designate the recommended follow-up methods, such as scheduled appointments for reevaluations, further tests, or consultations.
  4. ICD-10 Codes: These orders often contain International Classification of Diseases, 10th Edition (ICD-10) codes for accurate coding and billing related to cardiac conditions.
  5. Clinical Reason: The clinical reason field may contain information about the medical necessity or rationale behind the cardiac order.
  6. Confidentiality: The confidential flag may indicate if certain cardiac orders or associated documents are restricted or confidential.
  7. Practice Information: Cardiac orders are associated with specific medical practices and may include practice-specific details.

The Cardiac Order source object plays a crucial role in the management of cardiac patients' health by facilitating accurate diagnostics, treatments, and follow-up plans.

Mapping Table

Data FieldSource Field Data TypeResource Mapping ContextSource Data Field CardinalitySource Data Field DescriptionExample ValueSource Data Field Validation RuleMapped FHIR ResourceMapped FHIR Data FieldAugmented MappingAssociated Coding SystemAssociated FHIR Data Field ExtensionMapped FHIR Data Field Type
chart_dateDateTimeTop Level0..1Date at which this order was first seen in the patient's chart.--ServiceRequestextension[*].valueString-NAchart-dateTBD
clinical_reasonStringTop Level0..1The reason for clinical--ServiceRequestextension[*].valueString-NAclinical-reasonTBD
confidentialBooleanTop Level0..1Whether the provider has marked the order as confidential. Should not be shared with a patient.TRUEtrue, falseServiceRequestextension[*].valueBoolean-NAconfidentialTBD
created_dateDateTimeTop Level0..1Time at which elation created this order. Can be different from chart_date when the order was imported into a chart from a different source and document_date when documenting an order that happened at some other time.--ServiceRequestauthoredOn-NA-TBD
deleted_dateDateTimeTop Level0..1Time at which elation deleted this order.--ServiceRequestextension[*].valueDateTime-NAdeleted-dateTBD
document_dateDateTimeTop Level0..1Time at which this order was created in whichever system created it. Could be historical or same as the create_date.--ServiceRequestoccurrenceDateTime-NA-TBD
follow_up_methodStringTop Level0..1Freetext field communicating how the patient should receive their results.email-ServiceRequestextension[*].valueString-NAfollow-upTBD
icd10_codesObjectTop Level0..*List of ICD10 codes--ServiceRequest--NA-TBD
icd10_codes.codeStringTop Level0..1icd 10 code--ServiceRequestreasonCode.coding[*].code-NA-TBD
icd10_codes.descriptionStringTop Level0..1icd10 description--ServiceRequestreasonCode.coding[*].display-NA-TBD
idIntegerTop Level0..1The id of the Cardiac order in Elation's systems. Will be unique.--ServiceRequestid-NA-TBD
medicationsStringTop Level0..1---ServiceRequestextension[*].valueString-NAmedicationsTBD
patientIntegerTop Level0..1The id of the patient.--ServiceRequestsubject.reference-NA-TBD
practiceIntegerTop Level0..1The id of the practice.--ServiceRequestextension[*].valueReference.referenceOrganizationNApracticeTBD
prescribing_userIntegerTop Level0..1---ServiceRequestrequester.reference-NA-TBD
signed_dateDateTimeTop Level0..1The time when the order was signed.--ServiceRequestextension[*].valueString-NAsigned-dateTBD
testsObjectTop Level0..*The list of tests that should be performed--ServiceRequest--NA-TBD
tests.codeStringTop Level0..1Any code associated with the test.--ServiceRequestcode.coding[1].code-NA-TBD
tests.created_dateDateTimeTop Level0..1Time at which Elation created this Cardiac Order Test.--ServiceRequestcode.extension[*].valueDateTime-NAcreated-dateTBD
tests.deleted_dateDateTimeTop Level0..1Time at which this Cardiac Order Test was deleted.--ServiceRequestcode.extension[*].valueDateTime-NAdeleted-dateTBD
tests.idIntegerTop Level0..1The id of the Cardiac Order Test.--ServiceRequestcode.id-NA-TBD
tests.nameStringTop Level0..1The name of the Cardiac Order Test.--ServiceRequestcode.extension[*].valueString-NAtest-nameTBD
tests.practice_createdIntegerTop Level0..1The id of the practice that created the test if practice created.--ServiceRequestcode.extension[*].valueInteger-NApractice-createdTBD