Difference between revisions of "StatusRequest FHIR Resource Proposal"
Paul Knapp (talk | contribs) (Created page with "=StatusRequest= <!-- Resource names should meet the following characteristics: * Lower camel case * U.S. English * Domain-friendly * Short * Clear * Unique * Avoid non-univer...") |
Paul Knapp (talk | contribs) |
||
| 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:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | ||
| + | </div> | ||
| + | </div> | ||
| + | [[Category:FHIR Resource Proposal]] | ||
| + | [[Category:Pending FHIR Resource Proposal]] | ||
| + | |||
=StatusRequest= | =StatusRequest= | ||
Revision as of 16:41, 29 October 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 StatusRequest
- 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
StatusRequest
Owning committee name
Contributing or Reviewing Work Groups
- Claims with Attachments
- Patient Administration
FHIR Resource Development Project Insight ID
994
Scope of coverage
The StatusRequest resource indicates the resource for which the processing status is requested and provides supporting information for the status request.
RIM scope
New
Resource appropriateness
This is a formal request, for Payors which require such and/or transports which don't support a 'Get Operation', for the processing status of a previously submitted processing request.
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 Claim resource or a Reconciliation. Is referred to by a StatusResponse.
Timelines
Ready for DSTU 2
gForge Users
paulknapp
Issues
It has been suggested that Operations() may be used to fulfill the business needs for this resource, at least for REST implementations, this will be explored.
