Import Word#
For a first attempt, use the fictional asthma practice Word file. Its Markdown twin makes every simulated value readable without Word. This is a software fixture, not a clinically validated scenario.
To follow the recorded tutorial using the exact imported bytes, download the recorded tutorial source. The default practice copy differs only in title styling. The two files have distinct hashes; the tutorial’s extraction history belongs to its original source.
Open Scenarios → Scenario authoring. Import a fictional .docx file using the source-file control. The host saves the original document and its parsed source. Select the saved document and compare headings, lists and tables with the original Word file. Download the original from the source panel if you need to inspect it again.
An import captures source material; it does not yet create an approved simulation. Word is the primary guided path for this MVP. Other supported formats may produce warnings, and a scanned PDF without extractable text needs a different source or additional recovery. Do not interpret an empty source panel as an empty clinical scenario.
Extract a scenario#
Use Start AI course analysis for the source-document review flow when it is offered. The separate Extract scenario action uses the ordinary single-run path; the app labels the available workflow. Choose the actual configured provider and model, inspect the proposed input and confirm before sending it. The host records progress and saved workflow history.
Partial fields shown during streaming are unverified. Wait for the completed result, inspect machine source checks, then compare the proposed course with the source. Use the available save action to create a draft. Starting another run is a new request and may incur another provider charge.
If extraction fails or disconnects#
- A lost browser connection can leave the durable run continuing on the host. Reconnect or refresh its saved workflow before starting again.
- A cancelled request can still incur upstream provider charges. Check the saved state before retrying.
- An available retained-response or corrected draft is marked unverified. Saving it preserves material for review; it does not silently approve the result.
- The ordinary two-stage path may not retain a failed response for correction. Use the recovery controls actually shown for that workflow.
- If a save reply is uncertain, refresh drafts and inspect the saved record first. Avoid duplicate creation.
Review and approve#
Keep the source and the draft side by side. Work through each area before approval:
| Area | Check against the source |
|---|---|
| Patient and context | Fictional identity, history, allergies, medications, setting and handover. |
| Learning outcomes | The expected learner behaviour and its relationship to the scenario. |
| Patient course | States, entry points, transitions, conditions, timing, loops and end criteria. |
| Observations | Parameter, numeric value, unit, trend and whether a value appears on the next reading. |
| Dialogue and cues | Speaker/channel, exact meaning, timing and source association. |
| Scores | Table/scale, oxygen assumptions, source discrepancy and human review status. |
| Pre-brief and debrief | What learners may see, facilitator-only material and model selection. |
Save corrections, inspect validation and source-quality findings, and record any requested source comparison. Editing a field can reopen its review. A quotation associated with a group does not prove every value in that group. Review the actual saved revision rather than relying on an earlier approval label.
Use Approve only after the app’s required checks are satisfied and the reviewer is ready to accept that version locally. Local scenario approval is not clinical certification. An approved version is the stable selection used by session setup; revise through a new draft/version rather than assuming a running session changes with the editor.
Rehearse before learners use it#
Create an engineering rehearsal and exercise each important transition in the Live console. Check the first state, observation units, manual progression, loops, routed dialogue and end criteria. Use mock interfaces and paired browser outputs before involving hardware. Prepare and run the rehearsal.
Export and preserve the source#
Use the exports available for the draft’s actual review lineage. Ordinary approved scenarios, unverified corrections and marked source-review transfers have different export rules. Read the description before downloading: a sensitive engineering snapshot is not necessarily an importable, approved scenario. Keep the original Word source and your review notes according to your lab’s policy.
Troubleshooting#
| Problem | Next action |
|---|---|
| No source text or missing table cells | Compare with the original; inspect import warnings. Try a clean .docx source. Do not approve missing material. |
| No extraction task/provider | Ask an administrator to configure and enable the required services; check the provider endpoint and model. |
| Provider authentication or quota error | Check the host’s key reference and provider account. Never paste a key into a scenario or support report. |
| Approve is unavailable | Read the exact unresolved gaps, source review and score-scale requirements for the current revision. |
| Corrected draft cannot export or score | It may still be an unverified/source-review lineage. Use its stated review/rehearsal path rather than renaming it approved. |
| Setup cannot find a draft | Select an approved saved scenario version, or use the explicitly offered limited rehearsal path. |