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

RCPCH users adding causes workflow #877

Open
AmaniKrayemRCPCH opened this issue Apr 22, 2024 · 1 comment
Open

RCPCH users adding causes workflow #877

AmaniKrayemRCPCH opened this issue Apr 22, 2024 · 1 comment
Labels
feature request This is a desirable feature long-term-roadmap For long term ideas planning priority: high High Priority Work - Max 3 Items

Comments

@AmaniKrayemRCPCH
Copy link
Contributor

To discuss the workflow by which we (RCPCH staff) can add causes to the platform.
At the moment, I find the relevant condition on SNOMED, share with Colin for approval, Colin approves, I add to github. I believe Simon then adds the cause to 0006_seed_epilepsy_causes.py

This is currently working well but I anticipate that, as we approach the audit deadline, we'll get many requests that will need to be actioned quickly.

@AmaniKrayemRCPCH AmaniKrayemRCPCH added feature request This is a desirable feature priority: high High Priority Work - Max 3 Items long-term-roadmap For long term ideas planning labels Apr 22, 2024
@mbarton
Copy link
Member

mbarton commented Apr 23, 2024

Commenting to link this to the issues describing technical challenges with how we keep the causes up to date

as we approach the audit deadline, we'll get many requests that will need to be actioned quickly

Even if we don't implement this the team will prioritise these requests :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request This is a desirable feature long-term-roadmap For long term ideas planning priority: high High Priority Work - Max 3 Items
Projects
None yet
Development

No branches or pull requests

2 participants