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.
|Demo iDaaS Connect FHIR||iDaaS Connect FHIR Platform||This repository is specifically designed to test a subset of FHIR resources.|
|Demo iDaaS Connect HL7||iDaaS Connect HL7 Platform||This repository is specifically designed to test a subset of HL7 capabilities.|
|Demo iDaaS Connect Third Party||iDaaS Connect Third Party Platform||This repository is specifically designed to test a subset of iDaaS Third Party components and capabilities.|
|Demo iDaaS DREAM||iDaaS DREAM Platform||This repository is specifically designed to test a subset of iDaaS DREAM components and capabilities. This also is used to help showcase iDaaS Event Builder delivered capabilities.|
|Demo iDaaS Connect BlueButton||iDaaS Connect Blue Button||This component is specifically designed to show Blue Button capabilities.|
|Demo iDaaS Connect EDI||iDaaS Connect EDI||This component is specifically designed to show EDI capabilities.|
|Demo iDaaS Route Data Distribution||iDaaS Route Data Distribution||This component is specifically designed to show data routing capabilities.|
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 Connect accelerator is specifically implemented to help keep the iDaaS Connect (HL7 and FHIR) accelerators focus solely on connectivity, simplified initial data processing needs and auditing. It is also capable and intended to be used by the iDaaS Connect Third Party accelerator as well. It purpose is to route and move data, it does this by implementing an enterprise integration pattern named HCDD-EIP (Healthcare Data Distribution and Enterprise Integration Pattern). This accelerator apart from handling the needed specific connectivity with detailed routing logic built in and complete auditing integrated.|
|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 Data Hub||iDaaS Data Hub 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 Hub 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.|
We are also continuing to work on new and innovative components to help enable "Data as the asset" building efforts.
|Testing - Build Synthetic (Fictitious) Data||Data Synthesis||This component is specifically designed to enable implementors to quickly build fictitious data for testing. It has over 30B data attributes including names, address, phone numbers, zip codes, company names, drivers licenses, social security numbers, credit cards, bank routing numbers, UPC product codes and much more. All of the data is contained with a MySQL8 database which the dump for it can be easily downloaded and imported. There are also a few other projects as well that are intended (over time) to enable the community to develop and deliver coding capabilities from the extensive data tier. The project that has code artifacts for generating data and APis is located here. There could be future efforts possibly to add a project based on .Net Core.|