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.
...
Build and testing for a connected health program
TODO
Setup and testing for Epic integration
TODO
Information to send to Way to Health
...
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 Once we can access Interconnect, we have tools that can extract this PEM file |
Program changes and shutdown
...
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 |
...