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. Our main Implementation guide contains an overview of all our Epic integration features and the setup needed for them. This document contains the setup specific to programs that only use our Embedded View, and not the other integrations.

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.

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

Information to send to Way to Health

(reference: Send Specific Information to Your App Vendor)

	Example
Patient ID Type	“MRN”, “HUP MRN”, “MR”, etc.
Interconnect Base URLs Prod OAuth Non-prod OAuth	`https://vendorservices.epic.com/interconnect-amcurprd-oauth/`
Network configuration If needed to access Interconnect
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` Once we can access Interconnect, we have tools that can extract this PEM file

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%`

Program changes and shutdown

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

Implementation guide - embed only