> ## Documentation Index
> Fetch the complete documentation index at: https://docs.carelane.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Creating Queries

> How to raise data quality queries

Data queries are raised by the study team to request clarification or correction of submitted data. This guide covers how to create effective queries.

## Who Can Create Queries

| Role                           | Can Create Queries |
| ------------------------------ | ------------------ |
| **Data Reviewer (Study Team)** | Yes                |
| **Study Administrator**        | Yes                |
| **CI/D-CI**                    | Yes                |
| **Site Roles**                 | No                 |

## Creating a Query

<Steps>
  <Step title="Navigate to Record">
    Open the participant record and questionnaire response.
  </Step>

  <Step title="Select Field">
    Identify the field requiring clarification.
  </Step>

  <Step title="Open Query Dialog">
    Click the query icon or "Raise Query" option for the field.
  </Step>

  <Step title="Enter Query Details">
    Provide query text and options.
  </Step>

  <Step title="Submit">
    Submit the query. Site team is notified.
  </Step>
</Steps>

## Query Details

### Query Text

Write clear, specific query text:

* Describe the issue or discrepancy
* Specify what information is needed
* Reference relevant guidelines if applicable

<Tip>
  Good example: "The recorded blood pressure (280/160 mmHg) appears unusually high. Please verify this value against source documents."

  Avoid: "Check BP"
</Tip>

### Value Change Expected

Indicate whether you expect the data to change:

| Option  | When to Use                               |
| ------- | ----------------------------------------- |
| **Yes** | Data appears incorrect; expect correction |
| **No**  | Need clarification; data may be correct   |

This helps site teams understand what's needed.

## Query Reasons

Categorize queries by reason:

| Reason                  | Description                       |
| ----------------------- | --------------------------------- |
| **Clarification**       | Need more information             |
| **Out of Range**        | Value outside expected range      |
| **Missing Data**        | Required data not provided        |
| **Inconsistency**       | Data conflicts with other entries |
| **Protocol Deviation**  | Potential protocol deviation      |
| **Transcription Error** | Likely data entry mistake         |

## Field-Level vs. Record-Level

### Field-Level Queries

Most common type:

* Associated with a specific field
* Displayed inline with the field
* Clear context for site response

### Record-Level Queries

For general issues:

* Not tied to specific field
* Address overall record concerns
* May span multiple fields

## Query Tips

### Be Specific

<Accordion title="Examples of Specific vs. Vague Queries">
  **Specific (Good):**

  * "Date of Visit (15-Jan-2024) is before enrollment date (20-Jan-2024). Please clarify."
  * "Weight value (750 kg) exceeds physiological range. Please verify."

  **Vague (Avoid):**

  * "Check date"
  * "Weight looks wrong"
</Accordion>

### Provide Context

Include relevant context:

* What triggered the query
* What the expected value might be
* Reference to related data if applicable

### One Issue Per Query

Address one issue per query:

* Easier for site to respond
* Clearer audit trail
* Independent resolution

## Bulk Query Operations

For multiple related issues:

<Steps>
  <Step title="Review Records">
    Identify all records with similar issues.
  </Step>

  <Step title="Create Individual Queries">
    Create a query on each affected record.
  </Step>

  <Step title="Track as Group">
    Note the related queries for follow-up.
  </Step>
</Steps>

## Query Templates

If available, use query templates:

* Standardized text for common issues
* Consistent query quality
* Faster query creation

## Effect of Query Creation

When a query is created:

| Change            | Result                           |
| ----------------- | -------------------------------- |
| Record Status     | Changes to "Queries in Progress" |
| Site Notification | Site team alerted                |
| Query Count       | Incremented for tracking         |
| Audit Trail       | Query creation logged            |

## Best Practices

<AccordionGroup>
  <Accordion title="Review Before Querying">
    Ensure you've examined all relevant data before raising a query.
  </Accordion>

  <Accordion title="Professional Tone">
    Write queries professionally and neutrally.
  </Accordion>

  <Accordion title="Set Correct Expectations">
    Accurately indicate if value change is expected.
  </Accordion>

  <Accordion title="Avoid Duplicate Queries">
    Check for existing queries before creating new ones.
  </Accordion>
</AccordionGroup>

## Related

<CardGroup cols={2}>
  <Card title="Query Lifecycle" icon="circle-question" href="/data-quality/query-lifecycle">
    Full query workflow.
  </Card>

  <Card title="Responding to Queries" icon="reply" href="/data-quality/responding-queries">
    How sites respond.
  </Card>
</CardGroup>