Surge and usability notes

Open your materials, follow the steps, then turn in your work.

Students take notes on medical surge, mobile response facilities, and usability principles for public-health apps, then complete the PLTW online task.

1. Open your materials

Use the materials named in the first step below. Open lesson resources.

2. Start the work

Annotate notes on medical-surge planning and mobile facility design.

Show all 5 required steps
  1. Annotate notes on medical-surge planning and mobile facility design.
  2. List the core usability principles for a public-facing health app.
  3. Connect clear public-health communication to user trust and uptake.
  4. Sketch how user needs drive an app feature list.
  5. Complete the assigned PLTW online activity on surge response and design.

Lost your place? Reopen today's Surge and usability notes record. Find the last completed evidence ID, check it against the claim ceiling, and continue with the first unfinished step rather than restarting the whole task.

Check your work before submitting

  • Name three usability principles relevant to a health app.
  • Submit the PLTW online task fully completed.

3. Turn in your work

DueCheck Schoology
Hand in
Annotated notes listing three usability principles with health-app examples, a sketch connecting user needs to a feature list, and one trust-building communication strategy.
How to submit and name your file

Keep notes in your science notebook; bring them Wednesday for the design project.

In Schoology, open your course and the assignment for this lesson. Attach your file, select Submit, and check that it appears in the submission.

PDF upload help

You get two school days for every day you were absent, so this deadline moves with you.

Find this lesson's Schoology assignments

These are existing assignments for your section. Follow the directions in the assignment you are working on; this list does not add new work. Check Schoology for each deadline.

Link will not open? Open Schoology, choose your course and section, and find the title shown above.

How this lesson connects

Keep using what you learned last class: A defensible biomedical decision separates scientific evidence from value judgments, identifies who may benefit or be burdened, and states the uncertainty and tradeoffs that remain. Today: A biomedical design advances when test evidence is compared with explicit user needs, criteria, constraints, risks, and failure modes, then used to justify a documented revision.

Print or open for todayActivity 3.3.1 User-centered Design

Check you have the right sheet: the top of it prints today's portal day, Surge and usability notes. The PLTW activity itself is in myPLTW and is not posted here.

Unit 4 extra creditNine items, any order, turn one in any day. Read the cover sheet first.Cover sheet (6 pages)See all nine
Optional: listen or watch a unit review
Optional unit study notebook
Public-health surge capacity and designing tools people can use under pressure.
Open the notebook
Optional review video
Audio overviewVideo overviewMind mapStudy guideFlashcardsQuizData table
Need help? Warm-up, timing, and directions

💡 Big idea: A biomedical design advances when test evidence is compared with explicit user needs, criteria, constraints, risks, and failure modes, then used to justify a documented revision.

  1. 0-5 minWarm-up: name one app you use in an emergency and one thing that makes it fast to use.
  2. 5-28 minTeacher-led notes: medical-surge planning, mobile facility types, and deployment criteria.
  3. 28-45 minNotes: usability principles (learnability, efficiency, error tolerance, satisfaction) with health-app examples.
  4. 45-55 minConnect communication clarity to user trust; sketch how user needs produce a feature list.
  5. 55-75 minPLTW online activity on surge response and design (individual, self-paced).
  6. 75-80 minExit check: name three usability principles and one health-app example for each.
Mr. Mendoza's 5-minute intro
  • Wednesday your team designs a surge communication app: today's notes give you the principles to justify every design choice.
  • Usability is not aesthetics: it is whether a frightened person in a crisis can figure out the app in 10 seconds.
  • WebXam 072110 connects biotechnology and data handling to public-health communication tools.
  • Finish the PLTW activity today: the platform covers the same usability framework your Wednesday wireframe will use.
Know by the end
  • Mobile surge facilities require usability planning just as apps do: the target user's needs drive every design choice.
  • Core usability principles include learnability, efficiency, error tolerance, and satisfaction.
  • User trust in a public-health app depends on clear language, reliable updates, and minimal cognitive load.

PLTW connection and today's work

In myPLTW, open Lesson 3.3 Information Sharing and go to Activity 3.3.1 User-centered Design.

Today's stopping point: You started Activity 3.2.5 Medical Surge on Monday. Today finish Activity 3.3.1 User-centered Design so Thursday's design project uses the same principles.

PLTW activity titles identify the course connection. If your account will not open, use the posted materials for today and tell Mr. Mendoza. Do not mark an online activity complete unless you completed it.

Course connection

  • Activity 3.3.1 User-centered Design
Open Activity 3.3.1 User-centered Design in myPLTW

Use the turn-in directions at the top of this page. Do not create a second submission unless your teacher asks for one.

