Improving pregnancy support #55
Conversation
Adding pregnancy end date and adding maternal and neonatal outcomes
| z_cst_indv_pregnancy_maternal_outcome = fields.Selection( | ||
| [ | ||
| ("normal", "Normal"), | ||
| ("preterm", "Preterm birth"), | ||
| ("stillbirth", "Stillbirth"), | ||
| ], | ||
| "Maternal outcome", | ||
| ) | ||
| z_cst_indv_pregnancy_neonatal_outcome = fields.Selection( | ||
| [ | ||
| ("normal", "Neonatal death"), | ||
| ("conanomalies", "Congenital anomalies"), | ||
| ("infections", "Neonatal infections"), | ||
| ("loweight", "Low birth weight"), | ||
| ("small", "Small for gestational age"), | ||
| ("respiratory", "Respiratory distress"), | ||
| ("thrive", "Failure to thrive"), | ||
| ("seizures", "Neonatal seizures"), | ||
| ("neurodevdelay", "Neurodevelopmental delay"), | ||
| ], | ||
| "Neonatal outcome", | ||
| ) |
There was a problem hiding this comment.
Should this be here or in an event data where the last value is linked ? So we do not loose history of every birth.
There was a problem hiding this comment.
While working on this, I was also thinking that the entire pregnancy implementation (start/end/outcomes) should be event data. Like a "pregnancy event." Then the indicators could use the currently active pregnancy event, as only one pregnancy can be ongoing at the same time.
Should we spend the time to convert this into an event for the demo application? I agree it is a step in the right direction in showing how such data should be implemented in OpenSPP.
|
There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days. |
github-actions
bot
added
the
stale
Adding pregnancy end date and adding maternal and neonatal outcomes