Import and adapt a scenario

Recorded from the actual software with fictional engineering data. Narration: local Microsoft Zira Desktop. Simulation only; no clinical approval.

[00:00:00.000] An imported document is the beginning of a review, not its conclusion. This tutorial follows the source, the draft and the approval decisions in the actual authoring workspace, using a fictional Word example for software practice.

[00:00:16.175] Keep the exact original file with your work. The written guide links the source used for this recording separately from the general practice download. A similar filename or a later formatting revision does not prove that two documents have identical bytes.

[00:00:33.070] Open Scenario authoring and expand Import source. A Word document and pasted text are separate input choices. Importing keeps source material attached to a separate draft, so you can inspect what the parser actually received before accepting structured fields.

[00:00:51.745] Select the imported draft and find Source document. Compare the visible source with the document you supplied. If a table, heading or observation is missing here, resolve that source problem before trusting a later interpretation of it.

[00:01:08.495] Where an AI provider is configured, extraction is a separate operation. Its result is a proposal. A provider error is not a successful extraction, and a generated draft still needs review. Do not keep repeating a paid request when the concrete failure needs investigation.

[00:01:29.065] Review the scenario overview first. Check the title, purpose, learner level and learning outcomes against the source and your intended exercise. Use clear fictional labels in this practice copy. A plausible sentence can still be an unsupported addition.

[00:01:47.570] Then check the patient and handover fields. Names, identifiers and narrative details should have an identifiable source or an explicit human decision. Use fictional data for a shared demonstration. Keep real patient and learner information out of a public tutorial workspace.

[00:02:07.850] Read the states as a sequence of declared simulation pictures. Select each relevant node, inspect its observations and description, and compare them with the source. Do not assume that an empty value means zero; the interface explains how unchanged values are held.

[00:02:27.170] Review the connections and entry choices as carefully as the values. A transition describes when the exercise can move, and an entry point determines where it begins. Panning or zooming the graph is a reading action; editing a node or edge is a saved draft decision.

[00:02:45.725] Make a correction explicitly and save it. Keep the original source unchanged so another reviewer can understand the decision. When the screen presents source gaps, suggested values or warnings, resolve those decisions instead of hiding them behind a confident-looking draft.

[00:03:04.595] Read the review and validation sections before approval. Check source evidence, missing parameters and routing warnings in their actual context. Passing an engineering check does not validate a clinical target or establish that a room's physical outputs have been tested.

[00:03:22.585] Submit and approve only the version you intend to use. Approval makes a particular scenario version available to session preparation. A later draft remains a separate piece of work, while an existing session keeps the version it was configured to run.

[00:03:39.665] Finally, open session preparation and verify that the intended approved version is available. This connects the authoring decision to the next task without starting the simulation. Follow the written source-review procedure alongside the video, and use a qualified clinical review for teaching material.