Show another explanation or a smaller first step

Need help? Choose a starting point

Need a running start
Sort today's statements about Surge and usability notes into observation, teaching model, and decision before writing a claim.
On track
Complete the assigned Annotated notes listing three usability principles with health-app examples, a sketch connecting user needs to a feature list, and one trust-building communication strategy., cite at least two evidence IDs, apply the reviewed rule, and name one limitation.
Stuck? Get unstuck
Use the sentence frame: E1 shows ____. E2 helps explain ____. Therefore I can claim ____, but I cannot claim ____.
Push me further
Identify one additional measurement, control, or stakeholder perspective that could change the decision, then explain exactly how it would change the claim level.
Lesson resources: reading, slides, and vocabulary
Socratic teaching slide deck

The deck carries the prior idea forward, lets you inspect an analogy, maps the rule to biology, and ends with the same evidence decision and exit ticket used on this page.

Generated from this lesson's canonical data with a red-team citation check.

Carry forward

A defensible biomedical decision separates scientific evidence from value judgments, identifies who may benefit or be burdened, and states the uncertainty and tradeoffs that remain.

Daily take-home

A biomedical design advances when test evidence is compared with explicit user needs, criteria, constraints, risks, and failure modes, then used to justify a documented revision.

Inspect the analogy

An engineering team tests one prototype feature at a time against a written criterion and records each failure before revising.

  1. Which criterion is being tested?
  2. What stays controlled between trials?
  3. Which result justifies a specific revision?
Rule

A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.

Where it breaks

A classroom test can reveal a design weakness without establishing clinical , effectiveness, durability, or regulatory readiness.

Map the analogy to biology
  • The written criterion maps to the pass condition.
  • Repeated controlled trials map to test evidence.
  • The revision log maps to the next design change and its rationale.
Read this first

Driving question: A city pushes out a correct alert telling residents which mobile clinics are open, but half the people who open the app close it without finding the location. What about the design, not the facts, made a true message useless?

What you already know: A defensible biomedical decision separates scientific evidence from value judgments, identifies who may benefit or be burdened, and states the uncertainty and tradeoffs that remain.

New idea: A biomedical design advances when test evidence is compared with explicit user needs, criteria, constraints, risks, and failure modes, then used to justify a documented revision.

Visual or model: F1. F1. A lesson illustration or teaching diagram for Surge and usability notes. Use it with E1-E3; it is a model or context image, not experimental or patient data. What to notice: Trace the labeled observation or evidence sequence before choosing an explanation.

  1. Observe or measure the relevant feature in today's lesson.
  2. Organize the observation with a stable evidence ID.
  3. Apply this rule: A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.
  4. Choose the option the evidence supports and state the limit of the conclusion.

Real biomedical example: Today the biomedical investigation team uses Surge and usability notes to make a bounded evidence decision. A classroom prototype, , presentation, or does not establish clinical , effectiveness, manufacturing quality, or regulatory clearance.

What the evidence supports: E1-E3 and F1 support the daily take-home when the response meets the stated success criteria.

What it cannot prove: The package does not support claims beyond this lesson's or any real patient diagnosis.

Vocabulary:
  • : A health system's ability to rapidly expand staff, beds, and supplies to handle a sudden jump in patients during an emergency or outbreak.
  • : Healthcare delivered to people where they are, using vehicles or portable units to reach communities far from a fixed clinic or hospital.
  • : The science of protecting and improving the health of whole communities through prevention, education, and policies rather than treating one patient at a time.
  • surveillance: The ongoing, systematic collection and analysis of health data to detect disease early, track its trends, and trigger a timely response.
  • communication: Sharing information clearly and accurately between people, which in healthcare keeps patients safe and helps teams coordinate care.
  • usability: Use the lesson context and glossary entry to explain usability in your own words.

Use it now: Choose one decision option. Cite E1 and E3, then explain how the rule connects the evidence to your choice.

Go further, optional: The source links below are optional enrichment. Every fact required for today's local evidence decision appears in this lesson package.

Evidence set and decision
E1 · Source fact

U.S. Food and Drug Administration is the source this lesson's claim is checked against: Design Controls

Limit: A classroom prototype, , presentation, or does not establish clinical , effectiveness, manufacturing quality, or regulatory clearance.

E2 · Teaching model

A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.

Limit: A classroom test can reveal a design weakness without establishing clinical , effectiveness, durability, or regulatory readiness.

E3 · Task criterion

Name three usability principles relevant to a health app.

Limit: E3 defines the classroom product or success criterion. It is not independent scientific evidence and cannot justify a clinical or causal claim.

