Difference between revisions of "ChargeItemDefinition FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
 
(11 intermediate revisions by 2 users not shown)
Line 3: Line 3:
 
<div style="float: left;">[[Image:OpenHotTopic.GIF|35px| ]]</div>
 
<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:Approved FHIR Resource Proposal|Approved]] [[:category:FHIR Resource Proposal|FHIR Resource Proposal]]
 
</div>
 
</div>
 
</div>
 
</div>
 
[[Category:FHIR Resource Proposal]]
 
[[Category:FHIR Resource Proposal]]
[[Category:Pending FHIR Resource Proposal]]
+
[[Category:Approved  FHIR Resource Proposal]]
  
  
Line 32: Line 32:
 
Financial Management
 
Financial Management
 
==Committee Approval Date:==
 
==Committee Approval Date:==
7 Feb 2018 (Simone Heckman, Brian Postlethwaite 2-0-1)
+
PA approval: 7 Feb 2018 (Simone Heckman, Brian Postlethwaite 2-0-1)
 +
 
 +
FM approval: 14 May 2018
  
 
==Contributing or Reviewing Work Groups==
 
==Contributing or Reviewing Work Groups==
Line 50: Line 52:
 
The existing ChargeItem Resource specifies the instance of a charge item that documents billable codes for items and services rendered.
 
The existing ChargeItem Resource specifies the instance of a charge item that documents billable codes for items and services rendered.
 
The details, prices and rules associated with billing codes exist however, independent from these instances.
 
The details, prices and rules associated with billing codes exist however, independent from these instances.
 +
 
Following up on the [https://chat.fhir.org/#narrow/stream/terminology/topic/adding.20prices.20to.20CodeSytem discussion in Zulip], such details should be kept in separate Resources and not as properties of the codes, as such things as prices may change over time and independently from the CodeSystem lifecycle.
 
Following up on the [https://chat.fhir.org/#narrow/stream/terminology/topic/adding.20prices.20to.20CodeSytem discussion in Zulip], such details should be kept in separate Resources and not as properties of the codes, as such things as prices may change over time and independently from the CodeSystem lifecycle.
  
  
 
==RIM scope==
 
==RIM scope==
 
+
InvoiceElement in Definition Mood
-none-
 
<!-- 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. -->
 
  
 
==Resource appropriateness==
 
==Resource appropriateness==
Line 79: Line 80:
  
 
<!--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 billing information and needs to calculate prices and cost
+
* Any solution that tracks billing information and needs to calculate prices and cost
  
 
==Content sources==
 
==Content sources==
  
 
<!-- List all of the specifications (beyond those in the "standard"-->  
 
<!-- List all of the specifications (beyond those in the "standard"-->  
German statutory health services billing catalogue: http://www.kbv.de/html/online-ebm.php
+
* German statutory health services billing catalogue: http://www.kbv.de/html/online-ebm.php
 
* DRG Catalogue http://www.g-drg.de/content/download/7388/55411/version/1/file/Fallpauschalen_Katalog_2018_171124.xlsx
 
* DRG Catalogue http://www.g-drg.de/content/download/7388/55411/version/1/file/Fallpauschalen_Katalog_2018_171124.xlsx
 
 

Latest revision as of 21:28, 24 April 2019



ChargeItemDefinition

Owning committee name

Financial Management

Committee Approval Date:

PA approval: 7 Feb 2018 (Simone Heckman, Brian Postlethwaite 2-0-1)

FM approval: 14 May 2018

Contributing or Reviewing Work Groups

Patient Administration


FHIR Resource Development Project Insight ID

pending

Scope of coverage

The existing ChargeItem Resource specifies the instance of a charge item that documents billable codes for items and services rendered. The details, prices and rules associated with billing codes exist however, independent from these instances.

Following up on the discussion in Zulip, such details should be kept in separate Resources and not as properties of the codes, as such things as prices may change over time and independently from the CodeSystem lifecycle.


RIM scope

InvoiceElement in Definition Mood

Resource appropriateness

Tracking Financial information is vital in Patient Administration and Finance systems in most Healthcare Organizations. This resource provides the properties that apply to the (billing) codes necessary to calculate costs and prices. The properties may differ largely depending on type and realm, therefore this resource gives only a rough structure and requires profiling for each type of billing code system.

Expected implementations

  • Any solution that tracks billing information and needs to calculate prices and cost

Content sources

Please note that all such catalog definitions will be realm specific and need profiles for the ChargeItemDefinition in order to be useful.

Example Scenarios

  • Invoicing

In order to determine the actual price of a ChargeItem (when becoming an Invoice.lineItem) a billing engine needs to know base/unit prices, applicable surcharges and discounts and the rules associated with their application. The ChargeItemDefinition provides this information in an exchangeable and standardized form.

Resource Relationships

Referenced by:

  • ChargeItem.definition


Timelines

The aim is to have a draft (Maturity 0) ready for 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