Domain
EHR, ICD-10, LOINC, SNOMED CT, patient care and clinical documentation
16,101 clinical terms
Defines the numeric ordering position of a specific step, action, or intervention within a standardized clinical protocol. Ensures that care activities are executed in the correct prescribed order, supporting patient safety and consistent protocol adherence across clinical settings and care episodes.
Records the calendar date on which a protocol-defined clinical service or intervention was delivered to the patient. Used to track adherence to protocol timelines, measure care delivery gaps, and support longitudinal analysis of treatment patterns within standardized clinical care pathways.
Captures the assessed seriousness or acuity level of a patient's condition as defined within a standardized clinical protocol, such as mild, moderate, or severe classifications. Used to determine appropriate protocol pathways, escalation thresholds, and resource allocation for protocol-driven patient management.
Records the patient's biological sex classification as required by a standardized clinical protocol, where sex-specific criteria influence eligibility, dosing, or care pathway selection. Used to ensure protocol applicability and support sex-stratified clinical outcome reporting and quality measure calculations.
Identifies the originating reference, guideline, or authoritative body from which a standardized clinical protocol was derived, such as a specialty society, regulatory agency, or institutional committee. Used to maintain traceability, version control, and evidence-based validation of protocol content within clinical systems.
Records the calendar date on which a standardized clinical protocol was initiated for a patient. Used to establish protocol duration timelines, measure time-to-treatment metrics, assess adherence to evidence-based initiation criteria, and support longitudinal reporting of protocol-driven care episodes.
Records the exact clock time at which a standardized clinical protocol was initiated for a patient. Used in time-sensitive care contexts such as sepsis bundles or stroke protocols to measure adherence to critical treatment windows and calculate time-to-intervention performance metrics.
Captures the U.S. state or geographic jurisdiction associated with a standardized clinical protocol, indicating where the protocol applies or was enacted. Used to support regional compliance reporting, multi-site protocol management, and jurisdiction-specific regulatory or licensure requirements within clinical data systems.
Indicates the current operational state of a standardized clinical protocol for a patient or at the system level, such as active, suspended, completed, or discontinued. Used to manage protocol lifecycle tracking, trigger workflow alerts, and support audit reporting of protocol adherence and completion rates.
Records the physical street address associated with the care site or entity where a standardized clinical protocol is administered or managed. Used to support facility-level reporting, multi-site protocol deployment tracking, and geographic analysis of protocol utilization across clinical locations.
Specifies the drug concentration or dosage strength prescribed within a standardized clinical protocol for a medication-based intervention, such as 500mg or 0.9% concentration. Ensures consistent pharmacologic dosing adherence across all patients managed under the same evidence-based protocol framework.
Captures an intermediate calculated sum of costs, units, scores, or quantities associated with a subset of components within a standardized clinical protocol. Used in financial reconciliation, protocol cost analysis, and multi-phase treatment reporting where partial aggregations are required before a final total is computed.
Records the calendar date on which a surgical intervention defined within or triggered by a standardized clinical protocol was performed. Used to measure adherence to protocol-specified surgical timing windows, track operative outcomes, and support perioperative quality reporting within protocol-driven care pathways.
The unique system-generated identifier assigned to a standardized clinical protocol record, enabling consistent cross-system tracking, deduplication, and data linkage across EHR, clinical data warehouse, and care management platforms throughout the full lifecycle of the protocol.
Defines the specific clinical goal, therapeutic endpoint, or measurable outcome that a standardized protocol is designed to achieve, such as a target blood pressure, HbA1c level, or infection rate reduction. Used to assess protocol effectiveness and track patient progress against defined benchmarks.
Records the National Provider Identifier taxonomy code identifying the clinical specialty or provider type associated with administering a standardized protocol. Used to classify protocol ownership by specialty, support credentialing validation, and enable specialty-stratified protocol utilization reporting across clinical systems.
Records the patient's body temperature measurement captured as part of a standardized clinical protocol assessment, such as sepsis screening or post-operative monitoring. Used to evaluate protocol eligibility criteria, trigger escalation pathways, and document vital sign trends within protocol-driven clinical documentation.
The date on which a clinical protocol officially ended or was discontinued. Used in clinical trials, care management programs, and treatment pathways to mark when a standardized set of clinical procedures or guidelines ceased to be active for a patient or study cohort.
The specific time of day at which a clinical protocol action, intervention, or assessment was performed or scheduled. Used in clinical trials and care management workflows to ensure precise sequencing and adherence to time-sensitive treatment or data collection steps.
The combined date and time value recording when a clinical protocol event, intervention, or data entry occurred. Used in clinical trials and care management systems to establish an auditable, chronological record of protocol-driven activities and ensure regulatory compliance.