XyDromatics De-Identification Engine Specialized engine · De-identification

XyDromatics® De-Identification Engine — raw PHI in, de-identified data out.

The one-way de-identification appliance. Accept studies and reports across an untrusted network over mutually-authenticated encrypted channels, apply HIPAA Safe Harbor tag transforms under your own §164.514(b)(1) Expert Determination — replace identifiers with irreversible keyed codes, interval-shift dates, scrub free text and burned-in pixels — and forward the de-identified output to whatever destination you configure. It is a de-identification stage in a routing workflow as readily as a research-ingest node: an AI or algorithm vendor, an external reader, a teaching or registry archive, or XyDromatics Research Archive. The trust boundary between clinical data and anywhere PHI must not go.

Runs Synthology-hosted in the cloud or customer-operated on-prem — the same trust boundary either way. The re-identification key lives only on the engine and never crosses the wire.

Identifiers & classification

Classification
Non-device software
Product code
N/A
Statute
§520(o)(1)(D)
De-identification method
Safe Harbor tag transforms · §164.514(b)(2), under the site’s own §164.514(b)(1) Expert Determination
FDA listing
Not required (§520(o)(1)(D))
Full regulatory posture →

Capabilities

One job, done thoroughly: PHI in, de-identified data out.

Secure cross-network ingest, Safe Harbor tag transforms under your own Expert Determination, a content gate that reaches into free text and burned-in pixels, HL7 report de-identification, and a configurable forward to any DICOM destination — so the engine is a de-identification stage in an enterprise routing workflow, not only a research-ingest node. An opt-in PHI-free coded-concept harvest feeds research cohorts where that lane is licensed.

Secure cross-network ingest

Accept studies and reports pushed across an untrusted network, from any source, over an encrypted, mutually-authenticated channel. Every channel is fail-closed — an unauthenticated or unpinned peer is rejected before a single object is read.

  • DICOM-TLS C-STORE — secure DIMSE for C-STORE-only modalities and legacy PACS (TLS 1.2/1.3)
  • MLLP-over-TLS — secure HL7 v2 ORU for EMR / RIS report sources
  • DICOMweb STOW-RS over HTTPS — for cloud and third-party PACS sources
  • Mutual TLS with SHA-256 client-certificate thumbprint pinning on every channel
  • Optional sealed bearer token as an alternative to mTLS on the DICOMweb channel
  • Off by default — on-prem deployments keep plain DIMSE / MLLP inside the trusted network

De-identification core

The de-identification itself: HIPAA Safe Harbor tag transforms across the 18 identifier categories of §164.514(b)(2). Because the pseudonymization and interval-preserving dates go beyond pure Safe Harbor, the governing certification is a §164.514(b)(1) Expert Determination — the site’s own, by a qualified expert of its choosing, never one rendered by Synthology. Identity is replaced deterministically so the same patient stays linkable across studies without any correlation table.

  • Keyed-HMAC pseudonymization of patient and study identifiers (per-site key, never leaves the engine)
  • Interval-preserving per-patient date shift (DICOM Attribute Modification 113107) — exam intervals and chronological order preserved, absolute dates obscured
  • VR-aware tag substitution — replacements always fit the target value representation (no silent blanking)
  • Private / proprietary tag removal (default on)
  • Deterministic study-UID remapping — the de-identified study carries a stable, re-derivable UID
  • Optional operator-chosen sequential labeling (licensed; requires a captured §164.514(c) attestation)

Content gate — free text, pixels, documents

Identifiers hide in more than structured tags. The content gate finds and removes PHI in narrative reports, burned-in image pixels, and encapsulated documents — or quarantines what it cannot safely clean.

  • Free-text SR narrative scrubbing (shared PHI heuristic scrubber)
  • Burned-in pixel OCR redaction — local Tesseract renders the pixels and blacks out detected text (never cloud OCR)
  • Encapsulated-document handling (PDF rasterize + OCR-redact + rebuild, or text scrub)
  • Per-lane policy: clean, quarantine, or reject — operator-configurable per content type
  • Quarantined objects are sealed on the engine for operator review — never silently forwarded

