Intelligent by Design structures hospital planning as a sequence of operating-system decisions, checked continuously against regulation, cost, risk, cyber resilience, and sustainability — producing AI-native, cyber-resilient hospitals with architecture as the final block, not the first.
Each block builds on the one before it. Architectural translation — Block 7 — is where the operating system becomes a physical design brief, not where planning begins.
Establishes the facility's mandate — clinical scope, capacity targets, region, and the constraints the rest of the methodology will plan within.
A shared vocabulary and master data structure for the hospital — the foundation every later block and system reads from.
Maps clinical and operational workflows end to end, so the hospital's real processes — not assumptions about them — drive design.
Decides, task by task, what's done by people, by AI, or by automation — the basis for staffing, digital architecture, and space.
Defines the systems, integrations, and data flows needed to run the workflows and task allocation from Blocks 2 and 3.
Turns the operating model into the policies, standard operating procedures, and governance structures a hospital needs to run and be accredited.
Translates task allocation into a staffing plan and org design — roles, headcount, and skill mix for how the hospital will actually be run.
Converts the completed operating system into a physical design brief — space program, adjacencies, and infrastructure requirements for the architect.
Five layers run across every planning block, so compliance, cost, risk, governance, and sustainability are part of each decision — not a review that happens after the plan is finished.
Crosswalks every planning decision against the regulatory and accreditation requirements of the facility's jurisdiction.
Governs how digital systems, data, and AI are deployed and controlled across the operating system — building cyber resilience into the architecture from Block 0, not auditing it in after go-live.
Models cost across the facility's full lifecycle, not just capital cost at the point of design.
Identifies and mitigates operational and patient-safety risk as the operating system is being defined, not after it's built.
Applies sustainability considerations to workflows, staffing, digital architecture, and the eventual physical footprint.
IBD engagements are modeled against two planning hypotheses, used to size the impact of an operations-first approach before construction:
These are planning targets used to model current engagements, not guaranteed outcomes — actual results depend on scope, regulatory context, and how fully a project adopts the methodology.
IBD is scoped to greenfield hospital and health-network planning — new facilities, planned from the ground up. An IBD-Retrofit variant, adapted for existing hospitals, has been identified as a future direction but is not yet part of the methodology.
AI-native, cyber-resilient design is the target state an IBD engagement is built toward — the Human-AI-Automation-Robotics task allocation block and the Digital, Cyber & AI Governance layer exist specifically to produce it. The same sequence of planning blocks still adds structure and value in projects with a lighter AI footprint.