Connected Health / iDAAS (Intelligent Data As A Service) Technologies

Technologies

Here are the technologies that drive our ability to continue to extend the capabilities we continue to deliver:


Capability Capability Description
Integration Ties back to Red Hat’s Fuse and its upstream vibrant Apache Camel community. This technology is backed by one of the most active communities and continues to grow and expand this technology for well over a decade. As part of its commitment there are thousands of implementations of all sizes, types and scale levels in numerous industries with some of them growing to support 1 billion daily transactions. As part of its growth are the hundred plus connectors that it natively supports, this will be very beneficial as connectivity will continue to be extended to more and more platforms.
Business Rules, Workflow This capability is supported by Decision Manager and the upstream Drools community. This technology is very largely adopted and implemented throughout the community. Drools has a very large footprint in organizations all over the world delivering expert based solutions and capabilities.
Complex Event Processing This capability is supported by Process Automation Manager and the upstream Drools community. The specific technology within the Drools community is called Drools Fusion. This technology is very largely adopted and implemented throughout the community. Drools has a very large footprint in organizations all over the world delivering expert based solutions and capabilities.
Data Streaming A key effort for us is enabling and building a high end data streaming and distribution platform. This capability is being supported by AMQ-Streams and the upstream Kafka community. We are also looking at future implementations with other distributed queuing technologies. As a side note, within the codebase there is a codebase built atop Apache-MQ; however, we maintain the code ONLY for resources that would rather leverage that technology.
APIs For APIs we have two implementations: APIs for the iDAAS design pattern and APIs to demonstrate end to end FHIR capabilities. For all API management we have leveraged 3Scale.
Data We currently are moving to support DDLs for SQL Server, Maria DB (MySQL) and Postgres. This is because there is wide adoption of these within healthcare. The first few implementations with be SQL Server DDL centric as well finalize data model validation. We also intend to expand towards NoSQL standards quickly as we continue to implement new features. Connected Health/iDAAS overall objective is to ensure we help define data as an asset.
Hybrid-Cloud When and where possible this reference aarchitecture/design pattern is completely designed to be cloud native. The ONLY exception is when we have to deal with specific industry needs that cannot be done with a cloud native manner. In healthcare this refers specifically to HL7 v2 messaging. The reason is this form of messaging is legacy based on the client-server socket paradigm and is meant to be long running. However, ALL any FHIR components are cloud native by design. For our container capabilities we focused around the industry leading Openshift and all the supporting OpenShift technologies.