Search engines organize knowledge by category. People do not fit categories. This is a problem that did not exist thirty years ago, and it is one I think about more than I probably should -- because I live inside it.
Here is what happens when you Google a physician who also runs a technology division. The algorithm tries to resolve you into a single entity type. Google's Knowledge Panel system -- which now covers an estimated 5 billion entities according to Google's own documentation -- works by assigning categorical attributes. You are a Person. You are a Physician. You have a Medical Specialty. But what if you are also a technology executive? The system does not have a clean schema for that. It picks whichever signal is strongest and builds your digital identity around it. Everyone else who searches for you inherits that framing.
I first noticed this in 2019, when a potential business partner told me he had "looked me up" before our meeting. He had found my clinical background and assumed I was a practicing surgeon looking to consult on a side project. He had not found any of my technology work. Not because it did not exist, but because the algorithm had categorized me and served results accordingly. The search engine had decided who I was before I walked into the room.
The structural problem nobody writes about
Professional identity fragmentation is not a personal branding problem. It is a structural problem with how knowledge systems -- digital and human -- handle people who operate across domains.
A 2024 study in the Journal of Professions and Organization examined professionals transitioning into emerging occupations and found that identity construction involves constant negotiation between three competing frames: aspirational identity (who you want to be), professional identity (who your credentials say you are), and expected identity (who others assume you are). For most professionals, these three roughly align. For anyone working across multiple domains, they pull in different directions constantly.
I graduated from Duke University in 2000 with a BS in Biochemistry. But I had spent most of my undergraduate years as a web architect -- building websites professionally before the term "full-stack developer" existed. When I entered Stanford Medical School in 2001, I assumed I was choosing. Medicine was the serious career. Technology was the thing I used to do.
That assumption lasted about six years.
What Stanford's OR actually teaches you
Stanford's integrated plastic surgery residency selected three candidates per cycle for a six-year accelerated program. I matched in and spent the next six years operating on cleft palates, traumatic facial injuries, hand replantations, and complex craniofacial reconstructions. By the time I finished in 2012, I had accumulated thousands of procedures.
Craniofacial surgery teaches you something that no organizational chart or business framework can replicate. The distance between a plan and an outcome is measured in millimeters, and those millimeters belong to someone's face. A child's ability to eat normally. A veteran's ability to grip a steering wheel. There is no pivot. There is no minimum viable product. You get one attempt.
But here is the thing nobody mentions about surgical training: it also teaches you to think in systems. A free fibula flap is not just a technical procedure. It is a logistics problem involving donor site morbidity, recipient vessel quality, soft tissue coverage, and postoperative rehabilitation -- all of which have to be planned simultaneously before you make the first incision. That kind of multi-variable, sequential-but-parallel thinking is exactly what technology leadership requires. I just did not have the language for it yet.
The VA, the machinist, and the question that changed direction
At VA Palo Alto, where I started as an attending after residency, the patients were different from anything my Stanford training had prepared me for. Veterans present with decades of deferred care, complex wound histories, comorbidities stacked three and four deep. A hand reconstruction that might take two hours at a university hospital could take four at the VA because the tissue quality was compromised, the vascular anatomy was altered, and the patient had waited eleven months to get on my schedule.
One case sticks with me. A machinist -- 58 years old, dominant hand caught in a metal brake press, three fingers crushed. The reconstruction was technically demanding. But what stayed with me was not the surgery. It was the system around it. The referral had taken four months. The imaging was from a different facility and had to be re-ordered. His occupational therapy would require authorization from a separate department with its own waitlist. The surgery went well. The system around it was broken in ways that surgical skill could not fix.
I kept asking a question that annoyed my colleagues: why are we still doing this manually? Not the surgery -- the infrastructure. The referral chains, the data silos, the complete absence of interoperability between the systems that were supposed to support clinical decision-making.
That question pulled me toward technology. Not away from medicine. Toward the machinery that medicine runs on.
The identity tax
Here is where the fragmentation really costs you. When I joined iMerit as Senior Director of Medical AI in 2022, I sat in a product strategy meeting explaining how we needed to restructure our radiology annotation pipeline. Fifteen minutes in, our VP of Engineering stopped me. "Wait -- you have actually done surgery? Like, on people?" He had read my LinkedIn. He had hired me. But the surgeon part had not registered as real.
I laughed it off. But the moment stuck with me, because it was the inverse of a conversation I had had years earlier at the VA. An OR nurse asked what I had been doing before joining the VA. When I mentioned working on a medical device for peritoneal dialysis infection reduction through Stanford's Bioinnovation program, she gave me a look I have come to recognize. Polite confusion. The unspoken question: why would a surgeon care about that?
The identity tax is real and quantifiable. Every new professional relationship starts with the same overhead: establishing that the "other" credentials are real, that they are not hobbies or past lives, that they are actively relevant to the work at hand. At a tech conference, I am "the surgeon." At a medical conference, I am "the tech guy." Neither group is wrong to categorize me. Both are missing the point.
ORCID, the digital identifier system for researchers, now has a 72% adoption rate among academics -- reaching 93% in biological and biomedical sciences. It was built to solve exactly this problem: disambiguating researchers so their work across institutions and disciplines could be properly attributed. But ORCID solves for academic publishing. It does not solve for Google. It does not solve for the hiring manager who sees "surgeon" and stops reading. It does not solve for the investor who hears "MD" and assumes you will go back to the OR.
Building across the gap
At iMerit, I built the Medical AI division from scratch -- radiology annotation, endoscopy labeling, robotic surgery datasets, and drug development pipelines that grew to more than $4M in annual recurring revenue over three years. Every project started with the same question I had learned at the VA: what does the clinician actually need to see?
The answer is almost never what the engineers assume. A radiologist reading chest CTs does not need an AI that flags "abnormality detected." She needs an AI that can distinguish between a benign granuloma and a spiculated nodule, because that distinction determines whether a patient gets a follow-up scan in six months or a biopsy next Tuesday. That level of clinical specificity requires someone who has stood on the other side of the decision -- someone who has had to tell a patient what the scan found.
A 2026 review in Frontiers in Health Services examined professional identity work in emerging healthcare roles and found that "role ambiguity, contested expertise claims, and fragmented organizational structures" are the defining challenges for professionals who span traditional disciplinary boundaries. The review treated this as a problem to be studied. I live it as a Tuesday.
That VP of Engineering at iMerit? Six months after his "on people?" moment, he told me the reason our medical AI products worked was precisely because I had done surgery on people. He figured it out. Most people do, eventually. The problem is that "eventually" is expensive when you are trying to build trust, close deals, or get a meeting.
What the algorithm misses
I am writing this from Oakland, where I have lived long enough to watch the healthcare AI industry cycle through three waves of hype. Each wave produces the same character: the "physician-turned-entrepreneur" who left medicine to join tech. The narrative is always framed as a departure. A before and an after.
I have never experienced it that way. The surgeon who spent two hours reconstructing a veteran's hand and the executive who built an AI annotation pipeline are not two different people who share a name. They are the same person applying the same pattern -- understand the system, find the constraint, operate precisely within it. Whether "operating" means a scalpel or an org chart is a detail, not an identity.
But search engines do not index patterns. They index categories. And until that changes, anyone whose career crosses domain boundaries will keep paying the identity tax -- explaining themselves in every room, watching the algorithm flatten their trajectory into whichever label it picked first.
So I stopped waiting for permission to be all of it at once. Surgeon. Executive. Builder. Duke biochemistry, Stanford MD, over 12,000 clinical procedures, a multimillion-dollar AI division, and a career that makes no sense to an algorithm until you understand the pattern underneath. That is the answer to "who is Dr. Sina Bari." Not a title. Not a category. The whole trajectory.
Frequently Asked Questions
What is Dr. Sina Bari's medical and educational background?
I earned my BS in Biochemistry from Duke University in 2000, my MD from Stanford University School of Medicine in 2006, and completed a six-year accelerated plastic surgery residency at Stanford Hospital in 2012. I have performed over 12,000 clinical procedures across academic, VA, and private practice settings, specializing in craniofacial surgery, hand surgery, and reconstruction.
What does Dr. Sina Bari do in healthcare AI?
I served as Senior Director of Medical AI at iMerit, where I built the Medical AI division from inception to more than $4M in annual recurring revenue. That work spans radiology annotation, endoscopy labeling, robotic surgery training datasets, and drug development data pipelines. Previously, I served as Chief Innovation Officer at a healthcare technology company focused on AI applications in dermatology, ophthalmology, and ENT.
What is professional identity fragmentation and why does it matter?
Professional identity fragmentation occurs when digital systems and human mental models cannot accommodate a person who operates across multiple professional domains. A 2024 study in the Journal of Professions and Organization found that professionals in emerging roles must constantly negotiate between aspirational, professional, and expected identities. For multi-domain professionals, this creates measurable friction in hiring, fundraising, and professional trust-building.
Where is Dr. Sina Bari based?
I am based in Oakland, California. My clinical training took place at Stanford Hospital and VA Palo Alto in the San Francisco Bay Area.