Can we handle the semantics of different surgery codes at analysis time and not within REDCap?

NU-QDSC / cancer-informatics

Repository to track cancer informatics best practices and shared code.

3 stars 1 forks source link

Can we handle the semantics of different surgery codes at analysis time and not within REDCap? #276

Closed mgurley closed 2 weeks ago

mgurley commented 3 weeks ago

NAACCR has a very bad habit of changing the meaning of codes based on year and or anatomic site. This would be very difficult to handle in REDCap. Can we just store the codes in REDCap and leave the semantics to analysis time? https://www.naaccr.org/crosswalks-interoperability/

mgurley commented 2 weeks ago

We can remove 1290 because it is for 2022 cases and before.

PerifanosPrometheus commented 2 weeks ago

Yes, Sun will handle this.

Here are the two crosswalk files needed to map codes: RX-Summ-Surg-Prim-Site-2024-Tables.xlsx (live.com) - diagnosis dates in 2024 and afterwards RX-Summ-Surg-Prim-Site-2023-Tables.xlsx (live.com) - diagnosis dates in 2023 only