How to Handle Conflicting Source Documents (and Document It Correctly)
In pharmacovigilance, the source documents don’t always agree.
A clinical narrative may conflict with a discharge summary. A lab report may contradict a progress note. An EDC entry may not match the medical record. And sometimes, the only “source” is a fragmented report from a site or patient.
Conflicting information is not rare, it’s normal in real-world safety case processing. The real risk isn’t that the documents conflict. The risk is how the case is documented when they do.
A well-written, defensible ICSR narrative can withstand conflicting data. A vague narrative can create audit risk, rework, and downstream confusion for reviewers and signal detection teams.
⸻
Why Conflicting Source Documents Matter
When source documents conflict, teams often respond in one of two ways:
1. They choose one version of the facts and write the narrative as if it’s confirmed, or
2. They include everything without structure, resulting in a confusing narrative that reads like a copy/paste.
Neither approach is defensible.
The goal is not to “solve” the conflict in the narrative. The goal is to document it clearly, transparently, and in a way that supports clinical review.
⸻
Common Types of Conflicts in Safety Cases
Conflicts can show up in many forms, but these are the most common:
1) Timeline Conflicts
• AE onset date differs between notes
• Medication start/stop dates vary
• Hospital admission dates don’t match
2) Diagnosis Conflicts
• One document states pneumonia, another states pulmonary edema
• One note calls it an allergic reaction, another calls it anxiety
3) Lab / Imaging Conflicts
• Labs reported in EDC don’t match the actual lab report
• Imaging impression differs between preliminary vs final read
4) Outcome Conflicts
• One note indicates recovery, another indicates ongoing symptoms
• Follow-up information is missing or contradictory
5) Treatment Conflicts
• Medication changes appear in the MAR but not in provider notes
• Steroids given but not documented consistently
⸻
The Most Defensible Mindset: “Clarify, Don’t Guess”
In PV documentation, the most defensible approach is simple:
Do not guess. Do not smooth over. Clarify what is known and what is conflicting.
Your narrative should communicate:
• What each source states
• Where the discrepancy is
• What the most reliable source appears to be (if appropriate)
• What is unknown / unconfirmed
• Whether follow-up was requested or possible
This protects the case, the sponsor, and the medical reviewer.
⸻
Step-by-Step: How to Handle Conflicting Source Documents
Step 1: Identify the conflict clearly
Before you write anything, isolate exactly what is conflicting.
Ask yourself:
• What is the “fact” that differs?
• Which documents contain each version?
• Are the documents from the same time period?
• Is one a summary and one a contemporaneous record?
⸻
Step 2: Prioritize contemporaneous clinical documentation
As a general rule, documentation created closest to the event tends to be more reliable than retrospective summaries.
Examples:
• ED provider note written on the day of the event
• Lab report with timestamp
• Final imaging report
Less reliable (but still important):
• Discharge summary written later
• Case report form completed after the fact
• Patient recollection with no clinical confirmation
This doesn’t mean you ignore the less reliable source, it means you treat it appropriately.
⸻
Step 3: Write the narrative to reflect the conflict transparently
Instead of forcing the case into one storyline, document it as a known discrepancy.
A defensible narrative might say:
“The AE onset date was inconsistently reported. The ED note dated 12-Jan-2026 documented symptom onset on 10-Jan-2026, while the discharge summary dated 15-Jan-2026 documented onset on 11-Jan-2026.”
This is far stronger than choosing one date and pretending it’s confirmed.
⸻
Step 4: Avoid loaded language
This is a big one.
Avoid phrases like:
• “The patient clearly experienced…”
• “It is certain that…”
• “This was definitely caused by…”
When the sources conflict, certainty is not defensible.
Use neutral clinical language:
• “reported”
• “documented”
• “noted”
• “per”
• “per available records”
⸻
Step 5: Use structured wording to keep the narrative readable
Conflicting source documentation can quickly make narratives messy.
A clean approach is to group information by:
• Event summary
• Timeline
• Diagnostics
• Treatment
• Outcome
• Follow-up / missing information
This keeps the narrative reviewer-friendly while still transparent.
⸻
Step 6: Document follow-up attempts (if applicable)
If the case required clarification, it’s defensible to show that follow-up was requested.
Example language:
“Follow-up was requested to clarify AE onset date; no additional information was available at the time of case processing.”
That single sentence can be the difference between a clean audit trail and a finding.
⸻
Examples: Defensible Narrative Language for Conflicting Sources
Here are a few ready-to-use examples (and these are very “SCS”):
Timeline conflict
“The onset date was inconsistently reported across source documents.”
Diagnosis conflict
“The diagnosis was variably documented as urticaria in the ED note and anxiety/panic reaction in the discharge summary.”
Lab conflict
“The CRF documented a potassium of 2.9 mmol/L; however, the available lab report documented potassium 3.4 mmol/L on the same date.”
Outcome conflict
“The outcome was inconsistently reported. The progress note documented symptom improvement, while follow-up information was not available to confirm resolution.”
⸻
What Not to Do (Common Mistakes)
Even experienced teams fall into these traps:
❌ Mistake 1: “Choosing the best story”
PV is not storytelling. It’s documentation.
❌ Mistake 2: Copy/pasting both sources without explanation
This creates confusion and makes medical review harder.
❌ Mistake 3: Writing around the conflict
Avoiding the discrepancy doesn’t remove it, it just makes it look like the case wasn’t reviewed carefully.
❌ Mistake 4: Using absolute conclusions
If the source data conflicts, your narrative should not sound definitive.
⸻
Why This Matters for Inspection Readiness
When inspectors review safety cases, they often look for:
• Consistency with source
• Evidence of review
• Traceability
• Clinical logic
• Documentation of uncertainty
Conflicting source documents are a test of your case processing maturity.
A defensible narrative doesn’t need perfect data — it needs transparent, clinically sound documentation.
⸻
How SafeCue Solutions Helps
At SafeCue Solutions, we support biotech and safety teams with:
• Narrative QC and defensibility review
• Backlog remediation without sacrificing quality
• Support for complex cases with inconsistent or incomplete documentation
• Human-in-the-loop review that strengthens inspection readiness
If your team is seeing increased complexity — or inconsistent source documentation is becoming the norm — we can help stabilize your narrative quality and reduce rework.
