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

Separate CTV3 and TPP-CTV3 coding systems #1448

Open
Tracked by #1446
rebkwok opened this issue Nov 23, 2022 · 0 comments
Open
Tracked by #1446

Separate CTV3 and TPP-CTV3 coding systems #1448

rebkwok opened this issue Nov 23, 2022 · 0 comments

Comments

@rebkwok
Copy link
Contributor

rebkwok commented Nov 23, 2022

CTV3 is a retired coding system. We have the last (April 2018) release in OpenCodelists, and to this we add TPP's CTV3 codes, plus TPP-specific extensions (Y codes).

OpenCodelists calls this "CTV3", but it isn't really; it's CTV3 plus TPP extensions, plus some codes that are in the April 2018 CTV3 release but are not in TPP. As of 16th Nov 2022, CTV3 codes that are not in TPP are all concepts with "redundant" status.

OpenCodelists uses both raw CTV3 and TPP CTV3 codes when doing searches, but TPP only when building the hierarchy/tree.

Proposal: split CTV3 and TPP-CTV3 into separate coding systems in OpenCodelists. For the most part, they're treated separately anyway, and have their own models which will be quite easily separated.

All CTV3 codelists currently in OpenCodelists are really TPP-CTV3. "Raw" CTV3 is unlikely to be used for new codelists (and certainly not for any that are to be used in OpenSafely), but we can maintain it for non-OpenSafely users.

This means that new imports for TPP-CTV3 only need to import the TPP models.

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

1 participant