{"id":5185,"date":"2026-07-30T15:36:19","date_gmt":"2026-07-30T15:36:19","guid":{"rendered":"https:\/\/www.new-vision.net\/endoscopy-pacs\/emr-ehr-integration\/"},"modified":"2026-07-30T15:36:19","modified_gmt":"2026-07-30T15:36:19","slug":"emr-ehr-integration","status":"publish","type":"page","link":"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/emr-ehr-integration\/","title":{"rendered":"Endoscopy EMR and EHR Integration"},"content":{"rendered":"<style>\n.nv-page{max-width:980px;margin:0 auto}\n.nv-page h1{margin:0 0 .5em}\n.nv-page h2{margin:1.8em 0 .6em}\n.nv-page h3{margin:1.3em 0 .3em;font-size:1.05em}\n.nv-lede{font-size:1.15em;line-height:1.65}\n.nv-page table{width:100%;border-collapse:collapse;margin:1.2em 0;font-size:.95em}\n.nv-page th,.nv-page td{border:1px solid #dde3ea;padding:.6em .8em;text-align:left;vertical-align:top}\n.nv-page th{background:#f4f7fa;font-weight:600}\n.nv-cta{background:#f4f7fa;border-left:4px solid #0a6ebd;padding:1em 1.2em;margin:1.6em 0}\n.nv-note{font-size:.9em;color:#5b6b7c}\n.nv-page ul,.nv-page ol{margin:.6em 0 1em 1.4em}\n<\/style>\n<div class=\"nv-page\">\n<h1>Endoscopy EMR and EHR integration<\/h1>\n<p class=\"nv-lede\">An endoscopy system that cannot exchange data with the EMR simply moves the retyping somewhere else. NewVision Endoscopy connects in both directions: it consumes orders, demographics and scheduling from the EMR, EHR or HIS, and it returns the signed report, the coded findings and the image series to the patient record.<\/p>\n<div class=\"nv-cta\">\n<p>Sending us your interface engine, EMR vendor and message samples is usually enough for us to scope the integration in one call. <a href=\"\/en\/contact-us\/\">Start an integration scoping call<\/a>.<\/p>\n<\/div>\n<h2>The two directions that matter<\/h2>\n<table>\n<tr>\n<th>Direction<\/th>\n<th>What moves<\/th>\n<th>Why the unit cares<\/th>\n<\/tr>\n<tr>\n<td>Inbound \u2014 EMR to endoscopy<\/td>\n<td>Scheduled procedures, patient identifiers, demographics, ordering physician, indication, accession number<\/td>\n<td>The clinician selects the patient from a worklist instead of typing a name at the tower, which is where wrong-patient attachment starts<\/td>\n<\/tr>\n<tr>\n<td>Outbound \u2014 endoscopy to EMR<\/td>\n<td>Signed PDF report, coded findings, procedure and specimen data, image series, study status<\/td>\n<td>Referring physicians and the rest of the care team read the result inside the chart, not as a scan attached later<\/td>\n<\/tr>\n<\/table>\n<h2>Integration mechanisms<\/h2>\n<p>Which mechanism applies depends on what your hospital&#8217;s interface layer already speaks. NewVision supports the three that cover practically every site.<\/p>\n<table>\n<tr>\n<th>Mechanism<\/th>\n<th>Typical use<\/th>\n<th>Notes<\/th>\n<\/tr>\n<tr>\n<td>HL7 v2 messaging<\/td>\n<td>ADT for demographics, ORM\/OMG for orders, ORU for results and report delivery, SIU for scheduling<\/td>\n<td>The workhorse in hospital environments; routed through an interface engine such as Mirth, Rhapsody, Cloverleaf or the vendor&#8217;s own<\/td>\n<\/tr>\n<tr>\n<td>DICOM Modality Worklist<\/td>\n<td>Worklist query from the endoscopy workstation and, where the processor supports it, from the processor itself<\/td>\n<td>Covered in detail on the <a href=\"\/en\/endoscopy-pacs\/dicom-integration\/\">DICOM integration page<\/a><\/td>\n<\/tr>\n<tr>\n<td>REST \/ API and database interface<\/td>\n<td>Real-time exchange with modern EHR platforms, appointment sync, status callbacks<\/td>\n<td>Used where the EHR exposes an API rather than a message feed<\/td>\n<\/tr>\n<tr>\n<td>Report file delivery<\/td>\n<td>PDF\/A report written to a watched share or transferred to a document repository<\/td>\n<td>Fallback path for sites whose EMR only accepts documents<\/td>\n<\/tr>\n<\/table>\n<h2>What a typical integration looks like<\/h2>\n<ol>\n<li><strong>Identifier agreement.<\/strong> We fix which identifier is authoritative \u2014 national ID, MRN, or visit\/accession number \u2014 before anything else, because mismatched identifiers cause every downstream reconciliation problem.<\/li>\n<li><strong>Inbound feed.<\/strong> Scheduling or order messages populate the endoscopy worklist. Same-day additions and cancellations are handled, since endoscopy lists change during the session.<\/li>\n<li><strong>Study performed.<\/strong> Capture and reporting happen in NewVision; the study carries the accession number through unchanged.<\/li>\n<li><strong>Sign-off event.<\/strong> Only a signed report triggers outbound delivery, so drafts never reach the chart.<\/li>\n<li><strong>Outbound delivery.<\/strong> The report goes to the EMR; images go to the enterprise PACS or to a NewVision archive that the EMR links out to.<\/li>\n<li><strong>Reconciliation.<\/strong> Failed or unacknowledged messages are queued and retried rather than silently dropped, with a log the hospital&#8217;s integration team can read.<\/li>\n<\/ol>\n<h2>Turkey: HBYS and e-Nab\u0131z<\/h2>\n<p>For Turkish hospitals and clinics the integration question is more specific. NewVision has been transferring images and reports into HBYS systems for years, including worklist appointment support, and the same outbound chain is what makes the e-Nab\u0131z obligation practical instead of a manual export routine. Turkish-language documentation and templates ship with the system.<\/p>\n<h2>Access control and audit<\/h2>\n<ul>\n<li>Role-based access so capture staff, reporting clinicians and administrators see different functions.<\/li>\n<li>Report sign-off is attributable to a named clinician, which is the point at which the document becomes the legal record.<\/li>\n<li>Study and report actions are logged, supporting both internal audit and the evidentiary use of the archive.<\/li>\n<li>Retention and archive policy is set by the institution, not hard-coded by the software.<\/li>\n<\/ul>\n<h2>Frequently asked questions<\/h2>\n<div class=\"nv-faq\">\n<h3>We use an interface engine. Do you connect to it or to the EMR directly?<\/h3>\n<p>To the interface engine, in almost every hospital. That is what it is for, and it keeps the integration inside your existing change-control process. Direct connections make sense mainly in single-clinic installations with no engine.<\/p>\n<h3>Which HL7 message types do you handle?<\/h3>\n<p>ADT for demographics, order messages for procedures, ORU for results and report delivery, and SIU where scheduling drives the worklist. The precise message set is agreed during scoping because sites profile HL7 differently.<\/p>\n<h3>Can the report be structured data rather than a PDF?<\/h3>\n<p>Yes. Coded findings and procedure data can be delivered as discrete fields in the outbound message, with the PDF carried as the human-readable rendering. Sites that want quality metrics need the discrete fields.<\/p>\n<h3>What happens if the EMR interface is down mid-session?<\/h3>\n<p>The endoscopy session continues. Capture and reporting are local, and outbound messages queue until the interface recovers. Losing the interface should never stop a procedure list.<\/p>\n<h3>Who does the integration work?<\/h3>\n<p>Our team builds and tests the NewVision side and works against your interface team&#8217;s specification. Message mapping is validated in a test environment against real message samples before go-live.<\/p>\n<h3>Does this also apply to the ultrasound product?<\/h3>\n<p>Yes \u2014 the same integration layer serves <a href=\"\/en\/ultrasound-pacs\/\">NewVision Ultrasound<\/a>, so a hospital running both disciplines maintains one interface pattern rather than two.<\/p>\n<\/div>\n<h2>Next steps<\/h2>\n<div class=\"nv-cta\">\n<p>Bring your EMR vendor name, interface engine and a sample message set to the first call and we can tell you what the endoscopy integration will involve. <a href=\"\/en\/contact-us\/\">Contact us<\/a> \u00b7 <a href=\"mailto:info@new-vision.net?subject=Endoscopy%20EMR%20integration\">info@new-vision.net<\/a> \u00b7 <a href=\"tel:+905437222210\">+90 543 722 22 10<\/a><\/p>\n<\/div>\n<p class=\"nv-note\">Related: <a href=\"\/en\/endoscopy-pacs\/\">NewVision Endoscopy PACS overview<\/a> \u00b7 <a href=\"\/en\/endoscopy-pacs\/dicom-integration\/\">DICOM integration<\/a> \u00b7 <a href=\"\/en\/endoscopy-pacs\/report-templates\/\">Report templates<\/a><\/p>\n<\/div>\n<p><script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@graph\": [\n    {\n      \"@type\": \"Organization\",\n      \"@id\": \"https:\/\/www.new-vision.net\/#organization\",\n      \"name\": \"NewVision\",\n      \"legalName\": \"URAL Telekom\",\n      \"url\": \"https:\/\/www.new-vision.net\/\",\n      \"logo\": \"https:\/\/www.new-vision.net\/wp-content\/uploads\/2021\/06\/logo.png\",\n      \"email\": \"info@new-vision.net\",\n      \"telephone\": \"+90-543-722-2210\"\n    },\n    {\n      \"@type\": \"WebPage\",\n      \"@id\": \"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/emr-ehr-integration\/#webpage\",\n      \"url\": \"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/emr-ehr-integration\/\",\n      \"name\": \"Endoscopy EMR and EHR Integration with HL7 and DICOM\",\n      \"inLanguage\": \"en\",\n      \"about\": { \"@id\": \"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/#software\" },\n      \"publisher\": { \"@id\": \"https:\/\/www.new-vision.net\/#organization\" }\n    },\n    {\n      \"@type\": \"BreadcrumbList\",\n      \"@id\": \"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/emr-ehr-integration\/#breadcrumb\",\n      \"itemListElement\": [\n        { \"@type\": \"ListItem\", \"position\": 1, \"name\": \"NewVision\", \"item\": \"https:\/\/www.new-vision.net\/en\/\" },\n        { \"@type\": \"ListItem\", \"position\": 2, \"name\": \"Endoscopy PACS\", \"item\": \"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/\" },\n        { \"@type\": \"ListItem\", \"position\": 3, \"name\": \"EMR and EHR integration\", \"item\": \"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/emr-ehr-integration\/\" }\n      ]\n    },\n    {\n      \"@type\": \"FAQPage\",\n      \"@id\": \"https:\/\/www.new-vision.net\/en\/endoscopy-pacs\/emr-ehr-integration\/#faq\",\n      \"mainEntity\": [\n        {\n          \"@type\": \"Question\",\n          \"name\": \"Do you connect to our interface engine or to the EMR directly?\",\n          \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"To the interface engine in almost every hospital, which keeps the integration inside your existing change-control process. Direct connections make sense mainly in single-clinic installations with no engine.\" }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"Which HL7 message types does NewVision Endoscopy handle?\",\n          \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"ADT for demographics, order messages for procedures, ORU for results and report delivery, and SIU where scheduling drives the worklist. The precise message set is agreed during scoping because sites profile HL7 differently.\" }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"Can the endoscopy report be delivered as structured data rather than a PDF?\",\n          \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"Yes. Coded findings and procedure data can be delivered as discrete fields in the outbound message, with the PDF carried as the human-readable rendering. Discrete fields are required for unit quality metrics.\" }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"What happens if the EMR interface goes down during a procedure list?\",\n          \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"The session continues because capture and reporting are local. Outbound messages queue until the interface recovers.\" }\n        },\n        {\n          \"@type\": \"Question\",\n          \"name\": \"Who performs the integration work?\",\n          \"acceptedAnswer\": { \"@type\": \"Answer\", \"text\": \"The NewVision team builds and tests the endoscopy side against your interface team's specification, and message mapping is validated in a test environment against real message samples before go-live.\" }\n        }\n      ]\n    }\n  ]\n}\n<\/script><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Two-way endoscopy integration with EMR, EHR and HIS: HL7 v2 messaging, DICOM Modality Worklist, REST APIs, signed report delivery, plus HBYS and e-Nabiz support in Turkey.<\/p>\n","protected":false},"author":12,"featured_media":0,"parent":5179,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":[],"_links":{"self":[{"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/pages\/5185"}],"collection":[{"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/users\/12"}],"replies":[{"embeddable":true,"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/comments?post=5185"}],"version-history":[{"count":0,"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/pages\/5185\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/pages\/5179"}],"wp:attachment":[{"href":"https:\/\/www.new-vision.net\/en\/wp-json\/wp\/v2\/media?parent=5185"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}