Stream: Da Vinci
Topic: Clinical Data Exchange (CDex)
Rick Geimer (Mar 19 2019 at 16:29):
Thread starter
Douglas DeShazo (May 28 2019 at 17:17):
@Rick Geimer Is there any new information, other than that at the Davinci Confluence pages, that we might need for tomorrow in Jacksonville?
Douglas DeShazo (Aug 21 2019 at 20:04):
@Rick Geimer Is this the channel for the Payer/Provider Information Exchange track for Atlanta? Also, is the plan still to have this track at the Atlanta Connectathon?
Sreekanth Puram (Aug 21 2019 at 20:53):
Rick Geimer Is this the channel for the Payer/Provider Information Exchange track for Atlanta? Also, is the plan still to have this track at the Atlanta Connectathon?
Attachments Track
Douglas DeShazo (Aug 22 2019 at 17:54):
CDex is being used in multiple tracks (Attachments and Payer/Provider, will those be separated out?
Rick Geimer (Aug 22 2019 at 19:22):
@Douglas DeShazo Please see https://confluence.hl7.org/pages/viewpage.action?pageId=55940211
@Durwin Day and @Christol Green are leading this track, so it will be up to them whether to reuse this stream or create a new one for the Connectathon in Atlanta.
Douglas DeShazo (Aug 22 2019 at 20:48):
@Rick Geimer thanks. I saw @Christol Green 's updates yesterday with task flow so I'll continue to check there.
rekha (Aug 23 2019 at 13:33):
Hi All,
I have gone through this IG: http://build.fhir.org/ig/HL7/davinciecdx/Push_(Unsolicited_Communication).html I want to know whether we need to use Task resource in Unsolicited and Solicited Communications,If we use Task resource what is the role of Task in the IG.
Lloyd McKenzie (Aug 23 2019 at 13:35):
Task gives you the ability to say "yes" or "no" or "yes, but...". It also allows you to check on status. Without Task, you're in a situation where there must always be a presumption of "yes" and where you just have to wait until the Communication shows up - no way to check on where things are at. So Task tends to be useful in more sophisticated workflow environments
rekha (Aug 23 2019 at 13:39):
Thank you @Lloyd McKenzie ,But I want to know that what is the main use of Task in the CDex IG
Lloyd McKenzie (Aug 23 2019 at 13:51):
That's the main use. If you ask for the Communication using Task, then the EHR can say "yes" or "no" by updating the Task.status. They can also update the Task.businessStatus and add comments so if you query the Task after a few days to see where things are at, there'll be an answer.
rekha (Aug 24 2019 at 06:19):
Ok Thank you @Lloyd McKenzie
Stanley Nachimson (May 18 2021 at 16:05):
Stanley Nachimson12:04 PM
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
