Here's an example of what's due today

Trace a patient route and find the delay

Mon, Feb 8, 2027 · Week 4 · Biotechnology for Health (Biomedical Innovations)

Today's goal: Use the supplied times to map a patient route, find a likely bottleneck, and propose one change to test.

Learn first

What a finished product looks like

This print-shop example shows how to organize your work. Use the supplied F0 to F4 patient-flow records for your assignment and write in your own words. Do not collect or invent patient data.

Model R: a print-shop queue
Completes: A separate, original workflow example. Use its structure for your F0 to F4 diagram and explanation; it contains no official PLTW case answers.

Model R is fictional. Route: job arrives → one printer prints → job is collected. The printer is ready at 10:00, takes 6 minutes per job, and runs without breaks. Collection is immediate. Jobs are served in arrival order. R1 arrives at 10:00 and prints from 10:00 to 10:06. R2 arrives at 10:02 and prints from 10:06 to 10:12. R3 arrives at 10:04 and prints from 10:12 to 10:18.

Waits before the printer: R1 = 0 minutes, R2 = 4 minutes, R3 = 8 minutes. I label these at the queue before printing. The printer is the likely bottleneck here: jobs arrive every 2 minutes but one printer needs 6 minutes per job. R2 and R3 show a growing wait.

I would test a second printer using the same arrivals and job lengths. A drawback is the extra cost and space. I would compare average wait before and after the change, keeping print quality the same. Three jobs cannot show demand all day, and this model does not include equipment failures.

RecordArrivalPrint startPrint endWait (minutes)
R110:0010:0010:060
R210:0210:0610:124
R310:0410:1210:188
Three fictional print jobs show a growing wait before one printer, from zero to eight minutes.
Why this matters

This model shows the level of evidence and organization needed to complete: A separate, original workflow example. Use its structure for your F0 to F4 diagram and explanation; it contains no official PLTW case answers.

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: Turn in your own F0 to F4 diagram and explanation together, not this print-shop model. The patient-flow handout links to Wk4 Lab notebook: Patient flow workflow in Schoology.

Use the patient-flow practice handout for your own records and four-step task. Keep Model R separate.

Submit one PDF with your labeled diagram, waiting times, and explanation in Wk4 Lab notebook: Patient flow workflow. Use the exact Schoology assignment linked here and follow its posted due date. Check the uploaded preview.

Schoology: Wk4 Lab notebook, Patient flow workflow

Claim ceiling: Four fictional records can show a likely bottleneck in this model. They cannot prove a change is safe or show what happens in a real hospital all day.

Check yourself

Practice today's skill

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.

WebXam-style domain: Course practice; BI exam mapping not confirmedSelf-check skill: Separating wait time from task time
A separate example, not one of the F records: a first review ends at 9:23. The next review starts at 9:31 and ends at 9:44. What is the wait between the reviews?

Tap an answer to see the full explanation. Nothing is recorded or graded.

Why this practice matters

It builds this reusable test skill: Separating wait time from task time.

Use it on a new WebXam question
  1. Name the concept or data pattern being tested.
  2. Cross out choices that violate that rule or the evidence.
  3. Justify the best remaining choice before checking the answer.