Healthc Inform Res Search

CLOSE


Healthc Inform Res > Volume 31(1); 2025 > Article
Molon: Extreme Prototyping for a Community Health Worker Medical Application

Abstract

Objectives

Noncommunicable diseases (NCDs) pose a significant burden, especially in low- and middle-income countries such as the Philippines. To tackle this issue, the Department of Health launched the Philippine Package of Essential Non-Communicable Disease Interventions (PhilPEN), which includes the use of the Noncommunicable Disease Risk Assessment Form. However, healthcare workers have encountered difficulties due to the form’s complexity and the lengthy process required. This study aimed to create a mobile medical app for community health workers by adapting the PhilPEN Noncommunicable Disease Risk Assessment Form using the extreme prototyping framework. The focus was on simplifying data collection and improving the usability of health technology solutions.

Methods

The study employed a qualitative research methodology, which included key informant interviews, linguistic validation, and cognitive debriefing. The extreme prototyping framework was utilized for app development, comprising static prototype, dynamic prototype, and service implementation phases. The app was developed with HTML5, CSS3, JavaScript, and Apache Cordova, adhering to World Health Organization (WHO) guidelines and PhilHealth Circular.

Results

The development process involved three prototype cycles, each consisting of multiple mini-cycles of feedback, system design, coding, and testing. Version 1.xx was aligned with WHO guidelines, Version 2.xx integrated the Department of Health NCD Risk Assessment Form, and Version 3.xx adapted to the updated form with expanded requirements.

Conclusions

The extreme prototyping framework was effectively applied in the development of a medical mobile app, facilitating the integration of health science and information technology. Future research should continue to validate the effectiveness of this approach and identify specific nuances related to health science applications.

I. Introduction

Noncommunicable diseases (NCDs), also known as chronic diseases, represent a major global health challenge, responsible for two-thirds of all deaths worldwide. These diseases place a particularly heavy burden on low- and middle-income countries (LMICs), including the Philippines. In this country, cardiovascular and cerebrovascular diseases are the primary causes of death. The most frequently reimbursed procedures by the Philippine Health Insurance Corporation (PhilHealth) pertain to complications arising from these NCDs. Economically, the impact is substantial, with losses amounting to 4.8% of the gross domestic product in 2017 [13].
To address this concern, the Department of Health (DOH) implemented the Philippine Package of Essential Non-Communicable Disease Interventions (PhilPEN) through Administrative Order (AO) No. 2012–0029. This initiative, adapted from the World Health Organization (WHO) guidelines, targets the management of NCDs in low-resource settings. The PhilPEN intervention protocol mandates that healthcare workers and volunteers use the Noncommunicable Disease Risk Assessment Form to gather patient data, evaluate risk factors, stratify cardiovascular risk, and, if necessary, refer patients for specialized consultation [37]. Despite these efforts, the program’s adoption has been sluggish, hindered by several factors, including the cumbersome nature of the multiple forms, the time-consuming process, and the overwhelming patient volume [8].
To address these challenges, information technology (IT) solutions, particularly mobile applications (apps), are emerging as potential aids in healthcare delivery, especially in LMICs such as the Philippines. This country not only has a growing mobile market but also a rising consumer interest in mobile apps [917]. However, the development of medical mobile apps, which integrate IT and health science disciplines, faces challenges due to the absence of clearly established frameworks (Table 1). This study aims to explore an alternative method for collecting NCD data using a mobile app. This app is based on the PhilPEN Protocol and was developed through extreme prototyping, an iterative software development framework that is well-suited to the unique requirements of health science [1821].

II. Case Description

