Overview

Way to Health is a platform used to power a range of programs in the realms of connected health, remote patient monitoring, and patient engagement. Most of our clinical programs use text messaging, but we also use surveys, connected devices, and other data sources.

This document is intended as a high-level overview of Way to Health’s Epic integration features, aimed at clinical or IT decision makers. Epic’s Third-Party App Setup and Support Guide on Galaxy also has

For technical audiences we can provide a more detailed Implementation Guide on request.

Different programs, different integration needs

Different Way to Health programs will have different workflows and integration needs. For example, Heart Safe Motherhood (a postpartum BP monitoring program) requires a way to enroll patients, start them in the program post-discharge, and send BPs received from the patient back to the medical record. Coloprep (a text program to improve colonoscopy prep) does not require manual enrollment, but instead uses an HL7 scheduling feed to enroll patients and trigger the text messages at the right time.

Your Way to Health implementation lead will guide your clinical, operational, and IT teams in deciding which features are needed for the specific program(s) you are implementing.

Setup once, use for multiple programs

Way to Health’s Epic integration requires a one-time setup before it can be used for any number of programs. For example, once the embed is available, health systems can begin enrolling and monitoring patients in as many W2H programs as they’d like with no additional IT setup. Similarly, once an outbound ADT feed is established, this can be used by any number of programs to start the intervention after discharge. This applies to all of the features described below except for flowsheets and InBasket messaging, which are typically configured for a specific program or care team and therefore require program-specific customization.

Use Cases and features

Epic embed: Enrolling and monitoring patients

<Screenshot: opening embed from More Link.> It’s up to you and your Epic analysts to figure out which menus it belongs in.

<Screenshot: list of programs - HSM sandbox, one other>

<Screenshot: enroll modal>

<Screenshot: inbox>

<Screenshot: BP snapshot>

Flowsheet

<Description. >

<Screenshot from a pt chart>

Automated enrollment

<File transfer - we can work with you to do daily CSV file transfer>

In Basket

<Our primary recommended way of sending escalations is via Inbasket to a pool>

<Screenshot of an inbasket message>

SDEs

<Available out of the box: program status>

<Also available: other SDE writes at various points in the intervention>

Smart Forms and Smart Phrases

Some of our health system customers use Smart Forms to drive some of the enrollment or tracking process. Some programs have set up Smart Phrases to pull flowsheet data sent from Way to Health into clinical notes. If you’re interested in using these tools, we can connect you with the IT staff or physician builders who set these up.

Implementation process

Build and testing for a connected health program

Your Way to Health Implementation Lead will work with you to gather requirements, build, and test a new connected health program. For multisite programs (e.g. a program launching at Penn followed by other locations), the program typically will be tested at the first site and will require much less testing at the subsequent sites (mostly covering any site-specific tweaks that may have been made).

Setup and testing for Epic integration

<We’ll give you a test script for each feature>

Program changes and shutdown

<There will be an assigned technical and project management point person. In addition, …>

Once a program is live, all program changes (including shutdown requests) should be submitted through our help desk located at http://support.waytohealth.org