This wiki has undergone a migration to Confluence found Here
Difference between revisions of "ChargeItem FHIR Resource Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Resource Proposal}}") |
|||
| Line 13: | Line 13: | ||
| − | = | + | =ChargeItem= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 28: | Line 28: | ||
==Owning committee name== | ==Owning committee name== | ||
| + | Patient Administration | ||
<!-- 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. --> | ||
| Line 37: | Line 38: | ||
<!-- 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== | ||
| Line 57: | Line 56: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | |||
| + | ChargeItem is used to communicate statistical or billing relevant codes that apply to delivered services. | ||
| + | ChargeItems are associated with an Account resource. | ||
==RIM scope== | ==RIM scope== | ||
| + | Financial Transaction | ||
<!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | <!-- Identify the formal RIM mapping for the root concept of the resource. The expectation is that the RIM mapping will be sufficiently precise so as to not overlap with any other resource definition. --> | ||
| Line 101: | Line 104: | ||
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 (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== | ==Timelines== | ||
Revision as of 21:57, 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
Patient Administration
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 codes that apply to delivered services. ChargeItems are associated with an Account resource.
RIM scope
Financial Transaction
Resource appropriateness
Expected implementations
Content sources
Example Scenarios
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
gForge Users
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
