Continua Personal Health Device Data Implementation Guide

Phd Device JSON Example

Phd Device Profile

The properties and specifications of the PHD are reported in the Device resource. These are the static fields of the attributes reported in the PHD MDS object or Bluetooth Low Energy Device Information Service. Dynamic and observational attributes such as the battery level, remaining battery time, and power status are reported using the Observation resource.

There are six MDS attributes that are reported. The Mds-Time-Info attribute has fields that are dynamic and static, and it is only the static entries which are required should the attribute be present. The following table summarizes these attributes and the Device elements to which they are mapped:

MDS attribute	Device element
System-Id	identifier 1
transport address	identifier 2
Friendly name	deviceName
System-Type-Spec-List	specializations
Production-Specification	serialNumber version partNumber
Reg-Cert-Data-List	version property
MdsTimeInfo	property

The transport address and friendly name are not provided by the MDS but come from the transport protocols. They may not be available are therefore optional. However, if the PHD does not report a System Id, which may happen if one needs to map non-certified and/or proprietary devices, a transport address should be reported. It is still strongly recommended that the transport address is reported as it is often beneficial to the data consumers. Transport addresses of wireless devices are often printed on the device or the device packaging whereas the system id is not. Most PHD transports provide a means of obtaining a transport address or an equivalent identifier such as a USB VID and PID.

There are several CodeableConcept data types in this mapping where the Coding data type has a 'display' element. It is recommended to put the MDC reference identifier as part of the display element if known and when the system element indicates the MDC coding system "urn.iso.std.iso:11073:10101".

The structure definition for the PHD Device Profile is shown below:

