Some studies never arrive by themselves. A patient brings a disc from another hospital. A specialist needs priors from a partner site. A research team needs a de-identified set. Trident gives the people who handle those requests one screen for the whole job: find the study, bring it in, make it right, and send it on.
Trident is driven by a person, never by a schedule. Nothing moves unless someone asks for it.
Search any PACS by patient name, patient ID, accession number, date range or modality, with wildcards.
Open a study to see its series before you retrieve.
Retrieve whole studies or chosen series by C-MOVE or C-GET. Trident checks that every expected image arrived.
Import from CD, DVD, USB or a folder, with or without a DICOMDIR.
Upload files from your own PC in the web client.
Receive studies sent to it by the systems you have listed.
View headers and validate them against the DICOM standard, with auto-correction that only touches what is safe.
Reconcile patient and order details from a Modality Worklist entry, a PACS study or by typing, field by field.
De-identify with profiles built on DICOM PS3.15, starting from Basic, Research and Teaching file templates, and preview the result before you send.
Choose a UID policy per destination: new UIDs, or keep the originals.
Every change is recorded in the object and in the audit trail. The stored original is never modified.
Send one study to any number of destinations at once.
Trident learns which compressions each destination accepts and converts when needed: lossless by default, lossy only if you allow it.
Workflow profiles save the whole recipe: destinations, de-identification, UID policy and validation.
Retry with back-off, a failed-jobs list, cancel, and resume after a restart.
The job list is always in view, so you know where every study stands.
The Windows console puts sources, search results, local storage, destinations and jobs on a single screen that reads left to right. The web client offers the same workflow in Edge or Chrome with nothing to install on the user's PC.
Install Trident on one workstation, on a server shared by a department, or in a Docker container.
Studies wait in local storage encrypted with AES-256-GCM. DICOM connections run over TLS 1.2 or 1.3, with a pinned certificate per peer if you want one. Sign-in uses local or Active Directory accounts with Administrator, Operator and Auditor roles.
Every action lands in a hash-chained audit trail that can be verified at any time and forwarded to your SIEM.
Ask for a guided demonstration built around your modalities, your PACS and your routing rules.
