STU3 Candidate

This page is part of the FHIR Specification (v1.8.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4B R4 R3 R2

Mappings for the device resource.

DeviceDevice
    identifier.id
    udiCarrier.id[where root is root for UDI]
    status.statusCode
    type.code
    lotNumber.lotNumberText
    manufacturer.playedRole[typeCode=MANU].scoper.name
    manufactureDate.existenceTime.low
    expirationDate.expirationTime
    model.playedRole[typeCode=MANU].code
    version.softwareName (included as part)
    patient.playedRole[typeCode=USED].scoper.playedRole[typeCode=PAT]
    owner.playedRole[typeCode=OWN].scoper
    contact.scopedRole[typeCode=CON].player
    location.playedRole[typeCode=LOCE].scoper
    url.telecom
    note.text

UDI is a unique numeric or alphanumeric code that consists of two parts: (1) a device identifier (DI), a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a device, and (2) a production identifier (PI), a conditional, variable portion of a UDI that identifies one or more of the following when included on the label of a device: (2a) the lot or batch number within which a device was manufactured; (2b) the serial number of a specific device; (2c) the expiration date of a specific device; (2d) the date a specific device was manufactured; (2e) the distinct identification code required by §1271.290(c) for a human cell, tissue, or cellular and tissue-based product (HCT/P) regulated as a device.

DeviceN/A
    identifierThe serial number which is a component of the 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.
    udiCarrierThe full UDI carrier - The Human Readable Form (HRF) representation of the barcode string as printed on the packaging of the device. The 'type' component should be set to “UDI” and the 'system' component to the the appropriate repository url. the additional URL is needed to identify the authoritative source for UDI generation within the jurisdiction. All UDIs are globally unique within a single namespace. with the appropriate repository uri as the system. This allows a recipient of a UDI to know which database will contain the UDI-associated metadata. For example, UDIs of devices managed in the U.S. by the FDA, the value is http://hl7.org/fhir/NamingSystem/fda-udi. Because of limitations on character sets in XML and the need to round-trip JSON data through XML, AIDC identifiers cannot be conveyed in FHIR.
    statusN/A
    typeThe device identifier (DI), a mandatory, fixed portion of a UDI that identifies the labeler and the specific version or model of a devicet. The system uri should be included. Possible URIs include
GS1 DIs:
http://hl7.org/fhir/NamingSystem/gs1-di
HIBCC DIs:
http://hl7.org/fhir/NamingSystem/hibcc-di
ICCBBA DIs for blood containers:
http://hl7.org/fhir/NamingSystem/iccbba-blood-di
ICCBA DIs for other devices:
http://hl7.org/fhir/NamingSystem/iccbba-other-di
    lotNumberThe lot or batch number within which a device was manufactured - which is a component of the the production identifier (PI), a conditional, variable portion of a UDI.
    manufacturerN/A
    manufactureDateThe date a specific device was manufactured - which is a component of the 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”.
    expirationDatethe expiration date of a specific device - which is a component of the 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”.
    modelN/A
    versionN/A
    patientN/A
    ownerN/A
    contactN/A
    locationN/A
    urlN/A
    noteN/A