Stream: patient empowerment
Topic: Patient Corrections - the Rest of the Work
Virginia Lorenzi (Jan 28 2021 at 09:55):
Let's just put the back and forth informal conversation between patient and provider in a box for now and assume we have that solved (and we might). There is alot more we have to get to.
We need to represent either via FHIR or a workaround (like a phone call!)
- cancellation of the request (the further thru the process the more annoying this would be)
- some level of updating of the request (I suggest we limit this ability as much as possible to keep it simple. They can always cancel and recreate and app could shield them from the pain of that)
we also need to represent partial correct and partial deny
- I recommend we progress the status to complete and create an output record that describes what was accepted and what was rejected and tell them how they can disagree with what was rejected. I suggest we do this in lieu of spawning additional tasks or such. Keep it simple.
We need to get more rigorous in our representation of the codes/topics fields and the inputs, outputs, or payloads.
- a code to mean correct record, a code to mean disagree
-
a code for each kind of input or output
-what does a denial look like -
what does a complete with corrected response in output look like?
- how do you communicate who to notify?
We also need to figure out how this will actually look to the patient on their portal or outbound API - will they see their data corrected? Will they see anything that shows it was corrected? Will they see their disagreement?
Last updated: Apr 12 2022 at 19:14 UTC
