Release Notes RelayClinical Platform 12.6

Transcription

1 Release Notes RelayClinical Platform 12.6 Health Connections Brought to Life

2 Table of Contents About this Document... 3 Your Feedback Matters... 3 New and Enhanced Features... 4 RelayClinical Results... 4 Results Manager Result Overlay Logic... 4 Service Performance Enhancements... 5 Service Corrections... 6 Development Update RelayHealth and its affiliates. All rights reserved. 2

3 About this Document This document highlights new and enhanced features included in the 12.6 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 Standard 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 Results Results Manager Result Overlay Logic With this release, we enhanced the overlay logic used in grouped, discrete value type results in Results Manager. Using the enhanced overlay logic, the service will now add any new OBXs not received in the previous ORU message and it will update any changes to any existing OBXs. Additionally, if an OBX is not included in the final result, it will not be overwritten but will still display as in the example below. Preliminary Result Preliminary Result Overlayed with Final Result The enhancement described above does not affect overlay logic for report value types and for hybrid values (a result that includes both discrete and report value types). For report and hybrid values, the service will continue to evaluate all OBXs in the newest result and display all those OBXs (replacing any OBXs from the previous results). This logic will continue to function unless the customer has chosen a configuration in which there is no overlay at all. In this case, the Results Manager queue displays two results (i.e., one for the final result and one for the preliminary result). 4

5 Service Performance Enhancements Our recent move to a new data center resulted in overall performance improvement to all areas of the service. The following are capacity additions to new data center, which improved both performance and scalability: Additional memory to database server More processing power to database server Network latency issue resolution Storage Area Network latency reduced with better drives and configuration We also provisioned many of the servers in our new data center with more memory and CPU to support future needs as the RelayClinical Platform continues to expand. To address service efficiency, we recently addressed performance optimization in the following areas: Data Warehouse Optimization We completed an enhancement to optimize the data warehouse to enable more efficient processing of BiClinical procedures. This enhancement improves Quality Reporting scalability and performance. Cloverleaf Optimization We completed a Cloverleaf enhancement that improves message processing time for customers that pass large amounts of data through the Cloverleaf service. IMS Optimization We completed an enhancement to support additional instances of IMS. This enhancement provides increased capacity to process messages and reduces latency. 5

6 Service Corrections In this release, we made the following service corrections in response to customer- and staff-reported issues: We corrected an escript Activity Report issue in which the report failed to populate when created for an individual patient with an apostrophe in his or her name (e.g., O Neal). With this correction, the service now recognizes the apostrophe character and creates the report as expected. We corrected an issue in the Batch Print Messages workflow that caused a customer to receive a Technical Difficulty error. This issue was related to a time zone offset. With this correction, the batch print workflow now responds without error. We addressed an issue in the Search Your Entire Network workflow in which the Patient Date of Birth field was incorrectly restricted to four characters. With this correction, end users may enter up to 10 characters in the field. We corrected an issue in which the Data Administration area displayed service errors when Administrators attempted to search for errored Clinical Results messages. With this correction, the Data Administration area of the service displays the messages as designed. We corrected a user interface navigation issue that caused the service to skip some fields in the Create a Patient workflow when users navigated from field to field by clicking the tab key. With this correction, the tab order from field to field now functions consistently. With this release we removed the Register for Training Events links from the Provider/Staff Home page and Help text because the links directed end users to a registration site that is no longer in use. We corrected an issue in which results routed to a default provider did not display the ordering provider s name in the patient s RelayClinical Record and in printed results. With this correction, results routed to default providers now display the name of the ordering provider if the ordering provider s name is received in an inbound results message. The ordering provider s name displays where appropriate for results data in the RelayClinical service (Results Manager, RelayClinical Record, printed results, etc.). We corrected a Quality Reporting issue in which medication allergies, medications, problems, and immunizations originating from a source EMR CCD were attributed to the last provider to interact with the patient record in the RelayClinical service. To support accurate Meaningful Use and PQRI reporting, this correction allows the service to parse the above patient data, originating from a source EMR CCD, and attribute the data appropriately to the provider sending the CCD rather than the last interacting provider. 6

7 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 per-patient 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 for cross-enterprise document sharing (XDS.b) transactions. When completed, this feature will use HL7 v2 messaging conventions to map patient identity between a document repository actor (e.g., RelayHealth) and a document registry actor (e.g., a state-level patient registry). Patient identity mapping is a prerequisite for sharing personal health information on a patient between enterprise systems within a community. 7