Fast Healthcare Interoperability Resources
fhirDefinition
ISO-11179 Definition
Fast Healthcare Interoperability Resources (FHIR) is a modern healthcare data exchange standard developed and maintained by Health Level Seven International (HL7). FHIR defines a collection of modular data objects called "resources" — such as Patient, Observation, Condition, Encounter, and MedicationRequest — each with a standardized JSON or XML schema and a RESTful API access pattern. Unlike earlier HL7 standards, FHIR was designed from the ground up to work with web technologies, making it accessible to developers using standard HTTP clients and JSON parsers without specialized EDI tooling.
FHIR is central to healthcare interoperability regulation in the United States. The CMS Interoperability and Patient Access Final Rule (CMS-9115-F) and the ONC 21st Century Cures Act Final Rule both mandate FHIR R4 API access for Medicare Advantage, Medicaid, CHIP, and federally-facilitated exchange plans. Payers must expose patient claims data, clinical data, and formulary information through FHIR APIs, making FHIR proficiency essential for any data engineer working at a health plan or healthcare IT vendor.
Healthcare data engineers encounter FHIR in two primary contexts: ingesting FHIR-formatted data from EHRs and payer APIs into analytical platforms, and building FHIR-compliant APIs to expose data to authorized applications. In Snowflake or Databricks, FHIR resources typically arrive as semi-structured JSON stored in VARIANT columns, requiring transformation pipelines that flatten nested elements such as coding arrays, extension blocks, and contained resources into normalized analytical tables. Key engineering tasks include mapping FHIR Observation resources to laboratory result fact tables, transforming FHIR Condition resources into diagnosis dimension tables, and handling the FHIR reference pattern (e.g., "Patient/12345") to resolve cross-resource foreign keys.
Related standards include ICD-10-CM for diagnosis coding within FHIR Condition resources, LOINC for FHIR Observation codes, SNOMED CT for clinical terminology, and US Core Implementation Guide profiles that constrain FHIR resources for the US healthcare market.
Standard Abbreviation
fhir
Category
Production DDL — DIM_SYSTEM
CREATE OR REPLACE TABLE DIM_SYSTEM (
sys_key INTEGER NOT NULL -- surrogate key,
sys_id VARCHAR(50) NOT NULL -- system identifier,
sys_nm VARCHAR(200) NOT NULL -- system name,
sys_type_cd VARCHAR(50) -- system type code,
sys_vrsn VARCHAR(50) -- system version,
vndr_nm VARCHAR(200) -- vendor name,
intfc_type_cd VARCHAR(50) -- interface type code,
intfc_proto_cd VARCHAR(20) -- interface protocol,
env_cd VARCHAR(20) -- environment code,
host_nm VARCHAR(200) -- hostname,
ip_addr VARCHAR(45) -- IP address,
sts_cd VARCHAR(20) -- status code,
eff_dt DATE NOT NULL -- effective date,
exp_dt DATE -- expiration date,
rec_creat_dt TIMESTAMP NOT NULL -- record created date
);
Standard Snowflake DDL for the canonical technology table. Convert to BigQuery or Databricks →
Why This Term Matters
Healthcare data terminology is foundational for any data engineer working in this industry. Precise understanding of standard terms enables accurate schema design, reduces downstream data quality issues, and ensures pipelines meet the regulatory and interoperability requirements imposed by HIPAA, HL7 FHIR, and CMS reporting frameworks. Without this foundation, even technically well-built pipelines produce data that fails validation when it reaches payers or regulators.
Related Content
Looking for more healthcare terms?
Browse our complete library of 100,000+ standardized healthcare data terms
Browse All Terms