The Rhapsody integration engine delivers advanced messaging capabilities to health sector organization of all kinds. Rhapsody acts as an intermediary between multiple information systems, each with different messaging formats.
Product Overview
Rhapsody is an integration software tool that provides connectivity and data sharing within and among Hospitals, Information Exchanges and Public Health Organizations. Rhapsody’s integration lays the foundation for the delivery of consistent, efficient and high-quality patient care. Rhapsody incorporates system connectivity, routing, message persistence, transformation and reliable delivery. It encompasses three main components:
-
- Rhapsody Integration Engine is the main messaging service that implements communication, inter-format mapping, persistent message delivery, and message
- Rhapsody Integrated Development Environment (Rhapsody IDE) has an easy-to- learn graphical user interface to configure the functionality of Rhapsody
- Management Console is a web-based application that displays system status and performance monitoring. It also enables the sorting, viewing, editing and re- sending of messages in Rhapsody, and real-time monitoring of system logs and error conditions.
Two additional applications are provided to facilitate the monitoring of Rhapsody engines from remote devices:
-
- Rhapsody Mobile is an mobile application that provides the basic monitoring capability of the Management Console
- Rhapsody Dashboard is a web-based application that displays the notifications and system health of multiple Rhapsody engines in a single monitoring centric view.
Features
The Rhapsody engine integrates disparate health systems, providing secure connectivity, reliable message delivery and high performance. The Rhapsody engine processes messages received from external systems on components called communication points. These messages are then archived in Rhapsody’s message store to ensure reliable reception and delivery. Once the messages have been stored, they are delivered to one or more Rhapsody routes for processing, according to the Rhapsody engine’s configuration.
The messages then follow the paths as defined by those routes. During this process, a number of filters can be applied to each message as it passes through the routes. Each filter performs a given action on each message, such as mapping, property extraction, or acknowledgement generation. Upon completion of the route processing, the messages are delivered to one or more communication points that connect to the desired destination systems. All messages remain available in the message archive until the configured archive period. The Rhapsody archives are stored on the healthcare organization’s appointed local file system or storage area network.
Delivery
Rhapsody provides message delivery with the use of internal queues and Rhapsody’s Message Tracking features. Messages are persisted as soon as they arrive on communication points and at various stages of processing. This ensures that all messages can be reprocessed should a failure occur. Any message being processed when a failure occurs is automatically processed from the last persisted point. Delivery is provided through higher level messaging protocols such as the HL7 acknowledgement protocol. Message Tracking can be configured to resend messages and trigger notifications if positive acknowledgements are not received
Backups
Rhapsody provides an embedded backup mechanism that can provide full and incremental backups of the Rhapsody configuration and message store. The scheduling of the backups is configurable. The Rhapsody backup management is designed to complement standard infrastructure backup, and creates a compressed copy of the backed up data in a configured location for loading onto tape or other backup media.
Open APIs
Rhapsody provides Open APIs for remote monitoring and configuration management: both REST- and SOAP-based. These APIs provide the ability to monitor and perform management actions (such as starting a communication point) in external applications, by writing code that calls the published API services. Deployments can be automated by developing scripts utilizing the REST API.
Versioned Configuration
Rhapsody’s configuration management provides access to full configuration version history, and the ability to compare versions and to roll back to previous versions.
Rhapsody IDE
The Rhapsody IDE is a Windows®-based application that provides a graphical user interface for creating and editing Rhapsody configurations. At startup, Rhapsody IDE requests connection and login information for a running Rhapsody engine. Upon a successful login, the latest configuration is copied from the Rhapsody engine to Rhapsody IDE. Rhapsody IDE enables the interface designer to create, view and modify configurations in a graphical drag-and-drop environment. Components are dragged into place from the toolbox of available processing actions (filters) and connection interfaces (communication points). Rhapsody IDE automatically generates formatted interface documentation describing the configuration. Users can choose between accessing Rhapsody’s help documentation online or via an offline version stored in Rhapsody IDE. Help documentation supports multiple languages where available. Interfaces in Rhapsody are primarily composed of five components:
-
-
- Communication points – an interface to an external system that can be configured to either accept or send messages, or both. Communication points implement a specific connectivity protocol such as TCP, FTP, web services or file-based.
- Filters – process and often modify messages in some specific way as they passes through the route. Each filter type performs a specific task (for example, validation and transformation) when processing a message. Filters (and conditional connectors) can have unit tests configured for direct analysis of the
- Filters – process and often modify messages in some specific way as they passes through the route. Each filter type performs a specific task (for example, validation and transformation) when processing a message. Filters (and conditional connectors) can have unit tests configured for direct analysis of the
- Filters – process and often modify messages in some specific way as they passes through the route. Each filter type performs a specific task (for example, validation and transformation) when processing a message. Filters (and conditional connectors) can have unit tests configured for direct analysis of the
- Connectors – conduits that deliver messages from one component to another. Conditional connectors can redirect messages based on the message structure or
- Routes – a combination of communication points, filters and connectors that define the ‘path’ taken by messages as they move through Rhapsody. Routes determine how messages will travel from Input to output communication points. A route has input communication points to receive messages and output communication points to which it delivers messages. Between these communication points, a route may contain any number of filters that can manipulate the data in the messages.
- Lockers enable Rhapsody administrators to compartmentalize Rhapsody’s configuration, whereby user access to configuration and messages can be controlled. Lockers provide fine-grained access controls to many components such as folders, communication points, routes, definitions and the processed
Rhapsody supports both real-time processing and batch processing. Users may also schedule communication points to operate only when required, for example on weekdays, weekends or only during business hours.
Built for healthcare
Rhapsody is a healthcare-focused integration engine used by public and private hospitals, health systems, Health Information Exchanges, vendors, public health departments and federal government organizations. The interoperability platform is represented globally with customers in 36 countries. It has support for all healthcare message formats and standards, including HL7 (v2 and v3), HL7® FHIR, CCDA, NCPDP, X12, IHE, DICOM, XML, and many more.
If required, custom protocols can be implemented using the Rhapsody Development Kit (RDK) to create custom components.
Communication Points
The following communication points are provided in a standard Rhapsody installation:
| COMMUNICATION POINT |
DESCRIPTION |
| ASTM TCP Client ASTM TCP Client |
Enable the sending and receiving of messages using ASTM 1381. |
| Amazon S3 |
Provides the ability to write content to S3 storage on Amazon Web Services. |
| Amazon SNS |
Provides connectivity to an Amazon Simple Notification Service (Amazon SNS), |
| Amazon SQS |
Provides connectivity to an Amazon Simple Queue Service (Amazon SQS). |
| Database |
Enables information to be read from, and written to, a database. |
| Directory |
Provides file-based connectivity (including batch file reading and writing). |
| Database Insertion |
Adds information into a database table, or updating existing rows in database table. It can be used in any situation where all the user wants to do is insert into or update one row in a database table for every message it receives - effectively fulfilling an archiving role. |
| Directory |
Provides file-based connectivity (including batch file reading and writing). |
| TCP Client TCP Server |
Provide TCP client-server capabilities. |
| Web Service Hosting |
Implements the communication for one or more methods of a web service. |
| Web Service Client |
Supports RPC and document-based web services. |
| Email Client |
Extracts and processes Information contained in the header of an email message, the body of an email message, or in an attachment. |
| COMMUNICATION POINT |
DESCRIPTION |
| Execute Command |
Enables a custom application or script to be selected for delivering messages. |
| (S)FTP Client |
Connects to an FTP or SFTP server and look for files from an input directory and/or to send messages to an output directory. It supports FTP, FTPS (FTP over SSL) and SFTP. |
| Dynamic Router |
Redirects messages dynamically between routes in a decoupled manner. |
| HTTP Client HTTP Server |
Enable Rhapsody to act as an HTTP client and HTTP server. |
| JavaScript REST Client |
Connects to remote REST servers using JavaScript to manage REST calls. |
| JavaScript TCP Client JavaScript TCP Server |
Enable the creation of a protocol for client-server communications using JavaScript. |
| JMS Client |
Sends and receives messages from a Java Message Service (JMS) Queue or Topic. |
| MSMQ Client |
Uses the Microsoft Message (MSMQ) API interface to communicate with a Microsoft® Message Queuing server. |
| Printer |
Enables the printing of plain text and PostScript (PS) documents. |
| Rhapsody Connector |
Provides reliable delivery of messages over an (optionally) secure connection to another Rhapsody connector. |
| Sink |
Used to discard messages. |
| SNA LU6.2 |
Enables Rhapsody to exchange messages with hardware compatible with IBM’s Systems Network Architecture. |
| Timer |
Used to trigger an event in Rhapsody. |
| Advanced Notification Communication Point |
Description |
| Watchlist Notifier |
Connects to watchlists to generate a routable message for events specified in the watchlists. |
Filters
The following filters are included with a standard installation of Rhapsody:
| STANDARD TOOLBOX |
DESCRIPTION |
| HL7 Acknowledgement Generation |
Generates acknowledgments for HL7 messages, using definitions from the built-in libraries or designed in the EDI Designer. |
| HL7 External Code Translation |
Translates HL7 coded fields from one coding system to another using an external database. |
| HL7 External Code Validation |
Verifies that HL7 fields contain valid coded values using an external database. |
| Batch / De-batch |
Batches messages into a single file, or separates a batched file into its component messages. |
| Character Encoding Translator |
Converts the contents of a message from one character encoding to another. |
| Content Population |
Inserts information into fields in a message. |
| Duplicate Message Detection |
Detects instances of duplicate messages. |
| EDI Message Validation |
Validates EDI messages for correctness. |
| Error Queue |
Sends messages to the Rhapsody’s Error Queue for manual processing. |
| Standard Toolbox |
Description |
| Error Message Redirector |
Enables tracked messages, which have met some error condition specified in a message tracking scheme, to be redirected for further processing rather than simply being discarded or sent to the Error Queue. |
| FHIR JSON - XML |
Converts bidirectional mapping between JSON and XML for FHIR messages. Supports Bundles and Resources, DSTU 1 and DSTU2 Ballot versions. |
| FreeMarker Mapper |
Is a template-based mapper used to transform an input message from one format to another, for example providing mapping between HL7 and XML formats. It features a versatile template editor. |
| HL7 Message Modifier |
Provides built-in functions for applying the most-common message transformations to HL7 v2.x messages. |
| Hold Queue |
Sends messages to the Rhapsody Hold Queue for manual processing. |
| JavaScript |
Executes user-written JavaScript code to process messages as they pass through the Rhapsody engine. |
| Intelligent Mapper |
Executes the mapping code generated by the Intelligent Mapper application. |
| Property Population |
Stores message properties as name value pairs that can be used for decision making during the routing and processing process. |
| RPG Decrypt and Verify RPG Encrypt and Sign |
Used to encrypt and sign, and decrypt and verify messages, providing OpenPGP-compliance. |
| Search and Replace |
Performs simple text substitution on a message. |
| Mapper |
Transforms messages from one message format into another message format, using mapping definitions created in the Map Designer. |
| S/MIME |
Transforms messages between MIME and Rhapsody message formats. |
| Save Snapshot Load Snapshot |
Simplify the splitting and collecting of messages in order to match downstream messages with a previous state. A snapshot of a message can be saved and then referenced (loaded) later in the processing pipeline. |
| DATABASE TOOLBOX |
DESCRIPTION |
| Database Lookup |
Retrieves information from JDBC accessible data sources and inserts the information into messages. |
| Database Message Extraction |
Replaces the body of a message with an XML message generated from a database query. |
| Generic Code Translation |
Enables simple lookups in a database table based on message fields to replace or populate other message fields. |
| DICOM TOOLBOX |
DESCRIPTION |
| DICOM JPEG Extractor* |
Extracts JPEG images from a DICOM message. |
| DICOM to XML / XML to DICOM* |
Transforms messages between XML and DICOM formats. |
* Supported on x86 operating systems only.
| EBXML TOOLBOX |
DESCRIPTION |
| ebXML |
Handles the creation and parsing of ebXML messages. |
| ebXML Acknowledgment |
Generates an acknowledgement for received messages parsed by the ebXML filter. |
| ebXML Message Status Service |
Implements the Message Status Service in co-ordination with the ebXML filter. |
| ebXML Ping Service |
Implements the Ping Service in co-ordination with the ebXML filter. |
| ebXML AutoReply |
Encompasses the response generating functionality of the ebXML Acknowledgement, ebXML Ping Service and ebXML Message Status filters. |
| HIPAA 4010 TOOLBOX |
DESCRIPTION |
| HIPAA 4010 De-identifier |
Replaces Personal Health Information (PHI) in the HIPAA 4010 message with anonymized data. |
| HIPAA 4010 Rebatcher |
Reassembles a batch of HIPAA 4010 messages that were previously split for processing. |
| HIPAA 4010 Segment Formatter |
Used to strip off or add carriage return and line feed characters at the ends of segments in a HIPAA message. |
| HIPAA 4010 Splitter |
Splits a HIPAA 4010 batch into individual messages for processing. |
| HIPAA 4010 Validation |
Validates against the HIPAA 4010 messaging standard. |
| UTILITY TOOLBOX |
DESCRIPTION |
| Asymmetric Cryptography |
Encrypts or decrypts messages using an asymmetric (public/private key) cryptography algorithm. |
| Base 64 Encoder-Decoder |
Encodes and decodes between binary data and Base64 encoded data. |
| Date Validation |
Validates dates within a message. |
| Execute Command |
Enables Rhapsody to call command line applications for processing messages. |
| HL7 Detect Character Encoding |
Detects the character encoding used in an incoming HL7 message. |
| HL7 Fill Empty Fields |
Populates empty fields in an HL7 message with the specified string or Rhapsody variable. |
| Zip / Unzip |
Compresses messages into a ZIP archive, or extracts messages from a ZIP archive. |
| X12 TOOLBOX |
DESCRIPTION |
| X12 Splitter |
Enables X12 messages to be split into multiple messages based on a configured message level. |
| X12 Rebatcher |
Enables split messages to be recombined into a single X12 batch message. |
| X12 5010 Validation |
Generates X12 acknowledgements with the option to output an HTML report. |
| XML TOOLBOX |
DESCRIPTION |
| Web Service Signing |
Uses the web services extensions framework to create digital signatures of parts of the XML (generally SOAP) message. |
| XML Encryption / Decryption |
Encrypts or decrypts XML messages or message parts. |
| XML Signing / Verifying |
Creates or verifies a digital signature for XML messages. |
| XML to PDF |
Transforms the XML document to an XSL:FO compliant PDF. |
| XML to RTF |
Transforms the XML document to an RTF document. |
| XML Validation |
Validates XML documents against an XML Schema Definition Language (XSD) schema. |
| XML TOOLBOX |
DESCRIPTION |
| XSLT Stylesheet |
Applies an XSLT stylesheet transformation to an XML document. |
Toolkits
Additional communication points and filters are available as part of optional toolkits:
| TOOLKIT |
DESCRIPTION |
| SAP Toolkit |
A licensed add-on module that enables communication between Rhapsody and a SAP server by executing Remote Function Calls (RFCs). The toolkit comprises both a filter and a communication point. |
| IHE Toolkit |
A licensed add-on module for Rhapsody, which is designed to simplify the process of implementing a system that complies with IHE Integration Profiles. |
Connectors
Rhapsody uses connectors to determine the direction and flow of messages through the route: from the input communication point, through configured filters to the output communication point. There are three types of connectors:
-
-
- Standard – passes messages from one Rhapsody component to another in a route. It does not restrict or change the messages passing along
- Conditional – allows for selective routing of messages based on their structure and/or
- JavaScript – uses a JavaScript code to make routing decisions for messages. It offers more flexibility than the regular expression Conditional connector, but requires knowledge of JavaScript to
Message Definitions
A message definition defines the structure of the messages being processed. Definitions enable Rhapsody to read and manipulate message data. XML messages typically use a W3C XML Schema (*.xsd), whereas Electronic Data Interchange (EDI) messages use a Rhapsody EDI message definition (*.s3d).
Managed Lookup Tables
Rhapsody’s managed lookup tables are configurable multi-column records embedded in the Rhapsody engine and modified using the Rhapsody IDE or the Management Console. The lookup tables allow the location of specific column values by matching one or more columns of data and returning the value in a named column. A common use for lookup tables is the mapping of coded elements, such as laboratory test result codes. For example, a lookup may return a value of “Tetanus” from the
description column, if provided with the values “76902006” and “SNOMED” for the
CodeValue and
CodeSystem columns. Lookup tables can be stored in a Rhapsody Local Configuration (RLC) file for easy migration between environments.
Web Service Standards
Rhapsody provides the ability to host web services as well as use external web services. The implementation follows the web services interoperability organization standards for WS-I basic profile and WS-I basic security profile. Rhapsody includes support for the following standards:
» WSDL 1
» SOAP 1.1, 2
» WS-Addressing
» WS-Security
» WS-Policy
Security
Access to configure and monitor the Rhapsody Integration Engine is granted via a secure login and password. Each user must also be assigned to one or multiple Access Groups, which in turn determine the functionality they can access. Lockers provide additional access control by enabling the Rhapsody configuration to be compartmentalized. Access groups are designed so an administrator can provide access based on user role (for example, Administrator, Developer, Monitor, or Dashboard). Within each access group, access rights can be assigned to different actions and lockers. Users and Groups can be locally defined or inherited from LDAP directories for centralized user management. Access levels for each Engine are managed separately. This enables administrators to assign different levels of user access to a Development server and a Production system, for example.
Intelligent Mapper
The Intelligent Mapper is a tool that determines the transformation (mapping) rules between input messages and output messages. The tool implements mapping through mapping projects which are stored on the Engine. The mapping projects are used to generate JavaScript mapping code from mapping rules. The mapping code is used by the Intelligent Mapper filter to perform the actual mapping in a Rhapsody route. The overall mapping process consists of matching input and output messages using message identifiers to create matched message pairs, and using the matched message pairs to analyze and generate the mapping rules that define the mapping across message sets. The user can select which mapping rules they would like to include as part of the mapping code. They can also create custom rules, if required. When the user has completed the analysis and reviewed all mapping rules, the Intelligent Mapper can be used to generate the mapping code. When the code has been generated, it can be tested and edited to suit the user’s requirements. The Intelligent Mapper filter executes mapping code associated with a selected mapping project in a route. Intelligent Mapper filters have access to all mapping projects within a specific locker, thereby allowing mapping code to be re-used in multiple routes.
Test Manager
The Test Manager provides a centralized hierarchical view of all the filter and conditional connector tests in your configuration, and enables you to manage and run tests across components. Users can generate a PDF report with a testing summary for the entire configuration.
Management Console
The Management Console is a web-based application that can be accessed through Internet Explorer, Microsoft Edge, Firefox, Chrome or Safari browsers. It displays information on the system status and state of message processing in the Engine. The Management Console highlights exceptional circumstances such as system connections that are not operating, interfaces that are not keeping up with the required throughput. It also allows access to critical administration tasks and processing logs. The Management Console allows access to copies of all messages processed by the Engine. Messages are stored in the Rhapsody archive for a configurable period of time (referred to as the archive period) and during that time they can be edited, resent and reprocessed as required. Messages can be viewed at all stages of processing and the complete path of a message is displayed graphically.
System Overview
The high-level system status overview.
Component Status
The status of individual routes, communication points and web services:
-
-
- Status (Running, Stopped, ).
- Message throughput/trends.
- Activity stream of notifications (Warnings, Alarms, Escalations).
- Real-time and historical view
- Define notifications thresholds for a range of
- Set recipients of
Watchlists
Watchlists are user-defined groups of routes, communication points and web services:
» Create watchlists, their associated components, and subscribed
» Schedules for watchlist user
Error and Hold Queues
The number and content of messages currently on the Error and Hold Queues.
Message Searches
» Input Search – locate messages received on an input communication
» Output Search – locate messages based on destination, time and acknowledgment status
» Full Text Search – locate messages based on source location, destination, time and text
» Search Options – searches can be refined by applying filters on the returned
Message View
HL7 messages within the Management Console can be presented to the user in a readable format providing the field names and values in a tree structure. Messages are also displayed in a flatwire view. The helps the user find the information find critical information quickly and easily.
Rhapsody Engine Statistics
» System Statistics – record a Rhapsody engine’s message throughput and memory» Latency Statistics – record the time taken to process messages passing through a Rhapsody engine and the time taken for external systems to respond to messages from» Performance Statistics – record the length of time messages spend in individual routes and» Message Breakdown Reports – reports generated based on content extracted from messages (for example,
facility identifier).
Server Status
» View the Rhapsody and Audit log
» Generate and view threads to help identify problems occurring in the
» Gather and consolidate diagnostic information (for example, logs, configuration, system information) and generate a single ZIP archive
Server Settings
» Manage the backup schedule for the Rhapsody message
» Remove old data from the Rhapsody message store.
» View or set the current user’s Management Console settings and
» Set the display parameters used when viewing statistical data.
» Configure Introduction Page and Information Banner messages.
» Define notifications generation for system-wide events (for example, high CPU usage).
» Set default thresholds, recipients and scheduling of communication point and route
Engine Uptime
The Engine Uptime report enables users to view engine uptimes and total message counts between user defined time frames.
Feedback
Users can provide feedback to Product Development through a user feedback module, available in every page within the Management Console.
Notifications
A multi-tier notification system enables administrators to configure various thresholds on a global and an individual component level to trigger warnings and alarms. If an alarm has not been dealt with in a specified time, the issue can be escalated to a specified individual or group. Watchlists allow the grouping of components into logical areas that can be monitored individually or according to shift rosters. The rosters allow notifications to be delivered based on the time of day and the user’s selected delivery mechanism (SMS, pager, or email).
Rhapsody Mobile
Rhapsody Mobile is an iOS and Android smartphone application that provides a subset of monitoring capability from the Management Console. Rhapsody Mobile provides administrators with a real- time view of the health of an Engine, empowering them to stay abreast of Rhapsody issues when they are on the move or do not have access to a workstation. Rhapsody Mobile complements the Management Console, Rhapsody Dashboard and email/SMS notifications.
Notifications Metrics
Rhapsody Mobile provides users with notifications metrics for diagnostic purposes. The application displays message counts and details of the Error Queue as well as all current Escalation, Alarm and Warning notifications for a Rhapsody engine. These notifications can be marked as read, suspended and dismissed as required.
Proactive Notifications
Users can receive e-mail notifications, which can be opened within the mobile application as they occur, providing visibility of any unintended events that may need attention.
Basic Component Interaction
Users can start, stop and restart Rhapsody components (communication points, web services, and routes) contained within notifications.
Rhapsody Dashboard
Rhapsody Dashboard is a standalone application designed to give users an at-a- glance picture of health for all their Rhapsody environments, enabling proactive maintenance overall. Rhapsody Dashboard can be accessed from a web browser on a range of devices. Rhapsody Dashboard displays the essential status indicators for multiple Rhapsody engines. The key status indicators include:
» CPU
» Disk space
» Memory utilization.
» Notifications – Error Queue count, components stopped in error, and components in retrying
Each Rhapsody engine instance is represented by an engine card. Users can apply custom filters to group engine cards into logical groups, such as Development, Test, or Production. For each engine card, users can expand the views to examine the engine details by clicking on relevant icons. The notifications provide a link to the Management Console to facilitate further diagnosis and remediation.
Rhapsody Electronic Data Interchange Tools
EDI Message Designer
The EDI Message Designer is used to create the definition of the EDI messages being parsed or created in one or more routes. The message definition defines the structure and separators of the messaging system and is the information that the parsing engines need to parse and create valid messages. The definition also contains information on how to validate incoming messages. The EDI Message Designer includes pre-built libraries for a number of messaging standards, including HL7, X12, HIPAA and EDIFACT, NCPDP and UB92. Messages from these libraries can be imported into the EDI Designer and modified to meet local requirements. The EDI designer also allows the creation of custom message formats, such as CSV files or fixed width formats. The message definitions are then used in the Engine for parsing, validating, mapping and modifying messages as required.
EDI Explorer
The EDI Explorer enables the visual creation and testing of messages. Explorer requires a message definition, created in the EDI Message Designer and follows the structure defined in that definition. EDI Explorer allows these messages to be placed in a text file, or to be sent over TCP to simulate an external system.
Map Designer
The Map Designer allows message structures to be mapped to alternate message structures. The structures can be EDI messages, or XML documents (such as CDA documents) with the Map Designer importing EDI Designer definitions or W3C XML schema definitions (*.xsd files). Mappings are then constructed by dragging components from one message structure to the other message structure to create the mapping code. The mapping code can then be modified for complex manipulations. The Map Designer includes a debugging environment that allows a user to step through the mapping to debug any problems using sample messages. The Map Designer also includes auto-mapping functionality for mappings where the structures of the input and output messages are similar, for example, HL7 2.3 to HL7 2.xml messages.
Supported Systems and Software
Rhapsody Engine
-
-
- AIX® 6.x, 7.x (POWER)
- HP-UX 11+ (Itanium)
- Red Hat Linux 6, 7 (x86 and x64)
- CentOS 6, 7 (x86 and x64)
- Ubuntu 12.04 LTS, 14.04 LTS
- Solaris™ 10, 11 (SPARC)
- Windows Server 2012, 2012 R2 (x64)
- Windows Server 2008 R2 SP1 (x86 and x64)
Rhapsody IDE
»
Windows® Server 2016, 2012, 2012 R2 (x64)
»
Windows® Server 2008 R2 SP1 (x86 and x64)
»
Windows® 7 SP1, 8.1, 10
» Microsoft® .NET Framework 4.6.2 (the Rhapsody installation wizard installs the .NET Framework if required)
Management Console
» Internet Explorer 11® or later
» Microsoft Edge
» Mozilla® Firefox® ESR
» Google Chrome™
» Safari®
Rhapsody Mobile
» iOS 7 and later
» Android 2.3.3-2.3.7, 4.0.x, 4.1-4.3.1, 4.4+
Rhapsody Dashboard
Rhapsody Dashboard is supported on following operating systems:
» AIX® 6.x, 7.x (POWER)
» HP-UX 11+ (Itanium)
» Red Hat Linux 6, 7 (x86 and x64)
» CentOS 6, 7 (x86 and x64)
» Solaris™ 10, 11 (SPARC)
»
Windows® Server 2012, 2012 R2 (x64)
»
Windows® Server 2008, 2008 R2 (x86 and x64)
Rhapsody Dashboard can be accessed through the following browsers:
» Internet Explorer 9® or later
» Microsoft Edge
» Mozilla® Firefox®
» Google Chrome™
» Safari®
Services and Support
Allegiance Healthcare Solutions has a reputation for excellence in providing service and support to its customers. These offerings include technical and project consulting, training, online resources, 24-hour phone and online support, and a growing catalogue of product and implementation documentation.
Professional Services
The AHS Professional Service Group (PSG) provides services related to the Rhapsody Integration Engine. PSG have a presence in North America and Europe. PSG provide expertise in Rhapsody implementation, interface design and development, troubleshooting, and interface optimization. PSG can also assist our clients to migrate from other vendors’ integration engines to Rhapsody.
Updates
All customers with current service contracts receive software and documentation updates of major releases.
Training
A wide range of educational services can be provided at the client’s site or through the online training program.
Online Forums
Users can engage with other members of the Rhapsody community.
