Questions we are asked
The questions procurement asks first
Relevant to youIs this a hospital management system?
For a clinic, yes: it runs registration, consultations, prescriptions, the dispensary and billing today. Underneath, every record is built to be shared across facilities as the platform grows. That shared layer is the roadmap.
Relevant to youWe already have systems. Do we replace them?
No. Facilities will connect existing systems through the FHIR API and keep them. Deployments are designed to begin with identity and exchange, and to adopt clinical or revenue modules only where the current system is the constraint.
Relevant to youWhere does patient data live?
Wherever national law requires. HealthOS is designed to deploy to managed cloud, to an in-country region, or inside government infrastructure. The sovereign model is designed so that data never has to leave the jurisdiction that governs it.
Relevant to youWhat happens when the internet goes down?
Facility operations are designed to continue, and to reconcile automatically on reconnection. Intermittent connectivity is a first-order design constraint, which is why the record is designed to converge rather than to require a permanent connection.
Relevant to youHow do you handle consent across facilities?
Consent is a recorded object with scope and expiry, not an implicit property of holding a login. Cross-facility access will be granted against that record, and every access written to an immutable audit trail.
Relevant to youWhich country are you starting in?
Sierra Leone. HealthOS is founded and built by Sierra Leoneans, and the first deployment is at home rather than in whichever market looked most convenient. The constraints here — intermittent connectivity, mixed-capacity facilities, constrained budgets — are the constraints that make a platform portable to the rest of the continent. Expansion follows proof.
Relevant to youWhat stage is HealthOS at?
Pre-launch. We are selecting the first cohort of private outpatient clinics in Freetown.