Stream: patient empowerment
Topic: Connectathon 29 - Patient Request for Corrections
Virginia Lorenzi (Nov 11 2021 at 23:30):
This is the official chat for the Patient Request for Corrections track at Connectathon 29 in January 2022!
Niek van Galen (Nov 17 2021 at 16:13):
When will a date in January be scheduled for this connectathon?
Lloyd McKenzie (Nov 17 2021 at 23:43):
The connectathon is Jan 10-12 (mostly 11-12). Details are here: https://www.hl7.org/events/fhir/connectathon/2022/01/
Virginia Lorenzi (Dec 17 2021 at 06:39):
Learn more about this track: https://confluence.hl7.org/display/FHIR/2022-01+Patient+Request+for+Corrections
(note orientation session is 3PM CDT Monday Jan 3rd - see above for details)
Virginia Lorenzi (Jan 04 2022 at 07:01):
Slides for today's orientation can be found Connectathon-29-Patient-Request-for-Corrections-Orientation-Jan-3pdf.pdf .
John Keyes (Jan 04 2022 at 16:23):
So that everyone is aware, we've made several updates to the Patient Request for Corrections IG over the past few days. Unfortunately, there is currently an issue with build.fhir.org that prevents me from publishing the updated version. Once that gets resolved, I will post another note here.
John Keyes (Jan 06 2022 at 14:43):
As noted in the #patient empowerment > Patient Request for Corrections IG updates stream, the updated IG has now been published.
Virginia Lorenzi (Jan 08 2022 at 09:53):
Virginia Lorenzi (Jan 10 2022 at 23:07):
@Jake Zhou @David Hay @Lisa Nelson @Timon Grob @Debi Willis Hey Dave, can someone just query Clinfhir and grab a patient to use for their correction requests? Jake, how do you plan to pick a patient? I could create some if need be.
David Hay (Jan 10 2022 at 23:08):
Not sure what you mean - create a correction request in graph builder?
Jake Zhou (Jan 10 2022 at 23:12):
I hardcoded adding "Patient/14" as the sender and subject of the Bundles I'm generating. Ideally, a real implementation would get the patient id of the current user of the patient app, but for testing I'm just using this value since I know it exists in clinFHIR
Jake Zhou (Jan 10 2022 at 23:13):
I found this value by grabbing all communications from clinFHIR in postman and saw this value existed for some of the existing records
David Hay (Jan 11 2022 at 00:07):
@Virginia Lorenzi - I see what you mean. What you can do is to PUT/POST a Patient resource to corrections.clinfhir.com:8091/baseR4/Patient - that's the hapi server that the app uses to store data and is externally accessible (usually it wouldn't be of course - but this is connectathon!). Note that this is http not https
David Hay (Jan 11 2022 at 03:52):
Actually, an even easier way is just to include the patient in the operation bundle - using a guid as the id (see the example below). The server will create a patient resource automatically (it's part of a transaction). The Communication that is returned will have the assigned id in the Communication.subject. Of course, the Communication will need to use the same guid in it's references to the patient
{
"resourceType": "Bundle",
"type": "collection",
"entry": [
{
"resource": {
"resourceType": "Patient",
"id": "e37792cd-ad43-455d-b0fe-0d0bd55db64f",
"name": [
{
"family": "Parker",
"given": [
"Peter"
]
}
],
"gender": "male"
}
},
{
"resource": {
"resourceType": "Communication",
"text": {
David Hay (Jan 11 2022 at 03:53):
It's quite straightforward to get examples of working messages from the log in the reference app - I can show that tomorrow morning...
David Hay (Jan 11 2022 at 23:18):
When the EHR accepts a change, a Communication is created that the patient can review. The Task remains open in this case. When the correction is logged (?ie changed in the record) is a Communication generated as well?
Virginia Lorenzi (Jan 12 2022 at 00:28):
Yes, most likely containing the amendment report. And the status is changed to AmendmentCompleted. Also Task.output points to that concluding Communication resource.
Virginia Lorenzi (Jan 12 2022 at 00:29):
(deleted)
Virginia Lorenzi (Jan 12 2022 at 00:29):
Trying to use the tool but when I go to the EHR side, I can only get patient with id=14, not the patient I created.
David Hay (Jan 12 2022 at 01:39):
Don't forget to refresh (or re-load) the page...
It's at the bottom...
Virginia Lorenzi (Jan 12 2022 at 04:57):
I tried that before anyway not sure cause now I am fine. Do not see button to move it from Queued to InReview anymore. Also, after patient replies to question, status should go from WaitingForInformation back to InReview because no longer waiting.
Virginia Lorenzi (Jan 12 2022 at 05:02):
When request is denied, Task.output should point to the Communication resource that describes the denial. Business status should be Denied in this case.
David Hay (Jan 12 2022 at 06:05):
Working on the workflow as we speak - hope to have completed by the mid-morning catch-up...
David Hay (Jan 12 2022 at 21:34):
BTW - just thinking on the 'multiple threads' of communication discussion - I can see difficulties in maintaining the Task business status. eg if one 'thread' is from the ehr to the patient waiting on more info, and in the other 'thread' the info has been supplied, what is the Task business status? is it always 'waiting for information if any 'thread is in that state?
I wonder if it is a bit complex for the first version of the spec...
Last updated: Apr 12 2022 at 19:14 UTC
