| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Overview
Way to Health is a platform used to power a range of programs in the realms of 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.
...
Once a program is live, all program changes (including shutdown requests) should be submitted through our help desk located at http://support.waytohealth.org
Technical details
Further details are included in the Implementation Guide, available on request.
Required setup for integration features
...
Use Cases
...
Feature
...
Required Setup
...
Enrolling patients
Monitoring patients (data, messaging, and more)
...
Embed
...
Webservices access (via frontend OAuth2/SMART on FHIR)
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 the medical record via flowsheets
(Requires only one of these 3 approaches)
...
Inbound HL7 flowsheet via TCP/IP
...
VPN between your interface engine and ours
Flowsheet identifiers for use in OBX-3
...
Inbound HL7 flowsheet over HTTPS
...
“Way to Health - Backend” client ID
Flowsheet identifiers for use in OBX-3
...
Flowsheet - via Observation.Create
...
Webservices access (via Backend OAuth2)
Flowsheet identifiers (see details below)
“Way to Health - Backend” client ID
...
SDE
...
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 text outreach programs post-discharge
Turning participant messaging on and off during readmissions
...
Outbound HL7 ADT feed
...
VPN between your interface engine and ours
Establishing outbound interface
...
Triggering text outreaches prior to a procedure
...
Outbound HL7 Optime Scheduling feed
...
VPN between your interface engine and ours
Establishing outbound interface
...
Triggering text outreaches prior to an appointment
...
Outbound HL7 Cadence Scheduling feed
...
VPN between your interface engine and ours
Establishing outbound interface
Different approaches for Flowsheet
There are several mechanisms we can use to file flowsheet data. Which approach we use is largely dictated by your health system’s preferences or resource constraints.
...
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
HL7
More information on setting up HL7v2 over HTTPS can be found in the Galaxy document Incoming HL7v2 Over HTTP or HTTPS Using Interconnect.
Setup required
New interface setup:
Interface Kind: Incoming Clinical Documentation Flowsheet Data [97]
No custom setting or custom executable codes used. All standard settings.
We have found success with having Bridges create a new encounter for each new data point received. That can be done by setting Bridges Profile variable VISIT_MATCH_USE_DATE_RANGE [80604] to 0 - Use visit ID only (default 1 - Use visit ID, then search by date range).
Sample message
| Code Block |
|---|
MSH|^~\&|WAYTOHEALTH|WAYTOHEALTH|YOUR_HOSPITAL|EPIC|20230614112200||ORU^R01^ORU_R01|12234|T|2.6
PID|1||0123456^^^^MR|876876^^^^WAYTOHEALTH|Doe^Jane||19600101
PV1|1||DEPT_A|
OBR|1||148745|29274-8^VITAL SIGNS MEASUREMENTS^LN|||20230614112132||||||||||||||||||F
OBX|1|NM|SYSTOLIC^INTRAVASCULAR SYSTOLIC^||126|^mmHg|||||F|||20230614112132
OBX|2|NM|DIASTOLIC^INTRAVASCULAR DIASTOLIC^||71|^mmHg|||||F|||20230614112132 |
Identifiers
The identifiers in OBX-3-1 (
SYSTOLICanDIASTOLICin the sample message above) can be modified if needed to match other flowsheet rows in your system.The dept ID (
DEPT_Ain the sample message) is used by Bridges to determine which dept to create an encounter inWe send MRN, First Name, Last Name, and Date of Birth in the PID segment. These are used for identity verification by Bridges. PID 4 contains the patient’s Way to Health ID, which isn’t used by Bridges but can be helpful for troubleshooting.
Observation.Create
Flowsheet identifiers
We can use two types of identifiers for flowsheet rows - either the FHIR ID or the FLO .1 ID coupled with an OID specific to your health system. FHIR flowsheet IDs can be generated in the Interface Programmer Menu in Text. (d ^AI -> Support Utilities -> Web Service Utilities -> Generate Encoded Flowsheet IDs. If you don’t know the health-system specific OID for flowsheet rows, your Epic TS can help. Reference SLG 4392308.