Difference between revisions of "StatusResponse FHIR Resource Proposal"
Paul Knapp (talk | contribs) (Created page with "=StatusResponse= <!-- Resource names should meet the following characteristics: * Lower camel case * U.S. English * Domain-friendly * Short * Clear * Unique * Avoid non-unive...") |
|||
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | |||
| + | <div class="messagebox cleanup metadata"> | ||
| + | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | ||
| + | <div style="background:#F0F0F0"> | ||
| + | This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | ||
| + | </div> | ||
| + | </div> | ||
| + | [[Category:FHIR Resource Proposal]] | ||
| + | [[Category:Approved FHIR Resource Proposal]] | ||
| + | |||
=StatusResponse= | =StatusResponse= | ||
Latest revision as of 17:50, 19 February 2015
This page documents a Approved FHIR Resource Proposal
Contents
- 1 StatusResponse
- 1.1 Owning committee name
- 1.2 Contributing or Reviewing Work Groups
- 1.3 FHIR Resource Development Project Insight ID
- 1.4 Scope of coverage
- 1.5 RIM scope
- 1.6 Resource appropriateness
- 1.7 Expected implementations
- 1.8 Content sources
- 1.9 Example Scenarios
- 1.10 Resource Relationships
- 1.11 Timelines
- 1.12 gForge Users
- 1.13 Issues
StatusResponse
Owning committee name
Contributing or Reviewing Work Groups
- Claims with Attachments
- Patient Administration
FHIR Resource Development Project Insight ID
994
Scope of coverage
The StatusResponse resource indicates the resource for which the processing status is requested and provides simple acknowledgement and status information of application level errors.
RIM scope
New
Resource appropriateness
This is the formal response to a StatusRequest.
Expected implementations
This is a key resource expected by most Healthcare billing implementations where Health care products and services are provided.
Content sources
Existing normative V3 and V2 specifications, Canadian Specifications, X12
Example Scenarios
Resource Relationships
Refers to a StatusRequest, PaymentNotice, FinancialAttachment or Enrollment.
Timelines
Ready for DSTU 2
gForge Users
paulknapp
Issues
It has been suggested that this may be replaced with OperationOutcome, but that will require turning OperationOutcome into a resource and adding a series of elements including: business identifiers, processing status and notes, processing level errors – and these changes may not be acceptable.