The study utilized the software prototyping model (Figure 1) as the framework for developing a mobile health app designed to replicate the Noncommunicable Disease Risk Assessment Form. This model divides a large project into smaller, manageable segments, facilitating modifications during development, reducing both risk and cost, and incorporating end-user input for immediate feedback. This approach significantly enhances the likelihood of user acceptance [18,22,23]. The conceptual framework was derived from Komatineni’s “Reshaping IT Project Delivery through Extreme Prototyping” (Figure 2). It is structured into three phases: the static prototype-extended static prototype phase, the dynamic prototype (also known as the extreme prototype or user-interface) phase, and the service implementation phase [21].
The study employed a qualitative research methodology, which included several key components. A semi-structured interview was conducted with the Muntinlupa City Health Officer (CHO) to establish the foundational concepts for the mobile medical app. Linguistic validation was carried out at the Sentro ng Wikang Filipino (SWF) of UP Manila and UP Diliman. Additionally, cognitive debriefing was performed with the head community health worker of the barangay, who met specific criteria: (1) completion of training for NCD intervention, (2) utilization of the NCD Risk Assessment Form, (3) proficiency in using a smartphone and web browser, and (4) provision of written consent. The mobile medical app was designed and developed using HTML5, CSS3, and JavaScript—essential technologies for creating web content. It was subsequently ported to Android using Apache Cordova, a framework that enables the development of cross-platform native applications using web technologies [2427].
The static prototype was designed using HTML5 and structured with CSS3, followed by the integration of a logical data model to enhance the prototype. The dynamic prototype required recoding and adjustments to the user interface, along with the implementation of field validation, computation functions, and a functional risk stratification routine.
The development of the PhilPEN Risk Stratification mobile medical app involved three prototype cycles. Each cycle included multiple mini-cycles consisting of feedback/requirement definition, system design, coding/testing, and then returning to feedback/requirement definition (Figure 3). Version 1.xx of the app was based on the WHO Prevention of Cardiovascular Disease 2007 [4] and PhilHealth Circular No.0020 s. 2013 24 [3] (Supplement A). This version was designed assuming the absence of facilities for necessary laboratory work and anticipated only 128 possible outcomes. A static prototype of this version was presented to the CHO, who noted the absence of laboratory data entry points. Subsequently, the DOH NCD Risk Assessment Form, translated into Filipino and adapted to include local nuances, was provided.
Version 2.xx of the app was developed based on the information and resources provided by the CHO. It supports two types of patient data entries: those without laboratory values, which have 128 possible outcomes, and those with laboratory results, featuring 640 possible outcomes (Supplement B). The app features a local language interface to enhance acceptance among the target user population. Concurrently, an extended static prototype and a dynamic prototype were developed. This process included recoding and adjusting the user interface, implementing field validation and computation functions, and establishing a functional risk stratification routine with 640 possible outcomes.
Upon presentation of Version 2.xx to the CHO, the DOH issued an updated NCD Risk Assessment Form (Supplement C). This new form requires more patient data and places a strong emphasis on risk screening, documenting associated factors, and streamlining the process for physicians to stratify patients’ risk profiles. Consequently, these expanded requirements necessitated an update to the app.
Version 3.xx of the app was developed based on feedback from the updated NCD Risk Assessment Form. During the development process, code refactoring and bug fixes that were identified internally were not included in the reported results. [1]

III. Discussion

This study aimed to apply design theory to the development of a mobile app intended to support data collection for healthcare delivery. Specifically, it focused on creating a mobile medical app for community health workers based on the PhilPEN NCD Risk Assessment Form, utilizing extreme prototyping. The analysis suggests that the extreme prototyping framework is not only applicable to general mobile app development but also effectively bridges the gap between health science and information technology in the context of medical mobile apps.
The prototyping framework served development well, primarily by clarifying previously ambiguous objectives. Initially, both the CHO and the head physician at the health center supported the idea of an IT-based solution. However, they were unable to provide specific details on its implementation beyond presenting the PhilPEN NCD Risk Assessment Form. Prototyping can begin with just a rudimentary understanding of the core business issue [18,23,28], enabling the creation of a preliminary system, as demonstrated by the extended static prototype for the PhilPEN mobile medical app (Figure 4).
Breaking down the medical mobile app into smaller components using the prototyping methodology made development more manageable, given the limited resources available [18,19,28]. The use of extreme prototyping further streamlined the process by enabling parallel progression; each component could independently undergo cycles of feedback, requirement definition, system design, and coding/testing. Crucially, end-user involvement, a key aspect of the prototyping methodology, enhanced the development process by securing stakeholder buy-in and facilitating open communication throughout the iteration cycles [18,28].
The level of interaction facilitated addressing the challenges associated with the prototyping approach, including the informal approval process, the risk of inadequate checks and balances, and the possibility of changing requirements [18]. The foundation of this approach was strengthened by WHO initiatives, complemented by insights from the CHO regarding DOH nuances, which enabled the developer to manage expectations and address potential shortcomings effectively. The hypothesized benefits of the prototype, such as reduced inherent project risks and costs, appear to have been realized. This success can be attributed to the cooperation among the involved parties and their early participation, which contributed significantly to the potential successful conclusion of the project.
The significant value of this methodology in the development of medical mobile apps may explain its popularity among researchers like Prabhakaran et al. [29] and Rudin et al. [30] when creating their own applications. Although their discussions primarily concentrated on the health science aspect, the methodology’s influence is evident. This formal documentation of prototyping in the development of mobile medical apps likely provides the first detailed insight into their creation process. It bridges the gap between conceptualization and actualization in mobile medical application development, offering a repeatable methodology for future innovation and design.
While the development process was limited yet relatively complete, the effectiveness of this approach in integrating two distinct disciplines can only be fully validated through further research. The next logical step involves ‘barangay’ health workers using the app with actual patients to validate its accurate representation of the NCD Risk Assessment Form, assess its usability in their work environment, and refine it through additional prototype iterations. Future research on mobile medical app development using extreme prototyping could confirm the utility and advantages of applying system development methodologies in this emerging field. The prototyping process, based on scientific principles, should be replicable for those interested in developing similar applications. These future studies could also clarify which processes are truly applicable to health science and pinpoint any unique nuances that need consideration. Overall, this study has established a foundation for a systematic and evidence-based approach to developing medical mobile apps, effectively bridging the gap between conceptualization and actualization in this interdisciplinary field.

