STAGE 02 · CLINICAL EVIDENCE
Resolve 3 inconsistencies in the LINQ-NEXT clinical evidence corpus.
TRIAGE QUEUE · YOUR CALL
VECTOR caught 3 inconsistencies in the evidence corpus.
During cross-validation of 847 patient records against the locked SAP, DSMB packets, and PMCF protocol, VECTOR flagged three documentation inconsistencies. Each one needs your sign-off to seal — some you can approve as-is, one needs Hiroshi's medical judgment. The CER cannot ship downstream to Stage 04 (Submission) until all three are resolved.
Critical 1Warning 1Info 1Resolved 0 of 3Blocks downstream 04 SUBM
INC-02-001Adverse event re-classification · M18 follow-up window
Discrepancy detected
Patient DBSubject 0418-22 · AE-2024-0117 · classified as Serious AE (related)
Safety summary v6Subject 0418-22 · AE-2024-0117 · listed as Non-serious (unrelated)
Source docDSMB packet 03 narrative section §4.2 · Investigator Brochure v8 §6.1
⬢ VECTOR · recommendationThis is a medical judgment call, not a documentation cleanup. The Patient DB entry was made by the local site investigator at the time of the event. The safety summary was updated 11 days later after CMO consultation but the rationale isn't captured in the audit trail. Escalate to Dr. Hiroshi Sato (CMO) for definitive classification. If Hiroshi rules "serious related," DSMB packet 04 needs re-issuing — adds 2 weeks.
Action required from Priya
INC-02-002Primary endpoint definition mismatch · CER §3.1 vs SAP §2.4
Discrepancy detected
CER §3.1"AF detection sensitivity at 24 months, ITT population"
SAP §2.4 (locked)"AF detection sensitivity at 24 months, per-protocol population"
Locked sinceSAP v3 lock · 02 Mar 2026 · receipt 8c12...0e44
⬢ VECTOR · recommendationSAP is the source of truth (locked pre-data-lock). CER §3.1 should be updated to match: "per-protocol population". VECTOR can auto-apply the edit to CER v17 draft on your approval. Receipt chain preserves both versions for audit. No statistical re-analysis required — the actual analysis used per-protocol throughout.
Action required from Priya
INC-02-003PMCF sample-size calculation uses outdated reference population
Discrepancy detected
PMCF protocol v2Sample size n=420 · uses APAC AF prevalence baseline from WHO 2019 dataset
Current standardWHO Global Burden of Disease 2024 update · APAC AF prevalence revised down 8%
ImplicationRecomputed sample size = n=455 · adds ~35 patients to PMCF
⬢ VECTOR · recommendationUpdate PMCF v2 → v3 with WHO 2024 reference. Adds ~35 patients to post-market follow-up cohort. Cost impact: ~$280k additional PMCF spend. Lin Wei should review the statistical methodology before approval.
Action required from Priya
EVIDENCE CORPUS · STAGE 02
Live state of all artifacts
SAP v3
DSMB packet 01
DSMB packet 02
DSMB packet 03
DSMB packet 04
CER v17 draft
PMCF protocol v2
Safety summary v6
Investigator Brochure v8
Patient-level data export
10 artifacts · 7 locked · 3 draftOpen evidence explorer →
STAGE OWNERS
Who's accountable
P
Priya Nair
Clinical Affairs Lead · Singapore
L
Dr. Lin Wei
Regulatory Lead · Hong Kong
H
Dr. Hiroshi Sato
CMO · Medical Affairs
WORKFLOWVECTOR's substages
▶
W1
W2
W3
W4
W5
W6
W7
Trial data ingest
SAP lock
DSMB packet build
CER drafting
Cross-validation scan
Triage queue
Corpus seal → VECTOR handoff
When all 3 are resolved →