Patient Request for Corrections Implementation Guide
1.0.0 - STU 1 Ballot International flag

Patient Request for Corrections Implementation Guide, published by HL7 International - Patient Empowerment Workgroup. This is not an authorized publication; it is the continuous build for version 1.0.0). This version is based on the current content of https://github.com/HL7/fhir-patient-correction/ and changes regularly. See the Directory of published versions

OperationDefinition: correction-request

Official URL: http://hl7.org/fhir/uv/patient-corrections/OperationDefinition/correction-request Version: 1.0.0
Draft as of 2023-09-11 Computable Name: PatientCorrectionRequestOperation

The correction-request operation is used to communicate a request for correction or a logging of a disagreement of a denial from a requester to a fulfiller. It includes the ability to send the request along with attachments. The fulfiller can spawn a task to manage the correction process as part of the operation. For the operation, we expect the server to store the Communication resource, spawn a Task when appropriate, and update the Communication and return the Communication resource with reference to a Task id if a Task is spawned. The correction-request operation is also used whenever the requester provides updates to the fulfiller (additional information, conversation).

URL: [base]/Communication/$correctionrequest

Parameters

UseNameScopeCardinalityTypeBindingDocumentation
INCorrectionRequest1..1Bundle

A collection of resources representing the correction request, disagreement, or back and forth conversation. The Bundle should follow Patient Correction Bundle profile.

OUTCorrectionResponse1..1Bundle

A collection of resources representing a correction request response. The Bundle should follow Patient Correction Bundle profile.