All case studies
ProductionDigital health · Flagship case study

Engineering reliable digital health software for low-connectivity hospitals

Full-stack product engineering for an evidence-based neonatal EHR and clinical decision-support platform used in frontline care environments.

My role
Software Developer · Mobile, web and backend
Period
2025–Present

PROJECT OVERVIEW

Neotree supports neonatal care teams with digital clinical workflows and decision support. I contribute across the Android application, web editor and backend services while working with clinicians, researchers and distributed engineering teams.

The problem

Clinical software has to stay useful when connectivity is intermittent, devices are constrained and workflows cannot pause while a server catches up. Changes also need to remain traceable and safe across distributed deployments.

My responsibility

I own and contribute to full-stack features, offline-first data flows, platform tooling and clinical usability improvements. Product and clinical decisions are made collaboratively; this case study describes only my engineering contribution.

REAL-WORLD CONSTRAINTS

Intermittent connectivity and server availability
Older and distributed Android devices
Sensitive health information
Dynamic clinical workflows and forms
Coordination across clinical, research and engineering teams

SOLUTION & CONTRIBUTION

The platform treats local operation as a first-class state, then synchronises validated data through backend services when infrastructure becomes available. Version-aware tooling and explicit changelogs improve release traceability, while targeted UI and performance work keeps clinical tasks clear on constrained devices.

  1. 01Designed and implemented changelog and version-control capabilities across platform modules.
  2. 02Improved offline-first synchronisation flows and recovery behaviour.
  3. 03Optimised clinical interfaces and dynamic form workflows for usability and performance.
  4. 04Built platform tooling for data-key integrity and safer script management.
  5. 05Contributed to application-update infrastructure and device acknowledgements.

SANITISED ARCHITECTURE

Clinical workflows
Offline-first Android client
Synchronisation and API services
Neotree data platform

Certain implementation details and screens are intentionally anonymised to protect organisational and user data.

Engineering challenge

A device can have a network connection while the server it depends on is unavailable. Treating those states as equivalent creates confusing failures. The engineering approach separates local persistence, network reachability, service availability and synchronisation acknowledgement so work can continue and recover predictably.

Observable outcomes

  • More explicit release history and version visibility
  • Safer recovery paths for interrupted synchronisation
  • Improved maintainability of dynamic forms and scripts
  • A stronger foundation for managing distributed application versions

Technology used

FlutterReactTypeScriptNode.jsPostgreSQLREST APIsDocker

Next case study

Neotree, Impilo and DHIS2 interoperability