Linked TLFs

Overview

On March 31, 2022 I had the pleasure of attending the CDISC Open Source Alliance (COSA) Spotlight where from various CDISC community members shared exciting developments from their work. If you're interested in the recording, it can be viewed here.

Among presenters were Mike Stackhouse and Eli Miller from Atorus demonstrating a new feature coming to {Tplyr}: the ability to to query and retrieve individual observations from a summary table using a metadata-driven approach.

Imagine a generic table. Imagine clicking on a particular cell of that table. Imagine being able to easily identify patients that comprise that cell. Let that sink in for a second as I did. Pretty powerful stuff...

An Example

Excited to give it a try, I spent the weekend coding up this example. It uses a demographics table as an anchor. Once a cell is selected, a variety of TLFs are linked for the patients in that cell.

Here is the anchor TLF. I've clicked on the overall total cell for patients categorized as being > 80 years of age. There are N = 77 such patients.

Here is the first linked TLF. A simple listing of the N = 77 patients. In Tplyr, you can specify any additional columns you wish to have too.

I mentioned figures! Here is a safety figure and an efficacy figure for those N = 77 patients. Each of these figures are also interactive thanks to {highcharter}.

Lastly, here is a TLF from a completely separate section (i.e. safety) for those N = 77 patients. I’ve leveraged some of the neat features of {reactable} to nest things.

Forward

Now take this impulse and multiply it by an entire catalog of TLFs and add to it Shiny's capabilities - what have you got?

A Swiss army knife of productivity capable of serving many functions. Think stat analysts, statisticians, medical writing and more...

Access

You can try the app I created for this example here.

You can also access the specific build of `{Tplyr}` with these capabilities by going here.

remotes::install_github("atorus-research/Tplyr@20beb73cd4c202308afbbb57c1f2b6e1590295b7")

I’ll definitely be keeping an eye on more developments and hope to share more with you here.