The Clinical Architect
Why Healthcare Companies May Soon Need Architects as Much as Clinicians
Medicine has always had clinicians.
It has had surgeons and researchers, educators, department chairs, and medical directors. Likewise, hospitals have long relied upon specialists to diagnose disease, perform procedures, interpret evidence, and train the next generation of physicians. For most of modern healthcare, these roles were sufficient because healthcare itself remained relatively linear - patients entered the system, saw a clinician, received treatment, and moved on.
Increasingly, however, healthcare companies are being asked to do something different.
Modern women’s health organizations are not simply delivering care, but are building systems. Menopause platforms, fertility companies, and digital health organizations all working to merge multiple moving parts into a single patient experience.
At small scale, these systems often function through proximity and enthusiasm. A handful of clinicians can communicate informally, discuss cases, and increase patient response through repeated interaction. As organizations grow, however, informal systems begin to fracture. Questions that once resolved themselves quickly become operational problems requiring deliberate design.
Who reviews the patient who does not fit the protocol? When should a nurse practitioner escalate a case? Which outcomes should be tracked? How are adverse events identified? How do twenty clinicians practicing across ten states make twenty similar decisions instead of twenty different ones?
These are not simply staffing questions.
They are, instead, architecture questions.
Buildings Require Blueprints
No one would attempt to build a hospital by hiring talented individuals and simply hoping the structure organizes itself. Hospitals require blueprints. Airports require blueprints. Even relatively simple buildings depend upon architects who understand how people, information, and resources move through physical space.
Healthcare systems are no different.
Yet many healthcare organizations behave as though expertise naturally emerges from assembling intelligent people in the same room. Physicians are hired. Nurse practitioners are onboarded. Coaches and care navigators are added. Protocols are distributed. Technology platforms are implemented. Leadership assumes the system will somehow organize itself around these components.
And, interestingly, sometimes it does.
More often, however, variability quietly accumulates beneath the surface. One clinician approaches a problem one way while another approaches it differently. Escalation pathways become inconsistent. Outcomes become difficult to interpret because the underlying processes generating those outcomes are no longer uniform. What initially appears to be a personnel problem gradually reveals itself to be a systems problem.
Healthcare companies rarely fail because they lack intelligent people. They fail because intelligence without architecture does not reliably scale.
Protocols Scale…Until They Don’t
Protocols are among the most powerful tools in modern medicine.
They reduce variation, improve efficiency, facilitate training, and improve safety. Few clinicians would argue against standardized approaches to hypertension management, antibiotic prophylaxis, or postoperative care. In fact, much of modern medicine depends upon converting expert knowledge into repeatable systems that can be applied consistently across large populations.
The challenge is that protocols perform best in predictable environments.
And as we know, medicine is not always predictable.
The patient with straightforward vasomotor symptoms rarely creates difficulty. The complexity emerges, instead, when menopause intersects with breast cancer survivorship, autoimmune disease, premature ovarian insufficiency, complex psychiatric histories, or medication interactions that fall outside the boundaries of the original protocol. The further one moves toward subspecialty care, the more exceptions begin to appear.
Brian Redman captured this distinction well:
“Be warned that being an expert is more than understanding how a system is supposed to work. Expertise is gained by investigating why a system doesn’t work.”
In many respects, expertise lives in the exceptions.
Protocols explain what happens when patients follow the expected path. Specialists become valuable when patients leave it.
The Rise of Operational Medicine
Patients see only a small portion of modern healthcare systems.
They see the appointment, the prescription, the laboratory order, and the follow-up message. The visible interaction feels personal and straightforward. Behind that interaction, however, exists an increasingly complex operational layer that determines whether the patient experience succeeds or fails.
Someone decides which patients qualify for a given pathway and which require physician review. Someone determines how side effects are reported, how quality metrics are measured, and how outcomes are tracked over time. Someone designs the intake forms, the escalation criteria, the documentation standards, and the clinical review process that sits quietly beneath the patient-facing interface.
Patients rarely see this work.
Investors often underestimate it.
Healthcare companies eventually discover that it is unavoidable.
As organizations scale, operational medicine becomes increasingly important. What initially appears to be a technology problem gradually reveals itself to be a governance problem, and what initially appears to be a staffing problem often reveals itself to be a workflow problem. Scale has a tendency to expose weaknesses in clinical design that remain invisible at smaller volumes.
The invisible layer often determines whether the visible layer survives.
The Emergence of the Clinical Architect
Historically, medicine developed clear identities for physicians who generated evidence, physicians who delivered care, and physicians who led organizations. Increasingly, another role appears to be emerging alongside them.
Someone must design the system itself.
The clinical architect asks different questions than the traditional clinician. Which patients should never enter this pathway? When does protocol stop and expertise begin? How does information move through the organization? Which outcomes matter enough to measure? How should rare complications be identified and managed? What happens when the patient does not behave the way the flowchart predicted?
These questions are neither purely clinical nor purely operational, but instead exist in the space between medicine and systems design.
Increasingly, this work appears under titles such as Chief Medical Officer, Chief Clinical Officer, Clinical Strategy Lead, or fractional executive leadership positions that did not exist in healthcare a decade ago. The titles vary considerably. The underlying function is remarkably similar.
Healthcare systems require architecture - someone eventually has to draw the blueprint.
The Next Competitive Advantage
As I’ve written before, the first generation of women’s health innovation focused largely on visibility - conditions that had historically been minimized suddenly receiving attention. The second generation focused on access, using telemedicine, consumer branding, and digital platforms to reduce friction between patients and care.
The next phase may focus on coherence.
As women’s health companies mature, the challenge is no longer simply attracting patients or delivering prescriptions efficiently. The challenge becomes maintaining quality as complexity accumulates. Access can scale quickly. Expertise, however, scales more slowly. Clinical judgment scales more slowly still.
This is one reason clinical architecture may become increasingly important over the next decade. The organizations that succeed may not necessarily be those with the largest marketing budgets or the most sophisticated technology stacks. They may be the organizations that build systems capable of preserving expertise even as those systems expand.
For much of modern healthcare, the limiting factor was access to information. Increasingly, the limiting factor may be how effectively organizations organize that information into coherent clinical systems. Hospitals learned this lesson decades ago. Digital health companies may simply be arriving there by a different route.
Buildings require architects long before the first patient walks through the door.
Healthcare systems may not be all that different.
Corey R. Babb, DO, FACOOG, IF, MSCP