Technical Standards: The One Document That Can End a Clinical Program

Every clinical programme publishes a document called technical standards. Most students read it once, during admissions, and never again. It is the document a programme reaches for when it wants to remove someone and does not want the removal to be about grades — and because it sits at the intersection of academic judgment and disability law, it is also the document where programmes most often overreach.

What technical standards are supposed to be

They are the non-academic abilities a programme says are essential to complete the curriculum and enter the profession: observation, communication, motor function, intellectual and conceptual ability, and behavioural and social attributes. Accrediting bodies expect programmes to have them. They exist so that a programme can say, in advance and in writing, what the job requires.

They matter legally because of how disability law works. Section 504 and the ADA protect a student who is otherwise qualified — meaning able to meet the programme’s essential requirements with or without reasonable accommodation. Technical standards are the programme’s own statement of what those essential requirements are. So the document does double duty: it defines the job, and it defines the ceiling of what a programme can be made to change.

Where programmes get it wrong

• Writing the standard as a method instead of an outcome. A standard requiring a student to “hear a heartbeat with a stethoscope” describes one way of doing a task. A standard requiring the student to “assess cardiac function” describes the task. The first excludes a deaf student by drafting; the second asks whether an amplified or visual alternative works. Which version is in your handbook matters enormously.
• Requiring everything to be done unaided. Language like “without the use of auxiliary aids” or “independently and without assistance” is common and legally exposed, because reasonable accommodation is precisely the use of aids.
• Applying the standard only after a problem appears. A programme that never assessed technical standards at admission, never raised them for three years, and then invokes them the month after an accommodation request has a sequencing problem it will be asked to explain.
• Using them as a proxy for professionalism. “Behavioural and social attributes” is the elastic clause. It is where concerns land that would be hard to charge as misconduct and impossible to score as academic. See professionalism and fitness-to-practice findings.
• Deciding without an individualised assessment. A conclusion that a student cannot meet a standard has to rest on that student’s actual capabilities, not on assumptions about a diagnosis. Blanket judgments about what someone with a given condition can do are the classic Section 504 failure.

The two questions that decide these cases

Is the requirement genuinely essential? Programmes assert this reflexively. It is a question with an answer, and the evidence includes the programme’s own conduct: whether other students have completed the curriculum without that ability, whether the accreditor requires it, whether other programmes require it, and whether the requirement matches what practitioners actually do.

Would a reasonable accommodation let the student meet it? A programme is not required to lower a standard, waive an essential requirement, or fundamentally alter its curriculum. It is required to consider modifications that do not do those things, and to engage in an interactive process rather than announce a conclusion. See Section 504 and the ADA and the programme-specific detail on technical standards.

What to do the moment technical standards are mentioned

• Get the exact version that applies to you — the one in the handbook for your matriculation year, not whatever is on the website today. Programmes revise these, and the revision date matters.
• Ask which specific standard, and on what evidence. In writing. A general assertion that you cannot meet the standards is not a finding; make them name the clause and the facts.
• Separate the ability question from the performance question. Failing a rotation is not the same as being unable to meet a standard, and programmes blur the two. See failed clinicals, rotations and externships.
• Put any accommodation request in writing now, even if it feels late. A request on the record changes what happens next and makes anything adverse that follows a potential retaliation issue.
• Do not agree to a leave of absence to “sort it out.” A voluntary leave frequently converts a live accommodation dispute into a readmission problem with far weaker rights. See leave of absence and forced medical withdrawal.

Common questions

Can a programme dismiss me purely on technical standards?

It can try, and it happens. Whether it survives depends on whether the standard is essential, whether the assessment was individualised, and whether accommodation was genuinely considered.

I have met the standards for two years. Can they change them now?

Programmes do revise technical standards, but applying a new version retroactively to remove an enrolled student is a different question, and the handbook in force when you enrolled is usually the operative promise. See breach of contract against universities.

Do I have to disclose a disability to raise this?

To ask for an accommodation, yes, in some form and to the right office. There is a real difference between disclosing to disability services and disclosing to a clerkship director, and the sequencing is worth thinking about before you do either.

Does this apply outside medicine?

Yes. Nursing, PA, dental, pharmacy, physical and occupational therapy, veterinary and many allied health programmes all publish technical standards, and the analysis is the same.