simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
Comparison · Analytics
healthyR.data vs TLF-Library
A side-by-side editorial comparison of healthyR.data and TLF-Library — release velocity, themes, recent moves, and the top alternatives to consider.
healthyR.data vs TLF-Library: at a glance
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.
What is TLF-Library?
The Open Systems Pharmacology plotting layer spent 2025 absorbing a ggplot2 major break.
tlf is the plotting library behind Open Systems Pharmacology's tables, listings and figures — a ggplot2 wrapper producing the PK/PD reporting output the OSP suite generates. Recent work splits into two strands: a feature set adding Lower Limit Of Quantification annotation to time-profile and observed-vs-predicted plots alongside a reworked axis-limits API, and then hot fixes to survive ggplot2 v4.0.0's breaking changes. The axis change is the substantive one, separating cropping the view from filtering the data behind it.
healthyR.data vs TLF-Library: editorial side-by-side
healthyR.data
0.0ANALYTICS
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.
TLF-Library
0.0ANALYTICS
The Open Systems Pharmacology plotting layer spent 2025 absorbing a ggplot2 major break.
◆ Current state
tlf is the plotting library behind Open Systems Pharmacology's tables, listings and figures — a ggplot2 wrapper producing the PK/PD reporting output the OSP suite generates. Recent work splits into two strands: a feature set adding Lower Limit Of Quantification annotation to time-profile and observed-vs-predicted plots alongside a reworked axis-limits API, and then hot fixes to survive ggplot2 v4.0.0's breaking changes. The axis change is the substantive one, separating cropping the view from filtering the data behind it.
◆ Where it's heading
The library is maturing into a stable reporting dependency rather than growing new plot types — the newest releases are watermark placement, log-tick safety and upstream compatibility, not new figures. Its exposure is to ggplot2: v4.0.0 required same-day hot fixes, which is the risk profile of a wrapper this thin. Note that this feed's version numbers and publication stamps disagree, with 1.5.170 stamped four months before the lower-numbered 1.5.158, so the release order has to be read from version numbers and the changelog ranges rather than from the feed order.
◆ Prediction
With the ggplot2 v4 fallout patched and the LLOQ work promoted to a stable 1.6 line, the next releases most likely continue as small rendering fixes. Nothing in these entries points to a new plot class in progress.
Alternatives to healthyR.data and TLF-Library
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 TLF-Library.
lavaanExtra
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
ibis.iSDM
A raster-to-terra migration is the only readable change in a feed of merge notes.
anyflights
A nycflights13 generator whose recent work is all about the data being right.
vinereg
Conditional density and log-likelihood fill out a vine copula regression package.
stringx
A drop-in string API for base R, kept alive by upstream check failures.
See all healthyR.data alternatives → · See all TLF-Library alternatives →
Recent activity from healthyR.data and TLF-Library
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9mo agoTLF-LibraryWatermark positioning decoupled from plot scales
- 11mo agoTLF-LibraryHot fixes for ggplot2 v4.0.0 breaking changes
- 11mo agoTLF-LibraryLLOQ annotation and axis cropping split from data filtering
- 1y agoTLF-LibraryDev build introducing LLOQ plots and the xAxisLimits rename
- 1y agoTLF-LibraryError-bar cap fixes atop a restated feature list
- 1y agohealthyR.datahttr2 compatibility fix
- 1y agoTLF-LibraryDual-axis plots stop tripping cowplot
- 2y agohealthyR.dataFetchers handle CSV, Excel, and ZIP, with a record limit
- 2y agohealthyR.dataMetadata lookup and generic CMS fetchers replace bundled data ⚡
- 3y agohealthyR.dataTwenty CMS measure accessors added
- 3y agohealthyR.datacli, crayon, and rstudioapi dependencies dropped
- 5y agohealthyR.dataxz compression added to meet CRAN size policy
Frequently asked questions
What is the difference between healthyR.data and TLF-Library?
They serve adjacent needs but don't currently overlap on shipped themes. healthyR.data and TLF-Library 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 TLF-Library?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. healthyR.data and TLF-Library 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 TLF-Library?
Top TLF-Library alternatives in Analytics are ranked by recent ship velocity. Browse the "TLF-Library alternatives" section above for the current picks, or visit /alternatives/tlf-library for the full list with editorial commentary on each.