Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Website: feedback from FDA from January Meeting #135

Closed
bms63 opened this issue Jan 14, 2024 · 0 comments · Fixed by #136
Closed

Update Website: feedback from FDA from January Meeting #135

bms63 opened this issue Jan 14, 2024 · 0 comments · Fixed by #136
Assignees

Comments

@bms63
Copy link
Collaborator

bms63 commented Jan 14, 2024

Compile by @robertdevine

The FDA Review indicated that using the R generated ADaM data sets
in Pilot3, the reviewers were able to replicate the results of the
four analyses used in Pilot1.
The FDA Reviewer (Hye Soo) did identify (so far) several issues
and presented observations and questions for response from the
Pilot3 Team.
Items [1] through [3] are Actionable. Items [4] and [5] are
Non-Actionable.
[1]FDA Reviewer observed no statistical analysis plan (SAP) was
included with the Pilot3 submission.
Action Item: Confirm with FDA Reviewers that the SAP should be
included if a re-submission is requested. Given
Question 1(b) inclusion of the SAP may provide
clarity regarding correctness.

[2]The Primary output in Pilot 3 was different from the Pilot 1
result due to the QC findings. QC findings in the ADRG include
all of the discrepancies between the original ADaM datasets.

Action Item: Respond to FDA Review Question #1: How did you know
this was an issue from the CDISC ADADAS (Pilot1)
and how did you correct them?
Observation: FDA Reviewer shared an example using USUBJID 01-705-1292
Question 1(a): Why was LOCF required when there was no
missing data in the QS?

Observation: FDA Reviewer (Hye Soo) noted in the primary results
(i)slight difference in rounding and (ii)quite different
p-values. [Appears to be due to QC Findings discrepancies.]
Action Item: Respond to FDA Review Question 1(b): Which primary analysis
output is correct? Hye Soo noted lack of clarity regarding
determination of correctness due to unavailable SAP.

[3]FDA Review also presented an observation noting that in the
Pilot3 Summary Tables and Figures Report you noted that
different open-source packages were used when generating
each of the 4 analysis outputs to test wider use case
scenarios. However, the R packages and scripts seem identical
to Pilot1.

Action Item: Respond to FDA Review Question #2:
What exactly has changed?
*This was discussed at the R Consortium WG and
Ning responded to the question by stating the
language used in the Pilot3 submission was
carried over from Pilot1 to Pilot3. The Pilot3
response should confirm Ning's response to Hye Soo.

[4]Moderator Observation: Quality Control (Non-Actionable)
Should we have a standard or checklist for tracking differences between
Pilot1 and Pilot3 and Pilot(n).
Action Item: Recommend or suggest a checklist for comparison to a
single-point-of-truth as a Quality Factor.

[5]WG Team Observation (Non-Actionable)
The idea of using AI tools to check consistency was mentioned by Ning
Action Item: Review applicable AI Tools for application integration to
address inconsistencies, for example, Copy & Paste
differences which were noted by FDA Reviewer Paul

bms63 added a commit that referenced this issue Jan 14, 2024
bms63 added a commit that referenced this issue Jan 14, 2024
@bms63 bms63 linked a pull request Jan 14, 2024 that will close this issue
@bms63 bms63 changed the title Update Website: feedback from FDA from December/January Meeting Update Website: feedback from FDA from January Meeting Jan 14, 2024
@robertdevine robertdevine self-assigned this Jan 15, 2024
bms63 added a commit that referenced this issue Jan 16, 2024
…from-fda-from-decemberjanuary-meeting

Closes #135 Feedback from January 2024 Meeting
bms63 added a commit that referenced this issue Jan 22, 2024
…from-fda-from-october-meeting

Conflation of Pilot3 Issues #95, #135, #137, #138, and #139 per the discussion in the Issue #135 PR thread
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants