EndoManager® with your PACS or VNA
A PACS or VNA is optional with EndoManager. EMS stores images itself, so you don't need an archive to go live. If you have one, EndoManager sends images to it by DICOM, using C-Store, C-Move and Storage Commitment, and it can send to more than one archive, such as the health system's VNA and a community affiliate's.
How images get to the archive
| Protocol | DICOM: C-Store (send), C-Move (retrieve), Storage Commitment (confirm the archive has the study) |
|---|---|
| Sends from | EndoManager EMS, or straight from an EM4 capture station |
| How many archives | Optional, one or more. Each destination is labeled in the workflow |
| HL7 to the archive | Not needed. PACS and VNA connections are DICOM only |
Epic Gallery
Epic Gallery, Epic's image archive, sits between EMS and Lumens. EndoManager supports both connection methods in Epic's integration blueprint: HL7 MDM (recommended) and file drop / sweep. A Gallery workflow also uses Epic as the EHR and Lumens as the report writer. Epic integration →
Archives in the integration library
- Epic Gallery (HL7 MDM or file sweep)
- Fujifilm Synapse PACS / Synapse VNA (DICOM)
- Mach7 Enterprise Imaging Platform / VNA (DICOM)
- AGFA HealthCare (DICOM)
- Sectra (DICOM)
- Merge by Merative (DICOM)
- Hyland (Acuo) (DICOM)
- Philips Vue (DICOM)
- GE HealthCare (DICOM)
- Visage Imaging (DICOM)
- Other DICOM archives, by the same C-Store, C-Move and Storage Commitment connection
Frequently asked questions
Do we need a PACS or VNA to use EndoManager?
No. EMS stores images itself. A PACS or VNA is optional.
Which DICOM services does EndoManager use?
C-Store to send images, C-Move to retrieve them, and Storage Commitment to confirm the archive received them.
Can EndoManager send to more than one archive?
Yes. You can add as many PACS or VNA destinations as you need, each labeled in the workflow.
Does EndoManager work with Epic Gallery?
Yes, by HL7 MDM or by file drop / sweep, both part of Epic's integration blueprint.
Last reviewed .