Personal Health Device Implementation Guide
2.0.0-ballot2 - STU 2 - Ballot
Personal Health Device Implementation Guide
2.0.0-ballot2 - STU 2 - Ballot
Personal Health Device Implementation Guide, published by HL7 International / Health Care Devices. This guide is not an authorized publication; it is the continuous build for version 2.0.0-ballot2 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7/phd/ and changes regularly. See the Directory of published versions
| Official URL: http://terminology.hl7.org/CodeSystem/ASN1ToHL7 | Version: 2.0.0-ballot2 | |||
| Standards status: Trial-use | Maturity Level: 1 | Computable Name: ASN1ToHL7 | ||
CodeSystem for mapping IEEE 11073-10206 bitstrings to FHIR Codeable Concepts
IEEE 11073-10206 PHDs report some device or measurement attributes as an integer where each bit in the integer may mean something. There is no HL7 data type that treats this kind of measurement. This code system defines a code for each of the possible bit settings. The bit value can be reported in a CodeableConcept data type.
The bit 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. In addition the code may derive from an IEEE 11073-10206 device attribute or from an Observation. This is encoded in a property of the code. More codes maybe added to this list in the future.
The code values for the properties are included here as well, since the valueset extension for properties is not supported for FHIR R4.
The uploader can generate the code from the data received from the PHD. No external information is necessary unless the uploader wants to populate the display element of the CodeableConcept data type. It is recommended that the uploader populates the display element as defined by the CodeSystem if known, or otherwise populates the text element with the Reference Id or the MDC code as decimal string followed by "bit n". It is not required because it is desired to have an uploader that can still work with future specializations and in that case, it is not possible for the uploader to know what to use as display as it is not sent over the wire; it is only available from the specialization documents.
To generate the code, the uploader obtains the code for the type of measurement which is used to populate the Observation.code.coding.code –element. Then for each bit to be reported, a new code is generated by appending a period followed by the bit position being mapped.
A bit can only have two values, set or cleared. Thus the value is reported in the Observation.component.valueBoolean –element using true for set and false for cleared.
component elements and one with code 8418060.3 and the other with code 8418060.4. Note these are alpha-numeric strings and not decimal numbers. If one took the code 8418060.3 and looked it up in the ASN.1 Bits vocabulary one would find it meant 'sensor malfunctioned'.If the ASN.1 bit represents an event, only the set condition needs to be reported. If the ASN.1 bit represents a state, both the set and cleared conditions need to be reported. If the device does not support the bit, it is not required to report the value. If the uploader would, nevertheless, desire to report the unsupported situation it is done in an Observation.component.dataAbsentReason.coding.code –element with code "unsupported". The Observation.component.value[x] element is absent. Undefined bits are never reported.
This code system is used to report IEEE 11073-10206 Multiple Boolean State observations, where each bit represents a state and for Bluetooth GHS Compound state/event observations that come with a mask to indicate per bit if it is a state or an event and whether it is supported by the device or not.
It is also used for IEEE 11073-20601 Bit-Str metrics. In version 4 or later of the IEEE 11073-20601 specification the enumeration metric object supports both a Capability-Mask-Simple/Basic and State-flag-Simple/Basic attribute that must be present when Bit-Str is reported. The Capability-Mask attribute will have a bit set when the corresponding bit in the actual measurement is supported by the device. The State-Flag attribute will have a bit set if the corresponding bit is a state. If cleared, the corresponding bit is an event. These attributes are not present in IEEE 11073-20601 versions 3 or earlier. If such version is used, the uploader will need to obtain this information from the ASN.1 to HL7 code system.
This Code system is referenced in the content logical definition of the following value sets:
Profile: Shareable CodeSystem
Properties
This code system defines the following properties for its concepts
| Name | Code | URI | Type | Description |
| Event or State | eventOrState | http://terminology.hl7.org/CodeSystem/ASN1ToHL7#eventOrState | code | The code type is an event or state |
| Source | source | http://terminology.hl7.org/CodeSystem/ASN1ToHL7#source | code | The code originates from a measurement or an attribute that further describes a measurement or the sensor device. |
| MDC Code | MDCCode | http://terminology.hl7.org/CodeSystem/ASN1ToHL7#MDCCode | Coding | The decimal code for the MDC code of the bits observation |
Concepts
This case-sensitive code system http://terminology.hl7.org/CodeSystem/ASN1ToHL7 defines the following codes:
IG © 2016+ HL7 International / Health Care Devices. Package hl7.fhir.uv.phd#2.0.0-ballot2 based on FHIR 4.0.1. Generated 2025-08-14
Links: Table of Contents |
QA Report
| Version History |
|
Propose a change