Most of the setup process and instructions you can find Third-Party App Setup and Support Guide on Galaxy. This document serves as a supplement - it adds details specific to Way to Health, and points you to specific sections of the Galaxy document as not all portions of that document are necessary.

Overview

The Way to Health platform powers a diverse range of programs with different workflows and integration needs. Our app listings specify the broadest set of APIs and interfaces we use, but each connected health program will only use a subset. In this document we’ll try to specify which features, which setup, and which apps are required for specific types of connected health programs.

Much of this setup is applicable to all Way to Health programs - once the Embed is set up for one program, no additional IT setup is required to launch a second (or third, or thirty-third) program. If a future program requires an additional integration point (such as an outbound ADT feed), subsequent programs will be able to use that with no additional IT setup. The only exception is flowsheet rows and inbasket pools, which typically are set up per-program or at least per-care team or per type of data.

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.

Use Cases, Features, and Required Setup

Use Case	Feature	Required Setup
Enrolling patients Messaging them manually Viewing data	Embed	Webservices access (via OAuth) 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 flowsheets	Flowsheet - via webservices	Webservices access (via Backend user) Flowsheet FLO, FLT (Details below) “Way to Health - Backend” client ID
Sending patient-entered data to flowsheets	Inbound HL7 flowsheet feed
Alerting clinicians or care teams of patients needing attention	InBasket	Webservices access (via Backend user) Inbasket pool/HIP (details below) “Way to Health - Backend” client ID
Triggering programs post-discharge Silencing programs during admissions	Outbound HL7 ADT feed
Triggering pre-procedure programs	Outbound HL7 Optime Scheduling feed

Information to send to Way to Health

(reference: Send Specific Information to Your App Vendor)

	When do we need this?	Example
Patient ID Type	Always	“MRN”, “HUP MRN”, “MR”, etc.
Interconnect Base URLs Prod OAuth Non-prod OAuth	Embed	`https://vendorservices.epic.com/interconnect-amcurprd-oauth/`
Interconnect Base URLs Prod Basic Auth Non-prod Basic Auth	Backend App (flowsheet, inbasket)	`https://vendorservices.epic.com/interconnect-amcurprd-username/`
Backend user EMP Username Password	Backend App (flowsheet, inbasket)	`waytohealthuser` / `15 char random string`
Inbasket pool Pool ID (HIP .1)	Each Inbasket where we’ll send escalations	`14234`
Flowsheet information FLT .1 FLO .1	For each data point (e.g. systolic BP) that we’ll send via WebServices
Network configuration	If needed to access Interconnect
VPN info To be worked out between your networking/security team and our sysadmin team	If we’re using a TCP-based HL7 feed (in either direction) For inbound HL7 flowsheet, we can use the HL7v2 webservice instead
Root CA	If interconnect uses TLS certificates that are self-signed or signed by a CA not in Mozilla’s trust store	PEM file such as `yourhospital_root_ca.pem`

Epic embed

Desktop Integration

The Galaxy document Create Integration Records for Active Guidelines describes how to create the embedded view. Here are the details you’ll need to supply as you complete that setup:

Recommended method, using SMART launch

reference: Configure the Integration Record for SMART on FHIR

Client ID	Prod:	`3aa086b8-6dfb-4143-9100-b8e003ebe2a2`
Client ID	Non-prod:	`3ced6ceb-0741-4cf1-83ba-99f3b34d600a`
Integration type	SMART on FHIR
Authentication Method	SMART on FHIR
Launch URL	Prod:	`https://app.waytohealth.org/epic/smartLaunch`
Launch URL	Non-prod:	`https://staging.waytohealth.org/epic/smartLaunch`
Launch Context	`epicUsername`	`%SYSLOGIN%`
	`userFirstName`	`%USERFNAME%`
	`userLastName`	`%USERLNAME%`
	`mrn`	`%EPTID;;; ; ;nnnn;NONE;%` Instead of `nnnn`, use the ID type that w2h will use. See the launch token library for details.
	`csn`	`%CSN%` In some contexts this value will be empty, but if the embed is launched in the context of an encounter, having the CSN is useful for some workflows
	`frameAncestor`	`%CLIENTHOSTSOURCE%`

Legacy launch, using AES encryption

reference: Configure the Integration Record for HTTP GET

Type	1-PACS
Model	10-Web PACS
Patient ID Type	A value should be specified here, but will depend on your health system
CRYPTURL	Prod:	`https://app.waytohealth.org/epic/embed?encrypted=%CRYPTSTR%`
CRYPTURL	Non-prod:	`https://staging.waytohealth.org/epic/embed?encrypted=%CRYPTSTR%`
CRYPTALGO	AES128
CRYPTIVLENGTH	0
Launch Context	`EPICUSERID`	`%SYSLOGIN%`
	`USERFNAME`	`%USERFNAME%`
	`USERLNAME`	`%USERLNAME%`
	`PATID`	`%EPTID;;; ; ;nnnn;NONE;%` Instead of `nnnn`, use the ID type that w2h will use. See the launch token library for details.
	`CSN`	`%CSN%` In some contexts this value will be empty, but if the embed is launched in the context of an encounter, having the CSN is useful for some workflows
	`frameAncestor`	`%CLIENTHOSTSOURCE%`

Flowsheet

via WebServices

We need the following information:

For each data point (e.g. systolic blood pressure), we need the flowsheet ID and flowsheet template ID. These correspond to the

You should name the flowsheet rows to be clear that this

via HL7

Inbasket

Base requirements:

Webservices access (see “User and Security Setup” above)
Requires installing backend app

Project setup

We need Pool ID (HIP.1)
We typically send messages as Staff Message (message id type = 1). Sending messages into other folders requires more complex setup - consult your Epic TS for details on which message types can receive messages via API.

Other optional setup

Smart forms?

Used at LGH. probably don’t want to recommend to the general public

Smart phrases?

Program changes and shutdown

All program changes (including shutdown requests) should be submitted through our help desk located at support.waytohealth.org

Implementation guide