Generated Narrative: StructureDefinition profile-Device Name Flags Card. Type Description & Constraints Device 0..* Device Item used in healthcare #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:definition 0..1 (Complex) R5: The reference to the definition for the device (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.definition #xD; extension:availabilityStatus 0..1 CodeableConcept R5: lost | damaged | destroyed | available (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.availabilityStatus Binding: R5DeviceAvailabilityStatusForR3 (0.1.0) (extensible): The availability status reason of the device. #xD; extension:biologicalSourceEvent 0..1 Identifier R5: An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.biologicalSourceEvent #xD; extension:serialNumber 0..1 string R5: Serial number assigned by the manufacturer (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.serialNumber #xD; extension:partNumber 0..1 string R5: The part number or catalog number of the device (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.partNumber #xD; extension:category 0..* CodeableConcept R5: Indicates a high-level grouping of the device (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.category Binding: R5DeviceCategoryForR3 (0.1.0) (example): Categories of medical devices. #xD; extension:conformsTo 0..* ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/device-conformsTo]] R5: Identifies the standards, specifications, or formal guidances for the capabilities supported by the device (new) URL: http://hl7.org/fhir/StructureDefinition/device-conformsTo #xD; extension:property 0..* (Complex) R5: Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.property #xD; extension:mode 0..1 CodeableConcept R5: The designated condition for performing a task (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.mode Binding: R5DeviceOperationModeForR3 (0.1.0) (example): Operational mode of a device. #xD; extension:cycle 0..1 Count R5: The series of occurrences that repeats during the operation of the device (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.cycle #xD; extension:duration 0..1 Duration R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.duration #xD; extension:endpoint 0..* Reference(Cross-version Profile for R5.Endpoint for use in FHIR STU3(0.1.0) | Endpoint) R5: Technical endpoints providing access to electronic services provided by the device (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.endpoint #xD; extension:gateway 0..* (Complex) R5: Linked device acting as a communication/data collector, translator or controller (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.gateway #xD; extension:parent 0..1 Reference(Cross-version Profile for R5.Device for use in FHIR STU3(0.1.0) | Device) R5: The higher level or encompassing device that this device is a logical part of (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.parent #xD; udi #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:displayName 0..1 string R5: The name used to display by default when the device is referenced additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.displayName #xD; extension:value 1..1 string R5: The term that names the device additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.name.value #xD; extension:type 1..1 code R5: registered-name | user-friendly-name | patient-reported-name (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.name.type Binding: R5DeviceNametypeForR3 (0.1.0) (required): The type of name the device is referred by. #xD; Slices for modifierExtension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; modifierExtension:display 0..1 boolean R5: The preferred device name additional types URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.name.display #xD; entryType #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:entryType 0..1 code R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown additional codes URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.udiCarrier.entryType Binding: R5UdiEntryTypeForR3 (0.1.0) (required): Codes to identify how UDI data was entered. #xD; version #xD; Slices for extension 1..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:type 0..1 CodeableConcept R5: The type of the device version, e.g. manufacturer, approved, internal (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.type #xD; extension:component 0..1 Identifier R5: The hardware or software module of the device to which the version applies (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.component #xD; extension:installDate 0..1 dateTime R5: The date the version was installed on the device (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.installDate #xD; extension:value 1..1 string R5: The version text (new) URL: http://hl7.org/fhir/5.0/StructureDefinition/extension-Device.version.value #xD; owner #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:owner 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: owner additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; location #xD; Slices for extension 0..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:location 0..1 ?gen-e1? [CanonicalType[http://hl7.org/fhir/StructureDefinition/alternate-reference]] R5: Where the device is found additional types URL: http://hl7.org/fhir/StructureDefinition/alternate-reference #xD; Documentation for this format
Cross-version Profile for R5.Device for use in FHIR STU3
This cross-version profile allows R5 Device content to be represented via FHIR STU3 Device resources.
This resource identifies an instance or a type of a manufactured item that is used in the provision of healthcare without being substantially changed through that activity. The device may be a medical or non-medical device. Medical devices include durable (reusable) medical equipment, implantable devices, as well as disposable equipment used for diagnostic, treatment, and research for healthcare and public health. Non-medical devices may include items such as a machine, cellphone, computer, application, etc.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
not(parent::f:contained and f:contained)
If the resource is contained in another resource, it SHALL NOT contain any narrative
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()
not(exists(f:contained/*/f:meta/f:versionId)) and not(exists(f:contained/*/f:meta/f:lastUpdated))
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()
not(exists(for $id in f:contained/*/@id return $id[not(ancestor::f:contained/parent::*/descendant::f:reference/@value=concat('#', $id))]))
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
The only time that a resource does not have an id is when it is being submitted to the server using a create operation.
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.
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.
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.
The base language in which the resource is written.
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).
Text summary of the resource, for human interpretation
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.
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.
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.
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.
R5: The reference to the definition for the device (new)
R5: `Device.definition` (new:CodeableReference(DeviceDefinition))
Element `Device.definition` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.definition` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
All FHIR elements must have a @value or children
hasValue() | (children().count() > id.count())
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), 'value')])
R5: lost | damaged | destroyed | available (new)
R5: `Device.availabilityStatus` (new:CodeableConcept)
Element `Device.availabilityStatus` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.availabilityStatus` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: An identifier that supports traceability to the event during which material in this product from one or more biological entities was obtained or pooled (new)
R5: `Device.biologicalSourceEvent` (new:Identifier)
Element `Device.biologicalSourceEvent` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.biologicalSourceEvent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Necessary to support mandatory requirements for traceability from donor/source to recipient and vice versa, while also satisfying donor anonymity requirements. The element is defined consistently across BiologicallyDerivedProduct, NutritionProduct, and Device. The identifier references an event that links to a single biological entity such as a blood donor, or to multiple biological entities (e.g. when the product is an embryo or a pooled platelet product). A single biologicalSourceEvent identifier may appear on multiple products of many types derived from a single donation event or source extraction. As an example, a single donation event may provide 2 kidneys and a liver for organ transplantation, 2 corneas for eye surgery, heart valves and arterial tissue for cardiovascular surgery, multiple skin grafts, tendons, multiple shaped bone grafts and a large number of bone putty/paste products; and each of them may be assigned to the same biological source event identifier.
R5: Serial number assigned by the manufacturer (new)
Element `Device.serialNumber` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.serialNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). 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_.
R5: The part number or catalog number of the device (new)
Element `Device.partNumber` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.partNumber` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Alphanumeric Maximum 20.
R5: Indicates a high-level grouping of the device (new)
R5: `Device.category` (new:CodeableConcept)
Element `Device.category` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.category` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Identifies the standards, specifications, or formal guidances for the capabilities supported by the device (new)
R5: `Device.conformsTo` (new:BackboneElement)
Element `Device.conformsTo` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.conformsTo` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). An externally-defined extension that has been mapped as the representation of FHIR R5 element `Device.conformsTo`: `http://hl7.org/fhir/StructureDefinition/device-conformsTo`.
R5: Inherent, essentially fixed, characteristics of the device. e.g., time properties, size, material, etc. (new)
R5: `Device.property` (new:BackboneElement)
Element `Device.property` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.property` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Dynamic or current properties, such as settings, of an individual device are described using a Device instance-specific [DeviceMetric] and recorded using [Observation]. Static characteristics of a device could also be documented in an associated [DeviceDefinition] instance. The Device instance's properties, and their values, could be, but need not be, the same as those described in an associated DeviceDefinition.
R5: The designated condition for performing a task (new)
Element `Device.mode` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.mode` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: The series of occurrences that repeats during the operation of the device (new)
Element `Device.cycle` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.cycle` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: A measurement of time during the device's operation (e.g., days, hours, mins, etc.) (new)
Element `Device.duration` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.duration` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Technical endpoints providing access to electronic services provided by the device (new)
R5: `Device.endpoint` (new:Reference(Endpoint))
Element `Device.endpoint` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.endpoint` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: Linked device acting as a communication/data collector, translator or controller (new)
R5: `Device.gateway` (new:CodeableReference(Device))
Element `Device.gateway` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.gateway` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). The Device.gateway may be used when the Device being referenced has a gateway and/or to capture one or more gateways associated with the device. If the Gateway is included in the Observation resource, the Observation.gatewayDevice should be used instead.
R5: The higher level or encompassing device that this device is a logical part of (new)
R5: `Device.parent` (new:Reference(Device))
Element `Device.parent` has a context of Device based on following the parent source element upwards and mapping to `Device`. Element `Device.parent` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). For example a vital signs monitor (parent) where three separate modules can be plugged into such as interchangeable blood pressure, oximeter, temperature modules. These modules are represented as devices with the .parent valued to the vital signs monitor when plugged in.
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.
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.
Unique instance identifiers assigned to a device by manufacturers other organizations or owners.
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. For [UDI](http://hl7.org/fhir/STU3/device.html#5.11.3.2.2), this element corresponds to the variable portion of the UDI that identifies the serial number of a specific device. See [UDI mappings](http://hl7.org/fhir/STU3/device-mappings.html#udi) for a complete mapping of UDI parts to Device.
The serial number which is a component of the production identifier (PI), a conditional, variable portion of a UDI. The identifier.type code should be set to “SNO”(Serial Number) and the system left empty.
Unique Device Identifier (UDI) Barcode string
[Unique device identifier (UDI)](http://hl7.org/fhir/STU3/device.html#5.11.3.2.2) assigned to device label or package.
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/STU3/device-mappings.html#udi) for a complete mapping of UDI parts to Device.
unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
R5: The name used to display by default when the device is referenced additional types
R5: `Device.displayName` additional types (string) additional types from child elements (value)
Element `Device.displayName` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.displayName` do not cover the following types: string. The mappings for `Device.displayName` do not cover the following types based on type expansion: value.
R5: The term that names the device additional types
R5: `Device.name.value` additional types (string) additional types from child elements (value)
Element `Device.name.value` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.name.value` do not cover the following types: string. The mappings for `Device.name.value` do not cover the following types based on type expansion: value.
R5: registered-name | user-friendly-name | patient-reported-name (new)
Element `Device.name.type` has a context of Device.udi based on following the parent source element upwards and mapping to `Device`. Element `Device.name.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: The preferred device name additional types
R5: `Device.name.display` additional types (boolean) additional types from child elements (value)
Element `Device.name.display` is mapped to FHIR STU3 element `Device.udi` as `RelatedTo`. The mappings for `Device.name.display` do not cover the following types: boolean. The mappings for `Device.name.display` do not cover the following types based on type expansion: value.
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.
The device identifier (DI), a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device.
Name of device as used in labeling or catalog.
Use the `Device.type` for a generic type or kind of device name. Note the [GUDID](http://www.fda.gov/medicaldevices/deviceregulationandguidance/uniquedeviceidentification/globaludidatabasegudid/default.htm) lists the name as the 'Brand Name'.
Propietary/Trade Name of the medical Device as used in the labeling or catalog
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.
Allows a recipient of a UDI to know which database will contain the UDI-associated metadata.
The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.
If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
A unique device identifier (UDI) on a device label in plain text
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.
The AIDC form of UDIs should be scanned or otherwise used for the identification of the device whenever possible to minimize errors in records resulting from manual transcriptions. If separate barcodes for DI and PI are present, concatenate the string with DI first and in order of human readable expression on label.
Automatic Identification and Data Capture
A unique device identifier (UDI) on a device label a form that uses automatic identification and data capture (AIDC) technology.
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.
All UDIs are to be issued under a system operated by an Jurisdiction-accredited issuing agency. GS1 DIs: http://hl7.org/fhir/NamingSystem/gs1 HIBCC DIs: http://hl7.org/fhir/NamingSystem/hibcc ICCBBA DIs for blood containers: http://hl7.org/fhir/NamingSystem/iccbba-blood ICCBA DIs for other devices: http://hl7.org/fhir/NamingSystem/iccbba-other
A coded entry to indicate how the data was entered.
Supports a way to distinguish hand entered from machine read data.
Codes to identify how UDI data was entered
unique id for the element within a resource (for internal references)
R5: barcode | rfid | manual | card | self-reported | electronic-transmission | unknown additional codes
R5: `Device.udiCarrier.entryType` additional codes
Element `Device.udiCarrier.entryType` is mapped to FHIR STU3 element `Device.udi.entryType` as `RelatedTo`. The mappings for `Device.udiCarrier.entryType` do not allow expression of the necessary codes, per the bindings on the source and target.
active | inactive | entered-in-error | unknown
This element is labeled as a modifier because the status contains the codes inactive and entered-in-error that mark the device (record)as not currently valid.
Code or identifier to identify a kind of device.
Type description using GMDN or other code system
Lot number assigned by the manufacturer.
The lot or batch number within which a device was manufactured - which is a component of the production identifier (PI), a conditional, variable portion of a UDI.
The date and time when the device was manufactured.
The date a specific device was manufactured - which is a component of the production identifier (PI), a conditional, variable portion of a UDI. For FHIR, The datetime syntax must converted to YYYY-MM-DD[THH:MM:SS]. If hour is present, the minutes and seconds should both be set to “00”.
Date and time of expiry of this device (if applicable)
The date and time beyond which this device is no longer valid or should not be used (if applicable).
the expiration date of a specific device - which is a component of the production identifier (PI), a conditional, variable portion of a UDI. For FHIR, The datetime syntax must converted to YYYY-MM-DD[THH:MM:SS]. If hour is present, the minutes and seconds should both be set to “00”.
The "model" is an identifier assigned by the manufacturer to identify the product by its type. This number is shared by the all devices sold as the same type.
The version of the device, if the device has multiple releases under the same model, or if the device is software or carries firmware.
R5: The type of the device version, e.g. manufacturer, approved, internal (new)
R5: `Device.version.type` (new:CodeableConcept)
Element `Device.version.type` has a context of Device.version based on following the parent source element upwards and mapping to `Device`. Element `Device.version.type` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
R5: The hardware or software module of the device to which the version applies (new)
R5: `Device.version.component` (new:Identifier)
Element `Device.version.component` has a context of Device.version based on following the parent source element upwards and mapping to `Device`. Element `Device.version.component` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element). Note that the module of the device would not need to be tracked as a separate device, e.g., using different UDI, thus would typically involve one or more software modules. For example, a device may involve two software modules each on a different version.
R5: The date the version was installed on the device (new)
R5: `Device.version.installDate` (new:dateTime)
Element `Device.version.installDate` has a context of Device.version based on following the parent source element upwards and mapping to `Device`. Element `Device.version.installDate` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Element `Device.version.value` has a context of Device.version based on following the parent source element upwards and mapping to `Device`. Element `Device.version.value` has no mapping targets in FHIR STU3. Typically, this is because the element has been added (is a new element).
Patient information, If the device is affixed to a person.
If the device is implanted in a patient, then need to associate the device to the patient.
An organization that is responsible for the provision and ongoing maintenance of the device.
Extensions are always sliced by (at least) url
R5: `Device.owner` additional types from child elements (display, identifier, reference, type)
Element `Device.owner` is mapped to FHIR STU3 element `Device.owner` as `SourceIsBroaderThanTarget`. The mappings for `Device.owner` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Device.owner` with unmapped reference targets: Organization.
Literal reference, Relative, internal or absolute URL
A reference to a location at which the other 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.
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.
Logical reference, when literal reference is not known
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.
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.
Plain text narrative that identifies the resource in addition to the resource reference.
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.
Details for human/organization for support
Contact details for an organization or a particular human that is responsible for the device.
The place where the device can be found.
Device.location can be used to track device location.
R5: Where the device is found additional types
R5: `Device.location` additional types from child elements (display, identifier, reference, type)
Element `Device.location` is mapped to FHIR STU3 element `Device.location` as `SourceIsBroaderThanTarget`. The mappings for `Device.location` do not cover the following types based on type expansion: display, identifier, reference, type. The standard extension `alternate-reference` has been mapped as the representation of FHIR R5 element `Device.location` with unmapped reference targets: Location.
A network address on which the device may be contacted directly.
If the device is running a FHIR server, the network address should be the Base URL from which a conformance statement may be retrieved.
Descriptive information, usage information or implantation information that is not captured in an existing element.
Provides additional safety characteristics about a medical device. For example devices containing latex.
Codes used to identify medical devices safety characterics. These codes are derived in part from the [United States Food and Drug Administration recommendations](http://www.fda.gov/downloads/medicaldevices/deviceregulationandguidance/guidancedocuments/ucm107708.pdf) and are provided here as a suggestive example.