Customers using Corepoint’s Batch Processing have the ability to parse and modify incoming and outgoing large files to make them interoperable and immediately useful. This provides a tremendous advantage to organizations that exchange large files.

The technology allows healthcare organizations to send and receive batch file data through assembly or decomposition, in a size and format that applications require. This is all accomplished within Corepoint Integration Engine, allowing users to utilize the familiar actions and steps used to create interfaces and manage workflows.

Because batch files are delivered in a usable format, the files can process faster and without many of the errors that may occur with manual data manipulation. Without the ability to parse and modify the data, receiving organizations must modify the data, either manually or electronically, so it can be used by the intended application.

Batch Processing includes the ability to efficiently break apart and build up large files, as well as the ability to store large files for a period of time in a database before or after processing. Parsing the information contained in the batch files offers Corepoint customers an additional layer of control of the data.

Corepoint customers utilize Batch files for many different reasons. Some of the most common include:

  • Sending billing information to insurance companies/payers
  • Aggregation of HL7 ADT messages
  • Public health reporting
  • State reporting

See the Corepoint difference

For example, message distribution is a common workflow for billing workflows. In such a workflow, messages are presented in a large single file. That file is then broken up and sorted into three different data tables corresponding to receiving insurance companies. When it is time to build the separate billing files, a process is triggered to gather the messages from each data table into one file per data table and send them out to the correct insurance company. Once the batch is successfully sent, the process will purge the data tables.

In another common example, ADT messages are aggregated for hourly distribution. Real-time ADT V2 messages are inserted into a data table for scheduled batched delivery. A process is configured to run hourly which pulls all messages more than 24 hours old from the data table, sends them in a batch to a downstream system, and then removes them from the data table. This continues on an hourly-basis, batching messages, sending downstream, and purging.

Our Batch Processing technology offers users a comprehensive method of exchanging data contained in large files within Corepoint Integration Engine, which empowers hundreds of healthcare organizations as they manage data workflows.

 Print Friendly