Accréditation Sans Frontières

International Accreditation of Healthcare Facilities

Telemedicine Standards · Standard 4

Emergency Escalation for the Remote Patient

ASF-TM-STD3-v3.0  ·  Published  ·  12 September 2026  ·  113 pages  ·  10 chapters

STANDARD 4

Emergency Escalation for the Remote Patient

MANDATORY

5 criteria

  Standard 4.1 NON-NEGOTIABLE · Standard 4: Emergency Escalation for the Remote Patient
Patient Location Is Confirmed at the Start of Every Session
ASSESSMENT
ASF-TM-STD4-v3.0
CR FULL TR FULL SM FULL ST FULL
4.1
NON-NEGOTIABLE
L1
THE STANDARD
Patient Location Is Confirmed at the Start of Every Session
The patient's actual, current location is genuinely confirmed at the start of every single session — not assumed from an intake record or a prior visit, given that a patient's real location on any given day can genuinely differ from what's on file, and this is exactly the information an emergency response would need most.
SERVICE SELF-ASSESSMENT Tick YES, PARTIAL, or NO for each question.
1 Is the patient's actual, current location genuinely confirmed at the start of every single session?
Real, active confirmation every session, not assumed from intake or a prior visit.
Doc: Session-start location confirmation record
YES PARTIAL NO
2 Is this confirmation specific enough to guide an actual emergency response — not just a general city or region?
Real, specific detail sufficient for genuine emergency dispatch, not a vague general area.
Doc: N/A — tested directly
YES PARTIAL NO
3 Does a location differing from what's on file trigger any specific, genuine documentation or awareness?
Real, active awareness of a location change, not silently overwritten or ignored.
Doc: Location change documentation
YES PARTIAL NO

ALL YES Standard likely met. ANY PARTIAL Improvement plan required. ANY NO Blocks accreditation until resolved.

WHAT THE ASSESSOR DOES ON SITE no surprises, no hidden checks
OBSERVE
Session-start confirmation observation
Observes an actual session opening for genuine, specific location confirmation.
DOCUMENT
Confirmation specificity review
Reviews documented location confirmations for genuine, actionable specificity.
DOCUMENT
Location change awareness review
Reviews whether a location differing from file triggers genuine documentation.

REFERENCES

  1. [16] Genuine confirmation of a client's physical location at the start of every single session, not reliance on intake records, is established as essential telehealth crisis protocol, because not knowing where a patient actually is can be the difference between emergency help arriving and not arriving.
  Standard 4.1 · Standard 4: Emergency Escalation for the Remote Patient
Guidance & Learning
GUIDANCE
ASF-TM-STD4-v3.0
WHY THIS STANDARD EXISTS

A real documented case shows precisely why this matters: a patient in genuine crisis was actually located many hours from her home on the day of the emergency, and the provider was only able to activate emergency services in the correct jurisdiction because current location had been genuinely established — had the provider relied on the address on file, that emergency response would have gone to the wrong place entirely.

The evidence: [16] Genuine confirmation of a client's physical location at the start of every single session, not reliance on intake records, is established as essential telehealth crisis protocol, because not knowing where a patient actually is can be the difference between emergency help arriving and not arriving.
WHAT GOOD LOOKS LIKE
✓ Actual, current location is genuinely confirmed at the start of every session.
✓ Confirmation is specific enough to genuinely guide an emergency response.
✓ A location change from what's on file triggers genuine documentation and awareness.
WHAT FAILURE LOOKS LIKE
✗ Location is assumed from intake or a prior visit, not confirmed each session.
✗ Confirmation is vague, insufficient for genuine emergency dispatch.
✗ A location change goes unnoticed or undocumented.
MOST COMMON REASONS SERVICES SCORE PARTIAL

1 Confirmation happens reliably for new patients but lapses into assumption for established, long-term patients.

An established patient's actual location can change just as genuinely as a new patient's, and deserves the same confirmation.

2 Confirmation is verbal but not specifically documented in a way that's genuinely retrievable during an actual emergency.

Documentation that's difficult to retrieve quickly doesn't provide real, usable protection in an actual crisis.

