flowchart TD
A{BCTT available at prescription?}
A -->|Yes| P1["Path 1<br/>BCTT sets threshold (clinic)"]
P1 --> P2["Path 2<br/>home chest-strap, %HR band"]
P2 --> LA["Logic A<br/>weekly BCTT retest"]
A -->|No| P45["Path 4/5<br/>symptom cap or RPE, no device"]
P45 --> LB["Logic B<br/>CISG step rules"]
P45 --> LC["Logic C<br/>session ramp / duration (Kurowski, Micay)"]
A -.->|either| P3["Path 3<br/>wrist, ancillary only"]
P3 -.-> DEAD["DEAD — R(wrist) > 1<br/>blocks in-band adjudication under Logic A or C"]
classDef dead fill:#fdecea,stroke:#c62828,stroke-dasharray: 4 3,color:#7a1f1f;
class P3,DEAD dead;
Path × Logic Documentation Grammar for Adolescent PPCS Aerobic Care
Six decisions recur on an adolescent PPCS aerobic note—testing access, intensity-plus-device path, school/sport staging, progression logic, weekly volume. Primary sources support some of those combinations, forbid others, and leave most silent.
Caution
Not medical advice. Educational use only. Data from published literature.
Documenting a sub-symptom aerobic plan looks simple until the note has to name how hard, how long, which device, which school/sport step, and what event raises the dose next. Each field can be filled from published tools. The uncomfortable question is whether those fields can sit on the same page without contradicting each other—or without inventing compatibility the literature never claimed.
Primary sources support some intensity-plus-device paths and advancement logics, forbid others, and leave most unaddressed—with real consequences for what goes on the chart note.
Abbreviations: BCTT = Buffalo Concussion Treadmill Test; RTL / RTP = return to learn / return to sport (consensus documents often label sport steps RTS); CISG = Concussion in Sport Group.
| Label | Meaning in this piece |
|---|---|
| Logic A | Raise HR ceiling only after weekly BCTT retest |
| Logic B | Advance CISG return step on symptom gate (≥24 h floor on sport steps) |
| Logic C | Advance when a scheduled session in a fixed ramp is marked complete |
| Path 1 | Clinic BCTT sets the HR target |
| Path 2 | Home %HR band read by chest strap |
| Path 3 | Wrist optical (ancillary—not for narrow-band adjudication) |
| Paths 4–5 | Symptom cap or RPE (no HR device adjudicates the session) |
1. Problem
Those six clinical decisions—testing access, intensity-plus-device, weekly volume, school/sport staging, progression rule, monitoring channel—can each be filled from published tools. Written together on one note, the tools rarely say whether a given combination is one a clinician can actually write down and trust.
This piece asks where primary sources describe two choices working together, where they forbid or bandwidth-argue against a combination, and where they never address the combination at all. That third category is the largest: a flat form that lets every box be checked would invent compatibility the literature never claimed.
The clearest published exception anchors the rest:
“While the RTL and RTS strategies can occur in parallel, student-athletes should complete full RTL before unrestricted RTS.” — Amsterdam 2022 [PMID: 37316210]
“Children and adolescents should not return to sport until they have successfully returned to school.” — Berlin 2017 [PMID: 28446457]
That is a hard documentation gate: Logic A and Logic C cannot check off return-to-sport steps 4–6 (team drills, contact, unrestricted play) while return-to-learn is still below step 4 (full school day without concussion accommodations). The same gate limits which path/logic pairs belong on one note once RTP steps 4–6 are in play.
What follows separates rules a source actually states from tensions this piece only infers—kept visually apart in the figures below.
2. Methods: the interaction matrix
Six decisions recur on one note:
| ID | Dimension | Question |
|---|---|---|
| D1 | BCTT available at prescription? | Can the clinic run a Buffalo treadmill test this week to set or retest a heart-rate ceiling? |
| D2+D3 | Intensity + monitoring (coupled) | What stops the session—and which device (if any) may read it? |
| D4 | RTL / RTP staging | School-return step, sport-return step, or both? |
| D5 | Progression logic | What event authorizes the next increase — weekly BCTT (A), CISG step (B), or completed session (C)? |
| D6 | Weekly volume framing | Minutes per session, sessions per week, or weekly minute total? |
D2 and D3 stay one axis: the five paths above already bundle anchor + device. Symptom-cap and RPE do not raise a separate device question the way an HR band does.
Cells are colored four ways in the figures (legend on Figure 1a):
- Compatible — a primary source describes this pairing as working together
- Incompatible — a primary source forbids it or shows the measurement band is too wide
- Silent — no primary source addresses it either way
- Inferred — this piece’s own inference from two separate rules; dashed boxes in Figure 1b, never given the same weight as Compatible/Incompatible
Two findings
1. The RTL/RTP gate is the sharpest published veto. RTP steps 4–6 cannot proceed while RTL is below step 4, regardless of Logic A, B, or C Figure 3. Sport steps carry a ≥24 h floor; school steps do not—but both share one documentation veto at high-contact sport.
Reading Figure 3. Tracks may run in parallel at lower steps (Amsterdam: RTL and RTS strategies can occur in parallel). The incompatibility is specific: high-contact / unrestricted sport steps (RTP 4–6) while RTL is still below step 4. Lower-step simultaneous activity is outside that veto.
2. Most pairings are simply never addressed. Of 24 cells in the two priority triangles (19 in Figure 1a + 5 in the dual-track grid), 14 are silent (58%), 6 incompatible (25%), and 4 compatible (17%) — Figure 1c. No primary source says, for example, whether a session-ramp (Logic C) is an appropriate way to advance a symptom-cap prescription (Path 4). Silence does not authorize a combination. A flat form that lets every box be filled would imply validated compatibility the literature does not support—the same failure mode as treating a wrist watch as if it were a chest strap, one layer up in the paperwork.
Figure 2 shows how the paths and logics above bundle in practice.
Figure 2 — Decision topology, pruned
Reading Figure 2. Solid arrows are compatible bundles from Table A; the dashed Path 3 branch marks wrist optical as incompatible for in-band HR adjudication under Logic A or C. The P1→P2 arrow traces the Leddy-trial sequence (clinic BCTT, then home Polar strap)—not an exclusive dependency: when no treadmill exists, non-BCTT anchors (age-predicted %HRmax, symptom cap, or RPE) can still pair with a home chest strap without Path 1. Kurowski titrates bike-session duration at clinic visits (Logic C), not BCTT retest—so Path 1 × Logic C stays silent by design. Not shown: the RTL/RTP gate (Figure 3)—that veto applies after a bundle is running, not at initial path selection.
3. Comparison: what the primary text specifies
Table A — claims independently located in primary text (PMC full text or local PDF). Inferential material appears in Disagreements, not here.
Design key: RCT = randomized trial methods text; Feasibility RCT = Micay adolescent SRC feasibility study; RCT (pilot) = Kurowski Pittsburgh SE pilot; Consensus = CISG consensus document tables (not trial outcomes); Management protocol = published clinical management paper (session-tolerant Logic A variant); Clinical review = narrative review with explicit prescription algorithm (not trial methods).
| Source | Design | What the primary text specifies | Documentation element | PMID |
|---|---|---|---|---|
| Leddy/Buffalo RCT | RCT | “a provided Polar H7 Bluetooth Heart Rate Sensor and Fitness Tracker to monitor HR” | Monitoring device class | 30715132 |
| Leddy/Buffalo RCT | RCT | New target HR set by weekly clinic BCTT for as long as participant remained symptomatic | Progression logic (A) | 30715132 |
| Leddy 2013 BCTT review | Clinical review | “increase the exercise HR target by 5 to 10 bpm every 2 wk (via phone call or email)”; athletes 10 bpm/2 wk, nonathletes 5 bpm/2–3 wk; optional BCTT repeat every 2 wk for precision | Progression logic (A, non-weekly-BCTT fallback) | 24225521 |
| Leddy 2021 stage-ladder | Management protocol | Advance on session tolerance; re-evaluate every 1–2 weeks; goal 80%+ HRmax without exacerbation | Progression logic (A, session-observed variant) | 34817719 |
| Kurowski / Pittsburgh SE | RCT (pilot) | Cycling program 5–6 days/week at 80% of the duration that exacerbated symptoms; dose reassessed at each of 6 clinic visits | Progression logic (C, duration-titrated variant) | 27120294 |
| Micay fixed ramp | Feasibility RCT | 8 fixed sessions; intensity +5% age-predicted HRmax per session until 70%, no clinician adjustment mid-ramp | Progression logic (C, fixed-ramp variant) | 30018795 |
| Amsterdam 2022 | Consensus | RTS table: “each step typically takes a minimum of 24 hours”; RTL table carries no equivalent floor | Progression logic (B) — asymmetric time floor by track | 37316210 |
| Berlin 2017 | Consensus | RTS: “at least 24 hours (or longer) for each step… go back to the previous step” if symptoms worsen; no parallel sentence on the RTL table | Progression logic (B) — same asymmetry, prior consensus | 28446457 |
| Amsterdam 2022 | Consensus | “student-athletes should complete full RTL before unrestricted RTS” | Cross-track gate | 37316210 |
| Berlin 2017 | Consensus | “Children and adolescents should not return to sport until they have successfully returned to school” | Cross-track gate | 28446457 |
Figure 4 below visualizes the three intensity-shaped progression models in the Micay, Leddy 2021, and Kurowski rows.
4. Disagreements
The disagreements below are not a named-camp debate in the literature. They are silent and inferred cells from the matrix, written as prose.
Disagreement 1 — does progression logic interact with monitoring channel at all? Session-ramp advancement (Logic C: each completed session authorizes the next dose step) never states which device confirms in-band completion. Wrist optical channels often disagree with reference by more than a narrow HR band is wide. If completion was logged from a wrist reading, in-band zone membership is a soft claim. That pairing—Logic C × Path 3—is an inference here, not a finding either source states, and it does not carry the same weight as the two gate quotes in Table A.
Disagreement 2 — is the same-day combined-load rule a finding or a convention? One proposed default holds advancement on both school and sport tracks the next day if either track shows >2/10 symptom rise for >1 hour—and that specific rule has no published source. Any documentation format will need it somewhere, labeled as an adopted clinical-judgment default, not a citation.
Disagreement 3 — is silence permission? Of the 24 cells above, 14 (58%) are silent—no primary source addresses that combination either way (Figure 1c). A form that lets a clinician check any box in any combination treats that silence as resolved. The literature has not resolved it. Silence is not permission: when a Path × Logic pairing has no matrix cell, I would write “combination not addressed in published sources” on the chart and choose Path 4 or 5 before leaving wrist HR as the hidden adjudicator.
5. SOP: before you write the note
Step 1 — Declare the bundle, not the fields. Before any line is written, record two labels that rarely appear together on the same sheet:
| Label | Allowed values | What each value means |
|---|---|---|
| Path | 1–5 | 1 clinic BCTT sets HR ceiling · 2 home %HR band read by chest strap · 3 wrist optical (ancillary only) · 4 symptom cap · 5 RPE band |
| Logic | A · B · C | A weekly BCTT retest (or session-tolerant stage ladder) · B CISG RTL/RTP symptom-gated step · C scheduled session in a fixed ramp marked complete |
If the pair is incompatible in the matrix (e.g., Path 3 used to adjudicate narrow HR-band membership), do not proceed—change Path or change the control variable. Published wrist–reference LOA widths under exercise are typically wider than a narrow prescription band; treat wrist HR as ancillary, not as zone confirmation.
Step 2 — Record shared context (same meaning on every path).
| Field | What to write |
|---|---|
| RTL step / RTP step | Current step on each ladder: RTL = return-to-learn (symptom-limited class attendance → full day without concussion accommodations); RTP = return-to-sport (light aerobic → unrestricted play) |
| Logic label | A, B, or C — which advancement rule is active |
| Reassessment | Date + responsible clinician/AT |
Step 3 — Apply the cross-track gate before RTP steps 4–6. Table A rows for Amsterdam and Berlin are a hard documentation veto: if RTL is below step 4 (full school day without accommodations), RTP steps 4–6 (team drills, contact, unrestricted play) cannot be checked off, regardless of Logic A, B, or C. A form that allows both is worse than no form.
Step 4 — Fork path-specific items inside the module, not in a shared header.
| Topic | Why it forks |
|---|---|
| Same-day combined-load hold | Operational definition differs when the session stop rule is HR-band vs symptom-cap — proposed default: hold both tracks the next day if either track shows >2/10 symptom rise for >1 hour; label as adopted convention, not Table A finding (see Disagreement 2) |
| Device class / HR ceiling | Only for Paths 1–3; Paths 4–5 use symptom/RPE primacy |
Step 5 — Flag silent combinations. If the chosen Path × Logic × staging × weekly-volume pairing has no compatible or incompatible cell in the matrix, write “combination not addressed in published sources” on the note—do not leave the boxes filled as if validated.
Wrist + HR-band adjudication: Path 3 cannot be used to adjudicate narrow HR-band membership under any Logic that depends on in-band completion—not Logic C alone. Logic A’s weekly BCTT retest does not remove the bandwidth problem for home sessions read from a wrist sensor.
6. Limitations
Hypothesized gap, not field-tested. That these six decisions do not compose into one mutually compatible note without naming the bundle is a diagnosis from the matrix—not a clinic usability finding.
Matrix scope. Two priority triangles (D1×Path×Logic; D4×Logic×D6) do not exhaust every pairwise interaction across six dimensions. Remaining pairs are backlog or genuinely silent.
Triangle 2 scoped to dual-track. RTL × RTP × Logic is audited only when both tracks are active. Single-track recoveries (e.g., no sport ladder) are omitted to keep the grid finite.
Inferred tensions are not evidence. The wrist-read completion pairing and the same-day combined-load default (Disagreements 1–2) are inferences or unpublished conventions. They belong in documentation design discourse, not in Table A.
No new trial comparisons. This piece only asks whether published sources permit writing a Path × Logic bundle down without contradiction—not which bundle produces better outcomes.
7. Closing
No head-to-head trial picks a winning Path × Logic bundle. The practical minimum is still: name the bundle, veto incompatible pairings (wrist adjudication of narrow HR bands under completion-based Logic C), and label silent cells instead of checking boxes the literature never validated.
Series: Foundation Stack · methods · path × logic documentation