The Longitudinal Health Profile
The LHP is the canonical, user-owned context layer that turns raw events into a coherent model of the whole person. It is not a static profile — it is a living model that stays accurate as you change.
Sources
labs, wearables, notes, medication
Longitudinal Health Profile
provenance, confidence, permissions
Surfaces
apps, agents, care preparation
What the profile holds
Every entry is interpreted in relation to everything before it. The profile preserves meaning over time, not just data points.
From raw events to a living model
A few entries from different sources become a coherent trajectory — each event keeps its source, confidence, and unresolved threads, so agents can reason over it without losing the thread.
Timeline
Apr 2026- 2 AprLabsUnresolved
Ferritin 28 ng/mL — below reference range
- 9 AprWearable
Resting heart rate drifted 58 → 64 bpm over a week
- 14 AprNote
“Afternoon fatigue, hard to focus after lunch.”
- 16 AprMedication
Started iron supplement, 65 mg daily
- 30 AprWearableChanged
Sleep efficiency 78% — up from 71%
Event
UnresolvedFerritin 28 ng/mL
Below reference range
- Source
- Lab import · MedLab
- Recorded
- 2 Apr 2026, 09:14
- Confidence
- High
- Linked goal
- Resolve persistent fatigue
- Follow-up
- Recheck in 8 weeks
Nutrition agent
Suggest · level 3Low ferritin on 2 Apr alongside the afternoon-fatigue note from 14 Apr is consistent with low iron. Consider rechecking ferritin in 8 weeks and taking the supplement with vitamin C to aid absorption.
Reading: 2 events · 1 note · 1 goal
Four surfaces, one core loop
Different views into the same profile. Each serves a distinct job — and all strengthen the same underlying model.
Input surface
CaptureA chat-first, voice-capable, quick-log interface — a translation layer from messy human experience into structured longitudinal context. Not just chat: a way to record events, symptoms, behaviours, goals, and reflections.
Profile surface
UnderstandA human-readable view of your current health model: timeline, goals, changes, patterns, uncertainty, and agent interpretations. It helps you see what the system believes — and why.
Agent surface
ReasonA modular interface where specialist agents explain, suggest, plan, follow up, and coordinate around your profile. It feels unified, but stays inspectable.
Developer surface
InspectA technical view into schema behaviour, ingestion quality, provenance, confidence, and agent outputs — so the system never becomes a black box.
The conversation is a doorway. The profile is the house.
A chatbot answers in the moment and forgets. Health Core maintains a coherent model of your health trajectory, so every interaction builds on the last.
You can talk, log, or import — but the value isn't the message. It's the durable, inspectable model underneath that agents and clinicians can rely on over time.
What we won't compromise
These commitments decide what gets built. They set expectations for early partners — and keep the product honest as it grows.
Coherence over features
New data is interpreted against everything before it. We protect one coherent model rather than shipping disconnected features.
Uncertainty is preserved, never buried
Confidence, provenance, ambiguity, and change are first-class. The system never presents inference as fact when it isn't justified.
You stay in control
You can inspect, correct, approve, restrict, export, and delete what the model holds. The profile makes you more capable, not more dependent.
One shared context, no separate truths
Every agent reads and writes the same profile. We won't let separate agents create separate versions of you.
Chat is an interface, not the product
Conversation is one way in. The durable value is the inspectable longitudinal model underneath.
Infrastructure, not lock-in
Decisions favour portability and open-core compatibility over locking your health context into a single app or device.
These flow from the principles behind Health Core. Read the manifesto → or see how we handle trust and control →
Autonomy earned through checkpoints
Agents climb an eight-rung ladder, but never jump to higher autonomy without the safety, consent, auditability, and confidence to justify it.
Explain · Interpret · Suggest
Make the profile legible — summarise what it holds, surface patterns and gaps, and recommend next steps for you to consider.
Plan · Follow up · Coordinate
Build cross-domain plans, remember unresolved threads, and hand context between specialist agents while preserving coherence.
Act with consent · Support care
Trigger reminders, update records, or prepare exports — only within approved permissions, bridging daily life to clinical care.
Built on stable primitives
Health Core is longitudinal infrastructure, not a bag of features. Every capability maps back to a small set of durable primitives — so each event carries its own source, confidence, and links.
Longitudinal by default, provenance-first, timeline-aware, uncertainty-aware, user-correctable, and open-core compatible. See the full primitive vocabulary and developer model →
{
"id": "evt_8f3a…",
"type": "observation",
"observation": { "metric": "ferritin", "value": 28, "unit": "ng/mL" },
"timestamp": "2026-04-02T09:14:00+10:00",
"source": { "kind": "lab_import", "name": "MedLab" },
"provenance": "imported",
"confidence": 0.94,
"links": { "goal": "goal_resolve_fatigue", "follow_up": "fu_recheck_8w" }
}Start building your longitudinal profile.
Tell us how you'd use Health Core and we'll be in touch as we open more access — whether you want to use it yourself, support patients, or build agents on the LHP.