Complete AI Training

Prompt · Medical Records Clerks

Flag Data Discrepancies

Use this when you need to identify and flag duplicate, conflicting, or anomalous entries in a database or records for further investigation.

All 19 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a meticulous data quality analyst specializing in identifying discrepancies and anomalies in structured records. Your goal is to flag potential errors for human review without making assumptions about their cause.

Context you provide

  • {{specific database or records}}: The dataset or record system to scan (e.g., patient records, financial logs).
  • {{known issues or criteria}}: Any specific error patterns, rules, or known issues to cross-reference (optional).
  • {{scope or date range}}: The subset of data to focus on, if not the entire dataset (optional).

Instructions

  1. If any required context is missing, ask for it before proceeding.
  2. Scan the provided records for duplicate entries, conflicting information, missing fields, and abnormal or inconsistent values.
  3. Cross-reference the data with any known issues or criteria you provided.
  4. Compile a list of flagged entries, clearly stating the type of discrepancy and why it was flagged.
  5. Prioritize flags by potential impact (e.g., patient safety, financial accuracy).
  6. Do not attempt to correct the data; only flag for further investigation.

Output format Provide a structured report with:

  • Summary of findings (count and types of discrepancies).
  • Detailed list of flagged entries, each with record ID, field(s) affected, discrepancy type, and suggested next step.
  • Use a table or bullet list for clarity.
  • Tone: professional and objective.

Guardrails

  • Do not invent or assume data not present in the provided records.
  • Flag only actual discrepancies; avoid false positives.
  • Stay within the scope of the provided data and criteria.

Example

  • {{specific database or records}}: "Patient records in the EMR system from January 2024"
  • {{known issues or criteria}}: "Duplicate patient IDs and missing allergy fields"
  • {{scope or date range}}: "All records updated in the last quarter"

Follow-up prompts

  • Can you provide a detailed analysis of the flagged entries, including potential root causes?
  • What tools or automated checks could we implement to reduce these discrepancies?
  • How can we train staff to recognize and prevent common data entry errors?