DICOM imaging integration — currently no-go
Evidence-collection and pairing requirements for DICOM imaging devices.
DICOM imaging integration — currently no-go
Current status: NO-GO for public setup instructions. Cortex's DICOM receive, study finalization, and image-delivery path is under conformance hardening. This page must not be used to configure a live imaging device.
Why there is no generic recipe
DICOM behavior depends on the exact modality, Conformance Statement, negotiated transfer syntax, SOP classes, association roles, AE policy, and storage lifecycle. A successful association or echo alone does not prove that a study is durably spooled, finalized, correlated, uploaded, rendered, retried, or cleaned up safely.
No fixed called AE, calling AE, listener value, firewall rule, worklist claim, or image destination is valid for every installation. Those values are profile-specific and must come from a paired, reviewed runtime decision and the device's own Conformance Statement.
Evidence required for a future exact profile
For the exact manufacturer, model, software build, modality, and licensed options, obtain and checksum the Conformance Statement and record:
- association direction, AE allow-list, maximum PDU, timeout, TLS policy, and network boundary;
- supported SOP classes, presentation contexts, transfer syntaxes, character sets, and UID validation rules;
- whether the workflow needs storage, worklist, query/retrieve, storage commitment, or another service;
- multi-instance study finalization, restart recovery, duplicate handling, durable acceptance, upload retry, and confirmed encrypted cleanup.
Use only synthetic or deidentified imaging data. Keep raw diagnostic evidence encrypted and access-controlled outside Git; delete it once the signed packet is complete and no later than seven days. Retain only deidentified fixtures, hashes, and provenance.
Current operator action
Do not add a DICOM device from this page. Send the exact model, software build, paired Conformance Statement, and authorised test window to the Vetigen integration owner. The profile will remain NO-GO until the runtime decision, bounded-memory receive tests, durable response tests, actual image delivery, retry, and cleanup evidence pass together.
HL7 analyzer integration — profile-gated
Evidence-collection guidance for analyzer integrations that use an HL7 message profile.
List patients
Returns a paginated list of patients accessible to the clinic associated with your API key. ### Access Model Patients in Vetigen are **global entities** — a single patient record may be shared across multiple clinics via `CustomerClinicConnection`. This endpoint returns patients that have an active connection to the caller's clinic, regardless of which clinic originally created the record. ### Pagination Use `page` and `page_size` query parameters. The response includes `has_more: true` when additional pages are available. ### Common Errors - `PATIENT.ACCESS_DENIED` — API key's clinic has no connection to the requested patients. - `AUTH.RATE_LIMITED` — see rate-limit headers.