Mobile Imaging Fleet Operations
Site profiles without scanner reconfiguration.
Built for facility-based mobile programs
Flux Box makes a mobile imaging unit easy to run across many facilities — owned sites, partner locations, renovation and overflow coverage, screening events, and semi-permanent installs. It works for any modality on the coach — mammography, CT, MR, ultrasound, or general radiography — and the imaging device is configured once and always sends to the same local destination, so installers set it up a single time instead of reconfiguring the scanner at every stop.
Behind that single destination, Flux Box handles everything that changes between sites — PACS, worklist, routing, header rules, and delivery policy — and enforces each facility's safety rules automatically. The fleet is managed centrally, units move between facilities without truck rolls, and every study is protected before it leaves the box.
- Facilities change, scanner setup should not — Technologists should not manage a different PACS, worklist, AE title, or IP address at each stop.
- Overflow work is high pressure — Renovations, events, and capacity relief do not leave room for brittle network troubleshooting.
- Walk-ins and add-ons are real — Patients may not always appear on the active worklist before the exam starts.
Fleet safety layer
Five controls that make a mobile imaging fleet safe to operate
Flux Box gives each vehicle a stable local DICOM endpoint while Capacitor handles the profile, routing, worklist, and release decisions behind it.
Profile orchestration
Each facility gets its own operating profile.
A vehicle keeps the same scanner configuration everywhere. Flux Box activates the correct profile for the current facility and keeps inactive profiles out of the path.
- Fixed local AE titles, IPs, and ports on the acquisition device
- Per-site worklist, PACS, routing, compression, and tag rules
- Profiles can be started and stopped as isolated runtime containers
The mobile-ready feature set
Flux Box runs DICOM Capacitor as the routing and safety layer between the imaging device and the facility systems. The scanner keeps sending to the same local destination. Capacitor decides what is safe to receive, where each study belongs, and which profile is allowed to be active.
Site profiles
Each facility runs from its own profile — DICOM destinations, worklist source, routing rules, tag transformations, compression, and delivery policy. Profiles start cleanly when a unit arrives and stop when it leaves, so the technologist only ever sends to Flux Box.
Patient-release safeguards
Walk-ins and add-ons that aren't on the active worklist are held for deliberate review instead of being released automatically — and the review is scoped to the current facility, so an add-on at one site never mixes into another site's destinations.
Location-change safety
The highest-risk moment is a facility change. Flux Box can require a preflight check — confirming the acquisition system has been cleared — before it accepts any new-site storage. It fails closed by default.
Central fleet operations
Profiles are prepared, validated, and pushed from one place. Service teams bring the right profile online when a unit arrives and inspect queues, holds, and delivery state across the fleet without touching the scanner.
Profiles are managed centrally through Configatorium, the Flux portal where operators create and maintain each facility's profile and push it to the fleet. (A step-by-step Configatorium walkthrough with screenshots is in preparation.)
How the fleet workflow feels
For technologists
- Send every study to the same local Flux Box destination.
- Query the same local worklist endpoint.
- Keep scanning even when delivery is deferred by bandwidth or policy.
- Review unmatched patients only when the system asks for confirmation.
For service teams
- Prepare facility profiles centrally in Configatorium.
- Bring the right profile online when the unit arrives.
- Keep remote access and troubleshooting under a controlled service model.
- Inspect queues, holds, errors, and active profile state without touching the scanner.
For health-system operators
- Use one coach across owned facilities and partner locations.
- Support renovation capacity, event screening, overflow demand, and recurring installations.
- Standardize mobile imaging behavior across a fleet instead of re-solving every site.
- Keep patient-routing boundaries clear for each institution.
For IT and security
- Limit the scanner to a stable local endpoint.
- Keep per-site routing rules off the modality.
- Seal inactive profiles and caches.
- Require explicit release when patient or site context is uncertain.
Best-fit mobile imaging use cases
Enterprise mobile fleets
Operators that run units between multiple facilities — and teams that share trailers across institutions — can centralize profiles and support from one place while keeping each site isolated.
Facility overflow and renovations
When a truck is parked outside a facility to cover construction, equipment downtime, or a backlog, Flux Box lets the unit behave like an extension of that facility without reconfiguring the scanner every time.
Screening events and recurring programs
Health fairs, awareness-month events, and recurring partner-site programs can keep a stable workflow while still honoring facility-specific routing and worklist rules.
Standby and spare trailers
Spare coaches can be kept ready with the same profile model, then activated for the facility that needs coverage.
::
See the mobile fleet model in action
Flux Box is a compact, pre-configured appliance for mobile imaging programs that need profile control, patient-release safeguards, and safe facility changes.