HL7 v2 ORU de-identification

Reports de-identify with the SAME per-patient pseudonym and date-shift offset as the images, so a de-identified report lands on its de-identified study's timeline with no correlation table and in any arrival order.

  • MLLP listener de-identifies inbound ORU^R01 (PID / OBR / OBX / PV1 / ORC)
  • Cross-protocol demographic alignment — HL7 and DICOM derive the pseudonym + date shift from the same MRN + site key
  • OBX narrative scrubbed via the shared free-text PHI scrubber
  • Store-and-forward with fail-closed NACK — the sender holds any message the engine could not fully de-identify and forward
  • Forwards the de-identified report to a downstream HL7 research sink

Coded-concept harvest → research cohorts

Beyond de-identified images, the engine can harvest standards-coded clinical concepts from report-bearing objects into a PHI-free, pseudonym-keyed cohort store — the input to a Clinical Cohort Builder. Opt-in and gated.

  • Extract standards-coded concepts from pre-scrub report objects (never free-text PHI blobs)
  • PHI-free coded-concept batches keyed by the study pseudonym
  • Two-person export control — a licensed add-on (deid_cohort_export) AND a current §164.514(b)(1) Expert-Determination attestation
  • Cohort exports convey re-pseudonymized image bytes only — no report text, narrative or snippet leaves the host
  • Fail-open harvest: a harvest or ingest error never affects the de-identified image forward

Operations, durability & administration

A production appliance: durable store-and-forward, sealed configuration and secrets, PHI-free health telemetry, and the shared administration surface used across the fleet.

  • Durable outbound spool — store-then-drain so a downstream outage or restart never loses an instance
  • Quarantine + dead-letter queues with operator review
  • Whole-configuration encryption at rest (SYNTHIMG envelope; reversible secrets sealed, never emitted)
  • Append-only HIPAA audit log — count-capped ring with archive-before-evict to a durable store, configurable retention with a hard 6-year floor (45 CFR 164.316(b)(2))
  • Web admin UI with shared sidebar shell + role-based access control
  • PHI-free /api/health telemetry (queue depth, disk, channel posture) for pool + gateway monitoring

See it

De-identification, on screen.

Live captures from a running installation — click any screen to enlarge it.

01

Quarantine

Objects the engine would not release automatically — burned-in text risk, narrative SR content — held for a human decision, with the reason on every row.

02

Inbound

Every object received, the profile applied and where it went.

03

Configuration

De-identification profile, SCP listener, downstream target and quarantine policy.

Pixel data, not just headers

The same image, before and after the engine.

A Secondary Capture with a burned-in patient header — the kind an older ultrasound or a scanned document carries — sent to the engine and retrieved from the destination archive afterwards. The engine OCRs every frame, replaces every detected word with solid pixels (no blur, nothing recoverable), rewrites the identifying attributes, and records what it did in the object's own de-identification method. Fictional patient; real engine, real archive.

Before — as sent by the modality

Before — as sent by the modality: synthetic ultrasound frame with a burned-in patient header

After — as stored by the destination archive (redacted regions outlined)

After — as stored by the destination archive (redacted regions outlined): synthetic ultrasound frame with a burned-in patient header
AttributeBeforeAfter
(0010,0010) Patient Name DOE^JANE^A PSN-… (keyed HMAC, derived separately from the ID)
(0010,0020) Patient ID 4471982 PSN-4662DD7B90B24B62
(0010,0030) Birth Date 19610314 (removed)
(0008,0080) Institution ACME RADIOLOGY (removed)
Pixel data name, MRN, DOB, accession, institution burned in 23 words detected · 23 redacted
(0028,0301) Burned In Annotation YES NO
(0012,0064) De-identification Method — DCM 113100 · 113107 · 113101 Clean Pixel Data Option
Outlines are added to this page so the black redaction boxes are visible against the black background; the stored object has no outlines.

Dataflow

