OllyHealth Insurance + AI Triage
14 Go services · 953 process map · sub-second clinical triage · self-hosted.
14 Go services · 953 process map · sub-second clinical triage · self-hosted.
Claims, eligibility, enrollment, billing, provider, notifications, triage, care, consent, and more - each with its own schema and event streams.
Policies, coverage terms, claims adjudication, prior authorizations, billing cycles, provider credentialing - all modelled and explained.
Kafka event catalog covering all domains. Outbox pattern for guaranteed delivery. Temporal workflows for long-running sagas.
Keycloak identity with tenancy enforced in application code; TLS in transit; consent capture, audit trail and GDPR Article-17 erasure implemented in the consent service. Field-level encryption, OPA/ABAC and RLS are designed, not yet built - see Data Protection.
LLM-powered medical triage engine with decision tree traversal, differential diagnosis, and care pathway recommendations.
A 117-term ontology aligned to FIBO, FHIR, SNOMED-CT and Socotra, published in OpenMetadata with the ~80 Olly domain tables linked to the concepts they implement.
A self-hosted open-source data plane (Kafka, OpenSearch, Keycloak, Temporal, Novu). Today it runs on two docker-compose dev VMs; Google Kubernetes Engine is the production target, not the current deployment.
If you just joined Olly, walk through these four steps in order.
The L1 Business Landscape shows how the seven business capabilities fit together. Five actors, two clinical externals. No infrastructure noise.
L2 Container Views drills into each capability - every Go service, frontend, datastore, and shared platform rail.
The Business Processes page renders six dynamic views (claim adjudication, member enrolment, triage to care, etc.) as sequence diagrams from the same Structurizr model.
Designs holds the long-form decisions - start with Access Control & Data Protection.