R4 Ballot #2 (Mixed Normative/Trial use)
WorkflowThis page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions 
. Page versions: R3 R2
| Financial Management Work Group | Maturity Level: 2 | Trial Use | Compartments: Practitioner |
This resource provides processing status, errors and notes from the processing of a resource.
NOTE: This resource is slated to be refactored and reduced in scope as some of its functionality is taken over by the Task resource as part of the FHIR Workflow refactoring. Readers of this resource are encouraged to review the Task resource and consider using it instead and/or to provide feedback if they feel it will be inadequate to satisfy the use-cases associated with this resource and to express opinions about which purposes for they feel ProcessRequest and ProcessResponse should be retained.
The ProcessResponse resource indicates the resource for which the processing status is requested and provides simple acknowledgement and status information of application level errors. It may also be used to convey additional processing requirements in a text form.
This is the formal response to a ProcessRequest and may be used as a application level response to the PaymentNotice resource.
Structure
UML Diagram (Legend)
XML Template
<ProcessResponse xmlns="http://hl7.org/fhir"><!-- from Resource: id, meta, implicitRules, and language --> <!-- from DomainResource: text, contained, extension, and modifierExtension --> <identifier><!-- 0..* Identifier Business Identifier --></identifier> <status value="[code]"/><!-- 0..1 active | cancelled | draft | entered-in-error --> <created value="[dateTime]"/><!-- 0..1 Creation date --> <organization><!-- 0..1 Reference(Organization) Authoring Organization --></organization> <request><!-- 0..1 Reference(Any) Request reference --></request> <outcome value="[code]"/><!-- 0..1 Processing outcome --> <disposition value="[string]"/><!-- 0..1 Disposition Message --> <requestProvider><!-- 0..1 Reference(Practitioner|PractitionerRole|Organization) Responsible Practitioner --></requestProvider> <form><!-- 0..1 CodeableConcept Printed Form Identifier --></form> <processNote> <!-- 0..* Processing comments or additional requirements --> <type value="[code]"/><!-- 0..1 display | print | printoper --> <text value="[string]"/><!-- 0..1 Comment on the processing --> </processNote> <error><!-- 0..* CodeableConcept Error code --></error> <communicationRequest><!-- 0..* Reference(CommunicationRequest) Request for additional information --></communicationRequest> </ProcessResponse>
JSON Template
{
"resourceType" : "ProcessResponse",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // Business Identifier
"status" : "<code>", // active | cancelled | draft | entered-in-error
"created" : "<dateTime>", // Creation date
"organization" : { Reference(Organization) }, // Authoring Organization
"request" : { Reference(Any) }, // Request reference
"outcome" : "<code>", // Processing outcome
"disposition" : "<string>", // Disposition Message
"requestProvider" : { Reference(Practitioner|PractitionerRole|Organization) }, // Responsible Practitioner
"form" : { CodeableConcept }, // Printed Form Identifier
"processNote" : [{ // Processing comments or additional requirements
"type" : "<code>", // display | print | printoper
"text" : "<string>" // Comment on the processing
}],
"error" : [{ CodeableConcept }], // Error code
"communicationRequest" : [{ Reference(CommunicationRequest) }] // Request for additional information
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .
Changes since R3
| ProcessResponse | |
| ProcessResponse.outcome |
|
| ProcessResponse.requestProvider |
|
| ProcessResponse.processNote.type |
|
| ProcessResponse.requestOrganization |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
See R3 <--> R4 Conversion Maps (status = 3 tests of which 3 fail to execute.)
Structure
XML Template
<ProcessResponse xmlns="http://hl7.org/fhir">
JSON Template
{
"resourceType" : "ProcessResponse",
// from Resource: id, meta, implicitRules, and language
// from DomainResource: text, contained, extension, and modifierExtension
"identifier" : [{ Identifier }], // Business Identifier
"status" : "<code>", // active | cancelled | draft | entered-in-error
"created" : "<dateTime>", // Creation date
"organization" : { Reference(Organization) }, // Authoring Organization
"request" : { Reference(Any) }, // Request reference
"outcome" : "<code>", // Processing outcome
"disposition" : "<string>", // Disposition Message
"requestProvider" : { Reference(Practitioner|PractitionerRole|Organization) }, // Responsible Practitioner
"form" : { CodeableConcept }, // Printed Form Identifier
"processNote" : [{ // Processing comments or additional requirements
"type" : "<code>", // display | print | printoper
"text" : "<string>" // Comment on the processing
}],
"error" : [{ CodeableConcept }], // Error code
"communicationRequest" : [{ Reference(CommunicationRequest) }] // Request for additional information
}
Turtle Template
@prefix fhir: <http://hl7.org/fhir/> .
Changes since Release 3
| ProcessResponse | |
| ProcessResponse.outcome |
|
| ProcessResponse.requestProvider |
|
| ProcessResponse.processNote.type |
|
| ProcessResponse.requestOrganization |
|
See the Full Difference for further information
This analysis is available as XML or JSON.
See R3 <--> R4 Conversion Maps (status = 3 tests of which 3 fail to execute.)
See the Profiles & Extensions and the alternate definitions: Master Definition XML + JSON, XML Schema/Schematron + JSON Schema, ShEx (for Turtle) + see the extensions & the dependency analysis
| Path | Definition | Type | Reference |
|---|---|---|---|
| ProcessResponse.status | A code specifying the state of the resource instance. | Required | FinancialResourceStatusCodes |
| ProcessResponse.outcome | Local status of outcome codes. | Required | ProcessOutcomeCodes |
| ProcessResponse.form | The forms codes. | Example | Form Codes |
| ProcessResponse.processNote.type | The presentation types of notes. | Required | NoteType |
| ProcessResponse.error | The error codes for adjudication processing. | Example | Adjudication Error Codes |
Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.
| Name | Type | Description | Expression | In Common |
| identifier | token | The business identifier of the Explanation of Benefit | ProcessResponse.identifier | |
| organization | reference | The organization who generated this resource | ProcessResponse.organization (Organization) | |
| request | reference | The reference to the claim | ProcessResponse.request (Any) | |
| request-provider | reference | The Provider who is responsible the request transaction | ProcessResponse.requestProvider (Practitioner, Organization, PractitionerRole) | |
| status | token | The status of the process response | ProcessResponse.status |
®© HL7.org 2011+. FHIR Mixed Nomative/Trial Use Ballot #2 (v3.5.0-14907) generated on Sun, Aug 19, 2018 21:54+1000. QA Page
Links: Search |
Version History |
Table of Contents |
Credits |
Compare to DSTU3 |
Ballot Comparison |
|
Propose a change