17.2 Data Queries and Discrepancy Resolution

Data queries are an integral part of the clinical data cleaning process. A query is a formal request for clarification or correction of data entered into the Case Report Form (CRF) or Electronic Data Capture (EDC) system. Resolving these queries efficiently and accurately is one of the most critical responsibilities of a Clinical Research Coordinator (CRC) to ensure data integrity.

Understanding Data Queries

When data is entered into an EDC system, it undergoes various levels of review to ensure it is accurate, logical, and consistent with the protocol and source documents. When a discrepancy, missing value, or illogical entry is identified, a query is generated.

Queries serve multiple purposes:

• Correction: Fixing typographical errors or incorrect data entry.
• Clarification: Explaining anomalous but true values (e.g., an unusually high heart rate that is verified in the source).
• Completion: Prompting the entry of missing data.
• Verification: Confirming that a protocol deviation occurred and is documented.

Types of Queries

Queries generally fall into two categories based on how they are generated:

The Query Lifecycle

The management of a query follows a specific lifecycle, typically tracked within the EDC system. Understanding this workflow is essential for timely resolution.

1. Issuance (Open): The query is created, either automatically by the system or manually by a reviewer. It appears on the site's dashboard as requiring attention.
2. Review: The CRC investigates the query by consulting the source documents to determine if the entered data is correct or if an error was made.
3. Response (Answered): The CRC provides a response. This may involve correcting the data field or providing a clarifying comment (e.g., "Value is correct and matches source").
4. Re-evaluation: The reviewer (who issued the manual query or manages the auto-queries) evaluates the CRC's response.
5. Closure (Closed): If the response satisfactorily resolves the discrepancy, the query is closed. If not, it may be re-issued or a new query generated.

Best Practices for Query Resolution

Handling queries can be time-consuming, but following best practices can streamline the process and reduce the burden on the site.

1. Timeliness is Crucial

Sponsors typically set strict timelines for query resolution, often requiring responses within 3 to 5 business days of issuance. Delayed responses can bottleneck the data cleaning process and delay database lock. CRCs should make checking the EDC for new queries a daily habit.

2. Always Check the Source

Never guess or assume the answer to a query. Every response must be supported by the source document. If the EDC data is incorrect, update the EDC to match the source. If the EDC data is correct but flagged as unusual, respond by stating that the value has been verified against the source.

3. Provide Clear and Concise Responses

When a text response is required, be brief but explicit.

• Poor Response: "It's right."
• Good Response: "Value verified against source document dated 12-May-2025."

4. Do Not Correct Source Documents Improperly

If a query reveals an error in the source document itself (e.g., the physician wrote the wrong year on a lab requisition), the source document must be corrected according to Good Clinical Practice (GCP) guidelines (a single line through the error, initialed, dated, and the correct information added) before the EDC is updated. The EDC must always reflect the source.

Common Query Triggers

Anticipating what triggers queries can help CRCs avoid them during initial data entry. Common pitfalls include:

• Inconsistent Dates: A visit date that falls before the informed consent date, or a stop date for an adverse event that occurs before the start date.
• Missing Information: Leaving required fields blank without using approved missing data codes (like ND for Not Done).
• Concomitant Medications without Indications: Entering a medication (e.g., Lisinopril) without a corresponding medical history entry or adverse event (e.g., Hypertension) to explain why the patient is taking it.
• Out of Window Visits: A visit date that falls outside the protocol-specified window (e.g., Day 14 ± 2 days). While the date may be accurate, the system will flag it to confirm the protocol deviation.

Impact on Site Performance

Query rates are a major metric used by sponsors and Contract Research Organizations (CROs) to evaluate site performance.

• High Query Volume: A consistently high number of queries may indicate poor data entry practices, inadequate training, or staffing shortages at the site. It can trigger additional monitoring visits or audits.
• Slow Resolution Times: Failing to answer queries within the required timeframe negatively impacts the sponsor's ability to analyze data and can delay the entire clinical trial.

Sites that maintain low query rates and fast resolution times are viewed favorably by sponsors, making them highly desirable candidates for future trials. Proactive data management—double-checking entries against source before hitting save—is the most effective way to minimize the query burden.