MedicAITutor Docs

Station Review SOP

Short operating procedure for station review before publication.

Live API Station schema OpenAPI JSON

Table of Contents

Station Review SOP

Use this page as the short operating procedure for educators, station reviewers, and publishing admins. It is intentionally brief and suitable for printing or saving as PDF.

Rule

Station review supports QA. It does not replace human or clinical publication approval.

  1. Load the station and confirm the title, section, category, task, persona, key points, rubric, and 7-minute limit.
  2. For a material repair, set publication inactive with the block below, save, reload, and confirm the status and reason.
  3. Repair the content while it remains inactive, save a second time, and inspect the new revision and S3 read-back.
  4. Submit a structured review through POST /review or use the admin workspace.
  5. Run a station-specific candidate test and inspect the full scored evaluation.
  6. Require human clinical/content approval.
  7. Set publication published with the block below, save a third time, reload, and verify S3.
  8. For rollback or taxonomy migration, inspect the preview and affected stations before confirming.

Inactivate before repair

{
  "publication": {
    "status": "inactive",
    "reason": "Material repair - candidate retest pending",
    "expert_reviewed": false
  }
}

Publish after testing and approval

{
  "publication": {
    "status": "published",
    "reason": "Clinical review and candidate validation passed",
    "expert_reviewed": true
  }
}

Release checklist

  • Identity, section, category, and 7-minute limit are correct.
  • Task, persona, key points, guardrails, and rubric describe one coherent case.
  • Read-back has the intended publication state and revision.
  • Current S3 object matches the approved station JSON.
  • Candidate session is station-specific, loop-free, and ended.
  • Scored evaluation includes domains, ratings, rationales, and evidence.
  • Human clinical/content approval is recorded and expert_reviewed is true.
  • Published status, release reason, and expert-review provenance read back correctly.
Stop on failure

Do not continue after a failed Save, missing or mismatched S3 read-back, failed rollback, or publication mismatch. Resolve the error and verify the last known station state before retrying.

Full practitioner guidePOST /review reference
↑ Back to top