Online Clinic Software Prototype
We have developed a complete UI / UX part and a Clickable Software Prototype that End Users used during usability testing before starting development
Process
Before starting software programming, we went through the preliminary preparation stage. You can read more about its advantages on the Clickable Software Prototype page
Part 1
Requirements
Part 2
UI / UX
Part 3
Software Design
Requirements
Properly-collected requirements are crucial to the quality of the technical implementation of the software. It prevents excess spending on Customer Improvements, Reworks, Changes, and Refactoring after the Early Delivery stage.
This includes:
System & Functional
- Modules & Detailed Features Description
- Product Perspective
- Assumptions, Dependencies, and System Constraints
- Sequence, Data Flow, and State-Transition Diagrams
- Classes / Objects
Non-Functional
- Key Technical Indicators
- Technology Stack Consideration
- Security
- Performance
- Manageability / Maintainability
Compliance-Related
- GDPR, CCPA / CPRA, ISO / IEC 27001
- PCI DSS
- HIPAA / HITECH, PIPEDA
- C-CDA, EUPS / epSOS, HL7 / FHIR
UI / UX: Overview
We divided all the tasks into two types of activities: UX Design and UI Design with all stages from start to finish
User Experience
User Persona
It helps us gain user perspective and develop empathy for their needs and desires. We created User Personas for different roles: Healthcare consumers (Patients), Healthcare Providers (Doctors and other positions), Clinic Admins
Customer Jorney Map
CJM helps to understand the user more, see their unmet needs, and increase the quality of user experience and customer retention
Design System
Color Scheme
The UI Set of the product and the Color Scheme are prepared within Web Content Accessibility Guidelines (WCAG) 2.0, 2.1 and some of relevant items from Section 508 of the Rehabilitation Act
Typography
Carefully chosen and processed Typography provides a correct hierarchy and prioritization of the content. For this particular software, we selected the Major Second Type Scale scope
Form Elements 1
We use native libraries like Angular Material and process all states (active, filled, error, etc.) in the Design System. It ensures consistency across the software and prevents the developers from developing everything manually, thus saving time and money later on
Form Elements 2
Icons
Buttons
Menu
Tabs / Labels / Sliders /Progress Bars
Pop-Ups and Alerts
Charts and Infographics
Illustrations
Grids
Сorrect design of widgets based on grids allows applying general patterns and layout rules in different page structures. This way, each element has its place, reproduced in other areas of the system, providing consistency and responsiveness for different devices and screen resolutions
Flexible Design Components
A component-based Design System allows us to make quick product-wide changes and ensure that all elements are consistent across the software
User Flows
Many reworks, changes, and user experience improvements come after the early delivery stage. If you only focus on success user flows, people who use the product will encounter blockers and unfinished elements that lead to an incorrect perception of the software and the ways to use it.
That’s why we cover:
Success User Flows
Alternative User Flows
Exeption User Flows
Edge Cases
User Flow Examples
Here are a few examples of how we process User Flows
Clickable Software Prototype
Interactive Software Prototype allows testing user interface and user experience and see potential flaws saving money before software development starts
High-Fidelity Wireframes
High-Fidelity Wireframes are important to process all UI components, combine them, and properly work out the User Interface to ensure consistency and structural integrity across the software
Software Design
Inadequate processing and planning of architecture, server infrastructure, and other aspects at this step will significantly weaken the scalability and maintainability of the software, which will lead to revisions in the future, spending more time and money than necessary.
That is why we cover all the required elements for this stage:
Functional Decomposition
Product Architecture
Database Architecture
Modules Structure
Client-Server Architecture
Third-party Service APIs
Technology Stack Consideration
Key Technical Requirements
Entities & Attributes
Client Reviews
After speaking with Adrian (Founder & CEO), we knew they understood what we wanted and how to make it because they’d done it before. They’re easy to work with because they anticipate our needs. Overall, they’ve been outstandingly professional.
Mental Health Counseling Platform
Operations Manager
SEVEN produces on-target deliverables according to complex requirements. The product they developed is visually appealing and well-organized. SEVEN demonstrated that they have a large infrastructure. They have a lot of people on their team who are professional and know their jobs very well.
Health Supplement Provider
Former COO
I could go to them at any point, and they were always responsive and available to help us.I think SEVEN offers a very good value for money. They delivered a quality solution, it was very well executed, and it worked as requested. Project management is a great strength for them.
Medical Care App
CEO