Healthcare software is mostly plumbing and permissions
Clinical software rarely fails because a screen looks wrong. It fails at the joins: a referral that arrives as a PDF and gets re-typed, a booking system that does not talk to billing, a reception PC with a folder of exported patient lists on its desktop. When practices and HealthTech founders describe their systems, the same problems come up:
- Patient data ends up on endpoints. Scans, exports and email attachments land on shared clinic PCs that are used by several people, often under one login.
- Integration is the real scope. A new patient app has to read from and write to the practice-management system or EHR, and every vendor exposes something different: an HL7 v2 feed, a FHIR R4 API, a CSV export, or nothing at all.
- Access has to be provable, not just restricted. The HIPAA Security Rule expects you to know who viewed or changed a record and when. An audit log that an administrator can edit does not answer that question.
- Phone calls carry health data. Patients read out dates of birth, insurance numbers and symptoms. Any automation that touches call recordings has to strip those details before they reach a third-party AI model.
- Where the data lives is a legal question. In the UAE, health data generally has to be stored inside the country. In Canada, PIPEDA and provincial health-privacy laws decide how a provider outside the country may handle it.
Work of ours that applies
ThinClient OS for clinics. Our ThinClient OS turns an ordinary PC into a locked terminal that boots straight into a Windows session in the cloud, with no local desktop and no local storage. The healthcare and clinic management solution page sets out how that applies: no patient data on the reception or treatment-room PC, credentials pushed from the server so staff never see or share them, remote support over the live session, and a failed machine replaced from a USB stick and an enrolment key. ThinClient OS is a shipped product. It has not yet been deployed in a clinic.
CallIntell's redaction pipeline. CallIntell turns recorded calls into reviewed CRM records. Personal identifiers are redacted in the transcription worker, before any text reaches a language model, and anything the system is not confident about goes to a human review queue rather than being guessed. CallIntell is in pilot with a design partner outside healthcare. The pattern fits a patient phone line well, but it has not been tested against protected health information.
Audit and isolation from our own SaaS products. Esparks Biz adds the signed-in business to every database query through one shared data layer, which refuses to run any query that has no business attached, and a database trigger stops audit-log rows from being edited. Esparks Edu ships built-in tools to export or erase one person's data on request. A multi-clinic platform needs exactly these controls. We built them for inventory and school records, not for health records.
What we have and haven't built in healthcare
We have not shipped software for a healthcare client. We have not built an EHR integration, a telehealth platform or a remote-monitoring product, and we have never signed a HIPAA Business Associate Agreement. What we bring is the engineering underneath: access control, encryption, audit logging, redaction and deletion tooling that we have built and run in production in other sectors.
If your project needs our team to handle protected health information, that has to be agreed in the contract before any data is shared. Many builds can be developed and tested against synthetic or de-identified data, so our engineers never touch PHI at all, and we plan projects that way by default.
Compliance: what we design for
On US projects we design for HIPAA Privacy and Security Rule controls. On Canadian projects we design for PIPEDA and the provincial health-privacy law that applies, such as PHIPA in Ontario. On UAE projects we design for the federal PDPL (Federal Decree-Law No. 45 of 2021) and the UAE's health-data rules, including in-country storage. In software, that means role-based access, encryption in transit and at rest, audit logs, retention and deletion rules, and a documented record of where every copy of the data lives.
Esparks IT Solutions is not certified against any of these. We hold no SOC 2 report, and our ISO/IEC 27001:2022 certification is in progress, not held. Your compliance officer and auditor sign off, and we build what they need to see.
How to start
Most healthcare engagements begin as a custom web application or a mobile app, often alongside a security review of what you run today. We work remotely from India with clients in the United States, Canada and the UAE, and we sign an NDA before you share project details.