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.
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
The Way to Health is a platform powers used to power a diverse range of programs in the realms of programs with 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.
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
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 dataWay 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.
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 Case | Feature | Required Setup |
|---|---|---|
Enrolling patients Messaging them manually Viewing data Monitoring patients (data, messaging, and more) | Embed |
|
Sending patient-entered data to the medical record via flowsheets | Flowsheet - via webservices |
|
Inbound HL7 flowsheet feed | ||
Alerting clinicians or care teams of patients needing attention | InBasket |
|
Triggering text outreach programs post-dischargeSilencing programs during admissionsTurning participant messaging on and off during readmissions | Outbound HL7 ADT feed | |
Triggering pre-procedure programstext outreaches prior to a procedure | Outbound HL7 Optime Scheduling feed | |
Triggering text outreaches prior to an appointment | Outbound HL7 Cadence Scheduling feed |
Information to send to Way to Health
...
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: |
|
Non-prod: |
| |
CRYPTALGO | AES128 | |
CRYPTIVLENGTH | 0 | |
Launch Context |
|
|
|
| |
|
| |
|
Instead of | |
|
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 | |
|
| |
Flowsheet
There are a few different options for sending flowsheets, with pros and cons to each.
Method | Cons | Pros | Status | |
|---|---|---|---|---|
| 1 | AddFlowsheetValue |
|
| In use currently |
| 2 | Observation.Create (as backend user) |
|
| Can consider switching |
| 3 | Observation.Create (using patient access token) |
|
| Non-starter |
| 4 | HL7 clinical flowsheet |
|
| In use at LGH, in progress at UPHS |
| 5 | HL7 Incoming Clinical Documentation Flowsheet Data – Patient Entered writes to Device-Entered flowsheets |
|
| The order is a significant obstacle - some clinical programs may be OK with that, but so far we haven’t gotten traction with this. |
| 6 | HL7 Incoming Clinical Documentation Flowsheet Data Interface writes to Clinical Flowsheets |
|
| Not allowed since patients can modify data |
| 7 | HL7 over TCP/IP (for any of the 3 options above) |
|
| At Penn we don’t need a VPN, and any HL7 messages can go direct to Ensemble. We are requesting HL7v2 over HTTPS for outside health systems in case the HL7 methods above make sense there. |
| 8 | HL7 over HTTPS (for any of the 3 options above) |
|
|
via HL7
Mechanism can be either actual HL7 feed (in which case we need VPN) or HL7v2 interconnect (link to Galaxy doc for details)
Type of flowsheet can be:
via WebServices
We need the following information:
...
You should name the flowsheet rows to be clear that this
...
XXXXXX
Inbasket
Base requirements:
...
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
...
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.
Program changes and shutdown
...