Stamen Health Executive Summary

From Research Wiki
Revision as of 10:41, 15 April 2026 by Admin 3julmthh (talk | contribs) (Created executive summary with 2026 startup best practices, one-page plan, and 12-month milestones)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Executive summary and one-page plan for Stamen Health, the EHDS compliance and health data infrastructure startup from Oslo.

For full strategic analysis, see Stamen Health. For market data, see PHKG Business Models & Market.

One-Line Summary

Stamen Health builds the compliance and data infrastructure layer that EU private hospitals need to meet EHDS requirements — starting from Norway, expanding EU-wide.

The Problem (2026)

EU private hospitals face a compliance deadline they cannot meet alone.

  • The European Health Data Space (EHDS) requires hospitals to make patient data available in standardized formats by 2029-2030
  • EU private hospitals lack the IT resources and expertise to build data curation infrastructure
  • Data is fragmented across legacy EHRs, medical imaging, lab systems, and paper records
  • Hospitals spend significant portions of IT budgets on integration (est. 20-40% — Gartner/McKinsey range, no single clean source for hospitals specifically)
  • Norway has the world's best health data but, per Health Minister Vestre (Apr 2026), isn't exploiting it fast enough

The Solution

An ontology-backed data platform that connects to hospital systems, curates fragmented data into structured health knowledge graphs, and makes it EHDS-compliant.

Core product: Hospital data → SNOMED CT/FHIR structured knowledge graph → EHDS-compliant output

Key technology: Clinical NLP for unstructured text, SNOMED CT coding, FHIR output, PHKG architecture from AIDAVA.

Why Now (2026-2027)

  1. EHDS deadlines create regulatory pull: 2029-2030 is the compliance window. Hospitals must start building infrastructure now.
  2. Norwegian health data opening up: Government explicitly wants data to flow faster (Vestre, Apr 2026). Hospitals need tools to comply.
  3. AI-first development costs have collapsed: Building with AI agents (not just AI features) means a 3-person team can do what 20 did in 2024.
  4. Nordic VC recovering: B2B health data platforms getting funded. Strategic partnerships with hospitals/pharma critical for funding.
  5. First-mover advantage: Few companies are building EHDS-specific compliance infrastructure. Most competitors are either general-purpose data platforms or legacy EHR vendors.

The 2026 Playbook (Lean + Beyond)

The startup landscape has shifted. Building a health data startup in 2026 means:

AI-Native, Not AI-Enhanced

  • Build with AI agents as core team members — HR, legal, customer support, code generation, competitive analysis
  • AI for market validation — simulate customer discovery, generate prototypes, test hypotheses before writing code
  • "Minimum Viable Intelligence" — validate with AI agents first, then build the product
  • Agent-first architecture — design systems where AI agents are primary users alongside humans

Regulatory-First Development

  • Build compliance into core architecture — not as an add-on
  • Parallel regulatory + product tracks — don't wait for product-market fit to start regulatory work
  • Use regulatory sandboxes — available in Nordics, Germany, UK for health tech
  • Pre-submission meetings with authorities — standard practice, not a sign of weakness
  • Modular certification — EHDS compliance can be built incrementally

Speed > Perfection

  • Ship weekly, not quarterly — in health tech this means shipping to pilot hospitals, not the public
  • Hospital partnerships from day one — strategic partnerships > revenue in year 1
  • Defensibility through data governance — not through technology (which anyone can copy)
  • European/global market strategy from day one — EHDS is EU-wide, don't build for Norway only

Team Structure (2026)

  • 3 co-founders: Technical (AI/clinical NLP), Domain (health data/EHDS), Operations (sales/hospital partnerships)
  • Distributed team OK — but quarterly in-person at Oslo office
  • Early regulatory/compliance hire — month 3-4, not year 2
  • Advisory board: EU health policy expert + Norwegian hospital CIO + EHDS implementation consultant

Financial Model (Simplified)

Metric Year 1 Year 2 Year 3
Pilot hospitals 3 15 50
Revenue (ARR) €100K €800K €3M
Team 5 12 25
Funding €500K (grants) €2M (seed) €8M (Series A)
Focus Product + pilots Scale Nordics Expand EU

Revenue model: Per-patient curation fees + subscription platform fees. Hospitals pay €5-15 per patient record for EHDS-compliant structuring.

Non-dilutive funding: Innovation Norway, SkatteFUNN, IPN, Digital Europe EHDS calls — up to €500K in year 1.

Seed round: €2M at month 12-18, post-pilot traction. Nordic health tech VCs (Summa, Northzone, SNOW Ventures).

Series A: €8M at month 24-36, post-Nordic expansion. European health tech VCs (Index, Balderton).

Risks

  1. EHDS delays: Regulation could be pushed back or diluted
  2. Big tech enters: Microsoft/Google build EHDS compliance tools
  3. Hospital inertia: Private hospitals don't prioritize compliance until forced
  4. Regulatory complexity: Each EU country implements EHDS differently
  5. Founder health: 3 co-founders burning out in year 1

12-Month Milestones

Month Milestone
1-3 Founding team + AIDAVA research transfer + Innovation Norway application
4-6 Prototype + first hospital pilot (Norway)
7-9 Second pilot + EHDS regulatory analysis per country
10-12 Seed round + third pilot + Nordic expansion prep

See Also