Interoperability

Standards in, nothing out

VerityRT is a standalone system. It does not script a planning system, read a vendor database, or depend on any product's proprietary interface. A case arrives as standard radiotherapy objects, and nothing leaves through a write path, because none is built.

No vendor dependency

This platform is original work. It is not affiliated with, endorsed by, or derived from any treatment planning system vendor, and it reproduces no vendor source code, proprietary algorithm, confidential documentation, screen layout, icon set or trade dress. Where a vendor product is named anywhere in this material, it is named only to describe a standard interchange format that product also writes.

One boundary

Everything the system knows about a case arrives through a single interface. A site implements one file.

The ingest adapter: One interface with five methods: list cases, read the case, read the structure set, read the plan, read the dose. It returns an intermediate representation named the way this system names things, not the way a wire format names them.
Identifiers are first-class: Frame of reference, referenced series, referenced structure set and referenced plan are fields in that representation, not metadata carried alongside it. An object in the wrong frame of reference describes a different patient position, and every geometric number derived from the pair would then be attached to the wrong anatomy.
Integrity before interpretation: Referential checks run before any agent sees the case: frame of reference agreement, plan to structure set, dose to plan, histogram to region of interest, prescription target presence, beam meterset presence, and whether the modality is one the pipeline has been exercised against. A blocking problem stops the case, and the orchestrator halts before producing output derived from inconsistent parts.
No byte parser of our own: The adapter wraps an established DICOM library rather than a parser written here. A hand-written parser can only be tested against data its own author encoded, which shows that an encoder and a decoder agree with each other rather than that either agrees with the standard — and the failure would be silent.
Read-only by construction: There is no write method on the interface. Not a flag that is off: a method that does not exist. The same is true of the treatment record; this platform reads it and never writes to it.

What a case is made of

The system consumes the objects a plan review actually depends on, and nothing else.

Image series, with spacing and slice count
Frame of reference and study identifiers
Structure sets and each region of interest
Interpreted type, volume and contour extent
Plan label, intent and approval state
Beams, arcs, energies and control points
Beam meterset in monitor units
Dose grid dimensions, spacing and units
Dose summation type
Dose-volume histograms and their type
Prescription dose, fractions and named target
Who approved what, and when

Those inputs become 21 named artifacts inside the workflow. Four of them can only be produced by a person signing a gate, which is how a signature becomes structurally required rather than politely requested.

Two refusals worth stating plainly

Ingest never asserts deliverability or clearance: Neither is in an export. Deliverability is a machine question and collision clearance needs the machine model and the patient outline. So ingest records a clearance value no machine minimum accepts, and the deliverability check runs separately. A plausible-looking number here would be mistaken for a measurement.
A differential histogram is rejected, not converted: Converting one to cumulative form requires bin widths the export does not state. The curve is set aside with its reason shown to the reviewer. Every dose metric this system derives assumes a cumulative curve, and reading a differential curve as cumulative produces wrong numbers that look entirely ordinary.

What a site confirms before a pilot

None of this is software work.

Export path: Which system writes the radiotherapy objects, at which version, and whether the export is automatic or operator-initiated. The adapter is written against that answer.
Protocols with owners: The clinic's approved protocols, checklists and constraint sources, each with a named owner and a review date. Every constraint value in this repository is fictional and is replaced wholesale.
A named physicist: Someone qualified owns the checks, the commissioning record, and the decision that the system's output is fit to review against. This is a person, not a role in a document.
Regression on any interface change: An export format change can alter units, orientation conventions or field semantics with no visible error. An interface running without a passing regression suite is a stop condition that halts the case, not a warning that decorates it.
A non-clinical environment: Everything is exercised against synthetic and retrospective data first. Nothing is pointed at a live clinical system to find out what happens.

Standards baseline

DICOM and DICOMweb: The interchange baseline for imaging and radiotherapy objects, with a published conformance statement naming exactly which objects and attributes are read.
FHIR and HL7 v2: For clinical and administrative exchange, mapped into a canonical internal model that belongs to no single vendor.
TG-263 and ICRU 83: Structure nomenclature and dose reporting notation. Dose metrics are parsed from that notation rather than looked up in a table, so a site can express a constraint the system has never seen without a code change.
Round-trip integrity: Tests for coordinate systems, units, structure references, plan references and dose scaling, because a silent unit error is the worst kind of error this system could carry.

See also the security position, the clinical safety position and the technical documentation.