Submitted:
26 June 2024
Posted:
27 June 2024
You are already at the latest version
Abstract
Keywords:
1. Introduction
2. Related Work
- Subject Oriented. Subject oriented-ness in the context of a data warehouse refers to the design principle where the data warehouse is organized and optimized around business subjects or topics, rather than the operational processes or functions of an organization. This approach allows for a more user-friendly and business-focused structure, making it easier for analysts and decision-makers to retrieve relevant information. Subject oriented-ness ensures the data focuses on specific healthcare aspects, aiding in comprehensive analysis and decision-making. This approach enhances the effectiveness of healthcare services by providing valuable insights into patient care, operations, and outcomes.
- Integrated. The integrated-ness of a data warehouse refers to the degree to which data from various sources and formats are combined and made accessible in a unified manner within the warehouse. A highly integrated data warehouse ensures that data is consistent, accurate, and can be easily analyzed for decision-making purposes. Data warehousing in healthcare involves consolidating and organizing diverse healthcare data sources into a unified repository. Integrated-ness ensures seamless access and analysis, fostering data-driven decision-making in healthcare services. This approach enhances efficiency, patient care, and enables comprehensive insights for informed healthcare management.
- Volatile. Volatility refers to the frequency and extent of changes in the data. If data within the warehouse frequently changes or is updated, it is considered volatile. This could be due to regular updates, inserts, or deletions of data. A data warehouse unlike an operational database, should be non-volatile. In healthcare, data warehousing volatility refers to the fluctuation in the volume and types of data collected over time. It impacts the ability to maintain stable and consistent data for analysis, making it challenging to derive meaningful insights. This volatility can stem from evolving healthcare protocols, changing patient demographics, and technological advancements. This heightens the demand for data ware housing.
- Time-variant. And a data warehouse is considered time-variant because it stores historical data and allows users to analyze changes in data over time. Data warehousing in healthcare involves storing and managing vast amounts of patient-related information. Time variance in this context refers to tracking changes in health data over time, allowing for historical analysis. The time variance property also aids healthcare providers in making informed decisions, improving patient outcomes, and enhancing overall efficiency in delivering quality care.
2.1. Data Warehouse Architecture
2.2. Data Modeling
- Generic dimension: It helps provides a consistent framework for data collection, enabling comparison across different parameters such as age, community or gender. This is possible because generic dimension pattern involves standardized dimensions, such as patient demographics like age, gender or even address. This then improves data integrity.
- Date dimension: Date dimension track events with respect to time. For example, they can be used to track patient visits, treatments, or even follow-ups. With data dimensions, it is possible to carry out trend analysis, such as identifying peak times for outpatient visits or evaluating the effectiveness of treatment schedules over time.
- Degenerate dimension: Because degenerate dimensions deal with dimensions that don’t have associated tables, for example outpatient visit IDs. In healthcare delivery, they can help in uniquely identifying each patient visit without necessarily requiring a separate dimension table, streamlining data storage and retrieval processes.
- Role-Playing dimension: This pattern allows a single dimension to play multiple roles. For instance, the date dimension can represent appointment date, follow-up date, and treatment start date. It reduces redundancy and simplifies the data model, aiding in efficient reporting and analysis.
- Junk dimension: Junk dimensions combines several low-cardinality attributes, such as patient consent types or visit reasons, into a single dimension. In doing this, clutter in the data model is reduced making it easier to manage and query the attributes without overwhelming the schema.
- Outrigger Dimension: In working with outrigger dimensions, secondary dimensions are linked to primary dimensions such as linking patient data to socio-economic status. This enriches the primary data as it provides deeper insights into how socio-economic factors affect healthcare delivery and outcomes in low-resource communities.
- Transactional Fact Table: Records individual patient visits, capturing details like date, time, and services provided during each outpatient encounter.
- Periodic Snapshot Fact Table: Stores aggregated data over a specific time period, useful for tracking trends and changes in outpatient activities, such as monthly or quarterly summaries of patient visits.
- Accumulating Snapshot Fact Table: Monitors the evolution of a process, such as the stages a patient undergoes during treatment, providing a comprehensive view of the patient’s journey over time.
2.3. Enabling Tools
3. Materials and Methods
4. Results
4.1. Electronic Health Records (EHR)
4.2. The Healthcare Service Delivery Framework
4.3. The Healthcare Data Model
4.4. Enabling Tools
4.4.1. OPD Messaging App
- Setting up a list of patients including their specific details that include but may not be limited to: phone number, appointment date, and medication schedule.
- Using the schedule library, reminders for appointments, and medication adherence are scheduled.
- To send reminders to patients, the twilio messaging service is used.
- A function was written to handle the sending of scheduled reminders to patients.
4.4.2. The OPD Navigation App
- Geofencing Setup. Virtual geofences (geographic boundaries) are created around each of the departments in the medical facility.
- Patient Tracking. GPS or Bluetooth-based tracking is used to monitor patients locations within the facility. The patient’s location can be tracked through a mobile app installed on their smartphone.
- Notifications. When the patient gets to a specific geofence, they receive a notification on their mobile app with information relevant to that department, such as "This is the pharmacy. Move to the reception". Notifications can also include details such as waiting times, instructions, or other important information.
- Shortest Route Guidance. Using indoor mapping and routing algorithms, the app provides the patient with the shortest route to a specified department. The mobile app also offers turn-by-turn directions and updates based on the patient’s current position.
- System Integration. The geofencing system is integrated into the medical facility’s database to keep track of appointments and patient schedules. It can also be configured to provide personalized notifications based on a patient’s schedule.
- Privacy and Security. To ensure that patient location data is collected and stored securely, data anonymization and encryption techniques can be used.
4.5. Discussion
5. Conclusions
- Data warehousing necessitate the availability of fairly efficient infrastructure, availability of healthcare personnel, and patient acceptance and engagement with the technology. Future research focusing on longitudinal studies to assess the long-term impact of data warehousing and patient engagement apps on health outcomes.
- Additionally, exploring partnerships with local governments and non-governmental organizations could facilitate the scalability and sustainability of these initiatives.
Author Contributions
Funding
Data Availability Statement
Conflicts of Interest
Abbreviations
| BI | Business Intelligence |
| EHR | Electronic Health Records |
| ETL | Extraction, Transformation and Loading |
| HCI | Health Center I |
| HCII | Health Center 1I |
| HCIII | Health Center 1II |
| HCIV | Health Center 1V |
| MoH | Ministry of Health |
| NRH | National Referral Hospital |
| NMS | National Medical Stores |
| NPCs | Non-Physician Clinicians |
| OPD | Out Patient Department |
| OLAP | Online Analytical Processing |
| RRH | Regional Referral Hospital |
Appendix A. Data Schema