3 Confirmation happens for scheduled visits but is inconsistent for urgent or same-day sessions.

Every session, regardless of how it was scheduled, carries the same real emergency preparedness need.

HOW TO IMPLEMENT IF YOU ARE STARTING FROM ZERO

Week 1 Review current location confirmation practice for genuine consistency across all patients and session types.

Week 2 Establish a specific, mandatory location confirmation step at the start of every session.

Week 3 Build genuine documentation practice for location changes from what's on file.

Ongoing Audit confirmation consistency across established and new patients alike.

FOR SURVEYORS — WHAT IS NOT OBVIOUS

Observe an actual session opening to confirm location is genuinely, specifically confirmed.

Direct observation reveals genuine practice, not an assumption from stated policy.

Ask a long-term patient whether they're asked to confirm their location at the start of each session.

This tests whether the practice genuinely extends to established patients, not just new ones.

E-LEARNING academy.gmj.ge/tm-std4-1-session-location-confirmation — 30 min · complete before self-assessment
  Standard 4.2 NON-NEGOTIABLE · Standard 4: Emergency Escalation for the Remote Patient
A Specific, Tiered Emergency Activation Protocol Exists
ASSESSMENT
ASF-TM-STD4-v3.0
CR FULL TR FULL SM FULL ST FULL
4.2
NON-NEGOTIABLE
L1
THE STANDARD
A Specific, Tiered Emergency Activation Protocol Exists
A specific, tiered protocol exists for activating emergency services — direct local activation where covered, a patient-reported local dispatch number where standard coverage doesn't reach, and a relay mechanism connecting the provider to local emergency services as a further alternative — not a single, undifferentiated assumption that dialing a standard emergency number will always work regardless of the patient's actual location.
SERVICE SELF-ASSESSMENT Tick YES, PARTIAL, or NO for each question.
1 Does a specific, tiered protocol exist for activating emergency services across different location scenarios?
A real, multi-tiered protocol, not a single method assumed to work everywhere.
Doc: Tiered emergency activation protocol documentation
YES PARTIAL NO
2 Are providers genuinely trained on all tiers of this protocol, not only the most common, direct method?
Real, complete training across every tier, not familiarity with the simplest scenario alone.
Doc: Provider protocol training record
YES PARTIAL NO
3 Has this protocol genuinely been tested or rehearsed, not only described in written policy?
Real, tested practice, not a protocol that exists only on paper.
Doc: Protocol testing record
YES PARTIAL NO

ALL YES Standard likely met. ANY PARTIAL Improvement plan required. ANY NO Blocks accreditation until resolved.

WHAT THE ASSESSOR DOES ON SITE no surprises, no hidden checks
DOCUMENT
Protocol documentation review
Reviews the actual, specific, tiered emergency activation protocol.
DOCUMENT
Training completeness review
Reviews training records for genuine coverage of all protocol tiers, not the simplest scenario alone.
DOCUMENT
Testing record review
Reviews evidence the protocol has genuinely been tested or rehearsed.

REFERENCES

  1. [17] A documented telehealth emergency management protocol establishes a three-tiered emergency activation process: direct local emergency service activation where standard coverage exists, a patient-reported local dispatch number where it doesn't, and an e911 relay center connecting the clinician to local emergency services as a further alternative.
  Standard 4.2 · Standard 4: Emergency Escalation for the Remote Patient
Guidance & Learning
GUIDANCE
ASF-TM-STD4-v3.0
WHY THIS STANDARD EXISTS

Not every location a patient might genuinely be in has the same standard emergency service coverage, and a provider who only knows one method for activating emergency services has no real plan for the situations where that method doesn't apply — a genuine, tiered protocol is what ensures emergency activation remains possible across the real range of locations a patient could actually be in.

The evidence: [17] A documented telehealth emergency management protocol establishes a three-tiered emergency activation process: direct local emergency service activation where standard coverage exists, a patient-reported local dispatch number where it doesn't, and an e911 relay center connecting the clinician to local emergency services as a further alternative.
WHAT GOOD LOOKS LIKE
✓ A specific, tiered protocol genuinely exists for varying location scenarios.
✓ Providers are genuinely trained on all tiers, not just the most common method.
✓ The protocol has genuinely been tested, not only described in policy.
WHAT FAILURE LOOKS LIKE
✗ Only a single emergency activation method is known, assumed to work everywhere.
✗ Training covers only the most common, direct activation method.
✗ The protocol exists only in writing, never tested or rehearsed.
MOST COMMON REASONS SERVICES SCORE PARTIAL

