Domain
EHR, ICD-10, LOINC, SNOMED CT, patient care and clinical documentation
16,101 clinical terms
Numeric ratio value representing a proportional result for a diagnostic test in LIS and EHR systems, such as percent saturation or differential percentage. tst_pct requires precision-aware storage and normalization by data engineers to ensure cross-system comparability in clinical datasets.
Defined time span associated with a diagnostic test in LIS and EHR systems, such as a 24-hour urine collection window or timed glucose tolerance interval. tst_prd is used by data engineers to validate specimen timing, calculate collection durations, and align results to clinical events.
Contact telephone number associated with a diagnostic test facility, ordering provider, or laboratory department in EHR and LIS systems. tst_ph supports data engineers in provider directory matching, facility reference data maintenance, and contact record deduplication across healthcare datasets.
The chosen or colloquial display name for a diagnostic test, used when a shorter or more recognizable label is preferred over the formal test title. Supports user-friendly presentation in clinical ordering interfaces, patient portals, and results reporting while maintaining linkage to the official test identifier.
The established charge or cost assigned to a diagnostic test before insurance adjudication or contractual adjustments. Used in healthcare revenue cycle, charge master management, and claims processing systems to initiate billing, support price transparency reporting, and calculate patient and payer financial responsibility.
A flag designating whether a diagnostic test is the principal or primary test within a panel, order set, or clinical encounter. Used in laboratory and clinical systems to prioritize result processing, drive reporting logic, and distinguish the main diagnostic test from supplementary or reflex tests in the same order.
Coded urgency ranking assigned to a diagnostic test order in LIS and EHR systems, such as STAT, ROUTINE, or ASAP. tst_prty drives turnaround time expectations and is used by data engineers to apply SLA-based filtering, workload analysis, and result delivery workflow logic.
The calendar date on which a diagnostic test or clinical procedure was performed. Used in laboratory and clinical data systems to establish the timeline of diagnostic activity, support result interpretation, and enable longitudinal patient care tracking.
The patient's heart rate, measured in beats per minute, recorded at the time of a diagnostic test or clinical examination. Captured as a vital sign in clinical data systems to establish baseline cardiovascular status and monitor patient condition during testing.
Numeric count or volume value associated with a diagnostic test order or result in LIS, EHR, and claims systems, such as number of units ordered or specimen volume collected. tst_qty is validated by data engineers against reference ranges and billing quantity edits during claims adjudication.
The racial or ethnic identity of the patient associated with a diagnostic test record. Used in clinical and public health data systems to support population health analytics, identify health disparities, and meet regulatory reporting requirements for equity monitoring.
Defined minimum and maximum boundary values for a diagnostic test result in LIS and EHR systems, representing normal or therapeutic reference intervals. tst_rng is used by data engineers to implement result flagging logic, population health stratification, and clinical decision support rule engines.
Unit price or reimbursement amount associated with a diagnostic test in claims, PBM, and laboratory billing systems. tst_rt is used by data engineers to calculate total test costs, support fee schedule comparisons, and reconcile lab charges against contracted rates in financial reporting pipelines.
A scored or categorical assessment value assigned to a diagnostic test result or clinical finding. Used in clinical data systems to quantify severity, quality, or performance outcomes, supporting clinical decision-making and comparative effectiveness analysis.
A calculated proportional value derived from diagnostic test measurements, such as a lab analyte ratio or sensitivity-to-specificity comparison. Used in clinical data systems to express relative relationships between test components for diagnostic interpretation and clinical reporting.
Coded or free-text field in EHR and claims systems documenting the clinical indication or medical necessity justification for ordering a diagnostic test. tst_rsn is mapped to ICD diagnosis codes by data engineers to support prior authorization workflows and medical necessity validation logic.
The calendar date on which a diagnostic test specimen or test order was received by the laboratory or testing facility. Used in laboratory information systems to measure turnaround time, track chain of custody, and ensure timely processing of clinical specimens.
External identifier or pointer linking a diagnostic test to a source system record, accession number, or published standard in LIS, EHR, and claims platforms. tst_ref enables data engineers to perform cross-system lineage tracing, external code mapping, and interoperability reconciliation in integration workflows.
The calendar date on which a diagnostic test finding, abnormal result, or associated clinical condition was resolved or closed. Used in clinical data systems to measure the duration of abnormal test states and track follow-up care completion timelines.
The patient's respiratory rate, measured in breaths per minute, recorded at the time of a diagnostic test or clinical examination. Captured as a vital sign in clinical data systems to assess pulmonary function and patient stability during the testing encounter.