Ethics IRB AI Protocol
When to use
Use this skill when a research project uses AI in recruitment, consent, data handling, coding, analysis, writing, supervision, or participant-facing interaction. During coding work, qualitative-coding-discipline enforces the data rules this protocol sets. It is not for anonymizing identifiable participant data before it enters an AI tool, that is sensitive-data-anonymization-gate.
Inputs
- Research design.
- Participant population.
- Data types.
- AI use case.
- Jurisdiction or institution.
- Whether data are identifiable, pseudonymized, anonymized, or synthetic.
- Submission target, such as ethics committee, IRB, journal, or grant body.
Workflow
- Separate screening, research design, data processing, analysis, and writing uses of AI.
- Identify participant risk, vulnerability, consent implications, and data sensitivity.
- Apply data minimization, purpose limitation, access control, retention, and deletion rules.
- Map regulatory layers, including local ethics rules, KVKK, GDPR, EU AI Act transparency duties, and publisher disclosure rules when relevant.
- Define what data must never enter an AI system.
- Draft the AI-use disclosure for methods, ethics application, consent form, and manuscript note.
- Produce a protocol checklist with approval blockers.
- When identifiable data are involved, hand the data preparation step to sensitive-data-anonymization-gate before any AI processing begins.
Output
Return:
- AI use map.
- Data flow summary.
- Ethics and legal checklist.
- Consent language draft.
- Disclosure language draft.
- Data minimization rules.
- Approval blockers.
- Questions for the ethics committee.
- What to record at session end: the protocol checklist file, any approval blockers still open, and a note on which data categories were flagged for sensitive-data-anonymization-gate.
Verification
- Identifiable clinical or participant data are not sent to AI tools by default.
- Consent language names AI involvement clearly when participant data are affected.
- Jurisdictional claims are marked as checklist guidance unless a legal source was verified.
- High-risk or participant-facing AI use is escalated for human approval.
- Disclosure language matches the actual workflow.
- Before closing: every approval blocker is explicitly listed, identifiable data needing pre-processing are handed to sensitive-data-anonymization-gate, and the checklist is saved where the ethics committee reviewer can find it.
Safety
Do not provide legal advice as a final authority. Do not process raw clinical records, identifiable participant data, or institution secrets. Ask for anonymized summaries when examples are needed.
Example prompt
"Create an ethics committee AI-use checklist for a qualitative interview study where anonymized transcripts may be coded with AI assistance."
Expected smoke output:
- Data flow, consent, minimization, disclosure, and human oversight sections.
- A clear rule that non-anonymized transcripts must not be uploaded to AI systems.
- Approval blockers for vulnerable populations or identifiable data.
Türkçe kullanım notu
Bu beceri, yapay zekânın karıştığı bir araştırma için etik kurul ve veri koruma hazırlığını tek kontrol listesinde toplar. Hangi verinin hiçbir koşulda yapay zekâ sistemine giremeyeceği açıkça yazılır, onam ve beyan dili gerçek iş akışına göre taslaklanır, KVKK, GDPR ve AB Yapay Zekâ Yasası katmanları çalışmaya eşlenir. Hukuki kesinlik gereken yerde son söz kurula ve hukukçuya bırakılır. Kimlik içeren verinin yapay zekâ öncesi işlenmesi sensitive-data-anonymization-gate'e devredilir. Oturum sonunda onay engelleyen maddeler ve hangi veri kategorisinin anonimleştirme gerektirdiği kayda geçirilir.
1---2name: ethics-irb-ai-protocol3description: Use when an ethics committee or IRB application involves AI anywhere in the pipeline, when KVKK, GDPR, or EU AI Act duties must be mapped to a study, or when consent and disclosure language about AI use needs drafting before submission.4---56# Ethics IRB AI Protocol78## When to use910Use this skill when a research project uses AI in recruitment, consent, data handling, coding, analysis, writing, supervision, or participant-facing interaction. During coding work, qualitative-coding-discipline enforces the data rules this protocol sets. It is not for anonymizing identifiable participant data before it enters an AI tool, that is sensitive-data-anonymization-gate.1112## Inputs1314- Research design.15- Participant population.16- Data types.17- AI use case.18- Jurisdiction or institution.19- Whether data are identifiable, pseudonymized, anonymized, or synthetic.20- Submission target, such as ethics committee, IRB, journal, or grant body.2122## Workflow23241. Separate screening, research design, data processing, analysis, and writing uses of AI.252. Identify participant risk, vulnerability, consent implications, and data sensitivity.263. Apply data minimization, purpose limitation, access control, retention, and deletion rules.274. Map regulatory layers, including local ethics rules, KVKK, GDPR, EU AI Act transparency duties, and publisher disclosure rules when relevant.285. Define what data must never enter an AI system.296. Draft the AI-use disclosure for methods, ethics application, consent form, and manuscript note.307. Produce a protocol checklist with approval blockers.318. When identifiable data are involved, hand the data preparation step to sensitive-data-anonymization-gate before any AI processing begins.3233## Output3435Return:3637- AI use map.38- Data flow summary.39- Ethics and legal checklist.40- Consent language draft.41- Disclosure language draft.42- Data minimization rules.43- Approval blockers.44- Questions for the ethics committee.45- What to record at session end: the protocol checklist file, any approval blockers still open, and a note on which data categories were flagged for sensitive-data-anonymization-gate.4647## Verification4849- Identifiable clinical or participant data are not sent to AI tools by default.50- Consent language names AI involvement clearly when participant data are affected.51- Jurisdictional claims are marked as checklist guidance unless a legal source was verified.52- High-risk or participant-facing AI use is escalated for human approval.53- Disclosure language matches the actual workflow.54- Before closing: every approval blocker is explicitly listed, identifiable data needing pre-processing are handed to sensitive-data-anonymization-gate, and the checklist is saved where the ethics committee reviewer can find it.5556## Safety5758Do not provide legal advice as a final authority. Do not process raw clinical records, identifiable participant data, or institution secrets. Ask for anonymized summaries when examples are needed.5960## Example prompt6162"Create an ethics committee AI-use checklist for a qualitative interview study where anonymized transcripts may be coded with AI assistance."6364Expected smoke output:6566- Data flow, consent, minimization, disclosure, and human oversight sections.67- A clear rule that non-anonymized transcripts must not be uploaded to AI systems.68- Approval blockers for vulnerable populations or identifiable data.6970## Türkçe kullanım notu7172Bu beceri, yapay zekânın karıştığı bir araştırma için etik kurul ve veri koruma hazırlığını tek kontrol listesinde toplar. Hangi verinin hiçbir koşulda yapay zekâ sistemine giremeyeceği açıkça yazılır, onam ve beyan dili gerçek iş akışına göre taslaklanır, KVKK, GDPR ve AB Yapay Zekâ Yasası katmanları çalışmaya eşlenir. Hukuki kesinlik gereken yerde son söz kurula ve hukukçuya bırakılır. Kimlik içeren verinin yapay zekâ öncesi işlenmesi sensitive-data-anonymization-gate'e devredilir. Oturum sonunda onay engelleyen maddeler ve hangi veri kategorisinin anonimleştirme gerektirdiği kayda geçirilir.
OnourImpram