Sam Shahsavani
Back
B+H Architects logo
B+H / Healthcare BIM Data

BIM data orchestration for hospital rooms

On the Halifax Infirmary Expansion, I managed the B+H-side Revit-to-dRofus workflow that connected room content, equipment data, QA, and Room Data Reports.

Core Idea

A hospital room is not just geometry. It is also linked equipment, finishes, doors, windows, accessories, quantities, and database records.

Output

Room Data Reports turned room-by-room model and planning data into submission-ready information.

Content Layer

Families needed the right geometry, shared parameters, item IDs, and dRofus links before reports could work.

Data QA

The work included finding ghost data, duplicate geometry, door/window drift, and unlinked content before submission.

Team Alignment

I translated the workflow into an internal explainer so the team could see why small data errors mattered.

Why It Mattered

The report is only as trustworthy as the hidden data behind it.

Room Data Reports look like a finished output, but they depend on every upstream handoff: families, shared parameters, dRofus IDs, room placement, schedules, and QA.

01

Need Identified

A room, equipment item, accessory, door, or finish requirement enters the workflow through project coordination, requests, cutsheets, or planning data.

02

Content Created

Revit families are built or refined with the shared parameters required by the project database schema.

03

Content Managed

UNIFI and dRofus help keep the content request, library, item identity, and planning data connected.

04

Placed In Revit

Families are placed in the architectural model so geometry, room context, and schedules reflect the current design.

05

Linked + QA'd

The model is checked against dRofus for missing links, duplicate items, stale quantities, and mismatched identifiers.

06

Reported

Room Data Reports aggregate the current room state into a deliverable that the builder and project team can use.

Content Management

From request to usable model content

The content side was the foundation: understand the requirement, build the family, carry the right parameters, and make sure it could be placed and recognized downstream.

UNIFI content request form for a Revit family
A content request translating a project need into a family creation task.
Equipment cutsheet used as a reference for BIM content
Cutsheets and manufacturer information became modeling and parameter inputs.
Revit equipment family linework
Digital content had to work as geometry and as structured data.
Revit room model with equipment and wall protection
Placed content carried spatial context and room-specific implications.
Data Management

More than syncing

The data work was in the mismatches: missing links, old quantities, duplicate geometry, door/window changes, and records that no longer reflected the current model.

dRofus equipment item table
dRofus view showing how item numbers, BIM IDs, and planning data were connected.
Door schedule discrepancy log
Schedule discrepancy log from the same data-integrity problem.
Revit plan showing accessory placement
Plan/model context helped verify that report data matched the current design.
Accessory Utility Data Report spreadsheet screenshot
AUDR spreadsheet view showing aggregated accessory quantities and report structure.
Output

Room Data Reports made the invisible workflow visible.

The RDR pulls the whole workflow into one room-level output. The report pages below reconstruct the report format with modified values, paired with the AUDR view shown above.

Nova ScotiaNova Scotia Health

Room Data Report - RDR

PCL Submission - Ver 3.2

HIEP
Public Sample Project
Room Number
08-02.01
Room Name
Consult / Exam Room
Department
Public Sample Clinical Unit
Room Classification
RC-270 · Modified sample
Model Name
HIEP-PUBLIC-SAMPLE

Areas

NameValueRFI Number
Programmed Area130.00PUB-RFI-001
Designed Area130.87PUB-RFI-002
Area Variance %.67PUB-RFI-003

RDS

GroupValueRFI Number
Ceiling Height2700 mmPUB-RFI-011
RFI ShieldingRadiation shielding: noPUB-RFI-012

Acoustics

NameValueRFI Number
Room STC50PUB-RFI-021
NC Rating and Reverberation TimeRefer to acoustic performance sectionPUB-RFI-022

Wall Protection

GroupNameRFI Number
Sheet ProtectionSR-215 mmPUB-RFI-026
Sheet Behind SinkPVCu-215 mmPUB-RFI-027

Room Finishes

BIM IDNameRFI Number
EF-1Epoxy flooring, multicolourPUB-FIN-031
INC-1Integral cove base, 150 mm heightPUB-FIN-032
PTPaint, washable latexPUB-FIN-033
GWB-2Moisture-resistant gypsum boardPUB-FIN-034
EP-5Paint, epoxyPUB-FIN-035
GB-2Moisture-resistant ceiling boardPUB-FIN-036
4/17/2026 12:00 PM
public.sample@portfolio.local
Generated by dRofus © 2023-2024 Arcadis Inc.
Page 01
Reconstructed report format with modified room names, IDs, references, and values to show the structure without exposing project records.
Nova ScotiaNova Scotia Health

