Difference between revisions of "Payment FHIR Resource Proposal"
| Line 41: | Line 41: | ||
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
| + | |||
| + | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
994 | 994 | ||
| − | |||
| − | |||
==Scope of coverage== | ==Scope of coverage== | ||
| Line 56: | Line 56: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | This resource provides the ability to accurately track the different payments toward balances and how they apply to 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). The existing PaymentNotice and PaymentReconciliation resource are specific to adjudicated cliam payments and do not encompass self pay payments. | ||
==RIM scope== | ==RIM scope== | ||
| Line 75: | Line 77: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | |||
| + | 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 and how they apply to 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== | ||
<!--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: GE, Cerner, payment processors, healthcare providers, healthcare systems. | ||
==Content sources== | ==Content sources== | ||
| Line 85: | Line 94: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
| + | |||
| + | Existing normative V3 and V2 specifications | ||
==Example Scenarios== | ==Example Scenarios== | ||
<!-- 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 workflows. | ||
| + | |||
| + | Point of service payment and back office collections workflows. | ||
==Resource Relationships== | ==Resource Relationships== | ||
Revision as of 22:24, 13 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 and how they apply to 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). The existing PaymentNotice and PaymentReconciliation resource are specific to adjudicated cliam payments and do not encompass self pay payments.
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 and how they apply to 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: GE, Cerner, payment processors, healthcare providers, healthcare systems.
Content sources
Existing normative V3 and V2 specifications
Example Scenarios
Patient online bill pay workflows.
Point of service payment and back office collections workflows.
Resource Relationships
Resource Boundaries
Timelines
gForge Users
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
