Note: The “Zoom API Key” and “Zoom API Secret” fields should not be removed from the configuration.

New and Enhanced Features

• Enforce Scope - Currently when a user turns on “Enable Scopes”, it automatically fills in all the scopes that we have for Canvas. Now “Enforce Scopes” would only show the scopes associated with the feature that the user has turned on or the scopes that the user has selected from their platform.

• Section selector for Section Aware - There may be times an instructor wants a recording viewable by more than one of their sections. A section selector is provided to allow instructors a way for exceptions / to allow other sections to see the recordings if necessary.

  

  

• Alternate host search by name - Auto-populate and simplify the search process for the alternative host in the LTI meeting scheduler.

  

Resolved issues

• Bug fixes related to the LTI PRO section aware in Firefox

• Student role to the 40-minute limit reminder in the LTI meeting scheduler.

(1) Template for uploading practitioners

Currently it may not be clear how to upload practitioners using a CSV file. A template is now available that you can download from the Cerner practitioner page.

(2) Disable automatic appointment status update

Currently when a patient launches into a video visit, the integration will automatically update the Cerner appointment status to “checked-in”. If it is not desired to have this automatic status update, it can now be disabled in the configuration.

(3) New “Appointment Prepared” webhook

A new webhook notification type “Appointment Prepared” is now supported that indicates when an appointment has been updated with the Zoom meeting URLs. When this new webhook notification type is enabled in the configuration page,  a webhook notification will be sent to the configured endpoint. 

The webhook notification will contain appointment id, user type (2 = patient), user id (patient id), action (0 = appointment is prepared with meeting links) and patient join url.

In the Notification Records tab you can select the “Appointment Id” option, enter the appointment id, and click the Search button to display the “Appointment Prepared” notification record.

(1) Basic auth for customer network authorization

Customers wanting to validate messages from the Epic FHIR integration at their gateway/firewall before passing them into their network can now set up a custom basic auth header in the configuration page. Once enabled and set up, all messages from the Epic FHIR integration will carry a basic auth token using a customer defined header name

Structure of the header :

custom-header-name : Basic base64(username:password)

(2) Use logged-in user for video visit meeting

Currently when a provider launches a video visit, a “custCreate” user is created and used to start the video visit meeting. A new option is now available that would allow the provider to use their already existing Zoom user for the video visit. When enabled, providers will be required to be logged in to zoom.us. Once the user is already logged in, they will not be asked to login again. “custCreate” users will no longer be created for provider video visits.

To enable this feature, a new provider launch endpoint …/epicfhir/providerlaunchwithlogin is now supported. Customers must configure this new endpoint into their Epic FDI records used for provider launches instead of using the previous endpoint …/epicfhir/providerlaunch.

Support for multiple video visit appointment codes

Currently you can configure at most 1 regular video visit code and 1 group video visit code for identifying video visit appointments. After this release, you will now be able to configure multiple codes for both regular video visits and group video visits.

Instead of manually entering the codes, you have the option to upload a CSV file containing the video visit codes by clicking the “Upload” button.

Select a CSV file containing multiple video visit appt codes. A sample CSV file can be obtained by clicking the “Download CSV Sample” link.

After the upload, the video visit codes will be displayed.

You can also export either the regular or group video visit codes into a CSV formatted file.

Separate OAuth Authorization and Token Base URL Configuration

Currently you can only configure an “Epic OAuth Base URL” that the integration uses when getting OAuth authorization and OAuth tokens. This is a limitation for some customers that require different network/security settings for the authorization and token endpoints (e.g. when using an upcoming Mutual TLS feature). You can now configure separate OAuth Base URLs by enabling a new “Separate Auth/Tokens URLs” toggle on the integration configuration page:

(1) Group Visit ID Added to Notification Records

The group visit ID that is provided to the integration during group video visit launches will now be available in the Epic integration "Notification Records" tab.

(2) Resiliency when installation user has permissions reduced

