BIMinAM Healthcare Workstream Meeting 01-04-2026

BIMINAM HEALTHCARE WORKSTREAM MEETING, 01-04-2026

Date: 1 April 2026

Purpose of the Session

The session continued development of a minimum viable data and validation framework for asset information, specifically for fire-critical and operational assets in healthcare environments. The objective was to define what information must be available to a competent person at the point of work, and to establish a standardised schema and validation model that can support safety, compliance and operational effectiveness.

Key Themes from the Transcript

  1. Defining a standard schema for asset information

The session builds on previous workstreams (residential and education) to create a common, cross-sector structure for asset information.

The core framework follows four stages:

  • Identify – locate and define the asset
  • Understand – know what the asset is and how it performs
  • Work – enable safe execution of tasks
  • Prove – provide evidence of compliant completion

This structure is intended to form a repeatable, industry-wide schema for the Golden Thread.

  1. Focus on the person “walking in the door”

A critical principle is that the model should reflect:

what a competent individual needs at the point of intervention

This includes:

  • precise asset location (including coordinates and context)
  • asset identity, criticality and constraints
  • safety requirements (PPE, permits, hazards)
  • clear understanding of task purpose and scope

The emphasis is on practical usability, not theoretical completeness.

  1. Expanding asset definition – physical and digital

The discussion highlighted the growing need to include digital asset attributes, such as:

  • MAC address / IP address for connected devices
  • IoT-enabled monitoring systems
  • dynamic relationships between assets, automation and AI systems

This reflects a shift toward digitally connected and intelligent building systems, particularly relevant in healthcare environments.

  1. Understanding systems, dependencies and context

Participants emphasised that assets must be understood within their system context, including:

  • parent-child relationships between components
  • dependencies across systems (e.g. fire, HVAC, controls)
  • cause-and-effect implications of interventions

This ensures that work is carried out safely without unintended consequences.

  1. Gap between current practice and required standard

A strong consensus emerged that:

  • current industry practice delivers only a small fraction of required information
  • many engineers attend site with minimal context or data
  • critical information is often missing, incomplete or not updated

This represents a significant risk to safety, compliance and efficiency.

  1. “As-built” definition and accountability challenges

The session highlighted ambiguity around “as-built” information, including:

  • reluctance of designers to certify drawings as accurate
  • gaps between design intent and actual installation
  • lack of ownership for updating records during construction

There was strong agreement that:

  • the principal contractor should hold responsibility for maintaining accurate, updated information
  • mechanisms are needed to ensure change control and verification throughout delivery.
  1. Linking data structure to process and tasks

The discussion introduced a more structured, process-driven approach:

  • defining inputs, processes and outputs
  • assigning roles and responsibilities (RACI)
  • creating task-based checklists and workflows

This approach supports:

  • consistent execution
  • traceability
  • integration into digital systems (e.g. CAFM, CDE)
  1. Balancing completeness and simplicity

A key tension identified was:

  • the need for comprehensive data
    vs
  • the need for simplicity and usability

The group emphasised that:

  • over-complex models risk low adoption
  • data should be structured so it can be filtered, derived or automated, rather than manually captured in full

Key Insights from the Chat

  • Need to prioritise data based on importance and compliance (e.g. MoSCoW method)
  • Importance of cause-and-effect understanding when working on assets
  • Recognition that information should support both manager-level planning and engineer-level execution
  • Emphasis on checklists and acceptance criteria to ensure completeness
  • Requirement to update models, drawings, CAFM systems and asset registers as part of the workflow

Overall Conclusion

The session reinforced that delivering the Golden Thread in healthcare requires a standardised, task-driven schema for asset information, focused on real-world usability at the point of work.

The emerging model:

  • defines minimum, structured data requirements
  • integrates physical and digital asset attributes
  • links information to tasks, roles and validation processes
  • highlights significant gaps in current industry practice

Ultimately, the success of this approach depends on balancing completeness with simplicity, ensuring that information is both available and usable, and embedding accountability across the lifecycle to deliver safe, compliant and effective healthcare environments.