xCaliber healthCare Data Mesh

Lab Order

Lab Order

Source Object: Lab Order

The Lab Order source object is an integral part of healthcare data management, providing comprehensive information about laboratory orders, tests, and associated details. It plays a crucial role in facilitating diagnostic and monitoring processes for patients.

Overview

Laboratory orders are a common aspect of patient care, helping healthcare providers diagnose medical conditions and track patients' health. The Lab Order source object encompasses various data fields that capture essential information related to lab orders, tests, and their execution.

Usage

The Lab Order source object serves several key purposes in healthcare data management:

  1. Order Details: It captures information about the lab order, including the order's creation date, confidentiality status, and the physician who placed the order.
  2. Patient Information: It associates the lab order with the patient for whom the tests are intended, ensuring that test results are correctly matched with the patient's medical record.
  3. Practice and Facility: Specifies the practice responsible for the lab order and the facility where the tests will be conducted.
  4. Test Details: Provides comprehensive information about the tests, including test codes, names, compendium references, and associated procedures. This allows for clear test identification and proper execution.
  5. Submission Information: Tracks the state and metadata related to the submission of the lab order. This can include acknowledgment time and submission time.
  6. Answers: Captures answers to specific questions or queries related to the tests, providing additional context and information for healthcare professionals.
  7. Site Information: Specifies the location (address, city, state, etc.) where the tests are to be conducted.
  8. Specimens: Contains data related to the specimens collected for testing, including body site, container information, descriptions, and modifiers.
  9. Resolution Details: Documents information about the resolution of the lab order, such as notes and resolving documents.

