-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update Lab Grading Criteria Metadata #2492
Comments
github-project-automation
bot
added this to admiral (sdtm/adam, dev, ci, template, core)
Aug 7, 2024
Hey @millerg23 just checking on the progress for this issue |
15 tasks
@bms63 you OK if we spit this into 2 separate issues? One for using BNRIND (I just created a pull request for this), and another issue for handling different units? |
I always love breaking things into smaller things and finishing them quickly! What ever makes sense here for you I am okay with! |
bundfussr
moved this from Backlog
to In Progress
in admiral (sdtm/adam, dev, ci, template, core)
Nov 7, 2024
Created #2557 to cover different units. |
bms63
added a commit
that referenced
this issue
Nov 25, 2024
* 2492 use ANRIND for abnormal baseline * 2492 abnormal_indicator added to metadata and function * 2492 fix LINTR * 2492 make final updates including Vignette * Update NEWS.md --------- Co-authored-by: Ben Straub <[email protected]>
github-project-automation
bot
moved this from In Progress
to Archive
in admiral (sdtm/adam, dev, ci, template, core)
Nov 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Grading Criteria Metadata NCI-CTCAEv5
From lab_grading/assumptions-made-when-grading:
Some CTCAE grade definitions contain two sets of units, but only one is provided in the current grading metadata. For example,
TERM=Hypoalbuminemia
has only one row forunit = g/L
, so it's not be able to grade forunit = g/dL
can we add more rows to the metadata to cover different units?
Originally posted by @kaz462 in #2191 (comment)
The text was updated successfully, but these errors were encountered: