Difference between revisions of "Fullest Code Possible"
From Gomerpedia
Line 1: | Line 1: | ||
+ | [[File:2015 ACLS Algorithm.jpg|450px|thumb|right]] | ||
+ | |||
The '''fullest code possible''' trumps a standard [[Full Code]] and provides the patient with interrupted care long after the death. Whereas [[Hospicillin|hospice]] focuses on ''quality'' of life, the '''fullest code possible''' focuses on the ''quantity'' of futile interventions.<ref>[http://gomerblog.com/2017/02/fullest-code-possible/ Patient to be “Fullest Code Possible”]</ref> | The '''fullest code possible''' trumps a standard [[Full Code]] and provides the patient with interrupted care long after the death. Whereas [[Hospicillin|hospice]] focuses on ''quality'' of life, the '''fullest code possible''' focuses on the ''quantity'' of futile interventions.<ref>[http://gomerblog.com/2017/02/fullest-code-possible/ Patient to be “Fullest Code Possible”]</ref> | ||
Revision as of 00:03, 11 July 2017
The fullest code possible trumps a standard Full Code and provides the patient with interrupted care long after the death. Whereas hospice focuses on quality of life, the fullest code possible focuses on the quantity of futile interventions.[1]
Components
There are several components to the fullest code possible:
- it occurs infinitely;
- all health care professionals within a 25-mile radius and involved until exhausted and in rhabdo[2];
- all medications within the hospital pharmacy are consumed, especially bicarb;
- shocks are continued until the city's energy grid is fully depleted;
- ECMO is implemented;
- dialysis is implemented; and
- the kitchen sink has been thrown.[3]
References