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

Add optional fields to denote radiation boost #375

Open
hknahal opened this issue Nov 14, 2022 · 4 comments
Open

Add optional fields to denote radiation boost #375

hknahal opened this issue Nov 14, 2022 · 4 comments
Assignees

Comments

@hknahal
Copy link
Contributor

hknahal commented Nov 14, 2022

Implementation:

Based on discussions with MOHCCN Clinical Commitee and ARGO CMD Working Group, the following two new optional fields will be added to the Radiation schema:

Field Name Description Data Tier Attributes Type Permissible Values
“radiation_boost” A radiation boost is an extra radiation treatment targeted at the tumor bed, given after the regular sessions of radiation is complete (Reference NCIt: C137812). Indicate if this radiation treatment was a radiation boost. Extended TEXT Yes, No
“reference_radiation_treatment_id” If a radiation boost was given, indicate the 'submitter_treatment_id' of the primary radiation treatment the radiation boost treatment is linked to. Extended Required/Conditional Only required if 'radiation_boost' = 'Yes' TEXT

Rationale:
Some cancers (eg. breast cancer) require a supplemental dose of radiation. This provides a way to denote this in the clinical submission.

@puneet-oicr
Copy link

Can't be added to Dictionary 1.16 due to a clinical dependency

@puneet-oicr
Copy link

Almost complete

@puneet-oicr
Copy link

Dependency on clinical expectations, QA changes to be tested. To be part of Dictionary 1.18

@Buwujiu
Copy link
Contributor

Buwujiu commented Jul 27, 2023

Once the clinical cross file validation is ready, will deploy this too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants