Menu ▾ ▴

#3525 Measurement Display in Lab Viewer Omits Manually Entered Values

12.1.1
pending
nobody
None
7
2015-02-19
2014-10-12
Trimara Corporation
No

Problem Summary:
When you click a measurement within a lab (e.g. HDL, LDL, etc), the result window that appears doesn't show values that were manually entered by users through the measurements section, it only shows result that came from labs. This differs from the display when you click measurements in the measurements section where it shows the both types. Screenshots attached.

Expected Result:
The result window should show all results, regardless of whether or not they came from a lab or were manually entered by a user.

Actual Result:
The display only shows results from labs; results that were manually entered are not shown.

Steps to Reproduce:
(1) Upload the attached lab and assign it to a patient chart. The lab contains one HDL result.
(2) Go to Admin-->Customize oscarMeasurements and configure OSCAR to allow users to enter HDL results in the Measurements section of the Encounter Screen.
(3) In the chart from (1), manually and an HDL measurement through the measurements section.
(4) Click HDL in the measurements section ... note that two results are displayed, the one from the lab and the one that was manually entered.
(5) Open the lab uploaded in (1). Click "HDL CHOLESTEROL" ... note that only one result is displayed, the result entered in (3) is not displayed.

Reproduced In:
12_1 Deb 436 (fresh install) + Ubuntu 12 LTS (fresh install)

Additional Information:
-- The reason manually entered values are not displaying is because the query relies on the measurement having an entry in the measurementsExt table. Values entered through the measurements section do not have an entry in the measurementsExt table. An example query is shown below:
SELECT DISTINCT e2.val AS lab_no FROM measurements m JOIN measurementsExt e1 ON m.id=e1.measurement_id AND e1.keyval='identifier' JOIN measurementsExt e2 ON m.id=e2.measurement_id AND e2.keyval='lab_no' WHERE e1.val='2165' AND m.demographicNo='1'

3 Attachments
hdl_gamma_dynacare.txt
ldl_in_lab_section.png
ldl_in_measurements_section.png

Discussion

  • Trimara Corporation

    Trimara Corporation - 2014-10-12
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,5 +1,5 @@
 Problem Summary:
-When you click a measurement within a lab (e.g. HDL, LDL, etc), the result window that appears doesn't show values that were manually entered by users through the measurements section, it only shows result that came from labs. This differs from the display when you click measurements in the measurements section where it shows the both types.
+When you click a measurement within a lab (e.g. HDL, LDL, etc), the result window that appears doesn't show values that were manually entered by users through the measurements section, it only shows result that came from labs. This differs from the display when you click measurements in the measurements section where it shows the both types. Screenshots attached.

 Expected Result:
 The result window should show all results, regardless of whether or not they came from a lab or were manually entered by a user.
     

  • SBek

    SBek - 2014-10-14
    • status: open --> pending
    • Priority: 9 --> 7
     

  • SBek

    SBek - 2014-10-14

    This is the behaviour that has existed for some time. Need to verify what the required business requirements on this. Will leave the ticket as pending at this moment and downgrading the priority as a workaround is available.

     

  • Trimara Corporation

    Trimara Corporation - 2014-11-06

    Hi Suni. I don't think marking it as pending is the right handling here. When a physician clicks the measurement, they will want to see all of the HDL values over time regardless of whether they came from a lab or were user entered.

    Also, since all of the values come from the measurements table and it's just the fact the extended information isn't present, I'm pretty sure it's clear that the query was just a little too restrictive as a result of a programming oversight.

     

  • Trimara Corporation

    Trimara Corporation - 2015-01-12

    Hi Suni,

    Is there any update available for this issue?

     

  • Trimara Corporation

    Trimara Corporation - 2015-02-19

    Hi Suni,

    This has been an accepted issue since Oct 14, 2014. Is there any update available. Our clients would like to resolve this issue.

     
MongoDB Logo MongoDB