Details
-
Change Request
-
Resolution: Unresolved
-
Medium
-
Patient Corrections (FHIR)
-
1.0.0-ballot
-
Patient Empowerment
-
Actors and Use Cases
-
2.2.4
-
Enhancement
Description
The simplest use case (probably not following a HIPAA Request for Amendment workflow)
Proposed wording:
"2.2.0 Use case 0: Patient Requests a Correction to Their Medical Record and Receives Notice of Receipt
A patient reviews the records received from a provider (most likely this review is of the electronic health information accessed on their personal health record application). The patient determines that it contains one or more errors or discrepancies. The patient enters a correction request using their application. The request can be a simple unstructured request, but can also contain additional structured information to provide context or to pinpoint the error and the fix. The application (CorrectionRequester) sends the correction request to the appropriate provider system (RequestFulfiller). The provider (most likely a medical records professional but possibly a clinician) reviews whether the request can be processed and informs the CorrectionRequester of the receipt of their request, including textual information on how the request will be handled within the provider system and how further communication on this request can be realized. The actual workflow of handling the request is not supported through structured digital communication between the CorrectionRequester and RequestFulfiller.
Abstract Model – Request for Correction received
Just an interaction “Request received” from RequestFulfiller to CorrectionRequester, which contains the status (can the request be processed) and further instructions (who to contact how regarding the status of this request)."