TIP-Global-Health / eheza-app

Apache License 2.0
3 stars 1 forks source link

NCD - Labs - Lipid Panel [6h] #550

Closed jeanette-pelizzon closed 1 year ago

jeanette-pelizzon commented 1 year ago

Issue

We are adding in a lab called Lipid Panel into the NCD labs section.

(1) Icon is found in the components file here.

(2) The order screen for this lab looks and operates the same as most of the other labs.

Screen Shot 2022-11-16 at 11 49 17 AM

(3) The results screen for this lab operates differently than other labs. We have had to add in a question asking what format the results were returned in - mmol/L or mg/dL. This is because every lab has a machine that runs this test and the calibration of those machines varies across the different health centers and labs. This is a requirement so we need to figure out how to do this and report the results accurately on the progress report.

Here is the design. Notes are in red.

Screen Shot 2022-11-16 at 11 31 14 AM

(4) Results from this lab should be populated on the progress report in the labs section. Here are the normal ranges for results.

Screen Shot 2022-11-16 at 11 44 00 AM
anvmn commented 1 year ago

@jeanette-pelizzon

This is a requirement so we need to figure out how to do this and report the results accurately on the progress report.

What about definitions for this part?

Also, we need a design for how this should look like on progress report (since we got 4 values for single lab).

jeanette-pelizzon commented 1 year ago

Design:

You will see that the lipid panel comes up with results as abnormal/normal as an overview. These should show up abnormal if any of the individual subtests are abnormal which would then tell the nurse to click through to view the results.

Screen Shot 2022-12-12 at 10 46 44 AM

Once they click into results this is what it will look like:

Screen Shot 2022-12-12 at 10 51 02 AM
adamhstewart commented 1 year ago

@anvmn regarding the mg/dl and mmol/L conundrum, here is a solution:

cc @jeanette-pelizzon

anvmn commented 1 year ago

@adamhstewart

In this case, I'd expect normal ranges to have same proportions. However, this does not allign in any way. The relation is between 37 to 79 mg/dL for 1 mmol/L. It differs even for same measurement min and max (see LDL for example). Selection_1399

Online, I found that there's a conversion calculator. Note that relation for Cholesterol and Triglycerides is not the same.

Selection_1400

Also, about storing values. On backend, we have the value and the unit. These 2 are inputs from the form. We need the unit on backend, so that we can show the form with it's original selection. Now, if we need to store value in mg/dL, this may cause some confusion. So, the question is if we really need it stored in mg/dL, or we can simply have it presented on progress report in mg/dL?

//cc @jeanette-pelizzon

adamhstewart commented 1 year ago

@anvmn Thanks for checking teh work - it appears I came up with a general formula, but there is a different conversion for cholesterol measurements (not sure why, but alas):

For Total Cholesterol, HDL cholesterol and LDL cholesterol:

- To get from mmol/L to mg/dL multiply by 38.66976;
- To get from mg/dL to mmol/L multiply by 0.02586.

For Triglycerides:

- To get from mmol/L to mg/dL multiply by 88.57396;
- To get from mg/dL to mmol/L, multiply by 0.01129.

https://www.mdapp.co/cholesterol-conversion-calculator-600/

So, the question is if we really need it stored in mg/dL, or we can simply have it presented on progress report in mg/dL?

I think if we can effectively convert, it's important to store in a consistent unit - that way we can do meaningful data analysis.

Storing the original measurement unit is good though, for archival purposes.

LudmilaGoichman commented 1 year ago

@adamhstewart @anvmn

Please help. I am confuse with the ranges.

  1. the app has an error in the normal range for total cholesterol in mg/dL. The normal value is greater than 200
Screenshots_-_Google_Drive
  1. If the value of triglycerides in mmol/L is 0.67 and is below the normal range, then why is the value converted to mg/dL - 59.34 a normal value?
Screenshots_-_Google_Drive Screenshots_-_Google_Drive
  1. I didn't know about the following formula and entered the wrong values. Maybe LCD or HDL or Total Cholesterol should be calculated?

https://www.omnicalculator.com/health/ldl

