All fields in Daily Rounds table to treat no value specified as undefined instead instead of colaescing it with 0 or -1 in some fields

[nihal467]

Describe the bug

all the nutrition section field's in the patient critical care is saving the values as 0, when we save critical care without

To Reproduce
Steps to reproduce the behavior:

1. Go to patient critical care and open nutrition section
2. save the critical care without filling any nutrition section fields and save it
3. go to the nutrition tab in the patient consultation page
4. See error

Expected behavior
The empty field in the nutrition section should be a empty object not a 0

Tasks

This can be done as a two-part PR, front-end followed by back-end.

• Frontend: Treat no input as null/undefined (to have a clear distinction between no value specified and value specified but the value could be 0) #7070
• Custom Migration to clean no input values as null in Daily Rounds table care#1810

Screenshots

[rithviknishad]

As discussed,

For ALL THE FIELDS IN DAILY ROUNDS TABLE, we need to send null for if there's no value in the input field. We should not internally coalesce with 0.

This can be done as a two-step exercise:

• Update FE to have a clear distinction between null values and non-null values.
• Custom Migration to clean existing records.

[AshrafMd-1]

@rithviknishad Except nutrition all others show - if there is no data
and in io balance
it's due to the fact that the intake and out-take starts from 0

as you can see now there is no below values

[rithviknishad]

@AshrafMd-1 Let me rephrase how to replicate the issue:

Method 1:

Create a "NORMAL" log update

This form does not collect IO balance related information from the user, so we are NOT supposed to say that the IO Balance was ZERO at this point since we are not aware if it was actually zero since data wasn't collected.

But still we see a record in the chart that it was 0, even though no information about it was collected.

Method 2:

Create a "Critical Care" log update, but do not fill the I/O balance page and submit it.

Same situation here, information was not collected, so we are not supposed to represent that the IO balance was 0 during this log update. But still chart shows 0 in that record.

[github-actions]

Hi, @gigincg, @nihal467, @khavinshankar, @mathew-alex, @aparnacoronasafe, This issue has been automatically marked as stale because it has not had any recent activity.