Health tech
Health tech development
Member-facing health products across web, iOS and Android — built so that offline access works, and so the security questionnaire that arrives before the contract has real answers.
From £75/hrAn estimate before any work startsOne developer, start to finish
01
In health tech the questionnaire is the sales process.
Where the data sits, who processes it, how it is deleted, what happens when you are unavailable. These arrive as a spreadsheet before the contract, and a product that cannot answer them loses to one that can, whatever it does.
02
What actually gets built
Member-facing apps
Native iOS and Android with the web platform behind them, for products people carry rather than visit.
Offline and emergency access
The case where the network is the thing you cannot rely on. It changes the architecture, so it is decided at the start rather than bolted on.
The security questionnaire
Data residency, sub-processors, retention, deletion, access control and continuity — answered from how the system is actually built rather than from a document that describes a different system.
Integrations into the rest of care
Insurance, partners and whatever the buyer already runs — usually the part with a specification rather than a developer portal.
03
How the work runs
You describe it
Two sentences is enough to start. What you are building, who it is for, and which rule or buyer is forcing the shape of it.
A scope and a price, inside 24 hours
What is in, what is deliberately out, what each stage costs and what it depends on. Where a regulator or a procurement process sets the timeline, that goes in the plan rather than being discovered in week six.
Built in the open
Your repository from the first commit, deployed somewhere you can see it from the first week.
Handed over properly
Your accounts, your keys, your infrastructure, and a README that assumes the reader is not me.
- Rate
- From £75/hr
- Scope and price
- Inside 24 hours
- Written by
- The person who scoped it
Has a buyer sent you a security questionnaire? Those answers should come from the architecture, not from a document written afterwards. If they do not match, that is the finding.
Start a project →05
Who this has been done for
World Medical Card
Medical ID and emergency access for travellers. Midnyte leads the technical side: architecture, the native iOS and Android apps, the web platform behind them, and the infrastructure underneath.
An ongoing fractional CTO engagement rather than a finished project — it is live, and it can be opened and used above.
Common questions
Can you answer enterprise security questionnaires?
Yes, and the useful version of that is answering them from how the system is genuinely built rather than from a document that describes an aspiration. Where the two do not match, that gap is the finding and it is better found by you than by the buyer. There is a page on the questions that keep coming up.
Where will our data be stored?
Wherever you decide, and it is decided before any code is written: which region, which sub-processors, what is retained and for how long. Changing it afterwards is a migration, and in this sector it is a migration with a contract attached.
Do you work on regulated medical devices?
No. Software that is a regulated medical device carries a certification regime this does not cover, and saying otherwise would be the sort of claim these pages exist to avoid. The work here is member-facing products, the platforms behind them, and the security and data questions that come with enterprise buyers.
04
Tell me what you are building
Two sentences is plenty. You get back a scope, a price, and which of the data questions will decide your timeline.