Public-health design project
Mon, Dec 7, 2026 · Week 16 · Principles of Biomedical Technology (Principles of Biomedical Science)
Today's goal: Student teams design a usable public-health communication app for a surge scenario.
This is a model of the work you should turn in today. Use it to check your own: match the structure and the level of detail, do not copy it. Your data and wording should be your own.
SOP recorded: follow the user-centered design cycle: define users, list needs, prioritize features, sketch a wireframe, then plan a usability check.
Target users and the variables shaping their needs: language, data access, age, and health literacy all change what a user needs.
Persona 1, 'Rosa, 58': limited data plan, prefers Spanish, worried about exposing family. Top need: know if it is safe to seek care without traveling far.
Persona 2, 'Jamal, 19': smartphone-fluent, no car, relies on public transit. Top need: find the closest open mobile site and its hours.
Prioritized feature list (highest-urgency first):
- Live clinic and mobile-site map with wait times.
- Language toggle (English and Spanish).
- Low-bandwidth text-only mode.
- Symptom self-check with 'when to seek care' guidance.
Wireframe (two screens, low fidelity):
- Screen 1: big 'Find care near me' button, language toggle, last-updated stamp.
- Screen 2: map list of sites with wait time and hours, one tap to directions.
Usability-check plan: have three classmates find the nearest open site in under 30 seconds; count taps and note confusion points.
Limitation: our personas are composites we invented, not real users, so the feature priorities are our best guess until we test with actual community members.
This model shows the level of evidence and organization needed to complete: Completes the design project prep: two user personas, a prioritized feature list, a low-fidelity two-screen wireframe, and a usability-check plan with one limitation.
- Identify the purpose, hazards, and required controls.
- Write the procedure in a usable order.
- Confirm materials, measurements, and waste handling before starting.
Keep the structure. Replace the question, facts, measurements, and evidence. Then recheck units, vocabulary, and whether the conclusion goes beyond the evidence.
Also due today: One team member turns in the design package on the class site under the Wednesday Design Project assignment; all names must appear.
Claim ceiling: Today's evidence supports a classroom claim about public-health design project. It cannot prove causation, diagnose a real patient, or justify action outside this room.
One exam-style question that uses exactly what you practiced today. Try it before you reveal the answer, then read why each choice is right or wrong.
Tap an answer to see the full explanation. Nothing is recorded or graded.
It builds this reusable test skill: Defining a user persona in user-centered design.
- Name the concept or data pattern being tested.
- Cross out choices that violate that rule or the evidence.
- Justify the best remaining choice before checking the answer.