HOW THE CHAIN OF SURVIVAL GAVE PAUL THE BEST CHANCE
When someone suffers a cardiac arrest out of hospital, certain things happening in a certain order can dramatically increase their chances of survival. This order of events is know as the ‘chain of survival’.
The elements that make up the Chain of Survival are:
Early Intervention: Recognising early on that someone is in cardiac arrest
Access: Getting assistance and calling for help from the emergency services
CPR: Performing chest compressions until a defibrillator arrives
Defibrillation: Administering a controlled electric shock (this can triple the chance of survival)
Advanced Cardiac Life Support: Advanced care delivered by paramedics and/or doctors
Post-Resuscitation Care: Continued care once resuscitation succeeds
48-year-old Paul, our patient who was featured in episode 1 of More4’s Emergency Helicopter Medics, is a living example of the Chain of Survival in action. In August 2018, golfer Paul was heading out to tee-off on a golf course near Milton Keynes when he started to feel unwell.
Paul felt a tight pressure in his back and chest and instinctively knew something was wrong, so he returned to the clubhouse whilst his friends carried on with their round of golf.
At the clubhouse, Paul’s discomfort persisted and he asked the staff to call an ambulance. Without knowing it, Paul had just put himself on the Chain of Survival by realising that something was wrong, making an early intervention by deciding to stop his game of golf and accessing help by calling 999.
Within 16 minutes of being called-out, Thames Valley Air Ambulance’s Critical Care paramedic Jo and doctor Chloe arrived on scene to deliver advanced critical cardiac care to Paul. It was immediately clear to the team that Paul was suffering a catastrophic heart attack and he needed to get to the right hospital with the right facilities for the very best chance of survival.
Suddenly, Paul went into Cardiac arrest. Because he had accessed help early and the critical care team were already present, treatment could be started immediately with CPR and defibrillation. This treatment was crucial in keeping Paul alive.
Paul’s heart attack was very serious and there was a high probability that he might have another cardiac arrest or suffer other complications that would require further significant medical intervention.
Whilst the helicopter could have transported Paul to the hospital rapidly, there is not as much space to access the patient as there is in an ambulance – space which could be much needed if Paul required further treatment.
The Thames Valley Air Ambulance crew, together with paramedics of the South Central Ambulance Service, continued to treat Paul as they took him by land ambulance to the John Radcliffe Hospital.
This decision proved to be the correct one as Paul’s condition deteriorated further and he suffered several more cardiac arrests on route. Chloe and Jo took over Paul’s breathing by giving him an anaesthetic, placed Paul on a mechanical device which gives continuous chest compressions and delivered regular defibrillation and advanced post-resuscitation drugs to try and get his heart back to a stable rhythm.
Paul had a total of 28 shocks to the heart (13 of these were delivered pre-hospital) and surgery to remove a blood clot found by cardiac surgeons on the left-hand side of his heart.
As a result of Paul’s decision to intervene early and place himself on the Chain of Survival, he has defied all odds of survival and is now well on the way to a full and remarkable recovery. He is back at work full-time and running the Reading Half Marathon in March to raise money for Thames Valley Air Ambulance.
Join the community by signing up and keep up to date with news and events.
Privacy & Cookies Policy
These cookies remember choices you have made on our website in order to improve your experience. This could include your username, language or the region you are in. The information these cookies collect may be anonymised and only apply to your browsing activity on our website.
This cookie monitors which event pages the user has visited, in order to provide them a list of recently visited event pages. This cookie is only used to improve the user's experience of our website.
This cookie monitors which web stories the user has read, in order to provide them a list of recently read stories. This cookie is only used to improve the user's experience of our website.
These cookies collect information about how you use our website, for example which pages you most frequently visit, or if you receive error messages. These cookies don’t collect any information that could identify a visitor. The information collected by these cookies is aggregated and therefore anonymous. They are only used to improve how our website works.
This cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
This cookie is used by Google Tag Manager to store and track website conversions.
This cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the wbsite is doing. The data collected including the number visitors, the source where they have come from, and the pages viisted in an anonymous form.
This cookie is used by Hotjar to detect the first pageview session of a user. This is a True/False flag set by the cookie.
This is set by Hotjar to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.
This cookie is set by Hotjar. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the random user ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
This cookie is set to let Hotjar know whether a visitor is included in the data sampling defined by our site's pageview limit.
This cookie is set to let Hotjar know whether a visitor is included in the data sampling defined by the website's daily session limit.
This cookie is set by HotJar. When the Hotjar script executes they try to determine the most generic cookie path to use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, HotJar try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
5 months 27 days
This cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
This cookies is set by Youtube and is used to track the views of embedded videos.
These cookies collect information about your browsing habits to make advertising relevant to you and your interests.
This cookie is set by Facebook to deliver advertisement when they are on Facebook or a digital platform powered by Facebook advertising after visiting this website.
The cookie is set by Facebook to show relevant advertisments to the users and measure and improve the advertisements. The cookie also tracks the behavior of the user across the web on sites that have Facebook pixel or Facebook social plugin.
1 year 24 days
Used by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
This cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.