This wiki has undergone a migration to Confluence found Here
EOBRequest FHIR Resource Proposal
Revision as of 02:45, 22 October 2014 by Paul Knapp (talk | contribs) (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...")
Contents
- 1 EOBRequest
- 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
EOBRequest
Owning committee name
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.
