The Encounter Service models visits and admissions — admit, discharge, transfer — and publishes domain events when encounter state changes. ADT messages from ingestion drive most transitions.
Responsibility in one sentence
Persist the authoritative encounter record, enforce valid ADT transitions and notify downstream consumers.
Could not build diagram for model "example-healthcare".
Stores encounter aggregates.
Tracks admit / discharge / transfer.
Publishes encounter events to the bus.
The Encounter Repository stores encounter aggregates keyed by patient and visit id.
The Encounter State Machine rejects illegal ADT jumps that would corrupt census.
The Event Publisher emits domain events for apps and audit correlation.
REST endpoints support encounter lookup and status queries for portals and FHIR mappers. See the Overview tab for the OpenAPI contract.
Contract
Status transitions are idempotent on message control id so duplicate ADT replays are safe.