Skip to content
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

Closes #253 fix_bor_ne: Add CR and PR to bor_ne event #271

Merged
merged 6 commits into from
Dec 13, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 2 additions & 10 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,6 @@
Thank you for your Pull Request! We have developed this task checklist from the
[Development Process
Guide](https://pharmaverse.github.io/admiral/CONTRIBUTING.html#detailed-development-process)
to help with the final steps of the process. Completing the below tasks helps to
ensure our reviewers can maximize their time on your code as well as making sure
the admiral codebase remains robust and consistent.
Thank you for your Pull Request! We have developed this task checklist from the [Development Process Guide](https://pharmaverse.github.io/admiral/CONTRIBUTING.html#detailed-development-process) to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.

Please check off each taskbox as an acknowledgment that you completed the task
or check off that it is not relevant to your Pull Request. This checklist is
part of the Github Action workflows and the Pull Request will not be merged into
the `main` branch until you have checked off each task.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the `main` branch until you have checked off each task.

- [ ] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update). Then the issue is closed automatically once it is merged to `main`.
- [ ] Code is formatted according to the [tidyverse style guide](https://style.tidyverse.org/). Run `styler::style_file()` to style R and Rmd files
Expand Down
7 changes: 7 additions & 0 deletions NEWS.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# admiralonco (development version)

## Updates of Existing Functions

- The `bor_ne` event object was updated such that `CR` and `PR` are additionally
considered as event. This ensures that the confirmed best overall response for a
patient with a single `CR` or `PR` assessment is derived as `"NE"` instead of
`"MISSING"`. (#253)

## Documentation

- New vignette "Creating ADRS with iRECIST endpoints". (#233)
Expand Down
6 changes: 3 additions & 3 deletions R/response_sources.R
Original file line number Diff line number Diff line change
Expand Up @@ -136,11 +136,11 @@ bor_pd <- event(
#' @export
bor_ne <- event(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

shouldn't this update be for cbor_ne rather than bor_ne? that's what we did for admiralroche.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not have cbor_ne in admiralonco. We use bor_ne for both BOR and CBOR.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we should change this?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok, happy to go with your call as I see similar case with bor_sd. i'll approve for now and then if you decide to update i can re-review.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should also update ibor_ne for iRECIST

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point.
Updated

description = paste(
"Define not evaluable (NE) for best overall response (BOR) as SD, NON-CR/NON-PD,",
"or NE (should be specified after bor_sd and bor_non_crpd)"
"Define not evaluable (NE) for best overall response (BOR) as CR, PR, SD,",
"NON-CR/NON-PD, or NE (should be specified after bor_sd and bor_non_crpd)"
),
dataset_name = "ovr",
condition = AVALC %in% c("SD", "NON-CR/NON-PD", "NE"),
condition = AVALC %in% c("CR", "PR", "SD", "NON-CR/NON-PD", "NE"),
set_values_to = exprs(AVALC = "NE")
)

Expand Down
6 changes: 3 additions & 3 deletions vignettes/irecist.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -648,11 +648,11 @@ ibor_iupd <- event(

ibor_ne <- event(
description = paste(
"Define not evaluable (NE) for best overall response (iBOR) as iSD, NON-iCR/NON-iUPD,",
"or NE (should be specified after ibor_isd and ibor_non_icriupd)"
"Define not evaluable (NE) for best overall response (iBOR) as iCR, iPR, iSD,",
"NON-iCR/NON-iUPD, or NE (should be specified after ibor_isd and ibor_non_icriupd)"
),
dataset_name = "ovr",
condition = AVALC %in% c("iSD", "NON-iCR/NON-iUPD", "NE"),
condition = AVALC %in% c("iCR", "iPR", "iSD", "NON-iCR/NON-iUPD", "NE"),
set_values_to = exprs(AVALC = "NE")
)

Expand Down
Loading