Lesson L3-3 · authored fragments (docs/43)
Primary review content — the AI-avatar narration, in order.
Let's talk about mixers -- because this is a spot where a kind, helpful instinct can accidentally hurt your resident. A mixer is just a small spoon of plain food you put a dose in so it goes down easier. When a resident can't swallow a pill dry, your go-to mixer is a small spoon of plain applesauce. Small amount, one bite, whole dose gone. Applesauce, or pureed peaches -- plain, simple food your prescriber or pharmacist is okay with. That's a real, safe tool, and you'll use it a lot. Now here's the part I really need to land. A mixer is NOT a way around do-not-crush. If a pill is enteric-coated or extended-release -- remember the EC, ER, XR ones -- stirring it into applesauce is still crushing it. The applesauce doesn't make it safe. Your resident still gets the whole timed dose all at once, and that can make them very sick. So no -- you never sneak a do-not-crush pill down inside food. Two more things and you've got this. First: only use a mixer your prescriber or pharmacist has okayed. Not just whatever food is closest. Not a juice or a drink you picked because your resident likes the taste. Second: if your resident can't swallow a do-not-crush form, you stop, and you call the prescriber for a form they can take. You do not change the form yourself -- that is not your call to make. One rule ties all of it together: STOP. Ask. Never guess.
18 of 18 critical claims are verified_by: null (Gate-2 SME sign-off pending → preview only, production-blocked under the Rule-3.6 waiver). · runtime budget: 7:00
# Concept mirror — MA.L3-3.B (Safe Mixers & the Escalation Path)
> **MIRROR / NOTES ONLY.** The authoritative concept entry is **docs/42 §E, `MA.L3-3.B`**
> (Instructional Domain Model). This file is the local traceability ledger + decision queue for the
> derived-asset bundle; if it ever disagrees with docs/42, **docs/42 wins** (docs/43 §22 authority flow).
| Field | Value |
|---|---|
| `concept_id` | `MA.L3-3.B` |
| `competency_id` | `C-3.3` (⇄ `C-3.2` / `MA.L3-2.C` — this concept feeds the Critical crush rule) |
| `lesson_ids` | `[L3-3]` |
| `clinical_risk` | **High** (feeds the Critical crush rule MA.L3-2.C; ≥90% mastery, spaced repetition) |
| `medication_error_prevented` | Using a food mixer to bypass the crush rule — an enteric-coated / extended-release form stirred into applesauce is still crushed, dumping the whole timed dose at once |
| `learning_objective` | *Know* only prescriber/pharmacist-approved mixers, and that "take whole"/EC/ER means STOP + call; *do* use applesauce for a crushable tablet, refuse to mix an ER form and escalate |
| `transcript_blocks` | `l33-safe-mixers` (single block) |
| `storyboard_references` | `V-L3-3-02` (proposed) |
| `knowledge_checks` | `KC-L3-3-B-Q1` (ER-capsule escalation, primary); `KC-L3-3-B-Q2` (safe-mixer selection, primary); variants `Q1B`/`Q2B` **deferred** (owner decision 2026-07-05) |
| `simulation` | Don Montana Diltiazem ER — offering to mix the ER capsule into applesauce is a **force-fail** (inherited from the Critical MA.L3-2.C crush gate) |
| `sme_status` (docs/42) | `not_started` — this bundle is authored **ahead** under the Rule-3.6 waiver (below) |
| `apd_traceability_status` | sourced (applesauce mixer = `[APD]`; food-mixer-is-still-crushing decomposition = `[Waiver360-added]`; escalation target + grapefruit/hot-liquid legacy content = open, see queue) |
## Rule-3.6 author-ahead waiver (recorded 2026-07-05)
docs/42 lists this concept's `sme_status` as **`not_started`** (unlike the `in_review` reference
concept MA.L3-6.A). Per docs/42 §I.1 / docs/43 §4, this bundle is authored **ahead of concept
approval under a Rule-3.6 waiver** as part of the Oral Route reference build. Consequence:
**every fragment in this bundle is `sme_status: "draft"`, preview-flag only, and
production-publish-blocked** until (a) the concept reaches `approved` and (b) a Gate-2 SME sign-off is
recorded in `content_revisions.sme_signoff_*`. Because this concept **feeds the Critical / 100%-gating
crush rule MA.L3-2.C**, the answer to `KC-L3-3-B-Q1` restates that Critical concept's protected
escalation — changing it should be treated under the docs/43 §7 protection rule even though
MA.L3-3.B's own `clinical_risk` is High (see Decision queue #6).
## Source ledger (projects into `payload_json.sources`)
- `curriculum_source`: "APD BMA Module 2 (order to crush/dissolve/dilute; safe-mixer checkpoints) + APD MAR practical exam (Don Montana med pass, Diltiazem ER)"
- `form_reference`: `null` — the mixer/crush escalation is not tied to a specific APD form; it recurs on the MAR (65G-7.008 A) and the enteral/G-tube MAR.
| # | Claim | Tag | Source | verified_by |
|---|---|---|---|---|
| C1 | A mixer is a small amount of plain, prescriber/pharmacist-approved food (e.g. applesauce, pureed peaches) used so a dose can be swallowed; applesauce is an acceptable mixer for a plain crushable tablet | `[APD]` | Mod2 v2 Q26 (applesauce for a whole crushable tablet); v4 Q14 (offer applesauce/pureed peaches) | null |
| C2 | Altering a medication — including crushing, dissolving, or diluting/mixing it — requires a prescriber order; use only an approved mixer and STOP + ask when unsure | `[APD]` | Mod2 s118 ("must have an order to crush, dissolve, or dilute"). Instructional inference that s118's "dilute" extends to food mixers — see queue #2 | null |
| C3 | Mixing a crushed EC/ER form into applesauce/pudding does **not** bypass the do-not-crush rule — it is still crushing, releasing the whole timed dose at once, which can make the resident very sick | `[APD]` (rule + mechanism) + `[Waiver360-added]` (food-mixing-is-still-crushing decomposition + "very sick" DSP register) | Mod2 s118; mirrors MA.L3-2.C C5; consequence register per legacy recording guidance (forbids "fatal"/"could kill") | null |
| C4 | When the resident cannot swallow a "take whole"/EC/ER form, the MAP STOPS and contacts the prescriber for a different form; the MAP may not alter the form | `[APD]` + `[Needs Owner Review]` (escalation target) | Mod2 s118; Mod2 v2 Q25 (Procardia XL "take whole" → escalate). **`TODO(source-L32C-1)`**: concept says "prescriber"; Q25 key says "pharmacist" | null |
| C5 | Shared "STOP. Ask. Never guess." escalation chip | `[Waiver360-added]` | Reused reinforcement chip (docs/42 §E MA.L3-2.C / MA.L3-3.B field 14), grounded in the APD escalate-when-unsure / order-required principle — not APD-verbatim | null |
| C6 | Grapefruit-juice and hot-liquid unsafe-mixer cautions (legacy L3-3) | **excluded** — `[Needs Owner Review]` | Legacy `SRC-L3-3-4` (grapefruit) / `SRC-L3-3-5` (hot liquids) — **not in this concept's APD sources**; deliberately kept OUT of narration and answer keys (see queue #5) | null |
## Patient-safety chain (owner directive — treat as a patient-safety concept)
1. **Medication error prevented.** A resident can't swallow a big pill, so a MAP (or a well-meaning
coworker) opens the extended-release capsule or crushes the enteric-coated tablet and stirs it into
applesauce "so it goes down." The applesauce hides what actually happened: the slow-release design is
destroyed and a dose engineered to release over hours hits the resident all at once — an
overdose/toxicity event from a correctly-prescribed medication. This concept is the loophole-closer
for the Critical crush rule (MA.L3-2.C).
2. **Why staff make this mistake — the real-world reason.** It is not "forgot." It's the *opposite* of
forgetting — the MAP is trying hard to get the dose **in**. The resident is refusing or struggling to
swallow, skipping the dose feels like failing them, and a spoon of applesauce is the kind, obvious fix
any caregiver reaches for at the kitchen table. Mixing meds into food is also completely normal for
*most* pills, so the brain files "applesauce = safe" as a general rule — and then applies it to the
one pill where it's dangerous. The harm is invisible in the room: the resident swallows it fine and
nothing bad happens that shift, so the shortcut feels safe and gets repeated.
3. **How the lesson/transcript prevents it.** Block `l33-safe-mixers` teaches the mixer as a real,
approved tool (applesauce for a plain crushable tablet) **and in the same breath** names the loophole
out loud: a mixer is *not* a way around do-not-crush; an EC/ER pill stirred into applesauce is still
crushed. It replaces "any food works" with a bright line — only a prescriber/pharmacist-approved
mixer — and gives the single correct action when the resident can't swallow a do-not-crush form: STOP
and call the prescriber. "STOP. Ask. Never guess."
4. **How the simulator reinforces it.** In the Don Montana scenario the Diltiazem is an extended-release
capsule Don says is hard to swallow, and applesauce is on the tray. Offering to mix the ER capsule
into the applesauce is a **force-fail** — the same gate as the crusher path — because mixing in food
is still crushing. The scenario will not advance until the MAP escalates instead of altering the
form. The "helpful applesauce" instinct is met with an immediate, unmistakable stop.
5. **How the KC verifies mastery.** `KC-L3-3-B-Q1` puts the exact temptation in front of the learner —
a coworker suggests stirring the ER beads into applesauce — and mastery is refusing every
alter-the-form option (open/mix, crush-into-pudding, split) and choosing STOP-and-call.
`KC-L3-3-B-Q2` verifies the flip side: the learner must pick the plain, approved mixer (applesauce)
over "any food works," a juice, or a hot drink — proving they hold the approved-mixer line, not just
the do-not-crush half.
## Decision queue → owner / SME (Michele + Nicole)
1. **`TODO(source-L32C-1)` — escalation target: prescriber vs. pharmacist.** Inherited from the sibling
crush-rule bundle. The concept (docs/42 field 4) says "STOP + call" and this bundle follows
MA.L3-2.C in saying **prescriber**; APD checkpoint Mod2 v2 Q25 keys "call the **pharmacist**." Until
SME confirms the correct Florida-APD escalation contact, C4 stays `verified_by: null` and the bundle
is preview-only. **This gates the bundle to production.**
2. **Confirm the mixer principle (C2).** APD Mod2 s118 requires an order to "crush, dissolve, or
dilute." This bundle infers that "only a prescriber/pharmacist-approved mixer" follows from s118's
dilute/alter language. SME to confirm s118 covers *food mixers*, or supply the correct APD anchor for
the approved-mixer rule.
3. **Confirm the food-mixing decomposition (C3).** "Mixing an EC/ER med into applesauce is still
crushing" is `[Waiver360-added]` instructional structuring of the crush rule (mirrors MA.L3-2.C C5).
Acceptable as labeled `[Waiver360-added]`?
4. **Confirm the consequence register (C3).** Narration uses "can make them very sick," not
"fatal"/"could kill," per legacy recording guidance. Confirm register for the DSP audience.
5. **Grapefruit-juice / hot-liquid content (C6) — deliberately EXCLUDED.** The legacy L3-3 lesson
cautioned against grapefruit juice (`SRC-L3-3-4`) and hot liquids (`SRC-L3-3-5`); neither is in this
concept's APD sources. This bundle **excludes** those drug-specific pharmacology claims from
narration and answer keys — the grapefruit/hot-drink KC distractors are keyed on the
*approved-mixer/escalation* principle instead. SME to decide whether to (a) keep them out, or (b)
re-add them with an APD anchor or an explicit `[Waiver360-added]` badge. Authors did not self-resolve.
6. **KC key protection (Q1).** MA.L3-3.B is **High** (`keyProtected: false`), but `KC-L3-3-B-Q1`'s
correct answer restates the Critical MA.L3-2.C crush-rule escalation. Confirm whether Q1's key should
be treated as SME-protected copy by adjacency (docs/43 §7). Bundle currently sets `keyProtected:
false` with a note, mirroring the gateway pattern in `KC-L3-2-A-Q1`.
7. **Deferred variants.** `KC-L3-3-B-Q1B` and `KC-L3-3-B-Q2B` are deferred until the full route is
authored (owner decision 2026-07-05). `remediation.onWrong` references them as "(deferred — authored
on concept approval)"; the aggregator must record both in the manifest `deferred_variants` so the
remediation path is never a silent dead-end.
8. **Shared sim gate.** The MA.L3-3.B sim rule (`don-montana--mixer-bypass-forcefail`) targets the SAME
Don Montana Diltiazem ER pass as the MA.L3-2.C rule (`don-montana--crush-forcefail`), through the
mixer lens. Confirm they are one gate viewed through two concepts (single force-fail, no double
count), and that the force-fail is inherited from the Critical crush rule.
## Bundle manifest → `../MA.L3-3.B.manifest.json` · human index → `../MA.L3-3.B.README.md` *(owned by the later aggregation step)*
Don's Diltiazem is an extended-release ("ER") capsule. He says it is too big and won't go down. A coworker suggests opening the capsule and stirring the little beads into a spoon of applesauce so it goes down easier. What should you do?
Why: Right. An extended-release capsule has to go down whole. It is built to release the medicine slowly over hours. Opening it, crushing it, or splitting it -- even into applesauce or pudding -- is still altering the form, and Don would get the whole dose at once, which can make him very sick. Mixing it in food does not make it safe. You stop, and you call the prescriber for a form Don can actually take. STOP. Ask. Never guess.
Error prevented: An extended-release capsule opened, crushed, or split -- including into a food mixer -- releasing the whole timed dose at once -> overdose/toxicity.
Misconception: "Mixing it in applesauce bypasses do-not-crush" and "a safe mixer makes any pill okay to crush or split."
A prescriber has ordered a resident's plain crushable tablet to be given with a small amount of food because she cannot swallow it dry. Which is the safe choice as a mixer?
Why: Yes -- a small spoon of plain applesauce is a safe mixer for a plain crushable tablet. It is a small amount, so the whole dose goes down in one bite, and it is the kind of plain, approved food a mixer is meant to be. That matches what the prescriber ordered: the tablet, given with a small amount of food.
Error prevented: Mixing a dose into an unapproved food or drink chosen on preference rather than on the prescriber/pharmacist's approval.
Misconception: "Any food is a safe mixer" -- a mixer must be a small amount of a plain, prescriber/pharmacist-approved food.
Entry: At Don Montana's Diltiazem pass, Don says the extended-release ('ER') capsule is too big to swallow, and a spoon of applesauce is on the tray. A coworker or Don suggests opening the capsule and stirring the beads into the applesauce so it goes down.
Mastery: Force-fail on the mixer-bypass gate; no partial completion. Concept-level KC mastery is >=90% (High); the sim gate itself is pass/force-fail because it is a crush-rule bypass.
Force-fail: FORCE-FAIL. The scenario cannot complete while the ER form is altered into food. This is the SAME gate as don-montana--crush-forcefail (MA.L3-2.C): the applesauce path and the crusher path are treated identically because mixing in food is still crushing. The sim does not silently fail -- it surfaces the same compassionate-framing modal as KC-L3-3-B-Q1, names the food-mixing loophole explicitly ('mixing it in food is still crushing'), links to the l33-safe-mixers re-anchor clip, and offers a 'Try again' CTA.
Shot: Two-column card: LEFT 'Safe mixer' (a small spoon of plain applesauce / pureed peaches for a plain crushable tablet); RIGHT 'Never a fix for do-not-crush' (an EC/ER capsule stirred into applesauce -> red stop -> call for a safe form). Synthetic client 'Don Montana' Diltiazem ER named as the scenario tag only.
Camera: No live camera; the two paths animate side by side so the safe tool and its abuse are seen together; push to the red-stop on the right path.
Avatar: Voiceover; lean-in energy on 'a mixer is NOT a way around do-not-crush' (Michele off-screen).
Visual: Loophole-closer visual (docs/42 MA.L3-3.B fields 10-11): teach the approved tool (applesauce) and name its abuse (mixing an ER form to bypass do-not-crush) in the same card, so the safe tool cannot be rationalized into the unsafe shortcut. Grapefruit/hot-liquid deliberately absent.
Animation: Applesauce path (ok) completes with a green check (docs/42 MA.L3-3.B field 11); the ER-into-applesauce path turns red with a STOP glyph and routes to a 'call for a safe form' escalation node (recipient NOT named - TODO(source-L32C-1)).
Infographic: Left path (GREEN check): plain crushable tablet -> small spoon of applesauce -> one bite, whole dose. Right path (RED stop): EC/ER capsule -> stirred into applesauce -> 'still crushing' -> whole timed dose at once -> 'can make them very sick' -> STOP, call for a safe form. Only-approved-mixer bright line beneath both.
Shot: MS Michele back on camera with a split-screen reference of the completed sticker set (left) + the safe-mixer / do-not-crush card (right); close on centered Michele with the disclaimer footer.
Camera: Return to medium shot; picture-in-picture the two lesson reference stills; end on centered Michele for the sign-off.
Avatar: Michele on-camera; calm close; slight lean-in on 'STOP. Ask. Never guess.'
Visual: Tie both concepts together as one habit - read every sticker, use only an approved mixer, and escalate when unsure - and close on the shared escalation chip.
Animation: The two reference stills slide together into one summary board; the 'STOP. Ask. Never guess.' chip fades in; disclaimer footer holds through the close.
Infographic: Closing chip 'STOP. Ask. Never guess.'; disclaimer footer 'APD-aligned educational content. Not an APD-approved training program.'
Safe-mixer / never-a-fix two-column card: applesauce (or pureed peaches) as an approved mixer for a plain crushable tablet vs. an EC/ER capsule stirred into applesauce = still crushing -> red stop -> call for a safe form.
🖼 image prompt: Two-column flat-vector card. LEFT (green, 'Safe mixer'): a small spoon of plain applesauce / pureed peaches with a plain crushable tablet -> one bite, whole dose. RIGHT (red, 'Never a fix for do-not-crush'): an extended-release/enteric-coated capsule opened and stirred into applesauce, labeled 'still crushing -> whole timed dose at once -> can make them very sick -> STOP, call for a safe form'; a bright-line footer 'Use only a prescriber/pharmacist-approved mixer'; clinical neutral palette; synthetic (Don Montana Diltiazem ER scenario tag); no grapefruit juice, no hot liquids, no APD/state seal. [APD] applesauce mixer (ck Mod2 v2 Q26 / v4 Q14) + [Waiver360-added] 'mixing in food is still crushing' (C3) + [Needs Owner Review] escalation recipient (recipient NOT shown, TODO(source-L32C-1)).
🎬 video prompt: Left path completes with a green check (applesauce + crushable tablet -> one bite); right path (ER/EC capsule -> stirred into applesauce) turns red with a STOP glyph and 'still crushing', then routes to a 'call for a safe form' node; no recipient named; no camera move; transparent background. [APD] + [Waiver360-added]. Do not render grapefruit juice or hot liquids (deliberately excluded).
Shared 'STOP. Ask. Never guess.' escalation chip, reused across MA.L3-2.C / MA.L3-3.A / MA.L3-3.B.
🖼 image prompt: Minimal high-contrast reinforcement chip reading 'STOP. Ask. Never guess.'; warm neutral background; no faces, no logos, no APD/state seal; SVG-friendly. [Waiver360-added] shared escalation chip (grounded in the APD escalate-when-unsure / order-required principle; not APD-verbatim).
🎬 video prompt: Chip scales in with a soft bounce; 'STOP.' emphasized first, then 'Ask. Never guess.'; ~1.5s; transparent background. [Waiver360-added]
Target runtime: 7:00 · 5 chapters · not rendered (url: null)