-
Notifications
You must be signed in to change notification settings - Fork 7
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
Implement precancer/clinical data updates and testing #306
Comments
Pre-cancer atlases: BU, Duke, HMS, Stanford |
@aclayton555 set up time with Kristen to confirm approach and timelines for implementing changes in renewal, and how we want to implement these. Think about what we want to write into the renewal. Recommend that Kristen also connect with CRDC. |
We met with Kirsten on 2 Nov. Backlogged once we have concrete plans for data model implementation |
Notes from discussion with Kristen here: https://docs.google.com/document/d/18Krq5x-5dGcPxC9X_B24S5JMv0iXILF5_qwpvpUk4_U/edit#bookmark=id.8n4luqvw09n4 |
Also revisit updates of optional -> required fields, as outlined in # 2 of #355 |
Propose a new (simple) manifest called 'Clinical Data Update' that will allow DCC to capture two important bits of information about cases: vital status, and precancer designation/description.
This information is contained in the attached Excel spreadsheet. |
Update to 'Precancerous Condition Type' permissible value list is logged in ticket #334 |
I think the above comment was meant to be linked to: #392 |
@adamjtaylor I would suggest we not list specific WHO Tumour Classification v5 codes at this time (I am not sure I can find a comprehensive list - and the full list is by subscription only). |
regarding
I not able to implement this for I am hoping to be able to implement for |
Working with Kristen Anton to start implementing data model changes (maybe in separate branch). Consider proposed updates presented here: https://docs.google.com/presentation/d/1yWnmNKhEe9uXDMzdLa77DDPyQqh-54Lkq2ywSCztgjA/edit?usp=sharing
The text was updated successfully, but these errors were encountered: