This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Invoice FHIR Resource Proposal"

From HL7Wiki
Jump to navigation Jump to search
(Created page with " <div class="messagebox cleanup metadata"> <div style="float: left;">35px| </div> <div style="background:#F0F0F0"> This page documents a :category...")
(No difference)

Revision as of 09:47, 10 November 2017


Owning committee name

Patient Administration

Committee Approval Date:

24 Jan 2017

Contributing or Reviewing Work Groups

Financial Management

FHIR Resource Development Project Insight ID


Scope of coverage

The existing Claim resource is constricted to use cases where Claims are sent to insurances for reimbursement, in a message-like style. It neither references ChargeItems nor Accounts

It doesn't not cover use cases where existing ChargeItems in an Account are used to create an Invoice to be sent out to Individuals or Organizations in a document-style.

Unlike the Claim resource it reflect the perspective of the (healthcare) service providing organization.

An invoice is a financial document issued by a Healthcare provider to a patient or a payer indicating the goods and services (ChargeItems) performed with their quantities and prices. The invoice is the hospital’s view, whereas the Claim is the payer’s view on the performed services.

RIM scope


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 tracks billing information and needs to issue invoices

Content sources

Existing normative V3 and V2 specifications

Example Scenarios

  • Invoicing

Resource Relationships

  • Reference to Account (account)
  • Reference to ChargeItems (items)
  • Reference to Encounter/EpisodeOfCare (via Account) (context)
  • Reference to Patient|Group (subject)
  • Reference to any type of Request/Referal (basedOn) (via Account)
  • Reference to any type of Event (service)
  • Payor (Organization|Patient|RelatedPerson)

Referenced by:

  • Claim


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