PLTW-PBT-2026-12-10 · Simulated classroom evidence scenario

Your role: biomedical investigator

Decision: Your team must decide what the evidence from today's lesson supports before submitting the notebook record named on today's page.

  • Fix the app's design so a rushed resident can find the clinic, because usability is part of whether the message works.
  • Leave the alert alone because the health information is accurate and complete, which means the communication has already done its job.
  • Watch real users try to find a clinic in the app first, since alert counts cannot show where people gave up.

Response: State one choice, cite at least two evidence IDs, explain the rule that connects them, and add one limitation. Submit it as the notebook record.

Claim ceiling: Today's evidence supports a classroom claim about today's lesson. It cannot prove causation, diagnose a real patient, or justify action outside this room.

Composite case file · PLTW-PBT-2026-12-10

Reason for review: Your team must decide what the evidence from today's lesson supports before submitting the notebook record named on today's page.

Context: Today the biomedical investigation team uses Surge and usability notes to make a bounded evidence decision. A classroom prototype, , presentation, or does not establish clinical , effectiveness, manufacturing quality, or regulatory clearance.

Timeline:
  • T1: Annotate notes on medical-surge planning and mobile facility design.
  • T2: List the core usability principles for a public-facing health app.
  • T3: Connect clear public-health communication to user trust and uptake.
  • T4: Sketch how user needs drive an app feature list.
  • T5: Complete the assigned PLTW online activity on surge response and design.
Evidence records:
  • E1: U.S. Food and Drug Administration is the source this lesson's claim is checked against: Design Controls
  • E2: A useful prototype test links a controlled trial to a measurable criterion and turns the result into a documented revision decision.
  • E3: Name three usability principles relevant to a health app.

Measurements: Use only the measurements, units, graph, or counts supplied in today's task. No additional patient measurement is implied.

Figure finding: Teaching diagram for Surge and usability notes. Trace the labeled observation or evidence sequence before choosing an explanation. This is a teaching model, not patient or experimental data.

Uncertainty: This is a composite classroom scenario. Missing history, measurements, or confirmation tests remain unknown and limit the conclusion.

Math moment
Formula or setup

Rate or percent = part / comparison total x 100%. Percent change = (new - comparison) / comparison x 100%.

Worked parallel example

If 18 of 60 records meet a condition, the frequency is 18 / 60 x 100% = 30%.

Units and reasonableness

Name the comparison total. A percent describes the supplied group and does not automatically predict an individual's outcome.

Try it with today's data

Use today's supplied counts to calculate one rate, risk, frequency, or percent change. Show the denominator and interpretation.

Design record
Criteria
  • The solution must address the stated need in today's lesson.
  • The decision must be supported by E1-E3.
  • The final product must make the success criteria visible.
Constraints
  • Complete the work inside the 80-minute block.
  • Use only supplied or teacher-approved materials and evidence.
  • Do not trade , accessibility, or privacy for speed.
Tradeoff weights
  • and evidence quality: must pass before scoring other criteria.
  • User need and effectiveness: highest scored criterion.
  • Time, cost, and ease of use: compare only after and effectiveness pass.

Test evidence: For each option, record the E1-E3 result that supports or fails each criterion. Do not assign a score without a named observation.

Iteration log
  1. Version or option tested
  2. Criterion met or missed
  3. Evidence ID and result
  4. Revision made
  5. Reason for the revision
Decision record
  1. Need and user
  2. Criteria and constraints
  3. Chosen option and evidence
  4. Test result
  5. Revision and reason
Watch the trap

Students often think A polished answer about Surge and usability notes is trustworthy even when its evidence source, comparison, or limitation is missing.. The trap: Presentation quality cannot raise the evidence level. A classroom prototype, , presentation, or does not establish clinical , effectiveness, manufacturing quality, or regulatory clearance.

Worked example · a parallel case (guides, does not reveal)
Annotated surge and usability notes
Completes: Completes the surge and design note-taking task: three usability principles with examples, a user-needs-to-feature sketch, and one trust-building strategy.

Three usability principles (with health-app examples):

  • Learnability: a first-time user can figure it out fast. Example: a clear 'Find a clinic near me' button on the home screen.
  • Efficiency: frequent tasks take few steps. Example: check wait times in one tap, not five.
  • Error tolerance: mistakes are easy to recover from. Example: a confirmation step before submitting symptoms, with an 'edit' option.

(A fourth, satisfaction, means the experience feels trustworthy and not stressful.)

