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

Requirements: Narrative Conformance Statements

Official URL: http://hl7.org/fhir/uv/phd/Requirements/fromNarrative Version: 3.0.0-ballot
Standards status: Trial-use Maturity Level: 2 * Computable Name: FromNarrative
Other Identifiers: OID:2.16.840.1.113883.4.642.40.73.36.1

Conformance statements found throughout the narrative of the IG consolidated into this computable resource for traceability purposes

Language: en

1SHOULD

The PHG SHOULD specify a sufficiently selective conditional-create criterion so that at most one matching resource is found on the server.

2SHALL

When an equivalent UCUM code is known, this UCUM code SHALL be used.

3SHALL

An implementation SHALL use the MDC code if it does not know the UCUM code for the given unit.

4SHALL

The converted effective[x] SHALL retain fractional-second precision consistent with the PHD's tick resolution, so that time differences between observations are preserved.

5SHOULD

A derived RR interval Observation SHOULD reference the source ECG waveform Observation using Observation.derivedFrom.

6SHALL

The MDC code SHALL be present in a coding element.

7SHOULD

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.

8SHOULD

This measurement SHOULD contain a derived-from reference pointing to the measurement containing the glucose concentration.

9SHALL

For a PHD, Device.conformsTo SHALL contain at least one MDC specialization entry.

10SHOULD

PHDs SHOULD use the unchanged timestamp of a generated observation as received from the PHD.

11SHOULD

PHGs compliant with this IG SHOULD implement this identifier as specified to ensure this scheme works across all compliant gateways.

12SHOULD

For device settings known to the PHG, Observation.subject SHOULD point to the PHD.

13SHOULD-NOT

For Coincident Timestamp Observations, Observation.performer SHOULD NOT be provided.

14SHOULD

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.

15SHALL

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.

16SHOULD

When uploading to a FHIR server, the gateway SHOULD report the group observation with a hasMember reference to all member Observations.

17SHOULD

In FHIR, the session Observation SHOULD have hasMember references to all observations that are part of the session.

18SHALL

PHGs SHALL include a category element with a fixed coding as specified by the profile.

19SHOULD

Vital-sign Observations SHOULD include a category element as defined by the Vital Signs profile.

20SHALL

When encoding numeric Observation quantities in FHIR, the PHG SHALL follow the precision indicated by the PHD's IEEE 11073 FLOAT or SFLOAT encoding.

21SHOULD

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.

22SHALL

When a PHG encounters such a device it SHALL provide a transport address as a means of uniquely identifying the PHD.

23SHALL

The Accuracy attribute SHALL be reported if the PHD provides it.

24SHALL

Measurement-Confidence-95 SHALL be reported if the PHD provides it.

25SHALL

There SHALL be one coding element using the MDC coding system.

26SHALL

If the measurement is a vital sign, an additional coding element SHALL use a LOINC vital-sign code.

27SHALL

The PHG SHALL use a Patient.identifier supplied by the server when one is provided.

28SHALL

If the server does not provide an identifier, the PHG SHALL generate an implementation-dependent identifier whose value is unique within its assigning system.

29SHOULD

The type for a PHG-generated identifier SHOULD use a suitable code from the HL7 v2-0203 coding system.

30SHOULD

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.

31SHALL

Uploads generated by PHGs compliant to this IG SHALL use the mapping defined by this implementation guide when transforming PHD data to FHIR resources.

32SHOULD

The PHG SHOULD implement a duplication detection mechanism and filter out any observations that have already been uploaded.