Personal Health Device Implementation Guide
1.0.0 - STU 1

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

## PHD String Enumeration Observation Profile

The String Enumeration Observation Profile is used when the PHD metric measurement is a human readable string. These types of measurements have the disadvantage of being unprocessable by machine without out-of-band information. Codes are often used instead where the end user can display them appropriately based upon locale.

The measurement is a human reable string when the PHD metric measurement contains one of the following attributes:

Attribute | Value
--- | ---
Enum-Observed-Value-Simple-Str | Human readable string
Enum-Observed-Value | Human readable string when indicated

This measurement is just a human readable string and is not designed to support generic interpretation by machine. To date it is used in only the Cardiovascular specialization to report the name of some exercise program option.

Structure definition for this profile is defined here

### Mapping the Enumeration String to FHIR

The human readable string from the Enum-Observed-Value-Simple-Str attribute is mapped to the Observation.valueString element.

### Meta Data Profile

The uploader shall populate the Observation.meta.profile with http://hl7.org/fhir/uv/phd/StructureDefinition/PhdStringEnumerationObservation indicating this resource is generated following the PHD Implementation Guide.

### Conditional Create Identifier Generation

For a general description of the PHD Observation Identifier see the “PHD Observation Identifier” section in PHD Base Profile. The table below lists the items that make up the identifier.

Entry | value | Additional information
--- | --- | ---
device | “PHD Device.identifier.value” | This value is the PHD IEEE EUI-64 system identifier
patient | “Patient.identifier.value-Patient.identifier.system” or provided logical id | The dashes are part of the identifier. When the service provider gives the PHG a pre-determined patient logical id the PHG creates no Patient resource and has no patient information. In that special case the provided logical id is used
type | “Observation.code.coding.code” | See Obtaining the Observation.code
value | “Observation.valueString” or “Observation.dataAbsentReason.coding.code” | The human readable string or the data absent reason code if needed
reported PHD timestamp | “timestamp” | See Generating the PHD Reported Time Stamp
supplemental types | “Supplemental-Types.N-“ | A sequence of 32-bit MDC codes separated by a dash

The final identifier is made by concatenating the entries above as follows:

- “device-patient-type-value-reported PHD timestamp-supplemental types”

### Additional Enumeration Measurement Information

There are no additional descriptive attributes that are unique to the Enumeration type of measurement.

### Examples:

String enumeration measurements are very rare. This example shows an example from a glucose meter explaining why a measurement failed. There is no such measurement type defined in the Glucose specialization so this manufacturer used a private attribute. Enumeration String measurement.

### The Other Profiles

- Profiles Overview
- Base Observation Profile
- Numeric Observation Profile
- Compound Numeric Observation Profile
- Coded Enumeration Observation Profile
- BITs Enumeration Observation Profile
- Rtsa Observation Profile
- Coincident Time Stamp Observation Profile
- Phd Device Profile
- Phg Device Profile
- Patient Profile