Creation of a Functional Prototype to Enhance Patient Care

Development of a functional concept

We kicked off the project by conducting Product Discovery workshops, leveraging Design Thinking and Event Storming methodologies to deeply understand both user requirements and the flow of business processes. By applying these techniques, the business and technical analysis becomes more comprehensive, ultimately resulting in solutions that are better aligned with the real needs of end users.

• During our Design Thinking workshops, we collaborated closely with the client’s stakeholders to discuss the gathered insights—focusing specifically on the end-user’s perspective. We believe that a deep understanding of the user’s needs is essential for building an innovative solution that truly addresses their challenges. In this phase, we validated the initial assumptions from our earlier needs analysis to define the project’s core requirements and constraints.
• We also focused on thoroughly analyzing and modeling complex business processes. We used domain-specific tools to identify key events within the business context and to understand how these events impact the overall system. This allowed us to develop an initial functional concept for the product.

In the subsequent stages, we delivered the following:

• Three main UI mockups (screen wireframes), beginning with the design of a wizard that includes templates for various registers. The client placed strong emphasis on the front-end, aiming to ensure the application would be user-friendly, intuitive, and flexible. Ultimately, the goal is to create a system that can be easily configured by non-technical users without requiring software development expertise.
• A SWOT analysis of selected technologies to recommend the most suitable tech stack for the client’s needs. Our key focus was on selecting market-leading technologies that are both maintainable and scalable.

• We conducted a cloud infrastructure analysis, as the system will handle a large volume of data collected from various medical and non-medical entities. However, due to data security requirements, sensitive information must remain on the organization’s internal servers at the hospital level. At higher levels—national or European—data will be anonymized to ensure compliance and privacy.
• We also developed a project roadmap, which included a detailed Work Breakdown Structure (WBS) to define the project scope. We outlined the initial development steps, created a full project timeline, and identified key milestones using Gantt charts.

As a result of these workshops, we developed and aligned a common glossary of terms, documented each system module along with their interdependencies, identified user roles and personas, and outlined both functional and non-functional requirements—including considerations such as performance, security, usability, and accessibility. We also created an initial draft of the system architecture.