Skip to content

EndoManager® and Epic Gallery

EndoManager EMS works with Epic Gallery and supports both of Epic's published Gallery integration blueprints: HL7 MDM with web blob storage, and the Gallery file sweep. Once Gallery is in place, it becomes the source of truth for the image, and EMS no longer has to send the image back to Epic by API. Gallery sits between EMS and Epic Lumens, so images land in Epic's image archive and are ready for the Lumens procedure note. Sites moving to Gallery can choose either path. We recommend HL7 MDM.

How it works

  1. Orders and patient data in (HL7). EMS receives orders, scheduling and patient updates from Epic and puts the patient on the room's worklist.
  2. Capture. Images come from DICOM-capable equipment or an EM4 capture station at the tower.
  3. Images to Gallery. EMS sends each image to Epic Gallery by HL7 MDM or by file sweep. From then on, Gallery holds the image of record.
  4. Lumens. Gallery is used with Epic Lumens in almost all cases. Images in Gallery are available to the Lumens procedure note.
  5. Optional archive. EMS can also send copies to another PACS or VNA by DICOM.

The EM4 capture station can also capture and send straight to Epic Gallery on its own, without the full EMS back end.

Gallery integration blueprints

Epic publishes two Gallery blueprints, and NewCura integrates using one of them per site.

Option A: HL7 MDM with web blob storage (recommended)

Option A: EndoManager EMS sends an HL7 MDM message to Epic Gallery, and the images appear in Epic Lumens in the procedure record.

Option B: Gallery file sweep

Option B: EndoManager EMS saves images to a shared folder, Epic Gallery sweeps them in, and they appear in Epic Lumens.
EHREpic (HL7)
Image archiveEpic Gallery
Gallery methodsHL7 MDM (recommended) or file sweep
File types to GallerySingle-image JPEG, PNG or TIFF
Report writerEpic Lumens (used with Gallery in almost all cases)
Other PACS / VNAOptional, DICOM (C-Store, C-Move, Storage Commitment)
Epic Toolbox"EndoManager EMS by NewCura," Endoscope Data Capture

Why we recommend MDM: corrections flow through to Epic

Mistakes happen in a busy endoscopy unit. Images get captured under the wrong patient, or EGD and colonoscopy images end up in a single exam. Your staff fixes it in EndoManager, and with the MDM integration EMS sends the update to Epic Gallery, correcting the images in Epic without a manual Medical Records fix.

In the integration builder

Pick Epic Gallery in the Integrations Builder and it adds Epic Lumens as the report writer and Epic as the EHR automatically, since Gallery workflows almost always run with both. You can add other PACS or VNA destinations alongside Gallery.

Related

Epic and Epic Lumens · Integrations Builder · EndoManager EMS · Image Capture (EM4) · PACS and VNA

Frequently asked questions

Is EndoManager EMS compatible with Epic Gallery?

Yes. EMS supports both of Epic's published Gallery blueprints: HL7 MDM with web blob storage, and the Gallery file sweep.

Where does the image live once we use Gallery?

In Epic Gallery. Gallery becomes the source of truth for the image, so EndoManager no longer needs to send the image back to Epic by API.

Which Gallery integration should we choose?

We recommend HL7 MDM, because it lets corrections made in EndoManager update the images in Epic automatically.

What file types does EMS send to Gallery?

EMS sends individual JPEG, PNG or single-image TIFF files, as Epic requires. It doesn't send multi-image TIFFs, PDFs or DICOM to Gallery.

Do we need Lumens to use Gallery with EndoManager?

Gallery is used with Lumens in almost all cases, and the builder pairs them by default.

Can we send images to Gallery without the full EMS?

Yes. The EM4 capture station can capture and send straight to Epic Gallery on its own.

Compatibility depends on equipment model, software version, and site configuration. Listings and workflow diagrams are for planning only. Your NewCura team confirms every workflow before quoting.

Epic and Lumens are registered trademarks of Epic Systems Corporation.

Product and company names are trademarks of their respective owners and are used only to identify compatibility. Their use does not imply endorsement by, or affiliation with, those companies.

Last reviewed .