Coordination & Intelligence Layer
Years of reports, specialists and unanswered questions — reconstructed into one source-linked case both sides can actually use.
Stop being the project manager of your own illness.
One structured case view. Every finding source-linked. Ready before every visit.
Walk into the consultation already briefed.
Years of reports reconstructed into a reviewable case — timeline, gaps, contradictions.
Section 02 · The four surfaces
The same underlying case — rendered for patient, provider, payer and the nexus that holds them together. Each view has its own hook, its own central question, and its own dashboard.
Hook
You should not need a project manager to survive your own illness.
Central question
What is my next step — and what does my body actually say?
One calm surface across appointments, symptoms, specialties and open questions. Built for people who are exhausted, coordinating a life, a diagnosis and often a family.
Coordination load — one week
Calls, portals, insurers, referrals, prescriptions — carried by the patient.
Duration
5 y
Since 2021
Specialists met
6
No lead physician
Confirmed dx
2
ADHD · Vit D
Open tasks
3
1 overdue
Next appointment
Tue · 14 Jul · 09:30
Neurology · Dr. Keller
Inselspital · Room 4.12
Energy — last 12 weeks
Self-report + wearable · flare episodes marked
Symptom duration
Diagnoses
Confirmed
Suspected — under review
You decide what is shared and with whom. Every value shown here comes from your own records — source-linked and reversible.
Missing from work · school · life
ME/CFS, Long COVID, autoimmune, endocrine, neuro-immune — the invisible chronic multisystemic diseases. Patients disappear from work, from school, from the people they love. The system keeps paying. Nobody is coordinating. Nobody is connecting the dots.
2.5 yrs
Missing from the workforce
CHF 300k+
Direct + indirect system cost
5+
Specialties involved, no owner
0
Systems that talk to each other
MVP · Expert Validation Stage
NAVORA reconstructs fragmented medical histories into source-referenced, reviewable clinical case logic — with a timeline, gaps, contradictions and a specialty-directed briefing.
Source-linked
Every statement stays linked to its document, date and review status.
Human-reviewed
No autonomous diagnosis, no treatment recommendation. Clinical review stays central.
Phase 0 ready
A PDF upload is enough to validate usefulness before integration.
A single case · fully documented
Last total compensation of CHF 147,000 in a demanding banking role. Then a chronic multisystemic disease. What follows is what the system spent — and what the patient permanently lost.
Total system cost — one patient
CHF ~343,500
What the patient lost
And this is one case
Multiplied across ME/CFS, Long COVID and the invisible chronic diseases: a silent, structural failure the system pays for every day — while patients disappear from it entirely.
The structural problem
Complex cases rarely fail for lack of information. They fail because findings, lab values, reports, symptoms and course never become readable as one connected clinical trajectory.
CHF 90B+
Annual Swiss health expenditure (~12% GDP)
~10%
Ambulatory physician connectivity
<1%
EPD adoption in the population
Context figures on the care system — not NAVORA outcomes. Sources: Swiss federal health statistics; DigiSanté / Obsan.
Visible burden
Invisible burden
Context breaks at every change of specialty. Each handover reduces the case back to fragments.
The case is explained from scratch again and again. Patients and clinicians reconstruct the same story repeatedly.
More data does not automatically create understanding. Without a layer of meaning, data stays technically available but clinically hard to use.
Synthesis gap
Interoperability moves data. NAVORA focuses on what is still missing afterwards: a reviewable layer of meaning across documents, timelines, specialties and open questions.
Data & systems
NAVORA layer
Clinician
01
Every appointment starts from zero. When did it begin? What was ruled out? Which values were abnormal?
02
Systems document episodes. Diagnoses, services and encounters are stored — but never modelled as a trajectory.
03
Signals emerge over time. Connections, comorbidities and loss of function only become visible longitudinally.
Developed for
NAVORA is designed around Swiss ambulatory and interdisciplinary care — where a single case can touch 5–15 institutions over years, and every specialty inherits a fragment instead of a trajectory.
Practices carrying complex chronic cases across years of reports, labs and specialist letters — where every consult starts by re-reading the file.
Tumor boards, ME/CFS clinics, long-COVID units and rare-disease programs that need a source-linked case reconstruction before the board meets.
Coordination teams reconciling salary continuation, IV coaching, disability, RTW and case management with a single reviewable clinical trajectory.
A read-mode surface for patients and caregivers — timeline, open questions and prepared consultation packages, without diagnostic claims.
Product principle
NAVORA turns documents not into a one-off summary, but into structured clinical objects, a timeline, source tags, review status and reusable case logic.
1
Input
PDFs, reports, labs, notes
2
Ingestion
Extraction, OCR/NLP, date logic
3
Structuring
Clinical objects, not free text
4
Timeline
Trajectory, not an episode list
5
Gap Layer
Gaps, contradictions, open questions
6
Briefing
Reviewable, specialty-directed
Module
Structured case foundation. Source references, clinical objects, review status, auditability, role-based access.
Module
Clinical story engine. Readable case narratives, consultation preparation, specialty-directed briefings.
Module
Longitudinal pathway intelligence. Timeline, turning points, documentation gaps and trajectory views over time.
Product · Focus modules for Physicians & Patients
Core, Klio and Tractus are the first release focus — built for physicians and patients working through complex, multi-year cases. Every output stays linked to the source document, the reviewer and the moment in the trajectory.
Structured case foundation
Turns unstructured reports, PDFs and lab exports into source-referenced clinical objects with review status, roles and audit trail.
Open Core →Clinical story engine
Composes readable, specialty-directed case narratives and consultation briefings — always linked back to source objects.
Open Klio →Longitudinal pathway intelligence
Reconstructs the case as a trajectory across years, specialties and institutions — highlighting turning points and documentation gaps.
Open Tractus →Product · Comparison
Three modules, one pipeline. Each answers a different question about the same case — and each output stays linked back to Core's source objects. Each row highlights the module best positioned to answer that dimension, with a direct link into its page.
Perspective · Beyond the initial focus
Core, Klio and Tractus ship first — because that is where the orientation gap is sharpest. The modules below are the deliberate next arc: continuity, pattern, cohort and coordination layers built on the same source-referenced foundation.
Structured self-observation
Helps patients capture symptoms and observations in an ordered way — translating everyday experience into medically usable structure.
Care between appointments
Connects clinic visits to daily life — flares, stabilisation, exertion limits and warning signals become visible instead of lost between encounters.
Testable patterns, not diagnoses
Surfaces recurring relationships between exertion, symptoms, labs, sleep or medication. It does not diagnose — it makes patterns visible for review.
Anonymised case comparison
Compares similar cases in a privacy-preserving way. Over time this reveals care patterns, risks and treatment effects relevant to research and quality.
Structured cross-actor coordination
Structures collaboration across all involved parties — showing responsibilities, open questions and next steps to reduce coordination chaos for patients and families.
From complexity to concrete tasks
Translates complex situations into concrete everyday tasks — documents, appointments, applications, questions and relief steps that patients today coordinate alone.
Market position
Scribes document conversations. EHR/HIS AI optimises one system. Diagnostic AI detects findings. Research platforms analyse cohorts. NAVORA reconstructs the complex case across time, sources and specialties.
Scribes document the visit.
NAVORA reconstructs the case.
EHR AI improves one system.
NAVORA connects what no single system contains.
Diagnostic AI detects findings.
NAVORA makes the trajectory reviewable.
Research platforms analyse cohorts.
NAVORA prepares the next clinical review.
Competitive edge · AWS landscape analysis
The AWS competitive landscape confirms it: scribes, EHR AI, diagnostic AI and research platforms each solve one slice. None reconstruct the complex ambulatory case across years, specialties and institutions.
Every synthesised statement stays linked to the exact document, section and date.
Years of reports, labs and letters composed into one reviewable trajectory.
V0 outputs orientation only — never autonomous diagnosis or treatment.
Technical foundation
NAVORA runs on AWS's healthcare-eligible services in the EU, combined with a Swiss hosting layer for identifying data. LLM calls are wrapped in guardrails and audit trail; nothing leaves the controlled boundary without a source tag.
FHIR R4 clinical data lake — EU (Frankfurt) region.
HIPAA-eligible medical NLP for entity, RxNorm and ICD-10 extraction.
Controlled LLM orchestration with guardrails and audit trail.
Isolated compute enclaves, customer-managed keys, envelope encryption.
EU / CH
Data residency for clinical content
AES-256
Encryption at rest & in transit (TLS 1.3)
Zero-retention
LLM prompts and outputs, no training on client data
Trust architecture
NAVORA V0 is deliberately narrow: case structuring, source linking, timeline, gap marking and a review flow. No autonomous diagnosis. No treatment recommendation. No triage.
Document, section, date, author/institution, extraction confidence and review status stay visible.
Gaps and contradictions are not smoothed over, but marked as reviewable orientation.
The software supports the decision context. Responsibility stays with the physician.
Data minimisation, purpose limitation, pseudonymisation, visible consent logic — as baseline.
Patient, physician, caregiver and admin receive different rights, permissions and audit trails.
V0 avoids decision-support wording and stays limited to reviewable orientation.
From the product — ingestion path
NAVORA starts with a drag & drop. Structured HL7 FHIR and HIN connectivity are added only when a pilot has proven the value is real.
Phase 0 · today
Drag & drop
No integration required. The patient or practice provides source documents.
Core
Structured objects
Every object is source-linked — document, section, date, author.
Phase 1 · pilot integration
Secure API · HL7 FHIR
When the pilot demands it — never before real usefulness is proven.
Data protection & security
NAVORA is designed against Swiss and European healthcare requirements from day one: identity via HIN and GLN, clinical hosting in CH / EU, and a regulatory posture that keeps V0 firmly outside MDR-regulated decision support.
Purpose limitation, data minimisation, right of access and deletion are enforced at the data model — not the interface.
Identifying data hosted in a Swiss ISO 27001 Tier III data centre; clinical processing in AWS EU regions.
Physician authentication via HIN; providers identified by GLN to align with the Swiss e-health ecosystem.
AES-256 at rest, TLS 1.3 in transit, envelope encryption with customer-managed keys via AWS KMS.
Every access, extraction and review action is logged, timestamped and attributable to a role.
Patient consent is a first-class object — scoped by purpose, revocable, and visible to every role.
Section 03 · Validation KPIs
Ten metrics grouped into four layers. Each KPI carries its collection method and target corridor — the backbone of Phase 0 with our pilot partners.
Value at the case level — measured from the clinician's perspective.
Median seconds to first workable case hypothesis
Average handling time per case
Likert 1–7 after each case
Does NAVORA back up what it shows — and catch what is missing?
% of statements with a traceable, valid source
% of clinically relevant gaps correctly flagged
Average confirmed contradictions per 10 cases
Early indicators of willingness to pay and to continue.
% of pilot users who voluntarily start another case
Van Westendorp price-acceptance range
% of sites signing an LOI for Phase 1
Clarity for patients and caregivers (optional read-mode).
Comprehension score 1–5 after read-mode
Phase 0 validation
The first validation needs no deep EHR, HIS or FHIR integration. A PDF upload is enough to test whether NAVORA makes complex cases faster to understand, easier to review and more clinically connectable.
84
Day validation window
3
Clinical settings
CHF 1,500
MRR target
V0
Manual review / wizard-of-oz
Binary go / no-go criteria — targets for validation, not results achieved.
1
Upload / Export
Patient or practice provides PDFs, reports and selected longitudinal records.
2
Manual + assisted structuring
Documents become clinical objects, timeline entries, source tags and open questions.
3
Expert review
Clinicians evaluate usefulness, correctness, understandability and review effort.
4
Pilot decision
Continue only if real cases create measurable willingness to keep using NAVORA.
Phase 0 · Reference
The validation KPIs are a fixed part of the pilot agreement with our first clinical partners. Results are reviewed together at the end of each 4-week cycle.
For validation partners
NAVORA is looking for clinical sparring partners, specialists and healthcare operators who will critically pressure-test complex longitudinal cases, MVP limits, regulatory edges and pilot logic.
For clinical, technical, research or ecosystem conversations. We respond to thoughtful, relevant introductions.
Primary interest