Support year-based surgery codes #48
Assignees
Comments
|
The full data currently takes about 150KB of memory; I think we need to add about 8 versions of that data in this pass (to support the different versions of the SEER manual). That's still below 1MB of memory. It would be nice to optimize that number, but at the end, it's not huge and shouldn't cause any issues in software using the data. Also, the data will only be loaded per year if needed, so it's unlikely the old years would be loaded. |
depryf
added a commit
that referenced
this issue
Jan 7, 2019
depryf
added a commit
that referenced
this issue
Jan 8, 2019
depryf
added a commit
that referenced
this issue
Jan 12, 2019
garybeverungen
pushed a commit
that referenced
this issue
Jan 15, 2019
…ate utility to modify dxYear so that if it was 2019 it is changed to 2018. Update regex in SiteSpecificSurgeryUtilsTest to accept an optional period as in the Spleen Code 4.22 (#48)
garybeverungen
pushed a commit
that referenced
this issue
Jan 16, 2019
|
This issue was never closed, but it was released a long time ago. Closing now... |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The current surgery code modules takes it's data from the SEER website but only support "the latest data".
We need to add support for multiple SEER manuals (so we keep historic data) and the methods that request the data need to take a year parameter (I guess the current year can be assume if not provided).
The text was updated successfully, but these errors were encountered: