An OSCE collects personal data from four groups: candidates, simulated patients, any real patients, and examiners. Each group consents to something different, and recording a station adds a layer to all four. This page sets out the principles as a policy and a checklist. It does not give legal advice for any country. Your counsel maps the principles to your law.
Why does an OSCE need a consent and data policy?
A written exam produces one record per candidate: the answers. An OSCE produces many. Mark sheets with examiner comments, global ratings, incident logs, simulated patient feedback, adjustment records, and, if stations are recorded, video and audio of the candidate examining a person. Some of that data is sensitive. All of it is personal.
The Georgian accreditation review of medical schools noticed the gap. Among its recommendations for schools using the OSCE format was "developing patient consent forms when using the OSCE format (for international students as well)". The point is wider than patients. Everyone in the room has data collected about them and needs to know what for.
A UK test center's privacy notice for its OSCE candidates shows the shape of the answer. It states what data are collected, why, on what basis, who sees them, how long they are kept, and what the candidate can ask for. That is the template. The rest of this page fills it in for each group.
Who consents to what?
Group | What is collected | What they consent to or are told |
|---|---|---|
Candidates | Identity check, marks, examiner comments, ratings, incident entries, adjustment records, any recording | The purpose of each record; who sees it; retention; that recordings may be used for appeals, examiner training and quality review; their rights to access |
Simulated patients | Personal details, availability, training records, portrayal notes, any recording, health information relevant to the role | The role, including any physical examination and its limits; recording and its uses; payment data handling; the right to stop a station |
Real patients | Clinical information used in the station, presence in the room, any recording | Written consent for use in assessment, separate from clinical consent; the right to withdraw; recording uses; how candidates are told about the patient |
Examiners | Identity, training records, marking data, calibration results, any recording | That their marks are analyzed for consistency; that recordings may be reviewed; how their performance data are used and by whom |
Two points are easy to miss. Examiners are data subjects too: an examiner comparison report names them. And simulated patient consent is not one form. A simulated patient consents to a role, an examination, a recording, and a payment record, and can consent to some and not others.
Should OSCE stations be recorded?
Recording is optional. Many schools run OSCEs without it. Those that record do it for defined reasons, and the policy names them. A vendor's guidance on recording exams lists the usual ones: a legal basis for the recording, a retention period, and use in appeals. To those add examiner training and quality review.
The trade-offs:
- For. An appeal can be decided on what happened, not on recollection. Examiner calibration can use real stations. A station that went wrong can be reviewed.
- Against. Cost and set-up in every room. Consent from everyone recorded, every time. Storage that is secure, retained for a fixed period, and then deleted. Candidates and simulated patients who perform differently on camera.
If you record, decide four things and write them into the policy: the purpose, who can view a recording and on what authority, how long it is kept, and how it is deleted. A recording with no retention period becomes a permanent archive of candidates examining patients. That is a liability, not an asset.
If you do not record, say so, and say what the appeal evidence is instead: the mark sheet, the examiner's notes and the incident log. The regulations page covers the appeal side.
What data principles belong in the policy?
The principles below appear, in some form, in most data protection regimes. They are written here as policy lines. Counsel confirms the wording for your jurisdiction.
- Purpose. Each record is collected for a stated purpose: assessment, appeals, training, quality review. It is not used for another purpose without a new basis.
- Minimum. Collect what the purpose needs. An adjustment record holds the adjustment, not the diagnosis.
- Basis. Each collection has a stated lawful basis. For candidates, that is usually the assessment itself; for recording, it may be consent. Counsel decides.
- Access. A list of who can see each record, by role. Examiner comments go to the board and the candidate's feedback; the examiner comparison goes to the lead and the trainer.
- Retention. A period for each record type. Mark sheets and ratified results are kept as long as the program's records rules require. Recordings are kept for the appeal window plus the training use, then deleted.
- Security. Records are stored where access is controlled and logged. Paper mark sheets are collected and counted the same day.
- Rights. Candidates, simulated patients, and examiners can ask what is held about them and can correct errors. The policy says how.
- Transfers. If data leave the institution, to a vendor or another site, the policy says where and under what agreement.
The exam system, whatever it is, has to support these lines in practice: role-based access, an audit of who viewed what, and deletion at the end of the retention period.
The consent and data checklist
What goes wrong?
- One consent form for everything. A simulated patient who agrees to a role is taken to have agreed to a recording. Separate the items.
- Recording without retention. Years of video with no owner and no deletion date.
- The diagnosis in the adjustment record. Student support holds the reason; the exam holds the adjustment.
- Examiners forgotten. A comparison report circulates with names on it, and nobody told the examiners it existed.
- International candidates assumed to know the local rules. The Georgian review's recommendation singled them out. The notice is given to everyone in a language they can read.
Frequently asked questions
Do OSCE candidates need to sign a consent form?
Candidates are usually assessed under the program's regulations rather than by consent, so they receive a privacy notice that states what data are collected and why. Recording is different: many institutions ask for explicit consent to record, or rely on another basis that counsel has confirmed. Either way, candidates are told beforehand.
What should a simulated patient consent form cover?
The role and its script; any physical examination and its exact limits; whether the station is recorded and what the recording is for; how the simulated patient's personal and payment data are handled; and the right to stop a station. Each item is a separate decision, and a simulated patient can agree to some and not others.
How long should OSCE recordings be kept?
For the appeal window plus any agreed training use, then deleted. The policy names the period, who can view recordings in the meantime, and who deletes them. Marks and ratified results follow the program's records rules, which are usually longer. A recording without a retention period is a liability.
Are examiners' data protected too?
Yes. Examiner names, training records, marks, and calibration results are personal data. An examiner comparison report names people. Examiners are told how that data is used, who sees the comparison, and how it feeds training. Treating examiners as data subjects also helps them accept the comparison.
What about real patients in an OSCE?
A real patient consents to taking part in an assessment, separately from any clinical consent, with the right to withdraw at any time. The consent covers what candidates will do, whether the station is recorded, and how the patient's clinical information is used in the station. The Georgian accreditation review specifically recommended developing patient consent forms for the OSCE format.