Patient Request for Corrections Implementation Guide
1.0.0 - STU 1

Patient Request for Corrections Implementation Guide, published by HL7 International / Patient Empowerment. This guide is not an authorized publication; it is the continuous build for version 1.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. 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

## Artifacts

Page standards status: Informative

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

### Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

Patient Request for Corrections Capability Statement | Describes the capabilities for a FHIR server to support patient requests for corrections.

### Behavior: Operation Definitions

These are custom operations that can be supported by and/or invoked by systems conforming to this implementation guide.

Patient Correction Request Operation | 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).

### Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

Search on the PatientCorrectionCommunication.about element | Search Parameter extension enabling clients to search on the PatientCorrectionCommunication.about element
Search on the PatientCorrectionTask.reasonReference element | Search Parameter extension enabling clients to search on the PatientCorrectionTask.reasonReference element

### Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

Patient Correction Bundle | The Patient Correction Bundle contains a Patient Correction Communication and other resources related to a patient request for correction. Note that the operation has a bundle as its only parameter, as opposed to having multiple parameters for the input and output. The main reasons for this approach are:
    The bundle enables the expression of the relationships among the various resources that carry the necessary information.
    The entries in the bundle are full resources, which:
        allows the use of the profiling mechanisms to describe the different requirements for the different steps of the process
        sets the stage for future different RESTful approaches as an incremental change to the current specification
Patient Correction Communication | A Communication between a patient and a fulfiller relating to a patient correction request.
Patient Correction Task | Represents the process of reviewing the patient&apos;s request for correction or the patient’s request to log a disagreement to a prior request for correction decision. This Task is spawned by the Fulfiller as a result of a post of a Communication resource that indicates a new request for correction or a new logging of a disagreement.

### Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

Patient Correction Business Status | ValueSet of business statuses for patient request for corrections
Patient Correction Communication Types Value Set | ValueSet of Communication types for patient request for corrections
Patient Correction Output Types Value Set | ValueSet of output types for patient corrections
Patient Correction Task Types Values Set | ValueSet of task types for patient requests for corrections

### Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

Patient Correction Business Statuses | CodeSystem of business statuses for patient request for corrections
Patient Correction Communication Types | CodeSystem of Communication categories for use in Patient Correction Request
Patient Correction Output Types | CodeSystem of output types for patient request for corrections
Patient Correction Task Types | CodeSystem of task types for patient request for corrections

### Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

BundleExample | Example of an initial request for correction Bundle
Dummy DocumentReference example | Dummy DocumentReference example for completeness sake. No actual use of this resource other than an example target
Dummy Organization example | Dummy Organization example for completeness sake. No actual use of this resource other than an example target.
Dummy Patient example | Dummy patient example for completeness sake. No actual use of this resource other than an example target
Dummy Patient is smoking | Dummy Patient is a smoker. No actual use of this resource other than as an exmaple target.
Dummy Practitioner (PCP) example | Dummy Practitioner (PCP) example for completeness sake. No actual use of this resource other than an example target.
Dummy Practitioner example | Dummy Practitioner example for completeness sake. No actual use of this resource other than an example target.
additionalinfoneeded | Example of request for correction additional information needed Communication
additionalinfoprovided | Example of request for correction additional information provided Communication
correctionrequestprocess | Example of an initial request for correction Task
correctionrequestprocess2 | Example of request for correction additional information needed Task
correctionrequestprocess3 | Example of request for correction additional information provided Task
correctionrequestprocess4 | Example of request for correction in clinical review Task
correctionrequestprocess5 | Example of request for correction ammendment accepted Task
correctionrequestprocess6 | Example of request for correction ammendment completed Task
initialrequestforcorrection | Example of an initial request for correction Communication
recordamended | Example of request for correction amendment completed Communication