DICOM integration for endoscopy
The NewVision DICOM Server is the component that lets endoscopy behave like every other imaging modality in the hospital: it receives studies as a Storage SCP, answers and issues worklist queries, wraps captured stills and clips as DICOM objects, and forwards them to the enterprise PACS. It is the same DICOM engine already running in NewVision ultrasound and ophthalmic installations.
Need the paperwork before the meeting? Ask for the DICOM Conformance Statement for the endoscopy configuration: info@new-vision.net.
Service classes
| Service | Role | Use in an endoscopy unit |
|---|---|---|
| Storage SCP (C-STORE) | Receiver | Accepts studies sent by a DICOM-capable endoscopy processor or by a capture station |
| Storage SCU | Sender | Forwards the completed endoscopic series to the enterprise PACS or a second archive |
| Modality Worklist (C-FIND) | Query | Pulls the scheduled procedure list so the patient is selected rather than typed |
| Query / Retrieve (C-GET) | Retrieval | Retrieves prior studies for comparison at review time |
| Storage Commitment | Confirmation | Confirms the receiving archive has taken responsibility before local cleanup |
Objects, transfer syntaxes and metadata
| Item | Detail |
|---|---|
| Still images | Stored as DICOM image objects with patient, study and series context populated from the worklist |
| Video clips | Archived as multi-frame objects or as referenced media, depending on the processor output and PACS acceptance |
| Lossless compression | Lossless JPEG supported — transfer syntax 1.2.840.10008.1.2.4.70 — so the archived image is not degraded relative to what the endoscopist saw |
| Structured Report | SR objects are parsed on receipt, which is how device-produced measurement and procedure data reaches the report without retyping |
| Digital signature | Signature support is available for sites whose retention policy requires it |
| Conformance | A DICOM Conformance Statement is published for the configuration, listing supported SOP classes and roles |
How a study flows
- The worklist query returns today’s scheduled procedures; the endoscopist selects the patient.
- Capture begins. Each still and clip is bound to that study’s identifiers — no free-typed name, no orphan files.
- On a successful C-STORE the SOP instance is written to a local DICOM directory, and patient and study attributes are indexed in the database so the study is searchable immediately.
- Reporting reads from the same study record, which is why the report cannot reference an image that is not archived.
- After sign-off, the series is forwarded to the enterprise PACS as a Storage SCU, and the report is delivered to the EMR through the HL7 or API interface.
- SOP instances remain retrievable indefinitely until deliberately deleted or migrated to long-term storage.
When the processor is not DICOM-capable
This is the common case in endoscopy, and it does not block a DICOM workflow. The capture station becomes the DICOM producer: video or stills are grabbed from the processor’s digital or analogue output, then wrapped with the correct patient, study and series attributes taken from the worklist entry. The enterprise PACS receives standards-compliant objects and cannot tell the difference.
| Processor capability | DICOM path |
|---|---|
| Native DICOM Storage | Processor sends directly to the NewVision Storage SCP |
| Native DICOM + MWL | Processor also queries the worklist, so demographics appear on the tower display |
| Video output only | NewVision capture station grabs and DICOM-wraps; identifiers come from the worklist |
| File export only | Watched-folder import, then DICOM-wrapped and indexed |
Network and deployment notes
- Full implementation of the DICOM upper-layer protocol over TCP/IP, using the AE titles and ports your PACS team assigns.
- The server can run on the same machine as the reporting station in a single-room clinic, or on a dedicated host serving several procedure rooms.
- Studies are archived redundantly, so the DICOM archive is also the malpractice-evidence copy rather than a convenience cache.
- Where enterprise PACS storage is charged by volume, forwarding rules can be scoped to selected series rather than every captured frame.
Frequently asked questions
Can NewVision act as the PACS itself?
Yes for units that do not have an enterprise PACS — the DICOM Server plus its indexed archive is a complete storage and retrieval solution. In hospitals that already own a PACS, NewVision usually feeds it rather than competes with it.
Does the video get compressed lossily?
Stills can be archived with lossless JPEG so the diagnostic image is preserved. Video is handled according to what the processor produces and what the receiving archive accepts; we set this explicitly at commissioning rather than leaving it to a default.
Will our PACS accept endoscopic objects?
Most modern PACS do. The practical checks are which SOP classes it accepts, whether it takes multi-frame objects, and its storage policy for video. We validate against your PACS during installation, the same way the ultrasound DICOM transfer was validated on a Canon (Toshiba) system at Akdeniz University Faculty of Medicine.
Do you support DICOM Structured Reports?
SR objects are parsed when the device sends them, so device-generated data populates the report automatically. Where the processor emits no SR, findings come from the structured template instead.
Can you send to two archives at once?
Yes. Forwarding to a second destination — a research archive, a group-level PACS, or a disaster-recovery copy — is a configuration matter.
Get the conformance documentation
We will send the DICOM Conformance Statement and walk your PACS administrator through AE titles, ports and accepted SOP classes before any installation date is agreed. Contact the team · +90 543 722 22 10
Related: Endoscopy PACS overview · EMR and EHR integration · Ultrasound PACS
