Ensemble (Legacy)

The support was responsive and helpful. The documentation and knowledge articles were really helpful. APIs were easy to integrate.

Easy to apply changes

Robust integration Engine Ententsive connectivity options Monitoring and analytics

The initial onboarding took us some time, once we were comfortable with the usage, the daily operational overhead reduced a lot

Not easy to do a group of changes to be applied at same time for only doing parts that were changed. Have to define a schema for the Service as it should just receive the data matter what it is like and save the message saved. When configuring being web based makes it more difficult to be able to work like a real program. The basics for monitoring and stopping and starting of the interfaces are fine for web based but not for doing the configuration as it is very cumbersome and too many customs plugins would be needed to make it have a good look and feel of a good program. Cannot easily resend from a file if you have archived file based messages because the database gets too big when storing the data. Searching for messages in the database often hangs up and times out and have only 30 days stored. If all the messages were file based, this would not happen. Support often has to contact or consult with others to resolve or answer the non basic issues. Not easy to customize if a custom reply message needs to be sent. Would need to create a custom Service when it should be just a configuration items within the standard TCP/IP HL7 service. Viewing the productions does not look like there is an issue if not in alert status where will not show red if alert is to alert when 30 min have passed without being able to connect. To bounce a connection, if one of the connection settings I think it is the reconnect retry but not sure if that is the one but if set to 60 seconds, then the connection will not be able to be cycled quickly as could take up to 60 seconds to cycle/bounce. Resending messages should be allowed from service and go thru the routing, DTLs necessary for one specific Operation and not to all that the message originally routed to.

Need to improve the user interface The cost must be reduced.