Difference between revisions of "ChargeItem FHIR Resource Proposal"
| Line 28: | Line 28: | ||
==Owning committee name== | ==Owning committee name== | ||
| − | |||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | [[Patient Administration]] |
==Committee Approval Date:== | ==Committee Approval Date:== | ||
<i>Please enter the date that the committee approved this Resource proposal</i> | <i>Please enter the date that the committee approved this Resource proposal</i> | ||
| Line 38: | Line 37: | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
| − | + | Financial Management | |
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
Revision as of 22:15, 19 January 2017
This page documents a Pending FHIR Resource Proposal
Contents
- 1 ChargeItem
- 1.1 Owning committee 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 Timelines
- 1.13 gForge Users
- 1.14 When Resource Proposal Is Complete
ChargeItem
Owning committee name
Committee Approval Date:
Please enter the date that the committee approved this Resource proposal
Contributing or Reviewing Work Groups
Financial Management
FHIR Resource Development Project Insight ID
Scope of coverage
ChargeItem is used to communicate statistical or billing relevant information associated with delivered services. ChargeItems are placed into Patient Account resources. Tracking Financial information is vital in Patient Administration and Finance systems in most Healthcare Organizations. This resource provides the individual items to track.
RIM scope
Financial Transaction
Resource appropriateness
Tracking Financial information is vital in Patient Administration and Finance systems in most Healthcare Organizations. This resource provides the individual items to track.
Expected implementations
- Any solution that requires tracking billing information
Content sources
Existing normative V3 and V2 specifications
Example Scenarios
- Lab system sends ChargeItems containing billing codes for administered services to the patient's account
- Billing System queries patient account for all billable ChargeItems to create an Invoice/Claim
- Hospital maintains internal catalogue of statistically relevant services. All systems providing these services post ChargeItems into the Accounts of the Patients for whom these services have been provided. Customized queries can be used to analyze distribution of services among patient cohorts or developement of services provisions over time
Resource Relationships
- Reference to Account (account)
- Reference to Encounter/EpisodeOfCare (context)
- Reference to Patient|Group (subject)
- Reference to any type of Request (basedOn)
- Reference to any type of Event (service)
Timelines
We have built a draft placeholder for this resource, and working with the Finance WG to refine it during the 3.0/4.0 timeline.
gForge Users
brianpos simoneheckmann
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
