Troubleshooting when data acquisition runs slowly

Data Acquisition is the first step of the data pipeline that pulls data from the EHR, cleans it up, and makes it available for reporting and analysis in Relevant.This article presents tips for diagnosing and resolving a common data acquisition problem.

Note: to access the areas of Relevant discussed in this article, users must have the “View Data Pipeline” ability. To edit pipeline configuration, users must have the “Manage Data Pipeline” ability.

The data acquisition runs slowly

Slow data acquisitions may result from a variety of factors: a slow connection between the machine that hosts Relevant’s Data Acquisition Agent and the machine that hosts the source database; a slow connection from the machine that hosts the Data Acquisition Agent and Relevant’s infrastructure in Google Cloud; or performance issues for the machine that hosts the DAA or the machine that hosts the source database.

The health center’s IT department, or the vendor that manages the source database, will need to troubleshoot. We recommend testing network latency between the three endpoints discussed above; reducing the number of running processes on the Data Acquisition Agent machine and the source database machine; and increasing the CPU and RAM for both machines.