Pasted_Image_03_01_2023__18_13

LDL_Cholesterol_Calculator
  1. should fasting or non-fasting be considered? ^^
anvmn commented 1 year ago

@LudmilaGoichman

  1. The app has an error in the normal range for total cholesterol in mg/dL. The normal value is greater than 200.

Requirements should not have used <. Total cholesterol should be bellow 200. Selection_1463

  1. If the value of triglycerides in mmol/L is 0.67 and is below the normal range, then why is the value converted to mg/dL - 59.34 a normal value

Do not bother with conversions. We only use mg/dL ranges. Those are the ones that should be tested.

  1. I didn't know about the following formula and entered the wrong values. Maybe LCD or HDL or Total Cholesterol should be calculated?

I believe that calculations are performed at the lab. We only input those results.

  1. should fasting or non-fasting be considered? ^^

Right now, there were no such requirements. @jeanette-pelizzon do you know anything about it?

anvmn commented 1 year ago

@LudmilaGoichman with the answers above, I do not see a problem to proceed with QA for this issue, so I assign it back to you.

LudmilaGoichman commented 1 year ago

@anvmn @jeanette-pelizzon

I only checked the ranges in mg/dL

Do not bother with conversions. We only use mg/dL ranges. Those are the ones that should be tested.

The ranges in mg/dL: TC: < 200 LDL: 130 - 160 HGL: 40 - 60 TG: 54 - 150

NCD_-_Labs_-_Lipid_Panel__6h__·_Issue__550_·_TIP-Global-Health_eheza-app

Questions:

  1. The issue 4 from https://github.com/TIP-Global-Health/eheza-app/issues/417#issuecomment-1369135701 fixed in https://github.com/TIP-Global-Health/eheza-app/pull/581 , but in this fixed bug the entry in case management disappears after refreshing the page, and when testing the Lipid Panel, the entries don't disappear at all. I hope this is also fixed in https://github.com/TIP-Global-Health/eheza-app/pull/581
Screenshots_-_Google_Drive
  1. This test doesn't exist in Antenatal Care encounter, but the report shown at https://github.com/TIP-Global-Health/eheza-app/issues/550#issuecomment-1347077548 is from Antenatal Care. Should a test be added to this encounter?
207129132-b42bb79b-4b76-4865-8525-a33c649db339_png__884×1244_
  1. This question is not related to this issue, but I cannot be silent. Sorry.

Antenatal Care encounter. this screen looks bad and annoying. The space is missing under the word "Birth":

Screenshots_-_Google_Drive

Checked and Approved:

  1. The icon is correct:
active not active
Screenshots_-_Google_Drive Screenshots_-_Google_Drive
  1. The flow (screens) is correct. Example:

Activity:

Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive

Lab Results:

Screenshots_-_Google_Drive Screenshots_-_Google_Drive
  1. The lab results. The question asking what format the results were returned in - mmol/L or mg/dL has been added. The selected units are displayed next to the numeric fields.
Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive
  1. NCD. Report looks as expected (see images in the point 6)
  2. NCD. A test row in the Lab Results Table is displayed as abnormal if any of the individual subtests is abnormal.
at least one subtest is abnormal all subtests are normal
Screenshots_-_Google_Drive Screenshots_-_Google_Drive
  1. NCD. Results ranges in mg/dL are correct:
Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive
Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive
Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive
Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive
  1. NCD. Subsequent encounter report:
Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive
Screenshots_-_Google_Drive Screenshots_-_Google_Drive Screenshots_-_Google_Drive
anvmn commented 1 year ago

@LudmilaGoichman

Points 1 and 3 fixed at #581.

  1. This test doesn't exist in Antenatal Care encounter, but the report shown at ...

The design is not accurate here. The test appears only at NCD encounter.

LudmilaGoichman commented 1 year ago

@anvmn @jeanette-pelizzon

Checked and Approved:

  1. Case management entry disappears after entering test(s) results
Screenshots_-_Google_Drive Screenshots_-_Google_Drive
  1. Antenatal Care encounter. Added space under the word "Birth" in this screen:
Screenshots_-_Google_Drive