Farsight / Archive integrity & observability

Indexed isn’t
the same as retrievable.

Farsight checks the archive behind the dashboard. Probe retrieval, investigate integrity exceptions, and produce sealed evidence with an explicit scope and coverage.

Three complementary checks

Make integrity
something you can inspect.

01

Retrieval sweeps

Probe a configured sample through DICOMweb. Deep mode retrieves objects and checks that they parse as DICOM. Transport errors remain inconclusive.

02

Digest baselines

Compare retrieved objects with digests from an authenticated baseline to detect changes that valid DICOM parsing alone can miss.

03

Object-store reconciliation

Compare current S3-compatible object metadata with a sealed baseline to find vanished, resized, or retagged objects. This checks metadata, not every stored byte.

Evidence with boundaries

A verdict should tell you
what was actually checked.

PASS

Configured checks passed

The examined data met the checks and configured coverage threshold. A sampled pass speaks to that sample.

FAIL

An integrity failure was found

The sweep found missing, corrupt, or baseline-modified data. Review the affected studies and evidence.

INCONCLUSIVE

More investigation is needed

Errors, no positive verification, or insufficient configured coverage prevent a clean conclusion.

The deliverable

A sealed integrity attestation.

What ran. What it found.
How much it examined.

Attestations record the check scope, outcomes, and coverage. Authenticated baseline imports require an HMAC seal. Configured S3 Object Lock storage can retain evidence independently of a temporary archive.

A PRACTICAL DISTINCTION

Retrieval, parsing, and integrity are separate signals.

A valid DICOM object can still contain changed pixels. Sampling can miss objects it never touches. Metadata reconciliation can expose store changes without proving pixel identity. The assessment plan chooses the checks appropriate to your risk.

Operational visibility

See the bridge while it runs.

With a Lightbridge deployment, Prometheus and Grafana bring together configured archive counts, infrastructure health, and Skyward metrics for migration and HL7 flow. Scheduled integrity sweeps and CloudWatch alarms add visibility when enabled and connected to your notification path.

Monitoring is configured per engagement. Coverage, sweep intervals, alert routing, and retained evidence are explicit parts of the plan.

Let’s make it concrete

Find out what your archive can prove.

Scope an assessment around a compatible DICOMweb archive, the coverage you need, and the evidence you want to retain.

Request a briefing