Insights
AI in a hospital information system: encrypted keys, a catalog, and a token cap
Hospitals will use language models. The question is whether the key lives in someone’s Gmail. HospitalMgr treats AI as configuration: a catalog of models, encrypted API keys, enable flags, and a monthly token limit per tenant.
Keys are stored encrypted at rest. Other modules do not need them in plain text. A facility can run patients, pharmacy, and billing with AI switched off. When they switch it on, the same hospital_id owns the cap.
Providers are the ones the hospital chooses — OpenAI, DeepSeek, Qwen, Gemini, or others in the catalog. Output can be wrong. A model must not prescribe, diagnose, or post accounts without a human. That is in the terms for a reason.
Government and mission sites should never paste a key into a shared WhatsApp. Configuration AI settings is a permissioned screen. Login logs will show who opened it.
What AI does not replace
Reception, batch expiry, lab templates, and the cashier. Assist sits beside the record. It is not a second HIS.
Cost control
Token caps are per hospital. A group of health centres does not share one runaway bill. Ask for that in any vendor’s AI slide.