Heartland · FHIR

FHIR R4 · v0.3.0 draft · CC‑BY 4.0

Structured data for heart failure care where there’s no cardiologist.

A draft FHIR R4 specification for structured HEARTLAND examples. Explicit risk-input weights, complete-response checks, and synthetic identifiers support technical evaluation. Vendor interoperability and clinical validation are not established.

For professional educational use, not direct patient care. Examples are synthetic. Do not enter real patient information. Software v0.3.0 is archived; its draft and experimental status is unchanged.

Why this IG exists

The protocol is published. The EHR pieces are not. This IG is the bridge.

10

weighted criteria

Explicit true-answer weights; missing is not false.

0–18

heuristic points

A proposed framework pending validation, not an outcome probability.

R4

FHIR 4.0.1

Draft profiles and examples for reproducible technical evaluation.

A structured resource is only one part of an implementation. Compilation, terminology checks, cross-resource consistency and external EHR testing are separate checks. None proves clinical benefit.

What’s inside

Eight protocol modules, selected draft FHIR structures.

Six profiles, seven extensions, five code systems, five value sets, three questionnaires and five synthetic examples, plus the IG manifest. Newer workflow coverage remains incomplete; the cards distinguish existing structures from planned work.

Risk stratification

Ten weighted criteria, explicit true-answer weights and a complete Boolean response profile; missing inputs are not zero.

RiskAssessment + Questionnaire

Draft structure in v0.3.0

Medication planning

A draft care plan aligned with the Toolkit candidate. Tier does not prescribe treatment timing; a plan is not an authorized medication order.

CarePlan profile

Draft structure in v0.3.0

Monitoring route

Digital and analog track codes record communication context; they do not prove contact, delivery or equivalent outcomes.

MonitoringTrack code system

Draft structure in v0.3.0

Discharge transitions

Eight education domains at every tier, plus a workflow resource map. The map is not an operational exporter or proof of completed care.

CarePlan + workflow mapping

Draft structure in v0.3.0

Remote monitoring

Draft body-weight, BP and oxygen-saturation observations. A single reading does not prove a change, alert or clinical response.

Observation profile + LOINC

Draft structure in v0.3.0

Comorbidity context

Patient context plus an opaque synthetic county identifier; the identifier is not a real county GEOID.

Patient and synthetic identifier

Draft structure in v0.3.0

Primary-care linkage

Warm-handoff protocol: roles, triggers, and shared documentation between discharge and longitudinal primary care.

Phase 2

Not yet represented

Implementation tier

Facility capacity questionnaire and tier codes; no validated automatic assignment or permission to reduce clinical requirements.

FacilityTierQuestionnaire + ext.

Draft structure in v0.3.0

Current state

Where the IG stands today.

v0.3.0 is an archived technical draft, not an assertion of deployment readiness or clinical approval. Tier and education content is aligned with the Toolkit candidate; operational exchange and external EHR validation remain separate checks.

Cureus articlePublished article; separate from software validation
HEARTLAND ToolkitV3.3 published; V3.4 release candidate
FHIR IGv0.3.0 archived release — draft and experimental
Zenodo archivesSoftware v0.3.0 archived; technical report 1.0 remains a separate historical work
Pilot site EHR validationPhase 3 — not yet started

Explore the archived draft files

Version 0.3.0 is draft and experimental, for technical evaluation with synthetic examples. Its source release is archived on Zenodo; publication is not clinical or EHR validation. R4B conversions are not included.

The Publisher QA report is included. The standalone validator separately reports unresolved tooling annotations in the IG manifest; see the documented limitation. Neither check establishes clinical validation or vendor interoperability.