In sales, there’s a mantra of “Always be Closing/Selling”. From a product development perspective, the mantra is “Always be Listening”, in this case, to your customers and the market. At Rhapsody, we’ve integrated that product perspective into our development and our customers—and their feedback—have become critical drivers of our product strategy. With the release of Rhapsody 6.5 we have focused on helping our customers to deliver quality interoperability solutions efficiently while improving their delivery of care. We shifted 60% of our development resources to act on customer requests and feedback, enhancing the customer experience and expanding Rhapsody’s functionality.
We were thrilled to kick off 2019 with an exciting new brand that emphasizes our refocus on the product and our commitment to the customer experience. Rhapsody 6.5 celebrates this with a new look and feel that better aligns with our refreshed brand promise. In the spirit of our brand, Rhapsody 6.5 further enhances the customer experience with improved support for Windows high DPI scaling, enabling users to take advantage of the strong clarity and sharpness potential offered by high-resolution screens. We are also improving the testing experience by exposing APIs for filter testing functionality, making it possible to include filter testing in continuous integration pipelines.
Rhapsody built its reputation on helping diverse health organizations deliver care by providing connected solutions with our deep industry knowledge and various interoperability solutions. We are excited to expand these capabilities in Rhapsody 6.5 to support broader customer needs. This is highlighted by the introduction of advanced routing, a highly requested capability. Users will now be able to act on messages that failed to transmit, improving the ability to automate error handling. We have also bolstering our Directory communication point, expanding its features to gain parity with our (S)FTP communication point. Customers will now have greater flexibility when using Directory communication points and will be better positioned to protect the integrity of the interface by restricting the files that will be processed.
The following are Rhapsody 6.5’s most notable key features:
- Product Usage Data: Rhapsody is now embracing data-driven decision making to enhance the product and user experience. Rhapsody 6.5 introduces the ability to gather product usage data to better understand customer behavior. The information will impact Rhapsody’s decisions pertaining to product prioritization, improvements, documentation and training.
- Test Execution and Monitoring: Another highly requested enhancement is the inclusion of APIs for test management and execution. These APIs extend the testing options by enabling the management and execution of filter tests in the Rhapsody Engine.
- Rhapsody IDE Update: In addition to sporting Rhapsody branding, the IDE has been enhanced to better support Windows high DPI scaling. This results in a crisper appearance when using high DPI scaling (over 100%) and on popular high-resolution screens.
- Advanced Routing: This highly requested feature extends Rhapsody’s message routing capability. Rhapsody 6.4 introduced Continued Routing on Success to support store-and-forward and deposit-and-notify workflows. Rhapsody 6.5 extends Advanced Routing by introducing Continued Routing on Failure. Messages that fail transmission are tagged with message properties capturing the failure reason and are made available for re-routing via the new error connectors on the communication points. This enables the automation of error handling.
- DICOM Update: DICOM capability has been enhanced by the introduction of 64-bit filters to convert between DICOM and XML formats and to extract images from DICOM messages. This means that customers processing DICOM messages can use the 64-bit Rhapsody engine and larger messages by giving their engines access to more memory.
- Directory Communication Point Update: In response to customer requests, the Directory communication point has been extended to bring better feature parity with the (S)FTP communication point. This gives the Directory communication point greater flexibility and ability to process only the expected file.
