Personal Health Device Implementation Guide
1.0.0 - STU 1

Publication Build: This will be filled in by the publication tooling

## Terminology

The ISO/IEEE 11073-10101 Nomenclature standard (11073 MDC) provides a comprehensive terminology for device models according to the ISO/IEEE 11073-10201 and 11073-20601 Domain information models (DIM). It is the required code system for profiles in this implementation guide. Other additional coding systems expressing the same concepts may also be used. Reference identifiers, terminology codes, and descriptions are available at the Rosetta Terminology Mapping Management System (RTMMS).

The PHD profiles define rules for terminology usage:

- `Device.specializations` shall have a coding from the 11073 MDC Infra partition describing the device specializations and sub-profile standards the PHD conforms to. As the specialization elements are of type CodeableConcept there can be additional codings from other code systems.

The Vital Signs Profile, which is part of FHIR core specification, applies for some commonly used measurement observations (e. g., heart rate, blood pressure, respiratory rate, oxygen saturation, body temperature). The main impact this core requirement imposes on the PHD profiles is that for measurements that are considered vital signs, the LOINC code for that vital sign must be present. Consequently for vital signs measurements the `Observation.code` and, for compound metrics, the `Observation.component.code`:

elements must contain a matching LOINC code in addition to the required 11073 MDC code. The Vital Signs Profile also specifies that the Quantity data type in `Observation.value[x]` and `Observation.component.value[x]` contains the units of measure which shall be UCUM. The PHD profiles extends this requirement for all measurements that are of type Quantity.

### Code Systems

ContinuaDeviceIdentifiers | Codes used to describe the Device (PHD or PHG) Identifiers, such as the system id or Bluetooth Address. More codes maybe added to this list in the future.
ASN1ToHL7 | Maps IEEE 11073 ASN1 BITS measurements to codes. All these codes have two possible values, set or cleared. The code may either represent an event or a state. When an event, the defined event has occurred when set. If a state, the described item is either set or cleared. Sometimes the states may be defined in unexpected manners. For example, the regulation state when set is unregulated and when cleared it is regulated. In addition the code may derive from an IEEE 11073 attribute or from a measurement. More codes maybe added to this list in the future.
Measurement status codes | Measurement status definitions from the ISO/IEEE 11073-10201 DIM.
ContinuaHFS | Codes used to describe the Continua Health and Fitness interfaces supported by a Personal Health Gateway. More codes maybe added to this list in the future.
ContinuaPHD | Codes used to describe the Continua Personal Area Network (PHD) interfaces supported by a Personal Health Gateway. More codes maybe added to this list in the future.

### Value Sets

CodeableConcept 11073 Attributes | ValueSet for the ISO/IEEE 11073-10101 Nomenclatures Describing 11073-20601 attributes whose values are codes and thus represented as Codeable Concepts.
Quantity 11073 Attributes | ValueSet for the ISO/IEEE 11073-10101 Nomenclatures Describing 11073-20601 attributes whose values are Quantities.
Range 11073 Attributes | ValueSet for the ISO/IEEE 11073-10101 Nomenclatures Describing 11073-20601 attributes whose values are Ranges.
String 11073 Attributes | ValueSet for the ISO/IEEE 11073-10101 Nomenclatures Describing 11073-20601 attributes whose values are Strings.
11073 MDC Non-Object codes | ValueSet for the ISO/IEEE 11073-10101 Nomenclature excluding Object partition.
ANS1ToHL7 codes defined for non-measurement attributes | ValueSet for the ANS1ToHL7 codes that are not derived from enumeration measurements.
ANS1ToHL7 codes defined for measurement attributes | ValueSet for the ANS1ToHL7 codes that are derived from enumeration measurements.