1 Providers know the direct activation method well but are less confident with the relay center alternative.

Every tier deserves the same genuine provider confidence, since any tier might be the one actually needed.

2 The protocol is documented but hasn't been updated to reflect current relay center contact information.

An outdated contact detail can undermine the entire protocol's genuine, real functionality when actually needed.

3 The protocol has been reviewed internally but never tested through an actual simulated emergency scenario.

An untested protocol may not hold up reliably during a genuine, real-time emergency.

HOW TO IMPLEMENT IF YOU ARE STARTING FROM ZERO

Week 1 Review current emergency activation knowledge for genuine coverage of all protocol tiers.

Week 2 Establish or update the specific, tiered protocol with current contact information.

Week 3 Train all providers on every tier, not the most common scenario alone.

Ongoing Test the protocol periodically through simulated emergency scenarios.

FOR SURVEYORS — WHAT IS NOT OBVIOUS

Ask a provider to walk through all three tiers of the emergency activation protocol, not just the simplest one.

A specific, complete answer reveals genuine, full training, not familiarity with one method alone.

Ask when the protocol was last genuinely tested through a simulated scenario.

A specific, real answer reveals genuine practice, not a protocol that exists only on paper.

E-LEARNING academy.gmj.ge/tm-std4-2-tiered-emergency-protocol — 30 min · complete before self-assessment
  Standard 4.3 NON-NEGOTIABLE · Standard 4: Emergency Escalation for the Remote Patient
The Provider Remains Connected Until Emergency Services Have Genuinely Taken Over Care
ASSESSMENT
ASF-TM-STD4-v3.0
CR FULL TR FULL SM FULL ST FULL
4.3
NON-NEGOTIABLE
L1
THE STANDARD
The Provider Remains Connected Until Emergency Services Have Genuinely Taken Over Care
When emergency services are activated during a session, the provider genuinely stays connected with the patient until local emergency responders have arrived and care has actually been transferred — not disconnecting once the call for help has been made, leaving the patient alone in the interval before help physically arrives.
SERVICE SELF-ASSESSMENT Tick YES, PARTIAL, or NO for each question.
1 Does the provider genuinely remain connected with the patient until emergency responders have actually arrived?
Real, continuous connection through the full interval, not disconnecting once the call is made.
Doc: N/A — tested directly
YES PARTIAL NO
2 Is care genuinely, actively transferred to responders, not simply the session ending once they're present?
Real, active handoff of relevant information to responders, not a passive disconnection.
Doc: N/A — tested directly
YES PARTIAL NO
3 Is this expectation specifically, clearly trained, not left to individual provider judgment in the moment?
Real, specific training on this expectation, not assumed instinctive behavior under crisis pressure.
Doc: Provider training on remaining connected
YES PARTIAL NO

ALL YES Standard likely met. ANY PARTIAL Improvement plan required. ANY NO Blocks accreditation until resolved.

WHAT THE ASSESSOR DOES ON SITE no surprises, no hidden checks
ASK
Provider practice interview
Asks a provider to describe what they would do, and when they would disconnect, during an actual emergency activation.
DOCUMENT
Training review
Reviews training records confirming providers are specifically trained to remain connected through handoff.
DOCUMENT
Real event review
Reviews documentation from a genuine past emergency event, where available, for evidence of continued connection through handoff.

REFERENCES

  1. [18] Established telehealth emergency management protocol specifically requires clinicians to remain connected on the session with the patient until local emergency services arrive on scene and care is genuinely transferred, only disconnecting once that handoff has actually occurred.
  Standard 4.3 · Standard 4: Emergency Escalation for the Remote Patient
Guidance & Learning
GUIDANCE
ASF-TM-STD4-v3.0
WHY THIS STANDARD EXISTS

