This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "StatusRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<div style="background:#F0F0F0">
 
<div style="background:#F0F0F0">
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
+
This page documents a [[:category:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved FHIR Resource Proposal]]
  
 
=StatusRequest=
 
=StatusRequest=

Latest revision as of 17:50, 19 February 2015

StatusRequest

Owning committee name

Financial Management

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.