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