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

SCT Code for Neoplasm Malignant Primary (Tumor) possibly outdated #4

Open
LennyN95 opened this issue Oct 1, 2023 · 3 comments
Open
Labels
bug Something isn't working help wanted Extra attention is needed

Comments

@LennyN95
Copy link
Member

LennyN95 commented Oct 1, 2023

We currently use the code 86049000 for the segmentation of primary malignant neoplasms.
According to the SCT browser, this code is marked as "OUTDATED".

@fedorov this is the code we use in IDC:

Bildschirmfoto 2023-10-01 um 12 13 50

I'd like to start the discussion on how we best proceed w.r.t. MHub:

  • What does "OUTDATED" actually mean for SCT codes?
  • What are the consequences of using an outdated code?
  • Do we keep using the code to maintain consistency with the segmentations in IDC?
  • Do we need to switch to an updated code?
  • Which code would be an appropriate candidate?
@LennyN95 LennyN95 added bug Something isn't working help wanted Extra attention is needed labels Oct 1, 2023
@dclunie
Copy link

dclunie commented Oct 8, 2023

SNOMED has notified DICOM about the recent (JULY 2023 INT release) inactivation of:

86049000 | Neoplasm, malignant (primary)

I have discussed this with them and will probably end up replacing it in DICOM with:

372087000 | Primary malignant neoplasm (disorder)

in a forthcoming CP, which will become available in November (I will link it here when ready).

@LennyN95
Copy link
Member Author

LennyN95 commented May 6, 2024

which will become available in November

Checking back if we have any update here :)?

@dclunie
Copy link

dclunie commented May 6, 2024

The DICOM CP 2358 to fix this is currently out for ballot, which means that it will be final text later this month. I don't expect there will be any opposition to using 372087000 as the CP proposes.

@vanossj vanossj mentioned this issue Aug 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants