Decisions has a full custom reference model allows messages from different versions to share the same logic and handling. Data is represented in a way that is easy to consume within the tool, and understood by business users. You can also see raw messages and change them before they are processed. Communication protocols and interface definitions are easy to setup and configure.
Like dedicated interface engines, the Decisions Platform has data transformation and management. However, with Decisions + HL7/FHIR you get much more:
Message processing is very flexible. From prebuilt handling steps like split, merge, validate, etc, additionally the flow engine can handle this functionality very flexibly. Data can be changed, manipulated, etc. The flow and rule engine have capabilities of handling data in a very flexible manner. There are hundreds of data manipulation steps as well as capability of integration into external systems for validations, lookups, and other data centric operations.
Going well beyond processing HL7 into database tables, HL7 support in the Decisions Platform enables full integration into services, databases, other data types or systems. Data can be cleaned up, routed, processed and stored all without any programming.
Graphically map data from your system into outbound message systems. These messages can be triggered in a number of ways:
Placing the Decisions engine between systems allows for content based routing, placing business rules to intercept conditions, involve users/tasking and send on modified, cleaned or secondary messages to other systems. As everyone knows HL7 data is often dirty and different systems expect very specific data content and constraints. Using Decisions as an interception engine to process this data and route it, the integration between systems can be much cleaner.