The real gap between activating emergency services and responders actually arriving on scene is exactly when a patient in crisis is most vulnerable and most alone, and a provider who disconnects once the call is made abandons the patient during precisely this interval — remaining connected through genuine handoff is what makes emergency activation an actual continuation of care, not simply a referral out.

The evidence: [18] Established telehealth emergency management protocol specifically requires clinicians to remain connected on the session with the patient until local emergency services arrive on scene and care is genuinely transferred, only disconnecting once that handoff has actually occurred.
WHAT GOOD LOOKS LIKE
✓ Providers genuinely remain connected until emergency responders have actually arrived.
✓ Care is genuinely, actively transferred to responders, not a passive disconnection.
✓ This expectation is specifically, clearly trained, not left to individual judgment.
WHAT FAILURE LOOKS LIKE
✗ Providers disconnect once the emergency call is made, before responders arrive.
✗ The session ends without any genuine, active handoff to responders.
✗ No specific training establishes this expectation.
MOST COMMON REASONS SERVICES SCORE PARTIAL

1 The expectation is generally understood but the specific point of appropriate disconnection isn't clearly defined.

A specific, clear definition of when handoff has genuinely occurred provides more reliable guidance than general understanding alone.

2 Training addresses this for adult patients but hasn't specifically been extended to pediatric or otherwise vulnerable patient scenarios.

Every patient population deserves the same genuine commitment to remaining connected through handoff.

3 Providers report they would remain connected but this hasn't been specifically confirmed through a real or simulated event.

Stated intention isn't the same as confirmed behavior under genuine, real-time pressure.

HOW TO IMPLEMENT IF YOU ARE STARTING FROM ZERO

Week 1 Review current provider understanding of remaining connected through emergency handoff.

Week 2 Establish specific, clear training on this expectation, including the defined point of appropriate disconnection.

Week 3 Extend training to cover the full range of relevant patient populations.

Ongoing Confirm this practice through review of real events or simulated scenarios.

FOR SURVEYORS — WHAT IS NOT OBVIOUS

Ask a provider directly when they would consider it appropriate to disconnect during an emergency activation.

A specific, confident answer reveals genuine, trained understanding, not an assumption of instinctive good judgment.

Review documentation from a real past emergency event, where one exists, for evidence of continued connection.

A real, documented example reveals genuine practice, not a stated intention.

E-LEARNING academy.gmj.ge/tm-std4-3-remain-connected-through-handoff — 30 min · complete before self-assessment
  Standard 4.4 NON-NEGOTIABLE · Standard 4: Emergency Escalation for the Remote Patient
Emergency Contacts Are Genuinely Verified as Aware and Willing
ASSESSMENT
ASF-TM-STD4-v3.0
CR FULL TR FULL SM FULL ST FULL
4.4
NON-NEGOTIABLE
L1
THE STANDARD
Emergency Contacts Are Genuinely Verified as Aware and Willing
A patient's designated emergency contact is genuinely verified as aware of and willing to serve in that role — not simply a name and number listed on an intake form without any actual confirmation that this person knows they've been named or agrees to it.
SERVICE SELF-ASSESSMENT Tick YES, PARTIAL, or NO for each question.
1 Is the designated emergency contact genuinely verified as aware of and willing to serve in that role?
Real, active verification, not a name listed without actual confirmation.
Doc: Emergency contact verification record
YES PARTIAL NO
2 Does the patient have both a primary and secondary emergency contact, each genuinely verified?
Real, verified coverage for both a primary and a genuine backup, not reliance on a single, unconfirmed contact.
Doc: N/A — tested directly
YES PARTIAL NO
3 Is verification genuinely reconfirmed periodically, not assumed to remain accurate indefinitely?
Real, periodic reconfirmation, not a one-time check assumed valid forever.
Doc: Periodic reconfirmation record
YES PARTIAL NO

ALL YES Standard likely met. ANY PARTIAL Improvement plan required. ANY NO Blocks accreditation until resolved.

WHAT THE ASSESSOR DOES ON SITE no surprises, no hidden checks
DOCUMENT
Verification record review
Reviews evidence of genuine verification that emergency contacts are aware and willing.
DOCUMENT
Primary and secondary coverage review
Reviews whether both a primary and secondary contact are genuinely designated and verified.
DOCUMENT
Reconfirmation schedule review
Reviews whether verification is periodically reconfirmed, not treated as permanently valid.

