A data-rich hospital is not necessarily a hospital that knows.
Often the opposite is true. Data accumulates across system after system, yet the hospital cannot answer a single question like “did that ad campaign from last month actually lead to surgeries?” Data is everywhere; understanding is nowhere. Why? Because data must pass through several stages before it becomes knowledge — and in most hospitals, those stages are broken somewhere in the middle.
Four Stages: Subject, Record, Information, Knowledge
Knowledge does not appear in an instant. It is built through four stages: from subject to record, from record to information, from information to knowledge.
Something happens. It is written down. Meaning is attached to what was written. Those meanings accumulate into understanding that can actually be used. There is no shortcut across this flow. From the moment a patient sees an ad and picks up the phone, to the moment that person becomes a loyal patient who truly understands your hospital — data follows these four stages.
Following a Single Phone Call
Monday afternoon. A phone rings.
If that call remains only a “phone call received,” it never even becomes data. The conversation ends and vanishes. But the moment it is recorded as “a first inquiry about varicose veins, from a patient who saw a specific advertisement” — it becomes a record with a subject. That is the first stage.
Next, this record passes through perspectives to become information. Through the marketing lens, it is “one result from that ad campaign.” Through the consultation team’s lens, it is “a prospective patient to be guided toward conversion.” Through management’s lens, it is “an opportunity not yet converted to revenue.” One phone call awakens as three different pieces of information.
Then, as this patient actually comes in for a consultation, undergoes tests, proceeds to surgery, and returns for follow-up — all of this information weaves into the story of one person. When hundreds and thousands of these stories accumulate, knowledge finally emerges. “Patients from this ad come readily for consultations, but surgery conversion is low.” “Patients through this channel take an average of this many days to decide.” None of this could ever be known from a single phone call.
Why Spreadsheets Stop Here
Many hospitals do this work in spreadsheets. Spreadsheets are excellent tools. But spreadsheets excel at storage, not connection.
One cell in a spreadsheet does not know what the cell next to it means. The spreadsheet cannot tell whether “inquiries” on the ad sheet and “surgical cases” on the revenue sheet refer to the same patient. A person must lay the two sheets side by side and match them by eye. More sheets means more matching, and once something goes wrong, finding where it went wrong is hard. Records accumulate, but because those records cannot recognize each other, they never rise to knowledge.
An ontology is not about filling cells. It is about connecting the meaning between cells. Put in the same data, and the output differs. A spreadsheet stores numbers. An ontology knows that those numbers are the story of one patient.
Why Most Hospitals Stop in the Middle
The problem is that most hospitals stop at the second stage. They record. They organize into information, to a degree. But it all remains scattered, never reaching knowledge. Call logs stay with call logs. Revenue stays with revenue. Ad spend stays with ad spend. Each sits in its own place, never connecting into one story.
So the hospital knows how much it spent on advertising but not which surgeries that money produced. Not because data is lacking. Because the connection between stage and stage is broken. This is why hospitals with multiple expensive systems still end up saying: “We have all these numbers, but we can’t understand anything.”
How This Differs from Search — It Accumulates
Here the decisive difference from search becomes clear. Every time you search, it scrapes scattered data from scratch. Every query starts over, so nothing accumulates. Nothing remains between yesterday’s question and today’s.
An ontology works differently. Knowledge organized once stays, and is used faster and more accurately for the next question. Yesterday’s analysis becomes today’s starting point, and understanding grows thicker day by day. The longer a hospital operates, the wider the gap between a hospital that relies on search and one that holds an ontology. One starts from scratch every time; the other starts from accumulated understanding.
The Flow Circles Back
Keynoty’s system is built on top of this entire flow. What happens in the hospital is recorded with its subject, defined as information through its perspectives, and accumulated into knowledge of the hospital.
And that knowledge returns to the floor. When the understanding “this ad generates many inquiries but rarely converts to surgery” takes shape, it changes the next ad, changes the next consultation, makes the next record more precise. The flow is not one-directional — it circulates. This is why we say we build an OS from the floor, not from a desk. We run this circulation ourselves, finding and closing the broken points every day.