 ANSI/HL7 V3 AB, R2-2008 (R2012) HL7 Version 3 Standard: Accounting and Billing, Release 2 03/06/2008 (reaffirmed 6/5/2012) |
Content Last Edited: 2008-06-04T13:47:15
3.2 Storyboards
3.3 Application Roles
3.4 Trigger Events
3.5 Refined Message Information Models
3.6 Hierarchical Message Descriptions
3.7 Interactions
|
||||||
|
For details on the interpretation of this section, see the storyboard discussion in the Version 3 Guide.
This domain area addresses the posting of financial transactions against patient billing accounts.
| Post Financial Transaction Notification |  FIAB_IN020001UV02 |
Patient Account Posting
During the course of Ms. Smith's hospital stay charges, adjustments, and credits related to the services provided and items consumed are accumulated by her patient account.
|
||||||||
|
For details on the interpretation of this section, see the discussion of application roles and their relationships in the Version 3 Guide.
Informs a tracker of posts of financial transactions against accounts.
Monitors posts of financial transactions against accounts.
|
||||||
|
For details on the interpretation of this section, see the discussion of trigger events in the Version 3 Guide.
| Type: |
This trigger event signals that a financial transaction is posted to the patient billing account for billable service charges; payment made for the portion of the charges that are the patient's responsibility; or a payment by an alternative guarantor, e.g. Workers' Insurance payor. The charge or reversal can be triggered from different systems once the account is already established in the billing system. A) Hospital Information systems generate charge or reversal triggered at various instances of a clinical workflow based on different status. For example Charge on Order, Charge on Charting, Charge on Result, Charge on Assessment. The Status can be active, Complete, etc. B) Hospital Information Systems can generate charge or reversal, which are manually posted. These are material, supply or miscellaneous that could not be generated in a workflow and need to be captured manually. C) Departmental Systems like Oncology, Cardiology etc. can post charges or reversals, which are directly sent to the billing system, or may be routed via the Hospital Information system. D) Ancillary Systems like Laboratory and Radiology can post charges or reversals, which are directly sent to the billing system, or may be routed via the Hospital Information system. E) The Master ADT system may generate charges or reversals to be sent to the billing system, once a patient account has been established. V2 Reference: The Post financial transaction most closely aligned with the HL7 2.4 DFT^P03-Post Detail Financial Transaction and HL7 2.5 DFT^P11 - Post Detail Financial Transactions - Expanded.
|
||||||
|
For details on the interpretation of this section, see the description of RMIMs in the Version 3 Guide.
| Parent: | Patient Billing Account (FIAB_DM000000UV) |
This model includes the posting of financial transactions against those accounts (e.g. lab charge). Posting of charges is supplied through a financial transaction. In strictest accounting terms, the financial transaction would have a debit and credit association to 2 accounts (the debit account and the credit account). In this model, only 1 is specified. The financial transaction is supported by a costing component (invoice element), which is further supported by the actual service that was performed or the product that was supplied (billable). To add to the balance of a patient billing account, the ActFinancialTransactionCode should be "CHRG" with a positive amount. To reduce this balance, the code would be "REV", again with a positive amount.
| Patient Billing Post Event | FIAB_HD020100UV02 |
|
||||||
|
For details on the interpretation of this section, see the description of HMDs in the Version 3 Guide.
This model includes the posting of financial transactions against those accounts (e.g. lab charge). Posting of charges is supplied through a financial transaction. In strictest accounting terms, the financial transaction would have a debit and credit association to 2 accounts (the debit account and the credit account). In this model, only 1 is specified. The financial transaction is supported by a costing component (invoice element), which is further supported by the actual service that was performed or the product that was supplied (billable). To add to the balance of a patient billing account, the ActFinancialTransactionCode should be "CHRG" with a positive amount. To reduce this balance, the code would be "REV", again with a positive amount.
|
||||||
|
For details on the interpretation of this section, see the definition of Interactions in the Version 3 Guide.
Post financial transaction to a patient billing account.
| Trigger Event | Post Financial Transaction | FIAB_TE020001UV02 |
| Transmission Wrapper | Send Message Payload | MCCI_MT000100UV01 |
| Control Act Wrapper | Trigger Event Control Act | MCAI_MT700201UV01 |
| Message Type | Patient Billing Post Event Complete | FIAB_MT020101UV02 |
| Sender | Patient Billing Account Informer | FIAB_AR010001UV02 |
| Receiver | Patient Billing Account Tracker | FIAB_AR010002UV02 |
| Return to top of page |