Add nonPRD Pregnancy type to Episode of Care Search queries #49
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
…to parameters specified by Epic documentation.
…to apply function. Set parameters to lookback date specified by pilot partner.
Merged
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.
In recent testing of a patient with a pregnancy, the PRD Episode Of Care type ID was not returning any pregnancy resources, and was throwing an error in the console when added as an EoC Search parameter. This PR adds the nonPRD Episode of Care type ID, so that we can see whether pregnancies are in fact being recorded with this ID in SUP.
Note: this is to reflect a manual update that our pilot partner made in the deployed version of the codebase. It will be helpful to include in our code now while we are testing, but the extra FHIR Search may be removed once we have tested in production. Since an EpisodeOfCare.type ID is specified, I don't affect this update should negatively impact performance in any significant way.