Technical Implementation Guidance

These sections provide background on the concepts behind the technical mapping approach and how the PHD 11073 20601 objects are related to FHIR Observations. The normative details of the mapping are given in the Profiles sections.

It should be noted that the PHD profile is based upon FHIR 3.2.0 and the tool that generates this guide and structure definitions are based upon 3.0.1. Consequently, the structure definitions are created to the extent they can be in the 3.0.1 framework. The definitions will need to be updated when the tool supports 3.2.0. In most cases the differences are small except in the DeviceComponent. The differences that effect the PHD profile are listed below:

• In 3.0.1, the Observation.device element may only reference a Device and DeviceMetric resource
  • In 3.2.0 a reference to the DeviceComponent has been added
• In 3.0.1 the dataAbsentReason only supports the Not a Number (NAN) special value
  • In 3.2.0 support for positive infinity (PINF) and negative infinity (NINF) has been added
• In 3.0.1, the identifier of the DeviceComponent has cardinality 1..1
  • In 3.2.0 the cardinality has been changed to 0..*
• In 3.0.1 reporting several PHD properties require DeviceComponent extensions
  • In 3.2.0 a DeviceComponent.property element has been added