Health Data Connector – Digital health interoperability platform

The Health Data Connector (HDC) is an integration middleware application that enables interoperability across disparate data sources as a no-code application. A consistent approach to data retrieval, receipt, parsing, and transmission allows HDC clients to separate integration from business services, to standardize how the services communicate, improve integration monitoring capabilities, and reduce the complexity and cost of data interoperability.

The HDC is a web application that enables no-code configuration of FHIR and other RESTful APIs, HL7v2 Message listeners and data transmission, SMART on FHIR workflow management, and other integrations between our clients and their partners. The application can be deployed as a standalone Virtual Machine or within a Kubernetes cluster. HDC uses EC2 Instances, a S3 bucket and EKS.

Nordic provides additional capabilities layered on top of our integration services to perform high-value tasks including:

1. Workflow-based execution simplifies configuration via reusable building blocks and standardizes how your application services interact with the software
2. Data parsing and payload generation mechanisms enable creation of outbound data feeds using the results from API calls and inbound payloads
3. Process branching allows multiple concurrent processes triggered through a single event and can add significant value for long-running processes such as large API payload retrieval (using paging), bulk FHIR, and HL7 message acknowledgement
4. Rules-based processing allows for conditional process and workflow step execution and adds considerable flexibility at runtime to manage the unknown
5. Single-Sign On management with your identity provider within a SMART on FHIR launch process flow

Features:

• The HDC manages authorization with the EHR so that the process is entirely opaque to your software. Instead of worrying about authentication, just complete a field-by-field configuration to get started
• FHIR API connectivity, HL7v2 interface inbound and outbound connections, and SMART on FHIR workflow connectivity are setup and maintained via a no-code web portal
• SMART on FHIR workflows allow you to identify your own web endpoint(s) for redirect after the completion of the SMART handshake, and to login (SSO) the user into your own identity services as part of that handshake.
• Additional no-code configuration allows you to fetch FHIR data at the time of redirect within a SMART on FHIR launch. This enables you to hydrate your web app with healthcare data without the typical resource retrieval lag.
• Set rules logic within the SMART launch process such as identifying a provider type, logging the provider into their system (perform SSO), or reading and analyzing a FHIR resource, and use this logic to redirect the end user to an appropriate endpoint