Skip to content
Blimdata

For hospitals & imaging centres

Your archive is already an asset.We make it earn.

You are already storing, backing up and paying to keep millions of studies that generate nothing. Blimdata turns that archive into a recurring revenue line — without touching clinical workflow, and without identifiable data ever leaving your network.

  • Cost to your institution

    None. We fund deployment, processing and annotation.

  • Clinical workflow impact

    None. Read-only PACS access, outside working hours by default.

  • Data that leaves your network

    De-identified studies only, after validation.

  • Your revenue

    A share of every licence attributable to your data.

Why partner

Four things change. Nothing else does.

Partnership is designed to be invisible to your clinical staff and material to your finance office.

Revenue

A new, recurring income line

You receive a share of the licensing revenue attributable to studies sourced from your archive, reported against an auditable record of what was licensed and to whom.

Cost

Nothing to buy, nothing to run

Blimdata funds the gateway, the compute, the de-identification, the radiologist annotation and the compliance work. There is no licence fee and no hardware purchase.

Capability

A properly indexed archive

Cataloguing your archive by modality, body region and study characteristics is a side effect of the process — and the index stays yours, whether or not a study is ever licensed.

Standing

Representation in the science

Diagnostic models are trained on the data that reaches them. Studies from your patient population make those models work for patients like yours.

How partnership works

Four stages. You control every one.

Nothing is processed before a written agreement is signed, and you can pause or withdraw participation at any point.

Step 01

Written assessment

Tell us what your archive holds. We come back with a written view of which modalities are viable, what demand exists, and an indicative revenue range — before anything is installed.

Step 02

Technical review

A session with your PACS administrator and IT security lead. We walk through the gateway, the network posture, the AE title configuration, and answer diligence questions in writing.

Step 03

Data agreement

A written agreement covering scope, permitted use, de-identification standard, revenue share, reporting, audit rights, term and withdrawal. Your legal counsel reviews before signature.

Step 04

Deployment & operation

The gateway is deployed and begins processing the agreed scope. You receive periodic reports of what was processed, what was licensed, and what revenue was attributed.

What we install

One lightweight gateway.Read-only, outbound-only.

The gateway is a small containerised service that runs on hardware inside your network. It talks to your PACS the way any other DICOM node does, and it talks to us over a single outbound connection.

  • Standard DICOM C-FIND and C-MOVE against a read-only application entity title.
  • No inbound ports, no VPN tunnel, and no new firewall exceptions required.
  • Outbound TLS 1.3 only, to a fixed endpoint your team can allow-list.
  • Configurable rate limits and scheduling, so retrieval runs outside peak hours.
  • De-identification executes locally; studies that fail validation are never transmitted.
Inside your network
Your PACS Unmodified
Blimdata gateway Read-only AE title
De-identification 18 PHI identifiers + pixel redaction
Validation gate Fail = never transmitted

Only studies that pass validation cross the boundary, over outbound TLS 1.3.

Governance

You remain the data controller.

Your institution decides what is in scope and what is not — by modality, by department, by date range, by study type. Scope is written into the agreement, and changing it requires your agreement, not ours.

We process only what a hospital is lawfully permitted to release under its own ethics and consent framework. We are not a route around institutional governance, and we will decline an engagement that tries to use us as one.

Every action the gateway takes is logged. Reports show what was retrieved, what was de-identified, what failed validation, what was annotated, and what was ultimately licensed — so the revenue figure is checkable rather than asserted.

If your board cannot audit it, it is not a partnership — it is a data transfer with extra steps.

Hospital questions

What boards ask us.

Will this slow down our PACS or affect radiology workflow?

No. Retrieval is rate-limited and scheduled — by default outside peak clinical hours — and the gateway holds a read-only application entity title, so it cannot write to, modify or delete anything in your archive. Radiologists see no change to their working environment.

What happens if we want to stop?

The agreement includes a withdrawal clause. You can suspend processing immediately at any time, and terminate on notice. Datasets already licensed under executed agreements remain subject to those agreements, which is why the scope and term are set out in writing before anything begins.

Who owns the data?

Your institution retains ownership of the source archive throughout. What we license is a de-identified, annotated derivative produced under the terms of your agreement — and the agreement defines exactly what a licensee may and may not do with it.

How is our revenue share calculated?

As a share of licensing revenue attributable to studies sourced from your archive. Attribution is tracked per study through the pipeline, so the calculation is reconstructible from the audit log rather than being a lump-sum estimate.

What if our archive is disorganised or poorly catalogued?

That is normal and expected. Part of the ingestion work is reading DICOM headers to catalogue what actually exists — by modality, body region, study description and acquisition parameters. Most partners learn things about their own archive from the assessment.

Do you need patient records or reports as well as images?

Structured clinical context materially increases dataset value, but it is optional and separately scoped. Where a hospital can lawfully provide de-identified report text or outcome data, we handle it under the same de-identification standard as the imaging.

Hospital partnership

Start with one archive. No cost to you.

Tell us what you hold. We will come back with a written assessment of what your archive could support, what we would install, and what the revenue share looks like.

  • No cost, no licence fee and no hardware purchase for your institution.
  • Identifiable data never leaves your network — de-identification runs on-premise.
  • Read-only access to PACS. Clinical workflow is untouched.
  • Nothing is processed until a written data agreement is signed.

Helpful for scoping, but not required.

We use these details only to respond to your enquiry. No marketing lists, no third-party sharing.