Your family's medical history is not in one place. It's scattered across a decade of clinic visit summaries, a handful of specialist letters, the recall of a spouse who remembers which cardiologist saw who and when, and the vague knowledge that someone in the family "had something with their thyroid" a few years back. When a new specialist asks for a complete medical history at the intake appointment — and they always ask — you're reconstructing it on the spot.
When Recall Fails the Intake Form
The intake form is the diagnostic starting point. "Any previous diagnoses?" — and suddenly you're trying to remember whether the gallbladder issue was fully resolved or just not followed up on, whether the thyroid result was hypothyroidism or subclinical, which year the knee surgery happened, who the surgeon was. Specialists build differential diagnoses partly on what they're told at intake. Gaps and inaccuracies in that history lead to redundant testing at best and missed patterns at worst.
A structured database with one record per condition — not per person, per condition — changes the retrieval experience entirely. You open it, filter by family member, and hand the specialist a complete, timestamped medical history with treating physicians listed.
The Anatomy of a Condition Record
Status is the first field to understand. "Current" means active — ongoing treatment, active management, or a permanent diagnosis the family member lives with. "Past" means resolved: symptoms gone, treatment ended, condition no longer relevant to current health. "(Researching)" is the state that usually goes undocumented: something flagged by a lab result or symptom pattern that a physician wants to monitor before assigning a formal diagnosis. That liminal status exists for weeks or months sometimes, and it tends to fall out of the narrative entirely unless it's captured explicitly.
Date Diagnosed and Symptoms Began are two different data points that most people collapse into one in their memory. Symptoms began three months before the gastroenterologist finally ordered the colonoscopy and identified the Crohn's. The diagnosis date is the date on the report. The symptoms began date is the actual start of the disease experience. Both matter for longitudinal health tracking, and the gap between them tells its own story about how long it took to get from complaint to confirmed diagnosis.
Symptoms Ended closes the loop on resolved conditions. For acute illnesses, surgical resolutions, or successfully treated infections, this field converts a "past" record into a complete episode with known endpoints. It's the field that turns a vague entry into something a doctor can actually use.
Treated by Dr. and Dx'd By Dr. are deliberately separate fields. The diagnosing physician and the treating physician are often different people — an ER doctor makes a diagnosis, a specialist handles the treatment protocol. A GP refers, a hospitalist manages the inpatient stay. Keeping both names distinguishes who identified the condition from who you'd call if it recurred.
The Patient choice field — pre-populated with family initials — filters the entire database by family member in a single tap. One database, all household members, each with their own complete condition history.
The Emergency Use Case
The scenario that makes this database worth building: an ambulance is called and the paramedic asks whether the patient has any known conditions, is on any medications, has any allergies. The spouse or family member who answers that question is terrified and stressed and trying to think. The family member who can pull up a filtered database view on their phone and read a current condition list is the one who gives the paramedic actionable information in under two minutes.
Comments carries the nuance that doesn't fit in structured fields: "was not consistent with Lipitor, switched to Crestor after six weeks" or "symptoms substantially worsened with ibuprofen, avoid NSAIDs." The kind of clinical context that would take a reviewing physician three additional questions to elicit in a normal encounter.