Vitalis OS
Vitalis OS is an offline-first healthcare environment being designed to help healthcare workers access trusted reference knowledge and operate essential tools under real connectivity constraints.
The project begins with the Vitalis Kernel, a small technical core responsible for identity, permissions, audit boundaries, local storage, package verification, controlled updates and recovery.
The operating problem
Healthcare work continues when a network becomes slow or unavailable. A dependable system should preserve essential local functions instead of assuming uninterrupted cloud access.
Vitalis OS is being designed around:
- Local access to approved knowledge packs
- Search that continues without public internet access
- Clear user roles and permissions
- Encrypted local storage
- Visible audit records
- Signed software and content packages
- Backup, restore and rollback
- Carefully isolated interoperability adapters
Trusted knowledge packs
Every future knowledge pack should preserve its source, publisher, licence, publication date, review date, version, checksum, medical-review status and withdrawal instructions.
The objective is not to copy everything available online. It is to make a controlled body of properly licensed information available with visible provenance.
Prototype boundary
The first trusted-core prototype will test identity, permissions, audit, storage, offline search, package verification, backup and recovery using simulated or non-patient information.
It will not diagnose, recommend treatment, calculate medication doses, perform emergency triage, replace a clinician or control a medical device.
Development path
- Define intended use, users, workflows and non-goals.
- Complete architecture decisions and the initial hazard log.
- Build and test the Vitalis Kernel prototype.
- Package a small approved reference collection.
- Assemble the first developer environment.
- Run simulation and usability evaluation.
- Seek an independently reviewed controlled pilot.