BlueCode identified that users are using the "lost to follow-up" feature in the Android client to remove children who were registered with incorrect details. For example, they create a child with the wrong date of birth. We would like to create a materialized view in the ZEIR production ETL that identifies children who have been lost to follow-up.
Columns:
ZEIR_ID
(optional) m_zeir_id
eventType
base_entity_id
dateCreated
dateEdited
{Any values that are collected as observations}
This will be used to identify potential duplicate clients in the system. I made the m_zeir_id optional so that we could see if a child registration form accidentally created duplicate mothers.
BlueCode identified that users are using the "lost to follow-up" feature in the Android client to remove children who were registered with incorrect details. For example, they create a child with the wrong date of birth. We would like to create a materialized view in the ZEIR production ETL that identifies children who have been lost to follow-up.
Columns: ZEIR_ID (optional) m_zeir_id eventType base_entity_id dateCreated dateEdited {Any values that are collected as observations}
This will be used to identify potential duplicate clients in the system. I made the m_zeir_id optional so that we could see if a child registration form accidentally created duplicate mothers.