← All goals
Objective: RBQM in the browser — a study's raw files through the standard gsm workflows to the site-level charts, with R computing every number
Goal issue #375 · slug rbqm
3/12 member issues closed
Other open members 9
no readiness label yet.
- #391 the RBQM tab runs the query, data entry and data change metrics (kri0008 to kri0011) (Backlog · safety · status: backlog)
- #392 the RBQM tab shows country-level metrics (Backlog · safety · status: backlog)
- #393 the RBQM tab draws the time series chart across snapshots (Backlog · safety · status: backlog)
- #394 the RBQM tab makes gsm's KRI report in the browser (Backlog · safety · status: backlog)
- #395 the RBQM tab maps raw files whose column names are not gsm's (Backlog · safety · status: backlog)
- #396 decide whether the demo app, with its RBQM tab, moves to open.gismo (Backlog · safety · status: backlog)
- #397 the RBQM tab runs the three newer site metrics (kri0013 to kri0015) (Backlog · safety · status: backlog)
- #414 the Biomarkers tab and the RBQM tab share one R (Backlog · safety · status: backlog)
- #415 a page on the docs site for the RBQM tab, linked from its footnote (Backlog · safety · status: backlog)
✅ Done 3
closed members.
- #373 the standard gsm workflows run in browser R — adverse event rate by site, from raw files to Results rows, matching desktop R (Released · safety · status: released)
- #374 the RBQM tab — a study's raw files run through the gsm workflows in the browser and drawn as the three site-level charts (Released · safety · status: released)
- #398 the RBQM tab runs on the study the other charts use — R makes gsm's raw tables from the standard domains (Released · safety · status: released)
Direction
Intent
@jwildfire, 2026-10-07: "Build a barebones RBQM tab in the safety.viz demo app: a user loads their study's raw files, the standard gsm workflows run in R in the browser, and the standard site-level charts draw from the result. Top priority for the R/Pharma talk on 21 October 2026."
Nothing is precomputed. The reader's files stay in the browser; pressing Start R runs the mapping, metric and reporting workflows there through workr, and gsm.viz draws the Results, Bounds, Groups and Metrics tables that come out. The tab is the report.
Definition of done
End state: on the deployed dev demo (https://jwildfire.github.io/safety.viz/dev/demo/), choosing the RBQM demo study and pressing Start R runs the standard gsm workflows in the browser and draws the group overview table, the scatter plot and the bar chart for every site-level metric the loaded files support; loading a reader's own raw files with gsm's standard column names does the same; a metric whose files are not loaded says so; no number on the tab is computed by the app.
Proof: a browser test in safety.viz's CI holds every in-scope metric's Results rows to desktop R's on the same input; the app's network test shows the study's rows are sent nowhere; both requirements below are closed with their proof comments, and the second one's comment quotes the measured download size and run time.
Ships in: safety.viz v1.10.0, milestone 2026-10-talk.
Requirements
In session order:
- The gate: the standard gsm workflows run in browser R, adverse event rate by site from raw files to Results rows, matching desktop R (#373).
- The RBQM tab: the demo study, a reader's own files, and the three site-level charts for the metrics in scope (#374). Starts only when the gate has closed with its proof.
Boundaries
- The gate decides. If the standard workflows cannot be made to run in browser R, the first requirement closes with exactly what blocked it and the second is not started. The tab is not built on anything else: no precomputed results, no JavaScript re-implementation of a metric.
- The app computes no statistic. R computes every number the tab shows.
- Files never leave the browser. The footer says so today and names where R is downloaded from; when starting R downloads from more places, the footer names them and the network test holds it.
- Read-only outside the jwildfire account: no issue, comment or pull request on the gsm packages' repositories. A defect found in one is written up for @jwildfire and worked around locally.
- The tab ships with the Experimental badge. The pilot study's files do not change.
- Out of scope, each named as a follow-up on the second requirement: the query, data entry and data change metrics; country-level metrics; the time series chart; the R Markdown report; mapping non-standard column names; moving the app to open.gismo.
- The cut line if the calendar slips: the demo study running end to end beats loading a reader's own files; one metric drawn in all three charts beats eight metrics in one.
This issue was drafted by Claude Code using Opus 5.5 from @jwildfire's brief of 2026-10-07. The tree is signed off only by his comment here.
Members are generated from the objective issue's sub-issue links at build time; priority is the selecting session's judgment, not list order (#53 v2). The --auto policy binding — active/paused, grant profile, repo-level backlog feeds — lives in obot.agent/goals/registry.json. Readiness labels: auto = ready for autonomous implementation, draft = needs @jwildfire steering.