Interface/EMR/EHR Overview

Interface/EMR/EHR Overview

EMR/EHR FAQs

An Electronic Medical Record (EMR) or an Electronic Health Record is stored medical information about a person. Both EMR and EHR are often used synonymously when referring to software.

Interfaces are available with most EHR/EMR and other third party systems using standard HTTPS, SFTP and API connections.

Encounters received through integration are brought in as Incomplete Charges allowing a coder or biller to review for accuracy.  After the Encounter is reviewed and saved, it is put in the status of Ready For Submission. It is then eligible to be batched to send electronically or printed.

 

The documentation focuses on the HL7 format and communication with interfaced applications.


Process

After our Sales and Interface team receive and process the request for an Interface, we have the ability to interface with EMR/EHR and other third party groups using standard HL7, SFTP or API connections. Here we will focus on the use of the HL7 format to communicate between the PM System and your EMR/EHR. Once the setup is completed, Charges are imported from most EMR/EHR Systems using standard HL7 messaging. We display these Encounters as Incomplete Charges. A Coder or Biller should review them for accuracy and save as Complete.  After the Encounter is saved, it is ready to be batched and sent electronically or printed.

For Processing Incomplete Charges that are imported through the Interface, see Process Incomplete Charges​​ and Incomplete Charge Review Overview.

Learn More

  1. Interface Dashboard
  2. Interface Troubleshooting

    • Related Articles

    • Interface/EMR/EHR Management (Table of Contents)

      Contents Interface/EMR/EHR Overview HL7 Acronyms Incoming Mappings Change a Mapping Interface Troubleshooting Error - Unable to be Mapped Delete a Mapping
    • Interface Troubleshooting

      The following steps help you to investigate an Interface issue. Appointments are Not Updating on the Clinical Side Get a patient example. Go to Interface, and then go to Outgoing Messages. Select an Interface from the dropdown list. Select SIU from ...
    • Incoming Mappings

      As charges are created in your Clinical Documentation, the clinical terminology may need to be mapped to the correct items in the Billing Libraries. This may occur frequently after initially going live on the System, but should taper off quickly ...
    • Statements/Invoices Overview

      Statement and Invoice Profiles must be set up before Statements can be sent. Statements and Invoices must be set up separately. Both require Proofs to be approved. Statement Profiles Setup Setup for Invoice Billing System Settings for Invoices ...
    • Tags Overview

      Tags Overview The goal of Tags is to replace the need for Encounter Custom Claim Statuses which will give better access and functionality when working Charges. One of the key advantages of using Tags is that multiple tags can be attached to an ...