Medical information rarely arrives as one coherent story. A blood test may live in a laboratory portal, a consultation report in an email, and a medication change in a note that is difficult to find months later.
Hoom Health is being built as a patient-controlled archive for that fragmented history. The goal is not to replace a clinician or the original medical record. It is to keep the evidence connected and make the history easier to inspect over time.
One archive across time and providers
Hoom brings documents, readings, medications, symptoms, and notes into one longitudinal archive. A user can keep records from different providers and periods together instead of reconstructing the same history before every appointment.
The timeline is central to this approach. Individual facts remain useful, but dates and recurring periods make it possible to see how readings, medications, and symptoms overlap.
Keep the source behind the fact
Structured health facts should not become detached from their evidence. Hoom preserves original documents and links extracted facts back to their source. That makes it possible to inspect a reading or symptom and then open the report or note that supplied it.
AI-assisted extraction can still omit or misread information. Source preservation gives users and clinicians a practical way to verify what was extracted.
Use AI where it adds value
Some work does not need an AI model. Users can enter readings, medication periods, and symptom periods manually without consuming AI allowance. Documents and longer notes can use AI-assisted organization, while summaries and Health Reviews remain separate, user-requested operations.
Hoom’s AI output is informational. It can be incomplete or wrong, and it does not provide a final diagnosis, treatment, or emergency assessment.
What comes next
The current work focuses on making the archive dependable: preserving source files, improving extraction validation, supporting repeated health-history periods, and keeping AI operations transparent. We will use this blog to publish product changes and explain the decisions behind them.