BUG: Units of value are missing from Labs Component table

[angelathe]

Description

In the Lab Components tables, we're missing units of value under the Value column. It is important to display the units for each lab component to ensure accurate interpretation of the data and avoid misinterpretation.

This may require design review/consultation. Not sure if we want to concatenate with spaces (i.e. 36.1 g/dL), or without (i.e. 59%), or some combination of both?

Steps to reproduce

Examples:

• 3d607116-9e59-4e42-a084-c5cff4b023f1: Unit of measurement not displayed for relevant lab results
• 10e5b07b-5d3f-426f-a7e1-13ea909ff5a5: Unit of value is not displayed (Ex. should display 38%, 95%, etc.)
• 3a6febc6-cc0f-4706-8322-da0cd16bb7c6: Not displaying units for result value — relevant to all lab results
• TN_sample eCR2: Units for lab component values are not displayed when info is available
• TN_sample eCR4: Units for lab component values aren’t displayed when info is available
• 5370592c-6dd3-4de5-b4f6-8a2f4b0253aa: Value is missing data (%)

Expected Result

If units are available, they should be concatenated to the value.

Actual result

Example from 10e5b07b-5d3f-426f-a7e1-13ea909ff5a5:

Priority

Provide an estimate for level of impact the bug has today by placing an X in the applicable bracket

Priority

• [ ] Low priority The bug does not have to be fixed immediately. High and medium priority bugs should be addressed first.
• [x] Medium priority Typically, medium-priority bugs do not affect customers directly and therefore can be fixed in the normal course of testing and development.
• [ ] High priority High priority bugs must be addressed immediately. They often affect the app’s functionality and impact customers and their user experience. They must take priority.

Notes

We should already be converting units to FHIR (this will not require any conversion).

Please check that all examples of missing units (above) have been fixed via this ticket.