IMFS HOSPITAL OS
IMFS Hospital OS documentation
This documentation describes what exists in the application today, what is partially implemented and what is verified in the pilot project. Each feature page states who uses it, which documents it produces and what its limits are.
Features of the Spitale (hospital) module
Map of the IMFS Hospital OS hospital module: patients and admissions, inpatient chart, ED, operating theatre, laboratory, AI imaging, treatment, pharmacy, outpatient care, on-call duty, CNAS reporting, patient portal and take-over from InfoWorld.
ReadImplementation in the pilot project
How an IMFS Hospital OS pilot runs: assessment, Linux infrastructure, CNAS, InfoWorld and PACS connections, data take-over, role-based training and the final decision.
ReadSecurity and data
How IMFS Hospital OS protects patient data: a separate database per institution, role- and ward-based access, access log, qualified signature, a separate portal and the limits of AI assistance.
ReadFrequently asked questions
Answers about IMFS Hospital OS: pilot status, relationship with InfoWorld, the role of AI in imaging, CNAS reporting, offline use, languages and pricing.
ReadUser manual
Step-by-step work for each hospital role — registration, emergency department, ward physician, nurse, laboratory, imaging, operating theatre, pharmacy, outpatient care, CAS reporting and administrator — using the real button names from the application. The manual is in Romanian.
How to read a feature's status
- Implemented in the application · evaluated in the pilot — the feature exists in the application; verification on an institution's configuration happens in the pilot.
- Partially implemented — the feature exists, and its page states exactly what is missing.
- In preparation — a confirmed direction, not yet implemented.