CONNECTINGONTARIO CLINICALVIEWER 9.2. Release Overview Webinar

Transcription

1 CONNECTINGONTARIO CLINICALVIEWER 9.2 Release Overview Webinar 1

2 New in Release 9.2 Agenda 1. Communication and Education Plan 2. Overview: Integration with Provincial Client Registry 3. Release 9.2 Demo/Overview 4. Contribution Sites and PCR Integration 5. ClinicalViewer Release Roadmap 2

3 Objectives To provide education/training for Release 9.2 to sites with a focus on trainers to prepare and educate selves and end-users To inform of education/training resources and materials To inform of changes for Contribution Sites regarding Admin Portal and testing 3

4 Release 9.2 Communications Plan Item: Introduction of Release Live Education for External Stakeholders Timing: October 17 October 25, 26, 27, 30, 31 November 1 Specific tactics: announcement 1 Audience: all contacts for connected and soon-tobe-live sites Website Update 1 Webinars Audience: trainers of live sites + others who wish to learn about the changes Overview of 9.2 Enhancements November 23 December 3 announcement 2 Audience: All contacts for connected and soonto-be-live sites Focus on Site Trainers Website Update 2 Go Live Announcement and Survey announcement 3 Audience: all contacts for connected and soon-tobe-live sites Website Update 3 Audience: general public Audience: general public Audience: general public Content includes: Notification of upcoming Release Sign-up for webinars Webinar with demo to explain and show the changes Direct to updated support resources Recorded webinar or demo Confirmation of Go- Live Post-go live survey on communications received 4

5 Education and Training Plan Item: (Doreen to do) Live Education for Delivery Partners Live Education for Sites Release Specific Materials Viewing Training Toolkit Contribution Training Toolkit E-learning modules Timing: October 25 October 26, 27, 30, 31, November 1 Mid November Late November Late November December Specific tactics: Webinar Audience: delivery partners across GTA, SWO and NER Webinars (8 total) Audience: leaders, trainers, clinical champions, project teams of live sites + soonto-be live sites within 2 months ehealth Ontario Website Connecting Ontario ehealth Ontario website & Collab Space Audience: delivery partners, site trainers and end-users ehealth Ontario website & Collab Space Audience: delivery partners, site leads ehealth Ontario website & Collab Space Audience: delivery partners, site trainers and endusers Content: Demo and What s New in Release 9.2 Slide deck Preparation considerations Review of education and training resources Role of delivery partner Demo and What s New in Release 9.2 Preparation considerations Review of education and training resources Recorded webinar or demo Announce ments What s New deck Link to training materials Updated tip sheets, training decks, guides etc. End-user Training toolkit Train-thetrainer Help Desk Training toolkit (N/A) Slide decks, guides PCR Integration pre and post Release site requirements Updated modules 5

6 ConnectingOntario ClinicalViewer 9.2 Release Overview Enhancements Integration with Provincial Client Registry Changes to Patient Search function Graphing functionality in Lab and Pathology Results portlet User interface changes Updates to Admin Portal R9.2 is currently deployed in Train environment Scheduled go-live in Production: December

7 Integration of ConnectingOntario and Provincial Client Registry (PCR) In Release 9.2, the Provincial Client Registry is integrated with ConnectingOntario As a provincial repository of patient identifier and demographic information, PCR is the source of truth In the ConnectingOntario ClinicalViewer, PCR enhances patient searches and provides current, accurate and trustworthy health care client identity information This back-end change has resulted in some front-end/user interface changes ConnectingOntario contribution processes will change for sites in flight for contribution implementation 7

8 Provincial Client Registry (PCR) What is PCR? Provincial asset that forms the patient identity backbone of the provincial electronic health record Links individual records from disparate systems to create a client s golden record using proprietary Master Data Management technology (Enterprise Master Patient Index) Sources demographic data from: Ministry of Health and Long-Term Care (MOHLTC) Registered Persons Database: representative of 98% of Ontarians Hospital sites/sources: >88% of Ontario s hospitals Wait Time Information System Cardiac Care Network Utilized by the provincial viewers or portal based services to query and retrieve patient demographic and identifier data in support of patient search and resolution 8

9 PCR Golden Record Each record from a given source is stored in the PCR as a distinct record (member) Based on a matching algorithm and supporting business processes, PCR links these source records into a distinct person (entity) which is assigned a PCR managed Enterprise Client ID (ECID) The Golden Record is a virtual record assembled in real-time for a given person entity, returning the latest demographics based on the date and time updated for a given attribute across sources 9

10 Provincial Client Registry (PCR) What is contained in PCR and available in ConnectingOntario ClinicalViewer? Patient Information from PCR Health Card Number (HCN) Ontario Medical Record Number (MRN) Legal Name (First, Middle, Last) Gender Date of Birth (DoB) Home Address displays under Address Home Phone Cell Phone - displays under Other Phone if available in PCR; most sites contribute only one phone number Where displayed in ClinicalViewer My Workspace Patient Search Patient Banner Patient Search Patient Search Patient Search Results Patient Banner Patient Search Results and the Patient Banner display information from PCR Data is updated through daily reports received from MOHLTC and in near real-time from hospitals and other sources Other phone number will likely not be available is not available in PCR and will not display 10

11 Integration of ConnectingOntario and PCR Benefits to Providers and Patients Provides fulsome and common patient demographic information across all points of service accessing the ClinicalViewer Allows for more accurate patient searches and more sophisticated client matching resolving duplicates A patient record is viewable even when the patient information has not been added to the ConnectingOntario Clinical Data Repository by a contributing organization (i.e., hospitals and LHINs) 11

12 Release 9.2 Demo Refer to Release 9.2 Changes Viewing (Slide Deck) 12

