Difference between revisions of "Reversal FHIR Resource Proposal"
Paul Knapp (talk | contribs) (Created page with "=Reversal= <!-- Resource names should meet the following characteristics: * Lower camel case * U.S. English * Domain-friendly * Short * Clear * Unique * Avoid non-universal a...") |
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]] | ||
| + | |||
=Reversal= | =Reversal= | ||
Revision as of 16:39, 29 October 2014
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Reversal
- 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
Reversal
Owning committee name
Contributing or Reviewing Work Groups
- Claims with Attachments
- Patient Administration
FHIR Resource Development Project Insight ID
994
Scope of coverage
The Reversal resource indicates the resource which is to be reversed and provides both supporting information for the reversal and whether the receiving system is permitted to retain a copy of the reversed resource.
RIM scope
InvoiceElementGroup (classCode=INVE, moodCode=PRP,RQO)
Resource appropriateness
The reversal is the formal request to cease processing an incomplete prior request or to reverse and/or nullify a complete prior request or information submission. When nullify=true then all copies of the original submission are to be purged, although audit logs may be retained. When Nullify=false a copy of the original request may be retained.
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 a Claim resource, FInancialAttachment and uses Organization, Practitioner. Is referred to by a ClaimResponse.
Timelines
Ready for DSTU 2
gForge Users
paulknapp
