Personal Health Device Implementation Guide
3.0.0-ballot - STU 3 Ballot Global (Whole world)

Personal Health Device Implementation Guide, published by HL7 International / Devices. This guide is not an authorized publication; it is the continuous build for version 3.0.0-ballot built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phd/ and changes regularly. See the Directory of published versions

: Narrative Conformance Statements

Page standards status: Trial-use Maturity Level: 2

Raw xml | Download


<Requirements xmlns="http://hl7.org/fhir">
  <id value="fromNarrative"/>
  <language value="en"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: Requirements fromNarrative</b></p><a name="fromNarrative"> </a><a name="hcfromNarrative"> </a><table class="grid"><tr><td><b><a name="1"> </a></b>1</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>The PHG SHOULD specify a sufficiently selective conditional-create criterion so that at most one matching resource is found on the server.</p>
</div></td></tr><tr><td><b><a name="2"> </a></b>2</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>When an equivalent UCUM code is known, this UCUM code SHALL be used.</p>
</div></td></tr><tr><td><b><a name="3"> </a></b>3</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>An implementation SHALL use the MDC code if it does not know the UCUM code for the given unit.</p>
</div></td></tr><tr><td><b><a name="4"> </a></b>4</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>The converted effective[x] SHALL retain fractional-second precision consistent with the PHD's tick resolution, so that time differences between observations are preserved.</p>
</div></td></tr><tr><td><b><a name="5"> </a></b>5</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>A derived RR interval Observation SHOULD reference the source ECG waveform Observation using Observation.derivedFrom.</p>
</div></td></tr><tr><td><b><a name="6"> </a></b>6</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>The MDC code SHALL be present in a coding element.</p>
</div></td></tr><tr><td><b><a name="7"> </a></b>7</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Because PHDs often have unreliably set clocks, a PHD that generates measurements with timestamps SHOULD provide a means for the PHG to determine the PHD's current time and clock status information, such as its synchronization state.</p>
</div></td></tr><tr><td><b><a name="8"> </a></b>8</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>This measurement SHOULD contain a derived-from reference pointing to the measurement containing the glucose concentration.</p>
</div></td></tr><tr><td><b><a name="9"> </a></b>9</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>For a PHD, Device.conformsTo SHALL contain at least one MDC specialization entry.</p>
</div></td></tr><tr><td><b><a name="10"> </a></b>10</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>PHDs SHOULD use the unchanged timestamp of a generated observation as received from the PHD.</p>
</div></td></tr><tr><td><b><a name="11"> </a></b>11</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>PHGs compliant with this IG SHOULD implement this identifier as specified to ensure this scheme works across all compliant gateways.</p>
</div></td></tr><tr><td><b><a name="12"> </a></b>12</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>For device settings known to the PHG, Observation.subject SHOULD point to the PHD.</p>
</div></td></tr><tr><td><b><a name="13"> </a></b>13</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD-NOT">SHOULD-NOT</a></td><td><div><p>For Coincident Timestamp Observations, Observation.performer SHOULD NOT be provided.</p>
</div></td></tr><tr><td><b><a name="14"> </a></b>14</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Observations whose timestamps are neither from the PHD's current timeline nor from a timeline synchronized with an external time source SHOULD be discarded, since there is no way to give them a correct timestamp.</p>
</div></td></tr><tr><td><b><a name="15"> </a></b>15</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>When the PHG modifies an Observation's timestamp as received from the PHD, it SHALL also generate a Coincident Timestamp Observation that records how the Observation.effective[x] element is generated.</p>
</div></td></tr><tr><td><b><a name="16"> </a></b>16</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>When uploading to a FHIR server, the gateway SHOULD report the group observation with a hasMember reference to all member Observations.</p>
</div></td></tr><tr><td><b><a name="17"> </a></b>17</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>In FHIR, the session Observation SHOULD have hasMember references to all observations that are part of the session.</p>
</div></td></tr><tr><td><b><a name="18"> </a></b>18</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>PHGs SHALL include a category element with a fixed coding as specified by the profile.</p>
</div></td></tr><tr><td><b><a name="19"> </a></b>19</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>Vital-sign Observations SHOULD include a category element as defined by the Vital Signs profile.</p>
</div></td></tr><tr><td><b><a name="20"> </a></b>20</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>When encoding numeric Observation quantities in FHIR, the PHG SHALL follow the precision indicated by the PHD's IEEE 11073 FLOAT or SFLOAT encoding.</p>
</div></td></tr><tr><td><b><a name="21"> </a></b>21</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>However, if the PHD does not report a System-identifier, which may happen if one needs to map non-certified and/or proprietary devices, a transport address SHOULD be reported.</p>
</div></td></tr><tr><td><b><a name="22"> </a></b>22</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>When a PHG encounters such a device it SHALL provide a transport address as a means of uniquely identifying the PHD.</p>
</div></td></tr><tr><td><b><a name="23"> </a></b>23</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>The Accuracy attribute SHALL be reported if the PHD provides it.</p>
</div></td></tr><tr><td><b><a name="24"> </a></b>24</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>Measurement-Confidence-95 SHALL be reported if the PHD provides it.</p>
</div></td></tr><tr><td><b><a name="25"> </a></b>25</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>There SHALL be one coding element using the MDC coding system.</p>
</div></td></tr><tr><td><b><a name="26"> </a></b>26</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>If the measurement is a vital sign, an additional coding element SHALL use a LOINC vital-sign code.</p>
</div></td></tr><tr><td><b><a name="27"> </a></b>27</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>The PHG SHALL use a Patient.identifier supplied by the server when one is provided.</p>
</div></td></tr><tr><td><b><a name="28"> </a></b>28</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>If the server does not provide an identifier, the PHG SHALL generate an implementation-dependent identifier whose value is unique within its assigning system.</p>
</div></td></tr><tr><td><b><a name="29"> </a></b>29</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>The type for a PHG-generated identifier SHOULD use a suitable code from the HL7 v2-0203 coding system.</p>
</div></td></tr><tr><td><b><a name="30"> </a></b>30</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>PHG implementers that generate device alerts SHOULD follow the two alert-generation pathways — threshold/limit alerts on numeric observations and device/sensor status-bit alerts — described in the PhdDeviceAlert profile.</p>
</div></td></tr><tr><td><b><a name="31"> </a></b>31</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHALL">SHALL</a></td><td><div><p>Uploads generated by PHGs compliant to this IG SHALL use the mapping defined by this implementation guide when transforming PHD data to FHIR resources.</p>
</div></td></tr><tr><td><b><a name="32"> </a></b>32</td><td><a href="http://hl7.org/fhir/6.0.0-ballot5/codesystem-conformance-expectation.html#conformance-expectation-SHOULD">SHOULD</a></td><td><div><p>The PHG SHOULD implement a duplication detection mechanism and filter out any observations that have already been uploaded.</p>
</div></td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="dev"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="2">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/phd/ImplementationGuide/hl7.fhir.uv.phd"/>
      </extension>
    </valueInteger>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/phd/ImplementationGuide/hl7.fhir.uv.phd"/>
      </extension>
    </valueCode>
  </extension>
  <url value="http://hl7.org/fhir/uv/phd/Requirements/fromNarrative"/>
  <identifier>
    <system value="urn:ietf:rfc:3986"/>
    <value value="urn:oid:2.16.840.1.113883.4.642.40.73.36.1"/>
  </identifier>
  <version value="3.0.0-ballot"/>
  <name value="FromNarrative"/>
  <title value="Narrative Conformance Statements"/>
  <status value="active"/>
  <experimental value="false"/>
  <date value="2026-11-20T18:02:18+00:00"/>
  <publisher value="HL7 International / Devices"/>
  <contact>
    <name value="HL7 International / Devices"/>
    <telecom>
      <system value="url"/>
      <value value="http://www.hl7.org/Special/committees/healthcaredevices"/>
    </telecom>
  </contact>
  <description
               value="Conformance statements found throughout the narrative of the IG consolidated into this computable resource for traceability purposes"/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
    </coding>
  </jurisdiction>
  <statement>
    <key value="1"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="The PHG SHOULD specify a sufficiently selective conditional-create criterion so that at most one matching resource is found on the server."/>
  </statement>
  <statement>
    <key value="2"/>
    <conformance value="SHALL"/>
    <requirement
                 value="When an equivalent UCUM code is known, this UCUM code SHALL be used."/>
  </statement>
  <statement>
    <key value="3"/>
    <conformance value="SHALL"/>
    <requirement
                 value="An implementation SHALL use the MDC code if it does not know the UCUM code for the given unit."/>
  </statement>
  <statement>
    <key value="4"/>
    <conformance value="SHALL"/>
    <requirement
                 value="The converted effective[x] SHALL retain fractional-second precision consistent with the PHD's tick resolution, so that time differences between observations are preserved."/>
  </statement>
  <statement>
    <key value="5"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="A derived RR interval Observation SHOULD reference the source ECG waveform Observation using Observation.derivedFrom."/>
  </statement>
  <statement>
    <key value="6"/>
    <conformance value="SHALL"/>
    <requirement value="The MDC code SHALL be present in a coding element."/>
  </statement>
  <statement>
    <key value="7"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Because PHDs often have unreliably set clocks, a PHD that generates measurements with timestamps SHOULD provide a means for the PHG to determine the PHD's current time and clock status information, such as its synchronization state."/>
  </statement>
  <statement>
    <key value="8"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="This measurement SHOULD contain a derived-from reference pointing to the measurement containing the glucose concentration."/>
  </statement>
  <statement>
    <key value="9"/>
    <conformance value="SHALL"/>
    <requirement
                 value="For a PHD, Device.conformsTo SHALL contain at least one MDC specialization entry."/>
  </statement>
  <statement>
    <key value="10"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="PHDs SHOULD use the unchanged timestamp of a generated observation as received from the PHD."/>
  </statement>
  <statement>
    <key value="11"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="PHGs compliant with this IG SHOULD implement this identifier as specified to ensure this scheme works across all compliant gateways."/>
  </statement>
  <statement>
    <key value="12"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="For device settings known to the PHG, Observation.subject SHOULD point to the PHD."/>
  </statement>
  <statement>
    <key value="13"/>
    <conformance value="SHOULD-NOT"/>
    <requirement
                 value="For Coincident Timestamp Observations, Observation.performer SHOULD NOT be provided."/>
  </statement>
  <statement>
    <key value="14"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Observations whose timestamps are neither from the PHD's current timeline nor from a timeline synchronized with an external time source SHOULD be discarded, since there is no way to give them a correct timestamp."/>
  </statement>
  <statement>
    <key value="15"/>
    <conformance value="SHALL"/>
    <requirement
                 value="When the PHG modifies an Observation's timestamp as received from the PHD, it SHALL also generate a Coincident Timestamp Observation that records how the Observation.effective[x] element is generated."/>
  </statement>
  <statement>
    <key value="16"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="When uploading to a FHIR server, the gateway SHOULD report the group observation with a hasMember reference to all member Observations."/>
  </statement>
  <statement>
    <key value="17"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="In FHIR, the session Observation SHOULD have hasMember references to all observations that are part of the session."/>
  </statement>
  <statement>
    <key value="18"/>
    <conformance value="SHALL"/>
    <requirement
                 value="PHGs SHALL include a category element with a fixed coding as specified by the profile."/>
  </statement>
  <statement>
    <key value="19"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="Vital-sign Observations SHOULD include a category element as defined by the Vital Signs profile."/>
  </statement>
  <statement>
    <key value="20"/>
    <conformance value="SHALL"/>
    <requirement
                 value="When encoding numeric Observation quantities in FHIR, the PHG SHALL follow the precision indicated by the PHD's IEEE 11073 FLOAT or SFLOAT encoding."/>
  </statement>
  <statement>
    <key value="21"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="However, if the PHD does not report a System-identifier, which may happen if one needs to map non-certified and/or proprietary devices, a transport address SHOULD be reported."/>
  </statement>
  <statement>
    <key value="22"/>
    <conformance value="SHALL"/>
    <requirement
                 value="When a PHG encounters such a device it SHALL provide a transport address as a means of uniquely identifying the PHD."/>
  </statement>
  <statement>
    <key value="23"/>
    <conformance value="SHALL"/>
    <requirement
                 value="The Accuracy attribute SHALL be reported if the PHD provides it."/>
  </statement>
  <statement>
    <key value="24"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Measurement-Confidence-95 SHALL be reported if the PHD provides it."/>
  </statement>
  <statement>
    <key value="25"/>
    <conformance value="SHALL"/>
    <requirement
                 value="There SHALL be one coding element using the MDC coding system."/>
  </statement>
  <statement>
    <key value="26"/>
    <conformance value="SHALL"/>
    <requirement
                 value="If the measurement is a vital sign, an additional coding element SHALL use a LOINC vital-sign code."/>
  </statement>
  <statement>
    <key value="27"/>
    <conformance value="SHALL"/>
    <requirement
                 value="The PHG SHALL use a Patient.identifier supplied by the server when one is provided."/>
  </statement>
  <statement>
    <key value="28"/>
    <conformance value="SHALL"/>
    <requirement
                 value="If the server does not provide an identifier, the PHG SHALL generate an implementation-dependent identifier whose value is unique within its assigning system."/>
  </statement>
  <statement>
    <key value="29"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="The type for a PHG-generated identifier SHOULD use a suitable code from the HL7 v2-0203 coding system."/>
  </statement>
  <statement>
    <key value="30"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="PHG implementers that generate device alerts SHOULD follow the two alert-generation pathways — threshold/limit alerts on numeric observations and device/sensor status-bit alerts — described in the PhdDeviceAlert profile."/>
  </statement>
  <statement>
    <key value="31"/>
    <conformance value="SHALL"/>
    <requirement
                 value="Uploads generated by PHGs compliant to this IG SHALL use the mapping defined by this implementation guide when transforming PHD data to FHIR resources."/>
  </statement>
  <statement>
    <key value="32"/>
    <conformance value="SHOULD"/>
    <requirement
                 value="The PHG SHOULD implement a duplication detection mechanism and filter out any observations that have already been uploaded."/>
  </statement>
</Requirements>