REFERENCES

  1. [19] Genuine designation of primary and secondary emergency contacts requires a verification step confirming the contact has been informed and is willing to serve in that role, distinct from a name and number recorded without active confirmation.
  Standard 4.4 · Standard 4: Emergency Escalation for the Remote Patient
Guidance & Learning
GUIDANCE
ASF-TM-STD4-v3.0
WHY THIS STANDARD EXISTS

An emergency contact who doesn't actually know they've been designated, or who wasn't genuinely asked whether they're willing, provides no real, reliable support in an actual crisis — the whole protective value of this designation depends on it reflecting a genuine, confirmed relationship, not an assumption based on a name the patient happened to write down.

The evidence: [19] Genuine designation of primary and secondary emergency contacts requires a verification step confirming the contact has been informed and is willing to serve in that role, distinct from a name and number recorded without active confirmation.
WHAT GOOD LOOKS LIKE
✓ Emergency contacts are genuinely verified as aware and willing to serve.
✓ Both a primary and secondary contact are designated and genuinely verified.
✓ Verification is periodically reconfirmed, not assumed to remain accurate indefinitely.
WHAT FAILURE LOOKS LIKE
✗ Contacts are listed without any genuine verification of awareness or willingness.
✗ Only a single, unconfirmed contact exists, with no verified backup.
✗ Verification, if it happened, was never reconfirmed and may be outdated.
MOST COMMON REASONS SERVICES SCORE PARTIAL

1 Primary contacts are genuinely verified but secondary contacts are recorded without the same active confirmation.

A secondary contact carries the same real, genuine importance as a backup, deserving the same verification.

2 Verification happened at intake but hasn't been reconfirmed even as significant time has passed.

A relationship or willingness can genuinely change over time, and periodic reconfirmation reflects this reality.

3 Verification is documented as complete but the actual method of confirmation isn't specifically recorded.

Specific documentation of how verification occurred provides more genuine assurance than a completed checkbox alone.

HOW TO IMPLEMENT IF YOU ARE STARTING FROM ZERO

Week 1 Review current emergency contact designation for genuine verification versus unconfirmed listing.

Week 2 Establish a specific, active verification process for both primary and secondary contacts.

Week 3 Build a periodic reconfirmation schedule.

Ongoing Audit emergency contact verification for continued accuracy.

FOR SURVEYORS — WHAT IS NOT OBVIOUS

Ask to see the specific documentation of how a real emergency contact's willingness was actually confirmed.

A real, specific record reveals genuine verification, not an assumption based on a listed name.

Ask when emergency contact verification was last reconfirmed for a long-term patient.

A specific, real answer reveals genuine, ongoing practice, not a one-time check.

E-LEARNING academy.gmj.ge/tm-std4-4-emergency-contact-verification — 30 min · complete before self-assessment
  Standard 4.5 CORE · Standard 4: Emergency Escalation for the Remote Patient
A Specific Threshold Exists for When Telehealth Is No Longer Clinically Appropriate
ASSESSMENT
ASF-TM-STD4-v3.0
CR N/A TR FULL SM ADAPTED ST FULL
4.5
CORE
L1
THE STANDARD
A Specific Threshold Exists for When Telehealth Is No Longer Clinically Appropriate
A specific, defined threshold exists for recognizing when telehealth is no longer clinically appropriate for a given patient's situation and a higher level of care must be facilitated — not continuing remote sessions indefinitely because no clear point was ever established for when this shift should genuinely occur.
SERVICE SELF-ASSESSMENT Tick YES, PARTIAL, or NO for each question.
1 Does a specific, defined threshold exist for recognizing when telehealth is no longer clinically appropriate?
A real, specific threshold, not an undefined, case-by-case judgment made in the moment.
Doc: Level-of-care threshold documentation
YES PARTIAL NO
2 Are providers genuinely trained to recognize this threshold, not left to develop their own individual sense of it?
Real, specific training on the defined threshold, not assumed clinical instinct alone.
Doc: Provider threshold training record
YES PARTIAL NO
3 When this threshold is reached, is there a genuine, defined process for facilitating a higher level of care?
A real, specific facilitation process, not the threshold being recognized without a clear next step.
Doc: Higher-level-of-care facilitation process
YES PARTIAL NO