Appendix B. Reminder App.

Appendix C. Navigation App

References
- Ekholuenetale, M.; Wegbom, A.I.; Tudeme, G.; Onikan, A. Household factors associated with infant and under-five mortality in sub-Saharan Africa countries. IJCCEP 2020, 14, 1–5. [Google Scholar] [CrossRef]
- Bray, F.; Parkin, D.M.; Gnangnon, F.; Tshisimogo, G.; Peko, J.F.; Adoubi, I.; Assefa, M.; Bojang, L.; Awuah, B.; Koulibaly, M.; Buziba, N. Cancer in sub-Saharan Africa in 2020: a review of current estimates of the national burden, data gaps, and future needs. Lancet 2022, 23, 719–28. [Google Scholar] [CrossRef] [PubMed]
- Agw, a B. ; Dagba, G.; Opoku, P.; Amankwa, M.O.; Nyadera, I.N. Sub-Sahara Africa and the COVID-19 pandemic: reflecting on challenges and recovery opportunities. JDS. 2021, 37, 502–24. [Google Scholar]
- Kiross, G.T.; Chojenta, C.; Barker, D.; Loxton, D. The effects of health expenditure on infant mortality in sub-Saharan Africa: evidence from panel data analysis. Health Econ. Rev. 2020; 10, 1–9. [Google Scholar]
- Chewe, M.; Hangoma, P. Drivers of health in sub-Saharan Africa: a dynamic panel analysis. Health Policy OPEN. 2020, 1, 100013. [Google Scholar] [CrossRef] [PubMed]
- Anyangwe, S.C.; Mtonga, C. Inequities in the global health workforce: the greatest impediment to health in sub-Saharan Africa. IJERPH. 2007, 4, 93–100. [Google Scholar] [CrossRef] [PubMed]
- Langnel, Z.; Buracom, P. . Governance, health expenditure and infant mortality in sub-Saharan Africa. Afr. Dev. Rev. 2020, 32, 673–85. [Google Scholar] [CrossRef]
- van Heemskerken, P.; Broekhuizen, H.; Gajewski, J.; Brugha, R.; Bijlmakers, L. . Barriers to surgery performed by non-physician clinicians in sub-Saharan Africa—a scoping review. Hum resour health, 2020; 18, 1–2. [Google Scholar]
- Willcox, M.L.; Peersman, W.; Daou, P.; Diakité, C.; Bajunirwe, F.; Mubangizi, V.; Mahmoud, E.H.; Moosa, S.; Phaladze, N.; Nkomazana, O.; Khogali, M. . Human resources for primary health care in sub-Saharan Africa: progress or stagnation? Hum resour health bf 2015, 13, 1. [Google Scholar] [CrossRef] [PubMed]
- van Heemskerken, P.; Broekhuizen, H.; Gajewski, J.; Brugha, R.; Bijlmakers, L. Barriers to surgery performed by non-physician clinicians in sub-Saharan Africa—a scoping review. Hum resour health. 2020, 18, 1–2. [Google Scholar] [CrossRef] [PubMed]
- Muñoz, L.; Mazon, J.N.; Trujillo, J. ETL process modeling conceptual for data warehouses: a systematic mapping study. IEEE Lat. Am. Trans. 2011, 9, 358–363. [Google Scholar]
- Wyllie, D.; Davies, J. Role of data warehousing in healthcare epidemiology. JHI, 2015; 89, 267–270. [Google Scholar]
- Gavrilov, G.; Vlahu-Gjorgievska, E.; Trajkovik, V. Healthcare data warehouse system supporting cross-border interoperability. J. Health Inform. 2020, 26, 1321–32. [Google Scholar] [CrossRef] [PubMed]
- Tang, C.; Wang, H.; Liu, J.; Liu, C. A design for AIS data warehouse of traffic flow. In Proceedings of the 4th International Conference on Transportation Information and Safety (ICTIS), Banff, AB, Canada, 8 Aug 2017; 895–898. [Google Scholar]
- Ponniah, P. Data warehousing fundamentals: a comprehensive guide for IT professionals John Wiley & Sons; New York, USA, 2004; pp. 20–23.
- El Aissi, M.E.; Benjelloun, S.; Loukili, Y.; Lakhrissi, Y.; Boushaki, A.E.; Chougrad, H.; Elhaj Ben Ali, S. Data lake versus data warehouse architecture: A comparative study. In Proceedings of the 6th International Conference on Wireless Technologies, Embedded, and Intelligent Systems, Singapore, India, 22 July 2021; pp. 201–210. [Google Scholar]
- Kimball, R.; Ross, M. The data warehouse toolkit: the complete guide to dimensional modeling, 2nd ed., John Wiley & Sons: New York, USA; 6–14.
- Oliva, S.Z.; Felipe, J.C. . Optimizing public healthcare management through a data warehousing analytical framework. IFAC-PapersOnLine, 2018; 51, 407–412. [Google Scholar]
- Soliman, M.A.; Antova, L.; Sugiyama, M.; Duller, M.; Aleyasen, A.; Mitra, G.; Abdelhamid, E.; Morcos, M.; Gage, M.; Korablev, D.; Waas, F.M. A framework for emulating database operations in cloud data warehouses . In Proceedings of the 2020 ACM SIGMOD International Conference on Management of Data, 11 June 2020; pp. 1447–1461. [Google Scholar]
- Hai, R.; Koutras, C.; Quix, C.; Jarke, M. Data lakes: A survey of functions and systems. IEEE Trans. Knowl. Data Eng. 2023, 35, 12571–12590. [Google Scholar] [CrossRef]
- Khine, P.P.; Wang, Z.S. Data lake: a new ideology in big data era . In Proceeding of the ITM web of conferences, Beijing, China, 2 February 2018. [Google Scholar]
- Kimball, R.; Ross, M. The data warehouse toolkit: the complete guide to dimensional modeling, 2nd ed., John Wiley & Sons: New York, NY, USA; pp. 16–26.
- Bojičić, I.; Marjanović, Z.; Turajlić, N.; Petrović, M.; Vučković, M.; Jovanović, V. A comparative analysis of data warehouse data models. In Proceeding of the International Conference on Computers Communications and Control (ICCCC), Oradea, Romania, 10 May 2016; pp. 151–159. [Google Scholar]
- Kimball, R.; Ross, M. The data warehouse toolkit: the complete guide to dimensional modeling, 3rd ed., John Wiley & Sons: New Indianapolis, Indiana.
- Viqarunnisa, P.; Laksmiwati, H.; Azizah, F.N. Generic data model pattern for data warehouse. In Proceedings of the 2011 International Conference on Electrical Engineering and Informatics, Bandung, Indonesia, 17 July 2011; pp. 1–8. [Google Scholar]
- Kao, C.K.; Liebovitz, D.M. . Consumer mobile health apps: current state, barriers, and future directions. PM&R, 2017; 9, 106–115. [Google Scholar]
- Murphy, S.N.; Avillach, P.; Bellazzi, R.; Phillips, L.; Gabetta, M.; Eran, A.; McDuffie, M.T.; Kohane, I.S. . Combining clinical and genomics queries using i2b2–Three methods. PloS one, 2017; 12, 5317760. [Google Scholar]
- Naeem, M.; Jamal, T.; Diaz-Martinez, J.; Butt, S.A.; Montesano, N.; Tariq, M.I.; De-la-Hoz-Franco, E.; De-La-Hoz-Valdiris, E.. Trends and future perspective challenges in big data. In Advances in Intelligent Data Analysis and Applications: In Proceedings of the Sixth Euro-China Conference on Intelligent Data Analysis and Applications, Arad, Romania, 15–18 October 2019; pp. 309–325.
- Shahid, A.; Nguyen, T.A.; Kechadi, M.T. Big data warehouse for healthcare-sensitive data applications. Sensors 2021, 21, 2353. [Google Scholar] [CrossRef] [PubMed]
- Berndt, D.J.; Fisher, J.W.; Hevner, A.R.; Studnicki, J. Healthcare data warehousing and quality assurance. Computer, 2001; 34, 56–65. [Google Scholar]


