An evidence-based evaluation of clinical pathways, operational coordination, and system-level measurement gaps in a regional EMS system in Poland.
Evidence key: Observed = directly documented observation (none separately specified in the source); Reported = stated in the source, including self-reported figures; Calculated = a value transparently derived from source data (no new calculated outcome is presented); Not Measured = the source lacks that measure; Proposed = future work or a working target. Reported figures require validation.
01 · SUMMARY
What MOST Evaluated
The assessment describes a functioning, high-volume prehospital STEMI pathway with reported formal protocols, ECG teletransmission, direct catheterization-laboratory contact, and standardized handoff. The central limitation is the absence of validated case-level visibility into deterioration, escalation, receiving-center acceptance, repeated contact attempts, routing decisions, and shock-resource access. These are gaps in available evidence—not demonstrated clinical failures.
ReportedLegacy/self-reported; case overlap unverified
Scope and limitations
The scope covered prehospital STEMI and suspected cardiogenic shock, including interfaces with receiving facilities. The source did not audit hospital emergency departments, catheterization laboratories, intensive care units, or the hospital-side interfacility transport system.
A missing measure is not evidence that a capability is absent or that clinical care failed.
Root-cause hypotheses—not findings: departure intervals may reflect stabilization, dispatch logistics, acceptance, or coordination; repeat calls may reflect decision authority, receiving capacity, incomplete communication, or necessary escalation; handoff intervals may depend on receiving-team availability and transfer-of-care definitions. These possibilities require case records and stakeholder review before causes are assigned.
02 · METHOD
Assessment methodology and evidence basis
The available report presents legacy/self-reported volume figures and timing means/ranges, qualitatively classifies ten system capabilities, and describes measurement gaps and further data needs. This is the documented basis for the analysis.
The report does not specify observation duration, sample size, direct-observation methods, stakeholder-interview details, or access to case-level datasets. We do not represent those activities as completed. Human-factors assessment using NASA-TLX, TeamSTEPPS, and SART was not conducted; simulation and such tools remain potential follow-up work.
Any follow-up review requires agreed scope, pseudonymization, permissions, and partner data approvals.
02A · DATA SPECIFICATION
Minimum data collection and validation specification
These are proposed fields and source roles to agree. Access to partner records is not assumed.
Domain
Minimum fields / controls
Source / owner to negotiate
Case / denominator
Pseudonymous case ID; date; eligibility; suspected vs confirmed STEMI; shock flag; exclusion code
EMS patient-care documentation / quality
EMS clocks
First contact; ECG acquisition/transmission; destination decision; departure; arrival; handoff; ready status
EMS records / CAD; reconcile clocks
Receiving-center coordination
All contact timestamps, recipient role, decision, acceptance status, refusal/conditional reason
Contact log and partner records
Deterioration / escalation
Documented trigger and state change; first escalation; activation; recipient
EMS chart / medical lead
Destination / resource
Intended and actual facility; bypass reason; resource inquiry; consultation and decision
EMS operations / consenting receiving partners
Human factors
Scenario, workload, communication checklist, situational-awareness measure, observer notes
Use case-level pseudonymization, least-privilege access, appropriate Polish/EU data protection processes, and formal permissions for hospital-held information. Do not imply data-sharing arrangements already exist.
03 · FINDINGS
Operational strengths and system capability status
The statuses below reproduce the source classifications. A protocol or procedure being present does not demonstrate consistent execution or outcomes.
Ten system capabilities in the source assessment
Capability assessed
Evidence status
Why it matters / proposed follow-up
Formal STEMI protocol
ReportedQualitatively confirmed / implemented
Supports a defined response framework; validate current version, access, and case-level use.
Destination-selection algorithm
ReportedQualitatively confirmed / implemented
Structures destination decisions; test actual routing, exceptions, and decision authority.
Cath-lab contact procedure
ReportedQualitatively confirmed / implemented
Defines a critical coordination step; verify timestamps and response documentation.
Direct EMS–cath-lab communication
ReportedQualitatively confirmed / implemented
Can support timely coordination; review contact records and escalation alternatives.
ECG teletransmission
ReportedQualitatively confirmed / implemented
Enables early information exchange; validate transmission and receipt timestamps.
Deterioration escalation procedure
ReportedQualitatively confirmed / implemented
Provides a route for escalation; time from recognized deterioration to first contact was not measured.
Standardized patient handoff
ReportedQualitatively confirmed / implemented
Supports continuity; define and validate the handoff event and completion time.
Formal cardiogenic shock protocol
ReportedPartially implemented; needs validation
Clarify triggers, activation roles, and pathway use with clinical leadership.
Secondary transfer / redirection procedure
ReportedPartially implemented; responsibilities need clarification
Map ownership and decision pathways across organizations; verify local rules.
Criteria to bypass nearest emergency department
ReportedUnconfirmed or not implemented in source form
Confirm policy status, legal authority, receiving capabilities, and case-level rationale.
Six reported timing indicators
Source-reported means and ranges are reproduced as given. No sample size, observation period, timestamp provenance, distribution, missingness, exclusions, or patient-level validation was supplied. A range crossing a target does not show how many cases exceeded it.
Visual of reported ranges and means (0–20 minute scale)
05101520 min
First medical contact → ECG
Mean 4 min · 2–6 min
ECG → catheterization-lab contact
Mean 5 min · 3–7 min
ECG → destination decision
Mean 5 min · 3–7 min
Decision → departure
Mean 10 min · 8–12 min
Arrival → completed handoff
Mean 15 min · 5–20 min
Arrival → unit ready
Mean 10 min · 5–15 min
Bar = reported range; marker = reported mean. This is not a case distribution or a calculated median/P90.
Interval
Reported mean
Reported range
Source working target / interpretation
First medical contact → ECG
Reported 4 min
Reported 2–6 min
≤10 min; meets target
ECG → catheterization-lab contact
Reported 5 min
Reported 3–7 min
≤10 min; meets MOST working target
ECG → destination decision
Reported 5 min
Reported 3–7 min
≤10 min; meets MOST working target
Decision → departure
Reported 10 min
Reported 8–12 min
≤10 min; mean at threshold, range includes values above target
Arrival → completed handoff
Reported 15 min
Reported 5–20 min
≤15 min; mean at threshold, range includes values above target
Arrival → unit ready
Reported 10 min
Reported 5–15 min
≤30 min; meets MOST working target
Targets other than the cited early ECG benchmark are MOST working goals, not universal clinical guideline requirements. Report median and P90 alongside means, case volume, denominator, target compliance, missing-data rates, outliers, source, and trends. Do not claim before/after improvement until validated baseline and repeat data exist.
04 · EVIDENCE GAPS
The Critical Missing Evidence
These entries separate source limitations from a validation plan. A potential vulnerability means an unanswered operational question—not an established defect in care.
GAP 01
Deterioration → escalation
Available evidence: Not measured: elapsed time from recognized deterioration to first escalation contact.
Why it matters: Without event-level timestamps, leadership cannot distinguish rapid escalation from delay or determine how often escalation is needed. This is an evidence gap, not proof of delay.
Evidence needed: Case narratives, documented trigger and state change, first escalation timestamp, recipient, and context; validate definitions with clinical leadership.
MOST proposed follow-up: MOST proposes a ≤5-minute working threshold for testing, subject to approval; use outlier review and contextual case review.
GAP 02
Shock recognition → pathway activation
Available evidence: No corresponding interval or validated activation denominator.
Why it matters: The system cannot quantify activation frequency or time from recognition to pathway response; uncommon cases make denominator and uncertainty important.
Evidence needed: Agreed clinical trigger, eligibility and exclusion criteria, recognition/activation timestamps, and all eligible cases over an agreed period.
MOST proposed follow-up: Test a proposed ≤15-minute internal measure after clinical approval; analyze shock cases separately and report small denominators.
GAP 03
Receiving-center acceptance and coordination
Available evidence: Acceptance, refusal, and conditional-acceptance time was not measured.
Why it matters: Unseen response intervals or reasons can affect destination decisions; the available report does not establish that coordination failed.
Evidence needed: Every contact start and response time, recipient role, decision, reason, and intended/actual destination, with partner permissions.
MOST proposed follow-up: Proposed ≤10-minute testable internal objective from first call to decision; review refusals and unresolved cases individually.
GAP 04
Repeated calls and communication
Available evidence: Multiple calls were described qualitatively but not counted.
Why it matters: The number, sequence, necessity, and reason for repeat contacts are unknown; repeated contact is not automatically avoidable or an error.
Evidence needed: Contact count per case, timestamps, reason codes, transfer of responsibility, and communication documentation.
MOST proposed follow-up: Track distribution and coded reasons; one contact is aspirational only, not a performance standard.
GAP 05
Destination selection and decisions
Available evidence: The destination algorithm was qualitatively confirmed; bypass criteria were unconfirmed or not implemented in the source form.
Why it matters: The report cannot establish the frequency or appropriateness of exceptions or any real-world routing deficit.
MOST proposed follow-up: Review local rules and case exceptions jointly; change policies only after appropriate clinical and legal review.
GAP 06
Specialist and advanced-resource access
Available evidence: No reliable time to specialist consultation, resource decision, or facility access; the source’s ≤60-minute goal needs a more precise event definition.
Why it matters: Consultation, decision, transport, arrival, and therapy delivery can be conflated unless each event is defined.
Evidence needed: Separate timestamps for consultation, decision, acceptance, destination, arrival, and care delivery; map actual capability.
MOST proposed follow-up: Proposed measure must distinguish MCS decision from device deployment; establish an agreed endpoint before interpreting a threshold.
GAP 07
Human factors, workload, team communication
Available evidence: NASA-TLX, TeamSTEPPS, and SART were not used in the original assessment.
Why it matters: The source cannot characterize workload, situational awareness, or team communication using those instruments.
Evidence needed: Designed scenarios, workload and communication measures, observer notes, validated instruments where suitable, and participant safeguards.
MOST proposed follow-up: Use an agreed interdisciplinary tabletop/simulation and structured evaluation as proposed follow-up, not as completed assessment activity.
05 · PROPOSED IMPROVEMENT
How MOST proposes to improve operational reliability
These are follow-up engagement proposals, not completed work.
01
Operational Pathway Mapping
Existing evidenceReported pathway elements and qualitative capability classifications.
Proposed interventionMap decision points, ownership, transfer stages, and interorganizational dependencies with stakeholders.
DeliverableValidated pathway map and process-ownership matrix.
EvaluationStakeholder sign-off; coverage of agreed pathway steps and documented exceptions.
02
Case-Level Data Validation
Existing evidenceLegacy/self-reported counts and timing summaries; no validated case-level dataset supplied.
Proposed interventionReview agreed pseudonymized cases, reconcile denominators and timestamps, classify missingness and variability.
DeliverableValidated baseline, data dictionary, evidence-gap and delay-classification register.
EvaluationSource traceability, denominator reconciliation, completeness, and reviewer agreement.
03
Clinical Escalation Standardization
Existing evidenceAn escalation procedure was qualitatively confirmed; deterioration-to-escalation time was not measured.
Proposed interventionReview triggers and communication sequence with clinical leaders; propose standardized escalation language.
DeliverableApproved trigger card and escalation workflow proposal.
EvaluationTabletop/simulation test, documentation audit, and event-level time capture.
04
Receiving-Center Communication
Existing evidenceDirect contact procedure and EMS–cath-lab communication were qualitatively confirmed; acceptance interval is unmeasured.
Proposed interventionMap calls, information exchange, response, refusal/conditional decisions, and escalation alternatives.
DeliverableContact/acceptance register and standardized handoff recommendations.
EvaluationAudit contact logs, completeness, decision traceability, and case-based review.
All work is prospective; no changes or results are represented as already completed.
Days 61–90 · Initial implementation and evaluation
Proposed activities
Pilot only approved changes; conduct targeted simulation; review dashboard; measure initial process performance; identify remaining gaps; prepare executive review.
Expected deliverables
Initial implementation findings, KPI dashboard, executive summary, and continued-monitoring recommendations.
Dependent on sponsor approval, partner participation, governance, and validated baseline data.
The source proposes review of 30 consecutive STEMI/suspected-shock cases as a practical process review—not a sample sufficient to infer rare outcomes. Review all available shock cases separately over an agreed period and report uncertainty.
07 · MEASUREMENT
Operational measurement dashboard
The six baseline indicators and proposed high-risk measures below reflect source values and recommendations. Denominators and definitions must be approved before use.
Measure
Operational definition
Available baseline
Proposed approach / target
Source & owner / cadence
First medical contact → ECG
First patient contact to ECG acquisition.
ReportedReported mean 4 min; range 2–6 min.
ProposedReport median, P90, denominator, missingness, and share ≤10 min. The source describes this target as met.
EMS record/CAD; operations & quality; monthly after validation.
ECG → cath-lab contact
ECG acquisition to first cath-lab contact.
ReportedReported mean 5 min; range 3–7 min.
ProposedMedian, P90, denominator, share ≤10 min; MOST working goal.
EMS timestamps/contact log; operations; monthly.
ECG → destination decision
ECG acquisition to documented destination decision.
ReportedReported mean 5 min; range 3–7 min.
ProposedMedian, P90, denominator, share ≤10 min; MOST working goal.
EMS/receiving records with permissions; joint quality owners; monthly.
Arrival → unit ready
Arrival to source-defined unit-ready status.
ReportedReported mean 10 min; range 5–15 min.
ProposedConfirm definition, then median/P90 and share ≤30 min; MOST working goal.
EMS record; operations; monthly.
Deterioration → escalation
Recognized deterioration to first escalation contact.
Not measuredNot measured.
ProposedProposed ≤5 min, subject to clinical approval; include denominator and exceptions.
Case record/call log; medical lead and quality; monthly review.
Shock recognition → activation
Agreed shock trigger to pathway activation.
Not measuredNot measured.
ProposedProposed ≤15 min, subject to approval; define trigger and eligible denominator.
EMS record; medical leadership; each eligible case and monthly summary.
First call → receiving-center decision
First receiving-center call to acceptance, refusal, or conditional decision.
Not measuredNot measured.
ProposedProposed ≤10 min as testable internal objective; track refused/unresolved cases.
Contact log and partner records; operations/consenting centers; monthly.
Number of contacts
All receiving-center/resource contacts per eligible case and reasons.
Not measuredNot measured; multiple calls described qualitatively.
ProposedTrack distribution and reasons; one contact is aspirational only.
Contact register; operations; monthly.
Access to MCS decision
Agreed recognition/referral event to resource consultation and decision (separate from device deployment).
Not measuredNot measured; source ≤60-minute working goal requires event definition.
ProposedDefine each event before setting/reporting a threshold.
EMS and consenting partner records; medical/operations leads; each eligible case.
Data completeness
Required fields present and validated for eligible cases.
Not measuredNot measured.
ProposedSource proposes ≥80% in first collection cycle, then improve; proposed data-quality threshold.
Named data owner; quality; each collection cycle.
Targets other than the cited early ECG benchmark are MOST working goals, not universal clinical guideline requirements. Report median and P90 alongside means, case volume, denominator, target compliance, missing-data rates, outliers, source, and trends. Do not claim before/after improvement until validated baseline and repeat data exist.
08 · LEADERSHIP
What healthcare executives should know
Protocols and favorable average intervals are useful signals, but do not describe the full distribution or performance in atypical, high-risk cases. Without case-level measurement, leaders may be unable to distinguish an isolated event from a recurring process issue—or to tell whether a delay occurred during stabilization, communication, acceptance, routing, transport, or handoff. Clear process ownership, valid timestamps, and a shared review method let executives target follow-up questions without attributing blame unsupported by evidence.
09 · POTENTIAL DELIVERABLES
From assessment to implementation support
These are examples of a potential follow-up engagement, subject to agreed scope and institutional cooperation.
Operational workflow map
Clinical decision and process-ownership matrix
Evidence-gap register
Case-review and delay-classification framework
KPI definitions and executive dashboard
Escalation and handoff recommendations
Destination pathway recommendations
Interdisciplinary simulation program
Human-factors evaluation
Prioritized 30/60/90-day roadmap
Executive reporting and implementation support
10 · CONCLUSION
From identifying gaps to measurable operational reliability
Reliable pathways require more than written protocols and favorable averages. Leaders need visibility into critical decisions, variability, and high-risk exceptions. MOST’s proposed approach combines workflow assessment, operational measurement, clinical coordination, simulation, and structured quality improvement—subject to institutional agreement and validated evidence. No mortality reduction, patient-outcome improvement, or financial return is claimed.
Revised English and Polish source reports are available for internal review, but their disclosure authorization and full metadata/redaction status have not been independently confirmed here. Downloads are withheld pending internal approval of appropriately de-identified copies. The online analysis is complete without them.
Supporting reports pending internal approval
Institutional Project Inquiries
For hospitals, EMS agencies, universities, healthcare organizations, technology companies, and institutional partners. Describe the organizational challenge and the support you are seeking.
Thank you. Your project inquiry has been received. We will review it and contact you about possible next steps.
We could not send your inquiry. Please try again; your entered information remains in the form.
Please do not submit patient-identifiable information, sensitive operational plans, classified information, or unnecessary professional documents through this general inquiry form.
What happens next
We will review your inquiry and contact you to discuss whether our expertise fits your needs and what a suitable next step could be. Project scope and commercial terms are agreed before work begins.