← Back to home
Comparison · Analytics

healthyR.data vs reda

A side-by-side editorial comparison of healthyR.data and reda — release velocity, themes, recent moves, and the top alternatives to consider.

Shared themes:r-package

healthyR.data vs reda: at a glance

FeaturehealthyR.datareda
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesr-package, healthcare-data, cms, api-clientsurvival-analysis, recurrent-events, maintenance-mode, cran
Last editorial update51m ago1h ago
WebsiteVisit →Visit →

What is healthyR.data?

From a bundled hospital dataset to a live CMS API client.

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

Read the full healthyR.data trajectory →

What is reda?

A mature recurrent-event toolkit in careful maintenance, shedding weight rather than adding surface.

reda provides nonparametric mean cumulative function estimation, gamma-frailty rate regression, and event-data simulation for recurrent-event survival analysis. The core API settled at 0.5.0 when Recur() replaced Survr() and the MCF internals moved to C++. Everything since has been consolidation: small argument additions, method completions, and CRAN hygiene.

Read the full reda trajectory →

healthyR.data vs reda: editorial side-by-side

H
healthyR.data
ANALYTICS
0.0

From a bundled hospital dataset to a live CMS API client.

◆ Current state

healthyR.data supplies the data layer for the healthyverse packages. It began by shipping hospital data inside the package and now fetches from CMS and provider endpoints at call time through get_cms_meta_data(), fetch_cms_data(), and their provider counterparts. The most recent release is a single httr2 compatibility fix.

◆ Where it's heading

The 2023 release added roughly twenty current_*_data() accessors, one per CMS measure file - a wide but static surface. The 2024 releases replaced that approach with metadata lookup plus generic fetchers, then taught the fetchers to handle CSV, Excel, and ZIP payloads rather than API responses alone. The package's weight has moved from what it ships to what it can retrieve.

◆ Prediction

With the fetch layer generalised, the next visible work is more likely record-limit and error handling around httr2 than further per-measure accessors.

R
reda
ANALYTICS
0.0

A mature recurrent-event toolkit in careful maintenance, shedding weight rather than adding surface.

◆ Current state

reda provides nonparametric mean cumulative function estimation, gamma-frailty rate regression, and event-data simulation for recurrent-event survival analysis. The core API settled at 0.5.0 when Recur() replaced Survr() and the MCF internals moved to C++. Everything since has been consolidation: small argument additions, method completions, and CRAN hygiene.

◆ Where it's heading

The last three releases contain no new modelling capability at all — a dependency reshuffle, a test-example correction, and a print-order fix. The package is being kept installable and correct rather than extended. Its tightest coupling is to splines2, a sibling package from the same maintainer, which supplies the derivative machinery reda depends on.

◆ Prediction

Expect continued small-cadence CRAN-compliance releases tracking ggplot2 and splines2 changes. The entries show no in-progress feature work, so a substantive release would have to arrive without warning from this feed.

Alternatives to healthyR.data and reda

Other Analytics 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 healthyR.data or reda.

See all healthyR.data alternatives → · See all reda alternatives →

Recent activity from healthyR.data and reda

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 11mo agoredaggplot2 and grDevices demoted to Suggests
  2. 1y agoredaTest example and documentation typo fixes
  3. 1y agohealthyR.datahttr2 compatibility fix
  4. 2y agohealthyR.dataFetchers handle CSV, Excel, and ZIP, with a record limit
  5. 2y agohealthyR.dataMetadata lookup and generic CMS fetchers replace bundled data
  6. 3y agohealthyR.dataTwenty CMS measure accessors added
  7. 3y agohealthyR.datacli, crayon, and rstudioapi dependencies dropped
  8. 4y agoredasimEvent() gains a user-supplied rate bound
  9. 5y agohealthyR.dataxz compression added to meet CRAN size policy
  10. 5y agoredasummary() method completes the Recur object
  11. 5y agoredaDerivatives sourced from splines2's deriv method
  12. 6y agoredaMCF estimates can now skip variance computation

Frequently asked questions

What is the difference between healthyR.data and reda?

Both compete on the same themes — r-package — within Analytics. healthyR.data and reda are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is healthyR.data better than reda?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. healthyR.data and reda are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to healthyR.data?

Top healthyR.data alternatives in Analytics are ranked by recent ship velocity. Browse the "healthyR.data alternatives" section above for the current picks, or visit /alternatives/healthyr-data for the full list with editorial commentary on each.

What are the best alternatives to reda?

Top reda alternatives in Analytics are ranked by recent ship velocity. Browse the "reda alternatives" section above for the current picks, or visit /alternatives/reda for the full list with editorial commentary on each.