Engaging Conversations on Healthcare and Technology

  • TwitterFacebookRSS

EMR Interfacing Best Practices

The demand for healthcare interfaces with Electronic Medical Records (EMR) is increasing. This increase is due to the rising adoption of EMR systems, emerging clinical healthcare data standards (HL7, CCR, CDA, CCD, ELINCS), and increasing interoperability requirements, such as CCHIT (Certification Commission for Healthcare Information Technology).

To achieve the most effective and efficient EMR connectivity, the following steps should be included in the process:

  1. Understand workflow:  Define the workflow within your organization and between your organization and the organization with the EMR system
  2. Document requirements:  Define the data requirements of your systems and the EMR in which you will be exchanging patient information
  3. Implement interfaces:  Build the interfaces to facilitate the workflow and meet each application’s requirements

Understand workflow.  Understanding the healthcare data flow within your organization and then the data flow of the organization with the EMR system is critical when you start automating the healthcare workflow. You cannot successfully automate a system or workflow which you do not fully understand.

Document the requirements.  Documenting the requirements for both applications in terms of the standards being used to transmit the clinical data in the specific data format will help identify the gaps between the two clinical applications. The interface can then bridge the identified gaps between the EMR and your application.

Implement interfaces.  A systematic approach to interface implementation should include the basic stages of developing, testing, implementing, and maintaining the interfaces. An effective and flexible approach, that can include tools, will help overcome common challenges such as technology, patient matching, procedure or physician code matching, and lack of cooperation to meet the end goals.

In summary, an interface to or from an EMR application is no different than an interface for any other healthcare application. Connectivity is achieved by acquiring knowledge regarding the workflow and the requirements, plus utilizing effective methodologies or solutions to implement the interfaces.

Related posts:

  1. How Do HL7 and XML Co-Exist in Clinical Interfacing?
  2. HL7 3.0 Considerations for Healthcare Vendors
  3. HL7 3.0 Considerations for Healthcare Providers (Clinics, Hospitals, Labs, Diagnostic Imaging)
  4. What Is HL7 Version 3 or V3?
  5. Why Map HL7 Messages?
Posted in CCD, CCR, CDA, EMR
  • http://qianjin.m-book.net/?p=30 qianjin@Health » Blog Archive » EMR Interfacing Best Practices

    [...] EMR Interfacing Best Practices [...]

  • http://www.xbuyonline.com Marcus Bactroban

    Thanks again for another excellent post.

  • http://www.hl7standards.com/blog/2007/11/02/get-the-workflow-right-first/ Get the Workflow Right First

    [...] on your workflowis critical to any healthcare IT project or initiative. Once the workflow is documented and [...]

  • http://eldir.info/ Eric

    Thanks for usefull information.

  • http://www.hl7standards.com/blog/2008/06/12/hl7-continuity-of-care-document-quick-start-guide/ HL7 Continuity of Care Document Quick Start Guide

    [...] EMR Interfacing Best Practices [...]

  • http://www.hl7standards.com/blog/2008/01/25/comparing-hl7-messages-to-hl7-documents/ Comparing HL7 Messages to HL7 Documents | HL7 Standards

    [...] information at one specific point in time. Both are critical, however, especially when delivering connectivity or integration to Electronic Medical Record (EMR) applications in various healthcare provider [...]

blog comments powered by Disqus