Methodology

Eight planning blocks. Five cross-cutting layers.

Intelligent by Design structures healthcare facility planning as a sequence of operating-system decisions, checked continuously against regulation, cost, risk, cyber resilience, and sustainability — producing AI-native, cyber-resilient healthcare facilities with architecture as the final block, not the first.

Planning blocks

The sequence, block by block.

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.

0

Scope Definition

Establishes the facility's mandate — clinical scope, capacity targets, region, and the constraints the rest of the methodology will plan within.

1

Nomenclature, MDM, Ontology & Knowledge Graph

A shared vocabulary and master data structure for the healthcare facility — the foundation every later block and system reads from.

2

Process & Workflow Mapping

Maps clinical and operational workflows end to end, so the facility's real processes — not assumptions about them — drive design.

3

Human–AI–Automation–Robotics Task Allocation

Decides, task by task, what's done by people, by AI, or by automation — the basis for staffing, digital architecture, and space.

4

Digital Architecture

Defines the systems, integrations, and data flows needed to run the workflows and task allocation from Blocks 2 and 3.

5

Policies, SOPs & Governance

Turns the operating model into the policies, standard operating procedures, and governance structures a healthcare facility needs to run and be accredited.

6

AI-Native Staffing Blueprint

Translates task allocation into a staffing plan and org design — roles, headcount, and skill mix for how the facility will actually be run.

7
The final block, not the first

Architectural Translation

Converts the completed operating system into a physical design brief — space program, adjacencies, and infrastructure requirements for the architect. Everything above it has to be decided before this block starts.

This block hands the brief to the project's architects, engineers, and planners — it does not replace their work. They still design the building; IBD makes sure the brief they're designing from reflects how the facility will actually run.

Cross-cutting layers

Checked continuously, not bolted on at the end.

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.

Regulatory & Accreditation

Crosswalks every planning decision against the regulatory and accreditation requirements of the facility's jurisdiction.

Digital, Cyber & AI Governance

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.

Financial & Lifetime Cost

Models cost across the facility's full lifecycle, not just capital cost at the point of design.

Risk & Safety

Identifies and mitigates operational and patient-safety risk as the operating system is being defined, not after it's built.

Sustainability

Applies sustainability considerations to workflows, staffing, digital architecture, and the eventual physical footprint.

Planning hypotheses

What the sequence is designed to achieve.

IBD engagements are modeled against two planning hypotheses, used to size the impact of an operations-first approach before construction:

  • 20–35% reduction in administrative and documentation FTE load, from re-allocating tasks across people, AI, and automation.
  • 20–30% footprint reduction versus conventional healthcare facility planning, from designing space around actual workflow and task allocation rather than convention.

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.

Scope & boundaries

Where IBD applies today.

IBD applies in two directions: to new facilities and health-network developments, planned from the ground up, and to existing healthcare facilities, run in reverse against a live building instead of a blank site. See Existing Hospitals for how the diagnostic works and what it produces.

IBD does not replace the architects, engineers, or healthcare facility planning firms on a project, and is not scoped to do their work. It is scoped to do work none of them are engaged to do: define the operating system those disciplines then design, engineer, and plan around.

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. This is no longer optional groundwork: a healthcare facility without this foundation will struggle to implement AI at the enterprise level, and is likely to remain significantly exposed to cyber attack no matter how much security technology is added after opening.