Versions Compared

Old Version 7

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

Saved on

compared with

New Version 8

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

Saved on

Key

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

...

Table of Contents
minLevel1
maxLevel6
outlinefalse
typelist
printablefalse

Overview

The Way to Health platform powers a diverse range of programs with different workflows and integration needs. 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 programs.

...

Your Way to Health implementation lead will guide your clinical, operational, and IT teams in deciding which features are needed for the specific program(s) you are implementing.

Use Cases, Features, and Required Setup

Use Case

Feature

Required Setup

Enrolling patients

Messaging them manually

Viewing data

Embed

  • Webservices access (via OAuth)

  • 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 flowsheets

Flowsheet - via webservices

  • Webservices access (via Backend user)

  • Flowsheet FLO, FLT (Details below)

  • “Way to Health - Backend” client ID

Inbound HL7 flowsheet feed

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 programs post-discharge

Silencing programs during admissions

Outbound HL7 ADT feed

Triggering pre-procedure programs

Outbound HL7 Optime Scheduling feed

Information to send to Way to Health

(reference: Send Specific Information to Your App Vendor)

...

Recommended method, using SMART launch

reference: Configure the Integration Record for SMART on FHIR

Client ID

Prod:

3aa086b8-6dfb-4143-9100-b8e003ebe2a2

Non-prod:

3ced6ceb-0741-4cf1-83ba-99f3b34d600a

Integration type

SMART on FHIR

Authentication Method

SMART on FHIR

Launch URL

Prod:

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

Non-prod:

https://staging.waytohealth.org/epic/smartLaunch

Launch Context

epicUsername

%SYSLOGIN%

userFirstName

%USERFNAME%

userLastName

%USERLNAME%

mrn

%EPTID;;; ; ;nnnn;NONE;%

Instead of nnnn, use the ID type that w2h will use. See the launch token library for details.

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

frameAncestor

%CLIENTHOSTSOURCE%

...

reference: Configure the Integration Record for HTTP GET

...

Launch URL

...

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

...

parameters

...

EPICUSERID=%SYSLOGIN%

...

  • USERFNAME=%xxxx%

  • USERLNAME=%xxxx%

    • Method

    AES

    Type

    1-PACS

    Model

    10-Web PACS

    Patient ID Type

    A value should be specified here, but will depend on your health system

    CRYPTURL

    Prod:

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

    Non-prod:

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

    CRYPTALGO

    AES128 (question)

    CRYPTIVLENGTH

    0

    Launch Context

    EPICUSERID

    %SYSLOGIN%

    USERFNAME

    %USERFNAME%

    USERLNAME

    %USERLNAME%

    PATID

    %EPTID;;; ; ;nnnn;NONE;%

    Instead of nnnn, use the ID type that w2h will use. See the launch token library for details.

    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

    frameAncestor

    %CLIENTHOSTSOURCE%

    Flowsheet

    via WebServices

    ...

    We need the following information:

    ...