Technology

Unique system-generated key assigned to a documented coexisting chronic or secondary condition present alongside a primary diagnosis. Used in clinical and claims systems to support risk adjustment, care management stratification, and accurate coding of complex patient health status.

Unique system-generated key assigned to a documented secondary adverse condition arising during or after treatment. Used in clinical quality and coding systems to track hospital-acquired conditions, surgical complications, and their impact on care outcomes and claims coding.

A dimension table designed to be shared across multiple fact tables and subject areas in a data warehouse, ensuring consistent definitions and values for common attributes across all analytics domains. In healthcare data warehouses, DIM_MEMBER and DIM_PROVIDER are the canonical conformed dimensions referenced by claims, pharmacy, encounters, and quality measure fact tables, enabling cross-domain analytics such as total cost of care that requires joining member attributes consistently across all care settings.

Unique system-generated key assigned to a patient consent document record, including informed consent for procedures or data sharing agreements. Used to verify consent status across clinical and compliance systems prior to treatment delivery or protected health information release.

Unique system-generated key assigned to a specialist consultation request and response record. Used in clinical systems to track referral initiation, specialist findings, and recommendations, linking the consulting clinician's input to the ordering encounter and care plan.

Unique system-generated key assigned to a single-use clinical supply item record, such as syringes, dressings, or IV tubing. Used in supply chain and charge capture systems to track inventory consumption, cost attribution, and billing of disposable items to patient encounters.

Unique system-generated key assigned to a licensed mental health counselor or therapist within clinical and behavioral health platforms. Enables consistent tracking of counselor-patient relationships, session history, and treatment outcomes across care coordination and EHR systems.

Unique system-generated key assigned to a Current Procedural Terminology code record within claims processing and billing systems. Links procedure codes to claims, remittance, and reimbursement workflows, enabling accurate fee schedule lookups, utilization tracking, and medical billing reconciliation.

The date or timestamp recording when a record was first inserted into a healthcare data system. Standard audit column in all healthcare data warehouse tables following ISO-11179 naming conventions. Implemented as create_dt in physical schemas across EHR, claims, pharmacy, and member enrollment systems.

Unique system-generated key assigned to a credit transaction representing an overpayment, adjustment, or balance reduction in healthcare billing and accounts receivable systems. Used to track and reconcile financial credits applied against patient accounts, claims, or provider payments.

Unique system-generated key assigned to a computed tomography imaging record within radiology information systems and clinical data warehouses. Enables tracking of CT scan orders, results, and associated diagnostic reports across imaging workflows and care episodes.

A boolean indicator identifying the most recent version of a record in a slowly changing dimension table in a healthcare data warehouse. Only one version of each entity has current flag set to true at any point in time. Used alongside effective date and expiration date in SCD Type 2 implementations.

The irreversible process of removing or altering personal identifiers in a dataset such that individuals cannot be re-identified even by the data custodian using any available means, distinguishing it from pseudonymization or tokenization where re-identification is possible with access to a key. In healthcare analytics, data anonymization enables use of clinical data for research, public health reporting, and AI model training without HIPAA Privacy Rule restrictions, but requires rigorous privacy risk assessment to prevent re-identification through data linkage attacks.

Technical professional responsible for designing and overseeing the data architecture of healthcare information systems. Data architects define data models, integration patterns, governance frameworks, and technology standards for healthcare data platforms. They bridge clinical and business requirements with technical implementations across EHR systems, data warehouses, and analytics platforms.

The design and structure of data systems including data models, storage systems, integration patterns, and governance frameworks within a healthcare organization. Healthcare data architecture encompasses source systems like EHRs and claims platforms, integration layers, data warehouses, and analytics environments. Sound data architecture ensures data quality, security, scalability, and compliance with HIPAA and CMS requirements.

A centralized metadata management tool that provides a searchable inventory of data assets including tables, columns, pipelines, dashboards, and ML models, enriched with business definitions, data quality scores, ownership information, and lineage relationships. In healthcare data platforms, a data catalog enables data engineers, analysts, and clinical informatics teams to discover available datasets, understand their content and quality, and assess regulatory classification such as PHI sensitivity before accessing or using data.

The process of categorizing data assets according to their sensitivity, regulatory classification, and required handling procedures, typically using tiers such as public, internal, confidential, restricted, and highly restricted. In healthcare data platforms, data classification drives PHI identification, access control policies, encryption requirements, audit logging intensity, and data sharing agreements, with PHI and ePHI classified at the highest sensitivity tiers requiring the most stringent controls.

A formal agreement between data producers and data consumers defining the schema, semantics, quality standards, freshness guarantees, and support level associated with a data product or pipeline output. Data contracts are an emerging practice in healthcare data engineering that shift data quality responsibility to the producing team, reducing the reactive burden on consuming teams when upstream schema changes or data quality issues break downstream pipelines and reports.

A change in the statistical properties of input data over time relative to the data distribution the model was trained on, which degrades machine learning model performance if the model is not retrained to reflect the new distribution. In healthcare predictive models, data drift occurs when changes in coding practices, patient population demographics, care delivery patterns, or payer policy changes alter the distribution of input features such as diagnosis codes, utilization rates, or pharmacy claims in ways that invalidate the original model assumptions.

The process of encrypting data stored in databases, file systems, and cloud object storage to prevent unauthorized access to healthcare data in the event of physical media theft, unauthorized storage access, or cloud infrastructure breach. HIPAA technical safeguards require encryption of ePHI at rest as an addressable implementation specification, and all major cloud healthcare data platforms enforce encryption using AES-256 or equivalent standards for data stored in Snowflake, BigQuery, Databricks, and S3.