The engine is the trust boundary.

Raw PHI arrives from the customer site over an encrypted, mutually-authenticated channel — DICOM-TLS C-STORE, MLLP-over-TLS, or DICOMweb STOW-RS. The engine de-identifies at the boundary and forwards only de-identified output to the destination you configure — a vendor, an external reader, a teaching or registry archive, or XyDromatics Research Archive. It occupies the same position whether Synthology hosts it in the cloud or the customer runs it on-prem.

Secure cross-network de-identification ingest A customer site on the left holds the plaintext sources: a PACS or modality that speaks DICOM C-STORE, an EMR or RIS that emits HL7 v2 ORU reports, and a third-party PACS or cloud that speaks DICOMweb. Each pushes to the De-Identification Engine across an untrusted network over an encrypted, mutually-authenticated channel: DICOM-TLS C-STORE, MLLP-over-TLS, or DICOMweb STOW-RS with mutual TLS. Every channel is fail-closed — an unauthenticated or unpinned peer is rejected before any object is read. The De-Identification Engine is the single trust boundary and the only place the re-identification key lives: it replaces identifiers with irreversible keyed codes, interval-shifts dates, scrubs free text and burned-in pixels, and harvests standards-coded concepts. Only de-identified output leaves it, flowing to whichever destinations the site configures: XyDromatics Research Archive — a Research-Use-Only de-identified archive plus a PHI-free coded-concept cohort store — an AI vendor or external reading service that receives permanently de-identified studies only, and a downstream HL7 sink for the de-identified reports. The forward is an ordinary C-STORE destination, so the engine serves a routing workflow as readily as a research pipeline. It occupies the same trust-boundary position whether Synthology hosts it in the cloud or the customer runs it on-premises. CUSTOMER SITE SECURE TRANSIT · UNTRUSTED NETWORK DE-IDENTIFICATION ENGINE DE-IDENTIFIED OUTPUT PACS / modality DICOM C-STORE · plaintext PHI EMR / RIS HL7 v2 ORU · plaintext PHI 3rd-party PACS / cloud DICOMweb · plaintext PHI DICOM-TLS · C-STORE secure DIMSE · TLS 1.2/1.3 MLLP-over-TLS secure HL7 v2 DICOMweb · STOW-RS HTTPS · multipart Part 10 mTLS · FAIL-CLOSED · PINNED De-Identification Engine The only place the key lives Irreversible codes · interval date-shift Free-text + burned-in pixel scrub Coded-concept harvest Expert-Determination method TRUST BOUNDARY XyDromatics Research Archive De-identified DICOM archive · RUO + PHI-free coded cohort store AI vendor · external reader de-identified studies only Downstream HL7 sink de-identified ORU ✓ NO PHI LEAVES de-identified Encrypted, mutually-authenticated ingest (raw PHI, in transit only) De-identified output — no PHI, no key Same trust boundary, two deployments: Synthology-hosted (the engine + the destination archive run in Synthology's cloud) · or customer-operated (the customer runs the whole chain on-prem). The de-identified forward is a configurable C-STORE destination.

Use cases

Six deployment patterns.

In a routing workflow or at the edge of the network, cloud-hosted or on-prem, image or report, external-vendor shielding or research-cohort building — the engine is the single de-identification point for all of them.

Pattern 1

De-identification inside a routing workflow

The engine is a stage in the route, not a destination. XyDromatics Router sends the studies that match a rule to the engine, which de-identifies and forwards to the configured peer — so one clinical feed can serve both a PHI-bearing clinical destination and a de-identified one, without the sending modality knowing the difference.

Flow

  1. 1 Router matches a routing rule and forwards the study to the engine over C-STORE (plain on the LAN, or DICOM-TLS across a network)
  2. 2 The engine de-identifies at the trust boundary under the site Expert-Determination policy
  3. 3 The de-identified copy is forwarded to the configured downstream peer — any host, port and AE title, with optional TLS
  4. 4 A keyed, object-bound marker lets a re-imported object pass through rather than be de-identified a second time
  5. 5 The clinical route is untouched — the identified copy still reaches the clinical archive on its own path
Pattern 2

Synthology-hosted de-identified ingest (cloud)

A customer sends studies to a Synthology-hosted De-Identification Engine across the internet. Raw PHI crosses only inside a mutually-authenticated, encrypted channel; nothing re-identifiable is ever stored in the cloud.

Flow

  1. 1 Customer PACS / modality sends over DICOM-TLS C-STORE (or DICOMweb STOW-RS) with a pinned client cert
  2. 2 The engine authenticates the peer, decrypts in memory, and de-identifies at the trust boundary
  3. 3 Identifiers pseudonymized, dates interval-shifted, free text + burned-in pixels scrubbed
  4. 4 De-identified study forwarded to the configured destination; where the research lane is licensed, PHI-free coded concepts are harvested to the cohort store
  5. 5 No PHI and no re-identification key persist in the cloud — only de-identified output
Pattern 3

On-prem de-identification appliance

The customer runs the whole chain inside their own network. The engine is the internal gate between the clinical estate and anywhere PHI must not travel — a vendor evaluation, a teaching file, a registry submission, or a research environment. TLS optional, since traffic never leaves the trusted network.

Flow

  1. 1 Clinical PACS / Router forwards studies to the on-prem engine over plain C-STORE (inside the trusted LAN)
  2. 2 The engine de-identifies under the site's Expert-Determination policy
  3. 3 De-identified output lands wherever the downstream destination points — commonly an on-prem XyDromatics Research Archive
  4. 4 Where the research lane is licensed, coded concepts populate the local Clinical Cohort Builder
  5. 5 The re-identification key stays on the customer's engine; researchers see only de-identified data
Pattern 4

AI-vendor / external-reader PHI shielding

Send permanently de-identified studies to an AI vendor or outside reading service that is not in BAA scope. De-identification here is irreversible for the recipient — unlike the Router's reversible pseudonymization-on-export, nothing the vendor receives can be turned back into PHI by anyone holding it.

Flow

  1. 1 Source study irreversibly de-identified — Safe Harbor tag policy, keyed-HMAC identity codes, interval-preserving date shift, free-text and burned-in-pixel scrub
  2. 2 De-identified study sent to the AI vendor / external reader
  3. 3 The vendor analyzes and returns findings tagged with the same de-identified code
  4. 4 The covered entity re-derives the same code from the MRN it already holds, so findings match back to the right patient — a §164.514(c) re-identification code, never disclosed and never sent downstream. No reverse map exists for anyone to obtain.
  5. 5 The vendor never received PHI and has no means of re-identification; the clinical workflow still benefits from the findings
Pattern 5

Research report de-identification (HL7)

ORU reports from the EMR / RIS de-identify alongside the images and land on the matching de-identified study's timeline, so a research reporting environment has both the pixels and the narrative — with no PHI.

Flow

  1. 1 EMR / RIS emits ORU^R01 over MLLP-over-TLS
  2. 2 The engine de-identifies PID / OBR / OBX / PV1 / ORC and scrubs the OBX narrative
  3. 3 HL7 and DICOM derive the same pseudonym + date shift from the same MRN + site key
  4. 4 The de-identified report is store-and-forwarded to the research HL7 sink (fail-closed on any failure)
  5. 5 Report and study align on the timeline with no correlation table
Pattern 6

Clinical-cohort building for research

A research program needs cohorts defined by coded clinical concepts, not free text. The engine harvests standards-coded concepts into a PHI-free, pseudonym-keyed store that a Clinical Cohort Builder queries. Retained text is used only for the customer own internal cohort search and never leaves the host.

Flow

  1. 1 Harvest lane extracts standards-coded concepts from pre-scrub report objects (opt-in, licensed)
  2. 2 PHI-free coded batches keyed by the study pseudonym are posted to XyDromatics Research Archive
  3. 3 A researcher composes cohort criteria (coded concepts, demographics, intervals)
  4. 4 Export is gated: the deid_cohort_export add-on AND a current §164.514(b)(1) Expert-Determination attestation, both required
  5. 5 Cohorts export under an enforced k-anonymity floor

Integration points

Sources in, de-identified output out.

Sources (senders)

  • Modalities + PACS over DICOM C-STORE (plain on-prem, or DICOM-TLS across a network)
  • EMR / RIS over HL7 v2 ORU (plain MLLP, or MLLP-over-TLS)
  • Third-party PACS / cloud over DICOMweb STOW-RS (mTLS or sealed bearer)
  • XyDromatics Router — can route studies to the engine for de-identification

Destinations (de-identified output)

  • Any DICOM C-STORE peer — the de-identified forward is a configurable SCU destination (host, port, called/calling AE, optional TLS), not a fixed research sink
  • XyDromatics Research Archive — de-identified DICOM archive (Research-Use-Only)
  • XyDromatics Research Archive coded-concept cohort store (PHI-free) — the Clinical Cohort Builder input
  • Downstream HL7 research reporting sink (de-identified ORU)
  • AI vendors / external reading services — pseudonymized studies only

Cross-product orchestration

  • Shared customer key-escrow master — every node derives its keys from the one customer master, so a pooled deployment issues one identity per patient across the pool
  • Shared DICOM SCP library — the same C-STORE receive path used fleet-wide (now with optional DICOM-TLS)
  • Unified key-escrow (IKeyEscrow) — every reversible secret sealed under one customer master
  • Synthology QMS — change control on de-identification policy

Identity, audit, observability

  • Local admin accounts (PBKDF2-SHA256) with role-based access control; machine ingest authenticated by sealed bearer token or pinned client-certificate mTLS
  • Append-only HIPAA audit log with a 6-year retention floor
  • PHI-free health telemetry (SynthIQ pool + SynthGateway console)
  • Per-source-AE accounting of every received object — accepted, quarantined, rejected or failed — plus an append-only HIPAA audit log of every administrative action

Availability

Poolable, with two prerequisites.

The De-Identification Engine is a steady-state DICOM receiver: it takes C-STORE associations, de-identifies each instance in transit, and hands it to a durable outbound spool. That makes it a normal member of a SynthIQ pool, and it publishes the queue depths and load score SynthIQ ranks on.

Its own resilience matters more day to day. The receiver seals each de-identified object into the spool and acknowledges immediately, so forwarding happens off the association: a downstream outage delays delivery rather than failing the send, and anything unrecoverable lands in a dead-letter queue instead of disappearing.

Two conditions for a pooled deployment. Every node must be activated under the same customer key-escrow master, because the pseudonym, UID-remap and date-shift derivations are all keyed from it — different masters would give one patient different identities depending on which node happened to take the study. And sequential labeling mode is single-instance only: it allocates from a counter that nodes do not share.

System requirements & sizing

Sized to study volume + content-gate depth.

Pixel-OCR redaction and encapsulated-document handling are the heaviest operations; sizing reflects study volume and how much of the content gate is enabled.

Tier Study volume CPU RAM Storage Typical site
Small (single facility) < 5,000 studies / day 4 vCPU 8 GB 250 GB (spool + quarantine + audit) Imaging center feeding one de-identified destination.
Medium (community hospital) 5,000 – 25,000 studies / day 8 vCPU 16 GB 1 TB Full modality mix with pixel-OCR + HL7 report de-id.
Large (academic / multi-site) 25,000 – 100,000 studies / day 16 vCPU per node 32 GB per node 2 TB per node Academic center; cohort harvest + multi-source cross-network ingest.
Enterprise (Synthology-hosted / IDN) > 100,000 studies / day 32 vCPU per node 64 GB per node 4 TB per node Cloud-hosted de-identified ingest — a dedicated engine instance per customer site, each with its own site key, scaled out across the hosted fleet.

Licensing

Three packages.

Core de-identifies and forwards. Secure Ingest & Content Gate adds the cross-network channels, HL7 report de-id, and the pixel / document scrubbing. Cohort Builder adds the coded-concept harvest under two-person Expert-Determination control.

De-ID Core

DICOM de-identification + store-and-forward. The base appliance for turning clinical studies into de-identified output.

  • C-STORE SCP ingest + de-identified C-STORE forward
  • Keyed-HMAC pseudonymization + interval-preserving date shift
  • Private-tag removal + VR-aware substitution
  • Durable spool, quarantine, dead-letter
  • Hash-chained HIPAA audit + web admin UI + RBAC

De-ID + Secure Ingest & Content Gate

Cross-network secure ingest on all three channels, HL7 report de-identification and the content gate (free text, pixels, documents) all ship with the product — this tier differs by install count and services, not by capability.

  • Everything in Core
  • DICOM-TLS C-STORE + MLLP-over-TLS + DICOMweb STOW-RS (all mTLS)
  • HL7 v2 ORU de-identification with cross-protocol alignment
  • Free-text narrative scrub + burned-in pixel OCR redaction
  • Encapsulated-document handling (PDF / text)

De-ID + Cohort Builder

Everything, plus the coded-concept harvest lane and the Clinical Cohort Builder — under two-person Expert-Determination export control.

  • Everything in Secure Ingest & Content Gate
  • Coded-concept harvest → PHI-free pseudonym-keyed cohort store
  • deid_cohort_export add-on with §164.514(b)(1) attestation gate
  • k-anonymity-floored cohort export
  • Run two or more in a SynthIQ pool with a designated standby · premium support eligible

Per-deployment licensing. Multi-product bundles (De-ID Engine + XyDromatics Research Archive + Router) get bundle pricing and shared site-key provisioning. The Synthology-hosted deployment is offered as a managed service — see Managed services.

Documentation

The controlled-document set.

Current GA release v1.0.1.63 · released 2026-08-05

Every De-Identification Engine deployment ships with the documents below, all managed under SynthQMS document control. The DICOM Conformance Statement is publicly available; the rest are shared under mutual NDA.

What’s new·v1.0.1.63

Raw PHI in, research-safe data out — a dedicated de-identification pipeline

  • Secure, fail-closed ingest over mutually-authenticated TLS — DICOM C-STORE, HL7 v2, and DICOMweb STOW-RS — so an unrecognized peer is turned away before any object is read.
  • De-identification designed to support a HIPAA Expert-Determination workflow — identifiers are pseudonymized deterministically, so the same patient stays linkable across studies, and dates are shifted per patient to preserve intervals while obscuring the calendar.
  • A content gate beyond structured tags — scrubbing free-text report narratives, redacting burned-in pixel text with on-box OCR (never the cloud), and handling encapsulated PDFs — quarantining anything it cannot safely clean instead of forwarding it.
  • De-identify HL7 v2 result reports onto the same de-identified study’s timeline, and optionally harvest standards-coded clinical concepts into a PHI-free, pseudonym-keyed cohort store — gated by two-person export control and a k-anonymity floor.
  • Runs Synthology-hosted or on-prem, with the re-identification key kept only on the engine, durable store-and-forward, secrets sealed at rest, and a tamper-evident HIPAA audit log. Ships with the approved EULA and clears a full QA + security-test pass.
Document Title Notes
DOC-2026-444 Hardware & Software Requirements (De-Identification Engine) Sizing, OS support, dependencies
DOC-2026-445 DICOM Conformance Statement (De-Identification Engine) Public — Storage SCP + DICOMweb STOW-RS ingress; de-identified egress SCU
DOC-2026-446 EULA Annex (De-Identification Engine) Annex to the Synthology Master EULA (DOC-2026-063)
DOC-2026-450 Penetration Test Results (De-Identification Engine) Available under NDA
DOC-2026-449 QA Runner Manual (De-Identification Engine) Internal QA + customer-validated test runs
DOC-2026-447 User Guide (De-Identification Engine) Operator + administrator workflows
DOC-2026-448 Installation Guide (De-Identification Engine) Includes MSI deploy + Linux tarball install

Frequently asked

The questions prospects ask.

How is this different from anonymization inside the Router or the VNA?

The Router and the archive family can pseudonymize on export as part of a routing or archive workflow. The De-Identification Engine is the dedicated, one-way appliance whose whole job is turning raw PHI into a de-identified data set — Safe Harbor tag transforms under your own §164.514(b)(1) Expert Determination — with the secure cross-network ingress, the content gate (free text + burned-in pixels + documents), HL7 report de-identification, and the coded-concept cohort harvest that a general router does not carry. It is the trust boundary between clinical data and anywhere PHI must not go — a research environment, an AI vendor, an external reader, or a teaching archive.

Do you support secure ingest over both DIMSE and DICOMweb?

Yes — both, plus HL7. A source can push over DICOM-TLS C-STORE (secure DIMSE, for C-STORE-only modalities and legacy PACS), MLLP-over-TLS (secure HL7 v2), or DICOMweb STOW-RS over HTTPS. Every channel is mutually authenticated with SHA-256 client-certificate thumbprint pinning and is fail-closed: an unauthenticated or unpinned peer is rejected before any object is read. All of it is off by default, so an on-prem deployment inside a trusted network keeps plain DIMSE / MLLP.

Who holds the re-identification key?

Only the engine. Pseudonymization uses a keyed HMAC with a per-site key that never leaves the engine, sealed at rest under the unified key-escrow master. De-identified output carries no key and cannot be re-identified by any downstream — XyDromatics Research Archive, an AI vendor, or an external reader. In the Synthology-hosted deployment, no PHI and no key persist in the cloud; only de-identified output does.

Does the date shift break longitudinal research?

No — that is the point of it. Each patient gets a stable, per-patient offset (HMAC-derived), applied uniformly to every date. Exam intervals and chronological order are preserved exactly, so longitudinal analysis still works; only the absolute calendar dates are obscured. The engine stamps DICOM Attribute Modification 113107 whenever a date was actually shifted. Ages over 89 are handled per Safe-Harbor expectations.

How do reports stay aligned with their de-identified studies?

Cross-protocol demographic alignment. Both the HL7 and the DICOM paths derive the pseudonym AND the date-shift offset from the same MRN + site key, so a de-identified report lands on its de-identified study's timeline with no correlation table and regardless of which arrives first. The HL7 path is store-and-forward and fail-closed: the sender holds any message the engine could not fully de-identify and forward.

What is the coded-concept cohort harvest, and how is it controlled?

An opt-in lane that extracts standards-coded clinical concepts from report-bearing objects into a PHI-free, pseudonym-keyed store — the input to a Clinical Cohort Builder. It never stores free-text PHI blobs. Turning it on and exporting cohorts is a two-person control: it requires the deid_cohort_export licensed add-on AND a current §164.514(b)(1) Expert-Determination attestation on file, and cohort export is held to an enforced k-anonymity floor.

What is the regulatory classification?

Non-device software under FD&C Act §520(o)(1)(D) — the 21st Century Cures Act carve-out for software that transfers, stores, converts, or displays device data without interpreting it. The engine does not interpret images or reports; it de-identifies and forwards. Its de-identified output is intended for Research Use Only. The de-identification applies HIPAA Safe Harbor tag transforms (45 CFR §164.514(b)(2)); because the keyed pseudonymization and interval-preserving date shift go beyond pure Safe Harbor, the governing certification is a §164.514(b)(1) Expert Determination — yours to make, by a qualified expert of your choosing, not one rendered by Synthology.

Is it cross-platform?

Yes — Windows (MSI installer) and Linux (self-contained tarball), same as the rest of the fleet. The Synthology-hosted deployment runs on Linux; on-prem customers run either.

Build your de-identification boundary.

Cross-network ingest to a Synthology-hosted engine, or an on-prem appliance inside your network? Tell us where your PHI starts and where the de-identified data needs to land, and we’ll come back within one business day with a proposed architecture.