Questions
The things doctors actually ask us.
Answered at the length the question deserves rather than the length that fits on a card. If yours is not here, ask it in the first conversation.
01 · The company
What Manara is, and how it works
What exactly does Manara do?
Manara is a healthcare technology company founded and run by doctors, working in Cairo and across Egypt. We start with a healthcare problem rather than with a product. We listen to the people living the problem, study the workflow it sits inside, find the root cause, and then build the technology that solves it. Depending on what the diagnosis turns up, that might be software, AI, automation, better data infrastructure, or digital strategy, and it is often a combination. Today two of our three layers are things you can actually buy. Clinical technology covers our first product, an AI medical scribe, alongside implementation of a standards based clinical record system and custom clinical systems built for one practice. Digital practice growth covers healthcare branding, digital presence, search and AI search visibility, and content. The third layer, healthcare intelligence, meaning data infrastructure, AI monitoring and predictive systems, is in development and we describe it that way rather than selling it. We are not an EMR vendor, we are not a marketing agency that happens to work with doctors, and we are not a company that believes AI solves everything.
Is Manara an EMR company?
No. We implement and configure a clinical record system where a practice needs one, and Manara EMR is built on HL7 FHIR R4, the international standard for exchanging healthcare information, so the data stays portable. But selling one fixed clinic system identically to every practice is what the market already does, and it is not our shape. We diagnose first, then build what the problem actually needs, which is sometimes a record system and often is not. In most practices our record work runs alongside the system you already have rather than replacing it, because ripping out something a clinic depends on is rarely the highest impact first move. If your problem turns out to be documentation time, or how patients find you, or five tools that do not talk to each other, then a new EMR is not the answer and we will tell you so.
Do you work with individual doctors, or only clinics?
Both. An individual doctor with one specific problem is a legitimate place to start, and the scribe can be bought on its own without the rest of the platform. That is often the cheapest way for both sides to find out whether we are useful to each other. Private clinics are where most of our work sits today, because a practice has enough moving parts that fixing one thing usually reveals the next. With healthcare organizations we work on assessment, custom builds and record systems, while being clear that the data and analytics side of what they usually want is still in development. Healthcare systems at national scale are a direction of travel for us rather than something we offer.
How does an engagement start?
With a conversation about the problem, not a demonstration of a product. Thirty minutes, with a doctor on the team. If it is worth going further, the next step is a structured assessment of the practice: clinical workflow, documentation, records, data, operations, patient experience and digital visibility, together with an honest read on where AI genuinely helps and where it does not. The assessment ends with the highest impact opportunities we found and one recommended first step, which is deliberately small. We would rather solve one thing properly and earn the next conversation than sign a large engagement neither side can carry.
What does it cost?
It depends on the practice and on what the assessment finds, so we quote after we understand the problem rather than before. We would rather give you a number that survives contact with your clinic than one that looks good on a website and gets revised upward later. The shape of it: implementation work is quoted once, ongoing service is monthly, and the scribe is priced per doctor. Tell us what you are dealing with and we will tell you what it takes.
02 · The scribe
The product that exists today
Does the AI medical scribe work in Arabic?
Yes, and specifically in the way Egyptian clinics actually speak. The scribe handles Egyptian Arabic, English, and both mixed inside a single sentence, with medical terminology in either language. That last case is the one that breaks most systems: a doctor who says the history in Egyptian Arabic and the findings in English, switching mid sentence without noticing, because that is simply how the work is done. The scribe was built for that linguistic reality from the start rather than adapted to it afterwards. Clinical output is produced in English, which is what hospitals and referral letters ask for, with Arabic names transliterated rather than left in mixed script. You can also type instead of dictating, upload audio recorded earlier, or photograph a report and let it read that. If a field was never stated, the system asks a short follow up question about it rather than inventing a plausible answer.
How accurate is it, really?
On our internal benchmark the scribe hears about ninety five words in every hundred correctly and fills about four fifths of the structured record straight from the dictation. Here is the part most vendors leave out: that benchmark runs on synthetic, text to speech audio rather than real clinical recordings. Synthetic audio is cleaner than a consulting room, so treat the number as a floor measured in quiet conditions and not as a promise about yours. Real consented recordings collected during a pilot are what would upgrade the claim, and when we have them we will publish the new number whether it is better or worse. We would rather be the company that tells you how a figure was measured than the one with the bigger figure.
Does the AI make clinical decisions?
No. The system drafts, asks about fields that were not stated, and files. It does not decide anything. 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. Nothing we build changes that, and we would not want it to. It is worth saying that the same principle limits what we will build: we will not ship something that quietly makes a clinical judgement on a doctor's behalf, however well it might demonstrate.
03 · Data and records
Where things live, and who owns them
Where is our data stored, and does it leave the clinic?
That is a decision you make with us, not one we make for you. Manara can run as a hosted service on infrastructure we operate, or it can be deployed on servers your practice controls. If you choose the hosted option then yes, data leaves the clinic, and we say so plainly because the opposite claim is common in this market and is often made about systems where it is not true. If you choose to run it yourself, the record system sits on hardware you own, and anything that calls a model we do not host ourselves is named before you sign rather than discovered afterwards. Ask us that question directly, and ask every other vendor the same one.
Whichever deployment you pick, we set out in writing which component runs where before any live patient data is involved. Your practice is the data controller and Manara is the processor, set out in a data processing agreement rather than left implied, and 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. 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 choice changes. We treat it as work in progress and we will show you where the work stands rather than claim a certification we do not hold.
Who owns the records?
Your practice does. The records are exportable on demand in FHIR R4, which is an open international standard rather than a format only we can read, and the exit process is written into the agreement rather than left to goodwill. If you decide to leave, your data leaves with you in a form another system can actually accept, which is the part that usually goes wrong. This matters more than it sounds. A large amount of the frustration doctors have with clinical software comes from data that is technically theirs and practically trapped, and 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.
Do you build patient booking and patient messaging?
Not today. Anything that collects information directly from patients carries data protection obligations under Egypt's Personal Data Protection Law that we are working through first, and we will not sell it before that work is done. We are aware this is the answer nobody wants, and we would rather give it than take a deposit for something we cannot yet do properly. When patient facing surfaces do exist, they will ship under your practice's name rather than ours, because the relationship with the patient is yours. What we do integrate today is on the doctor's side: WhatsApp is where a lot of clinical work already happens, so rather than asking you to stop using it, we let something a doctor sends on WhatsApp land inside the system.
Still have a question?
Ask it in the first conversation. Thirty minutes, with a doctor on our team, about your practice rather than about our product.