Digital-first without compromising clinical duty
Remote access only works if the pathway still supports consent, safeguarding, correct result delivery, and clear escalation when something looks wrong.
EmERGE: secure digital care delivery — flexible for clinicians, safe for patients.
EmERGE mHealth builds clinically evaluated digital pathways used by sexual health and HIV services — combining a patient-facing app with clinic systems so care can be delivered face-to-face or remotely without fragmenting the record or the clinical conversation. We worked with their team to harden the platform architecture, improve reliability, and keep the system ready for the next wave of service and compliance demands.
Healthcare & healthtech
Platform evolution
Clinical safety & scale
Not-for-profit provider
Remote
+ in-person pathways on one platform
Clinic-led
Co-designed with clinicians & communities
Secure
Architecture ready for regulated data
Operational
Capacity-friendly service delivery
The Client
Clinical innovation, carried forward as a sustainable digital service.
EmERGE mHealth is a not-for-profit organisation dedicated to secure, high-quality, clinically evaluated services for hospitals, clinics and communities. Its platform grew out of the EU Horizon 2020 EmERGE programme — a collaboration between specialist clinicians, digital builders and the European AIDS Treatment Group — and now operates commercially on a not-for-profit basis so revenues can continue to support delivery and improvement.
Today the Core EmERGE app and tailored offerings such as the PrEP EmERGE app give patients a governed route to message their clinic, review results, manage medications and appointments, and stay on track — while teams retain control inside the clinical setting. Learn more on EmERGE mHealth's site.
The Challenge
Deliver flexible care at scale — without a fragile stack or a compliance gap.
One platform, many services
Different cohorts (for example PrEP users versus wider sexual health pathways) need tailored journeys — without multiplying codebases or operational risk.
Services do not stand still
Integrations with clinic systems, new sites joining, and evolving information governance expectations all place pressure on architecture, observability and release discipline.
What the platform enables
Patient-facing tools that stay inside the clinical relationship.
The app is not a standalone “consumer health” product sitting outside the service. It is designed to work in combination with clinic systems so teams can offer a continuous digital pathway — switching between remote touchpoints and face-to-face appointments when clinically appropriate — without losing traceability.
- Blood and swab results surfaced where the pathway allows
- Medication and vaccination information aligned to the care plan
- Appointment prompts that reduce silent drop-off
- Messaging that routes through the governed clinical channel
Secure access
Passcode, biometrics and session handling appropriate to health data.
Results & context
Numeric and graphical views of results patients are cleared to see — tied to the clinic record.
Medication support
Information, frequency, and reminders that sit alongside — not instead of — clinical advice.
Appointments & messaging
Reminders, calendar hooks, and two-way communication within the governed pathway.
Representative capabilities described on the EmERGE product pages; exact feature mix varies by deployment and clinical configuration.
Our Approach
Build for clinical reality, not only the roadmap deck.
FatFish specialises in regulated digital delivery. For EmERGE, the goal was not simply to “add features” but to make the platform easier to operate safely as more NHS and partner services route patient contact through the pathway — echoing the narrative on our public EmERGE case overview.
01
Ground in live services
We aligned engineering priorities with how clinics actually roster care, handle spikes in demand, and recover when integrations misbehave — not a slide-deck-only architecture review.
02
Strengthen platform bones
Reliability, separation of concerns, and clear boundaries between patient experience and clinical back-end reduce the cost — and risk — of each new cohort or integration.
03
Design for assurance
Security and governance are treated as product requirements: traceability, access control, and operational logging that stand up when procurement or IG ask sensible questions.
04
Ship so services can adopt
Releases emphasise operational readiness: observability, rollback discipline, and documentation that clinical operations teams can trust during go-live.
How it fits together
A pathway model clinicians recognise.
Digital care only earns trust when it mirrors professional responsibility: the app extends the clinic, it does not substitute for it. The architecture reflects that split — patient experience on device; clinical accountability in the systems that already carry the record.
01
EHR & scheduling
Appointments, results authoring and clinical decisions stay anchored in the systems trusts already run.
02
Governed exchange
Clear interfaces so data moves predictably — including newer deployments such as integrations with electronic health records where services require them.
03
Patient pathway
Passcode and biometrics, tailored screens per programme (for example Core versus PrEP journeys), and messaging in the clinical channel.
04
Run & improve
Service owners can see whether the pathway is healthy — not only whether the app released on time.
Who it helps
Outcome-led for patients, accountable for clinics.
Confidence that remote touchpoints are clinically bounded.
Pathways keep high-risk decisions and diagnostics inside appropriate governance, while still reducing unnecessary footfall for routine tasks.
Capacity that flexes with demand.
Well-run digital triage and asynchronous contact can absorb peaks — particularly where sexual health services face predictable pressure — without stacking hidden manual work.
Access that respects privacy and literacy.
Co-design — for example on PrEP journeys — means the interface reflects how people actually manage medication, results and messaging, not only clinical defaults.
Evidence suppliers expect.
Security posture, data flows and supplier assurance line up with how NHS organisations and partners procure healthtech — including certifications such as Cyber Essentials carried by EmERGE mHealth.
Outcomes
A digital service patients can use — and trusts can stand behind.
As described in FatFish's overview of the engagement, EmERGE now operates a more robust platform that supports flexible service delivery, eases pressure on clinical resources, and maintains high standards of patient care as digital channels scale.
Flexiblepathways
Remote and in-person care supported through the same governed stack — matching how services want to work post-pandemic.
Efficiencythat shows up in rosters
Less time chasing routine contact means teams can focus people who need face-to-face assessment.
Secureby design
Architecture and process choices aligned to health data expectations and partner assurance — not bolted on after go-live.
Evolvingwith services
Platform thinking that makes new integrations and cohort-specific apps tractable as EmERGE continues to grow with clinics.
Risk & governance
Healthtech that stands up to serious scrutiny.
In digital health, the failure mode is not only a outage — it is the wrong information in the wrong hands. EmERGE's model depends on sustained trust from clinicians, commissioners and patients; our work is shaped around that bar.
Clinical safety before feature velocity
Product decisions are checked against what could confuse a patient or bypass a safeguard — pace follows safety, not the other way around.
Clear data responsibilities
The pathway keeps a crisp story for who stores what, who processes it, and how access is revoked when care ends — a baseline expectation for health data platforms.
Operational evidence
Logging, deployment records and incident practice are part of the deliverable — procurement and IG reviews are easier when operations are already documented.
Third-party realism
Integrations such as EHR connections are treated as shared-risk programmes: contracts, technical cut-over and clinical cut-over planned together.
Next steps
Building regulated digital care?
We help health and care organisations ship platforms that are secure, operable and proportionate to NHS governance. Book a short intro call to explore architecture, assurance and delivery — or start with our digital readiness audit.