Systems' Data Infrastructure
MOOVPAD general and pro user apps will generate a lot of data across the different platforms and contexts. This data itself needs to be analysed to improve service provision. There's also a need to analyse the performance of the systems themselves, as well as general and pro user interaction data with each other and the systems. Here's a brief overview of the current plan for the management of all these...
Examples of the types and levels of data to be analysed include:
- WebAPI requests from different clients, to help assess the performance of servers and systems infrastructure;
- General and Pro user data such as the types and volume of interactions with the systems;
- Interactions between general and pro users, to help optimise the systems accordingly;
- MOOV data uploaded to the system by users, which will be useful for improving service delivery and creating new MOOV templates, as well as providing opportunities for health research;
- Pro user interactions relating to business functions within the overall system context, to optimise these;
- Overall MOOVPAD performance statistics relating to system bottlenecks at the infrastructure, workflow, application, and human levels.
There will be other categories of data collected, but the above examples highlight the large scope and volume of information that needs to be managed. And all of these analyses and reporting needs will require specialised tools. Some of these are already available, and I continue to learn more about these as I progress. However there are a wide range of management functions that I cannot find suitable tools currently available for at this stage. This means that at some point, I will also need to develop specific tools and systems for particular MOOVPAD administrative and research and development functions. In order to build these solutions well, I will need to make more progress on all of the MOOVPAD apps themselves before delving too deeply into these analytical systems.
The work and ongoing learning in relation to webAPI's and issues such as security are helping to get my brain around the needs of these admin systems, and I'm trying to factor these requirements into the coding as I go along. For now though, I just wanted to bookmark these factors here for later discussion.
Back to work 🙂
Stay awesome,
EMH
HOW MOOVPAD IS BEING BUILT
For the overview of how MOOVPAD apps are being developed, the reasoning behind particular decisions during development, policies, and more in relation to all the technical things, please see the link to the left.
This will be an ongoing work in progress, and will always be linked to the bottom of each upcoming Blog post.