Release Notes RelayClinical Platform 12.10

Transcription

1 Release Notes RelayClinical Platform Health Connections Brought to Life

2 Table of Contents About this Document... 3 Your Feedback Matters... 3 New and Enhanced Features... 4 RelayClinical Exchange... 4 Supported Browsers... 4 Service Corrections... 5 Development Update RelayHealth and its affiliates. All rights reserved. 2

3 About this Document This document highlights new and enhanced features included in the release of the RelayClinical Platform service. These Release Notes provide users, staff, and partners with details you need to get up and running with the new features and changes to the existing service. What We Include in this Document For every major enhancement, this document provides: A brief description of the new feature, enhancement, or workflow Instructions to help you get started with setup and administration, if applicable Screenshots to highlight changes to the user interface. This document also describes minor enhancements and service corrections we made since our previous release. Interested in what we re working on now? Check the Development Update section for brief descriptions of some of our upcoming features and enhancements. Your Feedback Matters At RelayHealth, we place high value on our customer, partner, and staff member feedback. Please take a moment to let us know how we re doing and how we can help you to meet your RelayClinical Platform service goals. You can submit suggestions, corrections, or comments by any of the following methods: Use the Contact RelayHealth link at the bottom of your Home page to send a secure message directly to our Customer Support organization. You can also call our toll-free number and speak to one of our Customer Support representatives from 4:30 am to 5:00 pm Pacific Time. Call RELAY-ME ( ) and select option 1. Speak with your RelayHealth Territory Director or Deployment Specialist. These RelayHealth professionals welcome your suggestions and comments about the service, your experiences with system use, and any concerns you may have. 3

4 New and Enhanced Features RelayClinical Exchange With release 12.10, we introduce the following enhancements to Continuity of Care Document (CCD) exchange: XDS Logic Modified to Use Source Patient ID for ID Routing and Certificate With this release, we modified XDS.b processing to make use of the source patient ID (Assigning Authority OID, located in the XDS.b message s source node) rather than the external patient ID. Going forward, RelayHealth will use the source patient ID for client certificate validation, message routing, and registry matching purposes. Using the source patient ID will allow RelayHealth to support circumstances in which a sending system uses one security certificate to send CCDs from multiple facilities with different MRNs. This enhancement also includes changes to client certificate logic. With this release, the service will now allow multiple Assigning Authorities to use the same client certificate thumbprint. OID Replaces GUID as Unique Document Repository Identifier In order to conform to the latest published IHE standard specifications for the XDS.b profile, with this release we adjusted the unique identifier used in XDS.b transactions that identifies the RelayClinical document repository in the US. Going forward, the unique identifier used will be an OID-formatted value, which replaces the previous GUID value. This change will allow the RelayClinical service to continue to act as a repository of patient health information and will allow XDS.b state registries to retrieve documents successfully from our repository. Supported Browsers With release 12.10, we adjusted the list of browsers supported for use with the RelayClinical service. We have removed support for Internet Explorer version 6. The current list of supported browsers is: Microsoft Internet Explorer 7 and 8 on Windows XP and IE 9 on Windows 7 OS Firefox 3.5 or later on Windows XP and higher Safari 4 on Mac OS 10.4 and higher 4

5 Service Corrections In this release, we made the following service corrections in response to customer- and staff-reported issues: We corrected an issue that caused a customer to report failures in the merge duplicate patient records workflow. This issue was related to patient records that included very long diagnosis descriptions. With this correction, the diagnosis data no longer causes merge failures, and the customer can merge patient records successfully. We corrected an issue in which patient invitations sent with only an address, instead of name and address, did not appear in the Sent Invitations report. With this correction, the invitations appear in the Sent Invitations report as expected. We corrected an issue in which several customers reported that outbound RelayClinical service messages failed to transmit to customer EMRs as expected. With this correction, customers report that the issue has been resolved and messages now transmit to the EMRs successfully. We corrected an issue in the Data Administration feature that caused users to receive errors when attempting to review data for results messages. With this correction, end users can now access results message data from the Data Administration feature without error. We corrected an issue in escript that caused customers to receive an error when they attempted to access the View All link in the Medication Hx panel. This issue has been resolved, and customers can now access and select from the medication history list as expected. 5

6 Development Update We recently began the development process for the service enhancements listed below. Look for detailed communications related to these items in the near future. Patient Panel Reassignment This feature will introduce a new workflow in the service that will allow Practice Administrators to assign a patient panel from one provider to one or more other providers who are members of the same health system (affiliation). When completed, Practice Administrators will be able to manage patient reassignment efficiently by reassigning patients in bulk, rather than on a perpatient basis. Practice Administrators will find this new feature useful under circumstances in which a provider leaves a practice or clinic (e.g., transfer to new location, graduating resident physician(s), provider leaves the health system, etc.). Allscripts Messaging API This feature will allow for messaging integration between the RelayClinical service and Allscripts Enterprise EHR and will allow for exchange of clinical and administrative types of provider and patient messages. When completed, this feature will allow providers to transmit messages to RelayHealth patients where the message will populate the patient s RelayHealth inbox, while messages from RelayHealth patients to providers will populate the provider s Allscripts EHR inbox. Secure Registry Transactions This feature will allow customers to leverage the RelayClinical service to publish data to patient registries using SOAP web services. When completed, the service will have the ability to notify a registry that data is available for a specified patient, and that patient data can then be retrieved by authorized registry users when and if requested. Patient Identifier Cross-Referencing (PIX) in XDS.b Transactions This feature will allow RelayHealth to support the IHE industry standard for patient identity mapping when supporting cross-enterprise document sharing (XDS.b) transactions. When completed, this feature will use HL7 messaging conventions to resolve patient identity between a document repository actor (e.g., RelayHealth) and a document registry actor (e.g., a statelevel patient registry). 6