Financial

Receives financial transactions. It can receive charge and credit transactions for hospital accounts for Epic's Hospital Billing application, and post or void charges on guarantor accounts for Epic's Professional Billing application. These charges are subject to charge entry checks.

Receives messages that notify the billing applications (Resolute Hospital, Professional, Home Health (Dorothy), or Enterprise Billing) that a scanned explanation of benefits document exists. Receiving a message opens a new payment batch in the appropriate billing application based on scan type.

Sends financial transactions. The ability to send financial transactions is typically only applicable if Epic's billing applications are not in use and financial transactions need to be sent to an external billing system.

Epic provides support for credit cards to be used with the Epic system to pay copays, hospital and outpatient bills, and for medications. This integration is handled through credit card gateway systems, which send payment data to processing services that verify the payments with appropriate banks. The gateway then sends the verified payment information back to the Epic system to post the payment. This integration is handled through the patient portal and patient kiosk software as well as in over-the-phone and billing-office use cases. Epic software for credit card processing follows the PA-DSS requirements in its development.

This incoming batch interface creates a record of deposits for cash reconciliation using a configurable flat file format. The flat file is configurable and the preferred format is in the linked specification, however Epic can also support industry standard formats such as CCD+.

In addition to the Credit Card and Bank Account Integration specification, Epic provides separate and additional support for non-keyboard emulation credit card devices. This integration is handled through an interface between Epic and your gateway software. The gateway software integrates with the device and provides Epic with transaction results for the credit card payment. This integration is handled through the patient kiosk and by front desk personnel during check-in or check-out. This interface is supplemental to the generic credit card interface described above and should be implemented in addition to that interface if you want to provide support for EMV devices.

Epic can generate a flat file extract to collections agencies containing information about charges assigned to the agency. Epic can also receive flat file imports with updates to those charges to support tracking of payments and changes to charges in Resolute.

Epic can generate a delimited plain text file of information that can be shared with a statement vendor. This file includes information about the patient and their Professional Billing balances in Epic. File format subject to change - fields and segments may be added or removed with future development. Programming should accept or ignore additional fields and segments when they occur gracefully.

Epic can generate a delimited plain text file of information that can be shared with a statement vendor. This file includes information about the patient and their Enterprise billing balances in Epic. File format subject to change - fields and segments may be added or removed with future development. Programming should accept or ignore additional fields and segments when they occur gracefully.