Connected Health / iDAAS (Intelligent Data As A Service) - Common Questions and Answers

Connected Health / iDAAS (Intelligent Data as A Service) - Common Questions and Answers


There is so much material to digest and so many areas where people have questions. So we wanted to try and put together an area for questions and answers.

Connected Health / iDAAS (Intelligent Data as A Service) - Platform Questions

Question Answer
Is iDAAS a Red Hat product offering No. We describe iDAAS as many things like reference architecture, design pattern, accelerator or platform. iDAAS is built atop Red Hat's technologies and is intended to be a value add. Because of the way iDAAS is designed, implemented, and maintained existing training and support agreements can be leveraged.
Why are there so many "components" As we discussed in the main introduction when we started we want to focus on extensibility. While we could implement everything in ONE single application that would not be effective or help us showcase the tremendous flexbility this design offers for processing data at scale.
Does this component architecture container based the iDAAS platform is cloud native built from the ground up. However, MLLP (HL7) itself at the protocol level because it is client-server socket based is not cloud native enabled. Typical implementation is to implement iDAAS-Connect-HL7 on a small server or VM. We have seen a VM with 4vpus and 16GB of RAM process tens of throusands of messages sustained over many hours.

Connected Health / iDAAS (Intelligent Data as A Service) - HL7 Integrattion Questions


Question Answer
What vendors does this platform component support? This iDAAS Connect accelerator does not have any specific vendor requirements or limitations. It has been tested with Cerner, Epic, Meditech and several other EHR/EMR platforms.
What messages does this platform component support? 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.
Does this component architecture container based the iDAAS platform is cloud native built from the ground up. However, MLLP (HL7) itself at the protocol level because it is client-server socket based is not cloud native enabled. Typical implementation is to implement iDAAS-Connect-HL7 on a small server or VM. We have seen a VM with 4vpus and 16GB of RAM process tens of throusands of messages sustained over many hours.

Connected Health / iDAAS (Intelligent Data as A Service) - FHIR Questions


Question Answer
I was unaware Red Hat had a FHIR Server Red Hat does not have its own FHIR server. When we wanted to focus on assisting organizations meet and exceed the CMS Interoperability Final Rule we did not want to align and continue forcing vendor lock in. Our iDAAS Connect FHIR accelerator has been, and will continue to work with multiple FHIR servers. To date It has been tested and works with several FHIR servers: HAPI JPA Server, Microsoft Azure FHIR Server and IBM FHIR Server. In order to assist in implementation these settings are all configurable so you can also change as your business needs evolve. In addition to this support it natively has enabled support for over 80+ FHIR resources that DO NOT need a FHIR server for processing. Apart from handling the needed specific FHIR resource connectivity it also has a detailed auditing platform enabled that tracks ALL data sent to the platform and any responses the platform receives.
FHIR Resource processing This iDAAS Connect accelerator specifically and ONLY supports ALL FHIR resources. From an integration perspective it enables processing of over 80+ 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. As mentioned above te platform has auditing enabled for any data interactions it is involved with.