The Verbal Medical Record: Why Patients and Families Become Their Own Health Data Systems

When my Co-Founder and our CEO Bobby Hill's father had a stroke and was rushed to Atlantic City Hospital, none of his records were there. His father had lived in the Philadelphia area most of his life. He could not walk. He could not talk. And the hospital had nothing.

Bobby had just spent months at CHOP with his son, who had been diagnosed with a rare lung disease called pulmonary interstitial glycogenosis. He had watched his wife become the verbal medical record for their child, the person in the room who knew what had happened previously, what medications had caused problems, what the last attending had said. He thought that experience would make it easier to navigate his father's care.

It was worse.

Six months at a brain rehab center. Social workers have no answers about discharge planning. Three different home health care agencies across two states. A defibrillator flagged as a pacemaker at a Penn appointment, months after six months of care at Drexel. No records transferred. His sister, a cardiac nurse at Penn, stood in the room as the verbal medical record for a man who could not speak for himself.

The System That Makes Patients the Data Layer

This story is not exceptional. It is the default.

Patients and their families are routinely forced to serve as the connective tissue between fragmented systems that cannot communicate. They carry records in folders. They repeat histories to every new provider. They catch errors that the previous provider never communicated. They sit in appointments and mentally scan their memory for what this physician does not know and what they should say.

The cost is not just inconvenience. It is a clinical risk. When a patient cannot be their own verbal medical record because they are unconscious, cognitively impaired, elderly, a child, or simply do not know what they do not know, the gaps become dangerous.

A defibrillator is documented as a pacemaker. A medication that caused two ICU admissions, not in the record. A discharge to a facility with abuse charges because no one reviewed the records. These are not hypotheticals. They are what happens when data is fragmented without a trust layer to connect it.

What Fragmentation Actually Means

The fragmentation problem in health data is not that data does not exist. It is that the data exists in the wrong places, in the wrong formats, without provenance tracking to verify its accuracy, without a consent architecture to share it appropriately, and without recency signals to know whether it still reflects the patient's reality.

A record captured six months ago may be materially different from the patient's current status. A record in one system may contradict a record in another, and both can be technically correct representations of different moments in the patient's history. An AI model that ingests both without understanding the temporal relationship between them will produce an inference that is worse than no inference at all.

The problem is not that we lack data. The problem is that we lack a trust layer that tells us which data to believe, how current it is, where it came from, and what it is authorized for.

The DTI Response

The SuperTruth Data Trust Index was designed for exactly this problem. Every health data record scores across eight dimensions: Provenance, Consent, Recency, Quality, Concordance, Validation, Breadth, and Stability.

Recency matters here in a specific way. Health data is not static. A CBC from eighteen months ago and a CBC from last week are not equivalent inputs. The DTI applies time-decay functions by data modality. A continuous HRV stream ages differently than a lab result, which ages differently than a medication reconciliation. The score reflects not just what the data says, but how current that statement is.

Provenance matters because a record without a documented chain of custody is not the same as one from a CLIA-certified lab with a complete audit trail, even if the content appears identical. The DTI scores the source, not just the contents.

Consent matters because the same record may be authorized for one use and not another. The ability to share with a treating physician under HIPAA is different from the authorization to include in a research cohort. ConsentOS tracks which uses are permitted and propagates revocations downstream in real time.

What Changes

When health data has a trust layer, a few things become possible that are not possible today.

Providers get a complete, scored, current picture of the patient before the appointment — not a fragmented record from whichever system happens to be connected, but a reconciled view with trust scores that tell them which data to weight and which to verify.

Patients stop being the verbal medical record. The data does the work their families have been doing manually. The advocacy burden shifts from the person in the room to the infrastructure that was supposed to do this all along.

The fragmented system does not become integrated overnight. But the trust layer gives every component of the system a common language for describing what it knows, how it knows it, and whether it should be trusted.

To talk about what this looks like for your organization, reach Louis Simeonidis at louis@supertruth.ai or (215) 918-4140.