Quickstart
Run the full stack with docker compose up and verify it end-to-end in 5 minutes.
subscription-service
subscription-service is an Apache 2.0 pipeline that ingests HL7 v2 over MLLP (or proprietary REST), transforms it to FHIR R4 via Matchbox + StructureMaps, persists it to HAPI FHIR JPA, and fires FHIR Subscription notifications to downstream subscribers. It ships with an operator UI, an admin REST API, observability (Prometheus + Grafana + Jaeger), Keycloak-based OIDC, multi-tenancy, channel security, and a plugin SPI for vendor profiles and custom sinks.
Where to start
Architecture
The big picture — message flow, modules, multi-tenancy, channel security, plugin seams.
Deployment recipes
Working recipes for compose, k8s (EKS / GKE / AKS), nginx, Cloudflare tunnel, bundled observability.
Plugin SPI
Eight extension surfaces — vendor profiles, message sinks, filters, UI extensions — without forking.
By role
- You operate an integration shop — start with the Quickstart, then the Admin API, then the Deployment recipe that matches your target cluster.
- You evaluate engines — read the Architecture, then Security, then Vendor profiles to see what your EHR support looks like.
- You author a plugin or profile — start with Plugin SPI, then Vendor profiles if your work is HL7-specific.
- You subscribe to events — read External subscribers.
Source code
- Engine:
bzimbelman/fhir-ehr-subscriptions-service(Apache 2.0) - Vendor profiles:
bzimbelman/subscription-service-profiles - Community plugins:
bzimbelman/subscription-service-plugins-community