Laboratory

Defines the classification tier of a biological sample such as primary, aliquot, or derived in LIS and EHR systems, distinguishing specimen roles within the testing workflow. Data engineers use this field to enforce class-specific handling rules, support specimen hierarchy modeling, and map classification tiers to downstream result and billing systems.

Contains the standardized coded value identifying the type or nature of a biological sample using coding systems such as SNOMED CT or HL7 v2 specimen type codes in LIS and EHR systems. Data engineers use this field for specimen type normalization, interoperability mapping, and LOINC-based test ordering validation across lab interfaces.

Stores free-text notations entered by laboratory or clinical staff regarding a biological sample's condition, collection circumstances, or processing instructions in LIS and EHR systems. Data engineers must handle this field with NLP processing pipelines to extract structured insights from unstructured text for quality reporting and lab exception workflows.

Records the communication point, such as a provider, ordering clinician, or department contact, associated with a biological sample in LIS and EHR systems. Data engineers use this field to support result notification routing, critical value alert workflows, and provider attribution in lab analytics and quality reporting pipelines.

Tracks the total number of biological samples associated with an order, patient encounter, or batch submission in LIS and EHR systems. Data engineers use this field for specimen volume reporting, batch validation to detect missing samples, and workload analytics across laboratory information system ingestion pipelines.

Records the date on which a biological sample record was first created or registered in the LIS or EHR system, establishing the start of the specimen's data lifecycle. Data engineers use this field for audit logging, SLA turnaround time calculations, incremental data load strategies, and temporal partitioning in lab data warehouse pipelines.

The calendar date a biological specimen was collected from a patient, recorded in LIS, EHR, and lab claims systems. Critical for data engineers linking lab results to encounters, tracking turnaround times, and validating temporal sequencing in diagnostic workflows.

The combined date and timestamp capturing the precise moment a biological specimen was collected, as recorded in LIS and EHR platforms. Data engineers use this field to calculate lab turnaround times, resolve ordering conflicts, and enforce time-based data quality rules.

The recorded date associated with specimen invalidation or patient death, used in EHR and LIS systems to flag specimens that should be excluded from active processing pipelines. Data engineers use this to filter deceased-patient records in longitudinal lab analytics and cohort studies.

Free-text or coded textual explanation of a biological specimen's type, source, or condition, as stored in LIS and EHR systems. Data engineers rely on this field for specimen classification, normalization to standard terminologies like SNOMED or HL7, and downstream lab result routing logic.

Granular attribute data describing the characteristics of a biological specimen, such as volume, color, or collection method, stored in LIS and EHR systems. Data engineers use this field for specimen quality validation, rejection workflows, and building enriched lab datasets for clinical analytics.

The date on which a biological specimen record becomes active and valid for use in clinical or analytical processes within LIS, EHR, and lab claims systems. Data engineers apply this field in slowly changing dimension logic, temporal joins, and active-record filtering across lab data pipelines.

The electronic mail address associated with a specimen record, typically referencing the ordering provider or lab contact in LIS and EHR systems. Data engineers use this field for notification workflow integrations, result delivery routing, and provider communication audit trail construction.

The date marking the close of a specimen's active processing window or record validity period in LIS and EHR systems. Data engineers use this field in date-range filtering, SCD Type 2 historical tracking, and identifying specimens no longer eligible for result reporting or quality review.

The date after which a biological specimen is no longer considered viable for testing, as stored in LIS and lab inventory systems. Data engineers use this field to enforce data quality rules, exclude expired specimens from analytical pipelines, and support lab compliance reporting requirements.

A binary or coded status marker indicating a specific condition or exception for a biological specimen, such as hemolysis or rejection, within LIS and EHR systems. Data engineers use this field to filter invalid specimens, trigger quality control workflows, and build exception-based lab reporting datasets.

The unique alphanumeric key assigned to a biological specimen within LIS, EHR, and lab claims systems, enabling traceability from collection through result reporting. Data engineers use this as a primary join key when linking specimen records to orders, results, and patient encounter data across systems.

A positional or sequential number assigned to a biological specimen within an ordered set or collection batch in LIS and EHR systems. Data engineers use this field to maintain ordering integrity, manage multi-specimen workflows, and resolve duplicate specimen records during data integration processes.

A boolean or coded value signaling a specific status or attribute of a biological specimen, such as fasting state or chain-of-custody compliance, within LIS and EHR platforms. Data engineers use this field to segment specimen populations, apply business rules, and support conditional logic in lab pipelines.

Structured or free-text guidance associated with the handling, processing, or storage of a biological specimen, captured in LIS and EHR order management systems. Data engineers use this field to automate routing logic, validate compliance with collection protocols, and enrich lab workflow datasets.