Stream: Da Vinci
Topic: Unique Device Identifier (UDI) Data
Stanley Nachimson (May 07 2021 at 16:07):
Want to know if anyone participating in the upcoming May Connectathon has UDI data available in their servers to test the exchange of it in PDEX or CDEX transactions?
Lloyd McKenzie (May 07 2021 at 17:28):
@Nikolai Schwertner @Saul Kravitz
Nikolai Schwertner (May 11 2021 at 19:50):
@Stanley Nachimson The CDEX reference implementation does not have device data. The data requested and returned in exchange is conditions and binary documents. This said, we can add your device based query (on the requester side) or sample device data (on the responder side) if you could share them.
Stanley Nachimson (May 12 2021 at 17:00):
Nikolai Schwertner said:
Stanley Nachimson The CDEX reference implementation does not have device data. The data requested and returned in exchange is conditions and binary documents. This said, we can add your device based query (on the requester side) or sample device data (on the responder side) if you could share them.
@Lloyd McKenzie - Not sure what this means, can you help me with it?
Lloyd McKenzie (May 12 2021 at 18:36):
It means that the reference implementation is not set up to run 'arbitrary' queries - it just does pre-canned ones. Nikolai - how hard would it be to have a received query just run against a FHIR server (one we could configure in the RI) and return the response - and similarly for device codes just do a search on the server for matching DocumentReferences?
Nikolai Schwertner (May 12 2021 at 22:36):
@Lloyd McKenzie The provider side RI already runs any FHIR query received via a Task against the underlying FHIR server. It is just that the sample data set loaded on that server is limited. We could load additional data to the server, if available, or @Stanley Nachimson could add his own. On the other hand, the payer side implementation does indeed offer a selection of canned queries to choose from. It won't be hard to extend that component to accept arbitrary FHIR queries for packaging in a Task request in addition to the canned ones.
Stanley Nachimson (May 18 2021 at 16:04):
I have created a couple of test patients with UDI resource included. They are at the HAPI R4 server, URL:http://hapi.fhir.org/baseR4/. The Patient IDs are cfsb1621007238203 and cfsb1621344950821. I would love for someone to test their query and see if they can retrieve the UDI information for the patients. The JSON language for the UDI resource is:
{
"resourceType": "Device",
"id": "cfsb1621007158908",
"meta": {
"versionId": "1",
"lastUpdated": "2021-05-18T15:09:33.280+00:00",
"source": "#wYDfpAmpgVz8KuUh"
},
"text": {
"status": "additional",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\">Knee implant for Bob</div>"
},
"udiCarrier": [
{
"deviceIdentifier": "09504000059316",
"issuer": "09504000059316://hl7.org/fhir/NamingSystem/gs1-di",
"jurisdiction": "hl7.org/fhir/NamingSystem/fda-udi",
"carrierHRF": "(01)09504000059316(17)250101(21)A123999",
"entryType": "manual"
}
],
"status": "active",
"serialNumber": "347a552889",
"deviceName": [
{
"name": "NACH123",
"type": "manufacturer-name"
},
{
"name": "Brand B Implant",
"type": "manufacturer-name"
}
],
"modelNumber": "A12",
"patient": {
"reference": "Patient/cfsb1621007238203"
}
}
Last updated: Apr 12 2022 at 19:14 UTC
