Phg DeviceComponent Profile

The properties and specifications of the PHG are reported in the DeviceComponent. A PHG does not have an MDS object, but for the purposes of reporting the PHG information like its system identifier, time synchronization, and serial number these values are treated as if they came from MDS-attributes in an MDS object.

Unlike the PHD where one reports the information if delivered, in the PHG case far fewer fields are required to be reported. The following table summarizes the required fields and their mapping:

The transport address is not required. It is still strongly recommended that the transport address is reported as it is often beneficial to consumers. Most PHD-PHG transports provide a means of obtaining a transport address or an equivalent identifier such as a USB VID and PID.

Similar to the PHD case, when CodeableConcept data types are used it is recommended to put the MDC reference identifier as part of the display element when the system element indicates the MDC coding system "urn.iso.std.iso:11073:10101".

The structure definition for the Phg DeviceComponent Profile is shown below:

PhgDeviceComponent

urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680

urn:iso:std:iso:11073:10101

531981

urn:iso:std:iso:11073:10101

http://hl7.org/fhir/specification-type

A JSON example is given in Phg DeviceComponent JSON Example

This structure definition is missing the property element as it is based upon a tool that does not yet support version 3.2.0 of FHIR. The structure definition will be updated when support for 3.2.0 is available.

Meta Data Profile

The uploader shall populate the DeviceComponent.meta.profile with http://pchalliance.org/phdfhir/StructureDefinition/PhgDeviceComponent indicating this resource was generated following the PHD Implementation Guide.

System Identifier

All 11073 20601 PHGs are required to have a system identifier. It is an EUI-64 consisting of 8 bytes. The system id is mapped to the DeviceComponent.identifier.value element as a sequence of 8 2-digit bytes as HEX separated by dashes without the '0x' prefix commonly used in programming languages. An example of such a string is FE-ED-AB-EE-DE-AD-77-C3. It shall be reported.

It is strongly encouraged to also report the transport address in a second identifier element. The transport addresses are as follows:

The System-Id entry shall be first and the transport entry, if present, shall be second.

Device Type

The PHG always has the same type given by the MDC code 531981. The reference identifier for this code is MDC_MOC_VMS_MDS_AHD. "AHD" is the previous name Continua gave to what is now known as the PHG. However, reference identifiers are normative and once accepted, they cannot change.

Parent

There is no parent element in this profile.

Production Specification and System Model

The treatment of these fields is the same as in the Phd Parent DeviceComponent Profile. One should read that section in Phd Parent DeviceComponent Profile before proceding if not already familiar with it.

The final mapping of MDS attributes to the DeviceComponent.productionSpecification element is similar to that for the PHD and shown in the following table:

Given that a PHG is often an application hosted on a platform that may support several applications, it may not make sense to report many of the above fields. What is reported is up to the application.

Property

The property element is introduced in version 3.2.0 of FHIR. This element is used to report the regulation status, Continua certified PAN (Personal Area Network) and H&FS (Health and Fitness) interfaces, and the static time properties such as synchronization state, synchronization accuracy and the resolution of the time clock. It is not necessary to report the type of time clock; PHGs are always capable of using Base-Offset time.

'Reg-Cert-Data-List' Contributions

In addition to the Continua version reported in the DeviceComponent.productionSpecification, one may also report the list of certified PAN interfaces, list of certified H&FS interfaces, and regulation status.

The Continua codes for the PAN interface are detailed in the section Phd Parent DeviceComponent Profile section and are not repeated here. However, the H&FS codes are only present on the PHG. The following interfaces are defined:

The mapping of these Reg-Cert-Data-List attribute values to the DeviceComponent.property element is as follows:

Time Properties

A PHG is required to be capable of supporting synchronization to UTC and knowning the offset to local time.

Time Synchronization

It is required to report the time synchronization protocol. It indicates the method and state of the PHG time synchronization. It is one of the values in the following table:

Similar to the PHD, if the PHG has, for some reason, lost its synchronization, the value reported is 532224 or no time synchronization.

The uploader maps the state of synchronization to the DeviceComponent.property as follows:

• DeviceComponent.property.type.coding.code="68220"
• DeviceComponent.property.type.coding.system="urn.iso.std.iso:11073:10101"
• DeviceComponent.property.type.coding.display="MDC_TIME_SYNC_PROTOCOL" (optional)
• DeviceComponent.property.valueCodeableConcept.coding.code="32-bit code for sync method"
• DeviceComponent.property.valueCodeableConcept.coding.system="urn.iso.std.iso:11073:10101"
• DeviceComponent.property.valueCodeableConcept.coding.display="the ref id" (optional)

Time Synchronization Accuracy

The time synchronization accuracy should be reported if known in microseconds. The mapping is as follows:

• DeviceComponent.property.type.coding.code="68221"
• DeviceComponent.property.type.coding.system="urn.iso.std.iso:11073:10101"
• DeviceComponent.property.type.coding.display="MDC_TIME_SYNC_ACCURACY" (optional)
• DeviceComponent.property.valueQuantity.value="time sync accuracy"
• DeviceComponent.property.valueQuantity.system="urn.iso.std.iso:11073:10101"
• DeviceComponent.property.valueQuantity.code="264339" (MDC code for microseconds)
• DeviceComponent.property.valueQuantity.units="us" (Optional UCUM string)

Time Resolution

The PHG may report the resolution of its time clock. If it does it reports it in units of microseconds as follows:

Consumer of the PHD DeviceComponent Profile

For the Consumer of this profile the following table gives a quick guide to the main features