HEARTLAND Protocol FHIR Implementation Guide
0.3.0 -
HEARTLAND Protocol FHIR Implementation Guide
0.3.0 -
HEARTLAND FHIR candidate 0.3.0 — draft, experimental R4 4.0.1 reference. Prepared for technical review; not evidence of clinical validation or vendor interoperability.
| Official URL: https://fhir.heartlandprotocol.org/ImplementationGuide/heartland.fhir.us.protocol | Version: 0.3.0 | |||
| Draft as of 2026-09-29 | Computable Name: HeartlandProtocolIG | |||
Candidate 0.3.0 — draft, experimental FHIR R4 resources.
An educational implementation-support specification for structured, synthetic HEARTLAND examples. This is not proof of clinical validation, vendor interoperability, or full Toolkit V3.4 workflow coverage.
The public landing page at https://fhir.heartlandprotocol.org and this generated reference have distinct build and publication steps. The root landing page is not a version-pinned copy of this guide.
| Field | Value |
|---|---|
| FHIR release | R4 4.0.1 |
| Dependency | US Core 6.1.0 |
| Canonical URL | https://fhir.heartlandprotocol.org |
| Candidate version | 0.3.0 |
| Conformance status | Draft and experimental |
Depending on US Core is not a claim that every profile conforms to it. Source compilation, structural validation, terminology checks, cross-resource tests and external EHR testing are distinct checks.
This Implementation Guide is an educational implementation-support resource for healthcare professionals. It does not provide medical diagnoses, treatment recommendations for individual patients, or replace clinical judgment. Not intended for direct patient care. For professional use only.
The HEARTLAND Risk Stratification Framework is proposed pending validation and has not been validated against clinical outcomes. Bundled examples are synthetic; no real patient information should be entered into demonstrations.
Vicky Muller Ferreira, MD · ORCID 0009-0009-1099-5690 · vickymuller@heartlandprotocol.org.
Narrative and generated resources: CC-BY 4.0. Build tooling: MIT.
This publication includes IP covered under the following statements.
| IG | Package | FHIR | Comment |
|---|---|---|---|
  HEARTLAND Protocol FHIR Implementation Guide | heartland.fhir.us.protocol#0.3.0 | R4 | |
 HL7 Terminology (THO) | hl7.terminology.r4#7.4.0 | R4 | Automatically added as a dependency - all IGs depend on HL7 Terminology |
| FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#5.3.0 | R4 | Automatically added as a dependency - all IGs depend on the HL7 Extension Pack |
 US Core Implementation Guide | hl7.fhir.us.core#6.1.0 | R4 | |
 HL7 Terminology (THO) | hl7.terminology.r4#5.0.0 | R4 | |
| FHIR Extensions Pack | hl7.fhir.uv.extensions.r4#1.0.0 | R4 | |
| Bulk Data Access IG | hl7.fhir.uv.bulkdata#2.0.0 | R4 | |
| SMART App Launch | hl7.fhir.uv.smart-app-launch#2.1.0 | R4 | |
| VSAC | us.nlm.vsac#0.11.0 | R4 | |
| Structured Data Capture | hl7.fhir.uv.sdc#3.0.0 | R4 | |
| PHINVads | us.cdc.phinvads#0.12.0 | R4 | |
 IHE FormatCode Vocabulary | ihe.formatcode.fhir#1.1.0 | R4 | |
 FHIR Tooling Extensions IG | hl7.fhir.uv.tools.r4#1.1.2 | R4 | for example references |
Package hl7.fhir.uv.extensions.r4#5.3.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sat, May 16, 2026 18:32+1000+10:00) |
Package hl7.fhir.uv.extensions.r4#1.0.0 This IG defines the global extensions - the ones defined for everyone. These extensions are always in scope wherever FHIR is being used (built Sun, Mar 26, 2023 08:46+1100+11:00) |
Package hl7.fhir.uv.bulkdata#2.0.0 FHIR based approach for exporting large data sets from a FHIR server to a client application (built Fri, Nov 26, 2021 05:56+1100+11:00) |
Package hl7.fhir.uv.sdc#3.0.0 The SDC specification provides an infrastructure to standardize the capture and expanded use of patient-level data collected within an EHR. |
Package ihe.formatcode.fhir#1.1.0 Implementation Guide for IHE defined FormatCode vocabulary. (built Thu, Feb 24, 2022 16:55-0600-06:00) |
Package hl7.fhir.us.core#6.1.0 The US Core Implementation Guide is based on FHIR Version R4 and defines the minimum conformance requirements for accessing patient data. The Argonaut pilot implementations, ONC 2015 Edition Common Clinical Data Set (CCDS), and ONC U.S. Core Data for Interoperability (USCDI) v1 provided the requirements for this guide. The prior Argonaut search and vocabulary requirements, based on FHIR DSTU2, are updated in this guide to support FHIR Version R4. This guide was used as the basis for further testing and guidance by the Argonaut Project Team to provide additional content and guidance specific to Data Query Access for purpose of ONC Certification testing. These profiles are the foundation for future US Realm FHIR implementation guides. In addition to Argonaut, they are used by DAF-Research, QI-Core, and CIMI. Under the guidance of HL7 and the HL7 US Realm Steering Committee, the content will expand in future versions to meet the needs specific to the US Realm. These requirements were originally developed, balloted, and published in FHIR DSTU2 as part of the Office of the National Coordinator for Health Information Technology (ONC) sponsored Data Access Framework (DAF) project. For more information on how DAF became US Core see the US Core change notes. (built Fri, Jun 30, 2023 14:02+0000+00:00) |
Package hl7.fhir.uv.tools.r4#1.1.2 This IG defines the extensions that the tools use internally. Some of these extensions are content that are being evaluated for elevation into the main spec, and others are tooling concerns (built Tue, Mar 24, 2026 11:13+1100+11:00) |
This candidate's evaluated contract is FHIR R4 4.0.1 only. The Publisher can automatically produce R4B conversions; these are not evaluated deliverables and are not included in the prepared website downloads. Automatic conversion is not evidence of R4B interoperability.
There are no Global profiles defined