Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove IMRs from report/measure context #734

Merged
merged 3 commits into from
Mar 22, 2024
Merged

Remove IMRs from report/measure context #734

merged 3 commits into from
Mar 22, 2024

Commits on Mar 21, 2024

  1. Fix progress reporting 

      - Report both `Patient` and initial data retrieval.
  - Don't preemptively round to the nearest cent.
  - Report to the nearest mille.
    @smailliwcs
    smailliwcs committed Mar 21, 2024
    Configuration menu
    Copy the full SHA
    80117cc View commit details
    Browse the repository at this point in the history

  2. Fix unsafe publication 

    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.
    @smailliwcs
    smailliwcs committed Mar 21, 2024
    Configuration menu
    Copy the full SHA
    b041967 View commit details
    Browse the repository at this point in the history

  3. Remove IMRs from measure context 

    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.
    @smailliwcs
    smailliwcs committed Mar 21, 2024
    Configuration menu
    Copy the full SHA
    7d07583 View commit details
    Browse the repository at this point in the history