DeviceComponent	I		DeviceComponent	Element id DeviceComponent Short description An instance of a medical-related component of a medical device Definition The characteristics, operational status and capabilities of a medical-related component of a medical device. A PHD is JUST the medical-related component. Comments For the initial scope, this DeviceComponent resource is only applicable to describe a single node in the containment tree that is produced by the context scanner in any medical device that implements or derives from the ISO/IEEE 11073 standard and that does not represent a metric. Examples for such a node are MDS, VMD, or Channel. With PHD medical units, there is no medical scanner and the unit is only a single node, a single 'simple' MDS, and it is static. Thus a PHD has no parent 'Device'. When a PHD supports multiple device specializations, the single unit description is still the case. A specialization is just an way to organize a set of metric objects that tend to be generated by a single sensor, but the device could expose metric objects from several specializations which usually means it has more than one sensor. In PHDs that is rare. Since FHIR does not have a means to list multiple types for the DeviceComponent resource, child DeviceComponents are used to expose these additional specializations should they occur. Child DeviceComponents can appear in two ways, a single specialization that supports one or more sub-profiles, or a hydra PHD that supports multiple specializations. Data type DeviceComponent Constraints dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources `contained.contained.empty()` dom-1: If the resource is contained in another resource, it SHALL NOT contain any narrative `contained.text.empty()` dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated `contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()` dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource `contained.where(('#'+id in %resource.descendants().reference).not()).empty()` Mappings rim: Entity. Role, or Act w5: administrative.device
id	Σ	0..1	id	There are no (further) constraints on this element Element id DeviceComponent.id Short description Logical id of this artifact Definition The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. Comments The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Data type id Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
meta	Σ	1..1	Meta	There are no (further) constraints on this element Element id DeviceComponent.meta Short description Metadata about the resource Definition The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource. Data type Meta Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a rim: N/A
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.meta.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.meta.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
versionId	Σ	0..1	id	There are no (further) constraints on this element Element id DeviceComponent.meta.versionId Short description Version specific identifier Definition The version specific identifier, as it appears in the version portion of the URL. This values changes when the resource is created, updated, or deleted. Comments The server assigns this value, and ignores what the client specifies, except in the case that the server is imposing version integrity on updates/deletes. Data type id Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
lastUpdated	Σ	0..1	instant	There are no (further) constraints on this element Element id DeviceComponent.meta.lastUpdated Short description When the resource version last changed Definition When the resource last changed - e.g. when the version changed. Comments This value is always populated except when the resource is first being created. The server / resource manager sets this value; what a client provides is irrelevant. Data type instant Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
profile	Σ	1..*	uri	Element id DeviceComponent.meta.profile Short description Profiles this resource claims to conform to Definition A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. Comments It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. Data type uri Sliced: Unordered, Open, by phdParentDeviceComponent(Value) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
phdProfile	Σ	1..1	uriFixed Value	Element id DeviceComponent.meta.profile:phdProfile Short description Profiles this resource claims to conform to Definition A list of profiles (references to StructureDefinition resources) that this resource claims to conform to. The URL is a reference to StructureDefinition.url. Comments It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Fixed value phdParentDeviceComponent Mappings rim: n/a
security	Σ	0..*	CodingBinding	There are no (further) constraints on this element Element id DeviceComponent.meta.security Short description Security Labels applied to this resource Definition Security labels applied to this resource. These tags connect specific resources to the overall security policy and infrastructure. Comments The security labels can be updated without changing the stated version of the resource The list of security labels is a set. Uniqueness is based the system/code, and version and display are ignored. Data type Coding Binding Security Labels from the Healthcare Privacy and Security Classification System. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding
tag	Σ	0..*	Coding	There are no (further) constraints on this element Element id DeviceComponent.meta.tag Short description Tags applied to this resource Definition Tags applied to this resource. Tags are intended to be used to identify and relate resources to process and workflow, and applications are not required to consider the tags when interpreting the meaning of a resource. Comments The tags can be updated without changing the stated version of the resource. The list of tags is a set. Uniqueness is based the system/code, and version and display are ignored. Data type Coding Binding Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones" ?? (example) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding
implicitRules	Σ ?!	0..1	uri	There are no (further) constraints on this element Element id DeviceComponent.implicitRules Short description A set of rules under which this content was created Definition A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Comments Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
language		0..1	codeBinding	There are no (further) constraints on this element Element id DeviceComponent.language Short description Language of the resource content Definition The base language in which the resource is written. Comments Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute). Data type code Binding A human language. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
text	I	0..1	Narrative	There are no (further) constraints on this element Element id DeviceComponent.text Short description Text summary of the resource, for human interpretation Alternate names narrative, html, xhtml, display Definition A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety. Comments Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded in formation is added later. Data type Narrative Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a rim: N/A rim: Act.text?
contained		0..*	Resource	There are no (further) constraints on this element Element id DeviceComponent.contained Short description Contained, inline Resources Alternate names inline resources, anonymous resources, contained resources Definition These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. Comments This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Data type Resource Mappings rim: Entity. Role, or Act rim: N/A
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	?! I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
identifier	Σ	1..1	Identifier	Element id DeviceComponent.identifier Short description Information that uniquely describes the device Definition The locally assigned unique identification of the device that is semantically meaningful outside of the FHIR resource context. An example would be the IEEE EUI-64 System-Id or transport address. For PHDs the systemIdentifier is required and the transportAddressIdentifier is highly recommended as this is what most end users see and can obtain from the device itself or device packaging. Comments In future versions of FHIR the cardinality of this element will become [0..] and this element will be used to report the system id and optionally the transport address. Data type* Identifier Sliced: Ordered, Open, by system(Value) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - see see identifier pattern at http://wiki.hl7.org/index.php?title=Common_Design_Patterns#Identifier_Pattern for relevant discussion. The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier w5: id
systemIdIdentifier	Σ	1..1	Identifier	Element id DeviceComponent.identifier:systemIdIdentifier Short description IEEE EUI-64 identifier Definition This entry contains the IEEE EUI-64. If absent (bad device) set to all zeros. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - see see identifier pattern at http://wiki.hl7.org/index.php?title=Common_Design_Patterns#Identifier_Pattern for relevant discussion. The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier w5: id
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.identifier:systemIdIdentifier.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.identifier:systemIdIdentifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id DeviceComponent.identifier:systemIdIdentifier.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. Requirements Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Comments This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Data type code Binding Identifies the purpose for this identifier, if known . ?? (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id DeviceComponent.identifier:systemIdIdentifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Requirements Allows users to make use of identifiers when the identifier system is not known. Comments This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: CX.5 rim: Role.code or implied by context
system	Σ	1..1	uriFixed Value	Element id DeviceComponent.identifier.system Short description IEEE EUI-64 identifier Definition Identifies the system as an IEEE EUI. Requirements There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Comments see http://en.wikipedia.org/wiki/Uniform_resource_identifier Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Fixed value urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680 Mappings rim: n/a v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	Σ	1..1	string	Element id DeviceComponent.identifier.value Short description The value that is unique Definition 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. Comments 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 Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Examples General 123456 Mappings rim: n/a v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ I	0..1	Period	There are no (further) constraints on this element Element id DeviceComponent.identifier:systemIdIdentifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Comments This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval\|Duration. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.empty() or end.empty() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ I	0..1	Reference(http://hl7.org/fhir/StructureDefinition/Organization)	There are no (further) constraints on this element Element id DeviceComponent.identifier:systemIdIdentifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. Comments The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Data type Reference(http://hl7.org/fhir/StructureDefinition/Organization) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %resource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
transportAddressIdentifier	Σ	0..1	Identifier	Element id DeviceComponent.identifier:transportAddressIdentifier Short description Transport address identifier Definition This entry contains the transport address, for example the Bluetooth, ZigBee, USB, or mac address. Comments USB does not have an 'address' as it is a point to point wired protocol. However, it does have a Vendor identification and Production identification number which together uniquely define the unit. For USB transports, the VID.PID in HEX is used as the transport identifier. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - see see identifier pattern at http://wiki.hl7.org/index.php?title=Common_Design_Patterns#Identifier_Pattern for relevant discussion. The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier w5: id
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.identifier:transportAddressIdentifier.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.identifier:transportAddressIdentifier.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
use	Σ ?!	0..1	codeBinding	There are no (further) constraints on this element Element id DeviceComponent.identifier:transportAddressIdentifier.use Short description usual \| official \| temp \| secondary (If known) Definition The purpose of this identifier. Requirements Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. Comments This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Data type code Binding Identifies the purpose for this identifier, if known . ?? (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: N/A rim: Role.code or implied by context
type	Σ	0..1	CodeableConceptBinding	There are no (further) constraints on this element Element id DeviceComponent.identifier:transportAddressIdentifier.type Short description Description of identifier Definition A coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Requirements Allows users to make use of identifiers when the identifier system is not known. Comments This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. Data type CodeableConcept Binding A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD v2: CX.5 rim: Role.code or implied by context
system	Σ	1..1	uri	There are no (further) constraints on this element Element id DeviceComponent.identifier.system Short description The namespace for the identifier value Definition Establishes the namespace for the value - that is, a URL that describes a set values that are unique. Requirements There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. Comments see http://en.wikipedia.org/wiki/Uniform_resource_identifier Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Examples General http://www.acme.com/identifiers/patient Mappings rim: n/a v2: CX.4 / EI-2-4 rim: II.root or Role.id.root servd: ./IdentifierType
value	Σ	1..1	string	Element id DeviceComponent.identifier.value Short description The value that is unique Definition 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 Comments Transport addresses are supposed to be unique for a given device. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Examples General 123456 Mappings rim: n/a v2: CX.1 / EI.1 rim: II.extension or II.root if system indicates OID or GUID (Or Role.id.extension or root) servd: ./Value
period	Σ I	0..1	Period	There are no (further) constraints on this element Element id DeviceComponent.identifier:transportAddressIdentifier.period Short description Time period when id is/was valid for use Definition Time period during which identifier is/was valid for use. Comments This is not a duration - that's a measure of time (a separate type), but a duration that occurs at a fixed value of time. A Period specifies a range of time; the context of use will specify whether the entire range applies (e.g. "the patient was an inpatient of the hospital for this time range") or one value from the range applies (e.g. "give to the patient between these two times"). If duration is required, specify the type as Interval\|Duration. Data type Period Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` per-1: If present, start SHALL have a lower value than end `start.empty() or end.empty() or (start <= end)` Mappings rim: n/a v2: DR rim: IVL<TS>[lowClosed="true" and highClosed="true"] or URG<TS>[lowClosed="true" and highClosed="true"] v2: CX.7 + CX.8 rim: Role.effectiveTime or implied by context servd: ./StartDate and ./EndDate
assigner	Σ I	0..1	Reference(http://hl7.org/fhir/StructureDefinition/Organization)	There are no (further) constraints on this element Element id DeviceComponent.identifier:transportAddressIdentifier.assigner Short description Organization that issued id (may be just text) Definition Organization that issued/manages the identifier. Comments The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Data type Reference(http://hl7.org/fhir/StructureDefinition/Organization) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %resource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity) v2: CX.4 / (CX.4,CX.9,CX.10) rim: II.assigningAuthorityName but note that this is an improper use by the definition of the field. Also Role.scoper servd: ./IdentifierIssuingAuthority
type	Σ	1..1	CodeableConceptBinding	Element id DeviceComponent.type Short description What kind of component it is Definition The type or 'specialization' of the PHD. Comments In most cases a PHD supports only a single specialization such as a Blood Pressure monitor and only one DeviceComponent is needed and that specialization is recorded in this element. Since there is no way to indicate additional supported specialziations with this element (it has cardinality 1..1), additional child DeviceComponents are needed when multiple specializations and/or sub-profiles are present. The value entered in this element comes from the System-Type-Spec-List attribute which is unique to the 11073 20601 specification; 11073-10201 does not have such an attribute. If there is more than one specialization, the special HYDRA specialization value is entered here and child DeviceComponent resources are used to map the specializations. If there is only a single specialization but one or more sub profiles., the specialization is entered here and the sub profiles are handled in child DeviceComponents. Note that sub-profiles are a packaging of objects within a specialization that serve a special use case. For example, the Cardiovascular specialization has numerous objects that can represent all kinds of physical activities from treadmills to skiing. One sub-profile is a minimum set of objects needed to describe a step counter. Data type CodeableConcept Binding Describes the type of the component. ?? (preferred) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD w5: class
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.type.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.type.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
coding	Σ	1..*	Coding	Element id DeviceComponent.type.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Sliced: Ordered, Open, by system(Value) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
11073Type	Σ	1..1	Coding	Element id DeviceComponent.type.coding:11073Type Short description Code defined by a terminology system Definition The 11073 10101 code for the PHD specialization. Requirements Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Comments This coding is provided by the System-Type-Spec-List attribute. Note that PoCDs do not have a System-Type-Spec-List but express specializations in different VMD objects. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.type.coding:11073Type.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.type.coding:11073Type.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
system	Σ	1..1	uriFixed Value	Element id DeviceComponent.type.coding.system Short description Identifies IEEE 11073 10101 Definition This value identifies the IEEE 11073 10101 coding system Requirements Need to be unambiguous about the source of the definition of the symbol. Comments The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Fixed value urn:iso:std:iso:11073:10101 Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceComponent.type.coding:11073Type.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	Σ	1..1	code	Element id DeviceComponent.type.coding.code Short description Device specialization code Definition 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 8216 + term code. When 'hydra' is used, the code is 528384 and the reference id is MDC_DEV_SPEC_PROFILE_HYDRA Requirements* Need to refer to a particular code in the system. Comments Note that FHIR strings may not exceed 1MB in size Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	Element id DeviceComponent.type.coding.display Short description Representation defined by the system Definition A human readable display descrbing the meaning of the code. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments This element should contain the reference identfier for the reported specialization code. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id DeviceComponent.type.coding:11073Type.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceComponent.type.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
lastSystemChange	Σ	0..0	instant	Element id DeviceComponent.lastSystemChange Short description Recent system change timestamp Definition The timestamp for the most recent system change which includes device configuration or setting change. This field is not provided by PHD devices via standardized exchange protocols and is, therefore, not required in this profile. Comments A PHD is static and does not change and the appropriate value for this entry would be its manufacture date. However, this information is not available by protocol and shall not be used. Its absence indicates a static unit. Data type instant Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a w5: when.init
source	Σ I	0..0	Reference(http://hl7.org/fhir/StructureDefinition/Device)	Element id DeviceComponent.source Short description Top-level device resource link Definition The link to the source Device that contains administrative device information such as manufacture, serial number, etc. Comments PHDs are considered medical devices only and are not part of a device complex which PoCD devices might be. The DeviceComponent is considered to represent the medical device subset of a device complex and since that is all a PHD is, this element is not used. Data type Reference(http://hl7.org/fhir/StructureDefinition/Device) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %resource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
parent	Σ I	0..1	Reference(http://hl7.org/fhir/StructureDefinition/DeviceComponent)	Element id DeviceComponent.parent Short description Parent resource link Definition The link to the DeviceComponent resource representing the Personal Health Gateway (PHG) that processed the sensor data and converted it to FHIR Requirements The PHG does limited correction of the received data; in particular, any errors in the time line and mapping the time line to local time plus UTC offset Comments This element shall be present if a PHG is involved in generating the FHIR data. Data type Reference(http://hl7.org/fhir/StructureDefinition/DeviceComponent) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ref-1: SHALL have a contained resource if a local reference is provided `reference.startsWith('#').not() or (reference.substring(1).trace('url') in %resource.contained.id.trace('ids'))` Mappings rim: n/a rim: The target of a resource reference is a RIM entry point (Act, Role, or Entity)
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.parent.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.parent.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
reference	Σ I	1..1	string	Element id DeviceComponent.parent.reference Short description Literal reference, Relative, internal or absolute URL Definition 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. Comments Using absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure "/[type]/[id]" then it should be assumed that the reference is to a FHIR RESTful server. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a rim: N/A
identifier	Σ	0..1	Identifier	There are no (further) constraints on this element Element id DeviceComponent.parent.identifier Short description Logical reference, when literal reference is not known Definition An identifier for the other resource. This is used when there is no way to reference the other resource directly, either because the entity is not available through a FHIR server, or because there is no way for the author of the resource to convert a known identifier to an actual location. There is no requirement that a Reference.identifier point to something that is actually exposed as a FHIR instance, but it SHALL point to a business concept that would be expected to be exposed as a FHIR instance, and that instance would need to be of a FHIR resource type allowed by the reference. Comments When an identifier is provided in place of a reference, any system processing the reference will only be able to resolve the identifier to a reference if it understands the business context in which the identifier is used. Sometimes this is global (e.g. a national identifier) but often it is not. For this reason, none of the useful mechanisms described for working with references (e.g. chaining, includes) are possible, nor should servers be expected to be able resolve the reference. Servers may accept an identifier based reference untouched, resolve it, and/or reject it - see CapabilityStatement.rest.resource.referencePolicy. When both an identifier and a literal reference are provided, the literal reference is preferred. Applications processing the resource are allowed - but not required - to check that the identifier matches the literal reference Applications converting a logical reference to a literal reference may choose to leave the logical reference present, or remove it. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - see see identifier pattern at http://wiki.hl7.org/index.php?title=Common_Design_Patterns#Identifier_Pattern for relevant discussion. The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier rim: .identifier
display	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceComponent.parent.display Short description Text alternative for the resource Definition Plain text narrative that identifies the resource in addition to the resource reference. Comments This is generally not the same as the Resource.text of the referenced resource. The purpose is to identify what's being referenced, not to fully describe it. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a rim: N/A
operationalStatus	Σ	0..*	CodeableConceptBinding	Element id DeviceComponent.operationalStatus Short description Current operational status of the component, for example On, Off or Standby Definition The current operational status of the device. For example: On, Off, Standby, etc. Comments 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 Data type CodeableConcept Binding Codes representing the current status of the device - on, off, suspended, etc. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
parameterGroup	Σ	0..1	CodeableConceptBinding	Element id DeviceComponent.parameterGroup Short description Current supported parameter group Definition The parameter group supported by the current device component that is based on some nomenclature, e.g. cardiovascular. Comments 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. Data type CodeableConcept Binding Codes identifying groupings of parameters; e.g. Cardiovascular. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
measurementPrinciple	Σ	0..1	codeBinding	Element id DeviceComponent.measurementPrinciple Short description other \| chemical \| electrical \| impedance \| nuclear \| optical \| thermal \| biological \| mechanical \| acoustical \| manual+ Definition The physical principle of the measurement. For example: thermal, chemical, acoustical, etc. Comments This information is not available fron PHD devices by protocol. Its use is up to the implementation. Data type code Binding Different measurement principle supported by the device. ?? (required) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
productionSpecification	Σ	0..*	BackboneElement	Element id DeviceComponent.productionSpecification Short description Specification details such as Component Revisions, or Serial Numbers Definition The production specification such as component revision, serial number, etc. For the 11073 20601 Personal Health Device, the production specification entries come from the Production-Specification, System-Model, and Reg-Cert-Data-List attributes. There will be one productionSpecification entry for each item to be reported. Comments All the PHD productionSpecification entries are strings and have IEEE 11073-10101 codes that define which production specification the string represents. Compliant PHDs will always have at least some entries for this element. If the PHD reports one or more such entries, they shall be recorded here. However, to allow the mapping of naughty proprietary devices, this element is made technically optional. Data type BackboneElement Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
modifierExtension	Σ ?! I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.modifierExtension Short description Extensions that cannot be ignored Alternate names extensions, user content, modifiers Definition May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
specType	Σ	1..1	CodeableConceptBinding	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType Short description Type or kind of production specification, for example serial number or software revision Definition The specification type, such as, serial number, part number, hardware revision, software revision, etc. Comments 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. Data type CodeableConcept Binding Codes for device specification types such as serial number, part number, hardware revision, software revision, etc. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
coding	Σ	1..*	Coding	Element id DeviceComponent.productionSpecification.specType.coding Short description Code defined by a terminology system Definition A reference to a code defined by a terminology system. Requirements Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Comments Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Data type Coding Sliced: Ordered, Open, by system(Value) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
11073Type	Σ	1..1	Coding	Element id DeviceComponent.productionSpecification.specType.coding:11073Type Short description The 11073-10101 code Definition The 11073-10101 code defining what the productionSpec is Requirements Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Comments 11073 10101 codes have been defined for the Production-Specification and System-Model sub entries for use in V2 messaging. Though FHIR has provided its own set of codes based upon the names of the 11073-* Production-Specification.spec-type entry, the 11073-10101 codes are used since they are ubiquitous in these PHD-related profiles and it helps accelerate the acceptance of the MDC coding system in HL7. Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:11073Type.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:11073Type.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
system	Σ	1..1	uriFixed Value	Element id DeviceComponent.productionSpecification.specType.coding.system Short description Specifies IEEE 11073 10101 Definition Identifies the IEEE 11073 10101 coding system Requirements Need to be unambiguous about the source of the definition of the symbol. Comments These codes are not seen on the wire between the PHD and the PHG. They are seen on the wire in PCD-01 messages. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Fixed value urn:iso:std:iso:11073:10101 Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:11073Type.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	Σ	1..1	code	Element id DeviceComponent.productionSpecification.specType.coding.code Short description actual code Definition The 32 bit code identifying what the string in the DeviceComponent.productionSpecification.productionSpec element is. Requirements Need to identify what the reported string value represents Comments 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. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	Element id DeviceComponent.productionSpecification.specType.coding.display Short description Representation defined by the system Definition A human readable display descrbing the meaning of the code. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments This element should contain the reference identfier for the reported code. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:11073Type.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
fhirCoding	Σ	0..1	Coding	Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding Short description The IEEE concept in the DeviceSpecificationSpecType coding system Definition The IEEE concept defined in the 11073Type coding element expressed in the DeviceSpecificationSpecType coding system. Requirements Besides satisfying a system requirement, including these values supports searches for DeviceComponents based upon the DeviceSpecificationSpecType codes. Of course, as of 3.0.1 searches on the DeviceComponent.productionSpecification are not supported but this is to change in the future. Comments FHIR requires this element to be present IF the production specification being reported is included in the DeviceSpecificationSpecType value set. Currently that is all the possible entries defined in the IEEE 11073 ProductionSpecification attribute. These codes and entries are as follows: Code Description unspecified Unspecified Production Specification serial-number Serial Number part-number Part Number hardware-revision Hardware Revision software-revision Software Revision firmware-revision Firmware Revision protocol-revision Protocol Revision gmdn Global Medical Device Nomencalture Data type Coding Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE subset one of the sets of component 1-3 or 4-6 rim: CV orim: fhir:Coding rdfs:subClassOf dt:CDCoding v2: CE.1-8, CE.10-22 rim: union(., ./translation) orim: fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
id		0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding.id Short description xml:id (or equivalent in JSON) Definition unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
extension	I	0..*	Extension	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding.extension Short description Additional Content defined by implementations Alternate names extensions, user content Definition May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Data type Extension Sliced: Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` ext-1: Must have either extensions or value[x], not both `extension.exists() != value.exists()` Mappings rim: n/a rim: N/A
system	Σ	1..1	uriFixed Value	Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding.system Short description Identity of the terminology system Definition The identification of the code system that defines the meaning of the symbol in the code. Requirements Need to be unambiguous about the source of the definition of the symbol. Comments The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. Data type uri Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Fixed value http://hl7.org/fhir/specification-type Mappings rim: n/a v2: CE.3 rim:* ./codeSystem orim: fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
version	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding.version Short description Version of the system - if relevant Definition The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Comments Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.7 rim:* ./codeSystemVersion orim: fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
code	Σ	1..1	code	Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding.code Short description Symbol in syntax defined by the system Definition A symbol in the syntax defined by the DeviceSpecificationSpecType system. Requirements Need to refer to a particular code in the system. Comments FHIR requires this code if the specType being coded is a member of this value set. Data type code Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.1 rim:* ./code orim: fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
display	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding.display Short description Representation defined by the system Definition A representation of the meaning of the code in the system, following the rules of the system. Requirements Need to be able to carry a human-readable meaning of the code for readers that do not know the system. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.2 - but note this is not well followed rim:* CV.displayName orim: fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
userSelected	Σ	0..1	boolean	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.coding:fhirCoding.userSelected Short description If this coding was chosen directly by the user Definition Indicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). Requirements This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Comments Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely. Data type boolean Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: Sometimes implied by being first rim: CD.codingRationale orim: fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
text	Σ	0..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.specType.text Short description Plain text representation of the concept Definition A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. Requirements The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Comments Very often the text is the same as a displayName of one of the codings. Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE.9. But note many systems use CE.2 for this rim: ./originalText[mediaType/code="text/plain"]/data orim: fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
componentId	Σ	0..1	Identifier	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.componentId Short description Internal component unique identification Definition The internal component unique identification. This is a provision for manufacture specific standard components using a private OID. 11073-10101 has a partition for private OID semantic that the manufacturer can make use of. Data type Identifier Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CX / EI (occasionally, more often EI maps to a resource id or a URL) rim: II - see see identifier pattern at http://wiki.hl7.org/index.php?title=Common_Design_Patterns#Identifier_Pattern for relevant discussion. The Identifier class is a little looser than the v3 type II because it allows URIs as well as registered OIDs or GUIDs. Also maps to Role[classCode=IDENT] servd: Identifier
productionSpec	Σ	1..1	string	There are no (further) constraints on this element Element id DeviceComponent.productionSpecification.productionSpec Short description A printable string defining the component Definition The printable string defining the component. Comments Note that FHIR strings may not exceed 1MB in size Data type string Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a
languageCode	Σ	0..1	CodeableConceptBinding	Element id DeviceComponent.languageCode Short description Language code for the human-readable text strings produced by the device Definition The language code for the human-readable text string produced by the device. This language code will follow the IETF language tag. Example: en-US. Comments 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 Data type CodeableConcept Binding A human language. ?? (extensible) Constraints ele-1: All FHIR elements must have a @value or children `hasValue() \| (children().count() > id.count())` Mappings rim: n/a v2: CE/CNE/CWE rim: CD orim: fhir:CodeableConcept rdfs:subClassOf dt:CD

A JSON example is given in Phd Device JSON Example

Meta Data Profile

The uploader shall populate the Device.meta.profile with http://pchalliance.org/phdfhir/StructureDefinition/PhdDevice indicating this resource is generated following the PHD Implementation Guide.

System Identifier

All 11073 20601 PHDs are required to have a system identifier. It is an EUI-64 consisting of 8 bytes. The system id is mapped to the Device.identifier.value element as a sequence of 8 2-digit bytes as HEX separated by dashes without the '0x' prefix commonly used in programming languages. An example of such a string is FE-ED-AB-EE-DE-AD-77-C3. Though required for Continua compliance, it is not required in the Bluetooth Low Energy health device specifications. When a PHG encounters such a device it shall enter 00-00-00-00-00-00-00-00 and it is highly recommended to provide a transport address as a means of uniquely identifying the PHD.

The transport addresses are as follows:

transport	format	example
Bluetooth	EUI-48	00-E5-DE-AD-77-C3
ZigBee	EUI-64	36-ED-9A-EE-DE-AD-77-C3
USB	vid.pid	0043.F90D

The identifier is encoded as follows:

Source	Device Encoding
System-Id.value	identifier.value=formatted as above identifier.system="urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680" identifier.use="official" identifier.assigner.display="EUI-64
Bluetooth Address	identifier.value=formatted as above identifier.system="urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680" identifier.assigner.display="EUI-48
ZigBee Address	identifier.value=formatted as above
USB Address	identifier.value=formatted as above

Device.type

The Device type is the same for all PHDs and it indicates that the device is a PHD. The details of what the PHD does is found in the Device.specializations element. The MDC code being used is 65573 (reference id MDC_MOC_VMS_MDS_SIMP). In 11073-10201 this code is described as indicating "a single-purpose medical device". The code is also used in 11073-20601 to identify the MDS object, but there is no particular description as to its interpretation.

The Device.type shall be encoded as follows:

Device.type.coding.code="65573"
Device.type.coding.system="urn.iso.std.iso:11073:10101"
Device.type.coding.display="MDC_MOC_VMS_MDS_SIMP: Continua Personal Health Device"

The display element is optional but highly recommended.

System Type Spec List

The System-Type-Spec-List attribute contains a list of specializations the PHD complies to. The elements in the list indicate not only what the PHD does, but that it does so in a manner specified in the specialization documents. Each element in the list contains the specialization and its version. The specialization is reported as a 16-bit MDC term code with an assumed partition of INFRA (8) and the version is an interger. In most cases there is just one entry in the list.

For each entry in the System-Type-Spec-List a specializations entry is encoded as follows:

System-Type-Spec-List entry	Device encoding
System-Type-Spec-List.type	specialization.systemType.coding.code="code" specialization.systemType.coding.system="urn.iso.std.iso:11073:10101" specialization.systemType.coding.display"reference-id plus additional text"
System-Type-Spec-List.version	specialization.version="version"

where "code" is the 32-bit nomenclature code computed from the partition INFRA and the term code from System-Type-Spec-List.type and "version" is the version from System-Type-Spec-List.version.

The display element is optional but it is highly recommended that it be included and the reference id be in the description. The table below gives a list of some of the most common specializations and their codes:

Specialization	MDC Code partition:term code	Reference Identifier
Generic 20601 Device	8:4169	MDC_DEV_SPEC_PROFILE_GENERIC
Pulse Oximeter	8::4100	MDC_DEV_SPEC_PROFILE_PULS_OXIM
Electro cardiograph	8::4102	MDC_DEV_SPEC_PROFILE_MIN_ECG
Blood Pressure Cuff	8::4103	MDC_DEV_SPEC_PROFILE_BP
Thermometer	8::4104	MDC_DEV_SPEC_PROFILE_TEMP
Respiration rate	8::4109	MDC_DEV_SPEC_PROFILE_RESP_RATE
Weight Scale	8::4111	MDC_DEV_SPEC_PROFILE_SCALE
Glucose Monitor	8::4113	MDC_DEV_SPEC_PROFILE_GLUCOSE
Coagulation meter	8::4114	MDC_DEV_SPEC_PROFILE_COAG
Insulin Pump	8::4115	MDC_DEV_SPEC_PROFILE_INSULIN_PUMP
Body Composition Analyizer	8::4116	MDC_DEV_SPEC_PROFILE_BCA
Peak Flow meter	8::4117	MDC_DEV_SPEC_PROFILE_PEAK_FLOW
Sleep Apnea Breathing Equipment	8::4120	MDC_DEV_SPEC_PROFILE_SABTE
Continuous Glucose Monitor	8::4121	MDC_DEV_SPEC_PROFILE_CGM
Cardiovascular Device	8::4137	MDC_DEV_SPEC_PROFILE_HF_CARDIO
Strength Equipment	8::4138	MDC_DEV_SPEC_PROFILE_HF_STRENGTH
Independent Activity/Living Hub	8::4167	MDC_DEV_SPEC_PROFILE_AI_ACTIVITY_HUB
Medication Monitor	8::4168	MDC_DEV_SPEC_PROFILE_AI_MED_MINDER

The 'generic' device on the PHD side indicates that the device follows 20601 but not any specialization. On the PHG side it indicates that the PHG understands anything following the 20601 standard. That would include all specializations since all specializations are a subset of the 20601 standard.

The table below gives the set of 32-bit MDC codes and reference identifiers used in the subsequent mappings.

11073 Attribute	description	MDC code	MDC reference identifier
System-Model	Model number	531969	MDC_ID_MODEL_NUMBER
System-Model	Manufacturer name	531970	MDC_ID_MODEL_MANUFACTURER
Production-Specification	Unspecified	531971	MDC_ID_PROD_SPEC_UNSPECIFIED
Production-Specification	Serial number	531972	MDC_ID_PROD_SPEC_SERIAL
Production-Specification	Part number	531973	MDC_ID_PROD_SPEC_PART
Production-Specification	Hardware revision	531974	MDC_ID_PROD_SPEC_HW
Production-Specification	Software revision	531975	MDC_ID_PROD_SPEC_SW
Production-Specification	Firmware revision	531976	MDC_ID_PROD_SPEC_FW
Production-Specification	Protocol revision	531977	MDC_ID_PROD_SPEC_PROTOCOL
Production-Specification	Global Medical Device Nomenclature (GMDN)	531978	MDC_ID_PROD_SPEC_GMDN
Reg-Cert-Data-List	Continua version	532352	MDC_REG_CERT_DATA_CONTINUA_VERSION
Reg-Cert-Data-List	Continua Certified Device List	532353	MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST
Reg-Cert-Data-List	Regulation status	532354	MDC_REG_CERT_DATA_CONTINUA_REG_STATUS
PHG only	Continua Certified H&FS List	532355	MDC_REG_CERT_DATA_CONTINUA_AHD_CERT_LIST
Mds-Time-Info	Synchronization method	68220	MDC_TIME_SYNC_PROTOCOL
Mds-Time-Info	Time capabilities	68219	MDC_TIME_CAP_STATE
Mds-Time-Info	High resolution relative time resolution	68224	MDC_TIME_RES_REL_HI_RES
Mds-Time-Info	Relative time resolution	68223	MDC_TIME_RES_REL
Mds-Time-Info	Absolute Time time resolution	68222	MDC_TIME_RES_ABS
Mds-Time-Info	Base offset time resolution	68226	MDC_TIME_RES_BO
Mds-Time-Info	Time synchronization accuracy	68221	MDC_TIME_SYNC_ACCURACY

System Model

The System-Model attribute contains two strings, the manufacturer name and the model number. The Device resource has stand-alone primitive elements for these two fields. The mapping is straight forward:

System-Model	Device encoding
System-Model.manufacturer	manufacturer="System-Model.manufacturer"
System-Model.model-number	modelNumber="System-Model.model-number"

Production-Specification

The Production-Specification attribute values are mapped to three separate elements in the Device, the Device.serialNumber, Device.partNumber, and Device.version. The serialNumber and partNumber elements are string primitives, thus it is not possible to map the PrivateOid of those two values without extensions. The version element, on the other hand, is a Backbone element which will allow such a mapping without the use of extensions.

The mapping is as follows:

Production-Specification entry	Device encoding
Production-Specification.spec-type = 1 (serial number) Production-Specification.value	serialNumber="Production-Specification.value"
Production-Specification.spec-type = 2 (part number) Production-Specification.value	partNumber="Production-Specification.value"
Production-Specification.spec-type = 3 (hardware version) Production-Specification.PrivateOid Production-Specification.value	version.type.coding.code="531974" version.type.coding.system="urn.iso.std.iso:11073:10101" version.type.coding.display="MDC_ID_PROD_SPEC_HW + optional text"** version.value="Production-Specification.value" version.component.system="system id formatted as above"* version.component.value="Production-Specification.PrivateOid"*
Production-Specification.spec-type = 4 (software version) Production-Specification.PrivateOid Production-Specification.value	version.type.coding.code="531975" version.type.coding.system="urn.iso.std.iso:11073:10101" version.type.coding.display="MDC_ID_PROD_SPEC_SW + optional text"** version.value="Production-Specification.value" version.component.system="system id formatted as above"* version.component.value="Production-Specification.PrivateOid"*
Production-Specification.spec-type = 5 (firmware version) Production-Specification.PrivateOid Production-Specification.value	version.type.coding.code="531976" version.type.coding.system="urn.iso.std.iso:11073:10101" version.type.coding.display="MDC_ID_PROD_SPEC_FW + optional text"** version.value="Production-Specification.value" version.component.system="system id formatted as above"* version.component.value="Production-Specification.PrivateOid"*
Production-Specification.spec-type = 6 (protocol version) Production-Specification.PrivateOid Production-Specification.value	version.type.coding.code="531977" version.type.coding.system="urn.iso.std.iso:11073:10101" version.type.coding.display="MDC_ID_PROD_SPEC_PROTOCOL + optional text"** version.value="Production-Specification.value" version.component.system="system id formatted as above"* version.component.value="Production-Specification.PrivateOid"*

*The PrivateOid is only a 16-bit unsigned number. To give it some meaning, the system-id of the device is placed in the Identifier 'system' value to link the PrivateOid to this physical device in the presence of some other possible identifiers.

**The display elements are optional but it is encouraged to include them and populate them with at least the reference identifier.

Reg-Cert-Data-List

The Reg-Cert-Data-List contains the Continua version, list of certified PAN interfaces, and the regulation status. The Continua version is mapped to an additional Device.version element and the other two fields are mapped to a Device.property element.

Reg-Cert-Data-List Continua version

The Continua version has a major and minor component which are 8-bit unsigned integers. The code reported in the Device.versions element is obtained by concatenating the major-version, a dot (.), and the minor version. For example, "6.1" where "6" is the major version and "1" is the minor version.

The Continua version code is mapped to a Device.version element.

Reg-Cert-Data-List Continua Certified PAN interfaces

The Reg-Cert-Data-List attribute reports the list of Continua certified PAN (Personal Area Network) interfaces as a list of Continua-specified 'PAN' codes. Note there is a difference between certified PAN interfaces and supported PAN interfaces. The Continua-specified certification codes obtained from the Reg-Cert-Data-List are a combination of a transport code, Tcode, and a specialization code which is based on the 16-bit term code of the MDC code for the specialization. The obtained code was generated from

PANCode = Tcode * 8192 + (specialization term code - 4096)

Consumers of the data will need to know this relationship in order to interpret the code.

The transport 'Tcodes' are as follows:

Tcode	Transport
0	Continua version 1.0
1	USB
2	Bluetooth HDP
3	ZigBee
4	Bluetooth Low Energy
5	NFC

The special Tcode of 0 is for Continua version 1.0 when there was no transport component in the reported certified PAN interface codes.

The PANCodes are mapped to a list of property.valueCode elements. The property.type element, which identifies the property, is given by the MDC 32-bit code 532353. Its reference id is MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST.

Reg-Cert-Data-List Regulation Status

The regulation status element is a 16-bit ASN1 BITs 'state' value. At the current time only Mder bit 0 is defined. Being a state value, both set and cleared states are reported. In fact, it is the cleared state which represents that the device is regulated.

The regulation status is mapped to an additional Device.property.valueCode element. The Device.property.type element, which identifies the property, is given by 532354.0 following the ASN1 BITs mapping where the code 532354 is the MDC code for the regulation status. Its reference identifier is MDC_REG_CERT_DATA_CONTINUA_REG_STATUS. The '0' appended to the regulation status code indicates Mder bit 0. The Device.property.valueCode will indicate either "Y" (set) or "N" (cleared).

The following table summarizes the mapping of the Reg-Cert-Data-List information to FHIR:

Reg-Cert-Data-List	Device Mapping
Reg-Cert-Data-List: continuaVersion	version.type.coding.code="532352" version.type.coding.system="urn.iso.std.iso:11073:10101" version.type.coding.display="MDC_REG_CERT_DATA_CONTINUA_VERSION + text" version.value="Continua version code"
Reg-Cert-Data-List: certified PAN interfaces	property.type.coding.code="532353" property.type.coding.system="urn.iso.std.iso:11073:10101" property.type.coding.display="MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST + text" property.valueCodeN.coding.code="PANCodeN" property.valueCodeN.coding.system="placeholder/fhir/reg-cert-codes "
Reg-Cert-Data-List: regulation status	property.type.coding.code="532354.0" property.type.coding.system="placeholder/fhir/IEEE.ASN1" property.type.coding.display="regulation-status" property.valueCode.coding.code="Y/N" property.valueCode.coding.system="http://hl7.org/fhir/v2/0136 " property.valueCode.coding.display="Y=unregulated N=regulated"

Display elements are receommended but optional.

Mds-Time-Info

The Mds-Time-Info attribute is required on PHDs that support a real time clock of some type and report time stamps in their measurements. In Bluetooth Low Energy devices these properties must be inferred from other information like the Current Time Service. If the PHD does NOT report a time stamp in any of its measurements, there is no need to report the static time information.

Time Capabilities

The Mds-Time-Info attribute has a 16-bit ASN1 BITs field for the time capabilities. They are mapped as follows:

Mder Bit position	IEEE.ASN1 Code	ASN.1 name	static	Device.
0	68219.0	mds-time-capab-real-time-clock	yes	property.type.coding.code="68219.0"
1	68219.1	mds-time-capab-set-clock	yes	property.type.coding.code="68219.1"
2	68219.2	mds-time-capab-relative-time	yes	property.type.coding.code="68219.2"
3	68219.3	mds-time-capab-high-res-relative-time	yes	property.type.coding.code="68219.3"
4	68219.4	mds-time-capab-sync-abs-time	yes	property.type.coding.code="68219.4"
5	68219.5	mds-time-capab-sync-rel-time	yes	property.type.coding.code="68219.5"
6	68219.6	mds-time-capab-sync-hi-res-relative-time	yes	property.type.coding.code="68219.6"
7	68219.7	mds-time-capab-bo-time	yes	property.type.coding.code="68219.7"
8	68219.8	mds-time-state-abs-time-synced	no
9	68219.9	mds-time-state-rel-time-synced	no
10	68219.10	mds-time-state-hi-res-relative-time-synced	no
11	68219.11	mds-time-mgr-set-time	no
12	68219.12	mds-time-capab-sync-bo-time	yes	property.type.coding.code="68219.12"
13	68219.13	mds-time-state-bo-time-synced	no
14	68219.14	mds-time-state-bo-time-UTC-aligned	yes	property.type.coding.code="68219.14"
15	68219.15	mds-time-dst-rules-enabled	yes	property.type.coding.code="68219.15"

The required remaining property elements in each reported case are as follows:

property.type.coding.system="placeholder/fhir/IEEE.ASN1"
property.valueCode.coding.code="Y/N"
property.valueCode.coding.system="http://hl7.org/fhir/v2/0136 "

An optional display element containing at least the ASN.1 name from the above table is encouraged:

property.type.coding.display="ASN.1 name + any additional text"

Only the static fields shall be reported and all the static fields are treated as events thus they only need to be reported if set. Reporting cleared static states is optional.

Time Synchronization

The Mds-Time-Info.time-sync-protocol indicates the method of time synchronization which has one of the term code values in the following table:

32-bit code	Reference identifier	description	partition:term code
532224	MDC_TIME_SYNC_NONE	An uncalibrated and unsynchronized local clock source	8::7936
532234	MDC_TIME_SYNC_EBWW	A manually set time, by ‘eyeball and wristwatch’	8::7946
532225	MDC_TIME_SYNC_NTPV3	Network Time Protocol Version 3.0 (RFC 1305)	8::7937
532226	MDC_TIME_SYNC_NTPV4	Network Time Protocol Version 4.0 (under dev)	8::7938
532227	MDC_TIME_SYNC_SNTPV4	Simple Network Time Protocol v4 (RFC 2030)	8::7939
532228	MDC_TIME_SYNC_SNTPV4330	Simple Network Time Protocol v4 (RFC 4330)	8::7940
532229	MDC_TIME_SYNC_BTV1	Bluetooth Medical Device Profile	8::7941
532235	MDC_TIME_SYNC_USB_SOF	Synced to the 1kHz USB "start-of-frame" clock	8::7947
532230	MDC_TIME_SYNC_RADIO	Atomic Clock synchronization through RF	8::7942
532231	MDC_TIME_SYNC_HL7_NCK	Synchronized via Health Level 7 NCK (network clock)	8::7943
532232	MDC_TIME_SYNC_CDMA CDMA	mobile telecommunications synchronization	8::7944
532233	MDC_TIME_SYNC_GSM	GSM - Network Identity and Time Zone (NITZ)	8::7945

If the Mds-Time-Info.time-sync-protocol indicates some other value besides 7936 (no time synchronization) the uploader must look at the time capabilities bits 8, 9, 10, or 13 to see if the PHD actually is synchronized. If the time capabilities bits indicate that the PHD is synchronized, then the time synchronization method in Mds-Time-Info.time-sync-protocol is reported in the Device.property element. Otherwise the uploader reports that the PHD is unsynchronized.

The uploader maps the state of synchronization to the Device.property as follows:

Device.property.type.coding.code="68220"
Device.property.type.coding.system="urn.iso.std.iso:11073:10101"
Device.property.type.coding.display="MDC_TIME_SYNC_PROTOCOL" (optional)
Device.property.valueCode.coding.code="32-bit code for sync method"
Device.property.valueCode.coding.system="urn.iso.std.iso:11073:10101"
Device.property.valueCode.coding.display="the ref id" (optional)

To date there are no PHDs that support an external time synchronization. However, many PHDs have the PHG set its time and PHGs are required to support an external time synchronization. The IEEE PHD WG is working on providing some means to indicate synchronization by the PHG. In lieu of that, a consumer can only infer that the PHG probably set the time on the PHG if

the PHD indicates that set time is supported
the current time clock differences between the PHG and PHD are about 0.

Time Synchronization Accuracy

The time synchronization accuracy is given by the Mds-Time-Info.time-sync-accuracy field. This value shall not be reported if the PHD reports a value of 0xFFFFFFFF which indicates unknown. Otherwise the value reported is in units of 1/8^th millisecond. When reported in the Device.property element it is scaled to microseconds. The mapping is as follows:

Device.property.type.coding.code="68221"
Device.property.type.coding.system="urn.iso.std.iso:11073:10101"
Device.property.type.coding.display="MDC_TIME_SYNC_ACCURACY" (optional)
Device.property.valueQuantity.value="125 x Mds-Time-Info.time-sync-accuracy"
Device.property.valueQuantity.system="http://unitsofmeasure.org"
Device.property.valueQuantity.code="us" (UCUM code for microseconds)

Time Resolution

The Mds-Time-Info attribute has three fields that report the resolution of its time clocks.

The Mds-Time-Info.time-resolution-abs-time represents the resolution of the absolute-time clock when the sensor supports an absolute time clock. If the sensor supports a base-offset time clock it represents the resolution of the base-offset time clock. The sensor is not allowed to support both time clocks simultaneously during an association. Which time clock is supported is indicated by the settings of the Mder 0 and 7 bits of the time capabilities (Mds-Time-Info.mds-time-caps-state).

The sensor may additionally support both relative time clocks or just one or both of the relative time clocks without any ‘wall time’ clock. In practice, support of more than one real time clock at the same time is rare.

If the respective time resolution has a value of 0, it indicates that the resolution is unknown and it shall not be reported. In all other cases, the resolutions are reported.

All time resolution values shall be scaled to units of microseconds. When supporting absolute time, the Mds-Time-Info.time-resolution-abs-time is in units of 1/100th of a second. When supporting base-offset time, the Mds-Time-Info.time-resolution-abs-time is in units of 1/65536th of a second. In the base-offset case, the special value of 0xFFFF means one second. The Mds-Time-Info.time-resolution-rel-time is in units of 1/8th millisecond and the Mds-Time-Info.time-resolution-hi-res-relative-time is in units of microseconds.

The encoding is as follows:

Device.property element	value
Device.property.type.coding.code	"68222" (absolute time) "68226" (base-offset time) "68223" (relative time) "68224" (hi-res relative time)
Device.property.type.coding.system	"urn.iso.std.iso:11073:10101"
Device.property.type.coding.display (optional)	"MDC_TIME_RES_ABS" "MDC_TIME_RES_BO" "MDC_TIME_RES_REL" "MDC_TIME_RES_REL_HI_RES"

Device.property.valueQuantity.value	"10000 x Mds-Time-Info.time-resolution-abs-time" "1000000 x Mds-Time-Info.time-resolution-abs-time/65536" "125 x Mds-Time-Info.time-resolution-rel-time" "Mds-Time-Info.time-resolution-hi-res-relative-time"
Device.property.valueQuantity.system	"http://unitsofmeasure.org"
Device.property.valueQuantity.code	"us" (UCUM code for microseconds)

Consumer of the PHD Device Profile

For the Consumer of this profile the following table gives a quick guide to the main features

item	Location in Device resource
Type of Device	specializations.systemType.coding.code="MDC 32-bit code for device specialization"
Manufacturer name	manufacturer
Model number	modelNumber
serial number	serialNumber
system identifier	identifier.system="urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680" identifier.value="system id as 8 2-digit HEX values separated by dashes"
time synchronization	property.type.coding.code="68220" property.valueCode.coding.code="code for time synchronization"

Phd Device JSON Example

The following is an example of a Phd Device resource from a Blood Pressure Cuff.

{
	"resourceType": "Device",
	"id": "SysId-01040302f0000000",         // This resource is being uploaded as an Update
	"meta": {
		"profile": ["http://pchalliance.org/phdfhir/StructureDefinition/PhdDevice"]
	},
	"identifier": [{
		"system": "urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680",
		"value": "01-04-03-02-f0-00-00-00",
		"assigner": {
			"display": "EUI-64"
		}
	},
	{
		"system": "urn:oid:1.2.840.10004.1.1.1.0.0.1.0.0.1.2680",
		"value": "12-34-56-78-9A-BC",
		"assigner": {
			"display": "EUI-48"
		}
	}],
	"manufacturer": "Renesas Electronics",
	"serialNumber": "13456-BPM-BTLE",
	"deviceName":[{
	    "name": "Continua BP Monitor",
		"type": "user-friendly-name"
		}],
	"modelNumber": "Synergy-12345-Demo",
	"partNumber": "63-555",
	"type": {
		"coding": [{
			"system": "urn:iso:std:iso:11073:10101",
			"code": "65573",
			"display": "MDC_MOC_VMS_MDS_SIMP: Continua Personal Health Device"
		}]
	},
	"specialization": [{
		"systemType": {
		    "coding":[{
				"system": "urn:iso:std:iso:11073:10101",
			    "code": "528391",
			    "display": "MDC_DEV_SPEC_PROFILE_BP: Blood pressure Monitor"
			}]
		},
		"version": "1"
	}],
	"version":[
	{
		"type": {
			"coding": [{
				"system": "urn:iso:std:iso:11073:10101",
				"code": "531976",
				"display": "MDC_ID_PROD_SPEC_FW: Firmware revision"
			}]
		},
		"value": "1.0.0"
	},
	{
		"type": {
			"coding": [{
				"system": "urn:iso:std:iso:11073:10101",
				"code": "531975",
				"display": "MDC_ID_PROD_SPEC_SW: Software revision"
			}]
		},
		"value": "1.0.0"
	},
	{
		"type": {
			"coding": [{
				"system": "urn:iso:std:iso:11073:10101",
				"code": "531974",
				"display": "MDC_ID_PROD_SPEC_HW: Hardware revision"
			}]
		},
		"value": "1.0.0"
	},
	{
		"type": {
			"coding": [{
				"system": "urn:iso:std:iso:11073:10101",
				"code": "532352",
				"display": "MDC_REG_CERT_DATA_CONTINUA_VERSION: Continua version"
			}]
		},
		"value": "6.1"
	}],
	"property": [{
		"type": {
			"coding": [{
				"system": "urn:iso:std:iso:11073:10101",
				"code": "532353",
				"display": "MDC_REG_CERT_DATA_CONTINUA_CERT_DEV_LIST: certified device list as transport-specialization combo"
			}]
		},
		"valueCode": [{
			"coding": [{
				"system": "http://pcha.org/phd/documents/reg-cert-codes",
				"code": "32775"
				// In HEX this is 0x8007 Tcode = 8 which is the code
				// for Bluetooth Low Energy and 4096 + 7 = 4103 which is the term code in partition
				// Infra for the Blood Pressure specialization
			}]
		}]
	},
	{
		"type": {
			"coding": [{
				"system": "http://hl7.org/fhir/IEEE.ASN1",
				"code": "532354.0",
				"display": "regulation-status"
			}]
		},
		"valueCode": [{
			"coding": [{
				"system": "http://hl7.org/fhir/v2/0136",
				"code": "Y",
				"display": "Device is not regulated"
			}]
		}]
	},
	{
		"type": {
			"coding": [{
				"system": "urn:iso:std:iso:11073:10101",
				"code": "68220",
				"display": "MDC_TIME_SYNC_PROTOCOL: Time synchronization protocol"
			}]
		},
		"valueCode": [{
			"coding": [{
				"system": "urn:iso:std:iso:11073:10101",
				"code": "532224",
				"display": "MDC_TIME_SYNC_NONE: "
			}]
		}]
	}]
}