Replies: 1 comment 2 replies
-
|
Following up on my own post: I had a look through the code, and the isolated version of this turns out to be small for the two charts that already have WHO overlays (Weight and Height). The percentile graphs already position the WHO curves relative to the child's birth date. In reports/graphs/weight_change.py and Concretely, I think it's four small touch points:
That's the whole behaviour change. If due_date is left blank, everything stays exactly as it is today for term births. Happy to open a PR if that'd be welcome. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When tracking premature infants, using their actual birth date incorrectly positions them on the WHO weight growth charts. This makes them appear significantly underweight compared to full-term peers. Clinical practice routinely plots premature infants using their "adjusted age" (calculated from their expected due date) until they reach 2 years of age.
Issue #369 previously discussed this under a much larger scope (a full "Adjusted Age" mode toggling timelines, developmental milestones, and age calculations across the entire application). Because of that broad scope, it possibly became complex and stalled out?
I would like to propose a much simpler, isolated implementation: an optional field in the Child model for Expected Due Date, which is only used to shift the horizontal axis of the growth charts.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions