In the previous chapter, we said “perspective is what turns a record into information.” This chapter is about that single sentence. It holds the most important insight in all of ontology.
The same thing is divided differently depending on who is looking.
One Patient, Three Pairs of Eyes
A patient walks into the hospital. The same patient. But the patient seen in the exam room, the patient seen at the administrative desk, and the patient seen by management are not the same.
Through the clinician’s eyes: diagnosis, prescription, progress. Through the administrative staff’s eyes: billing codes, insurance eligibility. Through management’s eyes: how this patient arrived, how long they waited, which resources were used. Same patient, different knowledge.
What becomes important information is determined not by the subject but by the purpose of the observer. It is like how a library and a bookstore handle the same book differently. A library looks at classification and indexing; a bookstore looks at price and inventory. The same book — but in a library the “call number” is central, and in a bookstore the “retail price” is central. We call this “way of looking” a perspective, and we call the fields a perspective defines metadata.
The Common Failure — Building Separately Per Perspective
This is where most systems fracture.
The common approach is to create separate data for each perspective. The clinical system has the patient. The billing system has the same patient again. The marketing tool has them, the management report has them — the same person exists separately in every system.
The result is misalignment. Change a contact in one system, and the other keeps the old one. Clinical records and billing records fall out of sync. Numbers in the management report differ from what the floor observes.
Settlement Day
The day this misalignment hurts most is settlement day.
At month’s end, the numbers pulled from different systems do not match. The clinical tally disagrees with the billing tally. The conversions marketing reported do not align with actual revenue. The operations team spends days reconciling — merging, checking, merging again. During those days, the question that actually matters — “what went right this month, and what went wrong?” — gets pushed aside.
This is not because the staff is careless. It is because the same patient was designed to exist separately in each system. When the structure is misaligned, no amount of diligence from people can make the numbers align. The more data, the more confusion — that paradox is born here. More systems are brought in, and yet the work only multiplies.
One Truth, Many Expressions
A good ontology works in exactly the opposite way.
The patient exists as a single source of truth. Clinical, administrative, and management perspectives each see a different face of that one original. One truth, many expressions. So no matter who updates what or where, every screen points to the same fact.
When any staff member corrects a patient’s information, every other screen updates at that same moment. No separate reconciliation is needed, because it was always one. The patient seen in clinical care and the patient seen in billing cannot fall out of sync — because both are illuminating the same original from different angles. This is the true meaning of “single source of truth” from Part One. We do not multiply data through copying. We layer multiple perspectives precisely over a single fact.
Perspective Is Also Permission
Perspective carries one more important property. It is also the act of deciding who gets to see which face.
The consultation room sees as much as consultation requires. Administration sees as much as billing requires. Management sees as much as management requires. Over a single original, only the face each person needs can be opened to them. Sensitive patient information is not handed to everyone in full. In a system that copies data and scatters it everywhere, this is impossible. Because the truth is one, the question of who sees it, how, can be controlled with precision.
More Perspectives, Same Stability
Another strength of this structure is scalability. When a new department forms or a new report is needed, no new data is created. A new perspective is simply layered over the same original. As a hospital grows and becomes more complex, the approach of building separately collapses — and the approach of layering over a single truth holds.
What Integrates, and What Does Not
One thing should be stated clearly. What unifies here is the administrative and data expression layer. Not medical judgment.
That clinical, administrative, and management perspectives see the same patient without misalignment means administrative information is consistent. Decisions about diagnosis, treatment, and surgery belong entirely to the clinical staff of each medical institution. What Keynoty’s system provides is operational support in non-medical domains — marketing, settlement, inventory, staffing assistance, and the like. What we integrate is the order of data, not the practice of medicine.