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.
...
Way 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.
Use Cases,
...
features, and
...
required setup
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 programsThis table summarizes which integration features are available to support workflow needs, and the setup required.
Use Case | Feature | Required Setup |
|---|---|---|
Enrolling patients Monitoring patients (data, messaging, and more) | Embed |
|
Sending patient-entered data to the medical record via flowsheets (Requires only one of these 3 approaches) | Inbound HL7 flowsheet via TCP/IP |
|
Inbound HL7 flowsheet over HTTPS |
| |
Flowsheet - via Observation.Create |
| |
Alerting clinicians or care teams of patients needing attention | InBasket |
|
Triggering text outreach programs post-discharge Turning participant messaging on and off during readmissions | Outbound HL7 ADT feed |
|
Triggering text outreaches prior to a procedure | Outbound HL7 Optime Scheduling feed |
|
Triggering text outreaches prior to an appointment | Outbound HL7 Cadence Scheduling feed |
|
Implementation process
Build and testing for a connected health program
TODO
Setup and testing for Epic integration
TODO
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 |
|
Interconnect Base URLs
| Always |
|
Inbasket pool
| Each Inbasket where we’ll send escalations |
|
Flowsheet information | For each data point (e.g. systolic BP) that we’ll send via WebServices or HL7 | Either
OR
|
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’s TLS certificates are self-signed or issued by a private CA | PEM file such as |
...
Program changes and shutdown
All Once a program is live, all program changes (including shutdown requests) should be submitted through our help desk located at http://support.waytohealth.org
...
Mechanism | Content | Flowsheet row identifiers | Encounter | Receiving system | Requires VPN |
|---|---|---|---|---|---|
HL7 over TCP | HL7 message (ORU^R01) | OBX-3 identifier | Can be created by interface | Interface engine or Bridges | Yes |
HL7 over HTTPS | Interconnect | No | |||
Observation.Create | JSON | flowsheet ID (FLO .1) | Must already exist, and encounter ID in w2h |
...