Difference between revisions of "Payment FHIR Resource Proposal"
| Line 102: | Line 102: | ||
*Patient online bill pay payments | *Patient online bill pay payments | ||
| − | *Point of service payments for co-pays | + | *Point of service payments for co-pays |
| − | *Back office collection payments over the phone or mail | + | *Back office collection payments over the phone or mail |
| + | *Lockbox payments | ||
==Resource Relationships== | ==Resource Relationships== | ||
Revision as of 17:46, 20 November 2018
This page documents a Pending FHIR Resource Proposal
Contents
- 1 Payment
- 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
Payment
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 payments 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 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
- 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