Notes

Conflict of Interest

No potential conflict of interest relevant to this article was reported.

Acknowledgments

This research was submitted in partial fulfillment of the requirements for the Degree of Master of Health Informatics at the University of the Philippines College of Medicine.
The author would like to show gratitude to Dr. Alvin Marcelo for being first mentor and informatics pioneer, Dr. Maria Teresa Tuliao and Dr. Neal Jason Argana of the city health office for their oversight, Ms. Isis Alva for the administrative support, Dr. Tan and the thesis panel for their guidance, and fellow graduate students, Philip John Sales, Isidor Cardenas, and Roy Octaviano Dahildahil for unselfishly lending their respective works for reference.

Supplementary Materials

Supplementary materials can be found via https://doi.org/10.4258/hir.2025.31.1.88.

Figure 1
Prototyping system development methodology.
hir-2025-31-1-88f1.jpg
Figure 2
Extreme prototyping framework.
hir-2025-31-1-88f2.jpg
Figure 3
Methodology. CHO: city health officer, CHW: community health worker.
hir-2025-31-1-88f3.jpg
Figure 4
PhilPEN mobile medical application English screenshots: (A) Loading screen, (B) Main screen, (C) Language select, (D) Modifiable Risk Factors section, (E) Medical History section, (F) Measurements and Lab section, and (G) Risk Profile section.
hir-2025-31-1-88f4.jpg
Table 1
Summary of system development frameworks
Framework Waterfall Iterative Spiral Prototyping
Brief description Aka “Linear Sequential Life Cycle Model”
Each separate phase is fixed and must be completed before the next phase can begin.
Illustrates the software development process in a linear sequential flow wherein the phases do not overlap.
Aka “Incremental Model”
Basic idea: develop a system through repeated cycles (iterative) and in smaller portions (incremental).
Starts with a simple implementation.
Gradually enhances the evolving versions until system completion.
More than one iteration may be in progress at the same time.
Development process with a very high emphasis on risk analysis.
Completion of spirals.
At the end of each spiral is evaluation and risk analysis that (1) includes identifying, estimating, and monitoring the feasibility and management risks, and (2) takes into consideration customer feedback.
Aka “Evolutionary Process Model”
Iterative process of building a model of a system through incomplete versions of the software program being developed.
Prototype is a working model of the software with some limited functionality and typically runs through a quick design phase.
Advantages Very simple to understand and use.
Ideal for supporting less experienced project teams and project managers.
Orderly sequence of development steps and strict controls ensure the quality, reliability, and maintainability of the developed software.
Contributes to a measurable progress of development and demonstrates a conservation of resources which may benefit resource-constrained low- to middle-income settings.
Greatest advantage is the creation of a working model very early.
Finding functional or design issues early on enables early corrective measures, which reduces costs.
Benefits not limited to the early stages: a working model with its product issue identification is delivered at almost every iteration.
Management, testing, and debugging relatively easy, due to the smaller scope implemented.
Risk analysis lends itself well to healthcare in that it seeks to avoid or mitigate potential hazards.
Allows elements of the product to be added in, when they become known.
Assures no conflict with previous requirements and design.
Consistent with approaches that have multiple software builds and releases, allowing orderly transition to a maintenance activity.
Early user involvement.
Only a basic definition requirement necessary.
Enables designers to understand fundamental requirements at an early stage.
Increased user involvement even before its implementation.
Quicker user feedback.
Issues detected early, reducing time and cost.
Disadvantages Sequential steps are inflexible and cumbersome due to the same structure and tight controls.
Inadvertently promotes a gap between users and developers.
Projects tend to progress forward, allowing little to no room for use of iteration, reducing its manageability.
Depends upon early identification and specification of requirements, which contrasts with the shifting nature of healthcare.
There may be inconsistencies, missing system components, and unexpected development needs that may arise in the later stages.
Problems are often not discovered until system testing, which itself cannot be done until the system is almost fully coded; these problems are difficult to address.
The late realization of or response to critical changes may offset the early resource conservation.
Model applicable only to large and bulky development projects with defined requirements.
More resources may be required to initiate a project and to conduct parallel development.
Although cost of change is less (compared to the Waterfall Model), it is not very suitable for changing requirements.
System architecture or design issues may arise because not all requirements are gathered at the beginning of the entire life cycle, so the identification of prerequisites is critical.
This requirement definition is difficult in the healthcare space.
Very strict management to complete.
Risk of running the spiral in an indefinite loop.
Discipline of change and the extent of taking change requests is very important.
Not suitable for small or lowrisk projects and could actually be quite expensive for small projects.
Risk of insufficient requirement analysis.
User confusion between prototypes and actual systems.
May increase the complexity of the system.
Effort invested in building prototypes may be too much if it is not monitored properly.

