HEARTLAND Protocol FHIR Implementation Guide
0.3.0 - United States of America flag

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.

Extension: HEARTLAND Monitoring Track Assignment (Experimental)

Official URL: https://fhir.heartlandprotocol.org/StructureDefinition/heartland-monitoring-track-ext Version: 0.3.0
Draft as of 2026-09-29 Computable Name: HeartlandMonitoringTrackExtension

Records a documented CarePlan monitoring route: Track A (digital) or Track B (analog, telephone/paper). Access, patient preference and the supported local plan inform the choice; facility tier alone does not select a route. The code does not prove contact, completed monitoring or equivalent outcomes, and does not change clinical requirements. No third hybrid code is defined.

Context of Use

    This extension may be used on the following element(s)

Usage info

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Extension Content

Description of Profiles, Differentials, Snapshots, and their representations.

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension HEARTLAND Monitoring Track Assignment
... extension 0..0 Extension
... url 1..1 uri "https://fhir.heartlandprotocol.org/StructureDefinition/heartland-monitoring-track-ext"
... value[x] 1..1 CodeableConcept Value of extension
Binding: HEARTLAND Monitoring Track Value Set (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Extension.value[x] Base required HEARTLAND Monitoring Track Value Set 📦0.3.0 This IG
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension HEARTLAND Monitoring Track Assignment
... id 0..1 string Unique id for inter-element referencing
... extension 0..0 Extension
Slice: Unordered, Open by value:url
... url 1..1 uri "https://fhir.heartlandprotocol.org/StructureDefinition/heartland-monitoring-track-ext"

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Extension.value[x] Base required HEARTLAND Monitoring Track Value Set 📦0.3.0 This IG

Constraints

Id Grade Path(s) Description Expression

Summary

Simple Extension with the type CodeableConcept: Records a documented CarePlan monitoring route: Track A (digital) or Track B (analog, telephone/paper). Access, patient preference and the supported local plan inform the choice; facility tier alone does not select a route. The code does not prove contact, completed monitoring or equivalent outcomes, and does not change clinical requirements. No third hybrid code is defined.

Differential ViewDifferential View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension HEARTLAND Monitoring Track Assignment
... extension 0..0 Extension
... url 1..1 uri "https://fhir.heartlandprotocol.org/StructureDefinition/heartland-monitoring-track-ext"
... value[x] 1..1 CodeableConcept Value of extension
Binding: HEARTLAND Monitoring Track Value Set (required)

doco Documentation for this format

Terminology Bindings (Differential)

Path Status Usage ValueSet Version Source
Extension.value[x] Base required HEARTLAND Monitoring Track Value Set 📦0.3.0 This IG

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Extension 0..* Extension HEARTLAND Monitoring Track Assignment
... id 0..1 string Unique id for inter-element referencing
... extension 0..0 Extension
Slice: Unordered, Open by value:url
... url 1..1 uri "https://fhir.heartlandprotocol.org/StructureDefinition/heartland-monitoring-track-ext"

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Extension.value[x] Base required HEARTLAND Monitoring Track Value Set 📦0.3.0 This IG

Constraints

Id Grade Path(s) Description Expression

Summary

Simple Extension with the type CodeableConcept: Records a documented CarePlan monitoring route: Track A (digital) or Track B (analog, telephone/paper). Access, patient preference and the supported local plan inform the choice; facility tier alone does not select a route. The code does not prove contact, completed monitoring or equivalent outcomes, and does not change clinical requirements. No third hybrid code is defined.

 

Other representations of profile: CSV, Excel, Schematron