Fix isObesityCode individual check to match obesity_diag_ranges E65-E68#33
Open
Fix isObesityCode individual check to match obesity_diag_ranges E65-E68#33
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
isObesityCodeonly matched E66 for individual codes, whileobesity_diag_rangesdeclaresE65-E68. This meant passing"E65-E68"as a range returnedTrue, but passing"E65"individually returnedFalse— inconsistent behavior.Note for reviewer
Strictly speaking, only E66 is obesity per se. E65 (localized adiposity), E67 (other hyperalimentation), and E68 (sequelae of hyperalimentation) are related but not obesity diagnoses. The alternative fix would be to narrow
obesity_diag_rangesfrom['E65-E68']to['E66-E66']and keep the individual check as== 66. Either way, the two code paths need to agree.