late or lost to follow-up: 44 of 112 children in one retrospective series.
Pediatric guided-growth follow-up
Every growth tether has a clock.
GuidedLoop turns an active-implant registry and appointment export into one owned exception queue. It keeps every temporary growth-modulation implant visible from surgery through removal and rebound surveillance, even after a cancellation or no-show.
The agent manages follow-up work. The surgeon decides timing, imaging, and removal.
Agent checkJul 29, 2026
Queue current5implants in situ
3need action
3coordinated
Agent boundaryNo diagnosis. No image interpretation. No autonomous contact.
The actual gap
A temporary implant can keep correcting after the workflow loses the patient.
Guided growth is intentionally gradual. That makes follow-up part of the treatment, not a courtesy reminder. The product opportunity is to own that longitudinal loop without pretending software should make the clinical decision.
higher odds of overcorrection with late versus timely follow-up.
every active implant gets one named owner and one next due window.
The published rates describe one retrospective cohort; they are not claimed as universal incidence or proof that this software improves outcomes.
Integration-light pilot lab
Turn two ordinary exports into an exception queue.
Load a locked registry CSV, reconcile a schedule CSV, then download the cases that actually need work. The prototype processes files locally and does not write back anywhere.
De-identified pilot data only
Use opaque patient codes. File contents stay in browser memory; they are not uploaded, persisted, or transmitted by GuidedLoop. This prototype is not an approved system for PHI.
Bounded agent step
Compile one source note into verified registry fields.
The proposal must cite an exact quote. Code verifies that quote, then a human chooses which fields may enter the lifecycle. The model cannot supply ownership, make a clinical decision, or create an action.
0fields trusted automatically
Proposal modeAwaiting source
not runNo lifecycle can be created yet.
Run the fictional example or paste an explicitly de-identified excerpt. Offline mode recognizes only clearly labeled fields; it does not pretend to be AI.
Load active lifecycles
One row per temporary implant lifecycle, including its owner and clinician-authored due window.
Reconcile appointments
Match scheduled, canceled, completed, and no-show events by opaque case code.
Take out the worklist
Export only unresolved exceptions and a separate record of human approvals and completions.
No pilot files loaded. The fictional queue is active.
Register one lifecycle manually
Interactive product demo
Work the implant lifecycle, not an inbox.
Six fictional cases show the full loop. Advance time, approve a bounded action, and watch the queue recalculate.
GG-204Fictional record
Lena M. · 11y
Bilateral distal femoral medial tension-band plates
Current stateAction needed
Canceled follow-up has no replacement booking.
1
RegisteredJan 8, 2026
2
CorrectionInterval monitoring
3
RemovalHuman decision
4
ReboundPost-removal follow-up
Verified lifecycle
Human verifiedWhat the queue knows
- Implanted site
- Left distal femur · medialRight distal femur · medial
- Documented indication
- Genu valgum
- Operational owner
- N. Patel, RN
- Clinical authority
- Dr. E. Warren
- Next due window
- Jul 8, 202621 days past target
- Required imaging
- Standing alignment radiographRequested, not scheduled
- Preferred language
- Spanish
Clinician-authored plan
Continue surgeon-directed observation. Return in approximately 3 months with standing alignment imaging.
Event history
Why the case is here
- Guided-growth implant registered
Operative note and implant log verified by clinic staff.
- Interval visit completed
Surgeon continued observation and set a 90-day return window.
- Follow-up canceled
No replacement appointment is present in the supplied schedule.
Bounded agent proposal
Recover the missed follow-up
Canceled by family; no replacement appointment recorded. The lifecycle remains open because the implant is still recorded as in situ.
Draft task for N. Patel, RN
Prepare approved Spanish outreach asking the family to rebook the already-requested guided-growth follow-up. Escalate to N. Patel, RN if no booking is recorded within 2 business days.
Awaiting human reviewNo external action occurs in this prototype.
Agent run is current.
Useful before integration
Start with one coordinator and one living list.
The first pilot can create value from a daily surgery export or a 60-second registration form plus a weekly appointment export. Integration should remove work later; it is not required to test whether the lifecycle queue is valuable.
Register once
Propose procedure, implant site, and explicit dates from a de-identified source note. A human verifies every quote and enters ownership separately.
Quote-backed source compiler, CSV, or formWatch the clock
Compare due windows with bookings, cancellations, no-shows, and already-requested imaging. Recheck after every event.
Deterministic lifecycle stateClose the loop
Prepare staff work, require approval, and keep escalation open until booking, removal, or another documented disposition.
Human-controlled actionFictional baseline preview
Does the supplied list contain work worth owning?
These are aggregate queue facts, not a claim that GuidedLoop prevents overcorrection or saves money.
Active lifecycles5implants or tethers still owned
Need attention now33 bounded staff actions nominated
Missed visit state1cancellations or no-shows still open
Longest beyond tolerance7 dbased only on clinician-entered windows
3 supplied lifecycle exceptions can be worked now. Compare this exact list against the existing EHR queue before buying anything.
Incumbent falsification
Does GuidedLoop find anything the current queue misses?
Import the existing EHR report, registry, or spreadsheet exception list as one opaque case code per row. The comparison runs in this browser and treats neither queue as clinical ground truth.
No incumbent exception queue loaded.
Incremental value has not been tested.
Run the controlled fictional queue to inspect the method, or load pilot records and the exception list the current workflow produced for the same census and date. Review progress can be downloaded and restored as a strict opaque-code worksheet.
Pilot must prove95%+
of active implants captured from the real source workflow.
Review target<2 min
median human review time for each flagged case.
Safety floor0
wrong-patient actions or autonomous clinical decisions.
Novelty kill test
If the existing EHR can produce this exact exception queue, do not buy another product.
Epic publicly documents implant follow-up data, and general orthopaedic pathway platforms already exist. GuidedLoop earns a product only if its guided-growth-specific reconciliation, removal ownership, and rebound transition are materially faster to deploy and operate.
GuidedLoop owns
The follow-up state
- Active implant census
- Named operational owner
- Clinician-set due window
- Canceled and unresolved visits
- Removal and rebound transitions
- Human-reviewed outreach tasks
The surgeon owns
The clinical decision
- Radiograph interpretation
- Alignment measurements
- Follow-up interval selection
- Removal or reinsertion decisions
- New imaging orders
- Changes to the treatment plan