Evidence Record
evt_NCT02229084_v17_v18_8c46c3fd160d
NCT02229084 · Vaccination of High Risk Breast Cancer Patients
Severity is deterministic, reproducible, uncalibrated triage metadata, not validated review priority or proven wrongdoing. This page states what the registry evidence supports and what it does not support.
Triage severity
Triage: Low Category
Results Reconciliation
Versions
v17 to v18
Timing
Post Recruitment
Claims Supported
- TrialDiff compared ClinicalTrials.gov record version 17 to version 18 for NCT02229084.
- The JSON Patch for this comparison has hash 304cb43ec0019e315fae4575c9ab0ff7e19a6244e3146db655a1cb519e1add28.
- The active deterministic rule set hash was fc87f4f0a74bc789dbe4ba85893c2c96f55db62c22970be4e991288104291621.
- The deterministic triage label was low; before timing adjustment it was low.
- The triage label is uncalibrated metadata, not a validated review-priority finding.
- The patch satisfied these deterministic event-class predicates: outcome_edit_cooccurs_with_results_posting.
- The timing context for the from-version record was post_recruitment.
- The changed JSON Pointer paths were: /protocolSection/statusModule/statusVerifiedDate, /protocolSection/statusModule/lastUpdateSubmitDate, /protocolSection/statusModule/lastUpdatePostDateStruct/date, /protocolSection/outcomesModule/primaryOutcomes/1/description, /resultsSection/outcomeMeasuresModule/outcomeMeasures/1/description.
- An outcome path changed between versions 17 and 18 in a patch that also carried a hasResults or resultsSection co-occurrence signal.
Claims Not Supported
- That the amendment was scientifically unjustified.
- That the change constitutes misconduct or wrongdoing.
- That sponsor intent can be inferred from this registry change.
- That the change caused or altered the trial's results.
- That the change was or was not disclosed in a manuscript.
- That TrialDiff determines regulatory compliance or non-compliance.
- That co-occurrence with results posting proves the outcome edit was harmless, administrative, or substantively benign.
- That event-class membership is a validated global review-priority ranking.
Neutral Review Question
What source document explains this registry amendment, and does it change interpretation of the trial record?
Citation
TrialDiff Evidence Record evt_NCT02229084_v17_v18_8c46c3fd160d. ClinicalTrials.gov NCT02229084, versions 17-18. Evidence version 1.
Event Classes
outcome_edit_cooccurs_with_results_posting Changed Paths
/protocolSection/statusModule/statusVerifiedDate
/protocolSection/statusModule/lastUpdateSubmitDate
/protocolSection/statusModule/lastUpdatePostDateStruct/date
/protocolSection/outcomesModule/primaryOutcomes/1/description
/resultsSection/outcomeMeasuresModule/outcomeMeasures/1/description
View the field-level diff for before/after values on each changed path.
Deterministic Rules
No deterministic rules recorded.
Provenance
- Package generation
v0.1.3(active)- Supersedes
- evt_NCT02229084_v17_v18_81287f91f229
- Patch hash
304cb43ec0019e315fae4575c9ab0ff7e19a6244e3146db655a1cb519e1add28- Canonical hash
7fcd76d506bef64621f068623606f741539887de03d9003febac4aabc45b0375- Rule set hash
fc87f4f0a74bc789dbe4ba85893c2c96f55db62c22970be4e991288104291621- From snapshot
70909a794eab1a8f5e457b43ba03450ec7bbc39229c1fc454e7e3c3b2a4f1028- To snapshot
144354df08343d5e332771c3b46b2cbc6d437c814094dd387abf78c7be3640af- Patch source
- ctgov_internal_history
- Generated at
- 2026-08-03T06:46:43.000Z
- Source URL
- Registry payload
Canonical JSON Preview
Stored payload{
"changed_paths": [
"/protocolSection/statusModule/statusVerifiedDate",
"/protocolSection/statusModule/lastUpdateSubmitDate",
"/protocolSection/statusModule/lastUpdatePostDateStruct/date",
"/protocolSection/outcomesModule/primaryOutcomes/1/description",
"/resultsSection/outcomeMeasuresModule/outcomeMeasures/1/description"
],
"citation_text": "TrialDiff Evidence Record evt_NCT02229084_v17_v18_8c46c3fd160d. ClinicalTrials.gov NCT02229084, versions 17-18. Evidence version 1.",
"claims_not_supported": [
"That the amendment was scientifically unjustified.",
"That the change constitutes misconduct or wrongdoing.",
"That sponsor intent can be inferred from this registry change.",
"That the change caused or altered the trial's results.",
"That the change was or was not disclosed in a manuscript.",
"That TrialDiff determines regulatory compliance or non-compliance.",
"That co-occurrence with results posting proves the outcome edit was harmless, administrative, or substantively benign.",
"That event-class membership is a validated global review-priority ranking."
],
"claims_supported": [
"TrialDiff compared ClinicalTrials.gov record version 17 to version 18 for NCT02229084.",
"The JSON Patch for this comparison has hash 304cb43ec0019e315fae4575c9ab0ff7e19a6244e3146db655a1cb519e1add28.",
"The active deterministic rule set hash was fc87f4f0a74bc789dbe4ba85893c2c96f55db62c22970be4e991288104291621.",
"The deterministic triage label was low; before timing adjustment it was low.",
"The triage label is uncalibrated metadata, not a validated review-priority finding.",
"The patch satisfied these deterministic event-class predicates: outcome_edit_cooccurs_with_results_posting.",
"The timing context for the from-version record was post_recruitment.",
"The changed JSON Pointer paths were: /protocolSection/statusModule/statusVerifiedDate, /protocolSection/statusModule/lastUpdateSubmitDate, /protocolSection/statusModule/lastUpdatePostDateStruct/date, /protocolSection/outcomesModule/primaryOutcomes/1/description, /resultsSection/outcomeMeasuresModule/outcomeMeasures/1/description.",
"An outcome path changed between versions 17 and 18 in a patch that also carried a hasResults or resultsSection co-occurrence signal."
],
"classification": {
"calibration_status": "uncalibrated",
"categories": [
"results_reconciliation"
],
"category": "results_reconciliation",
"deterministic_rules": [],
"event_class_rule_set_hash": "74a6f55a686c29aa023171acd6b43f27ea95f2b0af2d49094ac70287ba4e502c",
"event_classes": [
"outcome_edit_cooccurs_with_results_posting"
],
"rule_set_hash": "fc87f4f0a74bc789dbe4ba85893c2c96f55db62c22970be4e991288104291621",
"severity": "low",
"severity_pre_timing": "low",
"timing_context": "post_recruitment",
"triage_label": "low",
"triage_rule_set_hash": "af5e5835e00a5fcfe2a17fd02b5fc244c2564104f93f78a1d77d7889f12a178b",
"value_signals": [
{
"category": "results_reconciliation",
"paths": [
"/protocolSection/outcomesModule/primaryOutcomes/1/description"
],
"severity": "low",
"signal": "results_reconciliation_outcome_suppression"
}
]
},
"event_id": "evt_NCT02229084_v17_v18_8c46c3fd160d",
"evidence_version": 1,
"patch": [
{
"op": "replace",
"path": "/protocolSection/statusModule/statusVerifiedDate",
"value": "2024-05"
},
{
"op": "replace",
"path": "/protocolSection/statusModule/lastUpdateSubmitDate",
"value": "2024-05-28"
},
{
"op": "replace",
"path": "/protocolSection/statusModule/lastUpdatePostDateStruct/date",
"value": "2024-06-10"
},
{
"op": "replace",
"path": "/protocolSection/outcomesModule/primaryOutcomes/1/description",
"value": "The patient-level primary outcome for this objective is pathological Complete Response (pCR), which is binary yes/no, and the study-level endpoint for this outcome is the rate of pCR, i.e. the percentage of patients that achieved pCR=yes.\nThe patient is assessed at the time of surgery for whether they achieved pCR=yes.\nThey have to do the surgery in order to obtain the tissue samples on which they do their pCR assessment.\nPathological Complete Response is defined as the absence of any residual invasive cancer on hematoxylin and eosin evaluation of the resected breast specimen and all sampled ipsilateral lymph nodes following completion of neoadjuvant systemic therapy (i.e., ypT0N0 or ypTisN0 in the AJCC staging system for staging solid tumors in the neoadjuvant setting that was described in a 2014 FDA Guidance for Industry)."
},
{
"op": "replace",
"path": "/resultsSection/outcomeMeasuresModule/outcomeMeasures/1/description",
"value": "The patient-level primary outcome for this objective is pathological Complete Response (pCR), which is binary yes/no, and the study-level endpoint for this outcome is the rate of pCR, i.e. the percentage of patients that achieved pCR=yes.\nThe patient is assessed at the time of surgery for whether they achieved pCR=yes.\nThey have to do the surgery in order to obtain the tissue samples on which they do their pCR assessment.\nPathological Complete Response is defined as the absence of any residual invasive cancer on hematoxylin and eosin evaluation of the resected breast specimen and all sampled ipsilateral lymph nodes following completion of neoadjuvant systemic therapy (i.e., ypT0N0 or ypTisN0 in the AJCC staging system for staging solid tumors in the neoadjuvant setting that was described in a 2014 FDA Guidance for Industry)."
}
],
"provenance": {
"from_snapshot_hash": "70909a794eab1a8f5e457b43ba03450ec7bbc39229c1fc454e7e3c3b2a4f1028",
"materiality_event_hash": "307e17aa5beb52e9c20799dacbc12aa2d4b77290414bb5d5521b27c432de1ce2",
"patch_hash": "304cb43ec0019e315fae4575c9ab0ff7e19a6244e3146db655a1cb519e1add28",
"patch_raw_hash": "630bbc07c0649e2d34b339d574f6f9c4fddf8f4f432a8fc03aec9e927c232ef4",
"patch_source": "ctgov_internal_history",
"patch_source_url": "https://clinicaltrials.gov/api/int/studies/NCT02229084/history/17?patchToVersion=18",
"to_snapshot_hash": "144354df08343d5e332771c3b46b2cbc6d437c814094dd387abf78c7be3640af"
},
"review_question": "What source document explains this registry amendment, and does it change interpretation of the trial record?",
"schema": "trialdiff.evidence_record",
"trial": {
"clinicaltrials_gov_url": "https://clinicaltrials.gov/study/NCT02229084",
"nct_id": "NCT02229084"
},
"versions": {
"from_version": 17,
"submitted_date": "2024-05-28",
"to_version": 18
}
}