This page is part of the Patient Request for Corrections Implementation Guide (v1.0.0: STU1) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

• Narrative Content
• XML
• JSON
• TTL

: Patient Correction Request Operation - XML Representation

Raw xml | Download

<OperationDefinition xmlns="http://hl7.org/fhir">
  <id value="correction-request"/>
  <text>
    <status value="generated"/>
    <div xmlns="http://www.w3.org/1999/xhtml"><p class="res-header-id"><b>Generated Narrative: OperationDefinition correction-request</b></p><a name="correction-request"> </a><a name="hccorrection-request"> </a><p>URL: [base]/Communication/$correctionrequest</p><h3>Parameters</h3><table class="grid"><tr><td><b>Use</b></td><td><b>Name</b></td><td><b>Scope</b></td><td><b>Cardinality</b></td><td><b>Type</b></td><td><b>Binding</b></td><td><b>Documentation</b></td></tr><tr><td>IN</td><td>CorrectionRequest</td><td/><td>1..1</td><td><a href="http://hl7.org/fhir/R4/bundle.html">Bundle</a></td><td/><td><div><p>A collection of resources representing the correction request, disagreement, or back and forth conversation.  The Bundle should follow <a href="StructureDefinition-patient-correction-bundle.html">Patient Correction Bundle</a> profile.</p>
</div></td></tr><tr><td>OUT</td><td>CorrectionResponse</td><td/><td>1..1</td><td><a href="http://hl7.org/fhir/R4/bundle.html">Bundle</a></td><td/><td><div><p>A collection of resources representing a correction request response. The Bundle should follow <a href="StructureDefinition-patient-correction-bundle.html">Patient Correction Bundle</a> profile.</p>
</div></td></tr></table></div>
  </text>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-wg">
    <valueCode value="pe"/>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-fmm">
    <valueInteger value="1">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/patient-corrections/ImplementationGuide/hl7.fhir.uv.patient-corrections"/>
      </extension>
    </valueInteger>
  </extension>
  <extension
             url="http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status">
    <valueCode value="trial-use">
      <extension
                 url="http://hl7.org/fhir/StructureDefinition/structuredefinition-conformance-derivedFrom">
        <valueCanonical
                        value="http://hl7.org/fhir/uv/patient-corrections/ImplementationGuide/hl7.fhir.uv.patient-corrections"/>
      </extension>
    </valueCode>
  </extension>
  <url
       value="http://hl7.org/fhir/uv/patient-corrections/OperationDefinition/correction-request"/>
  <version value="1.0.0"/>
  <name value="PatientCorrectionRequestOperation"/>
  <title value="Patient Correction Request Operation"/>
  <status value="active"/>
  <kind value="operation"/>
  <date value="2025-07-10T15:50:53+00:00"/>
  <publisher value="HL7 International / Patient Empowerment"/>
  <contact>
    <telecom>
      <system value="url"/>
      <value
             value="http://www.hl7.org/Special/committees/patientempowerment"/>
    </telecom>
  </contact>
  <contact>
    <name value="Virginia Lorenzi"/>
    <telecom>
      <system value="email"/>
      <value value="vlorenzi@nyp.org"/>
    </telecom>
  </contact>
  <contact>
    <name value="David Pyke"/>
    <telecom>
      <system value="email"/>
      <value value="david@pyke.ca"/>
    </telecom>
  </contact>
  <description
               value="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)."/>
  <jurisdiction>
    <coding>
      <system value="http://unstats.un.org/unsd/methods/m49/m49.htm"/>
      <code value="001"/>
      <display value="World"/>
    </coding>
  </jurisdiction>
  <code value="correctionrequest"/>
  <resource value="Communication"/>
  <system value="false"/>
  <type value="true"/>
  <instance value="false"/>
  <parameter>
    <name value="CorrectionRequest"/>
    <use value="in"/>
    <min value="1"/>
    <max value="1"/>
    <documentation
                   value="A collection of resources representing the correction request, disagreement, or back and forth conversation.  The Bundle should follow [Patient Correction Bundle](StructureDefinition-patient-correction-bundle.html) profile."/>
    <type value="Bundle"/>
  </parameter>
  <parameter>
    <name value="CorrectionResponse"/>
    <use value="out"/>
    <min value="1"/>
    <max value="1"/>
    <documentation
                   value="A collection of resources representing a correction request response. The Bundle should follow [Patient Correction Bundle](StructureDefinition-patient-correction-bundle.html) profile."/>
    <type value="Bundle"/>
  </parameter>
</OperationDefinition>