By utilizing the Lab Order source object, healthcare professionals can effectively manage the entire process of ordering, conducting, and resolving laboratory tests for patients. It ensures that test results are correctly associated with the corresponding patient's medical records and that the diagnostic process is conducted efficiently and accurately.

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
bill_typeStringTop Level0..1Who is financially responsible for the order.-'thirdparty', 'patient', 'client', 'workerscomp', 'specialbilling'ServiceRequestextension[*].valueCode-NAbill-typeTBD
ccsIntegerTop Level0..*List of physician ids who should be cc'd on any reports.--ServiceRequestextension[].extension[].valueInteger-NAccinteger
chart_dateDateTimeTop Level0..1Date at which this order was first seen in the patient's chart.--ServiceRequestextension[*].valueString-NAchart-datestring
confidentialBooleanTop Level0..1Whether the provider has marked the order as confidential. Should not be shared with a patient.-true, falseServiceRequestextension[*].valueBoolean-NAconfidentialstring
contentObjectTop Level0..1Represents the content of the lab order report.--ServiceRequest--NA-TBD
content.collection_datetimeDateTimeTop Level0..1If lab specimen collection is done onsite, this is the time at which the collection was taken.--ServiceRequestextension[*].valueDateTime-NAcollection-dateTBD
content.fasting_methodStringTop Level0..1Instructions for patient and lab on how long they should fast before specimen collection.-'fasting_12_hour', 'fasting_8_hours', 'fasting_2_hours', 'fasting_none', 'fasting_random'ServiceRequestextension[*].valueString-NAfasting-statusstring
content.icd10_codesObjectTop Level0..*ICD10 diagnosis codes provided along with the order.--ServiceRequest--ICD10-TBD
content.icd10_codes.codeStringTop Level0..1---ServiceRequestreasonCode[].coding[].code-ICD10-TBD
content.icd10_codes.descriptionStringTop Level0..1---ServiceRequestreasonCode[].coding[].display-NA-TBD
content.patient_instructionsStringTop Level0..1Notes for patient.--ServiceRequestpatientInstruction-NA-TBD
content.standing_order_end_dateDateTop Level0..1Date at which standing order should be canceled.--ServiceRequestextension[*].valueDateTime-NAend-dateTBD
content.standing_order_frequencyStringTop Level0..1Number of times order should be performed on a standing basis.-string(50)ServiceRequestextension[*].valueString-NAfrequencystring
content.stat_methodStringTop Level0..1--'wet_reading_phone', 'wet_reading_fax', 'stat_phone','stat_fax', 'stat_phone_fax'ServiceRequestextension[*].valueString-NAstat-methodstring
content.test_center_notesStringTop Level0..1Notes for Lab.--ServiceRequestnote[1].text-NA-markdown
content.testsObjectTop Level0..*The list of tests that should be performed by the lab. Must all be either from the same compendium or no compendium.--ServiceRequest--NA-TBD
content.tests.codeStringTop Level0..1Any code associated with the test, usually provided by the lab vendor's compendium.-string(50)ServiceRequestcode.coding[1].code-NA-TBD
content.tests.compendiumIntegerTop Level0..1The id of the compendium provided the lab vendor that provides the lab order test. All tests in the same order MUST share the same compendium.--ServiceRequestcode.extension[*].valueInteger-NAcompendiuminteger
content.tests.cptsIntegerTop Level0..*A list of CPT codes associated with the lab order test.--ServiceRequestcode.extension[*].valueInteger-CPTcptsinteger
content.tests.created_dateDateTimeTop Level0..1Time at which Elation created this Lab Order Test.--ServiceRequestcode.extension[*].valueDateTime-NAcreated-dateTBD
content.tests.deleted_dateDateTimeTop Level0..1Time at which this Lab Order Test was deleted. Can happen when a lab order compendium update deprecates a test.--ServiceRequestcode.extension[*].valueDateTime-NAdeleted-dateTBD
content.tests.idIntegerTop Level0..1The id of the Lab Order Test.--ServiceRequestcode.id-NA-TBD
content.tests.lab_vendorIntegerTop Level0..1The id of the lab vendor who provides the lab order test.--ServiceRequestcode.extension[*].valueInteger-NAlab-vendorinteger
content.tests.nameStringTop Level0..1The name of the Lab Order Test.-string(255)ServiceRequestcode.extension[*].valueString-NAtest-namestring
content.tests.practice_createdIntegerTop Level0..1The id of the practice that created the test if practice created.--ServiceRequestcode.extension[*].valueInteger-NApractice-createdinteger
content.tests.procedure_classStringTop Level0..1Code provided by specific compendiums that indicate the "class" of test, e.g. histology vs cytology. Some lab vendors require that tests with specific procedure classes need to ordered separately.-string(50)ServiceRequestcode.extension[*].valueString-NAprocedure-classstring
content.tests.questionsObjectTop Level0..*A list of Ask on Entry (AOE) Questions that need to be answered by the orderer when creating the order.--ServiceRequestcode.extension[*].valueString-NAquestionsstring
content.tests.synonymsStringTop Level0..*A list of synonyms that are useful when searching for a specific test.--ServiceRequestcode.extension[*].valueString-NAsynonymsstring
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
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
facilityIdTop Level0..1An identifier that represents the facility placing the order. Usually assigned by the lab vendor.--ServiceRequestextension[*].valueString-NAfacilityTBD
follow_up_methodStringTop Level0..1Freetext field communicating how the patient should receive their results.--ServiceRequestextension[*].valueString-NAfollow-upstring
idIntegerTop Level0..1The id of the lab order in Elation's systems. Will be unique.--ServiceRequestid-NA-TBD
ordering_physicianIntegerTop Level0..1The id of the physician who created the order.--ServiceRequestrequester.reference-NA-TBD
patientIntegerTop Level0..1The id of the patient.--ServiceRequestsubject.reference-NA-TBD
practiceIntegerTop Level0..1The id of the practice.--ServiceRequestextension[*].valueReference.reference-NApracticeTBD
requisitionIntegerTop Level0..1The requistion id of the order. Can be different from the order id if and when the order was created outside of elation.--ServiceRequestextension[*].valueInteger-NArequisitioninteger
signed_byIntegerTop Level0..1The id of the physician who signed off on the order--ServiceRequestextension[*].valueInteger-NAsigned-byinteger
signed_dateDateTimeTop Level0..1The time when the order was signed.--ServiceRequestextension[*].valueString-NAsigned-datestring
special_insuranceObjectTop Level0..1Used primarily to support specific electronic lab order integrations.--ServiceRequest--NA-TBD
special_insurance.codeStringTop Level0..1--string(5)ServiceRequestinsurance.reference-NA-TBD
special_insurance.nameStringTop Level0..1--string(64)ServiceRequestinsurance.display-NA-TBD
submissionsObjectTop Level0..*Record of the attempts to submit--ServiceRequest--NA-TBD
tagsStringTop Level0..*Any tags associated with the lab order.--ServiceRequestextension[]extension[].valueString-NAtagstring
test_dateDateTop Level0..1The date on which the tests should be performed, or were performed. Can be different than document_date, create_date--ServiceRequestextension[*].valueDateTime-NAtest-dateTBD
vendorIntegerTop Level0..1---ServiceRequestperformer.reference-NA-TBD
answersObjectContained0..*List of the answers provided for the Ask on Entry (AOE) questions if required by any lab order tests.--QuestionnaireResponse--NA-TBD
answers.created_dateDateTimeContained0..1When the answer was created.--QuestionnaireResponsecontained[].item[].extension[*].valueDateTimeresourceType == QuestionnaireResponseNAcreated-dateTBD
answers.deleted_dateDateTimeContained0..1When the answer was deleted--QuestionnaireResponsecontained[].item[].extension[*].valueDateTimeresourceType == QuestionnaireResponseNAdeleted-dateTBD
answers.questionIntegerContained0..1The id of the AOE question for which this answer pertains.--QuestionnaireResponsecontained[].item[].linkIdresourceType == QuestionnaireResponseNA-TBD
answers.testIntegerContained0..1The id of the test for which this answer pertains.--QuestionnaireResponsecontained[*].identifier.valueresourceType == QuestionnaireResponseNA-TBD
answers.valueStringContained0..1The value entered by freetext or chosen by the ordering physician.--QuestionnaireResponsecontained[].item[].answer[0].valueStringresourceType == QuestionnaireResponseNA-string
siteStringContained0..1The location where the patient will have the lab performed. Sites are specific to their lab vendor.--Location--NA-TBD
site.addressStringContained0..1The streetname of the site.-string(200)Locationcontained[*].address.line[2]-NA-TBD
site.cityStringContained0..1--string(50)Locationcontained[*].address.city-NA-TBD
site.faxStringContained0..1--string(20)Locationcontained[].telecom[].valuesystem == faxNA-TBD
site.nameStringContained0..1The name of the site.-string(200)Locationcontained[*].name-NA-TBD
site.phoneStringContained0..1--string(20)Locationcontained[].telecom[].valuesystem == phoneNA-TBD
site.stateStringContained0..1--string(2)Locationcontained[*].address.state-NA-TBD
site.suiteStringContained0..1--string(35)Locationcontained[*].address.line[1]-NA-TBD
site.zipStringContained0..1--string(10)Locationcontained[*].address.postalCode-NA-TBD
specimensObjectContained0..*Record of any specimens collected when creating the order.--Specimen--NA-TBD
specimens.body_siteObjectContained0..1Information about the body site where the specimen was collected.--Specimen--NA-TBD
specimens.body_site.codeStringContained0..1The HL7 code representing the body site from which a specimen was collected-string(16)Specimencontained.collection.bodySite.coding[1].code-NA-TBD
specimens.body_site.deleted_dateDateTimeContained0..1Represents if the body site was removed from the specimen.--Specimencontained.collection.bodySite.extension[1].valueDate-NAdeleted-datestring
specimens.body_site.textStringContained0..1A textual description of the body site from which the specimen was collected.-string(64)Specimencontained.collection.bodySite.coding[1].display-NA-TBD
specimens.container_idIntegerContained0..1An identifier representing the container used to store the specimen.--Specimencontained.container[1].identifier[1].value-NA-TBD
specimens.descriptionStringContained0..1A freetext description of the specimen.-string(40)Specimencontained.note[1].text-NA-markdown
specimens.modifiersObjectContained0..*Coded Modifiers indicating more information about the body site from which the specimen was collected.--Specimencontained.extension[1]-NAmodifierTBD
specimens.modifiers.modifier.codeStringContained0..1The HL7 code representing the modifier on the body site from which a specimen was collected-string(3)Specimencontained.extension[1].extension[*].valueString-NAbodysite_modifier_codestring
specimens.modifiers.modifier.textStringContained0..1A textual description of the modifier of the body site from which the specimen was collected.-string(64)Specimencontained.extension[1].extension[*].valueString-NAbodysite_modifier_textstring
specimens.modifiers.sequenceIntegerContained0..1The cardinal position in which the modifiers should be listed.--Specimencontained.extension[1].extension[*].valueString-NAbodysite_modifier_sequencestring
specimens.testIntegerContained0..1The lab order test for which the specimen as collected.--Specimencontained.extension[1].valueInteger-NAtestinteger
submissions.stateStringContained0..1The state of the electronic order submission.-string(20)Provenancecontained[].extension[].valueStringresourceType == ProvenanceNAstatestring
submissions.state_metadataStringContained0..1Useful error information collected as part of the submission. Including ERRORs or ACKs.-string(1500)Provenancecontained[].meta.extension[].valueStringresourceType == ProvenanceNAmetadataTBD
submissions.time_acknowledgedDateTimeContained0..1The time at which a user acknowledged any error shown to them about the electronic submission.--Provenancecontained[*].recordedresourceType == ProvenanceNA-TBD
submissions.time_submittedDateTimeContained0..1The time the electronic order was submitted to the lab vendor.--Provenancecontained[*].occurredDateTimeresourceType == ProvenanceNA-TBD
resolution.created_dateDateTimeContained0..1The datetime when this resolution state was created.--Taskcontained[].extension[].valueDateTime-NAcreated-dateTBD
resolution.deleted_dateDateTimeContained0..1The datetime when this resolution was deleted. Should never be null because we're providing the most updated resolution.--Taskcontained[].extension[].valueDateTime-NAdeleted-dateTBD
resolution.documentIntegerContained0..1Will be the same as the id of the lab order.--Taskcontained[].extension[].valueInteger-NAdocumentinteger
resolution.idIntegerContained0..1Internal id to represent the resolution state.--Taskcontained[*].idresourceType == Task & code.coding[].code== fulfillNA-TBD
resolution.noteStringContained0..1Any note that was added to represent why an order was cancelled.--Taskcontained[*}.note[1].text-NA-markdown
resolution.resolving_documentIntegerContained0..1If the order is fulfilled will indicate the document referenced. For lab orders will usually be a report.--Taskcontained[].extension[].valueInteger-NAresolving-documentinteger
resolution.stateStringContained0..1The resolution state of the order.-outstanding, fulfilled, cancelledTaskcontained[].extension[].valueString-NAstateTBD