Domain
Scheduling, facilities, departments, workflows, and staff
6,492 operations terms
The recorded body temperature value captured on a clinical assessment or vital signs form, typically expressed in Fahrenheit or Celsius. Used in inpatient, outpatient, and emergency care documentation to track patient physiological status and support clinical decision-making and care protocols.
The date on which a healthcare form, authorization, or associated record becomes inactive or expired. Used in prior authorization forms, member enrollment documents, and clinical agreements to define the end of a valid coverage or approval period, triggering workflow or renewal processes.
The time-of-day value recorded on a standardized clinical or administrative form in EHR or claims systems, capturing when a service, assessment, or event occurred. Data engineers use this field alongside form date to construct precise event timestamps for audit trails and chronological encounter sequencing.
The combined date and time value recording when a standardized form was created, submitted, or last modified in EHR, claims, or member enrollment systems. Data engineers rely on this field for change data capture, record versioning, SLA monitoring, and establishing event ordering in data warehouse pipelines.
The official name or label assigned to a healthcare form that identifies its purpose and clinical or administrative context, such as 'Prior Authorization Request' or 'Discharge Summary'. Used to classify, index, and retrieve forms within EHR and document management systems.
The aggregated sum value representing the cumulative score, cost, quantity, or measurement derived from all line items or sections of a standardized form in EHR, claims, or PBM systems. Used by data engineers to validate form completeness, calculate billed amounts, and support financial and clinical reporting.
The aggregate number of items, entries, line items, or form instances recorded within a given dataset or submission. Used in claims batch processing, clinical audit reporting, and healthcare operations to quantify volume and validate completeness of form submissions across data systems.
The category classification identifying the kind of standardized form used in EHR, claims, pharmacy, or member enrollment systems, such as prior authorization, clinical assessment, intake, or discharge form. Data engineers use this field to apply type-specific parsing logic, schema mappings, and routing rules during data ingestion.
The unit of measurement associated with a data element captured on a standardized clinical or administrative form in EHR or PBM systems, such as mg, days, or units. Data engineers use this field to normalize measurements across heterogeneous source systems and ensure dimensional consistency in analytics datasets.
The most recent date on which a healthcare form record was modified, corrected, or amended within a clinical or administrative system. Used in audit trails, version control workflows, and data governance processes to maintain an accurate history of changes to form-level data.
The priority or time-sensitivity level assigned to a healthcare form, indicating how quickly it must be processed or acted upon (e.g., routine, urgent, emergent). Used in prior authorization requests, referral forms, and clinical order documentation to drive appropriate response timeframes.
The specific measured or recorded data point captured within a field of a standardized clinical or administrative form in EHR, claims, or care management systems. Data engineers use this field to extract structured responses, populate fact tables, and support clinical and operational reporting across diverse form types.
The sequential or labeled version number of a healthcare form that tracks iterations resulting from regulatory updates, policy changes, or clinical guideline revisions. Used in document control and compliance workflows to ensure the correct and current form version is applied in clinical and administrative processes.
The five or nine-digit postal ZIP code associated with the address captured on a healthcare form, such as a patient address, service location, or billing address. Used in claims processing, member enrollment, and geographic analysis to support correct routing, eligibility, and reporting functions.
A code identifying the formulary tier assigned to a specific prescription drug under a health plan pharmacy benefit design, such as tier 1 generic, tier 2 preferred brand, tier 3 non-preferred brand, tier 4 specialty, or tier 5 high-cost specialty. Formulary tier determines member cost-sharing for the drug and is a primary lever in pharmacy benefit management cost control strategies.
The planned calendar date on which a specific drug formulation is scheduled to be prepared, dispensed, or administered to a patient. Used in pharmacy compounding workflows, infusion therapy scheduling, and medication management systems to coordinate preparation with clinical administration timelines.
The planned clock time at which a specific drug formulation is scheduled for preparation or administration. Used in inpatient pharmacy systems, infusion therapy, and chemotherapy protocols to coordinate compounding, delivery, and nursing administration within precise clinical timing requirements.
Standardized unit of measure defining the physical form and quantity of a drug preparation in pharmacy and PBM systems. Examples include mg, mL, or tablet, and are used to support prescription validation, drug utilization review, and formulary management workflows.
The physical location associated with a medication administration frequency record, such as the care setting or facility address where the dosing schedule is applied. Used in home health, long-term care, and outpatient medication management to link dosing schedules to the appropriate care delivery site.
The current authorization state of a medication administration frequency, indicating whether the prescribed dosing interval has been approved, pended, or denied by clinical review or pharmacy verification. Used in medication order management to ensure compliant and safe administration schedules before clinical execution.