Our Orion Specialists have supported the product for 9+ years.

Our Orion consulting group brings 24+ years of experience on the product line, all the way through current versions.  Let us help you with your integration tasks, big and small.

How We Can Help:

  • Planning
  • Design
  • Solution Evaluation
  • Vendor Selection
  • Architecture – Hardware and Software
  • Project plan
  • Implementation
  • Testing / QA
  • Production release and maintenance

Key Components we’ll Develop for you in Rhapsody

Communication Points

A communication point is an interface to an external system. It is the mechanism by which Rhapsody will send and receive information to and from the external systems. Messages arrive at an Input communication point, are processed by filters and conditional connectors on the route and passed to one or more Output communication points. From there, the messages are sent to the receiving application(s). The method of communication is defined by the type of communication point used.

  • ASTM TCP Client Communication Point
  • ASTM TCP Server Communication Point
  • Clinicom Client Communication Point
  • Clinicom Server Communication Point
  • Database Communication Point
  • Database Insertion Communication Point
  • Directory Communication Point
  • Email Client Communication Point
  • Error Message Redirector Communication Point
  • Execute Command Communication Point
  • FTP Client Communication Point
  • HTTP Client Communication Point
  • HTTP Server Communication Point
  • HylaFAX Client Communication Point
  • JavaScript TCP Client Communication Point
  • JavaScript TCP Server Communication Point
  • JMS Communication Point
  • Kermit over Serial (RS/232) Communication Point
  • MSMQ Communication Point
  • NHS DTS Client Communication Point
  • Printer Communication Point
  • Rhapsody Connector Communication Point
  • RPC Web Service Client Communication Point
  • Scheme Notifier Communication Point
  • SFTP Client Communication Point
  • Sink Communication Point
  • SMS Batch Communication Point
  • SMS Invision Communication Point
  • TCP Client Communication Point
  • TCP Server Communication Point
  • Timer Communication Point
  • TN3270 Communication Point
  • Waiting and Idle Count Notifier Communication Point
  • Web Service Client Communication Point
  • Web Service Hosting Communication Point
  • Wrapped Serial (RS/232) Communication Point
  • X/Y Modem over Serial (RS232) Communication Point
  • Zmodem Serial (RS-232) Communication Point
  • Deprecated Communication Points


Filters process and often modify messages in some specific way as they pass through a route. Rhapsody has a number of predefined filters for common tasks such as mapping from one message format to another, code validation and database lookups.

  • Asymmetric Cryptography Filter
  • Base64 Encoding Filter
  • Batch / Debatch Filter
  • Character Encoding Translator Filter
  • Code Translation and Validation Filters
  • Content Population Filter
  • Database LookUp Filter
  • Database Message Extraction Filter
  • Date Validation Filter
  • DICOM JPEG Extraction Filter
  • DICOM to XML / XML to DICOM Filter
  • Duplicate Message Detection Filter
  • ebXML Filters
  • EDI Message Validation Filter
  • Error Queue Filter
  • Execute Process Filter
  • Generic Code Translation Filter
  • HIPAA 4010 Filters
  • HL7 Acknowledgement Generation Filter
  • HL7 Detect Character Encoding Filter
  • HL7 Fill Empty Fields Filter
  • Hold Queue Filter
  • JavaScript Filter
  • Mapper Filter
  • No-operation Filter
  • Property Population Filter
  • Schematron Filter
  • Search and Replace Filter
  • Symmetric Cryptography Filter
  • X12 Filters
  • XML Filters
  • Zip/Unzip Filter


Message Definitions

The mapper needs definitions for the two objects in the Input and output trees.  The Mapper can map both XML and EDI messages. An XML Schema or DTD may be used for the XML Definitions but for EDI messages the mapper needs either a Symphonia / Rhapsody PCF file or a Composer DLL.  Users of Symphonia / Rhapsody will be familiar with Composer and the Direct ActiveX objects that it produces. Composer is Symphonia / Rhapsody’s Message definition GUI. It is a tool that allows the customisation of message definitions. There is a Composer for EDI message definitions and a Composer for XML document definitions; both of these are included with the Mapper.  A PCF file is a Parser Control File. It is generated by Composer for use in the Symphonia / Rhapsody Parsing Engine. It contains information about the structure of a set of EDI messages. Composer can also generate an ActiveX DLL for a message definition. If you have generated a DLL from Composer, the mapper will be able to use it without you having to change anything.  If you need to map messages from a commonly used EDI standard such as X12, EDIFACT or HL7, it is likely that the messages you are using will be included in the Composer Library. Use the Composer wizard to import these messages and generate a PCF.

Reach out for Instant Contact

If you need information fast, reach out to us for an immediate response. Our team of professionals is ready to discuss your challenges, requirements and questions. Please submit your contact information you’ll hear from us within a of couple hours.