References

1. World Health Organization. Global status report on noncommunicable diseases 2014. Geneva, Switzerland: World Health Organization; 2014.

2. World Health Organization. United Nations Development Programme Prevention and control of noncommunicable diseases in the Philippines. Geneva, Switzerland: World Health Organization; 2019.

3. Philippine Health Insurance Corporation. Adoption of the Philippine package of essential non-communicable disease (NCD) Interventions (PHIL PEN) in the Implementation of PhilHealth’s primary care benefit package [Internet]. Manila, Philippine: Department of Health; 2013 [cited at 2024 Dec 20]. Available from: https://www.philhealth.gov.ph/circulars/2013/circ20_2013.pdf

4. World Health Organization. Prevention of cardiovascular disease: guidelines for assessment and management of cardiovascular risk. Geneva, Switzerland: World Health Organization; 2007.

5. Ghorpade AG, Shrivastava SR, Kar SS, Sarkar S, Majgi SM, Roy G. Estimation of the cardiovascular risk using World Health Organization/International Society of Hypertension (WHO/ISH) risk prediction charts in a rural population of South India. Int J Health Policy Manag 2015;4(8):531-6. https://doi.org/10.15171/ijhpm.2015.88
crossref pmid pmc
6. Raghu A, Praveen D, Peiris D, Tarassenko L, Clifford G. Implications of Cardiovascular Disease Risk Assessment Using the WHO/ISH Risk Prediction Charts in Rural India. PLoS One 2015;10(8):e0133618. https://doi.org/10.1371/journal.pone.0133618
crossref pmid pmc
7. Dugee O, Palam E, Dorjsuren B, Mahal A. Who is bearing the financial burden of non-communicable diseases in Mongolia? J Glob Health 2018;8(1):010415. https://doi.org/10.7189/jogh.08.010415
crossref pmid pmc
8. Engelgau MM, Rosenthal JP, Newsome BJ, Price L, Belis D, Mensah GA. Noncommunicable diseases in low-and middle-income countries: a strategic approach to develop a global implementation research workforce. Glob Heart 2018;13(2):131-7. https://doi.org/10.1016/j.gheart.2018.05.001
crossref pmid
9. Kallander K, Tibenderana JK, Akpogheneta OJ, Strachan DL, Hill Z, ten Asbroek AH, et al. Mobile health (mHealth) approaches and lessons for increased performance and retention of community health workers in low- and middle-income countries: a review. J Med Internet Res 2013;15(1):e17. https://doi.org/10.2196/jmir.2130
crossref pmid pmc
10. Goldstein P. Report: Global smartphone penetration to jump 25% in 2014, led by Asia-Pacific [Internet]. Washington (DC): Fierce Network; 2014 [cited at 2024 Nov 11]. Available from: https://www.fiercewireless.com/wireless/report-global-smartphone-penetration-to-jump-25-2014-led-by-asia-pacific

11. Stryjak J, Sharma A, Hatt T. Country overview: Philippines - growth through innovation [Internet]. London, UK: GSMA Intelligence; 2014 [cited at 2024 Nov 11]. Available from: https://data.gsmaintelligence.com/research/research/research-2014/country-overview-philippines-growth-through-innovation

12. US Food and Drug Administration. Policy for device software functions and mobile medical applications [Internet]. Rockville (MD): US Food and Drug Administration; 2022 [cited at 2024 Nov 11]. Available from: https://www.fda.gov/regulatory-information/search-fda-guidance-documents/policy-device-software-functions-and-mobile-medical-applications

