Domain
Clinical
EHR, ICD-10, LOINC, SNOMED CT, patient care and clinical documentation
16,101 clinical terms
Identifies the anatomical or physiological pathway associated with a clinical finding, such as the route of medication administration, path of an infection spread, or location of a procedural approach. Used in clinical documentation to provide context for treatment decisions and to support accurate coding and clinical review.
A numeric value calculated from a standardized clinical assessment tool, such as an APGAR score, APACHE score, or depression screening scale, associated with a specific finding. Used across clinical and quality reporting workflows to quantify patient acuity, track condition severity over time, and benchmark care outcomes.
A numeric value that defines the ordered position of a clinical finding within a series of related findings or assessment components. Used in structured clinical documentation to maintain the correct display and processing order of multiple findings captured during an encounter, procedure series, or diagnostic evaluation.
Indicates the clinical seriousness or intensity level of a documented finding, such as mild, moderate, or severe. Used in EHR and clinical data systems to prioritize care responses, guide treatment decisions, and support population health risk stratification.
Records the biological sex associated with a clinical finding, used to contextualize diagnostic results that have sex-specific reference ranges or prevalence patterns. Supports clinical decision support rules and epidemiological analysis in health data systems.
Identifies the originating system, encounter, clinician, or diagnostic method that produced the clinical finding. Used in EHR and clinical data warehouses to establish provenance, support data reconciliation, and determine the reliability of documented observations.
Records the calendar date on which a clinical finding was first observed, documented, or became clinically active. Used in longitudinal patient records to establish onset timelines, track disease progression, and support duration-based clinical quality reporting.
Records the specific time of day at which a clinical finding was first observed or documented during a patient encounter. Used alongside finding start date to create precise timestamps for acute events, vital sign changes, and time-sensitive diagnostic observations.
Captures the workflow or lifecycle state of a clinical finding within a clinical documentation process, such as preliminary, confirmed, or amended. Used in EHR systems to manage documentation status and ensure findings are appropriately reviewed before influencing care decisions.
Indicates the current clinical or administrative status of a documented finding, such as active, resolved, refuted, or entered in error. Used in EHR problem lists and clinical data repositories to reflect whether the finding remains clinically relevant for ongoing patient care.
Captures the measured intensity, signal magnitude, or concentration level associated with a clinical finding, such as a lab result value or diagnostic signal. Used in clinical data systems to quantify findings that exist on a continuum requiring numeric representation for clinical interpretation.
Represents a partial aggregated value derived from a subset of related clinical finding records within an assessment or scoring instrument. Used in clinical data warehouses when composite scores are calculated incrementally across finding domains, such as pain assessments or functional evaluations.
Records the date on which a surgical procedure associated with or resulting from a clinical finding was performed. Used in clinical data systems to correlate pre-operative findings with operative interventions and support post-surgical outcome tracking and care coordination.
Identifies the anatomical site, body system, or clinical focus that a finding specifically addresses or describes. Used in structured clinical documentation to link observations to precise locations or physiological targets, supporting detailed diagnostic coding and clinical decision support.
Stores a standardized hierarchical classification code, such as SNOMED CT or ICD, used to categorize a clinical finding within a recognized medical terminology system. Enables interoperable exchange, clinical analytics, and consistent grouping of findings across health data platforms.
Records a body temperature measurement documented as a clinical finding during a patient encounter or monitoring period. Stored in clinical data systems as a vital sign observation to support fever detection, infection monitoring, sepsis screening protocols, and longitudinal wellness tracking.
Records the calendar date on which a clinical finding was resolved, discontinued, or closed in the patient record. Used in EHR and clinical data warehouses to calculate finding duration, mark inactive conditions, and support longitudinal analysis of disease resolution and treatment outcomes.
Captures the specific time of day associated with the observation or documentation of a clinical finding. Used in clinical data systems to sequence findings within an encounter, support time-critical clinical workflows, and enable precise event correlation in acute care and monitoring contexts.
Stores the combined date and time at which a clinical finding was observed, recorded, or last updated in the clinical system. Used in EHR audit trails, longitudinal records, and clinical data warehouses to establish precise chronological sequences for patient safety and outcome analysis.
Contains the human-readable label or descriptive name assigned to a clinical finding within the patient record. Used in clinical documentation and reporting to provide clinicians with a clear, standardized description of the observation that supplements coded terminology values.