abstractbaseDefinitioncopyrightdate- Values Differ
descriptionexperimentalfhirVersion- Values Differ
jurisdiction
jurisdiction[0]kindnamepublisher- Values Differ
purposestatustitletypeurlversion- Values Differ
| Left: | RTLS Tag Device Profile (http://hl7.org/fhir/uv/rtls/StructureDefinition/rtlsDevice) |
| Right: | RTLS Tag Device Profile (http://hl7.org/fhir/uv/rtls/StructureDefinition/rtlsDevice) |
| Error | StructureDefinition.version | Values for version differ: '1.0.0-ballot' vs '1.0.0-ballot2' |
| Information | StructureDefinition.date | Values for date differ: '2023-03-30T12:51:57+00:00' vs '2025-08-07T17:04:10+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International - Patient Administration Work Group' vs 'HL7 International / Patient Administration' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '5.0.0' vs '4.0.1' |
| Information | StructureDefinition.comment | Values for comment differ: 'Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' |
| Information | StructureDefinition.comment | Values for comment differ: '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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.' vs '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. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Contained resources do not have a 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 information is added later.' vs '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 information is added later.' |
| Information | StructureDefinition.definition | Values for definition differ: 'These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.' vs '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.' vs '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. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the resource. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.definition | Values for definition differ: '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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs '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 and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.comment | Values for comment differ: 'Certain attributes, like serial number and UDI Carrier (the HRF or AIDC barcode string) are not device instance identifiers as they are not consistently able to uniquely identify the instance of a device, thus are not appropriate to be used to value Device.identifier. The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used. The identifier is typically valued if the serialNumber or lotNumber is not valued and represents a different type of identifier. However, it is permissible to still include those identifiers in DeviceDefinition.identifier with the appropriate identifier.type.' vs 'The barcode string from a barcode present on a device label or package may identify the instance, include names given to the device in local usage, or may identify the type of device. If the identifier identifies the type of device, Device.type element should be used.' |
| Information | StructureDefinition.comment | Values for comment differ: 'UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](device-mappings.html#udi) for a complete mapping of UDI parts to Device.' vs 'UDI may identify an unique instance of a device, or it may only identify the type of the device. See [UDI mappings](http://hl7.org/fhir/R4/device-mappings.html#udi) for a complete mapping of UDI parts to Device.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.definition | Values for definition differ: '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' |
| Information | Device.udiCarrier.deviceIdentifier | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.definition | Values for definition differ: 'Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include: 1) GS1: http://hl7.org/fhir/NamingSystem/gs1-di, 2) HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-diI, 3) ICCBBA for blood containers: http://hl7.org/fhir/NamingSystem/iccbba-blood-di, 4) ICCBA for other devices: http://hl7.org/fhir/NamingSystem/iccbba-other-di # Informationsstelle für Arzneispezialitäten (IFA GmbH) (EU only): http://hl7.org/fhir/NamingSystem/ifa-gmbh-di.' vs 'Organization that is charged with issuing UDIs for devices. For example, the US FDA issuers include : 1) GS1: http://hl7.org/fhir/NamingSystem/gs1-di, 2) HIBCC: http://hl7.org/fhir/NamingSystem/hibcc-dI, 3) ICCBBA for blood containers: http://hl7.org/fhir/NamingSystem/iccbba-blood-di, 4) ICCBA for other devices: http://hl7.org/fhir/NamingSystem/iccbba-other-di.' |
| Information | Device.udiCarrier.issuer | Element minimum cardinalities differ: '1' vs '0' |
| Information | StructureDefinition.definition | Values for definition differ: 'The identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/us-fda-udi or in the European Union by the European Commission http://hl7.org/fhir/NamingSystem/eu-ec-udi.' vs 'The identity of the authoritative source for UDI generation within a jurisdiction. All UDIs are globally unique within a single namespace with the appropriate repository uri as the system. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi.' |
| Information | StructureDefinition.short | Values for short differ: 'barcode | rfid | manual | card | self-reported | electronic-transmission | unknown' vs 'barcode | rfid | manual +' |
| Information | StructureDefinition.definition | Values for definition differ: 'The Device record status. This is not the status of the device like availability.' vs 'Status of the Device availability.' |
| Information | StructureDefinition.definition | Values for definition differ: 'A name of the manufacturer or entity legally responsible for the device.' vs 'A name of the manufacturer.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Alphanumeric Maximum 20. While a serial number is a type of identifier, in the context of devices for which a UDI is required, thus a serial number may be part of the production identifier, it is more informative to have the serial number as a dedicated attribute together with the other UDI production identifier. When the device is not subject to including the UDI (e.g., its presence and exchange is not mandated by local regulatory requirements or specific use case at hand), thus the concept of production identifiers is not relevant as a set, it remains helpful for consistency to still use Device.serialNumber rather than using Device.identifier with an appropriate type. Systems that do not realize an identifier is a serial number may place it in Device.identifier or if the identifier.system is known for the serial number, it may also be populated in the Device.identifier as a globally unique id_.' vs 'Alphanumeric Maximum 20.' |
| Information | StructureDefinition.short | Values for short differ: 'The manufacturer's model number for the device' vs 'The model number for the device' |
| Information | StructureDefinition.definition | Values for definition differ: 'The manufacturer's model number for the device.' vs 'The model number for the device.' |
| Information | StructureDefinition.short | Values for short differ: 'The part number or catalog number of the device' vs 'The part number of the device' |
| Information | StructureDefinition.definition | Values for definition differ: 'The part number or catalog number of the device.' vs 'The part number of the device.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The kind or type of device. A device instance may have more than one type - in which case those are the types that apply to the specific instance of the device.' vs 'The kind or type of device.' |
| Information | Device.type | Element maximum cardinalities differ: '2147483647' vs '1' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.definition | Values for definition differ: '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.short | Values for short differ: 'The type of the device version, e.g. manufacturer, approved, internal' vs 'The type of the device version' |
| Information | StructureDefinition.definition | Values for definition differ: 'The type of the device version, e.g. manufacturer, approved, internal.' vs 'The type of the device version.' |
| Information | StructureDefinition.short | Values for short differ: 'The hardware or software module of the device to which the version applies' vs 'A single component of the device version' |
| Information | StructureDefinition.definition | Values for definition differ: 'The hardware or software module of the device to which the version applies.' vs 'A single component of the device version.' |
| Information | StructureDefinition.short | Values for short differ: 'Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc.' vs 'The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties' |
| Information | StructureDefinition.definition | Values for definition differ: 'Static or essentially fixed characteristics or features of the device (e.g., time or timing attributes, resolution, accuracy, intended use or instructions for use, and physical attributes) that are not otherwise captured in more specific attributes.' vs 'The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.' |
| Information | StructureDefinition.definition | Values for definition differ: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. 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 can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' |
| Information | StructureDefinition.definition | Values for definition differ: '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' vs '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 in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 can 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. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).' vs 'Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.short | Values for short differ: 'Code that specifies the property being represented' vs 'Code that specifies the property DeviceDefinitionPropetyCode (Extensible)' |
| Information | StructureDefinition.definition | Values for definition differ: 'Code that specifies the property, such as resolution, color, size, being represented.' vs 'Code that specifies the property DeviceDefinitionPropetyCode (Extensible).' |
| Information | StructureDefinition.short | Values for short differ: 'The higher level or encompassing device that this device is a logical part of' vs 'The parent device' |
| Information | StructureDefinition.definition | Values for definition differ: 'The higher level or encompassing device that this device is a logical part of.' vs 'The parent device.' |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/Device | ||
| copyright | |||
| date | 2023-03-30T12:51:57+00:00 | 2025-08-07T17:04:10+00:00 |
|
| description | Device resource profile for tags or badges in RTLS workflows | ||
| experimental | true | ||
| fhirVersion | 5.0.0 | 4.0.1 |
|
| jurisdiction | |||
| jurisdiction[0] | http://unstats.un.org/unsd/methods/m49/m49.htm#001 | ||
| kind | resource | ||
| name | RTLSDevice | ||
| publisher | HL7 International - Patient Administration Work Group | HL7 International / Patient Administration |
|
| purpose | This profile defines minimum expectations for the Device resource to be used in RTLS workflows. | ||
| status | draft | ||
| title | RTLS Tag Device Profile | ||
| type | Device | ||
| url | http://hl7.org/fhir/uv/rtls/StructureDefinition/rtlsDevice | ||
| version | 1.0.0-ballot | 1.0.0-ballot2 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Device | C | 0..* | Device | Item used in healthcare | 0..* | Device | Item used in healthcare | ||||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | |||||||||
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | |||||||||
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | |||||||||
| language | 0..1 | code | Language of the resource content Binding: ?? (required): IETF language tag for a human language
| 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||||||
| text | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | 0..1 | Narrative | Text summary of the resource, for human interpretation This profile does not constrain the narrative in regard to content, language, or traceability to data elements | |||||||||||
| contained | 0..* | Resource | Contained, inline Resources | 0..* | Resource | Contained, inline Resources | |||||||||||
 extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
 modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored | |||||||||
 identifier | S | 1..* | Identifier | Instance identifier | S | 1..* | Identifier | Instance identifier | |||||||||
 id | 0..1 | string | Unique id for inter-element referencing |
| |||||||||||||
| Slices for extension | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url |
| |||||||||||||
| use | ?!Σ | 0..1 | code | usual | official | temp | secondary | old (If known) Binding: ?? (required): Identifies the purpose for this identifier, if known . |
| ||||||||||||
| type | Σ | 0..1 | CodeableConcept | Description of identifier Binding: ?? (extensible): A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. |
| ||||||||||||
| system | SΣ | 1..1 | uri | The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient |
| ||||||||||||
| value | SΣ | 1..1 | string | The value that is unique Example General: 123456 |
| ||||||||||||
| period | Σ | 0..1 | Period | Time period when id is/was valid for use |
| ||||||||||||
| assigner | Σ | 0..1 | Reference(Organization) | Organization that issued id (may be just text) |
| ||||||||||||
| displayName | 0..1 | string | The name used to display by default when the device is referenced |
| |||||||||||||
| definition | 0..1 | CodeableReference(DeviceDefinition) | The reference to the definition for the device | 0..1 | Reference(DeviceDefinition) | The reference to the definition for the device | |||||||||||
| udiCarrier | Σ | 0..* | BackboneElement | Unique Device Identifier (UDI) Barcode string | Σ | 0..* | BackboneElement | Unique Device Identifier (UDI) Barcode string | |||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| deviceIdentifier | Σ | 1..1 | string | Mandatory fixed portion of UDI | Σ | 0..1 | string | Mandatory fixed portion of UDI |
| ||||||||
| issuer | Σ | 1..1 | uri | UDI Issuing Organization | 0..1 | uri | UDI Issuing Organization |
| |||||||||
| jurisdiction | 0..1 | uri | Regional UDI authority | 0..1 | uri | Regional UDI authority | |||||||||||
| carrierAIDC | Σ | 0..1 | base64Binary | UDI Machine Readable Barcode String | Σ | 0..1 | base64Binary | UDI Machine Readable Barcode String | |||||||||
| carrierHRF | Σ | 0..1 | string | UDI Human Readable Barcode String | Σ | 0..1 | string | UDI Human Readable Barcode String | |||||||||
| entryType | 0..1 | code | barcode | rfid | manual | card | self-reported | electronic-transmission | unknown Binding: ?? (required): Codes to identify how UDI data was entered. | 0..1 | code | barcode | rfid | manual + Binding: ?? (required): Codes to identify how UDI data was entered. | |||||||||||
| status | ?!Σ | 0..1 | code | A status of "active" indicates that a tracking tag is in use (regardless of current assignment to a subject) and "inactive" indicates that a tracking tag is no longer in use. Binding: ?? (required): The record status of the device. | ?!Σ | 0..1 | code | A status of "active" indicates that a tracking tag is in use (regardless of current assignment to a subject) and "inactive" indicates that a tracking tag is no longer in use. Binding: ?? (required): The availability status of the device. | |||||||||
| availabilityStatus | 0..1 | CodeableConcept | lost | damaged | destroyed | available Binding: ?? (extensible): The availability status reason of the device. |
| |||||||||||||
| biologicalSourceEvent | 0..1 | Identifier | An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled |
| |||||||||||||
| manufacturer | 0..1 | string | Name of device manufacturer | 0..1 | string | Name of device manufacturer | |||||||||||
| manufactureDate | 0..1 | dateTime | Date when the device was made | 0..1 | dateTime | Date when the device was made | |||||||||||
| expirationDate | 0..1 | dateTime | Date and time of expiry of this device (if applicable) | 0..1 | dateTime | Date and time of expiry of this device (if applicable) | |||||||||||
| lotNumber | 0..1 | string | Lot number of manufacture | 0..1 | string | Lot number of manufacture | |||||||||||
| serialNumber | 0..1 | string | Serial number assigned by the manufacturer | 0..1 | string | Serial number assigned by the manufacturer | |||||||||||
| name | C | 0..* | BackboneElement | The name or names of the device as known to the manufacturer and/or patient |
| ||||||||||||
| modelNumber | 0..1 | string | The manufacturer's model number for the device | 0..1 | string | The model number for the device | |||||||||||
| partNumber | 0..1 | string | The part number or catalog number of the device | 0..1 | string | The part number of the device | |||||||||||
| category | 0..* | CodeableConcept | Indicates a high-level grouping of the device Binding: ?? (example): Categories of medical devices. |
| |||||||||||||
| type | 0..* | CodeableConcept | The kind or type of device Binding: ?? (example): Codes to identify medical devices. | 0..1 | CodeableConcept | The kind or type of device Binding: ?? (example): Codes to identify medical devices. |
| ||||||||||
| version | 0..* | BackboneElement | The actual design of the device or software version running on the device | 0..* | BackboneElement | The actual design of the device or software version running on the device | |||||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| type | 0..1 | CodeableConcept | The type of the device version, e.g. manufacturer, approved, internal Binding: ?? (example): The type of version indicated for the device. | 0..1 | CodeableConcept | The type of the device version | |||||||||||
| component | 0..1 | Identifier | The hardware or software module of the device to which the version applies | 0..1 | Identifier | A single component of the device version | |||||||||||
| installDate | 0..1 | dateTime | The date the version was installed on the device |
| |||||||||||||
| value | 1..1 | string | The version text | 1..1 | string | The version text | |||||||||||
| conformsTo | 0..* | BackboneElement | Identifies the standards, specifications, or formal guidances for the capabilities supported by the device |
| |||||||||||||
| property | 0..* | BackboneElement | Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. | 0..* | BackboneElement | The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties | |||||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 0..1 | string | Unique id for inter-element referencing | |||||||||||
| extension | 0..* | Extension | Additional content defined by implementations | 0..* | Extension | Additional content defined by implementations | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | |||||||||
| type | 1..1 | CodeableConcept | Code that specifies the property being represented Binding: ?? (example): Device property type. | 1..1 | CodeableConcept | Code that specifies the property DeviceDefinitionPropetyCode (Extensible) | |||||||||||
| value[x] | 1..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Attachment | Value of the property |
| |||||||||||||
| valueQuantity | 0..* | Quantity | Property value as a quantity |
| |||||||||||||
| valueCode | 0..* | CodeableConcept | Property value as a code, e.g., NTP4 (synced to NTP) |
| |||||||||||||
| mode | 0..1 | CodeableConcept | The designated condition for performing a task Binding: ?? (example): Operational mode of a device. |
| |||||||||||||
| cycle | 0..1 | Count | The series of occurrences that repeats during the operation of the device |
| |||||||||||||
| duration | 0..1 | Duration | A measurement of time during the device's operation (e.g., days, hours, mins, etc.) |
| |||||||||||||
| owner | 0..1 | Reference(Organization) | Organization responsible for device | 0..1 | Reference(Organization) | Organization responsible for device | |||||||||||
| contact | 0..* | ContactPoint | Details for human/organization for support | 0..* | ContactPoint | Details for human/organization for support | |||||||||||
| location | S | 0..1 | Reference(RTLS Location Resource Profile) | Where the device is found | S | 0..1 | Reference(RTLS Location Resource Profile) | Where the device is found | |||||||||
| url | 0..1 | uri | Network address to contact device | 0..1 | uri | Network address to contact device | |||||||||||
| endpoint | 0..* | Reference(Endpoint) | Technical endpoints providing access to electronic services provided by the device |
| |||||||||||||
| gateway | 0..* | CodeableReference(Device) | Linked device acting as a communication/data collector, translator or controller |
| |||||||||||||
| note | 0..* | Annotation | Device notes and comments | 0..* | Annotation | Device notes and comments | |||||||||||
| safety | Σ | 0..* | CodeableConcept | Safety Characteristics of Device Binding: ?? (example) | Σ | 0..* | CodeableConcept | Safety Characteristics of Device | |||||||||
| parent | 0..1 | Reference(Device) | The higher level or encompassing device that this device is a logical part of | 0..1 | Reference(Device) | The parent device | |||||||||||
| statusReason | 0..* | CodeableConcept | online | paused | standby | offline | not-ready | transduc-discon | hw-discon | off Binding: ?? (extensible): The availability status reason of the device. |
| |||||||||||||
| distinctIdentifier | 0..1 | string | The distinct identification string |
| |||||||||||||
| deviceName | 0..* | BackboneElement | The name of the device as given by the manufacturer |
| |||||||||||||
| specialization | 0..* | BackboneElement | The capabilities supported on a device, the standards to which the device conforms for a particular purpose, and used for the communication |
| |||||||||||||
| patient | 0..1 | Reference(Patient) | Patient to whom Device is affixed |
| |||||||||||||
| Documentation for this format | |||||||||||||||||