LAMINATE / Deployment
A setup that
fits your team.
Upload to the web workspace directly, or connect your PACS to the cloud through an on-site gateway that hides patient identifiers and restores them when results return. With your own infrastructure, LAMINATE can also run inside your environment.
Web workspace
- Sign in to LAMINATE in the browser, with nothing to install.
- Upload archives of DICOM studies directly, or receive them from your PACS.
- Run analyses, review the results and generate reports.
- Roles for owners, admins and members, with permissions to upload and to run each analysis.
On-site gateway
- A container your IT team installs at your site, to connect your PACS with the LAMINATE cloud.
- Receives studies from scanners and PACS over DICOM, and handles queries and retrievals.
- Hides patient identifiers before anything leaves your network, and restores them when results come back to your site.
- Can start analyses automatically with a rule you switch on, and send results back to the PACS nodes you enable for writing.
Desktop app
- The same sign-in as the web, for macOS, Windows and Linux.
- Imports a DICOM folder or zip from your computer.
- On a computer that can reach your on-site gateway, it can show the original patient details next to the pseudonym.
- Access is controlled and limited by the gateway, and each lookup is logged on your site.
Inside your own environment
- For teams with their own infrastructure that is ready to use.
- Available once your environment meets Sentinel’s standards and requirements.
- We go through your requirements, hardware and support together, and agree the scope before anything is promised.
How patient data is protected
Identifiers replaced on site
The gateway replaces the patient name and ID with a pseudonym, shifts study dates, and removes private tags before data leaves your network.
Identity stays with you
The original identity is stored only at your site, encrypted. LAMINATE in the cloud works with the pseudonym.
Checked again in the cloud
Every ingest is de-identified again, including archives you upload yourself.
Results come back
When results return to your PACS, the original identity is restored on site.
Which setup fits?
| If you want to… | Start with | What that means |
|---|---|---|
| Try LAMINATE on a few studies | Web workspace | Upload DICOM archives in the browser. Nothing to install. |
| Have studies flow in from your PACS | On-site gateway | A container at your site receives studies and removes identifiers before upload. |
| Start analyses automatically | Gateway and an automation rule | An administrator switches on a rule for single timepoint or longitudinal analysis. |
| Get the FLAIR* series back in your PACS | Gateway with a write-enabled node | The result is sent to the nodes you allow, under the original patient. |
| Run LAMINATE inside your own environment | Your own environment | Available when your infrastructure is ready and meets Sentinel’s standards and requirements; we agree the scope together. |
what it does not do
Good to know
- Data in the cloud is pseudonymized, not anonymous.
- Text burned into image pixels is not removed. Configure your scanners so none is added.
- The gateway uses DICOM storage, query and retrieval, and accepts MR, CT and PT images. DICOMweb, HL7 and FHIR are not supported.
- Only the single timepoint result is returned to PACS as DICOM today.
This application is intended for research and educational purposes only. It is not FDA-approved and should not be used for clinical diagnosis, treatment decisions, or patient care.