Working title: MR Learning Readiness Pathway. Independent educational workflow concept; no patient data, scanner operation instructions or clinical clearance. Sponsor, regional leads and reviewers are simulated roles, not people engaged in this project.
Problem hypothesis: New learners receive fragmented learning resources and do not always know when unresolved questions require an authorised expert. Interviews have not yet validated this hypothesis.
Primary learners: newly onboarded staff receiving institution-approved MR education. Secondary users: educator and training coordinator. Clinical decisions remain with authorised professionals under applicable local procedures.
Design goal: Make the learning pathway, outstanding requirements, escalation route and evidence of learning visible. Course completion must remain distinct from authorisation to practise.
MVP scope: role-based entry; assigned learning checklist; source-linked orientation; one uncertainty/escalation scenario; assessment; instructor review; learning-status dashboard. Out of scope: diagnosis, patient-specific advice, automated clearance, autonomous scanner operation and claims of clinical validation.
Hypothetical pilot: 8–12 consenting adult volunteers using only fictional scenarios. No assertion that volunteers are clinical staff. This pilot evaluates usability and understanding of the educational workflow, not clinical competence.
| ID | Requirement | Acceptance criterion |
|---|---|---|
| MR-R01 | Explain purpose and limitations before entry | User can locate prototype status and understands completion is not clearance |
| MR-R02 | Show role-relevant pathway | Selecting a fictional role changes assigned tasks and preserves status |
| MR-R03 | Present approved-source metadata | Every instructional item has source owner, version and review status; empty source blocks release |
| MR-R04 | Escalate unresolved information | Ambiguity branch creates a pending-review record; completion cannot clear it |
| MR-R05 | Separate completion from readiness | Dashboard has distinct completion, assessment and instructor-review fields |
| MR-R06 | Support reassessment | Failed scenario opens targeted feedback and a different follow-up scenario |
| MR-R07 | Track changes | Release record includes version, owner, rationale and impacted learning objectives |
| MR-R08 | Provide accessible interactions | Core path usable by keyboard; text alternative for audio; feedback not colour-only |
| Stage | Learner need and touchpoint | Assumed pain point | Service owner | Observable measure |
|---|---|---|---|---|
| Invitation | Email/link explains why this training is assigned | Unclear relevance | Coordinator | Invitation-to-start rate |
| Orientation | Role choice and prerequisite checklist | Overload and unclear responsibilities | Educator | Correct pathway selection |
| Guided learning | Short source-linked modules | Resource fragmentation | Content owner | Learning task accuracy |
| Decision scenario | Choose next action with incomplete information | Confusing confidence with authority | Educator | Appropriate escalation choice |
| Expert review | Pending query with context | No visible owner or next step | Designated reviewer | Time to acknowledge query |
| Assessment | New scenario plus rationale | Memorisation without transfer | Assessor | Rubric score on novel task |
| Follow-up | Targeted refresher and reassessment | Same full course assigned to everyone | Coordinator | Gap closure on reassessment |
These pain points are assumptions to validate, not findings from customer interviews.
| Element | Proposed model |
|---|---|
| Service | Managed learning pathway from assignment to reviewed learning evidence |
| Accountable owner | Education lead owns programme objectives and release decision |
| Core design | Central content owner maintains objectives, source register and common assessments |
| Local adaptation | Regional lead proposes language/workflow changes; cannot override required expert review |
| Expert interface | Designated subject expert reviews domain content; availability is a release dependency |
| Delivery | LMS assigns and records modules; issue queue holds unresolved questions |
| Data | Pseudonymous learner IDs, task status and rubric results; no patient data |
| Cadence | Weekly issue review; monthly content review; immediate review on critical source changes |
| Improvement | Review evidence, prioritise change, test updated version, approve, release, monitor |
| Funding logic | Record authoring, review and support effort; cost-benefit remains a hypothesis until measured |
R = performs; A = accountable; C = consulted; I = informed. These are proposed roles; one person may fill several in a prototype but that does not demonstrate matrix-organisation experience.
| Activity | Education lead | Designer | Subject expert | Regional lead | LMS administrator |
|---|---|---|---|---|---|
| Define outcomes | A | R | C | C | I |
| Draft content | A | R | C | C | I |
| Approve domain accuracy | I | C | A/R | C | I |
| Approve local adaptation | A | R | C | R | I |
| Authorise release | A | R | C | C | R |
| Record delivery incidents | A | C | C | C | R |
Trigger: Learner encounters incomplete or contradictory information in a training scenario.
Input: fictional scenario ID, learning objective, source version, learner question.