This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Payment FHIR Resource Proposal"
Jump to navigation
Jump to search
(migrate to Confluence) |
|||
| (7 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
<div class="messagebox cleanup metadata"> | <div class="messagebox cleanup metadata"> | ||
| − | <div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> | + | Current version: https://confluence.hl7.org/display/FHIR/Payment+FHIR+Resource+Proposal<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div> |
<div style="background:#F0F0F0"> | <div style="background:#F0F0F0"> | ||
This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | This page documents a [[:category:Pending FHIR Resource Proposal|Pending]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]] | ||
| Line 13: | Line 13: | ||
| − | = | + | =FinancialTransaction= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 57: | Line 57: | ||
--> | --> | ||
| − | This resource provides the ability to accurately track the different | + | This resource provides the ability to accurately track the different payment and adjustment transactions toward balances on an account. |
==RIM scope== | ==RIM scope== | ||
| Line 78: | Line 78: | ||
--> | --> | ||
| − | Tracking financial information is vital in Patient Accounting and Patient Administration systems in many Healthcare Organizations. This resource provides the ability to accurately track the different payments toward balances | + | Tracking financial information is vital in Patient Accounting and Patient Administration systems in many Healthcare Organizations. This resource provides the ability to accurately track the different payments and adjustments toward balances on the account. ChargeItems (can) result in an increase in the balance on an Account. We now need a method to pay down that balance (i.e. post payments). |
==Expected implementations== | ==Expected implementations== | ||
| Line 84: | Line 84: | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| − | + | *Any solution that tracks financial accounting, payment, and billing information | |
| − | + | *Patient apps that support self-pay payments | |
| − | + | *Patient apps that show how a current balance was calculated | |
| − | + | *Interested parties: Cerner, payment processors, healthcare providers, healthcare systems. | |
==Content sources== | ==Content sources== | ||
| Line 101: | Line 101: | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| − | Patient online bill pay | + | *Patient online bill pay payments |
| − | + | *Point of service payments for co-pays | |
| − | Point of service | + | *Back office collection payments over the phone or mail |
| + | *Lockbox payments | ||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 115: | Line 116: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | Reference to: | ||
| + | |||
| + | *Account | ||
| + | *Encounter | ||
| + | *ChargeItem | ||
| + | *Claim | ||
| + | *Patient|Group|RelatedPerson (subject) | ||
| + | |||
| + | Referenced by: | ||
| + | |||
| + | *Payment | ||
==Resource Boundaries== | ==Resource Boundaries== | ||
Latest revision as of 15:18, 31 October 2019
Current version: https://confluence.hl7.org/display/FHIR/Payment+FHIR+Resource+Proposal
This page documents a Pending FHIR Resource Proposal
Contents
- 1 FinancialTransaction
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Resource Boundaries
- 1.13 Timelines
- 1.14 gForge Users
- 1.15 When Resource Proposal Is Complete
- 1.16 FMG Notes
FinancialTransaction
Owning work group name
Committee Approval Date:
PA Approval on 10/24/2018 Riki Merrick/Kathleen Connor:4-0-0
Contributing or Reviewing Work Groups
Patient Administration
FHIR Resource Development Project Insight ID
994
Scope of coverage
This resource provides the ability to accurately track the different payment and adjustment transactions toward balances on an account.
RIM scope
Resource appropriateness
Tracking financial information is vital in Patient Accounting and Patient Administration systems in many Healthcare Organizations. This resource provides the ability to accurately track the different payments and adjustments toward balances on the account. ChargeItems (can) result in an increase in the balance on an Account. We now need a method to pay down that balance (i.e. post payments).
Expected implementations
- Any solution that tracks financial accounting, payment, and billing information
- Patient apps that support self-pay payments
- Patient apps that show how a current balance was calculated
- Interested parties: Cerner, payment processors, healthcare providers, healthcare systems.
Content sources
Existing normative V3 and V2 specifications
Example Scenarios
- Patient online bill pay payments
- Point of service payments for co-pays
- Back office collection payments over the phone or mail
- Lockbox payments
Resource Relationships
Reference to:
- Account
- Encounter
- ChargeItem
- Claim
- Patient|Group|RelatedPerson (subject)
Referenced by:
- Payment
Resource Boundaries
Timelines
gForge Users
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
