Remove IMRs from report/measure context #734
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
- Report both `Patient` and initial data retrieval. - Don't preemptively round to the nearest cent. - Report to the nearest mille.
Since `ReportContext` is accessed from both the main request-handling thread and thread-pool threads (e.g., during query and evaluation, which are parallelized across patients), its fields must be published safely in order to ensure proper visibility.
This was causing `OutOfMemoryError`s for large ACH reports. To work around, store *only* POIs (not entire IMRs) to be evaluated in the supplemental phase. Then during aggregation, retrieve IMRs from the database since we don't have them lying around in memory.
seanmcilvenna
approved these changes
Mar 22, 2024
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.
No description provided.