MDsave Integrations with Electronic Health Records (EHRs)

MDsave is a bundled payment solution that your facility has selected to provide clear upfront pricing to patients and other payers and to facilitate disbursement of bundled payments to participating providers. MDsave bundles are purchased before the time of service by patients, care navigators, or your revenue cycle team's staff members.

To ensure the success of the program and ease of use of the MDsave platform, we highly recommend integrating MDsave with your Electronic Health Record (EHR). This will enable more seamless patient journeys by providing time saving and error prevention processes to speed up every interaction that your staff have with registering MDsave patients, purchasing services on their behalf, and reconciling the payments from MDsave.

We offer two options for our standard EHR integration, each with different levels of project scope and implementation timeline.

SMART on FHIR Application

A SMART app can be configured on most EHRs to allow authentication from the EHR to MDsave. This app can be launched from a shortcut on the toolbar on a patient record, work queue, etc. and will allow the user to seamlessly open MDsave in the context of their existing workflow. The MDsave implementation team will work with your Revenue Cycle team to determine where in the workflow they would like to integrate a link to MDsave.

The app also can be configured to allow authenticated users to request patient demographic data from the EHR to complete a checkout transaction.


Features

  • Single-Sign On from EHR
    • An MDsave bookmark or shortcut link can be configured to show up on relevant patient records or on dashboards in an EHR. When clicked by the user, the link will instantly send them to mdsave.com in another browser tab that is already authenticated and ready to use.
    • This will make it easy for staff to log into mdsave.com quickly, and not have to manage a separate login.
    • Depending on where in the workflow the link is created, the currently selected patient demographic information can be automatically sent directly to MDsave.

  • Patient Search
    • A user authenticated with the SMART app can search for registered patients from the MDsave checkout.
    • This will auto fill patient demographics data from the EHR to complete checkout.
    • A checkout transaction done this way will associate an EHR account or encounter number with an MDsave purchase at checkout and will remain linked during the entire Rev Cycle process.

Technical Implementation

Depending on the EHR, a shortcut link will be configured and added to relevant toolbars or the app can be launched directly from an apps menu.

When a user clicks the link, the SMART app initiates a sequence of FHIR requests that authenticates with the EHR and then creates a secure session in mdsave.com for that user and logs them directly into MDsave for Providers.

The app should be configured with input from PAD/Front Staff and Rev Cycle teams so that it is displayed in the places that are most relevant to the staff that will be using it to place MDsave into their existing workflows.


Requirements

  • An EHR that supports SMART on FHIR, e.g. Epic, Cerner, Athenahealth, etc.
  • IT or vendor resources to configure and install the app

Implementation timeline

  • MDsave will work with staff to establish the most efficient workflow.
  • Cloud-based implementation — No on-site or network-level IT work is required.

ADT Feed

When MDsave patients are registered in the provider’s EHR, the patient demographic information needed to purchase MDsave vouchers is automatically synced with MDsave. New patient encounters are automatically imported with the account number associated with the encounters. This allows hospital staff to select the encounter on checkout, and all information needed for the purchase to pre-populate. This ensures that the vouchers purchased are associated with the correct encounter.


Features

  • Real-time syncing of EHR accounts with MDsave accounts
  • As patients are registered with MDsave in the EHR, their MDsave accounts are automatically created with identical demographic information

Technical Implementation

A data feed over a secure site-to-site connection will be set up and configured so that registration events for MDsave patients will be sent over the data feed and processed in our system to synchronize the patient demographics and encounter information.


Requirements

  • An EHR or system that can send ADT messages over a secure channel
  • A dedicated VPN connection configured to connect the ADT feed

Implementation Timeline

6-9 weeks for planning, implementation, testing, and go-live

Related Articles