Service group
Identity & access
Session validation, trust boundaries, and partner access enforcement for platform requests.
Regional ingress and partner edge
Trusted entrypoint for clinical integrations, secure delivery, and platform traffic control.
The Siberia Health edge layer terminates TLS, applies traffic policies, and routes service requests to internal platform components with health-aware failover.
Service group
Clinical data exchange
Controlled ingress for structured medical payloads, integrations, and synchronization tasks.
Service group
Notifications & events
Delivery layer for asynchronous workflows, callback processing, and operational event streams.
Routing posture
Public traffic is separated from managed transport flows.
Site surface
The root path provides a public-facing service identity and lightweight operational context.
Gateway route
The dedicated gateway path is reserved for transport-specific handling and edge mediation.
Policy controls
Request handling is segmented by path so public pages and transport traffic do not collide.
Runtime snapshot
Operational indicators
Gateway edge
Available
TLS termination
Healthy
Internal routing
Connected