Intelligent by Design designs a healthcare facility's operating system first — workflows, staffing, technology, and governance, fully defined before a new building is designed, or redesigned inside one already running — instead of being pieced together informally after it opens.
These are outcomes Intelligent by Design is engineered to produce, not certified results. Figures are planning hypotheses used to model current engagements — not guaranteed. Results vary by scope, region, and regulatory context.
On most healthcare facility projects, architecture is deliberately designed — and the operating system isn't designed at all. No one sits down and defines it end to end, whether before a new building goes up or at any point after it opens. It accumulates informally: each department works out its own workflows, its own workarounds, its own version of how things get done, largely in isolation from the department next to it. The result isn't a coordinated operating model — it's years of siloed, ad hoc improvisation, bent around a floor plan none of it had any say in.
Intelligent by Design (IBD) defines a healthcare facility's full operating system before a design brief is written: its nomenclature and master data, its process workflows, how work is allocated across people, AI, and automation, its digital architecture, its governance and SOPs, and its staffing blueprint. That operating system is then translated into the physical design brief — so the building is sized, shaped, and organized around how the facility will actually run.
Intelligent by Design is not an architecture firm, an engineering firm, or a healthcare facility planning firm, and it does not compete with any of them. IBD defines the facility's operating system — workflows, staffing, technology, governance — and hands it to the architects, engineers, and planners already on the project as a design brief they build from. Their expertise still designs the building. IBD makes sure that building is designed around how the facility will actually run.
Design the building — form, adjacencies, structure, code compliance — using the IBD operating system as their brief, not a set of instructions that overrides their judgment.
Design the MEP, structural, and infrastructure systems the building needs, informed by an operating model that's already been defined rather than assumed.
Continue to lead space programming and functional planning — now working from a fully defined operating system, instead of the industry's usual mix of benchmarks and assumptions.
Defines the operating system before any of the above begins — a step that, across three decades of running healthcare operations, has never before existed as a discipline of its own.
IBD is applied at the planning stage of new healthcare facilities and health-network developments — before ground is broken, where decisions about systems can still shape the physical design. The same methodology runs in reverse against a hospital that already stands, redesigning the operating system inside the walls that already exist. See Existing Hospitals for how that works.
Human, AI, and automation task allocation is planned block by block, so the facility runs on AI and automation from opening day — not as a bolt-on system added after go-live.
Digital, cyber, and AI governance is a cross-cutting layer across every planning block, so security and resilience are built into the architecture, not audited in afterward.
Every planning block is cross-checked against a regulatory and accreditation crosswalk, so the operating system is designed to pass inspection, not just to look good on paper.
Developed from decades of running healthcare operations across multiple health systems and countries — not a theoretical framework applied from the outside.
Most healthcare facilities spend years informally assembling, department by department, an operating system nobody designed — workflows that don't fit the space, systems that don't talk to each other, policies written to match whatever the building already forces them to do, compliance gaps discovered under survey pressure. IBD is built to close all of that, whether at the blueprint stage or inside a hospital that's already running.
Workflows, escalation, and accountability are decided before staffing and space are fixed — closing the handoff gaps and workaround culture that drive most patient-safety incidents at the blueprint stage, not after opening.
Patient flow and digital systems are mapped and integrated before individual systems are procured, removing the fragmented handoffs and redundant steps that drive avoidable length of stay.
Space is sized to real task allocation and workflow, not generic bed-to-department ratios.
Fifteen domains, cross-walked against JCI, Magnet, CAP, HIMSS, ISO, NIST, WHO, and more — designed in from Block 0, not chased after opening.
A single shared data model and vocabulary is established before any system is selected — removing the reconciliation problems that come from systems chosen independently.
Digital, cyber, and AI governance is a cross-cutting layer from Block 0 — built into workflows and access design, not layered onto a finished network.
Task allocation across people, AI, and automation is decided before staffing and digital architecture are finalized — so AI is structural to how work gets done, not bolted onto existing roles.
Space, staffing, and systems are sized to the real operating model from Block 0 — avoiding the retrofits that inflate lifetime cost in conventionally planned healthcare facilities.
RolesCOO, Johns Hopkins Medicine International–UAE · EVP, Althea International (Europe, India, China) · Deputy Director/COO, Bangkok Dusit Medical Services · COO, Kuwait Hospital
TodaySpecial Envoy for AI & Synthetic Workforce Development, Arab Hospitals Federation · AI & healthcare-operations research with the World Health Organization
Fifteen compliance domains, mapped and cross-walked against JCI, Magnet, CAP, HIMSS, ISO, NIST, and more — designed into the operating system from Block 0, not bolted on after opening.
See how the 8 planning blocks and 5 cross-cutting layers fit together — and where architectural translation comes in.
View the methodologyIBD is a prerequisite for enterprise AI readiness and cyber resilience because both depend on the same thing most hospitals lack: a deliberately designed operating system.
The claim concerns enterprise AI — deployed at scale, across departments, embedded in core operations. That kind of AI does not succeed because a hospital buys models, licenses software, or hires data scientists. It requires clear workflows, clean data, consistent nomenclature, mapped decision rights, defined clinical pathways, accountable governance, reliable documentation, interoperable systems, and a workforce model that knows where AI fits into real work. Without that foundation, AI automates confusion: more alerts, more dashboards, more exceptions, more liability, more workarounds.
Cyber resilience has the same dependency. A hospital cannot protect what it has not defined. If roles, systems, data flows, devices, vendors, access rights, handoffs, escalation pathways, downtime procedures, and operational dependencies are unmapped, the cyber program can only react. The organization may have tools, policies, and audits — but not resilience. A breach becomes an operational failure, not just a technical event.
IBD addresses this by designing the hospital operating system first, before layering on AI and digital tools. It defines how the hospital works: who does what, with what information, through which systems, under which controls, with what governance, and with what fallback procedures.
Without a designed operating system, AI at scale sits on top of operational disorder.
Without a designed operating system, cybersecurity defends something the organization does not fully understand.
IBD makes the hospital knowable, governable, standardizable, monitorable, and improvable. That is the precondition for both.