Others titles
- FHIR Invoice Resource
- Electronic Health Records Exchange Through FHIR
Keywords
- FHIR
- HL7
- Medical Terminology
- Processes Data
- Processes Information
- Processes Documentation
- Health Information Exchange
- Electronic Health Records
- FHIR Smart
- Smart on FHIR
Invoice
![Invoice](https://www.johnsnowlabs.com/wp-content/uploads/2018/09/normal/FHIR-Definitions.png)
Invoice containing collected Charge Items from an Account with calculated individual and total price for Billing purpose. Tracking Financial information is vital in Patient Administration and Finance systems in most Healthcare Organizations. 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.
Get The Data
- Research
Non-Commercial,
Share-Alike,
Attribution Free Forever
- Commercial
Commercial Use,
Remix & Adapt,
White Label Log in to download
Description
The examples for invoice implementations are:
– Any solution that tracks billing information and needs to issue invoices
– Private Insurance Providers who want to deliver structured information to patients to increase cost transparency
– Patient apps that want to include information on the amount and reason of the charged costs for the healthcare services a patient received
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.
Competing invoicing standards such as EDIFACT or X12 are aiming at inter-organizational exchange and do not offer human readable representations or traceable links to services rendered which is a requirement for invoicing towards patients. This resource is used where existing Charge Items in an Account are collected to create an Invoice to be sent out to Individuals or Organizations in a structured way. The invoice is the hospital’s view, whereas the Claim is the payer’s view on the performed services.
Since the individual Charge Item resources that make up the line items of the Invoice do not carry any pricing information, Charge Item Definitions will have to be applied to the ChargeItems in order to calculate the price components for the Invoice depending on the context of the Charge Item.
About this Dataset
Data Info
Date Created | 2018-09-20 |
---|---|
Last Modified | 2023-03-26 |
Version | 5.0.0 |
Update Frequency |
Annual |
Temporal Coverage |
N/A |
Spatial Coverage |
United States |
Source | John Snow Labs; Health Level Seven International; |
Source License URL | |
Source License Requirements |
N/A |
Source Citation |
N/A |
Keywords | FHIR, HL7, Medical Terminology, Processes Data, Processes Information, Processes Documentation, Health Information Exchange, Electronic Health Records, FHIR Smart, Smart on FHIR |
Other Titles | FHIR Invoice Resource, Electronic Health Records Exchange Through FHIR |
Data Fields
Name | Description | Type | Constraints |
---|---|---|---|
Concept_Name | Name of the concept in the FHIR structure. | string | required : 1 |
Computer_Ready_Name | A Computer-ready name (e.g. a token) that identifies the structure - suitable for code generation. Note that this name (and other names relevant for code generation, including element & slice names, codes etc) may collide with reserved words in the relevant target language, and code generators will need to handle this. | string | - |
Type | The type the structure describes. | string | - |
Dollar_Ref | The "$ref" string value contains a Uniform Resource Identifier (URI) which identifies the location of the JSON value being referenced. | string | - |
Description | A free text natural language description of the structure and its use. | string | - |
Items | The value of the keyword should be an object or an array of objects. If the keyword value is an object, then for the data array to be valid each item of the array should be valid according to the schema in this value. | string | - |
Enum | The enum is used to restrict a value to a fixed set of values. It must be an array with at least one element, where each element is unique. | string | - |
Required | The value of the keyword should be an array of unique strings. The data object to be valid should contain all properties with names equal to the elements in the keyword value. | string | - |
Const | The value of this keyword can be anything. The data is valid if it is deeply equal to the value of the keyword. | string | - |
Data Preview
Concept Name | Computer Ready Name | Type | Dollar Ref | Description | Items | Enum | Required | Const |
Invoice | resourceType | This is a Invoice resource | Invoice | |||||
Invoice | id | #/definitions/id | The logical id of the resource | |||||
Invoice | meta | #/definitions/Meta | The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource. | |||||
Invoice | implicitRules | #/definitions/uri | A reference to a set of rules that were followed when the resource was constructed | |||||
Invoice | _implicitRules | #/definitions/Element | Extensions for implicitRules | |||||
Invoice | language | #/definitions/code | The base language in which the resource is written. | |||||
Invoice | _language | #/definitions/Element | Extensions for language | |||||
Invoice | text | #/definitions/Narrative | A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data | |||||
Invoice | contained | array | These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently | |||||
Invoice | extension | array | May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable |