Difference between revisions of "ExplanationOfBenefit FHIR Resource Proposal"
Paul Knapp (talk | contribs) (Created page with "=ExplanationOfBenefit= <!-- Resource names should meet the following characteristics: * Lower camel case * U.S. English * Domain-friendly * Short * Clear * Unique * Avoid non...") |
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]] | ||
| + | |||
=ExplanationOfBenefit= | =ExplanationOfBenefit= | ||
Revision as of 16:53, 29 October 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 ExplanationOfBenefit
- 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
ExplanationOfBenefit
Owning committee name
Contributing or Reviewing Work Groups
- Claims with Attachments
- Patient Administration
FHIR Resource Development Project Insight ID
994
Scope of coverage
The ExplanationOfBenefit resource combines key information from a Claim, a ClaimResponse and optional Account information to inform a patient of the goods and services rendered by a provider and the settlement made under the patients coverage in respect of that Claim.
RIM scope
New
Resource appropriateness
This is the logical combination of the Claim, Claim Response and some Coverage accounting information in respect of a single payor prepared for consumption by the subscriber and/or patient. It is not simply a series of pointers to referred-to content models, is a physical subset scoped to the adjudication by a single payor which details the services rendered, the amounts to be settled and to whom, and the coverage used and/or remaining.
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 Patient, Practitioner, Organization, Coverage, Referral.
Timelines
Ready for DSTU 2
gForge Users
paulknapp
Issues
May need to be per discipline depending upon the level of Claim details included.
