iDaaS is a series of accelerators, because of this component based design, building with it
or atop it is straight forward, repeatable and reusable. Within each iDaaS
component there is an implementation/running specific set of instructions.
Each component contains a link to the public Git Hub code repositories!!!
Demo Based Repositories: Platform Components
These are very specific repositories meant to showcase the capability with a limited set of features. In January 2021 we focused on consolidating almost thirty repositories to less than ten. We did this to ensure we simplified the development and implementation experience.
|Demo-iDaaS||iDaaS Demos||This repository is specifically designed to to maintain all the iDaaS platform demos. This repository contains demos for BlueButton, EDI, DREAM, FHIR, HL7, Route Data Distribution, and Third Party.|
|iDaaS Connect||iDaaS Connect||This repository is specifically designed to to maintain all the iDaaS Connect components. This repository contains iDaaS Connect components for Audit and Compliance, BlueButton, EDI, FHIR, HL7,, and Third Party.|
|iDaaS Route||iDaaS Route - Data Distribution||This repository is specifically designed to test a subset of iDaaS Route components and capabilities.|
|iDaaS DREAM||iDaaS DREAM Platform||This repository is specifically designed for iDaaS DREAM components and capabilities. Within this repository the is also the iDaaS Event Builder parsing, builder and generator code base.|
|iDaaS KIC||iDaaS KIC (Knowledge, Insight and Conformance)||This repository is specifically designed to specifically support all needed components for iDaaS KIC (Knowledge, Insight and Conformance). This specific capability is intended to enable auditing and reconciliation of anything the iDaaS platform is engaged in leveraging.|
Implementation Based Repositories: Platform Components
These are the full specific repositories with all features enabled.
|Receiving||iDaaS Connect Clinical - HL7||This iDaaS Connect accelerator specifically and ONLY supports the clinical integration standards of HL7. From an integration connectivity and standards perspective it has HL7 MLLP Servers that support the following types from any vendor and any specific message version from 2.1 to 2.8: ADT (Admissions), ORM (Orders), ORU (Results), SCH (Schedules), PHA (Pharmacy), MFN (Master File Notifications), MDM (Medical Document Management) and VXU (Vaccinations). This accelerator apart from handling the needed specific connectivity also does a minimal initial routing of data and has complete auditing integrated.|
|Receiving||iDaaS Connect - FHIR||This iDaaS Connect accelerator specifically and ONLY supports ALL FHIR resources. From an integration perspective it enables processing of over 75+ specific FHIR resources that span base, clinical, financial (all), specialized (all but testing). Another benefit of this platform is that you DO NOT require a FHIR server for this be leveraged. However, It has been tested to work with several FHIR servers: HAPI JPA Server, Microsoft Azure FHIR Server and IBM FHIR Server. This accelerator apart from handling the needed specific connectivity also does a minimal initial routing of data and has complete auditing integrated.|
|Receiving||iDaaS Connect Blue Button||This iDaaS Connect accelerator specifically and ONLY supports the critical FHIR need of processing data from BlueButton based on a series of data attributes that are passed to it.|
|Receiving||iDaaS Connect - Third Party||This iDaaS Connect accelerator is specifically designed to receive data from several dozens connectors. The connectors include JDBC (any jdbc compliant data source with a jar), Kafka, FTP/sFTP and sFTP, AS400, HTTP(s), REST and many more. Since this accelerator is built atop the upstream of Apache Camel this accelerator can leverage any supported components. This accelerator apart from handling the needed specific connectivity also does a minimal initial routing of data and has complete auditing integrated.|
|Routing||iDaaS Connect Data Distribution||This iDaaS Route component is specifically implemented to help enable a decoupled enterprise integration pattern. The focus of this component is solely on enabling data to be distributed with any implementation needs or requirements. The initial design pattern is termed the HCDD (healthcare data distribution) enterprise integration pattern.|
|Run (Transform and Re-Shape Data)||Event Builder||This component is what enables Red Hat, partners, SIs and developers to develop, extend or enhance the platform's ability to process data into any type of needed custom format for any type of needed processing. iDaaS Event Builder is designed to call out and invoke needed events and can be customized based on business needs very quickly. The only thing past cloning the source code is setting up the appropriate way to include iDaaS Event Builder jar files so that it can be included. If you do not wish to leverage the existing code, enhance or extend it developers are able to add their own custom code for processing and object building.|
|Run||iDaaS DREAM (Data Runtime Enterprise Automated Mgmt)||DREAM's design intent is to enable Red Hat, partners, SIs and developers to implement iDaaS and/or other capabilities internal or external to iDaaS in a dynamic manner without the need for stopping the platform and needing to restart it to work with data while adding new features.|
|Research and Resolve||iDaaS KIC (Knowledge, Insight and Compliance)||iDaaS KIC is where audit and other related data for the platform is stored. Like the rest of iDaaS it is intended to be extensible. iDaaS Data KIC is a platform to enable processing of data into the various components and data models included. The key things Data Hub is meant to ensure resources have data driven insights from ANY activity the iDaaS platform will do. A key thing to note in the data model and events the system focuses on is a way to associate one organization to many healthcare entities and to many applications and within each application any components wished to be defined. This is ALL up to the implementation. Because of this data enablement iDaaS focuses on enabling a detailed eventing model to iDaaS Data Hub for any activities the system does, this specifically is done through a transaction event which has a rich set of data attributes to enable detailed insight. iDaas KIC Integration specifically deals with the processing of all iDaaS Auditing events for scale and performance into both JSON documents and also a RDBMS table set.|
We are also continuing to work on new and innovative components to help enable "Data as the asset" building efforts.