Current version

Release

Product

PrismLink Commercial Authoring

Version

0.2.0 — Alpha 39

Channel

alpha

Status

Evaluation. Not yet released for general availability.

Platform

Windows, on-premise

In this release

Alpha 39 completes the commercial Windows service architecture — the shape the product will keep through general availability.

• Four isolated services, one for each job: DICOM intake, HL7 intake, runtime processing, and the reporting-system connector, each under its own dedicated Windows service identity with file access limited to its role.
• Installed switched off, activated deliberately. Setup installs the services stopped and disabled, with no listener configuration, credentials or firewall rules. A site administrator turns them on explicitly through Studio, confirming with a Windows administrator (UAC) prompt; activation creates exactly two firewall rules, each tied to its own service.
• Credential isolation. The reporting-system password is encrypted to that machine and readable only by the delivery connector. Studio never receives it.

Recent releases

The alpha series leading up to this release added, among other things:

• A built-in Test Lab: a one-click end-to-end demonstration, plus multi-modality and load scenarios, using verified synthetic studies against a simulated scanner and a simulated reporting system — no patient data involved, and unavailable in production mode.
• A single control point for all AI traffic during configuration: approved AI providers only, known patient-identifier fields removed before sending, no silent switching between providers, and an audit entry — without the content — for every request.
• Reviewed multi-document policies: a person classifies how the structured reports of one accession relate — a correction, a separate reading, or a companion document — and a document whose role has not been decided is held rather than merged.
• A short, fixed list of selection rules for choosing among prior and repeated observations — earliest or latest by date, first or last in the document, smallest, largest or average — applied only where the reviewed mapping chose one.
• Deeper migration tooling for sites replacing an existing integration: suggested matches between old and new report fields, side-by-side comparison of both systems' output on real studies, and field-by-field handover with no coverage gap.
• A self-contained Windows installer that carries everything it needs, downloads nothing onto the hospital machine, and is signed — plus updates that recover themselves after an interruption.
• Day-to-day quality of life: patient and accession search from a private local index, automatic refresh when new studies arrive, live mapping status and logs, and faster startup on large configurations.

How updates are distributed

Updates are published as signed packages. The manifest describing a release is signed with an Ed25519 key held offline; the public key is pinned into the installation and is never taken from the update server.

• The distribution server is treated as untrusted. It can serve bytes; it cannot authorise an installation.
• A package is verified before extraction, copied into immutable staging, and verified again there.
• Release sequence numbers only move forward. A superseded release cannot be re-offered as an update.
• Checking, downloading and installing are separate operator actions. Nothing installs itself.
• Installation backs up the existing deployment first and can roll back.