22 KiB
From Data to Information: How inou Connects the Dots
Draft — Iaso, March 15, 2026 Based on real dossier data from the inou family & friends network
The Core Idea
A number alone is not information. It becomes information the moment it connects to something else — another number, a gene, a symptom, an image, a supplement, a timeline.
That connection is what inou makes possible. Not by analyzing anything — inou doesn't analyze. By giving your AI the full picture: labs, genome, imaging, vitals, history. All of it in one place, structured, retrievable, ready to reason about.
This document shows what that looks like in practice, using real (anonymized) examples from the inou family and friends network. These are not hypotheticals. The numbers below are real.
Example 1: TSH + Iron Saturation + Clinical Context
Dossier: Sophia, female, age 7 at time of data
The numbers in isolation:
- TSH: 5.94 mcIU/mL (Aug 2022) — borderline high, upper limit of normal ~5.0 in children
- Iron saturation: 15% (Aug 2022) — low-normal; functional iron deficiency starts below 20%
- Ferritin: 43 ng/mL (Jul 2023) — adequate by most lab ranges
- CRP: 0.5 mg/dL (Aug 2022) — mildly elevated
What each specialist sees in their lane:
- Endocrinologist: TSH is "borderline, let's watch it"
- Hematologist: iron saturation is "low-normal, not anemic"
- Pediatrician: CRP is "slightly elevated, probably viral"
What the connected picture shows: Iron deficiency — even subclinical — is a known driver of elevated TSH. The thyroid needs iron for thyroid peroxidase activity. When iron saturation drops below ~20%, TPO function is impaired, TSH rises compensatorily even when T4 remains in range (T4 was 10.4 mcg/dL — technically normal).
The CRP suggests concurrent inflammation, which itself suppresses iron bioavailability by upregulating hepcidin. So the sequence may be: inflammation → functional iron sequestration → impaired thyroid function → elevated TSH. Three separate labs, three separate specialists, one underlying mechanism.
The actionable information: The TSH is probably not primary thyroid disease. It's a downstream signal of functional iron deficiency in an inflammatory context. That changes the intervention.
What inou enables: An AI connected to Sophia's dossier can see the TSH, the iron studies, the CRP, and the timeline — all at once. It can ask the right follow-up questions. It can flag that this pattern warrants iron optimization before thyroid intervention.
Example 2: Extremely Elevated Transaminases + Procalcitonin Spike
Dossier: Sophia, female, age 5 at time of data
The numbers:
- ALT: 158 IU/L (May 2022) — severely elevated (normal <35)
- AST: 169 IU/L (May 2022) — severely elevated (normal <40)
- Alkaline Phosphatase: 299 IU/L (May 2022) — elevated
- Procalcitonin: 15.18 ng/mL (May 2022) — markedly elevated (sepsis threshold >2.0)
- PT: 16.7 seconds — mildly prolonged
- Glucose: 190 mg/dL — significantly elevated for age
- WBC: 13.58 Th/cumm — elevated
- Lymphocytes Absolute: 9.9 Th/cuMM — extremely elevated (lymphocytosis)
The contextual data also present:
- CT Head, CT Spine Cervical, CT Abdomen/Pelvis: all May 2022
- Multiple serial chest X-rays (May 2022)
- MRI Brain W/WO Contrast: May 2022
- MRI Complete Spine W/WO Contrast: May 2022
- Echocardiogram markers (MV ANN D, TV ANN D)
What the connected picture shows: This is an acute critical illness. The combination of a procalcitonin of 15.18 (severe sepsis range), massively elevated transaminases suggesting hepatic involvement, lymphocytosis, elevated glucose, and a prolonged PT — alongside imaging of head, spine, chest, and abdomen — represents a child in serious multisystem distress. The full imaging workup happening simultaneously confirms this wasn't routine.
The actionable information: No single lab in isolation tells this story. The procalcitonin alone might be dismissed as a lab artifact. The liver enzymes alone might suggest viral hepatitis. But together with the imaging timeline, the glucose, the lymphocyte count, and the coagulation data — an AI with access to all of this can reconstruct what was happening and flag that this pattern needs to be part of Sophia's permanent medical narrative, not buried in a hospital encounter that no future specialist will see.
What inou enables: Every future provider who sees Sophia can give her AI access to this data. The AI can present a coherent narrative of her acute illness history. No more "I think she had something serious in 2022 but I don't have the records."
Example 3: D-Dimer Elevation + Chronic Inflammation Signal
Dossier: Sophia, female, Dec 2024
The numbers:
- D-Dimer: 1.15 ug/mL FEU (Nov 2024) — elevated (normal <0.5)
- ESR: 8 mm/hr (Jun 2024) — normal
- Cortisol: 8.6 mcg/dL (Apr 2024) — low-normal morning cortisol (optimal >15 AM)
What the connected picture shows: D-dimer is a fibrin degradation product — it elevates with clotting activity, inflammation, or both. ESR is normal, which argues against major systemic inflammation. But the low-normal cortisol is interesting: cortisol has anti-inflammatory and anticoagulant properties. Chronically low cortisol (or a blunted cortisol response) can contribute to hypercoagulable states.
This is a subtle pattern. Nothing here would trigger a clinical alarm in isolation. But an AI that can see the D-dimer, the cortisol, and the patient's broader history — including the 2022 acute illness — can ask: is there an ongoing low-grade inflammatory or coagulation issue that the normal ESR is missing?
What inou enables: The longitudinal view. Not just "D-dimer is elevated today" but "D-dimer is elevated, cortisol has trended low-normal across three measurements, and there's a history of critical illness in 2022." That's a different conversation with a hematologist.
Example 4: Lyme Borreliosis + Candida Overgrowth — The Co-infection Picture
Dossier: Mikhail, male, age 76
The numbers:
- Blood Parasites: POSITIVE (Oct 2025)
- Isolate: Borrelia — confirmed Lyme borreliosis
- Yeast Cells: Candida albicans 4+ (Oct 2025) — significant fungal load in urine
- Urine Appearance: HAZY — consistent with infection/inflammation
What each specialist sees:
- Infectious disease: Borrelia positive — treat with doxycycline
- Urologist: Candida 4+ — treat with fluconazole
- No one connects them.
What the connected picture shows: Borrelia burgdorferi infection triggers significant immune dysregulation. Chronic Lyme disease is associated with impaired Th1 immunity and compensatory Th2 dominance — exactly the immune profile that creates susceptibility to opportunistic fungal overgrowth. The Candida isn't coincidental. It may be a downstream consequence of the immune suppression caused by persistent Borrelia.
Treating each independently — antibiotics for Lyme, antifungals for Candida — without understanding the relationship misses the mechanism. Antibiotics will further disrupt the gut microbiome, potentially worsening Candida. The treatment sequence and selection matter, and they depend on understanding the connection.
The actionable information: Mikhail has a co-infection pattern with an immune-dysregulation mechanism. An AI connected to both the Borrelia lab result and the Candida finding — plus his age (76), vitals, and any genome data available — can provide context that neither specialist will spontaneously generate.
What inou enables: Mikhail (Sophia's grandfather, 76 years old) can share his inou dossier with any provider, anywhere. The AI connected to it can present the co-infection picture without Mikhail having to explain it from memory or carry paper results between clinics.
Example 5: Body Composition + Metabolic Risk — The Scale Doesn't Know Everything
Dossier: Johan, male, age 60
The numbers:
- Weight: 93.6–94.7 kg (recent range, Renpho smart scale)
- BMI: 26.0–26.2 — overweight range, barely
- Body Fat: 22.7–23.1%
- Visceral Fat score (Renpho index): tracked longitudinally
What BMI alone shows: "Slightly overweight." 26.2 BMI. Many physicians would stop there.
What the connected picture shows: Body fat percentage of ~23% in a 60-year-old male sits in the "acceptable" range but approaching the upper bound. More important than the static number is the trend and the composition breakdown — Renpho tracks visceral fat (the metabolically active fat that drives insulin resistance and cardiovascular risk) separately from subcutaneous fat (less dangerous). A BMI of 26 with high visceral fat is a very different metabolic picture than BMI 26 with low visceral fat and high muscle mass.
inou captures all Renpho metrics — not just weight. An AI connected to this longitudinal data can track whether body composition is improving even when scale weight is stable, and flag when visceral fat is trending in a dangerous direction regardless of BMI.
What inou enables: The conversation shifts from "your BMI is fine" to "your visceral fat index has increased over the past six weeks even though your weight is stable — let's talk about what's driving that."
Example 6: Sophia's Omega Profile + Brain Inflammation
Dossier: Sophia, female, age 8 (Jul 2025)
The numbers:
- OmegaCheck (EPA+DPA+DHA): 9.9% by weight — excellent (>8% is optimal)
- Arachidonic Acid/EPA Ratio: 4.4 — acceptable (optimal <6, inflammatory when >12)
- Vitamin B1 (Thiamine): 19.3 nmol/L — low (optimal >70 nmol/L, deficiency <66)
- Methylmalonic Acid: 57 nmol/L — normal (rules out functional B12 deficiency)
- Homocysteine: 6.85 umol/L — excellent (optimal <8)
What the connected picture shows: The omega profile is actually good. But the thiamine level is strikingly low — 19.3 nmol/L against an optimal of >70 is a 73% deficit. This is not a marginal deficiency. Thiamine (B1) is essential for neurological function: it's a cofactor for pyruvate dehydrogenase and alpha-ketoglutarate dehydrogenase, both critical for cerebral energy metabolism. Thiamine deficiency is associated with neurological symptoms, cognitive difficulties, and autonomic dysfunction.
The contrast is important: the omega-3 profile is optimized (someone is paying attention to that), but thiamine has been missed. This suggests targeted supplementation has occurred based on visible guidance, but thiamine — less commonly discussed — has slipped through.
The actionable information: A child with neurological complexity and a thiamine level of 19.3 nmol/L needs thiamine supplementation urgently. This is specific, measurable, and correctable. But no single specialist ordered this panel in the context of everything else — it took a comprehensive metabolic assessment.
What inou enables: When the AI has access to the full nutrition panel alongside the neurological history and imaging, it can surface the thiamine finding in context. Not "B1 is low" but "B1 is critically low in a patient with neurological complexity and known brain imaging findings — this is actionable."
What This Means for inou
These six examples come from three dossiers. None of them required AI to do anything inou couldn't already see. What they required was connection — across categories, across time, across what different specialists know.
That connection is infrastructure. That infrastructure is inou.
Tasks & Opportunities
Website Additions
1. "Data → Information" landing section
A new section on the homepage or a dedicated /why-inou page that shows 2–3 of these examples in simplified form. Not technical. Lead with the patient experience: "Your doctor said your thyroid is borderline. Your labs also showed low iron saturation. An AI connected to both can explain the relationship."
Owner: Johan / Iaso for copy
2. "What your AI can see" feature page A visual breakdown of each data category (labs, imaging, genome, vitals) with concrete examples of what an AI can reason about when it has access. Side-by-side: "What you told your doctor" vs "What your AI can see." Owner: Iaso for copy, James for design spec
3. Condition-specific landing pages SEO-targeted pages for specific patient communities: Lyme disease, thyroid disorders, pediatric neurology, metabolic health. Each page shows the multi-category data pattern relevant to that condition and how inou makes it accessible to AI. These are discoverable by patients actively researching their conditions. Owner: Iaso for copy
4. "The specialist problem" explainer A short, patient-facing piece explaining why specialists can't see across lanes — not because they're bad doctors, but because the system isn't designed for it. Ends with: "inou is the structure that was missing." Can live as a blog post, an FAQ item, or a dedicated page. Owner: Iaso
Tweets / X Content
Thread 1: The TSH thread
"Your TSH came back borderline. Your doctor said 'let's watch it.' But your iron saturation was 15%. And your CRP was elevated. Iron deficiency impairs thyroid peroxidase. Your TSH might not be a thyroid problem. It might be a downstream signal of functional iron deficiency. Three labs. Three specialists. One mechanism nobody connected. That's the structural problem. inou is the structure that was missing."
Thread 2: The D-Dimer thread
"D-Dimer elevated. Doctor said 'probably nothing, let's recheck.' But your morning cortisol has been low-normal for a year. Cortisol is anti-inflammatory and anticoagulant. A blunted cortisol response can contribute to hypercoagulable states. Nobody's looking at both. Not because they don't care. Because the data lives in different places. inou puts it in one place."
Thread 3: The scale thread
"BMI 26. Doctor said 'you're fine.' But BMI doesn't know the difference between fat and muscle. It doesn't know where the fat lives. Visceral fat — the fat around your organs — drives insulin resistance and cardiovascular risk. Your scale might. Your Renpho tracks it. inou captures it. Your AI can trend it. 'You're fine' is not information. The trend is."
Thread 4: The omega/thiamine thread
"Omega-3 index: excellent. Someone is paying attention. Thiamine: 19.3 nmol/L. Optimal is >70. That's a 73% deficit. Thiamine runs your brain's energy metabolism. It wasn't checked. It wasn't connected to anything else. inou doesn't miss it. It's just a number — until it's connected to everything else."
Standalone: Lyme + Candida
"Lyme disease. Treated with antibiotics. Three months later: Candida 4+. Coincidence? Maybe. Or: Borrelia suppresses Th1 immunity. Th1 suppression enables fungal overgrowth. Antibiotics further disrupt the microbiome. Two diagnoses. One mechanism. Zero connection in the chart. That's what inou is for."
Articles (External)
1. "The Specialist Paradox" — Medium/Substack Long-form exploration of why specialist medicine produces fragmented care by design. Cites mechanism (cognitive load, lane specialization, no shared data standard). Ends with inou as infrastructure, not solution. Target: health-interested general audience. Author: Iaso
2. "What Your AI Needs to Give Good Medical Advice" — towards data science / AI-focused Technical-ish piece on why LLM medical reasoning fails without structured data access. Covers MCP, the role of a health data vault, and what "context" actually means in clinical AI. Target: developers, AI-interested clinicians. Author: Johan/Iaso
3. "Iron, Thyroid, and the Problem With Normal Ranges" — patient advocacy publication Deeper dive into the TSH/iron connection with citations. Aimed at thyroid patient communities (large, engaged, underserved). Not an inou ad — an evidence-based piece that mentions inou as a tool at the end. Author: Iaso, needs citation review by Johan
4. "Thiamine Deficiency: The Neurological Missing Link" — pediatric neurology patient community Evidence-based piece on thiamine's role in pediatric neurological function, why it's underdiagnosed, and what a comprehensive metabolic panel reveals. Target: parents of children with neurological complexity. Author: Iaso
5. EkoUNIMED / Global Health angle — LinkedIn or health equity publication The story of inou's partnership with EkoUNIMED as a case study in health data equity. Why fragmentation is worse in low-resource settings. Why the next generation of African physicians need to understand connected health data from day one. Author: Iaso / Johan
New Features
1. Cross-category alert engine When an AI (via MCP) queries a dossier, it currently gets data on request. A future feature: a structured "alert" layer that surfaces pre-computed cross-category patterns — e.g., "TSH elevated + iron saturation <20% — possible functional iron-thyroid interaction." This is not diagnosis. It's a prompt to the AI to look deeper. Note: This is an AI-assist feature, not an inou analysis feature. inou surfaces the flag; the AI reasons about it.
2. Longitudinal trend view in API response
Currently labs return the latest value. For trend-dependent interpretation (cortisol, D-dimer, inflammatory markers, body composition), the API should optionally return the last N values with timestamps. Enables AI to reason about trajectory, not just snapshot.
Spec: add history=N param to /api/labs/results
3. Nutritional gap analysis scaffold A structured way to store micronutrient panels (thiamine, B6, zinc, copper, omega profile) and surface them as a category alongside standard labs. Currently they fall into the generic lab bucket. A dedicated nutritional category with reference ranges and trend tracking would enable more targeted AI reasoning.
4. Genome × Lab correlation prompts In the MCP instructions (currently in place), add explicit guidance for the AI to cross-reference genome variants with lab findings. E.g., if MTHFR C677T is homozygous and homocysteine is available, surface the relationship. This is prompt engineering, not a new feature — but it needs to be systematic.
5. Family dossier clustering When multiple family members are in the same account (Johan, Tanya, Sophia), enable the AI to reason across family members for heritable patterns. "Sophia has low thiamine and neurological complexity. Johan's metabolic profile shows X. Is there a familial pattern worth investigating?" Requires explicit consent flag and RBAC.
6. Tracker × Lab correlation Sophia has a tracker entry. If a patient logs "fatigue" in the tracker and their recent labs show low thiamine and borderline TSH — the AI should be able to connect symptom entries to lab findings temporally. Currently tracker and lab live in separate categories with no bridge.
Defects / Technical Issues
1. MCP backdoor scope
Current backdoor (192.168.0.0/22 LAN) gives access only to Johan's dossier (6e4e8192881a7494). When an AI on the LAN calls list_dossiers, it sees all dossiers — but list_entries only works for Johan's. This is inconsistent and confusing. Either:
- Scope the backdoor to all dossiers (if intentional for local agent use), or
- Filter
list_dossiersto only return Johan's dossier when accessed via backdoor Priority: Medium — current behavior is a UX defect, not a security issue
2. Genome API not accessible on port 8082
/api/genome returns 404 on port 8082 (API service). It appears to only be available via the portal (port 1080), but the portal requires auth that the LAN backdoor doesn't provide for non-MCP endpoints. This means genome data is inaccessible to LAN agents via REST. Either expose genome on 8082 or extend the LAN bypass to the portal REST endpoints.
Priority: Medium
3. Lab endpoint local=true bypass on 8082
The ?local=true parameter on the API service (http://192.168.1.253:8082/api/labs/) bypasses auth for Johan's dossier, but returns null results for other dossiers (e.g., Mikhail). This appears inconsistent — Mikhail's lab data exists (confirmed via list_categories) but doesn't return via local=true. Investigate whether local=true is scoped to Johan's dossier or is a bug.
Priority: Medium
4. MCP list_entries with category filter
When calling list_entries with a category filter other than the category that has a root entry (e.g., category=lab when the only root is vital), it returns null instead of an empty array or a navigable root. This makes it hard for an AI to know whether there's no data or whether it's navigating incorrectly. Should return [] with a hint.
Priority: Low — UX polish
5. Lab names inconsistency (Johan vs Mikhail)
Johan and Mikhail have the same lab tests (urinalysis) but with slightly different naming conventions (Isolate vs ISOLATE, Bacteria with different capitalization). This means cross-dossier queries won't normalize correctly. Lab name normalization should be applied at import time.
Priority: Low
Other Ideas
1. inou Health Letter A monthly email (or Substack) written in Iaso's voice: one clinical story, one mechanism explained, one data pattern that connects across specialties. Not a product newsletter. A health communication piece that builds trust and authority. inou mentioned only in the footer.
2. "Ask your AI" prompt library A public page on inou.com with example prompts patients can use with Claude/Grok once connected to their inou data. "Ask your AI: what does my iron saturation tell you about my thyroid function?" Lowers the barrier to actually using the tool and demonstrates the data-to-information transformation concretely.
3. Clinician outreach Target physician communities (not hospitals — too slow) who already think in systems: functional medicine, integrative oncology, complex pediatric neurology. inou is a natural fit for clinicians who already want to see the whole patient. A one-page PDF showing the data-to-information examples above, framed as "your patient can now share their complete picture with you."
4. Partnership with specialty labs Labs like Quest, LabCorp, and specialty nutrition labs (Genova, Great Plains) are not in inou yet. An import integration — similar to the genome import — would dramatically expand the value of the platform for patients who already have comprehensive lab panels done privately.
5. Podcast / audio content Short (5–8 min) audio episodes in Iaso's voice: "The Connection Nobody Made." One episode per data pattern. Evidence-based, patient-side, no jargon. Distributable on Spotify/Apple Podcasts. Positions inou as a trusted voice in evidence-based integrative health communication.