| Attribute | Data warehousing | Data lakes |
|---|---|---|
| Data structure | Employs a defined schema | Stores structured, |
| semi-structured, | ||
| and unstructured data | ||
| Data quality | High, due to rigorous | Variable, raw data storage |
| ETL processes | can lead to quality issues | |
| Query | Optimized for fast query | Can be slower for complex |
| Performance | performance and reporting | queries |
| Security | Robust security measures | Security can be complex |
| and access controls | due to diverse data formats | |
| Analytics | Advanced analytics and BI | Suitable for big data |
| tools for structured data | analytics and machine | |
| learning | ||
| Integration | Comprises of well-integrated, | Can integrate diverse |
| consistent data from multiple | data but requires | |
| sources | significant effort | |
| Governance | Strong data governance and | More challenging to enforce |
| compliance capabilities | governance and compliance |
| Serial No. | Categorical data | Details |
|---|---|---|
| 1 | Patient Registration | Personal details (name, age, gender) |
| Form | Contact information (address, phone number) | |
| Identification details (national ID, passport) | ||
| Next of kin information | ||
| 2 | Medical History | Previous illnesses and surgeries |
| Form | Allergies and medication history | |
| Family medical history | ||
| Immunization records | ||
| 3 | Outpatient Visit | Date and time of visit |
| Record | Chief complaints or reason for the visit | |
| Vital signs (blood pressure, temperature) | ||
| Preliminary diagnosis and treatment provided | ||
| 4 | Prescription and | Medication details (name, dosage, frequency) |
| Medication Record | Prescribing healthcare provider | |
| Instructions for use | ||
| Duration of the prescription | ||
| 5 | Laboratory and Diagnostic | Date and type of tests conducted |
| Test Results | Results of tests, imaging, or other diagnostics | |
| Interpretation of results | ||
| Follow-up recommendations | ||
| 6 | Follow-up Appointment | Date and time of scheduled follow-up |
| Record | Purpose of the follow-up | |
| Recommended actions or treatments | ||
| Any additional instructions for the patient | ||
| 7 | Billing and Payment | Details of services rendered |
| Records | Cost of services | |
| Payment method and amount paid | ||
| Outstanding balances if any | ||
| 8 | Consent Forms | Signed consent for treatments or procedures |
| Acknowledgment of privacy practices | ||
| Consent for release of medical information | ||
| Other relevant consent forms | ||
| 9 | Referral and Consultation | Details of referred specialists |
| Forms | Reason for referral | |
| Consultation notes and recommendations | ||
| Follow-up plans post-consultation | ||
| 10 | Quality Improvement and | Patient feedback on services received |
| Feedback Forms | Suggestions for improvement | |
| Incidents or complaints | ||
| Staff performance assessments |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2024 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (http://creativecommons.org/licenses/by/4.0/).