abstractbaseDefinitioncopyrightdatedescriptionexperimentalfhirVersion- Values Differ
jurisdiction
jurisdiction[0]kindnamepublisherpurposestatustitletypeurlversion- Values Differ
| Left: | PhgDevice (http://hl7.org/fhir/uv/phd/StructureDefinition/PhgDevice) |
| Right: | PhgDevice (http://hl7.org/fhir/uv/phd/StructureDefinition/PhgDevice) |
| Error | StructureDefinition.version | Values for version differ: '2.0.0' vs '3.0.0-draft' |
| Warning | StructureDefinition.fhirVersion | Values for fhirVersion differ: '4.0.1' vs '6.0.0-ballot5' |
| Information | StructureDefinition.comment | Values for comment differ: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.' vs '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 resource id depends on the given use case.' |
| Information | StructureDefinition.definition | Values for definition differ: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc. For DomainResources, if more than one implicitRules policy applies, additional policies may be conveyed using the [additionalImplicitRules](https://build.fhir.org/ig/HL7/fhir-extensions/StructureDefinition-additionalImplicitRules.html) extension.' |
| 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 it's 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 its narrative along with other profiles, value sets, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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.' |
| 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, and nor can they have their own independent transaction scope.' vs '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.' |
| 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. Contained resources may be a resource type defined in the FHIR specification, or an [additional resource](http://build.fhir.org/resource.html#additional).' |
| 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 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.' 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 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.' |
| 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 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).' 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 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).' |
| 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/R4/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://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' vs '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.' |
| 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 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.' 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 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.' |
| Information | StructureDefinition.definition | Values for definition differ: 'Establishes the namespace for the value - that is, a URL that describes a set values that are unique.' vs 'Establishes the namespace for the value - that is, an absolute URL that describes a set values that are unique.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Identifier.system is always case sensitive.' vs 'Identifier.system is always case sensitive. The FHIR specification, terminology.hl7.org and HL7 affiliates (for identifiers specific to their jurisdiction) define identifier systems that SHALL be used for certain types of identifiers. Specific rules can be found [here](http://build.fhir.org/identifier-registry.html).' |
| Information | StructureDefinition.comment | Values for comment differ: 'If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value extension](http://hl7.org/fhir/R4/extension-rendered-value.html). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processer to be confident that non-case-sensitive processing is safe.' vs 'If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the [Rendered Value](https://build.fhir.org/ig/HL7/fhir-extensions/StructureDefinition-rendered-value.html)). Identifier.value is to be treated as case sensitive unless knowledge of the Identifier.system allows the processor to be confident that non-case-sensitive processing is safe.' |
| Information | StructureDefinition.short | Values for short differ: 'Unique Device Identifier (UDI) Barcode string' vs 'Unique Device Identifier (UDI) value' |
| Information | StructureDefinition.definition | Values for definition differ: 'Unique device identifier (UDI) assigned to device label or package. Note that the Device may include multiple udiCarriers as it either may include just the udiCarrier for the jurisdiction it is sold, or for multiple jurisdictions it could have been sold.' vs 'Unique Device Identifier (UDI) placed on a device label or package. Note that the Device may include multiple UDIs if it is sold in multiple jurisdictions.' |
| 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](http://hl7.org/fhir/R4/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://build.fhir.org/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 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.' 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 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.' |
| 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 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).' 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 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).' |
| 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/R4/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://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.definition | Values for definition differ: 'The device identifier (DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.' vs 'The device identifier (UDI-DI) is a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device. The UDI-DI portion is placed on a device label or package. Note that the DeviceDefinition may include multiple UDI-DIs if it is sold in multiple jurisdictions.' |
| Information | Device.udiCarrier.deviceIdentifier | Element minimum cardinalities differ: '0' vs '1' |
| 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-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.' 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-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.' |
| Information | Device.udiCarrier.issuer | Element minimum cardinalities differ: '0' vs '1' |
| 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/fda-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/us-fda-udi or in the European Union by the European Commission http://hl7.org/fhir/NamingSystem/eu-ec-udi.' |
| Information | StructureDefinition.short | Values for short differ: 'UDI Machine Readable Barcode String' vs 'UDI Machine Readable value' |
| Information | StructureDefinition.definition | Values for definition differ: 'The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation of the barcode string as printed on the packaging of the device - e.g., a barcode or RFID. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC Formats *SHALL* be base64 encoded.' vs 'The full UDI carrier of the Automatic Identification and Data Capture (AIDC) technology representation as printed on the packaging of the device - e.g., a barcode , 2D Matrix, or RFID. Some AIDC representations contain non-printable characters and cannot be represented in a string format. For this reason, AIDC format SHALL be base64Binary encoded.' |
| Information | StructureDefinition.short | Values for short differ: 'UDI Human Readable Barcode String' vs 'UDI Human Readable value' |
| Information | StructureDefinition.definition | Values for definition differ: 'The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.' vs 'The full UDI carrier as the human readable form (HRF) representation as printed on the packaging of the device.' |
| Information | StructureDefinition.short | Values for short differ: 'barcode | rfid | manual +' vs 'barcode | rfid | manual | card | self-reported | electronic-transmission | unknown' |
| Information | StructureDefinition.definition | Values for definition differ: 'Status of the Device availability.' vs 'The Device record status. This is not the status of the device like availability.' |
| Information | StructureDefinition.definition | Values for definition differ: 'A name of the manufacturer.' vs 'A name of the manufacturer or entity legally responsible for the device.' |
| Information | StructureDefinition.short | Values for short differ: 'Date when the device was made' vs 'A production identifier that indicates the date when the device was made' |
| Information | StructureDefinition.short | Values for short differ: 'Date and time of expiry of this device (if applicable)' vs 'A production identifier that indicates the date and time of expiry of this device (if applicable)' |
| Information | StructureDefinition.short | Values for short differ: 'Lot number of manufacture' vs 'A production identifier that indicates the Lot number of manufacture' |
| Information | StructureDefinition.short | Values for short differ: 'Serial number assigned by the manufacturer' vs 'A production identifier that indicates the Serial number assigned by the manufacturer' |
| Information | StructureDefinition.comment | Values for comment differ: 'Alphanumeric Maximum 20.' vs '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_.' |
| Information | StructureDefinition.short | Values for short differ: 'The model number for the device' vs 'The manufacturer's model number for the device' |
| Information | StructureDefinition.definition | Values for definition differ: 'The model number for the device.' vs 'The manufacturer's model number for the device.' |
| Information | StructureDefinition.short | Values for short differ: 'The part number of the device' vs 'The part number or catalog number of the device' |
| Information | StructureDefinition.definition | Values for definition differ: 'The part number of the device.' vs 'The part number or catalog number of the device.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The kind or type of device.' vs '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.' |
| Information | Device.type | Element maximum cardinalities differ: '1' vs '2147483647' |
| 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 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.' 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 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.' |
| Information | StructureDefinition.short | Values for short differ: 'The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties' vs 'Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties.' vs '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.' |
| 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 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.' 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 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.' |
| 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 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).' 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 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).' |
| 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/R4/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://build.fhir.org/extensibility.html#modifierExtension).' |
| Information | StructureDefinition.short | Values for short differ: 'Code that specifies the property DeviceDefinitionPropetyCode (Extensible)' vs 'Code that specifies the property being represented' |
| Information | StructureDefinition.definition | Values for definition differ: 'Code that specifies the property DeviceDefinitionPropetyCode (Extensible).' vs 'Code that specifies the property, such as resolution, color, size, being represented.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The parent device.' vs 'The higher level or encompassing device that this device is a logical part of.' |
| Name | Value | Comments | |
|---|---|---|---|
| abstract | false | ||
| baseDefinition | http://hl7.org/fhir/StructureDefinition/Device | ||
| copyright | |||
| date | 2017-07-07T11:39:51.3383228-04:00 | ||
| description | Profile for the Device Resource for a PHG | ||
| experimental | |||
| fhirVersion | 4.0.1 | 6.0.0-ballot5 |
|
| jurisdiction | |||
| jurisdiction[0] | http://unstats.un.org/unsd/methods/m49/m49.htm#001 | ||
| kind | resource | ||
| name | PhgDevice | ||
| publisher | HL7 International / Devices | ||
| purpose | This resource describes the primary features of the Personal Health Gateway (PHG). A PHG does not have any IEEE 11073-10206 Objects or attributes though it is required to have a system identifier. However, for the purposes of reporting the information about the PHG entity, it is treated as if it can provide system information, clock and power source information. For compliance with this IG, the quantities that are required to be reported are the system identifier, the time synchronization method, the manufacturer and model number (of the software, not necessarily the hardware on which the application resides), and the PCHA certified interfaces. | ||
| status | active | ||
| title | |||
| type | Device | ||
| url | http://hl7.org/fhir/uv/phd/StructureDefinition/PhgDevice | ||
| version | 2.0.0 | 3.0.0-draft |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Device | 0..* | Device | Item used in healthcare | C | 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: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (required): IETF language tag for 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 Slice: Unordered, Open by value:url | |||||||||||
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?!Σ | 0..* | Extension | Extensions that cannot be ignored Slice: Unordered, Open by value:url | |||||||||
 Slices for identifier | 1..* | Identifier | Information that uniquely describes the personal health device Slice: Unordered, Open by value:type | 1..* | Identifier | Information that uniquely describes the personal health device Slice: Unordered, Open by value:type | |||||||||||
 id | 0..1 | string | Unique id for inter-element referencing | 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 | 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 . | ?!Σ | 0..1 | code | usual | official | temp | secondary | old (If known) Binding: ?? (required): Identifies the purpose for this identifier, if known . | |||||||||
| type | Σ | 0..1 | CodeableConcept | The type of identifier Binding: ?? (extensible) | Σ | 0..1 | CodeableConcept | The type of identifier Binding: ?? (extensible): MDC Device Identifier Types | |||||||||
| system | Σ | 0..1 | uri | The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient | Σ | 0..1 | uri | The namespace for the identifier value Example General: http://www.acme.com/identifiers/patient | |||||||||
| value | Σ | 0..1 | string | The value that is unique Example General: 123456 | ΣC | 0..1 | string | The value that is unique Example General: 123456 | |||||||||
| period | Σ | 0..1 | Period | Time period when id is/was valid for use | Σ | 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) | Σ | 0..1 | Reference(Organization) | Organization that issued id (may be just text) | |||||||||
| definition | 0..1 | Reference(DeviceDefinition) | The reference to the definition for the device | 0..1 | canonical(DeviceDefinition) | The reference to the definition for the device | |||||||||||
| udiCarrier | Σ | 0..* | BackboneElement | Unique Device Identifier (UDI) Barcode string | Σ | 0..* | BackboneElement | Unique Device Identifier (UDI) value | |||||||||
| 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 Slice: Unordered, Open by value:url | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized Slice: Unordered, Open by value:url | |||||||||
| deviceIdentifier | Σ | 0..1 | string | Mandatory fixed portion of UDI | Σ | 1..1 | string | Mandatory fixed portion of UDI |
| ||||||||
| issuer | 0..1 | uri | UDI Issuing Organization | Σ | 1..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 value | |||||||||
| carrierHRF | Σ | 0..1 | string | UDI Human Readable Barcode String | Σ | 0..1 | string | UDI Human Readable value | |||||||||
| entryType | 0..1 | code | barcode | rfid | manual + Binding: ?? (required): Codes to identify how UDI data was entered. | 0..1 | code | barcode | rfid | manual | card | self-reported | electronic-transmission | unknown Binding: ?? (required): Codes to identify how UDI data was entered. | |||||||||||
| deviceIdentifierSystem | 0..1 | uri | The namespace for the device identifier value |
| |||||||||||||
| status | ?!Σ | 0..1 | code | active | inactive | entered-in-error | unknown Binding: ?? (required): The availability status of the device. | ?!Σ | 0..1 | code | active | inactive | entered-in-error | unknown Binding: ?? (required): The record status of the 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 |
| |||||||||||||
| 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 | A production identifier that indicates the date when the device was made | |||||||||||
| expirationDate | 0..1 | dateTime | Date and time of expiry of this device (if applicable) | 0..1 | dateTime | A production identifier that indicates the date and time of expiry of this device (if applicable) | |||||||||||
| lotNumber | 0..1 | string | Lot number of manufacture | 0..1 | string | A production identifier that indicates the Lot number of manufacture | |||||||||||
| serialNumber | 0..1 | string | Serial number assigned by the manufacturer | 0..1 | string | A production identifier that indicates the Serial number assigned by the manufacturer | |||||||||||
| deviceName | 0..* | BackboneElement | The name of the device as given by the manufacturer |
| |||||||||||||
| modelNumber | 0..1 | string | The model number for the device | 0..1 | string | The manufacturer's model number for the device | |||||||||||
| partNumber | 0..1 | string | The part number of the device | 0..1 | string | The part number or catalog number of the device | |||||||||||
| type | 1..1 | CodeableConcept | Indicates the device is a PHG. Binding: ?? (example): Codes to identify medical devices. | 1..* | CodeableConcept | Indicates the device is a PHG. Binding: ?? (example): Codes to identify medical devices. |
| ||||||||||
| id | 0..1 | string | Unique id for inter-element referencing | 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 | 0..* | Extension | Additional content defined by implementations Slice: Unordered, Open by value:url | |||||||||||
| Slices for coding | Σ | 1..* | Coding | Code defined by a terminology system Slice: Unordered, Open by value:system | Σ | 1..* | Coding | Code defined by a terminology system Slice: Unordered, Open by value:system | |||||||||
| text | Σ | 0..1 | string | Plain text representation of the concept | Σ | 0..1 | string | Plain text representation of the concept | |||||||||
| Slices for specialization | 1..* | BackboneElement | This element contains an entry for each supported specialization or a generic representation. Slice: Unordered, Open by value:systemType.coding |
| |||||||||||||
| Slices for version | 1..* | BackboneElement | A PHG may report firmware, hardware, software, internal protocol, nomenclature and ACOM versions. Slice: Unordered, Open by value:type.coding |
| |||||||||||||
| Slices for property | 0..* | BackboneElement | The actual configuration settings of a device as it actually operates, e.g., regulation status, time properties Slice: Unordered, Open by value:type | 0..* | BackboneElement | Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. Slice: Unordered, Open by value:type | |||||||||||
| 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 Slice: Unordered, Open by value:url | |||||||||||
| modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized Slice: Unordered, Open by value:url | |||||||||
| type | 1..1 | CodeableConcept | Code that specifies the property DeviceDefinitionPropetyCode (Extensible) | 1..1 | CodeableConcept | Code that specifies the property being represented Binding: ?? (example): Device property type. | |||||||||||
| valueQuantity | 0..* | Quantity | Property value as a quantity |
| |||||||||||||
| valueCode | 0..* | CodeableConcept | Property value as a code, e.g., NTP4 (synced to NTP) |
| |||||||||||||
| value[x] | 1..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Attachment | Value of the property |
| |||||||||||||
| patient | 0..1 | Reference(Patient) | Patient to whom Device is affixed |
| |||||||||||||
| owner | 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 | 0..1 | Reference(Location) | Where the device is found | 0..1 | Reference(Location) | Where the device is found | |||||||||||
| url | 0..1 | uri | Network address to contact device |
| |||||||||||||
| note | 0..* | Annotation | Device notes and comments | 0..* | Annotation | Device notes and comments | |||||||||||
| safety | Σ | 0..* | CodeableConcept | Safety Characteristics of Device | Σ | 0..* | CodeableConcept | Safety Characteristics of Device Binding: ?? (example) | |||||||||
| parent | 0..0 | No reference to a parent device in PHG. PHGs are not part of a device hierarchy. | 0..0 | No reference to a parent device in PHG. PHGs are not part of a device hierarchy. | |||||||||||||
| availabilityStatus | 0..1 | CodeableConcept | lost | damaged | destroyed | available Binding: ?? (preferred): The availability status reason of the device. |
| |||||||||||||
| biologicalSourceEvent | 0..1 | Identifier | A production identifier of the donor, donation, or pooling event associated with the biological material incorporated into the device |
| |||||||||||||
| name | C | 0..* | BackboneElement | The name or names of the device as known to the manufacturer and/or patient |
| ||||||||||||
| category | 0..* | CodeableConcept | Indicates a high-level grouping of the device Binding: ?? (example): Categories of medical devices. |
| |||||||||||||
| Slices for deviceVersion | 1..* | BackboneElement | A PHG may report firmware, hardware, software, internal protocol, nomenclature and ACOM versions. Slice: Unordered, Open by value:type.coding |
| |||||||||||||
| Slices for conformsTo | 1..* | BackboneElement | This element contains an entry for each supported specialization or a generic representation. Slice: Unordered, Open by value:specification.coding |
| |||||||||||||
| additive | 0..* | BackboneElement | Material added to a container device |
| |||||||||||||
| Documentation for this format | |||||||||||||||||