Identifies the system as an IEEE EUI.

The System id from the System-Id attribute as an 8-byte HEX string where each byte is separated by dashes, for example FE-ED-AB-EE-DE-AD-77-C3.

The formatting is specified in the IEEE document Guidelines for 64-bit Global Identifier.

To allow the mapping of naughty, non-compliant proprietary devices that do not provide a system id, the value is set to all zeros in the same format, 00-00-00-00-00-00-00-00

The transport address. If Bluetooth, use an EUI-48 such as 00-E5-DE-AD-77-C3. If a USB device use the VID.PID as HEX such as 0043.F90D. If a ZigBee address use an EUI-64 as with the system id. If a TCP/IP address use the standard IP address format such as 192.168.127.4

Transport addresses are supposed to be unique for a given device.

This value identifies the IEEE 11073 10101 coding system

The device specialization is obtained from the System-Type-Spec-List attribute if the attribute has only a single entry or only a single specialization with one or more sub profiles from that specialization. If it has multiple specializations, this value is fixed to 'hydra' and there will be child DeviceComponent resources handling the specializations. The attribute provides only the term code, the partition is always 'infra' which has value 8. Thus the code will be 8*2**16 + term code.

When 'hydra' is used, the code is 528384 and the reference id is MDC_DEV_SPEC_PROFILE_HYDRA

A human readable display descrbing the meaning of the code.

This element should contain the reference identfier for the reported specialization code.

A reference to a location at which the PHG resource is found. The reference may be a relative reference, in which case it is relative to the service base URL, or an absolute URL that resolves to the location where the resource is found. The reference may be version specific or not. If the reference is not to a FHIR RESTful server, then it should be assumed to be version specific. Internal fragment references (start with '#') refer to contained resources.

OperationalStatus for the MDS, VMD, or Channel will be bound to a specific ValueSet that is defined in its profile. If used, a PHD is considered to be always on

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination.

This information is not available by protocol from the PHD and its use is up to the application.

This information is not available fron PHD devices by protocol. Its use is up to the implementation.

Identifies the IEEE 11073 10101 coding system

These codes are not seen on the wire between the PHD and the PHG. They are seen on the wire in PCD-01 messages.

The 32 bit code identifying what the string in the DeviceComponent.productionSpecification.productionSpec element is.

Need to identify what the reported string value represents

The currently defined codes used in this element are as follows:

FIELD CODE reference identifier

Model number 531969 MDC_ID_MODEL_NUMBER Manufacturer name 531970 MDC_ID_MODEL_MANUFACTURER The above come from the System-Model attribute

Unspecified 531971 MDC_ID_PROD_SPEC_UNSPECIFIED Serial number 531972 MDC_ID_PROD_SPEC_SERIAL Part number 531973 MDC_ID_PROD_SPEC_PART Hardware revision 531974 MDC_ID_PROD_SPEC_HW Software revision 531975 MDC_ID_PROD_SPEC_SW Firmware revision 531976 MDC_ID_PROD_SPEC_FW Protocol 531977 MDC_ID_PROD_SPEC_PROTOCOL Global Medical Device Nomenclature (GMDN) 531978 MDC_ID_PROD_SPEC_GMDN The above come from the Production-Specification attribute

Continua version 532352 MDC_REG_CERT_DATA_CONTINUA_VERSION The above comes from the Continua Reg-Cert-Data-List attribute

There may be more fields added in future versions of the 10101 specification.

A human readable display descrbing the meaning of the code.

This element should contain the reference identfier for the reported code.

A symbol in the syntax defined by the DeviceSpecificationSpecType system.

FHIR requires this code if the specType being coded is a member of this value set.

Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination. This infomration is not available by protocol from the PHD and its use is up to the application