Original illustration of a generic UK hospital. Not a real building or any specific hospital.
Welcome. Let's walk through the hospital together.
Step inside to see how a device-transition rehearsal could be organised, level by level, through to the bed space.
Whole-hospital deployment map: Example hospital working prototypeWhole-hospital deployment map: interactive demonstrator
How a short peripheral catheter (SPC) device-transition rehearsal for IV Cannulation could be organised across Example hospital: level by level, via lift banks B, C and D, down to a local training base, the bed space and each rehearsal stage.
How a short peripheral catheter (SPC) device-transition rehearsal for IV Cannulation could be organised across a hospital: level by level, via its lift banks, down to a local training base, the bed space and each rehearsal stage.
Seven levels, three lift banks
Illustrative example layout with synthetic department and status data. Drag to pan when zoomed.
Close scene: illustrative ward room not a specific ward
Example context: select a ward on the map
An illustrative ward room with a bed space, staff base, local training base and equipment trolley. Drag to rotate, scroll or pinch to zoom, or use the 2D view. The stage you choose below changes both this room and the whole-hospital map.
Briefing, demonstration, supported practice, local review
Stage and status content is illustrative and remains subject to clinical and operational review.
How a surge could run across three hospitals
An illustrative planning model for discussion. Every element remains subject to capacity, cost, governance and each organisation's agreement.
Three hospitals in parallel
Planning assumption only, subject to capacity and cost. No other sites are named or agreed.
Two-week surge, then return
Steps 1 to 3 run in the two-week surge. Step 4 is a return visit.
- Readiness and access checks
Confirm logins, resources, kit and the base before teaching starts. - Embedded high-volume practice
Supported practice on wards and at the base, shift by shift. - Pop-up fairs
Drop-in sessions in agreed spaces for staff who cannot be released. - Return review and scoop-up sessions
Local review, then follow-up sessions for anyone missed. Timing to agree.
Common access blockers to check
- App and learning resource awareness
- Passwords and account access
- Permissions to reach the right resources
- Staff returning from leave
Checked during readiness, and again at scoop-up sessions.
Distributed trainer network
Lead trainer with local trainers (blue). Subject to availability, rates, travel and governance.
Funding decision panel
Mark which party could cover each item, as a starting point for discussion. Nothing is agreed and no prices are shown. Selections stay in this browser view only.
| Item | Supplier | Trust | VeinTrain | Status |
|---|
Stakeholder discovery
Risks to plan for
- Operational pressure may limit how many staff can be released.
- Backlog may compete for space, staff time and attention.
- Leave and shift patterns may leave gaps that need scoop-up sessions.
- Access blockers may delay digital learning.
Risks to plan for, not promised outcomes. The rehearsal is not presented as a way to reduce backlog.
Device discovery questions
- Ported or portless SPC: which is in use or planned locally?
- Extension sets: which are in use, and is any change planned?
- Ultrasound: is ultrasound-guided cannulation in scope locally, and who leads it?
- Integrated devices: are integrated systems being considered?
Discovery questions only, not recommendations. Device and technique choices sit with the organisation, local policy and the IFU.
Base and logistics concepts
- Secure week-long pop-up base (location to confirm, not shown on the demonstrator)
- Secure overnight storage
- Optional external container, subject to site approval, security, access and local policy
- Mobile / pop-up practice kit
- Volunteer welcome and wayfinding (concept)
Queued later work (not built)
Queued until the hospital-location model is agreed. Not built in this version.
Queued for later. Not built or animated in this version.
Scope, status markers and next steps
Source note (generic mode)
This unlisted preview uses a fictional hospital and synthetic status data. It demonstrates interaction and deployment logic only.
What the markers mean
- Map only
- area ref number for that floor · dashed: proposed HALO overlay
- Training
- rehearsal stages completed · in progress or scheduled · follow-up rehearsal needed · not started
- Stock and devices
- practice kit and devices available · partial or awaiting delivery · not available yet
- Readiness
- ready for local sign-off discussion · actions open · not ready, issues routed · pending local review
- Support areas
- public or support areas. No status.
Status lenses use synthetic demo data and fictional area labels to show how a dashboard could work. They do not describe any real hospital.
Deployment note
- Asset ID
VT-HALO-HOSPITAL-DEMONSTRATOR-PREVIEW- Version
0.3.2·unlisted-public-preview-noindex- Source file
HALO Whole Hospital Deployment Demonstrator v0.3.html. Builds on v0.2 (unchanged).- Planned events
vt_halo_hospital_open,vt_halo_ward_open,vt_halo_rehearsal_play,vt_halo_register_interest- Fathom
- Pending. No verified site ID. This page never loads the Fathom script; it only calls an existing
window.fathomonce enabled. No learner or patient details are sent. - Release state
- Unlisted VeinTrain server preview. This page remains
noindexand is not linked into the HALO Intelligence Hub.
Event log (this preview, no data sent)
No events yet.