SFTP integrations enable secure file transfer between two entities. With an SFTP connection, your organization can either automatically push files to Rivet or Rivet can automatically pull files from your system.

Rivet leverages this type of integration for 835 and 837 files. When necessary, we can also transfer patient and appointment data in a .csv format via SFTP.

Rivet can work with any SFTP agent to securely deliver 835 and 837 data files through an automated SFTP upload. If your organization does not use an SFTP agent, we recommend Syncovery. You can read more on Syncovery here.

An API is a software interface that allows programs or applications to exchange data. This is our preferred integration method for importing patient demographic and appointment data due to the typically low cost and ease of implementation

Not all PM or EMR systems have APIs we can leverage, and it is very rare that we can pull 835 and 837 files via API. You can check out our integration roadmap to view the API integrations we have built to date and which we’re working on next.

API integrations offer the most extensive write-back integration functionality as well. With API integrations, Rivet is usually able to write claim notes and status changes that you record in Rivet back to your PM or EHR system. Often we can also post estimates and payments back to the PM or EHR system as well.

HL7 is a global standard for exchanging health information in a very compact format - similar to X12. It includes ADT (patient demographic) and SIU (patient appointment) data. Anytime a change happens in your EHR or PM system, the HL7 feed will send a formatted message outbound with information associated with the change.

HL7 messages are triggered by events such as patient check-in, editing a patient's profile, or scheduling a patient appointment. The source system pushes these changes to the receiver. Rivet accepts inbound ADT and SIU messages.

Rivet can also leverage an HL7 integration to automatically write claim notes and status changes that you record in Rivet back to your PM or EHR system.

ODBC refers to a direct-to-database way of connecting where one entity can write a query against another’s database and pull data out of it.

Rivet partners with Healthjump to extract patient demographic (ADT) and appointment (SIU) data from a number of PM/EHR systems. Healthjump is not a PM or EHR system itself, and we'll usually only recommend Healthjump when we don’t have an API integration with a system or your organization doesn't have an HL7 integration that Rivet can use.