Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Every EHR integration follows the same project stages 

Preparation:

 1) Sign a Business Associate Agreement (BAA)

A BAA is a legal document required by HIPAA when an entity will be handling Protected Health Information (PHI). It is crucial for any integration with an EHR system to ensure compliance and data protection. You must have a BAA in place before PHI can be uploaded to our products.

 2) Obtain the EHR Implementation Guide

Every EHR has a system Integration Implementation Guides which contain descriptions of the data transport requirements, data schemas and sample data which can be used during interface development.

How do I get the EHR implementation guide?

The best way to get the EHR implementation guide is first to have the provider using the EHR provide it or leverage their EHR vendor contact to obtain the guide.

 3) Requirements gathering 

Start by understanding the system workflows

  • How the data will be exchanged between the source and destination systems?

  • What are the data formats expected by the source and destination systems?

 4) Environment setup

Ensure all necessary Development, Test, and Production IguanaX instances are installed with the appropriate server specifications.

At this stage, you should also be working with the EHR team to obtain access to a sandbox or test system environments. 

Implementation:

 1) Design - Determine interface architecture and data mappings

After gathering the integration requirements and reviewing the system implementation guides, the interface architecture design, the validation test plan, and the data mapping documents should be prepared to expedite the build and test phase. The data mapping document is used to conduct a gap analysis ensuring all the required data is available and can be validated prior to the interface build.

 2) Build and Test - Implement interface and perform quality assurance

Interfaces are built and tested according to the design plan with the sample data from the system vendors. The build phase includes unit and functional testing, focusing on ensuring the mappings and translations match the specifications provided and the interface is operating as expected. The testing phase leverages the external system’s test environments to perform integrated, performance load testing, and soft-go-live testing for the interface. 

 3) Activation - Interface promotion to production (go-live)

Once testing is complete, interfaces can be promoted to the Production environment and turned on. 

  • No labels