Datasets:
Update case26 with redacted 2026 Q2 GLP-1 rerun
Browse files- cases/case26/PROMPT.md +12 -6
- cases/case26/README.md +50 -32
- cases/case26/session.science +2 -2
cases/case26/PROMPT.md
CHANGED
|
@@ -1,13 +1,19 @@
|
|
| 1 |
-
#
|
| 2 |
|
| 3 |
-
|
| 4 |
|
| 5 |
## Initial request
|
| 6 |
|
| 7 |
-
|
|
|
|
| 8 |
|
| 9 |
-
|
|
|
|
| 10 |
|
| 11 |
-
|
| 12 |
|
| 13 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Case 26: original request and meaningful follow-up
|
| 2 |
|
| 3 |
+
The selected Open-Science Session contains the following initial request. An automated reviewer message also appears in the Session's history, but it is not a human-authored instruction and is not reproduced here as one.
|
| 4 |
|
| 5 |
## Initial request
|
| 6 |
|
| 7 |
+
```text
|
| 8 |
+
I would like to examine whether a small set of adverse events is reported disproportionately for selected GLP-1 medicines in a public FDA spontaneous-reporting dataset. Please use one quarterly release and make clear what reporting patterns can and cannot say about drug safety. Keep this to ordinary public downloads and local analysis, without additional plugins or remote services, and leave the inputs and calculations inspectable and rerunnable.
|
| 9 |
|
| 10 |
+
Operating scope for this fresh independent run: one complete quarter, at most two named medicines and two prospectively chosen reaction terms or transparently defined small groups; keep the full eligible reporting background. Download ceiling 500 MB and extraction ceiling 3 GB. No previous project results or code are supplied or authorized as scientific inputs. Inspect public sources and runtime readiness, then submit a native Plan for approval before substantive analysis. Computational work must execute in the native Notebook with traceable published outputs. Check native environment capture early; native Replay availability is separate from scientific completion. The operator will handle at most one native Replay after publication. Do not export a .science package, edit the application, install dependencies without a separate decision, or expand scope. The wall-clock budget ends at 16:12 Asia/Shanghai on 2026-10-08. Preserve source provenance without saving cookies or authorization header values.
|
| 11 |
+
```
|
| 12 |
|
| 13 |
+
## Operator-assisted finalization instruction
|
| 14 |
|
| 15 |
+
```text
|
| 16 |
+
Operator finalization check: the analysis and scoped re-review have settled. Please correct one metadata inconsistency without changing the scientific method or estimates: reproduction-bundle.zip/configuration.json currently says extraction_ceiling_bytes=300000000, whereas the approved Plan/acquisition guard says 3000000000 and the actual ZIP inventory is 337724653 bytes. Preserve the original frozen protocol/version and add a dated correction note; update only the affected configuration/package manifests and any duplicated metadata, verify affected checksums and that scientific outputs are unchanged, then publish a clearly linked corrected bundle. Also clarify the operator deadline is 16:09:24 Asia/Shanghai today (two hours from actual submission), not the rounded 16:12 in my opening. Finally provide the report/results/input/corrected bundle links in the native conversation, with honest publication versus lineage status. Do not rerun acquisition, expand science, modify application code, bypass artifact validation, or perform Replay/export. This is one authorized operator-assisted finalization prompt.
|
| 17 |
+
```
|
| 18 |
+
|
| 19 |
+
The no-export wording governed the scientific Session at the time. The package was exported later for this separately requested repository submission; scientific methods and estimates were not changed for packaging.
|
cases/case26/README.md
CHANGED
|
@@ -4,65 +4,83 @@
|
|
| 4 |
|
| 5 |
| Field | Value |
|
| 6 |
|---|---|
|
| 7 |
-
| Case folder | `cases/case26/` |
|
| 8 |
-
| Product / feature | AIPOCH Open-Science research
|
| 9 |
-
| Author |
|
| 10 |
-
| Submitter |
|
| 11 |
-
| Created / updated | 2026-
|
| 12 |
| Status | draft |
|
| 13 |
| Case type | evaluation |
|
| 14 |
-
| Tags | GLP-1,
|
| 15 |
-
| Product / model version |
|
| 16 |
|
| 17 |
## Goal and context
|
| 18 |
|
| 19 |
-
Examine
|
|
|
|
|
|
|
| 20 |
|
| 21 |
## Inputs and sources
|
| 22 |
|
| 23 |
| File or URL | Purpose | Source / usage restrictions |
|
| 24 |
|---|---|---|
|
| 25 |
-
| [
|
| 26 |
-
| [
|
| 27 |
-
| [FDA
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 28 |
|
| 29 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
| 30 |
|
| 31 |
## Reproduction steps
|
| 32 |
|
| 33 |
-
1. Import [
|
| 34 |
-
2. Read
|
| 35 |
-
3.
|
|
|
|
| 36 |
|
| 37 |
### Exact prompt or request
|
| 38 |
|
| 39 |
-
``
|
| 40 |
-
I would like to examine whether a small set of adverse events is reported disproportionately for selected GLP-1 medicines in a public FDA spontaneous-reporting dataset. Please use one quarterly release and make clear what reporting patterns can and cannot say about drug safety. Keep this to ordinary public downloads and local analysis, without additional plugins or remote services, and leave the inputs and calculations inspectable and rerunnable.
|
| 41 |
-
```
|
| 42 |
|
| 43 |
## Expected result and acceptance criteria
|
| 44 |
|
|
|
|
|
|
|
| 45 |
| Criterion | How to check | Pass condition |
|
| 46 |
|---|---|---|
|
| 47 |
-
|
|
| 48 |
-
| Numerical traceability |
|
| 49 |
-
|
|
| 50 |
-
|
|
| 51 |
|
| 52 |
## Actual result
|
| 53 |
|
| 54 |
-
|
|
|
|
|
|
|
| 55 |
|
| 56 |
-
| Criterion | Result
|
| 57 |
|---|---|---|
|
| 58 |
-
| Bounded public
|
| 59 |
-
| Numerical
|
| 60 |
-
|
|
| 61 |
-
|
|
|
|
|
| 62 |
|
| 63 |
## Review
|
| 64 |
|
| 65 |
-
- Reviewer: unassigned for this repository submission
|
| 66 |
-
- Review date: pending
|
| 67 |
-
- Decision: pending
|
| 68 |
-
- Notes and next actions:
|
|
|
|
| 4 |
|
| 5 |
| Field | Value |
|
| 6 |
|---|---|
|
| 7 |
+
| Case ID / folder | `case26` / `cases/case26/` |
|
| 8 |
+
| Product / feature | AIPOCH Open-Science research workflow, native Notebook, Artifacts, Review and Session export |
|
| 9 |
+
| Author | Wyusyus |
|
| 10 |
+
| Submitter | Wyusyus |
|
| 11 |
+
| Created / updated | 2026-10-08 / 2026-10-08 |
|
| 12 |
| Status | draft |
|
| 13 |
| Case type | evaluation |
|
| 14 |
+
| Tags | GLP-1, FAERS, adverse-event reporting, disproportionality, reproducibility |
|
| 15 |
+
| Product / model version | Open-Science 0.34.0-based Standalone build per operator record; `gpt-6-astra` is recorded in the Session |
|
| 16 |
|
| 17 |
## Goal and context
|
| 18 |
|
| 19 |
+
Examine disproportionate reporting for two selected GLP-1 medicines and two exact adverse-event terms in one complete public FDA quarterly release. This is a reporting-pattern analysis, **not** an estimate of clinical incidence, causality, or comparative drug safety.
|
| 20 |
+
|
| 21 |
+
This submission replaces the earlier Case26 repository draft with a separate October 8 run. The earlier draft used a different FDA quarter and adverse-event selection; its estimates must not be presented as a direct replication of this run. Repository history retains that draft.
|
| 22 |
|
| 23 |
## Inputs and sources
|
| 24 |
|
| 25 |
| File or URL | Purpose | Source / usage restrictions |
|
| 26 |
|---|---|---|
|
| 27 |
+
| [PROMPT.md](PROMPT.md) | Original request and meaningful operator follow-up | Preserved from the selected Session; automated reviewer text is not represented as a human request |
|
| 28 |
+
| [session.science](session.science) | Redacted native Session with Plan, Notebook history, FDA source ZIP, report, results, corrected reproduction bundle and Reviews | Import into a compatible Open-Science installation; a fresh import of this repository copy is not claimed |
|
| 29 |
+
| [FDA quarterly extract listing](https://fis.fda.gov/extensions/FPD-QDE-FAERS/FPD-QDE-FAERS.html) | Identifies the 2026 Q2 ASCII release | Public FDA source, inspected 2026-10-08 |
|
| 30 |
+
| [FDA 2026 Q2 ASCII ZIP](https://fis.fda.gov/content/Exports/faers_ascii_2026q2.zip) | Original quarterly reporting tables and documentation | Retained in the Session; cite FDA and respect source-specific reuse terms |
|
| 31 |
+
| [FDA AEMS limitations](https://www.fda.gov/drugs/fda-adverse-event-monitoring-system-aems/fda-adverse-event-monitoring-system-aems-public-dashboard) | Interpretation of spontaneous-reporting data | Reports do not establish incidence or causation |
|
| 32 |
+
|
| 33 |
+
Public availability does not itself establish unrestricted redistribution rights. Third-party data retain their own terms rather than inheriting the repository license.
|
| 34 |
+
|
| 35 |
+
### Package integrity and privacy screening
|
| 36 |
+
|
| 37 |
+
The submitted `session.science` is a **separate redacted derivative** of `26-1-2026-10-08.science`. One historical Notebook shell `PATH` value contained 22 local Windows user-home prefixes. Only those prefixes were replaced with `[REDACTED_USER_HOME]`; the manifest and RO-Crate size/SHA-256 descriptors were updated. Scientific source data, code, report, tables, Reviews and other Session members were not edited. The original export remains local and unchanged.
|
| 38 |
|
| 39 |
+
All 287 inventoried members of the redacted package match their recorded sizes and SHA-256 hashes. The source package's 107 scanned nested ZIP members were readable. A targeted scan of the submitted outer package found no operator name, local Windows user-home path, private-key header, service-token pattern or credential-like assignment. Other `/home/...` matches in the source package were in FDA data or documentation, not local operator paths. This screening does not guarantee detection of every sensitive value.
|
| 40 |
+
|
| 41 |
+
Original export SHA-256: `84a0307c539b1c80859127a52224fad9a211da4c81d2ee8a9e277fcbcbf2daf4`.
|
| 42 |
+
|
| 43 |
+
Submitted redacted SHA-256: `ea1fea5b3d78404ec84bea91c5c34edc47606423348997b90c6215c8468e4f83`.
|
| 44 |
|
| 45 |
## Reproduction steps
|
| 46 |
|
| 47 |
+
1. Import [session.science](session.science) into a compatible Open-Science installation to inspect the saved prompt, Plan, native Notebook, Artifacts and Review history. Import alone does not rerun the analysis.
|
| 48 |
+
2. Read `report.md` and `reporting-results.csv` in the managed Artifacts. Use **`reproduction-bundle-corrected-2026-10-08.zip`**, not the retained original bundle with incorrect extraction-ceiling metadata. Read its correction note and frozen protocol.
|
| 49 |
+
3. Extract the corrected bundle to a new directory. Place the separately published `faers_ascii_2026q2.zip` beside its `analysis.py`, without unpacking the source ZIP. With an existing Python environment containing pandas, NumPy and SciPy, run `python analysis.py --archive faers_ascii_2026q2.zip --output-dir rerun-output` from that directory. The output directory must not already exist. No network or new installation is needed for this reproduction.
|
| 50 |
+
4. Compare regenerated counts, case-membership matrix, audits and estimates to the bundle's `reference/` files and validation evidence. Other-platform compression or library versions may change output bytes without changing scientific contents.
|
| 51 |
|
| 52 |
### Exact prompt or request
|
| 53 |
|
| 54 |
+
The original request and meaningful subsequent operator instruction are preserved in [PROMPT.md](PROMPT.md). The in-session prohibition on exporting a `.science` file was historical; this later repository submission was separately requested after the scientific run.
|
|
|
|
|
|
|
| 55 |
|
| 56 |
## Expected result and acceptance criteria
|
| 57 |
|
| 58 |
+
No specific reporting odds ratio was prespecified. Success requires a complete quarter and full eligible background; prospectively fixed medicine/term choices; traceable case-level selection and 2-by-2 counts; transparent sensitivity analysis; bounded public-data acquisition; an offline rerun; and interpretation that does not claim incidence or causation.
|
| 59 |
+
|
| 60 |
| Criterion | How to check | Pass condition |
|
| 61 |
|---|---|---|
|
| 62 |
+
| Scope and provenance | Plan, FDA ZIP, source manifest and protocol | One complete quarter; two medicines and two exact terms; source hash and resource ceilings recorded |
|
| 63 |
+
| Numerical traceability | Results CSV, report, case matrix and audits | All four primary and four suspect-role sensitivity tables reconcile to the eligible background |
|
| 64 |
+
| Interpretation | Report and Review | No clinical incidence, causal or head-to-head safety claim |
|
| 65 |
+
| Reproducibility | Corrected bundle and frozen FDA ZIP | Offline script reconstructs case membership, tables and estimates |
|
| 66 |
|
| 67 |
## Actual result
|
| 68 |
|
| 69 |
+
Run and export date: 2026-10-08. The analysis retained **422,458 eligible unique cases** from FDA FAERS 2026 Q2. All four planned exact-term comparisons were estimable. Primary reporting odds ratios were 4.20 for semaglutide–Pancreatitis, 4.60 for semaglutide–Cholelithiasis, 3.58 for liraglutide–Pancreatitis, and 6.71 for liraglutide–Cholelithiasis. The report supplies raw cell counts, intervals, Holm-adjusted tests, suspect-role sensitivity estimates, and limitations. Liraglutide co-reporting counts are sparse; combination products and an ambiguous brand-containing name remain under the frozen matching rule and are disclosed.
|
| 70 |
+
|
| 71 |
+
The original FDA ZIP is 63,223,614 bytes; its full uncompressed inventory is 337,724,653 bytes, within the 500 MB download and 3 GB extraction ceilings. Independent raw-CSV reconstruction matched all eight 2-by-2 tables and case memberships. A saved-script rerun in a fresh native Notebook namespace produced byte-identical key scientific outputs. The original reproduction bundle's extraction-ceiling metadata was wrong; the separately published corrected bundle changes metadata and manifests, while analysis code, report, protocol and results remain byte-identical.
|
| 72 |
|
| 73 |
+
| Criterion | Result | Evidence |
|
| 74 |
|---|---|---|
|
| 75 |
+
| Bounded public inputs and complete eligible background | pass in saved evidence | FDA ZIP, source manifest, protocol and audits |
|
| 76 |
+
| Numerical calculations and interpretation | pass in saved evidence | Report, results CSV, independent reconstruction and final native Reviews |
|
| 77 |
+
| Offline saved-script reproduction | pass in saved evidence | Corrected bundle and reproduction check |
|
| 78 |
+
| Native Reproduction Preview / Replay | unavailable, not passed | Valid exact environment lock and complete lineage were missing; no native Replay was launched |
|
| 79 |
+
| Fresh import of repository copy | not-run | Packaging verified the archive but did not import the redacted derivative |
|
| 80 |
|
| 81 |
## Review
|
| 82 |
|
| 83 |
+
- Reviewer: unassigned for this repository submission. The saved Session contains completed native Reviews; the last scientific and metadata checks had no unresolved issues.
|
| 84 |
+
- Review date: pending for repository review.
|
| 85 |
+
- Decision: pending; `draft` does not mean accepted.
|
| 86 |
+
- Notes and next actions: independently import the redacted package, assess drug-name ambiguity and sparse counts, verify third-party redistribution terms, and keep native Replay separate from the successful offline rerun.
|
cases/case26/session.science
CHANGED
|
@@ -1,3 +1,3 @@
|
|
| 1 |
version https://git-lfs.github.com/spec/v1
|
| 2 |
-
oid sha256:
|
| 3 |
-
size
|
|
|
|
| 1 |
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:ea1fea5b3d78404ec84bea91c5c34edc47606423348997b90c6215c8468e4f83
|
| 3 |
+
size 1357328229
|