Building the next generation web-based Aerospace Medicine Safety Information System (AMSIS).
A platform that guides over 4 million external and internal users through medical certification and drug test protocol for air safety.
Requirement Analysis User Research Wireframing Interactive Prototyping Usability Testing
Designers Product Owners Developers
2019 - Present
FAA (client) provided over 2,000 system and business requirements. Our team analyzed and decomposed the requirements into design and technical specifications for the AMSIS dev teams. To further understand the end-users' needs, the UX team conducted ethnographic studies for a week at the FAA (CAMI) headquarters in Oklahoma City. To continue the stakeholder and end-user feedback loop, the UX team organizes and facilitates monthly engagement workshops to validate business processes and screens. Below is a snapshot of user flows and workflows co-created with SMEs during one of the user engagement events.
There are over 47 user-roles that fall under one of two main AMSIS portals, Drug Abatement and Medical. In place of traditional personas - the team uses the 'Jobs-to-be-done' framework. Where we analyze each specified role and define their situations and motivations. This is an important step to take in order to develop accurate user-flows and screen interactions.
Employers, Schedulers, Inspectors, and Investigators amongst others manage DA registrations and conduct annual reviews for regulation reinforcement
Airmen (pilots / air traffic controllers), Doctors, Application Examiners, and Medical supervisors, handle all medical certification and clearance protocol.
Due to FAA brand and visual specifications. The AMSIS team architects guided us on determining the use of PrimeNG as the main UI component library. This gives the UX team some visual and functional constraints which allow us to determine quickly what is feasible from an interaction perspective.
The overall process of user research and screen validation is a reoccurring activity. The static wireframes and interactive prototypes that are produced during this time are used to guide business analysts when creating the backlog user stories. It also provides a visual guide for dev and testing teams. As a UX member, we are integrated into the SCRUM team to explain UI interaction decisions and observe functional constraints that may influence future screen designs.
Creating these screens/prototypes helps expedite the agile development process and has allowed for the team to continue to create visually consistent UI and a 508 compliant web-app.