General Notes to Consumers

A consumer of the PHD profile resources will find most of the mapping as expected, especially in the Observation-based resources. However, there are some caveats in reporting information about the PHD itself. Only the DeviceComponent is used to reduce bandwidth. In FHIR, the Manufacturer name and Model number are in the Device resource and the production specification information is in the DeviceComponent resource. Every PHD is required to have the Manufacturer name and Model number as well as some information in the production specification.

Consequently, the PHD profile has decided to use the DeviceComponent.productionSpecification element to report both the production specification and manufacturer information; an approach similar to the Device Information Service in Bluetooth Low Energy devices. Consumers of FHIR resources are likely to expect the Manufacturer name and Model number in a Device resource and not the DeviceComponent.

A consumer of this profile searching for PHD information on a specific device would need to search for DeviceComponents, perhaps the easiest manner is by 11073 system id or transport address in the identifier. Searches on the DeviceComponent productionSpecification and property are not yet supported; this situation is expected to be remedied in the near future.

For those familiar with Point of Care Devices (PoCDs) and their heirarchy, a PHD has one hierarchy; all metric information is sourced by a single MDS. The 'medical components' and the 'controller component' of the PoCD model are merged into a single static unit and thus have the same production specification, manufacturer information, and system identifier. The static nature of the PHD means that the lastSystemChange element is never populated.