BFD-3658: Create new SAMHSA list #2452
Open
+678
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alex-dzeda
requested review from
mjburling,
dondevun,
meliGuzman,
aschey-forpeople and
malessi
as code owners
| https://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets,H0015,1970-01-01,ACTIVE | ||
| https://www.cms.gov/Medicare/Coding/HCPCSReleaseCodeSets,H0050,1970-01-01,ACTIVE | ||
| http://www.ama-assn.org/go/cpt,99408,1970-01-01,ACTIVE | ||
| http://www.ama-assn.org/go/cpt,99409,1970-01-01,ACTIVE |
There was a problem hiding this comment.
Not a big deal, but for ease of reading through this, maybe it's better to have all the codes grouped by system?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
JIRA Ticket:
BFD-3658
What Does This PR Do?
This PR re-creates the existing SAMHSA list, with date-definite start and end dates for each code. It does not meet the criteria for BFD-3659, as further work is ongoing to determine the needs behind some of the historical codes. The formatting also differs slightly from the ticket. Given that there have been no updates to the ICD-9/ICD-10 lists since at least 2015, I believe it's more prudent to store a diff, rather than utilizing 1/5/24 as the starting point.
What Should Reviewers Watch For?
If you're reviewing this PR, please check for these things in particular:
This file will be cached / loaded into memory / into a database at runtime and referred to while data is ingestion. With the intent of this being used to find a union with a continuous timeframe, is a hardcoded date, or some other constant preferred for start and end dates?
What Security Implications Does This PR Have?
Please indicate if this PR does any of the following:
Adds any new software dependencies
Modifies any security controls
Adds new transmission or storage of data
Any other changes that could possibly affect security?
I have considered the above security implications as it relates to this PR. (If one or more of the above apply, it cannot be merged without the ISSO or team security engineer's (
@sb-benohe) approval.)Validation
The count for the "systems" and the codes provided match the existing list, with the addition of two historical entries for MS-DRG 522 + 523.