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.

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 setup needed depends on which Way to Health integration features are used, and which method we 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.

Information to send to Way to Health

...

Webservices access

To access webservices, we need:

• Install app(s)

• Backend user (if needed)

• security, public key, not sure what else

Epic embed

Parameters we need

Devs need to know:

• Base URLs

  • prod

  • non-prod

  • basic auth (if used)

  • oauth (if used)

• Which features will be used?

  • embed?

  • flowsheet?

  • inbasket?

Desktop Integration

...

(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

Legacy launch, using AES encryption

reference: Configure the Integration Record for HTTP GET

Flowsheet

via WebServices

...