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

Conformance

Page standards status: Informative

Conformance

This page lists the testable, free-text conformance statements marked in this Implementation Guide. It is a summary, not a complete list of requirements; computable expectations in profiles, value sets, capability statements, and other artifacts are not included.

IdExpectationRule
 SHALL
 SHOULD
 SHOULD NOT
§1SHALLWhen an equivalent UCUM code is known, this UCUM code SHALL be used.
§2SHALLAn implementation SHALL use the MDC code if it does not know the UCUM code for the given unit.
§3SHALLThe converted effective[x] SHALL retain fractional-second precision consistent with the PHD's tick resolution, so that time differences between observations are preserved.
§4SHOULDA derived RR interval Observation SHOULD reference the source ECG waveform Observation using Observation.derivedFrom.
§5SHALLWhen encoding numeric Observation quantities in FHIR, the PHG SHALL follow the precision indicated by the PHD's IEEE 11073 FLOAT or SFLOAT encoding.
§6SHALLThe MDC code SHALL be present in a coding element.
§7SHOULDBecause 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.
§8SHOULDA meal context measurement SHOULD contain a derived-from reference pointing to the measurement containing the glucose concentration.
§9SHALLFor a PHD, Device.conformsTo SHALL contain at least one MDC specialization entry.
§10SHOULDThe PHG SHOULD specify a sufficiently selective conditional-create criterion for Patient and Device resources so that at most one matching resource is found on the server.
§11SHOULDThe PHG SHOULD implement a duplication detection mechanism and filter out any observations that have already been uploaded.
§12SHOULD NOTPHDs SHOULD NOT change the timestamp of an observation once it has been generated.
§13SHOULDPHGs compliant with this IG SHOULD implement this identifier as specified to ensure this scheme works across all compliant gateways.
§14SHOULDFor device settings known to the PHG, Observation.subject SHOULD point to the PHD.
§15SHOULD NOTFor Coincident Timestamp Observations, Observation.performer SHOULD NOT be provided.
§16SHOULDObservations 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.
§17SHALLWhen 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.
§18SHOULDWhen uploading to a FHIR server, the gateway SHOULD report the group observation with a hasMember reference to all member Observations.
§19SHOULDThe Source-Handle-Reference attributes SHOULD be mapped to a derivedFrom element in the uploaded Observation.
§20SHALLPHGs SHALL include a category element with a fixed coding as specified by the profile.
§21SHOULDVital-sign Observations SHOULD include a category element as defined by the Vital Signs profile.
§22SHOULDIf 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.
§23SHALLWhen a PHG encounters such a device it SHALL provide a transport address as a means of uniquely identifying the PHD.
§24SHOULDPHG 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.
§25SHALLThe Accuracy attribute SHALL be reported if the PHD provides it.
§26SHALLMeasurement-Confidence-95 SHALL be reported if the PHD provides it.
§27SHALLThere SHALL be one coding element using the MDC coding system.
§28SHALLIf the measurement is a vital sign, an additional coding element SHALL use a LOINC vital-sign code.
§29SHALLThe PHG SHALL use a Patient.identifier supplied by the server when one is provided.
§30SHALLIf the server does not provide an identifier, the PHG SHALL generate an implementation-dependent identifier whose value is unique within its assigning system.
§31SHOULDThe type for a PHG-generated patient identifier SHOULD use a suitable code from the HL7 v2-0203 coding system.
§32SHALLUploads generated by PHGs compliant to this IG SHALL use the mapping defined by this implementation guide when transforming PHD data to FHIR resources.