Clinical

Numeric value representing the total number of documents or pages captured in a scanning session within EHR and claims document management systems. Data engineers use this field for batch validation, completeness checks, and reconciling ingested scan volumes against expected document totals.

The country in which the imaging facility performing the diagnostic scan is located. Used in claims processing for international or cross-border care scenarios, network configuration, provider credentialing records, and compliance reporting to identify the jurisdiction governing the imaging service rendered.

The unique identifier of the user, clinician, or system that initially created the diagnostic scan record in the radiology information or health information system. Used in audit logging, data governance, and workflow accountability to trace record origination and support compliance investigations.

Timestamp recording when a scanned document record was first created in EHR, claims, or document management systems. Data engineers use this field to establish audit trails, enforce SLA compliance for scan processing, and sequence records accurately during incremental data loads and ETL workflows.

The precise timestamp at which a diagnostic imaging scan record was first entered into the radiology information or health information system. Used in audit trails, workflow sequencing, and system reconciliation to establish data provenance and support turnaround time calculations for imaging services.

The patient's serum creatinine level recorded prior to a diagnostic imaging scan, particularly contrast-enhanced studies such as CT or MRI. Used to assess renal function and evaluate the risk of contrast-induced nephropathy, informing clinical decisions about contrast agent administration and patient safety protocols.

Calendar date on which a physical document or medical image was digitally captured and ingested into EHR or claims processing systems. Data engineers use this field to sequence document workflows, enforce processing SLAs, and correlate scanned records with corresponding claim or encounter dates.

Combined date and time timestamp recording the precise moment a document or medical image was captured in EHR or claims imaging systems. Data engineers use this field for high-resolution audit logging, event sequencing, and resolving processing order conflicts in real-time document ingestion pipelines.

The Drug Enforcement Administration registration number associated with a clinician who ordered a diagnostic imaging scan involving controlled substances, such as sedation protocols. Used to verify prescriber authorization, support regulatory compliance, and maintain a controlled substance audit trail in imaging workflows.

Date of death recorded or extracted from a scanned document during ingestion into EHR or member enrollment systems. Data engineers use this field to update member master records, trigger disenrollment workflows, and ensure downstream claims and eligibility systems reflect accurate mortality status.

The date on which a diagnostic imaging scan record was marked as deleted or logically removed from the active dataset in the radiology or health information system. Used in data governance, audit logging, and retention compliance to track record lifecycle management and support data integrity reviews.

Flag identifying whether a medical imaging scan record has been logically removed from the active dataset. Used in imaging workflow systems to exclude voided or erroneous scan records from clinical reporting and PACS integration without permanent data loss.

Textual explanation associated with a scanned document or medical image in EHR and claims document management systems. Data engineers use this field to support document classification, keyword indexing, and mapping scanned content to structured data elements during ingestion and transformation workflows.

Granular metadata or content information extracted from a scanned document in EHR, claims, or pharmacy systems. Data engineers use this field to capture line-level specifics such as procedure codes, member identifiers, or service details that supplement summary-level scan header records during processing.

Hospital discharge date extracted or captured from a scanned clinical or claims document in EHR and inpatient claims systems. Data engineers use this field to validate length-of-stay calculations, reconcile UB-04 claim data, and align scanned records with structured encounter and authorization records.

The scheduled deadline by which a medical imaging scan must be completed, typically driven by a physician order or clinical protocol. Used in radiology information systems to manage worklist prioritization, order compliance tracking, and patient care coordination.

The total elapsed time from scan initiation to completion for a medical imaging procedure such as MRI, CT, or ultrasound. Captured in radiology systems to assess equipment utilization, patient throughput efficiency, and procedure billing accuracy.

Electronic mail address associated with a scanned document or intake record in EHR and member enrollment systems. Data engineers use this field to link scanned correspondence to member or provider contact profiles and support automated notification workflows triggered during document processing pipelines.

Flag designating a medical imaging scan as emergent or stat, requiring immediate prioritization in the radiology worklist. Used in RIS and PACS systems to route urgent imaging requests ahead of routine orders and alert radiologists and technologists to expedite results.

Completion date marking the end of a scanned document's effective period or scanning session in EHR and claims systems. Data engineers use this field to define record validity windows, support date-range filtering in queries, and align scanned document lifecycles with claims or authorization processing timelines.