...
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 In Basket messaging, which are typically configured for a specific program or care team and therefore require program-specific customization.
...
For programs collecting blood pressures or other structured data, the Data Snapshot can be a useful way of viewing the BP data at a glance.
...
Flowsheet
<Description. >For programs collecting discrete data such as blood pressures, we can send that data back to the EHR to be filed in a flowsheet. (The Implementation
<Screenshot from a pt chart>
Automated enrollment
File transfer
<File transfer - we can work with you to do daily CSV file transfer>
HL7 ADT feed
<also useful for silencing>
HL7 scheduling feed (OpTime or Cadence)
In Basket
<Our Our primary recommended way of sending escalations is via Inbasket to a pool><Screenshot of an inbasket message>In Basket message to a pool. Some of our clinical teams will choose to use existing pools they use for communicating amongst themselves; others will create new pools specific to Way to Health programs.
Most Way to Health programs send messages using the Staff Message message type - this requires no additional EHR build. We can also send messages using a custom message type. The Implementation Guide contains instructions for setting that up if desired.
...
We can also send escalations to pagers, cell phones, or by email. (We do not include patient identifiers in escalation messages to pagers or cell phones unless an exception is approved by your privacy office.)
Escalations can also be monitored or managed in Way to Health’s Triage View.
SDEs
<Available out of the box: program status>
...
Your Way to Health Implementation Lead will work with you to gather requirements, build, and test a new connected health program. For multisite programs (e.g. a program launching at Penn followed by other locations), the program typically will be tested at the first site and will require much less testing at the subsequent sites (mostly covering any site-specific tweaks that may have been made).
...
Testing for Epic integration
<We’ll give you We will provide a test script for each feature>
Program changes and shutdown
<There Epic integration feature described above (embed, flowsheet, SDE, etc.). For the embed and In Basket, the test script only needs to be run once for Way to Health. Flowsheet and SDE test scripts may differ slightly for each program.
These test scripts can also be used as part of testing for Epic upgrades when warranted (primarily when Nova release notes indicate that things are changing in the affected areas).
Support, program changes, and shutdown
During the EHR setup process as well as during the setup of any connected health programs, there will be an assigned technical and project management point person. In addition, …>
Once a program is live, all any issues or program changes (including shutdown requests) should be submitted through our help desk located at http://support.waytohealth.org .