13. Censi F, Mattei E, Triventi M, Calcagnini G. Regulatory frameworks for mobile medical applications. Expert Rev Med Devices 2015;12(3):273-8. https://doi.org/10.1586/17434440.2015.1007125
crossref pmid
14. Lewis TL, Wyatt JC. mHealth and mobile medical apps: a framework to assess risk and promote safer use. J Med Internet Res 2014;16(9):e210. https://doi.org/10.2196/jmir.3133
crossref pmid pmc
15. Aungst TD. Medical applications for pharmacists using mobile devices. Ann Pharmacother 2013;47(7–8):1088-95. https://doi.org/10.1345/aph.1S035
crossref pmid
16. Buijink AW, Visser BJ, Marshall L. Medical apps for smartphones: lack of evidence undermines quality and safety. Evid Based Med 2013;18(3):90-2. https://doi.org/10.1136/eb-2012-100885
crossref pmid
17. Nacinovich M. Defining mHealth. J Commun Healthc 2011;4(1):1-3. https://doi.org/10.1179/175380611X12950033990296
crossref
18. Centers for Medicare and Medicaid Services. Selecting a development approach [Internet]. Baltimore (MD): Centers for Medicare and Medicaid Services; 2008 [cited at 2024 Nov 11]. Available from: https://www.academia.edu/13239574/SELECTING_A_DEVELOPMENT_APPROACH

19. McClendon C, Regot L, Akers G. The analysis and prototyping of effective graphical user interfaces [Internet]. St Louis (MO): University of Missouri-St. Louis; 2012 [cited at 2024 Nov 11]. Available from: https://www.umsl.edu/~sauterv/analysis/prototyping/intro.html

20. Davis AM. Operational prototyping: a new development approach. IEEE Softw 1992;9(5):70-8. https://doi.org/10.1109/52.156899
crossref
21. Komatineni S. Reshaping IT project delivery through extreme prototyping [Internet]. [place unknown]: satyakomatineni.com; 2006 [cited at 2019 Nov 11]. Available from: https://satyakomatineni.com/akc/display?url=displaynoteimpurl&ownerUserId=satya&reportId=1878

22. Rather M, Bhatnagar V. A comparative study of software development life cycle models. Int J Appl Innov Eng Manag 2015;4(10):23-9.

23. Crinnion J. Evolutionary systems development: a practical guide to the use of prototyping within a structured systems methodology. New York (NY): Plenum Press; 1991.

24. Moncur MG. JavaScript in 24 hours. Indianapolis (IN): Sams; 2007.

25. Myers M. A smarter way to learn JavaScript. North Charleston (SC): CreateSpace; 2013.

26. Myers M. A smarter way to learn HTML & CSS: learn it faster: remember it longer. North Charleston (SC): CreateSpace; 2015.

27. Wargo J. Apache Cordova 4 Programming. Boston (MA): Addison-Wesley Longman; 2015.

28. Overmyer SP. Validating system and software requirements: extending the Davis-Jordan requirements metamodel to the ‘user’s view’. Proceedings of the 2nd International Workshop on Rapid System Prototyping; 1991 Jun 11–13. Research Triangle Park NC, USA; p. 149-50. https://doi.org/10.1109/IWRSP.1991.218616
crossref
29. Prabhakaran D, Jha D, Prieto-Merino D, Roy A, Singh K, Ajay VS, et al. Effectiveness of an mHealth-based electronic decision support system for integrated management of chronic conditions in primary care: the mWellcare cluster-randomized controlled trial. Circulation 2019;139(3):380-91. https://doi.org/10.1161/CIRCULATIONAHA.118.038192
crossref pmid
30. Rudin RS, Fanta CH, Predmore Z, Kron K, Edelen MO, Landman AB, et al. Core components for a clinically integrated mHealth app for asthma symptom monitoring. Appl Clin Inform 2017;8(4):1031-43. https://doi.org/10.4338/ACI-2017-06-RA-0096
crossref pmid pmc
TOOLS
Share :
Facebook Twitter Linked In Google+ Line it
METRICS Graph View
  • 0 Crossref
  •     Scopus
  • 297 View
  • 24 Download
Related articles in Healthc Inform Res


ABOUT
ARTICLE CATEGORY

Browse all articles >

BROWSE ARTICLES
FOR CONTRIBUTORS
Editorial Office
1618 Kyungheegung Achim Bldg 3, 34, Sajik-ro 8-gil, Jongno-gu, Seoul 03174, Korea
Tel: +82-2-733-7637, +82-2-734-7637    E-mail: hir@kosmi.org                

Copyright © 2025 by Korean Society of Medical Informatics.

Developed in M2community

Close layer
prev next