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

Difference between revisions of "PendedRequest FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with "=PendedRequest= <!-- Resource names should meet the following characteristics: * Lower camel case * U.S. English * Domain-friendly * Short * Clear * Unique * Avoid non-univer...")
 
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]]
 +
 
=PendedRequest=
 
=PendedRequest=
  

Revision as of 16:41, 29 October 2014

PendedRequest

Owning committee name

Financial Management

Contributing or Reviewing Work Groups

  • Patient Administration

FHIR Resource Development Project Insight ID

994

Scope of coverage

The PendedRequest resource provides supporting information for the poll request. The response to this is a previously undelivered response or a StatusResponse (or other acknowledgement which may contain errors).


RIM scope

Poll

Resource appropriateness

This is required where either the Payor requires a specific request for outstanding responses or the transport does not support a 'Get Operation' with search parameters.

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

Example Scenarios

Resource Relationships

Refers to any outstanding response resource. Is referred to a Pended or Poll Request.

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.