User needs drive features (sketch in words):

  • User need: 'I do not know if it is safe to go to the ER.' -> Feature: live ER wait-time and capacity indicator.
  • User need: 'I do not speak English well.' -> Feature: language toggle.
  • User need: 'I have no data plan.' -> Feature: low-bandwidth text-only mode.

Trust-building strategy:

  • Show the source and time of every update ('Updated 10 min ago by County Health'). People act on information they believe is current and official, which is critical during a surge.
Why this matters

This model shows the level of evidence and organization needed to complete: Completes the surge and design note-taking task: three usability principles with examples, a user-needs-to-feature sketch, and one trust-building strategy.

Build yours step by step
  1. Date and label the entry.
  2. Record the procedure, observation, or design decision clearly.
  3. End with what the evidence means and the next step.
Change it for a new task

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: Complete the assigned PLTW online activity on surge response and design, then keep your notes for the design project.

See the full worked example
Portal terms
CER:
Claim, Evidence, Reasoning: make a claim, back it with evidence, explain your reasoning.
SOP:
Standard Operating Procedure, the exact steps to follow (especially in a lab).
Tracker:
Your PLTW progress log where you record completed evidence.
myPLTW:
The PLTW course site where you do the online activities. Find it in Clever with your Microsoft sign-in, right next to Schoology.
This unit's vocabulary
usability

Tap the speaker to hear a term. Add two of these to your notebook glossary with a definition and an example in your own words.

Build your vocabulary · optional, for extra credit

Pick just 2 or 3 words from today and make them yours: write what each one means in your own words, name the context clue or evidence that helped, then give one example from what you actually did in Surge and usability notes. Try your own words first; the glossary is there if you get stuck. This is voluntary and counts as extra credit, so keep it short.

surge capacity
mobile care
public health
surveillance
communication
usability

Saved on this device. Show Mr. Mendoza or add these to your notebook glossary to claim the extra credit.

Resources & readings

Hand-picked readings and interactives for this lesson, from authoritative open organizations and PLTW's own public course outline.

Practice: try a question, then check your answer

Claim ceiling for this check: Today's evidence supports a classroom claim about today's lesson. It cannot prove causation, diagnose a real patient, or justify action outside this room.

Quick self-check · commit, then reveal

A student makes a certain conclusion about Surge and usability notes from one classroom result. What must the student add before the conclusion is defensible?

How sure are you?

Write an answer and pick a confidence to unlock the key.

Cumulative WebXam review · flash practice

Fast retrieval with instant answers, not the commit-then-reveal check above. Try each from memory first: write what you remember about the earlier units, then check yourself here.

Tap an answer to check it · nothing is recorded or graded
[Review: Nosocomial Nightmare: the chain of infection and how to break it] During plating, why is a face shield considered user PPE rather than sample PPE?
[Review: Outbreak Evidence: line lists, epidemic curves, and identifying the agent] To confirm the causative agent of a foodborne outbreak, what evidence is most definitive?
[Review: Emergency Response: assessment, triage, and stabilization] A solution at pH 2 must be made safe for disposal. What target pH should you aim for?
When presenting surveillance data to decision-makers, what makes a data display most usable?
Missed class or ready for more?
Where this leads: careers
What to do if you were absent
If YOU are absent

Today is individual work you can do from home: complete the same target above, then submit your Notebook check.

FOR A GRADE
Open Schoology

Go to Schoology to turn this in. Submit one PDF. Put your first and last name in the document header. Name the file: FirstName LastName - Assignment Title - YYYY-MM-DD.pdf. If you cannot get in, see Mr. Mendoza. Do not skip the work.

If MR. MENDOZA is absent

Class still runs. Complete the online activity above (it's self-guided). Need the concept taught without a teacher? Use this authoritative explainer:

Ready.gov: pandemic and large-scale health emergencies
Optional extra credit (async)

You've passed Unit 2, so the optional extra-credit track is open. Complete reserved-unit work from home, including virtual labs, for extra credit. Each item shows its correct submission route.

Open the extra-credit track
How this is graded
For: Notebook check: Annotated notes listing three usability principles with health-app examples, a sketch connecting user needs to a feature list, and one trust-building communication strategy.
  • Complete
    Every required part of the artifact is present, nothing left blank.
  • Accurate
    The science and the data are correct and match the evidence.
  • Scientific reasoning
    You explain your claim with evidence and reasoning (CER), not just an answer.
  • Professional communication
    Clear, organized, labeled, and written the way a clinician or scientist would.
  • Submitted
    Go to Schoology to turn this in. Submit one PDF. Put your first and last name in the document header. Name the file: FirstName LastName - Assignment Title - YYYY-MM-DD.pdf. If you cannot get in, see Mr. Mendoza. Do not skip the work.