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

Difference between revisions of "EOBRequest FHIR Resource Proposal"

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

Revision as of 16:54, 29 October 2014

EOBRequest

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 EOBRequest resource provides the information to identify a Claim, and potentially a Pre-Determination or Pre-Authorization, so that the Explanation of Benefit resource can be generated and/or retrieved.


RIM scope

Query

Resource appropriateness

This is the formal request for an EOB for Payors which require one and/or use transports which do not support a 'Get Operation'.

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, NCPDP

Example Scenarios

Resource Relationships

Refers to Claim, Patient, Practitioner, Coverage, Is referred to by a Reconciliation.

Timelines

Ready for DSTU 2

gForge Users

paulknapp

Issues

This resource may be replaced with a more generic request for a resource.