The Ten-Second Query That Changed Everything
The most valuable use of clinical data is almost never the use it was collected for.
Duke University Medical Center. June 1989. A Saturday morning I never forgot.
It was early. The cafeteria was half empty. I was sitting with a cup of coffee when Bob dropped into the chair across from me looking like he hadn’t slept.
Bob was a senior anesthesia resident at Duke. Brilliant, serious, the kind of physician who was going to be somebody. But that morning he looked beaten. I asked him what was wrong.
He explained his weekend ritual. Every Saturday, he had to manually calculate how much time every third-year anesthesia resident had spent in each surgical specialty over the past week. That meant pulling paper anesthesia records one by one. Finding the start time. Finding the stop time. Identifying which resident was on that case. Determining which specialty. Tallying the hours. Then doing it all again for every resident, every case, every specialty. For the entire academic year.
Hours. Every Saturday. All year long.
I listened. And then something clicked.
“Bob,” I said, “I think that information is already sitting in our database.”
I need to back up.
At the time I was working for a company called DIATEK. We built technology for anesthesiologists, including a product called ARKIVE: an anesthesia information management system I had helped architect and build. The concept was ahead of its time. Capture data automatically from OR monitors, ventilators, IV pumps, blood bypass machines. Everything in the operating room that generated a signal. Then build the anesthesia record from that data automatically.
No more hand-charting. No more transcription errors. The anesthesiologist’s hands stayed where they belonged. On the patient, not on a clipboard.
ARKIVE ran on a database engine called Paradox. Windows DOS environment. The year was 1989.
The data Bob needed was all there: case start times, stop times, resident assignments, specialty areas. Captured automatically by ARKIVE on every single case. Sitting in that database the whole time. Nobody had thought to ask it the question Bob was answering by hand every weekend.
I sat down with him right there in the cafeteria. We wrote a Paradox query together. It took maybe an hour.
It ran in about ten seconds.
Bob stared at the screen. Every resident. Every case. Every specialty. Every hour. Calculated perfectly. Instantly.
He looked at me.
“You gave me my weekends back. I truly owe you.”
He didn’t owe me anything.
But that hour, that ten-second query on a Saturday morning in 1989, taught me something I have spent the next 36 years trying to apply at scale.
The most valuable use of clinical data is almost never the use it was collected for.
The ARKIVE data was collected to build the anesthesia record. That was its purpose. That was what justified its existence to every administrator and department chair who approved the budget for it.
But sitting inside that same data, quietly, patiently, invisibly, was the answer to a question nobody had thought to ask. A question that was consuming hours of a brilliant physician’s weekend every single week.
The data was already there. It just needed someone to ask it the right question.
Thirty-six years later I keep watching the same story repeat itself at a larger scale.
We deploy an EMR. We spend $40 million. We collect more clinical data than any previous generation of physicians could have imagined. And then we use it to document the same things we used to document on paper, only faster.
We deploy BCMA. We scan every medication at the bedside. We collect a perfect digital record of every drug that reaches every patient. And then we use it to verify the right drug reached the right patient. Nothing more.
We deploy machine learning on our automated dispensing cabinets. We score every transaction against a behavioral baseline. We collect a perfect digital record of every controlled substance that moves through the facility. And then we use it to flag statistical outliers with no access to the clinical record. Seventy-seven percent false positive rate. Nursing leadership furious. Good nurses under investigation.
Each time, the data was already there. Each time, we only asked it one question. The question the system was designed to answer.
Nobody asked what else was in it.
Here is what I believe, after five decades inside the companies that built these systems:
The problem was never the technology. The EMR worked. BCMA worked. The ML diversion platform worked. Every system performed exactly as designed.
The problem was the architecture. Each system was optimized for a single data source. None of them could reason across the full picture simultaneously. None of them could read the clinical story as a single coherent narrative and ask: does this make sense?
The physician order. The pharmacist verification. The cabinet transaction. The pump record. The patient vitals. All of it together. In real time.
That question, does this make sense?, is what Bob needed answered on those Saturday mornings. The data to answer it was right there in ARKIVE. He just needed someone to write the query.



