medOS ultra

System Topology

Service-to-service topology: gateway, NATS mesh, MongoDB, Supabase read model, edge functions.

1 min read diagramsUpdated 2026-04-15docs-site/docs/architecture/system-topology.md

Service topology

flowchart TB
  ALB["ALB / nginx"] --> GW["API Gateway :3001"]
  GW --- NATS(["NATS"])
  NATS --- AUTH["auth"]
  NATS --- CLIN["clinical"]
  NATS --- FIN["financial"]
  NATS --- DIAG["diagnostic"]
  NATS --- MED["medication"]
  AUTH --> M[("MongoDB")]
  CLIN --> M
  FIN --> M
  DIAG --> M
  MED --> M
  CLIN -. events .-> SUPA["Supabase<br/>edge fns + Postgres"]
  FIN -. events .-> SUPA

Service ports

Service Scope name Port Purpose
gateway ever-api-gateway 3001 API router, request aggregation
administration ever-api-administration 4002 System admin, settings
filestore ever-filestore 8083 File upload, IPFS integration
messaging ever-messaging 8084 / 3003 Socket.IO, email, SMS
printing (Spring Boot) 8088 PDF report generation
public-api ever-public-api 8082 Unauthenticated + FHIR endpoints
auth ever-api-aaa JWT auth, RBAC
clinical ever-api-clinical Encounters, notes
diagnostic ever-api-diagnostics Lab & imaging orders / results
financial ever-api-financial Billing, RCM
foundation ever-api-foundation Base models, master data
medication ever-api-medications Prescriptions, drug mgmt
global-sequence ever-api-global-sequence HN / VN / AN numbering
eform ever-api-eform E-Form API layer
interoperability 2575 (MLLP) HL7 / FHIR / CCDA bridges
patient-relationship PRM / opportunity tracking

Infrastructure ports

External integrations

Ask Anything