Skyward / Migration & repatriation

Move the studies.
Make the result reviewable.

Move imaging between compatible archives and reconcile what arrived. Use Skyward for a standalone migration, a vendor transition, or the return from a Lightbridge DR engagement.

Scope a migration pilotSee Lightbridge

A deliberate hand-back

Transfer. Reconcile. Review.

  1. 01

    Define the dataset

    Choose the source, target, filters, transport, and verification depth. Confirm endpoint compatibility and access first.

  2. 02

    Run the transfer

    Pull with WADO-RS and store with STOW-RS, or use configured dcm4chee DIMSE export. Persist progress so verified studies can be skipped on a resumed run.

  3. 03

    Check the destination

    Compare SOP Instance UID sets where available. If an endpoint lacks UID-level detail, the engine uses a count-based comparison; that offers less assurance.

  4. 04

    Resolve and sign off

    Review the manifest and exceptions. In a Lightbridge engagement, routine destruction authorization also depends on accepted signoff and completion of captured HL7 replay.

Choose your assurance

Presence and pixel integrity
answer different questions.

01

Identity reconciliation

Check that source instances appear at the target. A passing report means the configured in-scope checks passed.

02

Optional content checks

Compare raw PixelData hashes or decoded pixels where configured. Sampling and transcoding settings determine what can be concluded.

03

Optional HL7 replay

Replay captured ADT/ORM messages and track destination acknowledgments. An acknowledgment is not proof of the resulting downstream clinical workflow.

Validation status

Cross-vendor evidence.
A customer-specific pilot next.

In the July 4, 2026 internal AWS test, Skyward transferred three synthetic studies from dcm4chee to Orthanc and passed the reconciliation gate. That validates a specific DICOMweb path.

Your production VNA’s behavior, authentication, transfer syntaxes, and volume need their own validation. A bounded pilot makes those dependencies visible before a larger cutover.

The deliverable

An evidence-based cutover decision.

↗

Migration manifest + reconciliation report

Study and instance results, exceptions, and optional content-verification outcomes for your team to review. The report supports approval; a default reconciliation pass does not establish that every image byte is unchanged or that data is free of malware.

Let’s make it concrete

Start with a bounded migration.

Choose a study subset and a real source and destination. Agree on what must pass before you scale.

Request a briefing