Stamen Health Executive Summary

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. For AIDAVA research foundation, see AIDAVA.

What This Is

Stamen Health is a planned startup that would take the research architecture from AIDAVA (EU Horizon Europe, €7.7M, 2022-2026) and turn it into a commercial product for EU private hospitals that need to comply with EHDS (European Health Data Space).

The core product: connect to hospital systems, curate fragmented data (structured + unstructured) into structured knowledge graphs using SNOMED CT and FHIR, and produce EHDS-compliant output.

What AIDAVA actually proved: Automated curation of 45% of documents. 20 minutes per document. Tested in 3 languages (Dutch, German, Estonian) across breast cancer and cardiovascular use cases. Usability rated "good" by pilot users, but AI explanations rated "suboptimal." Ends August 2026 as a research prototype — not a commercial product.

What Stamen would need to prove: That this architecture can be production-hardened, sold to private hospitals at commercial scale, and maintained as a reliable compliance tool. None of this has been done yet.

The Opportunity — What's Real

EHDS is real, but distant. The regulation requires standardized health data availability by 2029-2030. National transposition is happening now. Hospitals will need tools — but the spending wave hasn't started yet. This is a build-now-for-2028-revenue bet, not a 2026 revenue story.

Norwegian data advantage is real, but underutilized. Health Minister Vestre said it plainly (April 2026): Norway has the data but isn't using it. Helsedataservice applications up 30% in 2025. Government wants data to flow faster. But "wanting" and "having infrastructure" are different things.

No one does the full pipeline commercially. The competitive analysis shows companies doing pieces: PicnicHealth (US, data collection), Better (FHIR), Averbis (German NLP), Healx (knowledge graphs). Nobody combines ingestion → NLP → KG → FAIRification → multi-stakeholder reuse as a commercial product. But "nobody does it" can mean either "opportunity" or "there's a reason."

Private hospitals are an underserved market. Public hospitals in the Nordics have national EHR systems (DIPS, Metavision). Private hospitals lack equivalent infrastructure and will feel EHDS pressure first — they need to comply without government IT departments.

The Hard Parts — What Will Be Difficult

Product

45% automation is not enough. Hospitals won't pay for a tool that only automates half their data curation. The product needs 80%+ automation to be commercially viable. Getting from 45% to 80% is a multi-year engineering problem, not a feature request.
AIDAVA is a research prototype. It was built by 13-14 academic partners across 9 countries. Hardening it for production — reliability, error handling, hospital IT integration, data privacy compliance — is a completely different engineering challenge than the research.
Clinical NLP across languages. AIDAVA's NLP works in Dutch, German, Estonian. Norwegian clinical text has its own quirks (bokmål/nynorsk, medical abbreviations, dialect in notes). Each new language is significant work.
SNOMED CT coding at scale. Automated SNOMED CT coding from unstructured text is still an open research problem. AIDAVA's 45% rate reflects this.

Sales

Hospitals are slow buyers. Enterprise sales cycles in healthcare are 6-18 months. Private hospitals have smaller IT teams and less budget than public systems. The first 3 customers will take 12+ months to close.
No existing budget line. EHDS compliance tools don't have a named budget category yet. Hospitals don't have a "EHDS compliance software" line item. You're creating demand, not capturing it.
Competition will come. Better (Slovenia), InterSystems ($5B), IQVIA ($35B), and potentially Microsoft/Google will build EHDS compliance tools. The window for a startup is narrow — probably 2026-2028 before big players move.

Team

Finding a clinical NLP / knowledge graph CTO is extremely hard. The intersection of SNOMED CT expertise, production ML engineering, and health data privacy is tiny. In Norway, it's close to zero. This role likely needs to come from the AIDAVA network (Maastricht, Tartu, etc.) — meaning relocation or remote co-founder.
COO with hospital sales experience. The plan calls for a Norwegian COO. Someone who has sold to Nordic hospitals, understands procurement, and can navigate hospital politics. These people exist but they're expensive and already employed.
Three co-founders with different skill sets. Clinical NLP, hospital sales, and operations. Getting three people aligned on vision, equity split, and working style is hard. Most startups fail on co-founder dynamics, not technology.

Funding

