Domain Model
Olly's domain model is the shared vocabulary every service, event, and schema is built from. These pages are the narrative layer: what each concept is, how it behaves over its lifecycle, the invariants that hold, and how it flows across services.
Two layers, know which to consult
The OpenMetadata catalog is the canonical field-level reference: every column, type, nullability, enum, and the concept↔table links. It is generated and kept in sync, never hand-maintained.
These domain pages are the narrative layer: lifecycle and state machines, load-bearing invariants, the why (double-entry ledger, CQRS read-models, effective-dated versioning), cross-service flows, and the modelling caveats (UK-vs-US framing, free-text-vs-enforced enums). For an exhaustive field list on any entity, follow its catalog link rather than expecting a table here. See Ontology & Catalog for how the two fit together.
Contract & money
Policy, PolicyTerm and PolicyElement (the effective-dated versioning model), and the quote-to-cancellation lifecycle owned by enrollment.
How a Claim moves from submission through adjudication to payment: ClaimLines, the append-only ClaimEvent trail, and prior authorization.
Charges, invoices, payments and the double-entry ledger that is the source of truth for money; installment schedules and the grace-period → lapse cycle.
Parties & care
The unified Party model (members, employers, brokers, providers), PartyRole and Accounts, plus Member as a projection over Party + coverage.
The provider directory, the credentialing lifecycle, and how in/out-of-network status feeds claim adjudication.
The clinical journey (Episode, Appointment, ProviderSlot, Prescription, DiagnosticsReferral), opened from a triage recommendation.
The CQRS read-models that drive adjudication (MemberCoverage, CoverageAccumulator, DeductibleStatus), projected from enrollment events.
Schemes, consent & communications
Employer group cover: Scheme, SchemeMember, bulk enrollment jobs, and the on-demand eligibility roster and billing aggregate.
ConsentRecord, the append-only consent audit trail, and the GDPR Article 17 right-to-erasure deletion workflow.
Notification preferences and the delivery log, a thin adapter in front of Novu, which owns templates and channel routing.
The triage Session/Turn conversation model, the structured disposition, and the LLM judge harness, plus the AI-chat assistant.
Broker configuration, delegated authority limits, and commission accrual on bound policies.
Generated member documents (schedules, EOBs, letters) and the market-keyed templates that render them.
The full, field-level ontology lives at catalog.dev.hiolly.com (OpenMetadata).