ALL YES Standard likely met. ANY PARTIAL Improvement plan required. ANY NO Requires improvement plan.

WHAT THE ASSESSOR DOES ON SITE no surprises, no hidden checks
DOCUMENT
Threshold documentation review
Reviews the specific, defined threshold for when telehealth is no longer clinically appropriate.
DOCUMENT
Training review
Reviews training records confirming providers are specifically trained to recognize this threshold.
DOCUMENT
Facilitation process review
Reviews the defined process for facilitating a higher level of care once the threshold is reached.

REFERENCES

  1. [20] Established telehealth crisis protocol specifically addresses when telehealth is no longer clinically appropriate and a higher level of care needs to be facilitated, establishing a defined threshold as necessary practice, distinct from indefinite continuation of remote sessions without a clear transition point.
  Standard 4.5 · Standard 4: Emergency Escalation for the Remote Patient
Guidance & Learning
GUIDANCE
ASF-TM-STD4-v3.0
WHY THIS STANDARD EXISTS

Some patient situations genuinely exceed what telehealth alone can safely manage, and without a specific, defined threshold for recognizing this, a provider may continue remote sessions well past the point where a higher level of care should have already been facilitated — a real, clear threshold is what prevents this drift from happening gradually and going unnoticed.

The evidence: [20] Established telehealth crisis protocol specifically addresses when telehealth is no longer clinically appropriate and a higher level of care needs to be facilitated, establishing a defined threshold as necessary practice, distinct from indefinite continuation of remote sessions without a clear transition point.
WHAT GOOD LOOKS LIKE
✓ A specific, defined threshold genuinely exists for this determination.
✓ Providers are specifically trained to recognize this threshold, not relying on individual instinct alone.
✓ A genuine, defined process facilitates a higher level of care once the threshold is reached.
WHAT FAILURE LOOKS LIKE
✗ No specific threshold exists; the determination is left to undefined, case-by-case judgment.
✗ Providers aren't specifically trained; recognition depends on individual instinct.
✗ The threshold, if recognized, doesn't lead to any defined facilitation process.
MOST COMMON REASONS SERVICES SCORE PARTIAL

1 A general principle is understood but the specific, defined threshold criteria aren't documented.

Documented, specific criteria provide more consistent, reliable recognition than general principle alone.

2 The threshold is well understood for acute crisis situations but less clearly defined for gradually deteriorating ones.

Gradual deterioration deserves the same genuine, defined threshold as acute presentations, since drift can be harder to notice.

3 A facilitation process exists but doesn't specify a genuine, named pathway to the actual higher level of care.

A real, named pathway is what makes facilitation actionable, not a process that ends at recognition alone.

HOW TO IMPLEMENT IF YOU ARE STARTING FROM ZERO

Week 1 Review current practice for a genuine, defined threshold versus undefined case-by-case judgment.

Week 2 Establish specific, documented threshold criteria, including for gradual deterioration.

Week 3 Train providers on recognizing this threshold and the defined facilitation process.

Ongoing Review threshold application against real, recent cases for consistency.

FOR SURVEYORS — WHAT IS NOT OBVIOUS

Ask a provider to describe the specific criteria that would tell them telehealth is no longer appropriate for a patient.

A specific, confident answer reveals genuine, defined understanding, not undefined individual judgment.

Ask for a real, recent example of a patient transitioned to a higher level of care and what specifically prompted it.

A real, traceable example reveals whether this threshold genuinely functions in practice.

E-LEARNING academy.gmj.ge/tm-std4-5-higher-level-of-care-threshold — 30 min · complete before self-assessment

Test your facility against this standard

Open self-assessment — no login, no fee.

Start the self-assessment

QR code
QR Code
Scan to open.
Print to share.
DocumentDownload QR
© 2026 Accréditation Sans Frontières · PHIG · Sheni Network