docs: SQL-on-FHIR analytics evaluation — query notebook that scales to BI (#650) - #775
Open
dougc95 wants to merge 3 commits into
Open
docs: SQL-on-FHIR analytics evaluation — query notebook that scales to BI (#650)#775dougc95 wants to merge 3 commits into
dougc95 wants to merge 3 commits into
Conversation
…o BI (#650) Decision document for #650. Recommends building a native query notebook for SQL-on-FHIR that scales into governed BI (charts -> dashboards -> semantic layer), staged on the #649 UI, over bundling any third-party notebook or BI tool. Includes: buy-vs-build framing, per-candidate license / no-CDN / footprint comparison across the full #650 candidate set, the BI-as-code blueprint (Evidence / Graphene / Cube adopted as design, not runtime), locally measured spikes (JupyterLite vendored-offline vs marimo WASM, with browser-verified off-origin request counts), security/tenant analysis, staged architecture, and proposed follow-up issues. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PTFfaGwHDggEbrFtfejJtE
…ted results (#650) $sql-run silently truncates at 100k rows (engine.rs:277), so browser-side group-by/sum/avg over a large ViewDefinition would chart a wrong number. Aggregation now specified as server-side (SQLView SQL); client-side DuckDB-WASM pivot is scoped to sub-cap results. Fixes a verified gap-review finding.
…vs proposal (#650) Adds a "Proof of concept" subsection to §5 mapping each option to its built demonstrator (PRs #768-#771) with what each verified, and relabels the now-shown feasibility as [demonstrated] while keeping the product decision, correct Stage 2, Stage 3, and the open questions as [proposal].
Open
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The #650 deliverable: a decision document under
docs/evaluating where users should analyze SQL-on-FHIR tabular output.Recommendation
Build a native query notebook for SQL-on-FHIR that scales into governed BI — query cells → charts → dashboards + a semantic layer — staged on the #649 UI, rather than bundling any third-party notebook or BI tool. Python / ML stays a later tier (companion service or external platform), fed result data, not credentials.
What's in it
Runnable POCs
Four demonstrators accompany this document as draft PRs: #768 native notebook · #769 DuckDB-WASM over Arrow · #770 pysof baseline · #771 JupyterLite.
Relates to #650. Follow-up implementation issues are proposed in §14; not auto-closing the research issue.