Room Data Report - RDR

PCL Submission - Ver 3.2

HIEP
Public Sample Project
Room Number
08-02.01
Room Name
Consult / Exam Room
Department
Public Sample Clinical Unit
Room Classification
RC-270 · Modified sample
Model Name
HIEP-PUBLIC-SAMPLE

Doors

NameNumberFramePanelQTY
Single 1220x2135D-08-021-A45 STO-105.7501P01 / P51

Interior Windows

NameNumberFrameGlazingTreatment
No interior window----

Millwork

NameYesNo
Millwork in roomx

Stainless Steel Casework / Modular Casework

Item GroupBIM IDNameQTY
LowerSBS-1Base cabinet, sample1
UpperSOFWall cabinet, sample1

MEP-01

BIM IDName
A-HBR-00Refer to abbreviations and definitions
A-PLU-00Plumbing fixtures: assignment schedule
CHM-2Chemical room: no
CSH-1Sprinkler head type: concealed
LTG3Lighting target type: solid rooms
4/17/2026 12:00 PM
public.sample@portfolio.local
Generated by dRofus © 2023-2024 Arcadis Inc.
Page 02
Reconstructed report format with modified room names, IDs, references, and values to show the structure without exposing project records.
Nova ScotiaNova Scotia Health

Room Data Report - RDR

PCL Submission - Ver 3.2

HIEP
Public Sample Project
Room Number
08-02.01
Room Name
Consult / Exam Room
Department
Public Sample Clinical Unit
Room Classification
RC-270 · Modified sample
Model Name
HIEP-PUBLIC-SAMPLE

Lighting

BIM IDName
LT06Lighting type 06 · Direct lighting
FAT00Fire alarm type 00 · No FA

HVAC

BIM IDName
HVAC-1Clinical support space · solid utility
TEMPTemperature monitor: yes
EXHExhaust requirement: standard
ALMAlarm action: N/A

Hand Hygiene Sink

BIM IDName
HHS-1Hand hygiene sink
EW-1Emergency eyewash · wall
S-5Sink · hopper

ICAT-01

BIM IDName
NC-0Nurse call: no nurse call
VS0Video surveillance: none
PB00Panic button: none
A-DATA-00Data drop quantities by room type
4/17/2026 12:00 PM
public.sample@portfolio.local
Generated by dRofus © 2023-2024 Arcadis Inc.
Page 03
Reconstructed report format with modified room names, IDs, references, and values to show the structure without exposing project records.
Nova ScotiaNova Scotia Health

Room Data Report - RDR

PCL Submission - Ver 3.2

HIEP
Public Sample Project
Room Number
08-02.01
Room Name
Consult / Exam Room
Department
Public Sample Clinical Unit
Room Classification
RC-270 · Modified sample
Model Name
HIEP-PUBLIC-SAMPLE

Accessories

BIM IDNameQuantity
A-1Paper towel dispenser2
A-2Hand sanitizer dispenser1
A-3Soap dispenser with drip tray2
A-4Waste receptacle1

Report QA

CheckResult
dRofus linkMatched to current public sample room record
Quantity checkNo duplicate accessories in sample room
4/17/2026 12:00 PM
public.sample@portfolio.local
Generated by dRofus © 2023-2024 Arcadis Inc.
Page 04
Reconstructed report format with modified room names, IDs, references, and values to show the structure without exposing project records.
Full Cycle

The journey of an accessory

This diagram is simple, but it is the best explanation of the system: need, family creation, Revit placement, dRofus QA, aggregation, and report output.

Diagram showing the accessory journey from need to Room Data Report
The original internal diagram that made the accessory workflow understandable to the team.
Scope

One defined workflow inside a larger delivery system.

My role focused on B+H-side data workflow leadership: content, links, QA, reports, and team communication within a larger multi-firm delivery structure.

Role Boundary

One side of a multi-firm system, run end to end

My role covered the B+H-side workflow under Arcadis as prime consultant: content, links, QA, reports, and coordination across the room-data handoff.

Workflow

A source-of-truth workflow between content, data, QA, and reports

The work connected Revit families, shared parameters, dRofus records, placement checks, discrepancy cleanup, and Room Data Report outputs.

Operating Pattern

Messy AEC data systems become useful when the hidden dependencies are made visible.

The work depended on understanding the source-of-truth problem, keeping content and data aligned, QAing the handoffs, and explaining the system clearly enough for a team to use it.