Institutional layer · Market entry

Pilot launch centre

A deliberately narrow first deployment. AI-MEDICS does not require the institution to replace its existing learning platform or residency-management system to begin.

Configuration confirmed

0/8

Each step written to the audit log

Governed cases

12–20

Clinician-reviewed before use

Mode

Shadow

Analysis only

Configuration checklist

A named programme owner confirms each step; nothing is assumed by the system.

Scope

One programme, one cohort, one competency domain

Governed content

12–20 clinician-reviewed cases approved by the local panel

Baseline

Baseline captured before any AI-assisted workflow runs

Success metrics

Named metrics agreed with the programme owner before start

Owner

Named programme owner accountable for decisions

Governance approval

Institutional governance sign-off recorded in the audit log

Import

Resident and faculty lists imported by CSV from existing systems

Access

Simple SSO configuration; no replacement of the existing LMS or residency system

Import and access

Existing lists come in by CSV; access uses the institution's own identity provider.

Resident and faculty import

MVP

Upload a CSV exported from the existing residency system. Column mapping is reviewed by the programme owner before any record is created.

Shadow mode

Active

In shadow mode AI-MEDICS analyses imported training data and shows what it would have detected, without becoming the institution's official system of record. No official resident record is modified.