Scenario Sharing on the Scenario Store

When you publish a scenario, a copy of it is added to the Scenario Store catalogue. Other educational organisations on the platform can browse the catalogue and import that copy into their own library. Once imported, they own that copy and can edit, group-restrict, or delete it without affecting your original.

We rely on the fact that every consumer of the catalogue is an educational organisation acting in good faith. The platform is not open to the public, and access is gated to staff at organisations that signed up to use SimPatient.

Every published scenario sits in one of three states. The state appears as a chip on the scenario card so importers can see at a glance what they're getting.

Browse defaults to showing all verified and pending-verification scenarios. The filter at the top of Browse can narrow to verified-only for users who want only the curated set.

By publishing a scenario you grant SimPatient a perpetual, irrevocable, worldwide, royalty-free licence to host, distribute, modify, and sub-license the scenario through the platform and the Scenario Store. This is the same licence that already covers Your Content under the Terms of Service; publishing to the Store is a deliberate extension of that licence to other organisations on the platform.

Other organisations who import your scenario receive the same use-on-the-platform rights through their own agreement with SimPatient. They do not receive any rights to use the scenario outside the platform.

Published scenarios show the publisher's organisation name on the catalogue card so that importers can see who authored the scenario. Within an importing org's library the imported scenario is owned by that org for editing purposes; it does not retain a visible byline once imported, because the importer can edit, regroup, or delete it like any other library entry.

Authors are credited within the platform through the catalogue listing. There are no financial incentives, royalties, or revenue-share arrangements tied to publishing or importing. Sharing is non-commercial and reciprocal: you publish so that others benefit, and you import knowing that someone else published in the same spirit.

When you publish a scenario you confirm that:

• The scenario is your own original work, or your organisation has the right to share it.
• It does not contain real patient data, real clinical records, or any other personal data of a third party.
• It is medically reasonable for the educational level it targets, to the best of your knowledge.
• It does not include third-party copyrighted content (textbook excerpts, copyrighted images, song lyrics, etc.) beyond what would be considered fair use in an educational context.
• You consent to the SimPatient team reviewing it as part of the verification queue.

When you import a scenario into your organisation's library you accept that:

• You are responsible for reviewing the scenario before assigning it to learners. The verification chip is a signal, not a guarantee of clinical accuracy.
• Your organisation is responsible for ensuring the scenario is appropriate for your learners' level, region, and curriculum.
• Editing is encouraged. Once imported, the scenario is your copy to adapt, regroup, or remove as you see fit.

When a scenario is published, the SimPatient team is notified and the scenario enters a review queue. The team reviews the scenario for medical reasonableness, scope, and platform fit, and either verifies or rejects it.

Verification is not a formal accreditation. It is a platform-level signal that the scenario looks reasonable for general educational use. If you need formal sign-off for a regulated curriculum, you should still review the scenario through your own internal processes regardless of its verification status.

Rejected scenarios are hidden from Browse but remain visible to the original publisher in their My Publishes view, with the rejection reason. You can edit the scenario in your library and republish; the new submission re-enters the queue.

You can withdraw a scenario from the Scenario Store at any time via the My Publishes tab. Withdrawing removes the entry from the catalogue so it can no longer be imported. Copies that other organisations have already imported remain in their libraries; we cannot retroactively delete copies that have left the catalogue.

If you believe a published scenario infringes a copyright or contains real patient data, contact us at hello@simpatient.co.uk and we will investigate and remove the entry from the catalogue if appropriate.

We may update this policy from time to time. Material changes will be flagged on the platform. The most recent version is always available at app.simpatient.co.uk/legal/scenario-sharing.