Phd Coded Enumeration Observation Profile
The Coded Enumeration Observation Profile is used when the PHD metric measurement contains one of the following attributes:
| Attribute | Value | Additional Information |
|---|---|---|
| Enum-Observed-Value-Simple-OID | 16-bit term code | The partition is obtained from the Type attribute or the Enum-Observed-Value-Partition attribute |
| Enum-Observed-Value | 16-bit term code when an OID | The partition is obtained from the Type attribute or the Enum-Observed-Value-Partition attribute |
The Enum-Observed-Value-Simple-OID attribute is used when the measurement is itself an MDC code. This type of measurement is most common when reporting the context of another measurement, for example the meal context of a glucose measurement and/or the current state of health. Enumeration measurements are used when there is a finite set of fixed possibilities for the measurement to take. The attribute contains only the 16-bit term code. The partition typcially comes from the Type attribute or, in special cases, the Enum-Observed-Value-Partition attribute.
The Enum-Observed-Value attribute is a complex attribute and can be any one of the three possible enumeration measurements. There is an element in the structure which indicates which type of enumeration it is. If it is an 'OID' type it has an MDC term code. The attribute also has its own metric-id value telling what it is and status value. The metric-id value replaces the term code given by the Type attribute for the type of measurement (not the measurement!) and the status value replaces the Measurement-Status attribute.
The structure definition for this profile is
| PhdCodedEnumerationObservation (Observation) | PhdBaseObservation | ||
| meta | 1.. | ||
| profile | 1.. | ||
| phdProfile | 1..1 | Fixed Value | |
| identifier | |||
| conditionalCreateIdentifier | ..1 | ||
| value | 1.. | ||
| status | |||
| code | |||
| 11073Type | |||
| valueCodeableConcept | 1.. | CodeableConcept | |
| coding | 1.. | ||
| 11073Value | 1..1 | ||
| system | 1.. | Fixed Value | |
| code | 1.. | ||
| dataAbsentReason | |||
| coding | |||
| system | 1.. | ||
| code | 1.. |
Mapping Coded Enumerations to FHIR
The following table shows how the coded enumeration attributes are mapped to FHIR.
| Attribute | FHIR coding |
|---|---|
| Enum-Observed-Value-Simple-OID.value | Observation.valueCodeableConcept.coding.code |
| Enum-Observed-Value.value Enum-Observed-Value.metric-id Enum-Observed-Value.status |
Observation.valueCodeableConcept.coding.code effects Observation.code see Obtaining the Observation.code see Measurement Status in Phd Base Observation Profile |
Conditional Create Identifier Generation
For a general description of the PHD Profile Identifier see the "PHD Profile 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.valueCodeableConcept.coding.code" or "Observation.dataAbsentReason.coding.code" |
The enumeration 32-bit MDC code of the measurement or the data absent reason code if there is no value |
| 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.
Phd Coded Enumeration Observation JSON Example
The following JSON example is from a Glucose Monitor. The context measurement is in regard to the meal status at the time of the measurement. The measurement itself is an MDC code. In the future this measurement will contain a second related element due to a Source-Handle-Reference attribute pointing to the Glucose Concentration measurement. It has been added by hand below. In a real case the logical id of the Observation would be known.
{
"resourceType": "Observation",
"meta": {
"profile": ["http://pchalliance.org/phdfhir/StructureDefinition/PhdCodedEnumerationObservation"]
},
"identifier": [{
"value": "sisansarahId-urn:oid:1.2.3.4.5.6.7.8.10-01040302f4000000-8417864-20171214103752-8417868"
}],
"status": "final",
"code": {
"coding": [{
"system": "urn:iso:std:iso:11073:10101",
"code": "8417864",
"display": "MDC_CTXT_GLU_MEAL"
}]
},
"subject": {
"reference": "Patient/PatientId-sisansarahId"
},
"effectiveDateTime": "2017-12-14T10:37:50-05:00",
"performer": [{
"reference": "Patient/PatientId-sisansarahId"
}],
"valueCodeableConcept": {
"coding": [{
"system": "urn:iso:std:iso:11073:10101",
"code": "8417868",
"display": "MDC_CTXT_GLU_MEAL_PREPRANDIAL"
}]
},
"device": {
"reference": "DeviceComponent/SysId-01040302f4000000"
},
"related": [{
"id": "coincidentTimeStampRelated",
"type": "qualified-by",
"target": {
"reference": "urn:oid:3.14159.20171214103753"
},
{
"id": "SourceHandleReferenceRelated",
"type": "qualified-by",
"target": {
"reference": "Observation/logical-id of Glucose concentration measurement"
}
}]
}