13 Release 9.2 Fixes R9.2 contains a number of fixes. These include but are not limited to: Consent Override Fixes Overriding consent should now always result in a refresh of the ClinicalViewer and the immediate display of previously blocked data Portlets will no longer display the Consent Directive warning indicating that there are blocked records after consent has been overridden for portlets when no records were returned Lab and Pathology Results Portlet : Group By sorting feature will now display all possible results Document Viewer : Patient's date of birth is now displayed in dd/mmm/yyyy rather than mm/dd/yyyy Timeline: Issue is corrected where the from and to dates initially displayed in the custom time interval dialog may not match the current timeline Refer to Release 9.2 Fixes for list of other fixes (to be posted in Release 9.2 folder) 13

14 Contributing Sites PCR Integration Admin Portal Changes 14

15 R9.2 Admin Portal Changes A number of enhancements in Admin Portal will facilitate site monitoring and handling of errors DLQ/EQ Viewer is renamed to Error Viewer 15

16 R9.2 Admin Portal Changes Updated Error Viewer Fields : Dead Letter Queue and Error Searches Search results display the Error code/description/error list columns instead of the Transaction ID/Source System ID/Sender ID. It is no longer necessary to use the magnifying glass to view the error details The following columns are available in the error viewer search results for Dead Letter and Error searches: Severity Error code Description Error List Sending System Message ID MRN Message Type Timestamp ER7 string Resolved Flag Related to 16

17 R9.2 Admin Portal Changes Resolved flag added to the Error Viewer Enables users to identify which errors have already been addressed. It is available as a search parameter, and the default search is for errors that are Not Resolved Search Query Search Result 17

18 R9.2 Admin Portal Changes Related to field added to the Error Viewer A free-text field entitled 'Related to' has been added to the Error Viewer This enables a site to identify other related issues against an error Free text entered in the Related to field is not searchable 18

19 R9.2 Admin Portal Changes Updated Error Viewer Fields: Suspend Errors Suspend errors: unknown or generic exceptions that require further investigation to determine the root cause of the issue, and subsequent corrective actions The following columns are available in the error viewer search results for Suspend searches: Severity Error code Description Error List Error List Sending System Message ID Message Type Timestamp ER7 string MRN Diverted Messages 19

20 R9.2 Admin Portal Changes Updated Error Viewer Fields: Diverted Messages Diverted Messages: messages associated with the suspended patient message. The first message is suspended and subsequent messages for that patient are diverted to the suspended queue The following information is displayed for the diverted messages: Timestamp Message ID Message Type Sending System Message Content 20

21 R9.2 Admin Portal Changes Export Site/Solution Administrators with access to the Error Viewer can now perform their own error handling and remediation processes more easily by exporting data into reports which contain the following fields: Severity Error Code Description Source System Name Message ID Timestamp HL7 Message Type 21

22 R9.2 Admin Portal Changes Date no longer required to search for a specific Message ID It is no longer necessary to specify a date when searching for a specific Message ID using the Error Viewer Removal of Date Range Restrictions Prior to release 9.1 the DL/EQ Viewers were limited to retrieving messages received within the previous 2 days The revised Error Queue viewer supports specifying an arbitrary date range for messages to review 22

23 Contributing Sites PCR Integration Testing 23

24 PCR Integration and Contributing Sites Release 9.2 ehealth Ontario is performing it s own testing of the icr/pcr transition icr/pcr transition regression testing is not required by current contributing sites to both PCR and CDR 24

25 PCR Integration and Contributing Sites Site Testing of CDR after Release 9.2 To facilitate testing of CDR after R9.2 when PCR is integrated, a site needs to be conformant with and contributing to PCR prior to CDR contribution Conformance Testing: Sites will need to point any test systems to feed test ADT data to the PCR lower environment, using their existing PCR interface design over the existing MPN connection Clinical Validation: No impact as a result of PCR integration Each site is expected to support an ongoing (or existing) ADT feed to PCR, as well as the clinical feed to CDR 25

26 PCR Integration and Contributing Sites Test patient/test data post R9.2 The PCR and the ConnectingOntario Clinical Data Repository (CDR) are supported by independent environments for both production and nonproduction needs Test patient/test data sent to the CDR today will not auto-populate the PCR lower environment To perform conformance testing Post 9.2, any test data/test patients will need to be contributed to both the CDR PST environment and PCR PST equivalent environment Sites that are already contributing to PCR today should already have a connection to the lower PCR environment, using the existing PCR interface configuration used by the site today to send their ADT data to ehealth Ontario Data source sites have to send 2 distinct feeds; one to PCR over a managed private network (MPN) as many hospitals currently do today, and the other data feed to the CDR. All but a small number of hospitals in the province are already contributing ADT data to the PCR, using a separate specification and interface configuration 26

27 PCR Integration and Contributing Sites Conformance testing and test patients in PST CDR (icr) Currently, there are no plans to migrate data from the icr lower environments to the PCR lower environments. Conformance testing approach recommended for sites scheduled for testing during this time is a) defer their conformance testing post R9.2, or b) complete conformance testing prior to R9.2 to avoid having to resend test patient data, or c) send test data to both CDR PST environment as well as PCR CONF environment concurrently, to ensure test patients are available in both environments 27

28 ConnectingOntario ClinicalViewer Release Roadmap Release10 In progress and scheduled for Spring 2018 Integration of Diagnostic Imaging Common Service (DI CS) Provincial repository of diagnostic reports and images Release 11 Planned for Summer 2018 Integration with Digital Health Immunization Repository (DHIR) Centralized repository of standardized electronic immunization data 28

29 Questions? Contact: 29