Epic Integration: Technical details for Epic analysts

Owned by Michael Kopinsky
Last updated: Apr 16, 2024
2 min read

Most of the implementation details for Way to Health’s epic integration are in our implementation guide below.

This page serves as a supplement with a) an overview tying use cases (from ) to specific technical integrations, and b) some additional technical details not found in the implementation guide.

Implementation Guide

  File Modified

PDF File Implementation Guide - Way to Health (embed + backend).pdf

Nov 24, 2023 by Michael Kopinsky

PDF File Implementation Guide - Way to Health.pdf

Nov 17, 2023 by Michael Kopinsky

Required setup for each integration feature

Use Cases

Feature

Required Setup

Use Cases

Feature

Required Setup

Enrolling patients

Monitoring patients (data, messaging, and more)

Embed

  • Webservices access (via frontend OAuth2/SMART on FHIR)

  • Web App Integration Record (details below)

  • Web App Integration Launch Point (see Galaxy for details)

  • “Way to Health” client ID

Sending patient-entered data to the medical record via flowsheets

(Requires only one of these 3 approaches)

Inbound HL7 flowsheet via TCP/IP

  • VPN between your interface engine and ours

  • Flowsheet identifiers for use in OBX-3

Inbound HL7 flowsheet over HTTPS

  • “Way to Health - Backend” client ID

  • Flowsheet identifiers for use in OBX-3

Flowsheet - via AddFlowsheetValue

  • Webservices access (via Backend OAuth2)

  • Flowsheet identifiers (see details below)

  • “Way to Health - Backend” client ID

Flowsheet - via Observation.Create

Documenting program participation or status in the EHR

SDE

  • Webservices access (via Backend user)

  • SDE (HLX) ID

  • “Way to Health - Backend” client ID

Alerting clinicians or care teams of patients needing attention

InBasket

  • Webservices access (via Backend user)

  • Inbasket pool/HIP

  • “Way to Health - Backend” client ID

Triggering text outreach programs post-discharge

Turning participant messaging on and off during readmissions

Outbound HL7 ADT feed

  • VPN between your interface engine and ours

  • Establishing outbound interface

Triggering text outreaches prior to a procedure

Outbound HL7 Optime Scheduling feed

  • VPN between your interface engine and ours

  • Establishing outbound interface

Triggering text outreaches prior to an appointment

Outbound HL7 Cadence Scheduling feed

  • VPN between your interface engine and ours

  • Establishing outbound interface

Different approaches for Flowsheet

There are several mechanisms we can use to file flowsheet data. Which approach we use is largely dictated by your health system’s preferences or resource constraints. Details are at