Mobile Imaging Fleet — Technical Details
This is the technical companion to the Mobile Imaging Fleet Operations overview. It describes how Flux Box, running DICOM Capacitor, enforces site profiles, isolation, patient-release review, and the location-change safety check between an imaging device and a facility's systems — for any modality on the coach.
Site profiles that start and stop cleanly
Each facility profile can carry its own DICOM destinations, worklist source, routing rules, tag transformations, compression settings, and delivery policy. Profiles can run in isolated runtime containers, and inactive profiles are stopped when the unit leaves a site.
The result is simple for the technologist: the imaging device always sends to Flux Box. The active fleet profile determines what happens next.
Geofencing plus network confirmation
Location awareness can use GPS/geofencing to select the expected facility, then network checks confirm the profile before it handles traffic. That combination avoids the old model where every site had to be represented directly on the scanner.
Per-institution cache isolation
Cached data is separated by facility profile. A study acquired for one institution is not visible to the next institution's active route, even when the same coach visits both sites in the same week.
Remote profile operations
Central teams can prepare and update profiles before the coach arrives. Configuration packages can be signed and pushed remotely when connectivity exists, or delivered offline when a site is locked down. Profiles are authored and maintained in Configatorium, the Flux profile-management portal.
Container isolation
Profiles can be invoked as individual runtime containers with no bleed between them, so an inactive site's routing and cache cannot affect the active one.
Patient-release safeguards
Mobile programs need an answer for patients who are not already on the worklist. Flux Box can hold those studies instead of releasing them automatically.
Unmatched patient review
When a study arrives without a match in the active facility worklist, Capacitor keeps it in a review state. A technologist or operator can inspect the study context, choose the correct destination, and release it deliberately.
This is the release-portal concept: the system does not guess when a patient is missing from the worklist.
Multi-site release boundaries
The review workflow is tied to the active profile. That means an add-on patient at Facility A is reviewed for Facility A, not silently mixed with Facility B's destinations after the unit moves.
Fail closed by default: an unmatched study should be held until someone confirms where it belongs.
Location-change safety check
The highest-risk moment is a facility change. Flux Box can require a preflight check before Capacitor opens its storage port for the new site.
- A new location is detected — geofencing and network evidence select the next expected profile.
- The imaging device is queried — Flux Box runs a DICOM C-FIND against the local acquisition system.
- Any remaining patient blocks storage — if the device still has patient records, Capacitor does not listen on the storage port for the new profile.
- The operator clears the local database — after the scanner is clear, the active profile can come online.
- New studies are accepted under the right profile — storage, worklist, routing, and release rules now match the current facility.
This check is intentionally conservative. It does not try to fix the acquisition system; it prevents new-site storage until the local imaging database is clean. It is an optional, per-fleet control.
What Flux Box keeps doing underneath
The safety controls sit on top of the core mobile imaging workflow:
- Local worklist cache — the imaging device queries a local endpoint, even when the upstream worklist is unavailable.
- Store-and-forward delivery — studies are written locally, validated, queued, and delivered when policy and connectivity allow.
- Resume-on-failure — interrupted sends pick up from the last acknowledged image instead of forcing manual resend.
- Bandwidth-aware transfer — real-time wireless delivery is used when it helps; scheduled or docked delivery can be selected by policy.
Back to the overview
The Mobile Imaging Fleet Operations page covers the business and operational picture — who it's for, how the workflow feels, and where it fits.