Lesson 0.3Lesson 0.3 · Why Healthcare Design Is Different
The Brief & the Healthcare Team
A hospital is briefed and built by a large specialist team - healthcare planners, clinicians, MEP and equipment engineers, infection-control experts - and the architect's job is to orchestrate all of it into one coherent building
A house can be briefed over coffee; a hospital is briefed by a small army - and the architect's job is not to know everything, but to orchestrate everyone.
Ask who designs a hospital and the honest answer is: not the architect alone, and not even mostly the architect. A hospital is briefed and designed by a large, specialist, multidisciplinary team - healthcare planners who turn a model of care into a schedule of rooms, the clinicians who will use each space, mechanical and electrical engineers whose systems rival the building in size, a medical-equipment planner, an infection-control specialist, structural and fire engineers, and more - working to a brief that arrives as a structured, evolving document rather than a conversation.
This raises a real question: if so much of the knowledge sits with specialists, what exactly is the architect for? The answer is the hardest role on the project - the orchestrator, the one who holds the whole building in mind and integrates every expert contribution into a single coherent, humane, buildable place, and who guards the patient's experience amid a process that pulls relentlessly toward the merely technical. This lesson is about that brief, that team, and that integrating role.
Hospital briefed by a team: model of care -> schedule -> room data sheets. Architect = orchestrator, not soloist.
Where the brief comes from
A house can be briefed in a conversation. A hospital cannot. Its brief is a large, structured, evolving document produced by specialists long before - and alongside - the architect, and learning to read and shape it is one of the first professional skills of healthcare design.
The brief does not begin with rooms. It begins with a model of care and a set of operational policies: decisions about how this hospital will actually work - what services it will offer, how many patients of what kinds, whether it runs centralised or decentralised sterile services, how patients flow from emergency to theatre to ward, whether it uses single rooms or open bays, how it staffs at night. These operational choices are made by the client - the health authority, trust or hospital group - usually with a specialist healthcare planner, and they drive everything the architect will draw. A plan is only as good as the model of care it serves; design a beautiful ward for an operational policy nobody intends to follow and you have designed the wrong building.
From the model of care flows the functional brief and the schedule of accommodation (sometimes called the schedule of spaces): the list of every department, every room, how many of each, and their approximate sizes and relationships. This is the skeleton of the hospital expressed as content rather than form. Below that sit room data sheets (or room layout sheets) - a document for each room type specifying its fittings, furniture, equipment, services (power, data, medical gases, drainage), environmental conditions and finishes, so that a single-bed room or an operating theatre is defined consistently wherever it appears.
The crucial point for the designer is that much of the 'what' of a hospital arrives as a given, generated by clinical and operational expertise, not invented at the drawing board. The architect's art is turning that content into a working, humane, buildable whole - and challenging the brief intelligently where the architecture reveals a better way. Treat every figure in these documents as typical guidance to verify against the current standards, the health authority and the specialists, never as a universal truth.
The brief starts with the model of care, not the rooms. Content before form.
The specialist team
No single person holds all the knowledge a hospital needs. It is designed by a large, specialist, multidisciplinary team, and understanding who does what - and respecting it - is essential.
At the centre of the clinical knowledge is the healthcare planner (sometimes a medical planner), a specialist - often with a clinical or architectural background - who translates the model of care into functional content, adjacencies and room requirements, and who is the architect's closest partner on the clinical logic. Around them are the clinicians and user groups: the doctors, nurses, heads of department and other staff who will actually use each space, consulted in structured user-group meetings to test and refine the design against the reality of their work. Their knowledge of how a department really operates is irreplaceable - and it is the designer's job to listen, synthesise and sometimes gently challenge.
The engineering team is unusually large for a hospital. MEP engineers (mechanical, electrical, and plumbing or public-health) design the ventilation, medical gas pipelines, power and standby power, water, drainage and the rest - systems that, as Lesson 0.1 noted, can rival the architecture in size. A dedicated medical-equipment planner coordinates the vast inventory of clinical equipment, from beds to CT scanners, much of which is heavy, hot, shielded, serviced and fast-changing (Module 7.4). An infection-control specialist advises on everything from isolation rooms and airflow to surfaces and handwashing. Structural and fire/life-safety engineers address the special problems of long-span, heavily-serviced, disaster-resilient buildings full of non-ambulant patients (Module 7). Cost consultants, commissioning specialists, acousticians, accessibility and wayfinding experts, and the eventual contractor all join.
TYPICAL HEALTHCARE DESIGN TEAM (composition varies)
- Client / health authority ..... owns the brief, the money, the decision
- Healthcare / medical planner .. model of care -> functional content
- Clinicians + user groups ...... how each department really works
- Architect ..................... integrates all of it into the building
- MEP + public-health engineers . ventilation, gases, power, water
- Medical-equipment planner ..... the clinical equipment inventory
- Infection-control specialist ... isolation, airflow, surfaces
- Structural + fire engineers .... resilient, compartmented structure
- Cost, commissioning, access .... buildability, validation, inclusionThe exact make-up varies by project, country and the demands of the accreditation body; treat this list as typical and confirm the roles your project and its standards actually require.
The architect as orchestrator
If so much expertise sits with others, what is the architect for? The answer is the most demanding role of all: the architect is the orchestrator - the one who holds the whole in mind and integrates every specialist contribution into a single, coherent, humane, buildable building. An orchestra of brilliant soloists with no conductor produces noise; a hospital designed by brilliant specialists with no integrating architect produces a building that fails at the seams, where the ventilation fights the structure, the equipment does not fit the room, and the flows cross.
The architect's integrating work has several faces. First, translation: turning the clinical and operational brief - the model of care, the schedule of accommodation, the room data sheets - into real plans, sections, adjacencies and flows (Module 1). Second, coordination: reconciling the demands of the MEP engineers, the equipment planner, the structural and fire engineers and the infection-control specialist so that their systems fit together in the same ceiling void, the same shaft, the same room - which is why hospitals lean on disciplined planning grids and generous service zones (Module 1.4). Third, consultation: running the user-group process, listening to clinicians, and synthesising dozens of strong, sometimes conflicting opinions into decisions. Fourth, and easily lost: being the guardian of the patient's experience and dignity, and of the building as architecture, amid a process that relentlessly pulls toward the merely technical.
Crucially, orchestrating does not mean pretending to be every specialist. A good healthcare architect becomes fluent enough in clinical operation, engineering and infection control to ask the right questions, coordinate intelligently and challenge when something is wrong - but knows exactly where their own knowledge ends and defers the binding specifics (air-change rates, gas capacities, radiation shielding, accreditation criteria) to the people and the codes that govern them. Leading well is largely knowing what you must verify with others, and building the collaboration that lets the whole team do its best work.
Architect = conductor. Integrate the specialists; guard the patient; know what to verify.
The living brief - iteration, change and verification
A final thing to understand about the hospital brief: it is not a document handed over once and then obeyed. It is a living agreement that evolves through design, and managing that evolution is part of the work.
Design proceeds as a dialogue with the brief. The architect produces a scheme; the user groups review it against how they actually work; the brief is refined; the scheme changes; and round it goes. Clinical knowledge and technology move during the years a hospital takes to design and build, so the brief that is right at the start may be wrong by completion - another reason hospitals are designed for change (Module 1.4). To keep this iteration from becoming chaos, projects use disciplined controls: design freezes at agreed stages, after which changes must be formally justified; derogations - documented, approved departures from a standard where a project has a good reason; and clear sign-off, so that everyone knows what has been agreed and by whom.
This is also where the course's accuracy rule lives in daily practice. The brief and its room data sheets will cite specific figures - areas, clearances, air changes, numbers of sockets and gas outlets. Treat them as project-specific requirements to verify, not universal truths. They derive from the operational policy, the health authority and the current standards - in India the National Building Code, the NABH accreditation standards and the relevant IS codes; globally the FGI Guidelines, the UK HBN/HTM series and WHO guidance - and they can and do change between editions and projects. The designer's discipline is to design to the agreed brief, to coordinate the specialists who own each figure, and to confirm the binding specifics against the current standard and the relevant engineer before anything is built.
> The brief is how a hospital thinks before it is drawn. Read it as a living agreement between a model of care, a team of specialists and the codes - and your job is to integrate it into a building and to verify every binding figure with the people who own it.
Schedule of accommodation
The list of every department and room, with numbers and approximate sizes
The hospital as content before form; owned by the healthcare planner and client. Its figures are project-specific - verify against the current standards.
Room data sheet
Per-room-type specification of fittings, equipment, services and finishes
Keeps each room type consistent across a huge team; binding figures follow the standards and engineers. Confirm against the current editions.
Healthcare planner / user groups
The specialist who turns the model of care into content, and the clinicians who test it
The architect's closest clinical partners. Roles and titles vary by project and country; confirm the team your accreditation framework expects.
Workshop — assemble a team and read a brief fragment
Healthcare design is a team sport, and the brief is its playbook. This exercise has you assemble the specialist team for a small project, identify what each owns, and draft a tiny piece of a brief - practising both the collaboration and the discipline of verification.
None - paper and the ideas in this lesson. No real project or code values required.
Goal: understand the hospital team and the structure of a brief Inputs: a small healthcare project you can imagine (a clinic or small hospital) + paper Time: ~35 minutes
- 1For your small project, list the specialists you would need on the team, and beside each write the one kind of decision they own.
- 2For each specialist, write one binding figure or requirement you, as the architect, would defer to them rather than decide yourself.
- 3Take one room you understand well - say a single-bed inpatient room - and draft a mini 'room data sheet': its furniture, key equipment, services and finishes.
- 4Mark which entries on your sheet are binding figures you would verify against a code, accreditation standard or engineer, rather than fix yourself.
- 5Write one sentence on where, as the orchestrating architect, you would intelligently challenge the brief rather than simply obey it.
You’ll walk away with
A short team chart (who owns what, and what you defer to each), plus a mini room data sheet for one room with its binding figures flagged for verification.
Three altitudes on the same idea
Read the band that fits you — or all three.
Your role is orchestrator, not soloist. You turn the model of care, schedule of accommodation and room data sheets into plans, adjacencies and flows, and you coordinate the MEP, equipment, structural, fire and infection-control specialists so that their systems fit one building. Run the user-group process, guard the patient's experience and the architecture, and know precisely which binding figures you defer to the codes and the engineers who own them.
Join the team early and read the room data sheets. The finishes, furniture, lighting and colour you specify are set against each room type's agreed specification and must satisfy infection control, durability and the clinical brief, not taste alone. Sit in the user-group conversations, learn how each space is really used, and bring the humane, healing dimension to a process that otherwise drifts toward the purely technical.
A hospital is designed by a team, and the architect conducts it. Understanding who owns what - the healthcare planner, the clinicians, the MEP and equipment engineers, the infection-control specialist - teaches you the most collaborative, integrative side of architecture. The lesson for any building: the architect's power is not knowing everything, but integrating many experts into one coherent whole, and knowing what to verify with whom.
“The architect designs the hospital; the consultants just fill in the engineering and the doctors say what rooms they want.”
Do it yourself
No tools needed - reason it through.
- 1What is the difference between a model of care, a schedule of accommodation, and a room data sheet?
- 2Name four specialists on a hospital design team and one decision each owns.
- 3What does it mean to say the architect is the 'orchestrator' rather than the author of a hospital?
- 4Why is a hospital brief described as a 'living agreement', and what controls keep its evolution orderly?
- 5Why should you treat the figures in a room data sheet as typical guidance to verify rather than fixed truths?
The one line to carry out
Peer-reviewed journals & authoritative standards
- 01Hospital — Wikipedia, 2026.
- 02Architecture — Wikipedia, 2026.
- 03Accreditation — Wikipedia, 2026.
- 04National Accreditation Board for Hospitals & Healthcare Providers (NABH) — NABH, 2026.
With the team and the brief understood, the last piece of the mindset is the evidence that should drive the design - what the research shows about how buildings affect healing.
The author
Amogh N P
Architect, interior designer, and creative polymath. Studio Matrx began in his notebooks — his vision of design made honest, useful, and open to everyone. Its Academy is written and taught in his memory, and free, forever.
More about Amogh →