Capabilities

Sources

• DICOM Structured Reports received over the network from ultrasound, DXA, CT post-processing and other structured-reporting modalities.
• HL7 ORU result messages received over MLLP, for departments whose structured data arrives as observation results rather than DICOM.
• Every received document is retained byte-for-byte in a content-addressed archive, with an append-only record of its status. The original is never modified.

Mapping

The same anatomical measurement is encoded differently by every manufacturer, and often differently between software versions of the same scanner. PrismLink treats device identity — modality, manufacturer, model and software version — as part of the mapping key, so a firmware upgrade that moves a value cannot silently redirect it into the wrong field.

• Clinical field ontology. A curated catalogue of report fields per exam type, versioned, with units, data types and permitted values.
• Per-device mapping. Each device's encoding is mapped to that ontology once, reviewed, and then applied to every subsequent study from that device.
• Repeatable findings. Measurements that occur per fetus, per lesion or per follicle keep their instance identity rather than being flattened into one value.
• Several documents, one exam. Where a single accession produces multiple structured reports, outputs are aggregated under review, with corrections superseding earlier documents.

Transformation

• Unit conversion between declared source and destination units, with per-field overrides.
• Site formatting — rounding, precision and presentation, configured once and applied consistently.
• Calculated fields authored in the browser from a closed, audited set of operations: arithmetic, typed conditional logic, and lookups against published clinical reference tables such as gestational-age percentile curves.
• Bounded values (<3%) retain their comparator as data rather than being silently rounded to the threshold.

Delivery

• Values are written into the reporting system as discrete custom report fields.
• A durable spool tracks every delivery attempt through to acknowledgement, with failed sends retained for inspection rather than discarded.
• A correction that removes a previously delivered value emits an explicit clear, so a stale number cannot persist in the report.

Configuration

PrismLink is configured through PrismLink Studio™, a browser interface served locally by the application. Setup walks through connecting modalities and the reporting system, indexing the exams a site actually performs, organising them, mapping them, and reviewing the result before anything goes live.

Day-to-day, Studio shows any received study side by side with what PrismLink extracted from it — the full structured source on one side, the mapped report fields on the other — so a mapping can be inspected against the study that produced it.

Deployment and data handling

• On-premises. PrismLink runs on hospital-controlled infrastructure inside the network, alongside the imaging and reporting systems. Studies are received, stored and processed locally.
• Deterministic runtime. Live study processing is performed entirely by audited local code. No external service is contacted to deliver a study.
• AI-assisted configuration. During setup, PrismLink can use a language model to propose how a device's encoding maps to the field ontology. Those proposals are reviewed and accepted by a person before they take effect, and the accepted mapping is then executed deterministically. This authoring step is the only point at which study content may be sent to an external model provider, and it can be operated under the appropriate agreements with that provider.
• Signed updates. Software updates are cryptographically signed and verified against a public key pinned at installation. The distribution server is treated as untrusted: an update is verified before it is extracted, and again before it is installed.