From CTO to Co-Inventor

For most of my career, healthcare and cybersecurity sat in different rooms in my head. One was about patients and diagnosis. The other was about protecting data and systems from people who want to misuse them. The patent is where those two rooms turned out to share a wall.

How a security person ends up on a medical patent

The invention is an AI system for finding disease in 3D medical images. That sentence makes it sound like a pure medical-imaging project, and the imaging science is genuinely the heart of it. But the moment you try to build something real with medical data, you run straight into the questions I have spent twenty-five years answering. Where does the data live? Who can touch it? How do you prove, later, who did what? How do you use sensitive information without exposing the people it belongs to?

A brilliant model that cannot answer those questions never makes it near a hospital. That is the gap I was there to close.

What the CTO role actually contributed

My job was not to invent the diagnostic math on my own. It was to turn a powerful idea into a system that could survive contact with the real world. That meant thinking about the parts that do not show up in a research demo and decide everything in production.

How the data is protected at every stage. How identity and access are enforced so only the right people and processes can reach anything. How every action leaves a trail you can audit. How the whole thing is designed so that a single mistake does not become a breach. The architecture had to be defensible, not just clever.

That is the difference between a research result and an invention you can protect and deploy. One works in a lab. The other holds up when a regulator, a hospital, and an attacker are all looking at it from different angles.

The lesson about working across fields

The most useful thing I brought was not a single skill. It was the habit of standing between two groups of experts and translating. The imaging and machine-learning side spoke one language. The security, privacy, and compliance side spoke another. They needed someone who could hold both at once and make decisions that respected both.

I have done that my whole career, between technologists and boards, between engineers and regulators. On the patent it just happened to be between data scientists and the realities of protected health information. Same instinct, higher stakes.

Why I am proud of it

I did not set out to become a co-inventor. It came from being in the room, asking the questions nobody else was asking, and refusing to wave away the hard parts. The invention is not only a way to look at a scan. It is a way to do that while keeping the patient protected, and that second half is mine to be proud of.

The title on the filing says co-inventor. What it really records is that the line between my two fields was never as solid as I thought.