Technology

Unique system-generated key assigned to a clinical evaluation or diagnostic assessment record within EHR and care management systems. Enables tracking of patient assessments, screening results, and clinical findings across care episodes, quality reporting, and utilization management workflows.

A software and data architecture pattern in which system components communicate by producing and consuming events — discrete records of something that happened — through a message broker such as Apache Kafka, AWS EventBridge, or Azure Event Hubs, enabling real-time data processing and loose coupling between systems. In healthcare data platforms, event-driven architecture enables real-time processing of ADT events for bed management, lab result streaming for clinical alerting, and claims status change notifications for revenue cycle workflows.

Unique system-generated key assigned to a patient experience or satisfaction survey record within healthcare quality and member engagement systems. Supports tracking of patient-reported perceptions of care quality across CAHPS reporting, value-based care programs, and member experience analytics.

A centralized repository that stores, manages, and serves machine learning features — transformed and aggregated data representations derived from raw data — for both model training and real-time inference, ensuring consistency between training and production feature values. In healthcare machine learning platforms, a feature store enables consistent computation of member risk features such as chronic condition counts, recent utilization history, and medication adherence scores that feed predictive models for readmission risk, disease progression, and care management targeting.

A machine learning approach that trains models across multiple decentralized data sources — such as different health systems or payer databases — without sharing raw data between organizations, instead sharing only model parameters or gradients. Federated learning enables healthcare organizations to collaboratively build more accurate predictive models using larger effective training populations while maintaining data privacy and eliminating the regulatory and contractual complexity of centralizing PHI from multiple organizations.

Unique system-generated key assigned to a clinical finding record representing an observed or measured result from a patient assessment within EHR and clinical data systems. Enables tracking of diagnostic findings, abnormal results, and clinical observations across care documentation and quality reporting workflows.

A column in a healthcare data table that references the primary key of another table to establish a relationship between the two tables. Used to enforce referential integrity in normalized and dimensional data models. Examples include member_key in a claims table referencing the member dimension table.

Unique system-generated key assigned to a medication or treatment frequency record within pharmacy and clinical management systems. Supports tracking of administration schedules and dosing intervals across prescription management, medication adherence monitoring, and clinical decision support workflows.

A data pipeline pattern that truncates and completely reloads a target table from the source on each execution, guaranteeing accuracy at the cost of higher compute and I/O compared to incremental loading. Full refreshes are appropriate in healthcare data engineering for small reference tables such as ICD-10 code sets, provider taxonomy codes, and ZIP-to-county crosswalks where the entire dataset is small enough to reload efficiently and source deletion semantics make incremental approaches complex.

Unique system-generated key assigned to a gastroenterology specialty record or encounter within clinical and claims systems. Enables tracking of digestive system diagnoses, endoscopic procedures, and specialist referrals across care management platforms, utilization reporting, and specialty network workflows.

Unique system-generated key assigned to a geriatric specialty record or encounter within clinical and care management systems. Enables tracking of elderly patient care plans, specialist visits, and age-related condition management across long-term care, population health, and utilization reporting workflows.

The third and final layer in a medallion architecture containing business-level aggregated, modeled, and analytics-ready datasets derived from the silver layer. In healthcare data platforms, the gold layer contains dimension tables such as DIM_MEMBER and DIM_PROVIDER, fact tables such as FACT_CLAIM_HEADER, and pre-aggregated summary datasets used by BI tools, dashboards, and data science teams for reporting and analysis.

Unique system-generated key assigned to a benefit group or employer group record within member enrollment and insurance administration systems. Links members to their specific plan group for eligibility verification, premium billing, coverage determination, and group-level utilization reporting.

Unique system-generated key assigned to the financially responsible party for a patient account within healthcare billing and revenue cycle systems. Enables tracking of guarantor payment obligations, statement delivery, and account balances across patient financial services and accounts receivable workflows.

Unique surrogate key assigned by the source system to a clinical practice guideline record. Enables consistent cross-system tracking of evidence-based care recommendations used in quality programs, clinical decision support, and care management protocol alignment.

A cryptographic hash value generated from one or more business key columns used as a surrogate key in Data Vault 2.0 healthcare data models. Typically generated using MD5 or SHA-256 algorithms. Enables consistent key generation across distributed systems and supports parallel loading of hub and link tables.

Unique surrogate key assigned by the source system to an HCPCS procedure code record. Used in medical claims processing and billing systems to track CMS-standardized codes representing services, supplies, and equipment submitted on professional and outpatient facility claims.

Health information technology encompasses the electronic systems, infrastructure, and standards used to store, manage, exchange, and analyze healthcare data across clinical, administrative, and operational settings. HIT includes electronic health record systems, health information exchanges, clinical decision support tools, patient portals, medical imaging systems, and interoperability frameworks such as HL7 FHIR. In healthcare data architecture, HIT serves as the source layer for data pipelines feeding analytics platforms, requiring data engineers to understand EHR data models, API integration patterns, and regulatory frameworks including HIPAA, the 21st Century Cures Act information blocking rules, and ONC certification requirements.

A managed service layer that sits between external application consumers and internal healthcare data services, handling authentication, authorization, rate limiting, request routing, protocol translation, and audit logging for API traffic. Healthcare API gateways enforce HIPAA-compliant access controls, log all PHI-touching API calls for audit purposes, and provide centralized management of FHIR, REST, and SOAP service endpoints across a healthcare organization integration architecture.

The set of technical controls, configurations, audit mechanisms, and governance processes required to operate healthcare data workloads on cloud platforms in compliance with HIPAA, HITRUST, SOC 2, FedRAMP, and state-specific health data regulations. Healthcare cloud compliance requires BAAs with cloud providers, encryption of ePHI at rest and in transit, access logging, vulnerability management, and regular compliance assessments to maintain certification status for cloud environments processing protected health information.