€25K/month founder salaries will be challenged. Innovation Norway early-stage approvals are 60-90K NOK/month. SkatteFUNN has fewer restrictions but is a tax credit, not cash. Plan for 70K NOK/month per founder in year 1.
Seed round timing. The realistic path: grants first (€300-500K from Innovation Norway + SkatteFUNN), then seed (€2-5M) at month 12-18 after proving the product with 2-3 pilot hospitals. Don't raise seed before having hospital traction.
EHDS VC interest is real but early. Nordic VCs are interested in health data platforms (Tandem Health raised €42.6M from Kinnevik). But they want product traction, not just a research prototype.

Realistic 12-Month Plan

Month	What	What This Actually Means
1-3	Founding team + AIDAVA license	Co-founders signed, equity split agreed, AIDAVA technology transfer/licensing negotiated with Maastricht University. Innovation Norway application submitted.
4-6	Architecture + first conversation	Take AIDAVA's research code, decide what to rebuild vs. reuse. Have conversations with 5-10 private hospitals. NOT a pilot — just listening to what they actually need.
7-9	Prototype + pilot agreement	Working prototype that does ONE thing well: e.g., curating radiology reports into FHIR. Sign pilot agreement with 1 Norwegian private hospital.
10-12	Pilot data + seed prep	Run the pilot. Measure: automation rate, time savings, hospital satisfaction. Use pilot data for seed deck. Apply for IPN/SkatteFUNN for year 2 R&D.

Year 1 budget: €300-500K total. Innovation Norway Innovation Contract (~€160K), SkatteFUNN (19% tax credit on R&D), founder contributions, possibly small angel round.

Year 1 team: 3 co-founders + 1 engineer (contract or part-time).

Year 1 goal: NOT revenue. Year 1 goal is: working prototype + first pilot agreement + seed deck with traction data.

Financial Model (Realistic)

Metric	Year 1	Year 2	Year 3
Pilots/Customers	1 pilot	2-3 customers	5-8 customers
Revenue	€0	€100-200K	€500K-1M
Team	3-4	6-8	10-15
Funding source	Grants + angel	Seed €2-5M	Series A €5-10M
Burn rate/month	€30-40K	€80-120K	€200-300K

Revenue model: Per-patient curation fee (€5-15 per record) + platform subscription (€2-5K/month per hospital). Year 1 is zero revenue — this is a grant-funded build year.

Break-even estimate: Year 3-4, with 10+ paying hospitals. Earlier if there's a strong licensing/partnership deal with a hospital group.

Why It Could Work

Timing is right: EHDS deadlines (2029-2030) mean hospitals need to start building infrastructure now. First movers who can sell EHDS compliance have a 2-3 year window before big tech enters.
Norway is the right base: Government wants data to flow faster, has strong data infrastructure, and the trust advantage for EU expansion (Norway = GDPR-conscious, not US big tech).
AIDAVA de-risks the technology: 45% automation with a research prototype across 3 languages. The architecture works — the question is engineering, not science.
No full-stack competitor exists: Companies do pieces. Nobody offers the complete ingestion → curation → compliance → multi-stakeholder reuse pipeline.
Non-dilutive funding is available: €300-500K in Norwegian grants is realistic for year 1. This funds the build phase without giving up equity.

Why It Could Fail

EHDS gets delayed or diluted: Regulatory timelines slip. Hospitals don't feel urgency until 2028.
45% → 80% is a hard engineering problem: The automation gap closes too slowly. Product isn't good enough for commercial use by year 2.
Co-founder team doesn't hold: Clinical NLP expert, hospital sales operator, and operations lead don't gel. One leaves.
Big tech moves faster than expected: Microsoft, Google, or InterSystems build EHDS compliance tools. Startup window closes.
Hospitals don't buy from startups: Private hospitals prefer established vendors. Trust takes too long to build.
AIDAVA licensing doesn't work out: Maastricht University or other partners make licensing terms unfavorable.

What Actually Matters in Year 1

Ship one thing that works. Not a full platform — one vertical (e.g., radiology reports → FHIR). Make it reliable.
Get one hospital to pay (or commit to pay).' Even a symbolic €5K pilot contract proves someone wants this.
Don't raise too early. Grants fund year 1. Raise seed only when you have traction data.
Find the CTO first. The technical co-founder is the hardest hire and the most important one. Everything else follows.
Don't build for Norway only. EHDS is EU-wide. Every feature should be built for cross-border use from day one.