ASF Standards · Medical Transport · Standard 7
Standard 7 — Governance & Management
Criteria in this standard
7.1 — Named Accountable Clinical Lead
7.2 — Incident Reporting and Root-Cause Investigation
7.3 — Internal Audit, On a Fixed Schedule
7.4 — Complaints Logged, Investigated, Closed
7.5 — Management Review, With Minutes and Actions
7.2 — Incident Reporting and Root-Cause Investigation
7.3 — Internal Audit, On a Fixed Schedule
7.4 — Complaints Logged, Investigated, Closed
7.5 — Management Review, With Minutes and Actions
7.1
Named Accountable Clinical Lead
Non-Negotiable
A named, currently employed individual holds documented, final clinical accountability for the transport organization’s quality and safety, with authority to halt an unsafe transport. Financial accountability is named separately, even where the same person holds both roles, and a brief, genuine statement of mission and values exists for the organization.
In plain terms: One real, current person is clearly on the hook for the organization’s clinical quality and safety — not a title left over from someone who’s since moved on.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
A clinical lead title left unassigned after someone departs creates exactly the accountability gap that becomes visible only when something goes wrong and the honest answer to “who owns this” is uncertain. Authority to halt an unsafe transport needs to be genuinely exercisable, not merely written into a job description that’s never actually been tested in practice.
What good looks like
- A current, verifiable individual holds the role, matching employment records.
- Documented authority to halt an unsafe transport exists and has been exercised.
- Crew can correctly name this person without hesitation.
Common failure modes
- A named lead has left the organization and the title was never reassigned.
- Halt authority exists on paper but has never actually been exercised.
- Crew give inconsistent answers about who holds this accountability.
Worked example
In practice
A mid-sized transport organization after a leadership transition.
BeforeThe organizational chart listed a clinical lead who had left for another position four months earlier. The operations manager had been informally handling clinical decisions without a formal appointment or documented halt authority.
ActionLeadership formally appointed the operations manager as Acting Clinical Lead, issued a signed appointment letter with explicit halt authority, updated the organizational chart, and briefed all crew directly.
AfterThe Monitor asked three crew members who held clinical accountability and all three correctly named the same person with accurate authority description. Criterion verified.
If you are starting from zero — do this first
- Check who is actually named as clinical lead and confirm current employment.
- Issue or update a formal appointment letter with explicit halt authority.
- Brief crew directly, not relying on an organizational chart update alone.
The most common mistake: Updating the organizational chart but never directly telling crew, who continue naming the previous lead months later when asked.
Self-assessment questions
1. Is there a named, current clinical lead, not a title left over from someone who has since left? — Verified against actual employment records, not an outdated organizational chart.
Evidence: Current employment record, appointment letter
Evidence: Current employment record, appointment letter
2. Does this person hold documented authority to halt an unsafe transport before it departs? — Authority on paper only is not authority.
Evidence: Signed delegation of authority
Evidence: Signed delegation of authority
3. Can crew correctly name this person if asked directly? — If frontline crew don’t know who it is, the accountability is not functioning in practice.
Evidence: Crew interview
Evidence: Crew interview
4. Is financial accountability named separately from clinical accountability, even if held by the same person? — A distinct, named responsibility, not assumed to be covered by the clinical lead role alone.
Evidence: Governance role documentation
Evidence: Governance role documentation
5. Does a brief, genuine statement of mission and values exist, specific to this organization? — A real, specific statement, not an absence of one on the assumption a transport service doesn’t need it.
Evidence: Mission/values statement
Evidence: Mission/values statement
Common reasons for a PARTIAL answer
- An acting lead functions informally without a formal appointment letter.
- Halt authority is assumed rather than explicitly documented.
Implementation plan
| When | What |
|---|---|
| Week 1 | Verify who is actually, currently accountable. |
| Week 2 | Issue or update the formal appointment letter with explicit authority. |
| Week 3 | Brief all crew directly and update the organizational chart. |
| Ongoing | Review this appointment whenever the role changes hands. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| ASK | Crew interview | Asks crew members separately who holds clinical accountability, without prompting. |
Evidence base
Joint Commission International. Accreditation Standards for Medical Transport Organizations, 1st ed. Oak Brook (IL): JCI; 2021.
7.2
Incident Reporting and Root-Cause Investigation
Non-Negotiable
Every clinical or safety incident is logged in a single system and investigated to identify root cause, not only the immediate symptom, with corrective action tracked to completion.
In plain terms: Every incident is logged in one place and genuinely investigated for the real reason it happened — not just “crew error” — with fixes actually tracked through to done.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
“Crew error” as a complete investigation finding is almost always incomplete — what allowed the error to occur is the genuine root cause, and stopping short of identifying it leaves the underlying condition fully intact to produce the same failure again. Fragmented, informal incident tracking across different staff members makes any real trend analysis or systematic investigation effectively impossible.
What good looks like
- A single incident log captures every reported event.
- Investigation identifies root cause beyond “crew error.”
- Corrective action is tracked to actual completion with a named owner.
Common failure modes
- Incidents are tracked informally across different staff, nothing centralized.
- Investigation stops at “crew error” with no deeper analysis.
- Corrective actions are agreed but never tracked through to completion.
Worked example
In practice
A repeated medication administration documentation error.
BeforeTwo similar documentation errors occurred within a month, each closed with “crew retrained,” with no investigation into why both involved the same busy handoff point between two specific crew pairings.
ActionAfter the second incident, the clinical lead investigated further and found both involved an ambiguous documentation field design that different crew interpreted differently. The corrective action redesigned the field, not just retrained the crew.
AfterThe Monitor reviewed the investigation record and found a genuine root cause beyond crew error, plus a documented effectiveness check confirming the redesigned field eliminated the recurring error. Criterion verified.
If you are starting from zero — do this first
- Build a single, centralized incident log if none exists.
- Review recent incidents for root-cause depth beyond “crew error.”
- Add a corrective action tracker with named owners and completion dates.
The most common mistake: Closing an incident investigation with “crew retrained” as both the finding and the complete fix, without asking what in the process or design allowed the error to happen in the first place.
Self-assessment questions
1. Does a single incident log exist capturing every reported event, not scattered informal records? — Fragmented, informal tracking makes trend analysis and real investigation impossible.
Evidence: Incident log
Evidence: Incident log
2. Pick a recent incident — does the investigation identify a root cause beyond “crew error”? — What allowed the error to happen is the root cause, not the error itself.
Evidence: Investigation record
Evidence: Investigation record
3. Is corrective action tracked to actual completion, with a named owner and date? — Agreed actions with no follow-through accomplish nothing.
Evidence: Corrective action tracker
Evidence: Corrective action tracker
Common reasons for a PARTIAL answer
- Investigations stop at the first obvious explanation.
- Corrective actions are agreed verbally but not formally tracked.
Implementation plan
| When | What |
|---|---|
| Week 1 | Build or consolidate a single incident log. |
| Week 2 | Train investigators on basic root-cause technique. |
| Week 3 | Build a corrective action tracker with owners and dates. |
| Ongoing | Review incident trends for recurring patterns. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Incident and corrective action review | Selects a recent incident and assesses root-cause depth and corrective action completion. |
Evidence base
Joint Commission International. Accreditation Standards for Medical Transport Organizations, 1st ed. Oak Brook (IL): JCI; 2021.
7.3
Internal Audit, On a Fixed Schedule
Core
The organization’s full operation is internally audited at least annually against a documented schedule, covering vehicles, crew records, and documentation across every base location, not only the most convenient to review.
In plain terms: Every base location gets genuinely audited on a real schedule — not just the main office, with a satellite base conveniently skipped.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
A satellite or remote base location excluded from audit scope, often simply because it’s less convenient to reach, creates exactly the kind of blind spot where gaps accumulate unnoticed. Audit findings need enough genuine detail for someone outside the audit to understand what was actually checked, rather than a checklist of ticks with no real substance behind it.
What good looks like
- The audit schedule explicitly covers every base location.
- The most recent audit actually happened on or near its scheduled date.
- Audit findings are detailed enough for someone outside the audit to understand.
Common failure modes
- A remote or satellite base is quietly excluded from audit scope.
- Audits slip significantly behind schedule with no tracking of the slippage.
- Findings are a checklist of ticks with no real substantive detail.
Worked example
In practice
An organization with a main base and a smaller satellite location two hours away.
BeforeThree consecutive annual audits covered the main base thoroughly. The satellite base, requiring a longer trip to reach, had never once been included — it simply wasn’t on anyone’s audit list.
ActionThe organization built a formal multi-year audit cycle explicitly naming both locations, with the satellite base’s audit scheduled on the shared organizational calendar, visible to all staff.
AfterThe Monitor reviewed the schedule and confirmed the satellite base’s first audit had been completed on time, with detailed findings on file. Criterion verified.
If you are starting from zero — do this first
- List every base location the organization operates.
- Check which of these your current or most recent audit actually covered.
- Build a multi-year cycle that explicitly includes every location.
The most common mistake: A satellite or harder-to-reach base location quietly falls outside the audit scope because nobody explicitly included it when the schedule was first built.
Self-assessment questions
1. Does the audit schedule explicitly cover every base location, not only headquarters? — A satellite or remote base that’s never included in audit scope is a specific, checkable gap.
Evidence: Audit schedule
Evidence: Audit schedule
2. Did the most recent audit actually happen on or near its scheduled date? — A schedule that’s routinely missed is not functioning.
Evidence: Audit completion records
Evidence: Audit completion records
3. Are audit findings detailed enough that someone outside the audit could understand what was actually checked? — A checklist with ticks and no detail is not a usable audit record.
Evidence: Audit report
Evidence: Audit report
Common reasons for a PARTIAL answer
- A satellite location was never explicitly added to audit scope.
- Audits happen but findings are too brief to act on.
Implementation plan
| When | What |
|---|---|
| Week 1 | List every base location requiring audit coverage. |
| Week 2 | Build a multi-year cycle with explicit scheduled dates for each. |
| Week 3 | Share the schedule and assign an auditor to the first session. |
| Ongoing | Track schedule adherence and escalate any slippage. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Schedule and report review | Checks the audit schedule’s completeness against all actual base locations. |
Evidence base
International Organization for Standardization. ISO 19011:2018, Guidelines for auditing management systems. Geneva: ISO; 2018.
7.4
Complaints Logged, Investigated, Closed
Core
Every complaint, from patient, family, or receiving facility, is logged in a single register, investigated, and closed with a documented outcome communicated back to the complainant where contact information exists.
In plain terms: Every complaint, from anyone, gets written down in one place, actually investigated, and the person who complained finds out what happened.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
A complaint resolved verbally in the moment, with nothing logged, is effectively invisible to the organization’s quality system — it cannot inform trend analysis or prevention, and leaves no record the concern was genuinely taken seriously. Complaints from receiving facilities about handover quality or communication are a particularly direct, valuable signal for this kind of organization, and are easy to lose if not formally captured.
What good looks like
- A single complaints register captures every complaint, regardless of source.
- Each entry has a documented investigation outcome.
- The complainant is informed of the outcome where contact exists.
Common failure modes
- Complaints handled verbally in the moment are never logged.
- Receiving facility complaints about handover quality go uncaptured.
- A complaint is received but the outcome is never communicated back.
Worked example
In practice
A receiving facility raising a concern about handover quality.
BeforeA receiving nurse mentioned to crew that a recent handover felt rushed and incomplete. The comment was passed along informally but never formally logged as a complaint, and no investigation followed.
ActionThe organization built a complaints register explicitly including a category for receiving facility feedback, with crew trained to log any such comment formally rather than treating it as informal conversation.
AfterThe Monitor reviewed the register and found a subsequent receiving facility complaint logged, investigated, and closed with a callback confirming the outcome to the complainant. Criterion verified.
If you are starting from zero — do this first
- Build a single complaints register covering all sources, including receiving facilities.
- Brief crew that informal feedback still counts and needs logging.
- Build a step to close the loop with the complainant.
The most common mistake: Treating a complaint or concern raised informally, especially from a receiving facility during a routine handover, as a casual comment rather than something requiring formal logging.
Self-assessment questions
1. Does a single complaints register exist, or are complaints handled informally by whoever receives them? — Complaints handled verbally and never logged are effectively invisible to the quality system.
Evidence: Complaints register
Evidence: Complaints register
2. Is there a documented outcome for each logged complaint? — Receipt without resolution is not complaint handling.
Evidence: Investigation outcome record
Evidence: Investigation outcome record
3. Was the complainant actually informed of the outcome where contact information exists? — Closing a complaint internally without telling the person who raised it undermines trust.
Evidence: Callback or communication record
Evidence: Callback or communication record
Common reasons for a PARTIAL answer
- Informal feedback from receiving facilities isn’t consistently logged.
- Outcomes aren’t consistently communicated back to complainants.
Implementation plan
| When | What |
|---|---|
| Week 1 | Build or consolidate a single complaints register. |
| Week 2 | Brief crew that informal feedback requires formal logging. |
| Week 3 | Add a required closing-the-loop step. |
| Ongoing | Trend complaint types quarterly for recurring themes. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Register review | Selects a logged complaint and verifies investigation outcome and complainant communication. |
Evidence base
Joint Commission International. Accreditation Standards for Medical Transport Organizations, 1st ed. Oak Brook (IL): JCI; 2021.
7.5
Management Review, With Minutes and Actions
Standard
Senior management formally reviews organizational quality and safety performance at least annually, with documented minutes covering incidents, complaints, and audit findings, and tracked output actions with owners and dates.
In plain terms: Leadership genuinely sits down once a year, looks at real incident and complaint data, writes down what they decided, and someone checks those decisions actually get done.
| Transport category | Standalone MTO | Hospital-operated | Ambulance service |
|---|---|---|---|
| Applicability | Full | Full | Full |
Why this matters
Management review is where quality data is meant to actually reach the people with authority to allocate resources and set direction. A review that covers operational and budget matters thoroughly while quality-specific inputs — incidents, complaints, audit findings — get only a passing mention isn’t functioning as a genuine quality review, regardless of how well-attended the meeting is.
What good looks like
- Documented minutes with named attendees exist for the most recent cycle.
- Minutes specifically cover incidents, complaints, and audit findings.
- Output actions from the previous review are traceable to completion.
Common failure modes
- Review happens but focuses on operations and budget, not quality inputs.
- No written minutes exist, just a verbal assurance it happened.
- Agreed actions from the previous review were never followed up.
Worked example
In practice
An organization’s first formal management review cycle.
BeforeAnnual “management review” consisted of leadership briefly mentioning operational metrics during a general planning meeting, with no structured coverage of incidents, complaints, or audit findings, and no written minutes.
ActionThe organization instituted a formal annual review with a fixed agenda explicitly covering incidents, complaints, and audit findings, with written minutes and an action tracker assigning owners and dates to every output decision.
AfterThe Monitor reviewed minutes from the most recent cycle and the action tracker, confirming prior actions were completed on time or had documented, reasonable extensions. Criterion verified.
If you are starting from zero — do this first
- Set a fixed annual date for the formal management review.
- Build an agenda explicitly covering incidents, complaints, and audit findings.
- Take real minutes and assign owners to every output action.
The most common mistake: Holding a review that covers operational and budget topics thoroughly while quality-specific inputs like incidents and complaints receive only a brief, passing mention.
Self-assessment questions
1. Do management review minutes exist for the most recent cycle, with named attendees? — Not a verbal assurance that “we discussed it.”
Evidence: Signed meeting minutes
Evidence: Signed meeting minutes
2. Do the minutes cover incidents, complaints, and audit findings specifically? — A review that only covers budget and operations is not a quality review.
Evidence: Meeting agenda and minutes
Evidence: Meeting agenda and minutes
3. Are output actions from the previous review traceable to completion? — Actions agreed and never followed up are a common, specific failure.
Evidence: Action tracker
Evidence: Action tracker
Common reasons for a PARTIAL answer
- Minutes exist but omit specific coverage of quality inputs.
- Actions are agreed verbally but never tracked to closure.
Implementation plan
| When | What |
|---|---|
| Week 1 | Set the annual review date and build a structured agenda template. |
| Week 2 | Gather required inputs — incident, complaint, and audit data. |
| Week 3 | Hold the review, take formal minutes, assign action owners and dates. |
| Ongoing | Track output actions to completion before the next cycle. |
How the Monitor verifies this
| Method | What | Detail |
|---|---|---|
| DOCUMENT | Minutes and action tracker review | Confirms minutes cover required quality inputs and checks prior action completion status. |
Evidence base
Joint Commission International. Accreditation Standards for Medical Transport Organizations, 1st ed. Oak Brook (IL): JCI; 2021.