Endoscope Data Capture How endoscopy images get from the scope to the EHR

Endoscope Data Capture is Epic's Toolbox category for software that gathers data from a scope, formats it, and sends it downstream. Epic says it is currently focused on image data, and that this data is used throughout Lumens workflows, such as documenting findings or writing a procedure note. NewCura's listing in that category is "EndoManager EMS by NewCura." Epic does not endorse, certify, or verify the integrity, safety, performance, or practices of NewCura or its software. Source: Epic Showroom, listing 3848 (opens in a new tab).

The listing "EndoManager EMS by NewCura" is listed with Toolbox status in the Endoscope Data Capture category (listing 3848). Epic describes Toolbox products as following Epic recommended connection practices for a category. Epic does not endorse, certify, or verify the integrity, safety, performance, or practices of NewCura or its software. View the listing on Epic Showroom (opens in a new tab).

Yes. EndoManager EMS takes orders, scheduling, and patient updates from Epic, puts the patient on the room's worklist, and sends captured images straight into the Lumens procedure note. A separate VNA is not required. See Epic integration details.

No. EndoManager stores images itself and sends them straight to Lumens. If you already use a PACS or VNA, EndoManager can route copies there too. It also works with Epic Gallery.

EndoManager EMS can send images to Epic Gallery in two ways: over HL7 MDM, or by a file drop, sometimes called a sweep. Both are ways Epic supports sending images to Gallery, and both can be used alongside Epic Lumens. If a wrong-patient image is corrected in EMS after it was sent over HL7 MDM, that correction carries through to Gallery. That carry-through applies to the MDM path, not to file drop or sweep.

Yes. EndoManager EMS exchanges HL7 messages with Oracle Health, formerly Cerner, and sends endoscopy images directly to Cerner by batch prep. Orders and patient details come in from Cerner so each image lands on the right patient. A separate VNA is not required; if you use a PACS or VNA, EMS can send copies there too. See Oracle Health (Cerner) integration details.

Yes. EndoManager EMS connects to MEDITECH, including MEDITECH Expanse, by HL7. Orders and patient details come in from MEDITECH so staff pick the patient from the room's worklist. Images go to the MEDITECH record as a PDF, either base64-encoded over HL7 or as a cold-feed PDF drop. Images can also be archived to a PACS or VNA by DICOM. See MEDITECH integration details.

Epic, Oracle Health (Cerner), and MEDITECH. Other connections are scoped per project. Call 866.578.5713 or schedule a demo to talk through your record system.

The EHR sends the order to EndoManager, which puts the patient on the room's worklist. The room captures, either from a camera that supports DICOM worklist or with EndoManager 4 (Image Capture) at the tower. EndoManager then forwards the images to the record, mostly hands-free.

No. Rooms with cameras that support DICOM worklist can send stills straight to EndoManager EMS. Rooms whose equipment does not support that path use EndoManager 4, a capture station connected to the tower, for stills and video.

EndoManager is vendor-neutral. It works with Fujifilm, Olympus, Pentax, and other camera systems, including mixed fleets. If a device produces a visible-light image and has a video output, it can be captured with EndoManager 4.

Yes. A PACS or VNA is optional, because EndoManager can store images on its own. If you use one, EMS can route images there by DICOM, including to more than one archive.

Yes. Sites that want a GI-specific report writer can use EndoManager Report Writer (EndoManager 3). Sites that only need images use EndoManager EMS and, where needed, EndoManager 4.

Yes. A NewCura integration engineer can share the interface specification, DICOM conformance statement, and HL7 samples during evaluation. Call 866.578.5713 or schedule a demo.