Feature request: SDTM input functions

Open
#516 2 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Gero1999 is already working on this.

Since Mar 16, 2026.

  • #517 by @Gero1999 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
20/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
data

Research direction

The issue proposes ex_to_pkncadose, pc_to_pkncaconc, and sdtm_to_pkncadata, and points to draft PR #517 as an example. Start by reviewing that PR and the existing input/mapping conventions in PKNCA. Done means the SDTM conversion functions and their behavior are agreed and implemented; the thread does not specify tests or acceptance criteria.

Written by the indexing model from the issue text.

Description

So in aNCA we are highly interested in simplifying more and more the mapping. I though that it might make sense to also have these functions available for PKNCA. The idea is to directly accept SDTM data (PC, EX) using their column assumptions and standard naming for the default arguments. That way if an user has a standard SDTM they can directly do:

o_dose <- ex_to_pkncadose(ex)
o_conc <- pc_to_pkncaconc(pc, ex)

or even

o_data <- sdtm_to_pkncadata(pc, ex, dm)

@billdenney what do you think? I will open a draft PR (#517) for you to check an example (ex_to_pkncadose), but feel free to close this issue/PR if is not seen as fitted for PKNCA

Dominant language
R
Stars
86
Forks
32
Avg merge
16h 25m
Merged PRs (30d)
51

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from humanpred/pknca

All issues in humanpred/pknca

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.