Menu

Epic EMR

Configured Socket Connection

The primary method of integration with Epic is through a configured socket connection; a TCP/IP socket that has been explicitly set up with custom parameters to optimize communication between networked applications. Beyond basic socket creation, configuration allows developers to fine-tune aspects such as:

  • IP address and port binding: Defines the local or remote endpoint for communication.

  • Timeouts: Controls how long the socket waits for operations like connect, read, or write before failing.

  • Buffer sizes: Adjusts the size of send and receive buffers to manage throughput and latency.

The Configured Socket Connections allows Epic to integrate with Quadax to leverage the following services:

  • Rapid Retest:

    • Rapid Retest leverages a Real Time Host Interface Module (RT HIM), which is a collection of services and APIs that allow a client to provide Quadax with an 837 and receive a 277 response in real time, through a configured socket connection. The intent of this integration is to consolidate the claim process while reducing duplicate efforts between Epic (source of truth) and Quadax by providing clients the ability to capture and fix errors up-front, prior to submission to the Payers.  

  • Real Time Eligibility

  • Claims Validation

  • External Account Look Up

    • The ExternalAccountLookup allows a user to query from Epic into Xpeditor and see all claims based on an account number query. The landing page for ExternalAccountLookup contains a grid in which users can view/open all of the claims that came back for the account number they query. The account number query is a starts-with query, therefore any account numbers in the Xpeditor system that start with the queried account number will be shown.

  • Remits

  • Comment Records

For additional information regarding Quadax / Epic integrations, please see: https://open.epic.com/Financial

MEDITECH EMR

Configured Socket Connection

The primary method of integration with MEDITECH is through a configured socket connection; a TCP/IP socket that has been explicitly set up with custom parameters to optimize communication between networked applications. Beyond basic socket creation, configuration allows developers to fine-tune aspects such as:

  • IP address and port binding: Defines the local or remote endpoint for communication.

  • Timeouts: Controls how long the socket waits for operations like connect, read, or write before failing.

  • Buffer sizes: Adjusts the size of send and receive buffers to manage throughput and latency.

The Configured Socket Connections allows MEDITECH to integrate with Quadax to leverage the following services:

  • Integrated Eligibility

Coming Soon:

  • Eligibility Verification - API

  • Claim Validation - API

Oracle Health (Cerner Millennium)

SFTP File Transfer

  • Quadax will leverage your already existing SFTP environment by providing your system with the appropriate login credentials and setting it up to place files in the designated folder.

  • File processing on the Quadax end is driven by the file name prefix, meaning the prefix you use when naming the files will determine how they are handled. For example, specific prefixes may be associated with different data types or workflows. While the prefix is essential, the rest of the file name is flexible: Quadax recommends including a unique identifier such as a timestamp to avoid overwriting files (e.g., prefix_20250603_0830.json).

  • Quadax utilizes the existing SFTP setup but does not manage the credentials or server configuration directly.

A SFTP File Transfer allows Oracle Health to integrate with Quadax to leverage the following services:

  • Eligibility

Coming Soon:

  • Eligibility Verification - API

  • Claim Validation - API