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

RXR-550: bring 48-hour criteria to KDIGO staging definitions #23

Merged
merged 8 commits into from
Oct 20, 2021
Merged

RXR-550: bring 48-hour criteria to KDIGO staging definitions #23

merged 8 commits into from
Oct 20, 2021

Commits on Oct 19, 2021

  1. Implement 48-hour criteria for KDIGO 

    Rise of 0.3 mg/dl is considered an AKI *if* it occurs within a 48-hour period
    @karawoo
    karawoo committed Oct 19, 2021
    Configuration menu
    Copy the full SHA
    5d01963 View commit details
    Browse the repository at this point in the history

  2. Fix check for age if age is NULL 

    Age isn't required if egfr is provided, but then if we don't use `isTRUE()` then
that conditional has length 0. Adds test for fixed age behavior -- previously if age was NULL this would return a stage of NA which was incorrect
    @karawoo
    karawoo committed Oct 19, 2021
    Configuration menu
    Copy the full SHA
    a1b163b View commit details
    Browse the repository at this point in the history

  3. Fix & add tests for new logic; add clarifying comments

    @karawoo
    karawoo committed Oct 19, 2021
    Configuration menu
    Copy the full SHA
    021c1cf View commit details
    Browse the repository at this point in the history

Commits on Oct 20, 2021

  1. Use double pipes 

    Co-authored-by: Jasmine Hughes <43552465+jasmineirx@users.noreply.github.com>
    @karawoo @jasmineirx
    karawoo and jasmineirx committed Oct 20, 2021
    Configuration menu
    Copy the full SHA
    6cf576c View commit details
    Browse the repository at this point in the history

  2. Don't throw warning if no scr in last 48 hours

    @karawoo
    karawoo committed Oct 20, 2021
    Configuration menu
    Copy the full SHA
    0411e19 View commit details
    Browse the repository at this point in the history

  3. Define new operator for >= with less strict floating point precision

    @karawoo
    karawoo committed Oct 20, 2021
    Configuration menu
    Copy the full SHA
    b363293 View commit details
    Browse the repository at this point in the history

  4. Add documentation for %>=%

    @karawoo
    karawoo committed Oct 20, 2021
    Configuration menu
    Copy the full SHA
    2a068b4 View commit details
    Browse the repository at this point in the history

  5. Update comment

    @karawoo
    karawoo committed Oct 20, 2021
    Configuration menu
    Copy the full SHA
    028ddbe View commit details
    Browse the repository at this point in the history