By using the FeverApp to document fever events, you support the scientific registry for research on fever in ambulatory care. The following provides those interested in research with a brief overview of the nested and grouped data structure. Certain data have 1:n or n:1 relationships.
In our system, the unit of observation is primarily the family, represented by an eight-digit lowercase string as the "family code," which is itself related to the four-digit practice number and thus simultaneously identifies the distributing practice in the corresponding country. It allows multiple users to view and edit the same data in a synchronized manner. All data that is deleted in the app is also deleted in the central register at Witten/Herdecke University. In each family (user), there can therefore be several users (roles) who observe several children (profiles). One or more users of a family therefore document one or more children with one or more entries (loops). These entries result in one or more fever phases (episodes), currently defined until a child is marked as "healthy" or when no entry was made for two days (>48h). Each episode can consist of one or more entries (loops).
Research
Each entry (loop) consists of 1 to n events:
- Temperature of the child in the user's observation
- Well-being of the child in the observation of the user
- Perception of safety of the user
- Warning signs on the child in the observation of the user
- Notes on the child in the observation of the user
- Measures taken on the child in the user's observation
- Medication (defined PZN list) for the child by administration of the user
- Doctor's presentations and recommendations during an episode
- diagnoses given there (defined list)
- or vaccinations (defined list)
- self-observed febrile seizures (only assigned by the family in the menu)
