ER inefficiency brief
Write a brief that identifies a specific ER inefficiency and frames it as a design problem.
ER inefficiency brief: specific bottleneck observation, stakeholder harm linked to the map, and a one-sentence design problem statement.
- 1Do thisWrite a brief that identifies a specific ER inefficiency and frames it as a design problem.
- 2Use this resource
- 3Submit thisCER: ER inefficiency brief: specific bottleneck observation, stakeholder harm linked to the map, and a one-sentence design problem statement.
- 4Submit it here
- 1CMSD website. Go to clevelandmetroschools.org and click the Clever button.
- 2Clever. Clever opens. Sign in if it asks.
- 3Microsoft (district) login. Use your district Microsoft account (the one for school).
- 4Schoology. Open Schoology, then your class, then Assignments, and find the file named below.
The file to submit is named: Biotechnology for Health (Biomedical Innovations) › Triage, patient flow, stakeholder needs, systems constraints. Debate: speed vs equity. › CEROpen Schoology
What counts as evidence, and where to find it
What makes evidence strong, and where do you find evidence you can trust?
Evidence is the data and observations you use to back up a claim. In science that means measurements, experimental results, images, and records, not “my friend said” or “I saw it once.”
Strong evidence is relevant (it actually bears on the claim), sufficient (there is enough of it), and reliable (it was collected carefully and others could repeat it). One data point is rarely enough; a pattern across many is far stronger.
Where you find it matters. Prefer primary sources and reputable ones: peer-reviewed studies, government and health agencies (CDC, NIH, NHGRI), and your own lab data. When you find a source online, do not trust it on looks. Check who is behind it and what better sources say.
- • Relevant: it directly supports (or tests) the claim.
- • Sufficient: there is enough of it, not a single lucky data point.
- • Reliable: collected carefully, and others could reproduce it.
- • Sourced: you can say where it came from and why that source is trustworthy.
- • Stop. Investigate the source: who made this and why?
- • Find better coverage: what do other reputable sources say?
- • Trace claims and quotes back to the original.
Find two pieces of evidence for a claim in this unit, one from your lab/class data and one from a reputable source. Note why each source can be trusted.
- 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 — you open it through Schoology.
Minute-by-minute · 80-minute block
💡 Big idea: A well-framed design problem is specific, observable, and tied to real stakeholder harm -- vague problems produce vague solutions.
- 0-10Review the brief rubric: what makes a design problem statement specific and evidence-based?
- 10-25Select the bottleneck: choose one from your workflow analysis and describe it in observable detail
- 25-45Stakeholder harm analysis: explain which stakeholders are harmed using your map as evidence
- 45-60Draft the one-sentence design problem and check it against the rubric
- 60-75Submit the ER inefficiency brief as the weekly summative
- 75-80Self-assessment: rate your brief on specificity and evidence quality
- • This week you have built a stakeholder map, a patient-flow diagram, and a team contract.
- • Today you bring those tools together into an ER inefficiency brief -- the document that frames your design problem.
- • A brief is only as good as the evidence behind it, so every claim you make must trace back to something you observed or read.
- • This is also your first weekly summative: the quality of your brief sets the standard for the rest of Problem 1.
- 1Choose one bottleneck from your workflow as the target problem.
- 2Describe the inefficiency with specific, observable detail.
- 3Explain which stakeholders it harms, using your map.
- 4State the inefficiency as a one-sentence design problem.
- 5Submit the ER inefficiency brief as the weekly summative.
- • Your brief names a specific, evidence-based inefficiency.
- • You can frame the inefficiency as a solvable design problem.
- • How to transform a bottleneck observation into a one-sentence design problem statement.
- • How to use your stakeholder map as evidence when describing who is harmed by the inefficiency.
- • What makes a design problem brief specific enough to guide solution development.
Your PLTW work today
Triage, patient flow, stakeholder needs, systems constraints. Debate: speed vs equity. · ER inefficiency brief
Day 5 of this lesson. Open this exact section in myPLTW (reached through Schoology), then do the work below.
Do this: Open Problem 1 in your myPLTW course shell and locate the brief or needs-assessment activity to review the expected format and evidence standards.
Mark the brief activity complete in your tracker after submitting the weekly summative.
The stakeholder map, workflow diagram, and team contract are all done; today you bring them together into the ER inefficiency brief as the weekly summative.
ER inefficiency brief with specific bottleneck description, stakeholder harm linked to your map, and a one-sentence design problem.
All PLTW activities are completed inside the PLTW course environment — this page only gives direction. Submit producibles on Schoology.
Today's PLTW tracker
Check things off as you work, then submit. This tells Mr. Mendoza how you're doing so he can help the class. It does not replace turning in your producible on Schoology.
Use the code Mr. Mendoza gave you, not your name. Saved on this device.
Triage, patient flow, stakeholder needs, systems constraints. Debate: speed vs equity. · ER inefficiency brief
Open Problem 1 in your myPLTW course shell and locate the brief or needs-assessment activity to review the expected format and evidence standards.
The stakeholder map, workflow diagram, and team contract are all done; today you bring them together into the ER inefficiency brief as the weekly summative.
This is how Mr. Mendoza sees the class keeping pace with PLTW. Be honest, it only helps if it is accurate.
🎯 Write a brief that identifies a specific ER inefficiency and frames it as a design problem.
- Choose one bottleneck from your workflow as the target problem.
- Describe the inefficiency with specific, observable detail.
- Explain which stakeholders it harms, using your map.
- State the inefficiency as a one-sentence design problem.
- Submit the ER inefficiency brief as the weekly summative.
CER: ER inefficiency brief: specific bottleneck observation, stakeholder harm linked to the map, and a one-sentence design problem statement.
Submit on SchoologyUpload by 11:29 PM for full credit.
| Task | Who |
|---|---|
| Choose one bottleneck from your workflow as the target problem. | _______ |
| Describe the inefficiency with specific, observable detail. | _______ |
| Explain which stakeholders it harms, using your map. | _______ |
| State the inefficiency as a one-sentence design problem. | _______ |
| Submit the ER inefficiency brief as the weekly summative. | _______ |
Working solo? Put your own name in "Who" for every row.
- Your brief names a specific, evidence-based inefficiency.
- You can frame the inefficiency as a solvable design problem.
Teacher-posted resources
Classroom documents for this lesson. Ones marked “Open the file” open right here; the rest are posted in Schoology. Use the label on each card to choose the right move.
Open this when the class reaches this activity and use it to complete the required lesson artifact.
Placement rationale
Matched Emergency room design and triage by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:er design. Score 138. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).
Open this when the class reaches this activity and use it to complete the required lesson artifact.
Placement rationale
Matched Emergency room design and triage by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:triage, admission. Score 138. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).
Use this as the classroom resource for Emergency room design and triage.
Placement rationale
Matched Emergency room design and triage by path:Biomedical-Innovations/Problem-1_Emergency-Room/1.1_Emergency-Room; keywords:triage, er design. Score 138. Visibility: student-schoology (student-facing resource; link through Schoology rather than local path).
How to get there: open the CMSD website, click Clever, sign in with your Microsoft (district) account, then open Schoology from Clever.
WebXam practice
Cumulative WebXam review
A quick mixed-review pulling questions from earlier units plus today, so the WebXam material stays fresh.
Where this leads — careers
What today's skills lead to. These are real health-science careers this course builds toward. Tap one to see, on the US Department of Labor's O*NET site, what the job actually involves, what it pays, and how fast it is growing.
What to do if you were absent
Today is individual PLTW work, so do exactly what we did in class, from home: complete the same PLTW target above, then submit your CER.
Open Schoology (CMSD) and keep goingHow to get there: open the CMSD website, click Clever, sign in with your Microsoft (district) account, then open Schoology from Clever.
Class still runs. Complete the online activity above (it's self-guided). Need the concept taught without a teacher? Use this authoritative explainer:
CDC Emergency Department Data- CompleteEvery required part of the artifact is present, nothing left blank.
- AccurateThe science and the data are correct and match the evidence.
- Scientific reasoningYou explain your claim with evidence and reasoning (CER), not just an answer.
- Professional communicationClear, organized, labeled, and written the way a clinician or scientist would.
- SubmittedTurned in the right way (Schoology for routine work) and confirmed.
Drop your Mon, Feb 1, 2027 · ER inefficiency brief here. Use a clear file name (your initials + project). Routine work still goes to Schoology (via the CMSD portal).
Upload a project