1 · Pull
Skyward enumerates the bridge with QIDO-RS and retrieves every study with WADO-RS — resumable, idempotent, and rate-aware so it never overruns the source.
When your primary VNA is restored, Skyward moves the imaging acquired during the outage back into production and proves the reconciliation before anyone cuts over. No silent gaps, no guesswork — a signed, verifiable hand-back, then a clean teardown.
Skyward enumerates the bridge with QIDO-RS and retrieves every study with WADO-RS — resumable, idempotent, and rate-aware so it never overruns the source.
Each study is written to your restored production VNA over STOW-RS, and the HL7 messages captured during the outage are replayed to your downstream systems.
A reconciliation gate reads everything back and must pass before cutover — surfacing any exception by name. Then a customer-authorized teardown takes the bridge to zero.
Skyward pulls each study from the bridge with WADO-RS, stores it to your restored VNA with STOW-RS, then reads it back with QIDO-RS. The reconciliation gate asserts that the bridge's SOP-Instance-UID set is fully contained in the target — and surfaces any exception by name, so the cutover decision is evidence-based.
Every ADT/ORM message captured during the outage is replayed to your restored systems on recovery — so orders and patient updates are never lost in the gap.
Migrations span hours or days and get interrupted. Re-running never duplicates; an interrupted run picks up where it left off.
Standards-based DICOMweb in and out, validated against a cross-vendor mock — Skyward speaks to the production VNA you already run.
A reconciliation report (studies verified, HL7 sent/ACK'd) is produced before anything is destroyed, and a certificate of destruction after.
Skyward is included with every Lightbridge engagement. Let's walk through how repatriation maps to your production VNA.