How gunsu12/hosim-go works
HOSIM-GO is a hospital information system and electronic health record with a Svelte client and Go API. The user-facing path runs from browser login and navigation through clinical or master-data screens to the backend; the README also describes emergency, outpatient, inpatient, interoperability, and audit capabilities. The graph preserves these documented areas, but several are represented by their existing module directories because their implementation was not sampled. Edges are limited to relationships visible in the excerpts or stated in the README.
Main entry points: main.go Go API server · clinical EHR and orders · App.svelte Svelte application · master Master screens
Components 23
Web client
- Svelte application
web/src/App.svelte - Session store
web/src/lib/stores/auth.svelte.ts - API client
web/src/lib/api.ts - Clinical screens
web/src/lib/pages/clinical - Master screens
web/src/lib/pages/master
API and security
- Go API server
cmd/api/main.go - Authentication
internal/auth - JWT middleware
internal/middleware/auth.go - PostgreSQL database
internal/database/database.go - Activity audit
internal/audit
Hospital records
- Patient records
internal/patient - Practitioner records
internal/practitioner - Organization masters
internal/organization - Payers and tariffs
internal/finance
Clinical care
- EHR and orders
internal/clinical - Care settings
internal/emergency - Outpatient care
internal/outpatient - Inpatient care
internal/inpatient
Hospital operations
- Item catalog
internal/catalog/item - Pharmacy
internal/pharmacy - Inventory
internal/inventory - Health integrations
internal/integration
Other components
- Hospital user
Connections 26
- Hospital user → Svelte application: uses
- Svelte application → Session store: checks session
web/src/App.svelte - Session store → API client: logs in through
web/src/lib/stores/auth.svelte.ts - Svelte application → Clinical screens: renders
web/src/App.svelte - Svelte application → Master screens: renders
web/src/App.svelte - Svelte application → Go API server: uses backend
- Go API server → Authentication: registers routes
cmd/api/main.go - Go API server → JWT middleware: protects routes
cmd/api/main.go - Go API server → Item catalog: wires handlers
cmd/api/main.go - Go API server → Organization masters: wires handlers
cmd/api/main.go - Go API server → PostgreSQL database: initializes
- Go API server → Patient records: serves master data
- Go API server → Practitioner records: serves master data
- Go API server → Payers and tariffs: serves master data
- Clinical screens → EHR and orders: presents
- EHR and orders → Care settings: supports
- EHR and orders → Outpatient care: supports
- EHR and orders → Inpatient care: supports
- EHR and orders → Pharmacy: orders prescriptions
- EHR and orders → Health integrations: interoperates
- EHR and orders → Activity audit: records activity
- Item catalog → Inventory: supports supplies
- Master screens → Patient records: manages
- Master screens → Practitioner records: manages
- Master screens → Organization masters: manages
- Master screens → Payers and tariffs: manages