Versions Compared

Old Version 4

changes.mady.by.user Michael Y. Kopinsky (Unlicensed)

Saved on

compared with

New Version 5

changes.mady.by.user Michael Y. Kopinsky (Unlicensed)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

The specific setup needed depends on which Way to Health integration features are used, and which method we

Feature

Required Setup

Required apps

Embed

  • Webservices access (via Oauth)

  • FDI (details below)

  • E2N, E2U, etc. (see Galaxy for details)

  • Way to Health [link]

Flowsheet - via webservices

  • Webservices access (via Backend user)

  • FLO, FLT (Details below)

  • Way to Health - backend [link]

Flowsheet - via HL7 feed

InBasket

  • Webservices access (via Backend user)

  • HIP (details below)

  • Way to Health - backend [link]

Webservices access

To access webservices, we need:

  • Install app(s)

  • Backend user (if needed)

  • security, public key, not sure what else

Epic embed

User and Security Setup

...

Parameters we need

Devs need to know:

  • Base URLs

    • prod

    • non-prod

    • basic auth (if used)

    • oauth (if used)

  • Which features will be used?

    • embed?

    • flowsheet?

    • inbasket?

Desktop Integration

Here are the w2h details you need to put on the FDI (referenced in section 1.2.3.4 of the Galaxy instructions):

Desktop Integration

...

Recommended method, using SMART launch

Launch URL

Prod: https://app.waytohealth.org/epic/

embed?encrypted=%CRYPTSTR%

parameters

  • EPICUSERID=%SYSLOGIN%

  • PATID=%xxxx%

  • USERFNAME=%xxxx%

  • USERLNAME=%xxxx%

v2: Future (using SMART launch)

Launch URL

smartLaunch

Non-prod: https://appstaging.waytohealth.org/epic/smartLaunch

parameters

  • epicUsername=%SYSLOGIN%

  • mrn=%EPTID;;; ; ;nnnn%nnnn;NONE;%

    • Instead of nnnn, use the ID type that w2h will use. See the launch token library for details. Using %PATID% instead can work too, as long as the correct MRN is sent.

    mrn_type=xxxxx

    • The alphanumeric MRN type (e.g. HUP MRN), used to look up demographics

  • csn=%CSN%

    • 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

  • userFirstName=%USERFNAME%

  • userLastName=%USERLNAME%

Method

SMART

Legacy launch, using AES encryption

Launch URL

https://app.waytohealth.org/epic/embed?encrypted=%CRYPTSTR%

parameters

  • EPICUSERID=%SYSLOGIN%

  • PATID=%xxxx%

  • USERFNAME=%xxxx%

  • USERLNAME=%xxxx%

Method

AES

Flowsheet

via WebServices

Sending data to flowsheets is part of the Premium Epic Integration package. It requires installing the Way to Health - PremiumBackend app from Connection Hub, and incurs an additional cost

We need the following information:

  • For each data point (e.g. systolic blood pressure), we need the flowsheet ID and flowsheet template ID. These correspond to the

You should name the flowsheet rows to be clear that this

via HL7

Inbasket

Base requirements:

  • Webservices access (see “User and Security Setup” above)

  • Requires installing backend app

Project setup

  • 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

Smart phrases?