Device

Top  Previous  Next

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.

Response Description

Sample Response

{

  "resourceType": "Device",

  "id": "DEV-DEV-11913-347",

  "meta": {

     "lastUpdated": "2022-11-14T12:00:00-05:00",

     "profile": [

        "http://hl7.org/fhir/us/core/StructureDefinition/us-core-implantable-device"

     ]

  },

  "text": {

     "status": "generated",

     "div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><table><tbody><tr><td>Patient:</td><td>Cole Andersonian (DEV-DEV-11913)</td></tr><tr><td>Device:</td><td>ACME Knee Replacement Device</td></tr><tr><td>Status:</td><td>active</td></tr><tr><td>Unique Device ID:</td><td>(01)99863313444316(17)220101(10)M320(21)AC221</td></tr><tr><td>Serial Number:</td><td>Ser83469421</td></tr><tr><td>Expiration:</td><td>12/12/48</td></tr></tbody></table></div>"

  },

  "udiCarrier": [

     {

        "deviceIdentifier": "99863313444316",

        "carrierHRF": "(01)99863313444316(17)220101(10)M320(21)AC221"

     }

  ],

  "status": "active",

  "manufacturer": "ACME",

  "manufactureDate": "2022-01-12",

  "expirationDate": "2048-12-12",

  "lotNumber": "3463463463",

  "serialNumber": "Ser83469421",

  "distinctIdentifier": "UNK",

  "deviceName": [

     {

        "name": "ACME Knee Replacement Device",

        "type": "other"

     }

  ],

  "modelNumber": "89530589",

  "type": {

     "coding": [

        {

           "system": "http://snomed.info/sct",

           "code": "109228008",

           "display": "Knee joint prosthesis"

        }

     ],

     "text": "ACME Knee Replacement Device"

  },

  "patient": {

     "reference": "Patient/DEV-DEV-11913",

     "display": "Cole Andersonian (DEV-DEV-11913)"

  }

}

 

 

Device.id

 

The logical ID of the resource, as used in the URL for the resource. Once assigned, this value never changes.

Cardinality

0..1

Type

string

Comment

The only time that a resource does not have an ID is when it is being submitted to the server using a create operation.

 

 

Device.meta

 

Metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.

Cardinality

0..1

Type

Meta

 

 

Device.text

 

A human-readable narrative that contains a summary of the resource and can 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.

Cardinality

0..1

Type

Narrative

Comment

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.

 

 

Device.udiCarrier

 

Unique Device Identifier (UDI) Barcode string.

Cardinality

0..*

Type

BackboneElement

Comment

UDI may identify an unique instance of a device, or it may only identify the type of the device.

 

 

Device.udiCarrier.deviceIdentifier

 

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.

Cardinality

1..1

Type

string

 

 

Device.udiCarrier.carrierHRF

 

The full UDI carrier as the human readable form (HRF) representation of the barcode string as printed on the packaging of the device.

Cardinality

0..1

Type

string

 

 

Device.status

 

Status of the Device availability.

Cardinality

0..1

Type

code: active | inactive

 

 

Device.manufacturer

 

Name of device manufacturer.

Cardinality

0..1

Type

string

 

 

Device.manufactureDate

 

The date when the device was manufactured.

Cardinality

0..1

Type

dateTime

 

 

Device.expirationDate

 

The date beyond which this device is no longer valid or should not be used (if applicable).

Cardinality

0..1

Type

dateTime

 

 

Device.lotNumber

 

Lot number assigned by the manufacturer.

Cardinality

0..1

Type

string

 

 

Device.serialNumber

 

The serial number assigned by the organization when the device was manufactured.

Cardinality

0..1

Type

string

Comment

Alphanumeric limited to 16.

 

 

Device.distinctIdentifier

 

The distinct identification string as required by regulation for a human cell, tissue, or cellular and tissue-based product.

Cardinality

0..1

Type

string

Comment

For example, this applies to devices in the United States regulated under Code of Federal Regulation 21CFR§1271.290(c).

 

 

Device.deviceName

 

This represents the manufacturer's name of the device as provided by the device, from a UDI label, or by a person describing the Device. This typically would be used when a person provides the name(s) or when the device represents one of the names available from DeviceDefinition.

Cardinality

0..*

Type

BackboneElement

 

 

Device.modelNumber

 

The manufacturer's model number for the device.

Cardinality

0..1

Type

string

 

 

Device.type

 

The kind or type of device.

Cardinality

0..1

Type

CodeableConcept. The codes SHALL be taken from FHIRDeviceTypes; other codes may be used where these codes are not suitable Codes to identify medical devices

 

 

Device.patient

 

Patient to whom Device is affixed.

Cardinality

0..1

Type

Reference(Patient)

Requirements

If the device is implanted in a patient, then need to associate the device to the patient.

 


 

Search

 

URL Syntax

Two HTTP methods are supported for searching: GET and POST. It is recommended to use HTTP POST.

Visit the FHIR Sandbox to try requests.

 

 

HTTP GET - searching

https://sandbox.pai.healthcare/preview/fhir/Device?{query string}

 

HTTP GET - return single record

https://sandbox.pai.healthcare/preview/fhir/Device/{resource id}

 

HTTP POST - searching

https://sandbox.pai.healthcare/preview/fhir/Device/_search

Set the Content-Type header to application/x-www-urlencoded

The body of the request is a similar query string used in the GET type of request detailed above.

 

 

Error Handling

If no records are returned or invalid search parameters are provided, then an HTTP 400 Bad Request is returned.

The body of the response will be an OperationOutcome.

 

 

Supported Search Parameters

 

_id

 

Corresponds to

Device.id

Search

exact

Example

https://sandbox.pai.healthcare/preview/fhir/Device?_id=dev-dev-11913-343

 

Returns Device used in encounter 343 for 11913 account.

 

patient + type

 

Corresponds to

Device.patient and Device.type

Search

exact

Example

https://sandbox.pai.healthcare/preview/fhir/Device?patient=Patient/dev-dev-11913&type=15447007

 

Returns Devices with SNOMED code 15447007 for account 11913.

 

patient + _revInclude:Provenance:target

 

Corresponds to

Device.patient

Search

exact

Example

https://sandbox.pai.healthcare/preview/fhir/Device?patient=Patient/dev-dev-15262&_revInclude=Provenance:target

 

Returns Devices for account 15262 in the dev practice, and include the Provenance record for each.

 

patient

 

Corresponds to

Device.patient

Search

exact

Example

https://sandbox.pai.healthcare/preview/fhir/Device?patient=Patient/DEV-DEV-11913

 

Returns all Devices for user 11913 from practice dev.