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.

• Narrative Content
• XML
• JSON
• TTL

: HEARTLAND Monitoring Track

Draft as of 2026-09-29

Raw xml | Download

<CodeSystem xmlns="http://hl7.org/fhir">
  <id value="heartland-monitoring-track"/>
  <language value="en"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: CodeSystem heartland-monitoring-track</b></p><a name="heartland-monitoring-track"> </a><a name="hcheartland-monitoring-track"> </a><p>This case-sensitive code system <code>https://fhir.heartlandprotocol.org/CodeSystem/heartland-monitoring-track</code> defines the following codes:</p><table class="codes"><tr><td style="white-space:nowrap"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td style="white-space:nowrap">digital-track-a<a name="heartland-monitoring-track-digital-track-a"> </a></td><td>Digital Track A</td><td>A planned digital route, such as app-based entries. This code alone does not assert Bluetooth devices, automatic transmission or reliable connectivity.</td></tr><tr><td style="white-space:nowrap">analog-track-b<a name="heartland-monitoring-track-analog-track-b"> </a></td><td>Analog Track B</td><td>A planned analog route, such as telephone contact and a paper diary. This code alone does not assert telephone access, staff entry, successful contact or review.</td></tr></table></div>
  </text>
  <url
       value="https://fhir.heartlandprotocol.org/CodeSystem/heartland-monitoring-track"/>
  <version value="0.3.0"/>
  <name value="HeartlandMonitoringTrack"/>
  <title value="HEARTLAND Monitoring Track"/>
  <status value="draft"/>
  <experimental value="true"/>
  <date value="2026-09-29T19:00:36-04:00"/>
  <publisher value="Vicky Muller Ferreira, MD"/>
  <contact>
    <name value="Vicky Muller Ferreira, MD"/>
    <telecom>
      <system value="url"/>
      <value value="https://heartlandprotocol.org"/>
    </telecom>
    <telecom>
      <system value="email"/>
      <value value="vickymuller@heartlandprotocol.org"/>
    </telecom>
  </contact>
  <contact>
    <name value="Vicky Muller Ferreira, MD"/>
    <telecom>
      <system value="email"/>
      <value value="vickymuller@heartlandprotocol.org"/>
      <use value="work"/>
    </telecom>
    <telecom>
      <system value="url"/>
      <value value="https://heartlandprotocol.org"/>
    </telecom>
  </contact>
  <description
               value="Documented monitoring routes with stable Track A and Track B codes. A route does not establish equivalent outcomes, successful contact, device availability or completed monitoring. Clinical requirements are not reduced by the route; access, preference and the supported local plan require separate documentation."/>
  <jurisdiction>
    <coding>
      <system value="urn:iso:std:iso:3166"/>
      <code value="US"/>
    </coding>
  </jurisdiction>
  <copyright value="CC-BY 4.0"/>
  <caseSensitive value="true"/>
  <content value="complete"/>
  <count value="2"/>
  <concept>
    <code value="digital-track-a"/>
    <display value="Digital Track A"/>
    <definition
                value="A planned digital route, such as app-based entries. This code alone does not assert Bluetooth devices, automatic transmission or reliable connectivity."/>
  </concept>
  <concept>
    <code value="analog-track-b"/>
    <display value="Analog Track B"/>
    <definition
                value="A planned analog route, such as telephone contact and a paper diary. This code alone does not assert telephone access, staff entry, successful contact or review."/>
  </concept>
</CodeSystem>