297 visits stop-gap bugfix #298
Merged
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
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.
@maximusunc This PR fixes the issue #297 and has been deployed to all ICEES+ instances for now before we update FHIR PIT and rerun FHIR PIT to generate new data. After FHIR PIT is updated and new data is regenerated, I'll need to create another small PR to remove a condition check in get_operator_and_value() function which is covered in detail in the comment there. Since I am not sure when we can finish FHIR PIT and data update and the condition check to be removed for the stop-gap solution is a small code change, I am creating this PR now to get this merged so the code is in sync with latest deployment.