Patient-reported outcomes, captured on schedule.
Registries can configure validated patient-reported outcome (PRO) instruments at baseline and at scheduled follow-up intervals. Patients receive reminders, and dashboards show enrollment, follow-up rates, and outcome trends.
How it works
- Instruments are versioned: every assessment links to the exact instrument version the participant completed.
- Assessments are scheduled at baseline and follow-up intervals, with reminders to keep follow-up rates up.
- Dashboards show enrolled-patient counts, follow-up rates, and outcome trends over time.
- PRO data exports with a data dictionary so biostatistics teams can work with it directly.
PNOS-P — Pediatric Neuro Outcome Scale (PANS/PANDAS)
PNOS-P is a pediatric neuro outcome instrument developed by Beacon for PANS/PANDAS research and care documentation. It runs on the platform’s versioned-instrument engine: an intake wizard before the first assessment, domain-based outcome tracking over time, and staff review workflows for care teams. Every response is recorded against the instrument version used, so longitudinal data stays interpretable as the instrument evolves.
- Structured intake before the first assessment
- Domain-level outcomes tracked across visits
- Care-team review workflow with audit trail
The data-integrity trail, state by state
Every response lives in exactly one state at a time, and every transition is attributed and audit-logged. The states below are wireframe mockups of the admin workflow — the same states a sponsor audit will walk.
Submitted
Participant submits; responses are original and immutable. Corrections create a new version; the original is preserved.
Correction / Review
A care-team member proposes a correction. The original response, the change, the author, and the timestamp are all on the trail.
Approved / Rejected
A second authorized reviewer approves or rejects each correction. Rejected corrections never overwrite the record.
Locked / Unlocked / Void / Withdrawn
Locked records resist edits for submission windows; unlock requires authority and reason; void and withdrawal preserve full history.
Correction approval and rejection are shown here as the participant-facing mockup; the admin workflow adds reviewer identity, reason codes, and export of the full trail per study.
See the participant view
The screens above are representative mockups of the participant and care-team experience. To see the live product — instrument scheduling, reminders, and dashboards running on a real protocol — request a demo and we’ll walk your team through it.
Request a demoNeed an instrument configured for your study?
Tell us which measures matter to your research question and we will scope the configuration.