Synetra Health
Exploring offline, low-power decision support for pre-hospital care in austere environments.
Synetra Health began during an intensive venture programme in Porto in July–August 2026. Our founding team explored how medics make high-stakes decisions when connectivity, power, time and equipment are constrained, and developed Synetra Insight: an initial hardware/software concept for local patient monitoring and decision support. It remains an early concept and prototype — not a clinically validated or deployed medical device.
- Role
- Co-founder — design, procurement, prototype and venture narrative
- Organisation
- Synetra Health
- Dates
- 2026-07 — ongoing
- Location
- Porto, Portugal · London, UK
- Type
- Venture
- Status
- Active
- Record
- Flagship
- Evidence
- B — first-hand account
- Disciplines
- Entrepreneurship, Product, Research, Design, Technology
40+
Still being verified
The context
Pre-hospital and austere care is where ordinary product assumptions fail: no reliable connectivity, no mains power, no time, and often no second opinion. Software written for a hospital corridor does not survive that environment.
The initial hypothesis
We began believing the problem was information access. Field conversations moved us toward something narrower: decision confidence under constraint, with the device required to work when everything else does not.
Research
The team ran more than forty early conversations with people working across emergency and pre-hospital settings. What those conversations can and cannot be used to claim is being documented explicitly; nothing here is presented as clinical evidence.
What I worked on
- Procurement and maker-lab access for the physical prototype.
- The web and software demonstrations used to make the concept legible.
- Programme submissions and the venture narrative.
- Prototype storytelling — turning a rough build into something a stranger can evaluate.
Honest status
Early-stage concept and prototype. No clinical validation, no deployment, no regulatory position. The interesting work right now is deciding which constraint the product refuses to compromise on.