FHIR Chat · Patient Request for Corrections IG updates · patient empowerment

Stream: patient empowerment

Topic: Patient Request for Corrections IG updates

view this post on Zulip John Keyes (Aug 04 2021 at 19:47):

I have updated the Patient Request for Corrections draft IG (v0.3.0) with the following changes, which we (@Debi Willis , @Virginia Lorenzi , @John Moehrke , @John Keyes ) discussed in our 2021-08-03 call:

  1. communication.about is now a reference to the original communication associated with the correction request (unless this is the original communication, in which case this will be empty).
  2. task.reasonReference (for a correction request, medRecCxReq) now is a reference to the original communication associated with the correction request.
  3. task.reasonReference (for a disagreement, medRecCxDenialDisagree) now is a reference to the original communication associated with the correction request (it is not a reference to the first communication of the disagreement).
  4. A new search parameter has been added for communication.about, allowing a client to find all communications associated with a corrections request.
  5. A new search parameter has been added for task.reasonReference, allowing a client to find the task(s) associated with a correction request. (There should be a Task created as a result of the original correction request, and also a Task created as a result of any disagreement.)

Comments welcome.

view this post on Zulip Debi Willis (Aug 04 2021 at 20:02):

Thank you John. This simplifies the IG and makes it cleaner.

We welcome any comments to help make this even better!

@Vassil Peytchev @Lisa Nelson @Jeffrey Danford @Jeff Danford @Emma Jones @Bart Carlson

view this post on Zulip John Keyes (Aug 17 2021 at 16:22):

I have updated the Patient Request for Corrections draft IG (v0.3.1) with the following changes:

  1. Updated Actors and Use Cases page based on 2021-08-15 email from @Virginia Lorenzi .
  2. Moved Communication-only and Task-only alternatives to new Archive tab.
  3. Updated text on Communication profile page to correctly describe use of Communication.about.
  4. Changed Communication.inResponseTo cardinality from 0..* to 0..1.
  5. Updated text on Task profile page to correctly describe use of Task.reasonReference.
  6. Removed incorrect definition of Task.note.

@Debi Willis @Virginia Lorenzi

view this post on Zulip John Keyes (Sep 03 2021 at 18:24):

In preparation the upcoming Connectathon, I have updated the Patient Request for Corrections draft IG (v0.4.0) with new & updated content supplied by @Virginia Lorenzi and @Debi Willis, and other details discussed in our recent calls.

view this post on Zulip John Keyes (Nov 08 2021 at 18:55):

I have updated the Patient Request for Corrections draft IG (v0.4.3) as follows:

  1. Added draft version of PatientCorrectionBundle. Likely needs more work.
  2. One Examples page, removed Event 6 Variant 1, and Variant 2 is now Event 6.

@Virginia Lorenzi @Debi Willis @John Moehrke

view this post on Zulip John Moehrke (Nov 08 2021 at 19:10):

I am being pulled in too many directions to help. sorry.

view this post on Zulip Virginia Lorenzi (Nov 11 2021 at 23:24):

NP - I just thought you might be interested. Some asked for info on the security workgroup.

view this post on Zulip John Keyes (Nov 15 2021 at 18:48):

I have updated the Patient Request for Corrections draft IG to add PatientCorrectionRequestOperation.

@Virginia Lorenzi @Debi Willis

view this post on Zulip John Keyes (Nov 29 2021 at 20:31):

I have updated the Patient Request for Corrections draft IG (v0.4.4). This version fixes many of the errors and warnings from the QA Report.
@Virginia Lorenzi @Debi Willis

view this post on Zulip John Keyes (Dec 13 2021 at 18:53):

I have updated the Patient Request for Corrections draft IG (v0.4.5). The Specifications page now contains @Timon Grob 's new state diagram and Virginia's business status table.
@Virginia Lorenzi @Debi Willis

view this post on Zulip John Keyes (Jan 06 2022 at 14:41):

I have updated the Patient Request for Corrections IG (v0.4.6) with the following changes:

  1. Updated Specifications page with new descriptions, RESTful interactions diagram from @Virginia Lorenzi .
  2. Updated Specifications page with new Task status & businessStatus table from Virginia and new corresponding state machine diagram from @Timon Grob .
  3. Updated Search Parameter definitions with corrections from @David Hay .

view this post on Zulip Timon Grob (Jan 06 2022 at 15:13):

2 remarks on item 2:
a) shouldn't there be an arrow from cancelled to the black dot at the bottom (the end state)?
b) in some boxes the /n is shown instead of a line break, due to update process?

view this post on Zulip John Keyes (Jan 06 2022 at 15:32):

Thank you Timon. I'm adding the arrow for item a. For item b, I don't know why PlantUML is not converting backslash n to newline; I thought it was supposed to.

view this post on Zulip John Keyes (Jan 06 2022 at 15:53):

In fact, the same .plantuml source generates newlines correctly using the online server. But not with my local build or the CI build.

view this post on Zulip David Hay (Jan 06 2022 at 16:55):

Thanks John - will review and update my server by connectathon!

view this post on Zulip John Keyes (Jan 09 2022 at 01:22):

I have updated the Patient Request for Corrections draft IG (v0.4.7) with a few more corrections/improvements to the PatientCorrectionCommunication, PatientCorrectionTask, and PatientCorrectionRequestOperation profiles, thanks to more helpful input from @David Hay .

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -