Frequently Asked Questions
Do we need to replace our HIS?
Usually not. The core clinical system is heavily certified and expensive to own, and what most providers actually lack is the layer around it: a trustworthy patient index, an access model that survives an audit, and machine calls to the insurer instead of portal re-keying. We integrate over HL7 and FHIR rather than replacing what already passes inspection.
What does it cost, and how do you price it?
Hours times $40 to $100 per hour by role. The module table gives the range for each of the eight modules and the worked example shows 1,640 hours coming to about $106,600 at a $65 blend. The regulated and HIPAA multipliers are stated separately rather than folded in, because they apply across the board and would otherwise hide inside every line.
Who owns the code, the patient data and the interfaces?
You do. The code is yours on delivery, patient data lives in your infrastructure rather than ours, and the interfaces are yours to keep running or hand to another supplier. We do not retain a copy of clinical data, and there is no arrangement under which it becomes training material for anything.
Is our product a medical device?
Possibly, and it is the question worth answering first. Clinical decision support crosses into regulated territory sooner than most teams expect, and EU MDR Rule 11 pushes much of it to Class IIa or higher and therefore to a notified body. We determine regulated scope during discovery and put it in writing. We are not a notified body and cannot certify you; we can make sure you are not surprised.
Can you connect us to Dhamani or NPHIES?
Yes, and the honest part is that connectivity is the small half. Each channel has a conformance path that has to be passed before production, NPHIES on FHIR R4 with Saudi profiles and certificates renewed annually. Budget those weeks as calendar rather than as hours, because nobody bills them and everybody waits for them.
How do you handle duplicate patient records?
Deterministic matching acts automatically, probabilistic matching only proposes into a human review queue, and merge is reversible with an approver. A wrong merge that cannot be undone is the worst outcome in this domain, so the design starts from that rather than from throughput.
Does health data have to stay in the country?
In Oman, cross-border transfer of sensitive data needs express consent plus an adequacy assessment, so in-country hosting is the sane default. The UAE restricts processing health data outside the country without approval. The practical consequence is that every offshore analytics call, support tool and model prompt is a transfer and has to be gated explicitly.
We only have one healthcare build. Is that enough?
We have iCareHeal, described in full above, and a client statement from a medical device business. That is what we have and we would rather say so than pad the page. Everything else here is protocol, regulation and failure modes, which you can verify independently of us.
Can you produce our validation package?
We can produce IQ, OQ, PQ and a traceability matrix alongside the build, which is far cheaper and more convincing than reconstructing them afterwards. Approval of that package belongs to your quality function and your auditor, not to us.
What happens to our data if we stop working with you?
It never leaves your infrastructure, so nothing has to be handed back. We document the interfaces and the mappings as part of delivery specifically so another supplier can pick them up without us, which is the test of whether documentation was real.