The integration obtains an OAuth token when the integration is installed and authorized by an admin user. If that user has their roles reduced, is deactivated, or is removed from the account, the integration will not work properly. Enhancements will made to address these situations but it requires that multiple admin users install the integration from Marketplace. When the integration detects an issue with the OAuth token it is actively using, it will automatically switch to using the OAuth token of another user. In addition, it will send an email to the configured email address to provide notification of the situation so that action can be taken.

A new “Account Alerts Delivery Email” field is added to the Epic app configuration page. Configure the email address to receive notification when an issue is detected:

Below is an example email sent when the integration detects an admin user has been downgraded or deactivated:

Note: To check a user’s role and status, visit the admin’s user management section on the Zoom account portal   : https://zoom.us/account/user#/

Webhook Notifications

Notifications can now be generated from the integration when the following actions occur:

• Practitioner joined video visit meeting

• Practitioner left video visit meeting

• Patient joined video visit meeting

• Patient left video visit meeting

New configuration parameters have been added for this enhancement

In addition to selecting which notifications are to be sent, “Auth Name” and “Auth Password” must be configured which will be used to include basic authentication in the notification (added to the HTTP “Authorization” header). A URL must also be configured to specify where the notifications are to be sent.

A new notifications records tab has been added to show details of sent notifications. The meeting ID or appointment ID corresponding to the video visit must be entered to show the corresponding notifications. Only notifications sent within the past 7 days can be viewed.

Notifications will be sent to the configured URL using the http GET method and will include the following as query parameters:

• appointmentId

• userId

• userType (1 = practitioner, 2 = patient)

• action (1 = joined, 2 = left)

• meetingId

• joinUrl

For example:

GET https://myserver@domain.com/myendpoint?appointmentId=4864183&userId=12753672&userType=1&action=2&meetingId=88094394350&joinUrl=https://applications.zoom.us/cerner?oid=hfutyiiouerhiIiKihJj8dh/hdYHJhf=&da=jjfuHjFS93DfuJJ84Hju&aid=fdtkKkdhfh3hf9Jdfumq

(1) New default Zoom app private key (Zoom Use Only for now)

Zoom is in the process of simplifying the integration setup and will be introducing a default auto-generated Zoom App private key. By using this default key, admins will no longer need to configure the private key themselves nor send the corresponding public key to Epic. Zoom is currently in the process of validating this feature with Epic. Customers should not yet use this feature.

(2) Non-admin access to notification records

The integration configuration will have a new ‘Healthcare Staff’ tab that admins can use to grant access to staff members so they can view the Epic FHIR notification records. Access is granted by configuring the staff member’s Zoom user email (users must be a Zoom user to access the notification records).

Granted staff members can use the link they receive via email to access the notification records which is used to view video visit meeting information. Staff members do not need to install the Epic FHIR app.

From the ‘Healthcare Staff’ tab, admins can delete users to revoke their access to the notifications records.

(1) Group video visits

The integration now supports group video visits. Each patient of the group appointment will receive an individual confirmation email after scheduling the appointment. All patients of the group appointment will join the same Zoom meeting via the meeting link in the confirmation email or reminder email. 

There is a new configuration field required to be set up to enable group video visits. Admins should enter a video visit code or description that is used by the integration to find group appointments.

Note that if video visit codes are used, the “Cerner Video Visit Code” and the “Cerner Group Video Visit Code” should not have the same value. If appointment descriptions are used, the “Cerner Appointment Description” should contain the text contained in the “Cerner Group Appointment Description”.

(2) “Patient Ready” status

Previously the patient status in the Smart-Launch app shows “scheduled” prior to the patient joining the meeting which then changes to “arrived” after the patient launches into the meeting. A new “ready” status has been added that a medical assistant can manually set the patient status to after performing pre-appointment activities. The status can be changed through a new “Ready” button in the Smart-Launch app.

Practitioners can use this new “patient ready” status to know when to join the video visit with the patient.