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
| Page standards status: Trial-use | Maturity Level: 2 |
{
"resourceType" : "Requirements",
"id" : "fromNarrative",
"language" : "en",
"text" : {
"status" : "generated",
"div" : "<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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</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>\n</div></td></tr></table></div>"
},
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-wg",
"valueCode" : "dev"
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm",
"valueInteger" : 2,
"_valueInteger" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/phd/ImplementationGuide/hl7.fhir.uv.phd"
}
]
}
},
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status",
"valueCode" : "trial-use",
"_valueCode" : {
"extension" : [
{
"url" : "http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom",
"valueCanonical" : "http://hl7.org/fhir/uv/phd/ImplementationGuide/hl7.fhir.uv.phd"
}
]
}
}
],
"url" : "http://hl7.org/fhir/uv/phd/Requirements/fromNarrative",
"identifier" : [
{
"system" : "urn:ietf:rfc:3986",
"value" : "urn:oid:2.16.840.1.113883.4.642.40.73.36.1"
}
],
"version" : "3.0.0-ballot",
"name" : "FromNarrative",
"title" : "Narrative Conformance Statements",
"status" : "active",
"experimental" : false,
"date" : "2026-11-20T18:02:18+00:00",
"publisher" : "HL7 International / Devices",
"contact" : [
{
"name" : "HL7 International / Devices",
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/healthcaredevices"
}
]
}
],
"description" : "Conformance statements found throughout the narrative of the IG consolidated into this computable resource for traceability purposes",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001"
}
]
}
],
"statement" : [
{
"key" : "1",
"conformance" : [
"SHOULD"
],
"requirement" : "The PHG SHOULD specify a sufficiently selective conditional-create criterion so that at most one matching resource is found on the server."
},
{
"key" : "2",
"conformance" : [
"SHALL"
],
"requirement" : "When an equivalent UCUM code is known, this UCUM code SHALL be used."
},
{
"key" : "3",
"conformance" : [
"SHALL"
],
"requirement" : "An implementation SHALL use the MDC code if it does not know the UCUM code for the given unit."
},
{
"key" : "4",
"conformance" : [
"SHALL"
],
"requirement" : "The converted effective[x] SHALL retain fractional-second precision consistent with the PHD's tick resolution, so that time differences between observations are preserved."
},
{
"key" : "5",
"conformance" : [
"SHOULD"
],
"requirement" : "A derived RR interval Observation SHOULD reference the source ECG waveform Observation using Observation.derivedFrom."
},
{
"key" : "6",
"conformance" : [
"SHALL"
],
"requirement" : "The MDC code SHALL be present in a coding element."
},
{
"key" : "7",
"conformance" : [
"SHOULD"
],
"requirement" : "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."
},
{
"key" : "8",
"conformance" : [
"SHOULD"
],
"requirement" : "This measurement SHOULD contain a derived-from reference pointing to the measurement containing the glucose concentration."
},
{
"key" : "9",
"conformance" : [
"SHALL"
],
"requirement" : "For a PHD, Device.conformsTo SHALL contain at least one MDC specialization entry."
},
{
"key" : "10",
"conformance" : [
"SHOULD"
],
"requirement" : "PHDs SHOULD use the unchanged timestamp of a generated observation as received from the PHD."
},
{
"key" : "11",
"conformance" : [
"SHOULD"
],
"requirement" : "PHGs compliant with this IG SHOULD implement this identifier as specified to ensure this scheme works across all compliant gateways."
},
{
"key" : "12",
"conformance" : [
"SHOULD"
],
"requirement" : "For device settings known to the PHG, Observation.subject SHOULD point to the PHD."
},
{
"key" : "13",
"conformance" : [
"SHOULD-NOT"
],
"requirement" : "For Coincident Timestamp Observations, Observation.performer SHOULD NOT be provided."
},
{
"key" : "14",
"conformance" : [
"SHOULD"
],
"requirement" : "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."
},
{
"key" : "15",
"conformance" : [
"SHALL"
],
"requirement" : "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."
},
{
"key" : "16",
"conformance" : [
"SHOULD"
],
"requirement" : "When uploading to a FHIR server, the gateway SHOULD report the group observation with a hasMember reference to all member Observations."
},
{
"key" : "17",
"conformance" : [
"SHOULD"
],
"requirement" : "In FHIR, the session Observation SHOULD have hasMember references to all observations that are part of the session."
},
{
"key" : "18",
"conformance" : [
"SHALL"
],
"requirement" : "PHGs SHALL include a category element with a fixed coding as specified by the profile."
},
{
"key" : "19",
"conformance" : [
"SHOULD"
],
"requirement" : "Vital-sign Observations SHOULD include a category element as defined by the Vital Signs profile."
},
{
"key" : "20",
"conformance" : [
"SHALL"
],
"requirement" : "When encoding numeric Observation quantities in FHIR, the PHG SHALL follow the precision indicated by the PHD's IEEE 11073 FLOAT or SFLOAT encoding."
},
{
"key" : "21",
"conformance" : [
"SHOULD"
],
"requirement" : "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."
},
{
"key" : "22",
"conformance" : [
"SHALL"
],
"requirement" : "When a PHG encounters such a device it SHALL provide a transport address as a means of uniquely identifying the PHD."
},
{
"key" : "23",
"conformance" : [
"SHALL"
],
"requirement" : "The Accuracy attribute SHALL be reported if the PHD provides it."
},
{
"key" : "24",
"conformance" : [
"SHALL"
],
"requirement" : "Measurement-Confidence-95 SHALL be reported if the PHD provides it."
},
{
"key" : "25",
"conformance" : [
"SHALL"
],
"requirement" : "There SHALL be one coding element using the MDC coding system."
},
{
"key" : "26",
"conformance" : [
"SHALL"
],
"requirement" : "If the measurement is a vital sign, an additional coding element SHALL use a LOINC vital-sign code."
},
{
"key" : "27",
"conformance" : [
"SHALL"
],
"requirement" : "The PHG SHALL use a Patient.identifier supplied by the server when one is provided."
},
{
"key" : "28",
"conformance" : [
"SHALL"
],
"requirement" : "If the server does not provide an identifier, the PHG SHALL generate an implementation-dependent identifier whose value is unique within its assigning system."
},
{
"key" : "29",
"conformance" : [
"SHOULD"
],
"requirement" : "The type for a PHG-generated identifier SHOULD use a suitable code from the HL7 v2-0203 coding system."
},
{
"key" : "30",
"conformance" : [
"SHOULD"
],
"requirement" : "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."
},
{
"key" : "31",
"conformance" : [
"SHALL"
],
"requirement" : "Uploads generated by PHGs compliant to this IG SHALL use the mapping defined by this implementation guide when transforming PHD data to FHIR resources."
},
{
"key" : "32",
"conformance" : [
"SHOULD"
],
"requirement" : "The PHG SHOULD implement a duplication detection mechanism and filter out any observations that have already been uploaded."
}
]
}