Trust and data
Healthcare technology carries a higher standard of proof.
These are the questions a doctor should ask any company that wants to touch clinical records, answered before you ask them.
01 · The hard questions
Our answers, in the order they get asked.
02 · Where it runs
Two deployments, and the choice is yours.
Some practices want the record system on hardware they own. Others would rather never operate a server. Both are real options here, and neither is the one we quietly assume.
Hosted by Manara
We run the infrastructure.
- Nothing for your practice to operate, patch or back up.
- Data leaves the clinic. We name the components that hold it and where they sit.
- The usual choice for a single doctor or a small practice.
On servers you control
Deployed onto your own infrastructure.
- The record system runs on hardware your practice owns or rents.
- Anything that calls a model we do not host ourselves is named before you sign, rather than discovered later.
- Needs someone on your side who can keep a server running.
Which one fits is a question about what the practice can actually operate, so it gets answered in the assessment rather than assumed in a proposal. What does not change either way: the written record of which component runs where, agreed before any live patient data is involved.
03 · Your records
Your records belong to your practice.
They are exportable on demand in FHIR, an open standard, and the exit process is written into the agreement rather than left to goodwill.
A large amount of the frustration doctors have with clinical software comes from data that is technically theirs and practically trapped. The only real protection against that is a standard format plus a written exit, agreed before you start rather than negotiated when the relationship is already unhappy.
The arrangement
Your clinic is the data controller and Manara is the processor, set out in a data processing agreement rather than left implied. We do not work with live patient data until consent, processing location and access controls are documented and reviewed with you.
Egypt's Personal Data Protection Law, Law 151 of 2020, governs this work. Where a deployment moves personal data across a border, that is a live question for every company in this category, ourselves included, and it is one of the things the hosting decision changes. We treat it as work in progress and we will show you where that work stands.
What we will not tell you
- We have no delivered clients to show you yet, and we will not invent any. When we have one, it will be a real name with written permission.
- We do not claim certification or compliance we have not achieved.
- We do not quote an accuracy figure without saying how it was measured.
- We do not tell you the hosting question is simple. If a component runs on our infrastructure, data leaves your clinic, and we will tell you which component.
04 · Our position on AI
The system drafts. A clinician decides.
Every record is reviewed and signed by a clinician before it becomes a record, and clinical responsibility sits with the treating clinician exactly as it did before any software was involved.
The same principle limits what we are willing to build. We will not ship something that quietly makes a clinical judgement on a doctor's behalf, however well it might demonstrate.
AI supports healthcare professionals. It does not replace them.
الذكاء الاصطناعي يدعم الطبيب، ولا يحل محله.
Ask us the question that is not answered here.
If there is something you need in writing before a clinical system comes near your practice, ask for it in the first conversation rather than after a contract.