Pre-defined recipes for common use cases
OpenHIM platform comes bundled with a set of generic packages that can be deployed and configured to support a number of different use cases. To help users of OpenHIM Platform get started with something they can make use of immediately, a number of default OpenHIM Platform recipes are provided. These help you get started with everything you need setup and configured for a particular use case.
These recipes combine and configure multiple packages together so that a functional HIE is stood up that is pre-configured to support a particular use case.
We currently support the following default recipes:
Central Data Repository with Data Warehouse
A FHIR-based Shared Health record linked to an MPI for linking and matching patient demographics and a default reporting pipeline to transform and visualise FHIR data.
Central Data Repository
A FHIR-based Shared Health record linked to an MPI for linking and matching patient demographics. No reporting is include but all FHIR data is pushed to Kafka for external system to use.
Master Patient Index
A master patient index setup using JeMPI. it also includes OpenHIM as the API gateway providing security, a mapping mediator to allow FHIR-based communication with JeMPI and Keycloak to support user management.
Note: This recipe is in a pre-release alpha stage. It's usable but do so at your own risk.
This recipe sets up an HIE that deploys JeMPI behind the OpenHIM with a mapping mediator configured to allow for FHIR-based communication with JeMPI. It also deploys Keycloak for user management and authentication.
To launch this package in dev mode copy and paste this into your terminal in a new folder (ensure you have the instant CLI installed):
Note: This recipe is in a pre-release alpha stage. It's usable but do so at your own risk.
This recipe sets up an HIE that does the following:
Accept FHIR bundles submitted securely through an IOL (OpenHIM)
Stores Clinical FHIR data to a FHIR store (HAPI FHIR)
Stores Patient Demographic data to an MPI (JeMPI)
Pushes FHIR resources to Kafka for other external systems to use
To launch this package in dev mode copy and paste this into your terminal in a new folder (ensure you have the instant CLI installed):
Note: This recipe is in a pre-release alpha stage. It's usable but do so at your own risk.
This recipe sets up an HIE that does the following:
Accept FHIR bundles submitted securely through an IOL (OpenHIM)
Stores Clinical FHIR data to a FHIR store (HAPI FHIR)
Stores Patient Demographic data to an MPI (JeMPI)
Pushes FHIR resources to Kafka for the reporting pipeline (and other systems) to use
Pulls FHIR data out of Kafka and maps it to flattened tables in the Data Warehouse (Clickhouse)
Allows for the Data Warehouse data to be visualised via a BI tool (Apache Superset)
To launch this package in dev mode copy and paste this into your terminal in a new folder (ensure you have the instant CLI installed):
When deployed in --dev
mode the location of the UIs will be as follows:
OpenHIM
Test SSO user: u: test p: dev_password_only
JeMPI
Test SSO user: u: test p: dev_password_only
Superset
Test SSO user: u: test p: dev_password_only
Grafana
Test SSO user: u: test p: dev_password_only
Keycloak
u: admin p: dev_password_only
Extra UIs only exposed in --dev
mode:
Kafdrop
none
HAPI FHIR
none
Use the following example postman collection to see interaction you cna have with the system and see how the system reacts.