‹ All posts

The Code

The System Had No Operating System: Patient First Healthcare

Patient first healthcare is a phrase the industry loves to say. After 25 years working across the healthcare ecosystem, I can tell you what I actually saw from the inside. The system had talented people, serious technology and real money moving through it every day. What it did not have was an operating system. Nothing connected the whole journey for the person at the center of it, and that person is the patient.

My career started in 2001, and it gave me the system from almost every seat. As a Pfizer representative I visited over 15,000 medical offices. From there my career moved into the operating room, where I have been part of over 10,000 procedures, and into health systems, where I learned how products and decisions actually move. Later, from an investor seat at Baseline Health, I watched care serve more than 200,000 lives across more than 80 unions, municipalities and counties. Every stop taught me the same lesson from a different angle.

Every part worked. Nothing worked together.

Here is what that view shows you. The doctor is not the problem. The nurse is not the problem. The technology, piece by piece, is often not the problem either. Hardworking people do hard work inside healthcare every single day. The problem sits between the parts. A record lives in one place. A result lives in another. The next step depends on a call nobody made, a form nobody sent, or a question the patient did not know to ask.

So the patient becomes the connection. The patient carries the story from office to office, repeats it at every new desk, and tries to enter care informed when the system has given them no map. In my interviews I say it plainly: the healthcare journey today is one of the most confusing and intimidating experiences people face. When most people think about going to the doctor, they feel anxiety, uncertainty and sometimes fear, and that fear often stops people from taking action early. People enter the system far too late. They do not understand the signals their bodies are giving them. They do not know where to start, who to trust, or what questions to ask.

What I saw at Harvard

I carried that conclusion into the Global Healthcare Leadership Program at Harvard Medical School, where I sat with about fifty global healthcare leaders. I expected to hear that other systems had solved the connection problem and that ours was the exception. I heard the opposite. Leaders from different countries and different systems described the same fragmentation, wearing different clothes. The problem was not one hospital, one insurer or one country. The problem was the design. There was no operating system for the person.

That room changed what I built next. From there, we founded the Global Healthcare Leaders Foundation in May 2024, where I serve as Founder and President of the Board. GHLF exists to bring global healthcare leaders together, because a problem this connected cannot be solved by leaders working alone in separate rooms. I told that classroom story in Why I Went Back to School at Harvard, and the ground level version of it in 200,000 Lives: What Baseline Health Taught Me.

Patient first is a design rule

Patient first cannot stay a slogan on a wall. It has to become a design rule that decides what gets built and what gets refused. At FreeHealth.ai, the company I founded in November 2025, that rule starts with ownership. The patient owns their data. FreeHealth never owns it, and never sells it without their agreement. Any sharing is opt in only, done alongside the patient, who shares in the value. That is not a policy detail to me. It is the foundation the whole platform stands on.

The second part of the rule is honesty about the role. We do not play doctor. We play data aggregator. FreeHealth.ai is for health education and navigation. It is not a diagnosis. The job is to help a person understand their health earlier, recognize signals sooner, and enter their healthcare journey informed instead of afraid. Think of it as a check engine light for your health: a signal that surfaces early, while there is still time to act on it well.

How an operating system gets built

Nobody fixes a system this large with one app or one announcement. You build the connection layer the way you build anything that lasts, brick by brick, and you hold the design rule on every brick. The standard behind mine is written out in The Code.

1. Start with the patient, not the system. Every workflow, every screen and every partnership gets one test first: does this make the journey clearer for the person receiving care? If it only makes life easier for the system, it fails the test, no matter how efficient it looks on a chart.

2. Connect before you add. Healthcare does not need one more silo with a new logo. It needs the pieces it already has, the records, the doctors, the services and the follow up, stitched into one journey the patient can actually follow. Connection is the product. Everything else is a feature.

3. Surface the signal early. Late is expensive in health, in money and in fear. A system that respects the patient warns early, explains plainly and points to a clear next step, so a small signal gets handled while it is still small.

Twenty five years, 15,000 offices, 10,000 procedures and 200,000 lives taught me that healthcare was never short on caring people. It was short on connection. The system had no operating system, so we are building one, patient first, with the patient owning their data and holding the map. That work is the conclusion of the healthcare chapter of my book, Built. Brick by Brick. It is the work I intend to be judged by.

Go deeper.

The book is Built. Brick by Brick. Chapter 1 is free, and the coaching waitlist is open now.