Release Notes RelayClinical Platform 12.3

Transcription

1 Release Notes RelayClinical Platform 12.3 Health Connections Brought to Life

2 Table of Contents About this Document... 3 Your Feedback Matters... 3 RelayHealth Maintenance Notification... 4 Service Corrections... 5 Development Update RelayHealth and its affiliates. All rights reserved. 2

3 About this Document This document highlights an important service downtime announcement and service corrections included in the 12.3 release of the RelayClinical Platform. This release does not introduce any feature or functional changes to the service. 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 RelayHealth Maintenance Notification Important Announcement RelayHealth Clinical Platform Maintenance on March 16, 2012 What is happening? At RelayHealth, we are continuously investing to improve our infrastructure. As such, we are migrating our platform infrastructure to a new data center (hosting facility) to leverage new technologies and infrastructure solutions. This migration will give us a wide range of benefits ranging from improved efficiency in data-center operations and better performance, reliability and scalability for our solutions. What services will be impacted? The RelayHealth website ( and all interoperability services will be unavailable during the migration. All messages transmitted to RelayHealth will be retained for processing when the migration is completed. All services will be fully operational and service levels completely restored at the end of this activity. When is it happening? The migration is scheduled for Friday, March 16, :00 PM Pacific Time to Saturday, March 17, :00 PM Pacific Time. The total planned downtime will be 24 hours to accommodate the logistical and technical complexity of the migration. Please understand that we are making every effort to minimize the duration of the downtime. Customers should check for updates before, during, and after the migration. What do you need to do? We do not foresee any technical activities at your end as part of this migration effort. We wanted to ensure that you are aware of the planned outage and that you take action to prevent any non-essential alerts for your support staff. If you experience any issues with the use of the RelayHealth website and interoperability services after this maintenance window, please notify Customer Support at immediately. As always, we will provide updates on operational issues and site performance at Do you have additional questions? For all specific questions and concerns related to this migration, please call Customer Support at , option 1. 4

5 Service Corrections In this release, we made the following service corrections in response to customer- and staff-reported issues: We modified a patient merge validation check to include logic for reversal of first and last name. With this modification, the service will perform the additional validation for first/last name to return a more accurate demographic match score. We corrected an issue that allowed deactivated health systems to display under Advanced Search in colleague messaging workflows. With this correction, health system accounts that are no longer active in the RelayClinical Platform will not display in the Health System dropdown list. We corrected an issue that caused health system users to receive an error in patient merge workflows when they attempted to accept a patient relationship and enter a patient identifier that was already in use. With this correction, the service will alert the user of the patient identifier conflict and will allow acceptance of the patient relationship provided the user does not enter a previously assigned identifier. 5

6 Development Update We ve begun the development process for the service enhancements listed below. Look for detailed communications related to these items in the near future. Transfer Dependent Accounts This feature will introduce a new process in the RelayClinical service that will allow a primary account holder to disassociate a dependent s health record from his or her account and, in turn, allow the former dependent to register for a primary account with RelayHealth. When completed, this new feature is intended to support scenarios in which primary account holders and their dependents choose to proactively alter account relationships. For example, this feature will allow a child s dependent account health record and provider relationships to be transferred when he or she reaches legal age. ANSI 5010 Support in RelayClinical escript This feature includes making the necessary changes to the RelayClinical escript application to support ANSI 5010 transaction standards, as required by The Centers for Medicare and Medicaid Services (CMS). When completed, escript will be updated to use a new 270/271 transaction set for benefit eligibility checking, and the escript application will be certified by SureScripts for compliance with the new transaction and data display requirements. 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. 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. Advanced Directives This feature will enhance Health Considerations section of the patient health record to include a new Unspecified designation. When completed, users will have the option to select a new Unspecified radio button to reflect a patient s wishes more accurately for: Living Will, Advanced Healthcare Directive, Organ Donation, and Religious Beliefs that Might Influence Health Care. Orders Detail Summary This feature will enhance Results Manager to display a new Result/Status Change line for order panels within an order set. When completed, this enhancement is intended to allow users to verify the time and date of result status change to improve care coordination and clinical decision making. With this enhancement, the Result/Status Change information will also be included in the result s print view for both providers and patients. 6