synthetic-dicomweb-endpoint
dicom-imaging-exchange
imaging informatics, privacy, and clinical governance review before live DICOM or DICOMweb exchange
Request signals
fixture-dicom-imaging-exchange-v1
dicomweb-imaging-synthetic-v1 fixture from synthetic-dicomweb-endpoint
01study: Synthetic study identifier and study-level metadata.
02series: Synthetic series identifier and series-level metadata.
03instance: Synthetic SOP instance identifier without production image data.
04patientReference: Synthetic patient pointer without production identifiers.
05modality: Synthetic imaging modality code.
06accession: Synthetic accession reference.
07acquisitionTimestamp: Synthetic acquisition timestamp preserved from the source fixture.
08sourceEndpoint: Synthetic DICOMweb endpoint identifier.
Expected signals produced after contract normalization.
- study
- series
- instance
- patientReference
- modality
- accession
- acquisitionTimestamp
- sourceEndpoint
Signals that block fixture acceptance when absent.
- study
- series
- instance
- sourceEndpoint
Unsafe connector behavior that must stay blocked.
- diagnostic interpretation
- production image exchange
- unreviewed record mutation
Fixture payload present
Every non-synthetic integration contract must have a synthetic request and expected-response fixture.
Synthetic-only fixture
Integration fixture requests must be explicitly synthetic-only until live connector approval.
Contract binding
Fixture and request payload must bind to the same integration contract slug.
No production identifiers
Fixture payload must not include obvious SSN, MRN, email, or phone identifiers.
Required signals covered
Fixture must cover every required signal declared by the integration contract.
Safeguards mapped
Fixture text must map all declared safeguards into guardrails, trace, review, or prohibited-action controls.
Trace complete
Expected response must include at least four deterministic trace steps.
Live review required
Fixture must require human review before live connector promotion.
Prohibited actions
Expected response must define prohibited actions for unsafe connector behavior.
Diff fingerprint
Fixture diff fingerprint must change when expected request or response fields change.