FoRecoML
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
A side-by-side editorial comparison of dqcheckr and medicalcoder — release velocity, themes, recent moves, and the top alternatives to consider.
dqcheckr adds drift analysis, then removes the YAML a user had to hand-write.
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
A comorbidity-coding package relicenses to BSD and grows past the American coding systems
medicalcoder maps ICD diagnosis codes to comorbidity conditions using the Charlson, Elixhauser, AHRQ and PCCC method families. Three releases since June 2026 moved it from a US-centric tool to one carrying Australian and Swedish modifications, added four new Charlson variants, and introduced a choice between precomputed code-condition links and regex mapping applied directly to input codes. The license moved from GPL-2 to BSD 3-Clause along the way.
dqcheckr runs configurable data-quality checks over files and DuckDB tables, driven by YAML dataset configs and recording results as snapshots. The 0.2.0 release added the ability to compare two historical snapshots and report per-column statistical drift, schema changes and trend charts, extending the tool from point-in-time checking into change over time. The most recent tag, 0.3.0, attacks the other friction point by generating the config itself from a sniff pass over the data.
Both moves point the same way: reduce what the operator has to write and know. Config generation removes the hand-authored YAML that gated first use, list_runs() and validate_config() make an existing setup inspectable, and the snapshot comparison turns accumulated run history into a second product surface. Check coverage keeps widening underneath — outlier detection, composite keys, row-count and file-size ceilings — and the reporting layer moved from rmarkdown to Quarto, with existing 0.1.x databases auto-migrated on first run.
Expect the generated configs and the drift reports to converge, so a sniffed config can seed thresholds from the snapshot history rather than from defaults, plus continued growth in the numbered QC check catalogue.
medicalcoder maps ICD diagnosis codes to comorbidity conditions using the Charlson, Elixhauser, AHRQ and PCCC method families. Three releases since June 2026 moved it from a US-centric tool to one carrying Australian and Swedish modifications, added four new Charlson variants, and introduced a choice between precomputed code-condition links and regex mapping applied directly to input codes. The license moved from GPL-2 to BSD 3-Clause along the way.
Two things are happening at once. The coding surface is broadening — ICD-10-AM, ICD-10-SE, Swedish register-based and MIMIC-IV-consistent Charlson methods — which points at users outside the US claims-data world. Separately, the package is hardening: validation on encounter ordering, deterministic result ordering, NA rather than NaN for zero counts, and corrected AHRQ and Quan mappings for fiscal years 2023 to 2026. The mapping argument is the first real fork in how the computation runs rather than what it covers.
Regex mapping is currently unavailable for charlson_beyrer2021 and the release notes flag it as a gap, so closing that is the most clearly signposted next step.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either dqcheckr or medicalcoder.
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
See all dqcheckr alternatives → · See all medicalcoder alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Infra & APIs. dqcheckr is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dqcheckr is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top dqcheckr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "dqcheckr alternatives" section above for the current picks, or visit /alternatives/dqcheckr for the full list with editorial commentary on each.
Top medicalcoder alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "medicalcoder alternatives" section above for the current picks, or visit /alternatives/medicalcoder for the full list with editorial commentary on each.