StrivingLife presents ...

JavaScript appears to be disabled. We recommend you enable JavaScript while visiting this site.

Should Doctors Always Tell Patients the Truth?

by James Skemp, December 31, 2004 01:01

(All original content on this site is licensed under the Creative Commons License Attribution-Noncommercial-No Derivative Works 3.0.)

Looking through an old philosophy anthology, Biomedical Ethics: Fifth Edition, I found and read On Lying to Patients, by Mack Lipkin. After reading this piece, I was again made to realize how much I dislike ethics. While Lipkin sets out to give us a theory, or method, he leaves us with more questions than answers. For this article, I would like to discuss whether doctors have an ethical obligation to tell the truth to their patients.

Answering the question of whether doctors can lie to their patients, or withhold the truth, either in part or whole, is deemed an ethical question necessary of an answer. Unfortunately, I’ve never been able to find a single article that gave an opinion or theory regarding this that I liked and found satisfactory rationally.

We can enlarge the question, for a moment, to the question of whether individuals, no matter their status or function in society, should ever lie to another individual. Some argue that one should never lie to another. Kant, for example, asks us to act according to how we would want everyone else to act. Since we wouldn’t want to be lied to, Kant argues, we should not lie to others.[1]

Opposed to this, some argue that it is okay to lie on occasion. If, for example, some man were thrust a gun into my ribcage and demand that I tell him where I lived and what my wife’s name was, I would not be wrong to either not tell him anything, or not tell him the truth. Taking another example, sometimes children that are left alone for a brief time are told to not say that their parents are not around. We also have the case where a surprise party may be planned for some date. If the individual who is to be surprised asks what is occurring on the date, it would cause no harm to lie to the individual.

I have, in the last sentence of the previous paragraph, suggested how it is that a lie could be acceptable. If a lie does not harm the individual that is lied to, then the lie should be acceptable. However, to guard against any problems, let us expand this to ‘A lie is acceptable if it causes no harm to the individual lied to, or if it is honestly believed or known that telling the truth would cause more harm to some individual than telling a lie.’

So, to use the three examples already stated above, with this suggestion in mind, are the lies told acceptable? In the case of the man thrusting a gun into my ribcage, I think we can safely assume that the man may intend to cause some harm to me and/or my wife. If I honestly believed that the man might bring some harm to my wife if I tell the man the truth, I believe it would also be acceptable to lie to this individual.

Looking at the children lying about being alone, I think we could also argue that telling the truth may cause more harm than lying. For example, some individual(s) may attempt to take advantage of the children, knowing that they are alone. However, if under the impression that the children are not alone, they would be deterred in their actions. The only case that I can presently think of which telling a lie would potentially cause more harm than telling the truth is in the case of the authorities asking the children the question. If the children were left alone for an extended amount of time, it would be better for the children if the authorities were alerted that the parents were derelict, or remiss, of their duty.

Our last example from above is the surprise party. If a party was being thrown for an individual, it would cause more ‘harm’ to the individual if I told them that a party was being thrown, rather than lying to the individual and saying that nothing was occurring.  Counter examples exist, such as if the individual would cause some harm to them self, thinking that no one cared about them. Another reason lying could be harmful is if the individual made plans to do something else. However, in this latter case, telling another lie that something may be occurring, or that the person and yourself should do something, is often employed, and is acceptable.

Our above examples, then, appear to comply with the argument that ‘a lie is acceptable if it causes no harm to the individual lied to, or if it is honestly believed or known that telling the truth would cause more harm to some individual than telling a lie.’ Can we think of any new examples that would nullify this claim?

One may argue that since we cannot know how another person would act, we can make no claim regarding what would or would not harm someone. However, educated guesses, and guesses based upon experience, are always possible. We may not always be correct, especially when it comes to individuals that we just met, but we can use experience to guide our judgement.

This leads to the question of how someone could determine whether they should lie to someone. As pointed out, the argument posited above does not answer every possibility. If we add Kant’s theory – that we should act according to how we would want someone to act if the positions were reversed – after what we’ve stated above as a point, then every possibility should be covered.

Moving to our original question, should doctors always tell their patients the truth? Clearly, based on the above, I cannot argue that doctors should always tell their patients the truth. Rather, doctors should follow the guidelines stated above regarding the acceptability of lies - ‘a lie is acceptable if it causes no harm to the individual lied to, or if it is honestly believed or known that telling the truth would potentially cause more harm to some individual than telling a lie, but if left in doubt, ask, if the positions reversed, what you would want told to you’.

Some argue that doctors have a particular interest in telling the truth to patients, which would seem to supersede what I have argued above. However, doctors primarily have an interest in helping their patients lead a health life. Stress has an extremely powerful effect upon an individual’s health, or well-being, and it is with this in mind that a doctor should sometimes lie to a patient.

Yet what if a patient specifically asks to be told the truth, meaning the whole truth – nothing is to be left out, or specifically asks to not be told about anything that is particularly life-threatening, or a particular ailment? Should a doctor abide by the individual’s desires?

As stated above, the effect the truth or a lie would have on the individual must be taken into account. If the doctor has found that there is the chance the individual has some life-threatening ailment, it may be better to tell the patient that the results have not come in, than to tell the patient that they may potentially have the ailment. Life-threatening ailments, in particular, cause problems because some people would rather die than suffer from some ailment. If the patient is willing to die before they begin suffering, it may be necessary to withhold a potentially rehabilitating ailment from them until it can verified. I believe this follows from what I have stated above.

As far as the patient asking to not be told about something, we must look at whether telling the individual would benefit them more from not telling them. For example, if the individual is particularly worried about cancer, but if the individual was told they had cancer, and began receiving treatments, they may feel some harm by being told that they had cancer, but would be able to receive treatments, lessening the chances they would have to be harmed in the future.

One problem with the medical profession that gives this all a level of fuzziness is the problem of the care patients receive. The days of a family doctor have come and gone. By losing these kinds of doctors, we have also lost the relationship that doctors once had with patients. It used to be that doctors would understand their patients – in particular their beliefs and past judgements. In today’s world, a doctor meets many more patients, and may only meet with a patient a few times throughout their career.

Because of this, a doctor may not be able to make an informed decision regarding how their patient, for the moment, would be able to handle the breaking of serious news. There are few other fields where a question this powerful arises. Can anything be done regarding this?

I believe that there is a way to resolve this issue. If each patient were asked, hypothetically, how they would act, or what they would and would not want to know (and why), then a doctor would be able to access how much potential harm the truth or a lie would cause. If a patient was required to fill out a questionnaire regarding any number of the various ailments deemed serious, with particular names of ailments listed, a doctor could examine this questionnaire, and the patients reasons, before making an assessment of what should be told.

The question is, can we find any fault with this idea? One may say that a patient may not fill out the form honestly, or may not give a sufficient reason for why they would or would not want to be told about something. However, if the patient did have to give a justification for particularly serious questions, the consulting doctor, or another member of the medical staff, would be able to eliminate any of the less than serious answers. Furthermore, lying on this form would only harm the patient – if the patient puts something on the form that they do not honestly believe, it can only be the patient’s fault for any harm that may come about, so long as the form makes this quite clear (in order to prevent any claims of negligence). As an aside, it’s unfortunate that people fight for the ability to make a choice yet dislike it when their choice leads down the wrong path.

It would also be acceptable, and in fact recommended or mandatory, for the patient to look over their choices before any further meeting with the doctor, with older versions of the questionnaire stored in order to secure against any vastly different answers. The problem of storing these forms in a safe environment, as well as allowing the form to move from doctor to doctor, would be a serious concern, based upon the fragmentary nature of the medical profession today. The insurance companies would also play an important role in the creation of these forms, for companies may argue that they have a vested interest in the answers that patients provide. At this point, I can only offer my biased opinion that insurance companies should not be allowed access to these forms, under any circumstance. In a way, the filling out of these forms is the individual stating how they feel about the very question of life and death – what constitutes life, and when life should lead to death.

The ethical question or whether doctors should always tell the truth to patients is not a difficult question to answer with a ‘no’, but justifying when a doctor can lie is extremely difficult. Hopefully my argument that ‘a lie is acceptable if it causes no (potential) harm to the individual lied to, or if it is honestly believed or known that telling the truth would cause more (potential) harm to some individual than telling a lie, but if left in doubt, ask, if the positions reversed, what you would want told to you’ is a working possibility. However, I feel that the best chance of putting this question to rest with a necessary answer is to put the question to the patient, when they can think and give an honest answer.

As a postscript to this conclusion, while it is true that an individual will think one way when healthy, and another when sick, and the individual will undoubtedly be filling this out when they believe they are healthy, it is hoped that the individual will keep both the healthy and sickly states of life in mind when they are filling out any such form, or more generally, making any arguments about how they feel about a particular issue. Hopefully, by keeping past versions of questionnaires, as stated above, any major changes to answers can be seen by staff and justified by patients.

Notes:

1. Kant may argue something closer to what we argue, something based upon circumstances. However, based upon the little that I know of Kant, I would argue, at this point, that he would like truth telling to be universal, and lying, of any kind, removed. However, I welcome comments on where in his works he states something contrary to this.

Thanks to Gavin S. for pointing out that potential harm should be made more clear. Hopefully the addition of this word, as well as the presence of ‘may’, will show that all harm here discussed is potential, not necessarily actual (although potential does not dismiss actual harm).

Created: December 31st 2004
Modified: January 2nd 2004

Tags:
Categories: article | philosophy

Apophysis 2.0: Free Fully Commented Scripts

by James Skemp, December 15, 2004 23:00

(All original content on this site is licensed under the Creative Commons License Attribution-Noncommercial-No Derivative Works 3.0.)

I offer the following, fully commented, scripts for use by the Apophysis (2.0) community. Feel free to copy the following scripts into the script editor for Apophysis 2.0 or download the script files from http://strivinglife.net/. Feel free to save the scripts on your own computers, but please do not share these scripts with others; rather, direct them to this article so they can be aware of my other scripts and any enhancements I release. Comments regarding these scripts are welcomed with open arms. Thanks, and enjoy J

Please note that these scripts all assume that you have a folder on your C drive called ‘renders’. If you do not, either change this directory in the scripts, or create a directory by this name in that location.

Full listing of available scripts:

  1. Modified Batch Render (ModBatchRen.asc) – 3 KB
  2. Preview Sweep - using ‘for’ – 1 KB
  3. Preview Sweep - using ‘repeat’ – 1 KB
  4. Render Single Flame (RenSingle.asc) – 2 KB

 


Modified Batch Render (download name: ModBatchRen.asc)

{Modified Batch Render – Apophysis 2.0}
{Renders selected flames in the
 current parameter file to disk.
 Set the render settings to taste}
{http://jamesrskemp.net/}
p := 1; {sets primary number to 1}
f := FileCount; {sets final number to the file count}
Renderer.Width := 1280; {sets render width – change to taste}
Renderer.Height := 960; {sets render height – change to taste}
InputQuery('First Flame to render', 'Actual Position:', p);
 {Prompts for the first flame to render – defaults to the very
  first flame, set by p above}
InputQuery('Last Flame to render', 'Actual Position (default is last):', f);
 {Prompts for last flame to render – defaults to the very last
  flame, set by f above}
Print('Input done'); {Prints to the editor window that values have been entered}
p := p - 1; {Since the first flame is really 0, not 1, you have to subtract one from the initial value}
f := f - 1; {You also have to subtract one from the final value}
Print('First actual: ');
Print(p); {Outputs the actual position number for the first flame}
Print(' and last actual: ');
Print(f); {Outputs the actual position number for the last flame}
for i := p to f do { from the first to the last flame...}
begin {begin the following until the ‘end’}
  LoadFlame(i); {load flame}
  n := i+1 {add one to current flame position value}
  Print('Loaded flame in position #');
  Print(n); {Output this value so that the user knows what flame is rendering}
  Flame.SampleDensity := 100; {best 200 - flame sample density – change to taste}
  Flame.Oversample := 1; {best 2 - flame oversample – change to taste}
  Flame.FilterRadius := 0.2; {best 0.4 - flame filter radius – change to taste}
  Renderer.Filename :='C:\renders\' + Flame.Name + '.jpg'; {render flame to this directory, in jpg format – change to taste}
  SetRenderBounds; {sets render bounds}
  Render; {renders the flame}
  Print('Rendered flame #');
  Print(n); {output that the flame has been rendered}
end; {end the for loop – if the ‘for’ is not done, go back to ‘begin’ and continue – automatically adds one to the ‘i’ value}
UpdateFlame := False; {don’t update the flame in the Apophysis window}

Sample output for entered values of ‘1’ & ‘1’

Input done
First actual:
0
 and last actual:
0
Loaded flame in position #
1
Rendered flame #
1

Please note that you must have the script editor open in order to see the outputs.  However, you can open the editor at any time (Ctrl + D) to check the progress of the script.


Preview Sweep – using ‘for’ (download name: PreviewSweep1.asc)

{Preview Sweep - Apophysis 2.0}
{Preview Flames, with information regarding the number down}
{http://jamesrskemp.net/}
UpdateFlame := false; {don't update the main display}
b := 0; {starting value – change if you’d like}
e := FileCount - 1; {ending value - 'FileCount - 1' (no quotes) for all - run as is to text SampleDensity – change after determining best sample density}
for i := b to e do {from b to e, do the following}
begin {begin 'for' loop}
if Stopped then Break; {if the Stop button is pushed, stop the preview}
LoadFlame(i); {load flame}
Flame.SampleDensity := 30; {change this value to allow the image to have time to preview on your computer}
{increase on faster machines, decrease on slower ones}
if (Transforms > 1) then
Preview;
else
Print('Bad flame'); {since only flames with more than one transform can be rendered, this checks for that}
print(i); {Print flame number from top - prints after showing the flame}
end; {end 'for' loop - go back to the 'begin' if the 'for' is not done}

See also Preview Sweep – using ‘repeat’ for an alternative method.


Preview Sweep – using ‘repeat’ (download name: PreviewSweep2.asc)

{Preview Sweep - Apophysis 2.0}
{Preview Flames, with information regarding the number down}
{http://jamesrskemp.net/}
UpdateFlame := false; {don't update the main display}
b := 0; {starting value – change if you’d like}
e := FileCount - 1; {ending value - 'FileCount - 1' (no quotes) for all - run as is to test SampleDensity – change after setting sample density to taste}
repeat {repeat the following until the below conditions are met}
LoadFlame(b); {load flame}
Flame.SampleDensity := 30; {change this value to allow the image to have time to preview on your computer}
{increase on faster machines, decrease on slower ones}
if (Transforms > 1) then
Preview;
else
Print('Bad flame'); {since only flames with more than one transform can be rendered, this checks for that}
Print(b); {Print flame number from top - prints after showing the flame}
b := b + 1; {increase flame value by one}
until (b >= e) or Stopped; {continue until the end value is reached}

See also Preview Sweep – using ‘for’ for an alternative method.


Render Single Flame (download name: RenSingle.asc)

{Render Single Flame - Apophysis 2.0}
{Renders single flame in the current parameter file to disk.}
{http://jamesrskemp.net/}
InputQuery('Input flame to render','Flame number to render (actual position):',f) {Prompt for flame to render where first flame = 1}
i := f-1; {Set value for flame to render, first = 0, last = total flames - 1}
Renderer.Width := 1280; {Set render width – change value to taste}
Renderer.Height := 960; {Set render height – change value to taste}
LoadFlame(i); {Load flame}
Flame.SampleDensity := 200; {best 200 - flame sample density – change to taste}
Flame.Oversample := 2; {best 2 - flame oversample – change to taste}
Flame.FilterRadius := 0.4; {best 0.4 - flame filter radius – change to taste}
SaveFlame('C:\renders\' + 'singlerenders.flame'); {save the flame parameters to this file – change to taste}
Renderer.Filename :='C:\renders\' + Flame.Name + '.jpg'; {render flame to this directory, with ‘jpg’ extension – change to taste}
SetRenderBounds;
Render; {set render bounds and render the image}
UpdateFlame := False; {don’t update the flame when done}


Created: February 13th 2004

Modified: March 9th 2004; March 12th 2004; September 13th 2004; November 25th 2004; December 16th 2004

Notes: Some of these scripts were originally developed during the beta stages of Apophysis 2.0, but they have all been run successfully on the final release and on 2.02 (the version current as of this update).

Tags:
Categories: article | software

On the Saying 'Shitcakes'

by James Skemp, December 6, 2004 01:01

(All original content on this site is licensed under the Creative Commons License Attribution-Noncommercial-No Derivative Works 3.0.)

The language used in this article is for mature audiences. If you might be offended, please stop reading now.

The saying “Shitcakes” is in no way a popular saying[1]. In fact, it’s something of a rarity in the world today. However, since it is a saying that I have heard many a time, and since I wanted to try to understand where this statement may have originated, I decided to try to work through its significance.

First, we are drawn to the word ‘Shit’. In fact, a popular variation of this saying is “Shit cakes” or “Shit-cakes”, neither of which, as my article will show, is correct. ‘Shit’ is not only meant to stand for faeces, but also as an exclamation of a bad move, or a stupid decision, and of a troublesome individual. Of course, there are numerous other meanings attached to the word ‘Shit’, since as feelings of love or emotion, or anger.

Second, we may be drawn to ‘cakes’, the second part of the saying, or conjunct. Cakes are typically a kind of dessert, or something that is sweet, nice smelling (as it brings to mind ovens and the odours that they release), and a treat.

The important thing to keep in mind is not the two words that are seen in the saying, but rather the result of the combination. It’s easy to think of a very similar word, namely cupcake. A cupcake is a cake that is contained within, or constrained by, a cup. You pour a batter into a metal tin, sometimes with a paper wrapper (if you’re smart), sometimes without, and you back it. While the wrapper, or ‘cup’, is not edible or very desirable (usually these are torn off), the cake is. Are there any similarities between ‘cupcake’ and ‘shitcake’?

First, we must see ‘shitcake’ in action. “Oh, shitcakes!” is the most common occurrence of the saying[2]. Yet, that doesn’t really tell us much, by itself. If we create a dialogue, however, we can gain context clues from the surrounding phrases.

“Hey Pete, I heard that lazy dog of yours got some bitch pregnant.”

“Yup, sure did Hank. I’ve had that son of a bitch since he was a pup and I never would have expected that he would have left me for some easy old one-eyed bitch.”

“Hey Pete, isn’t that your wife driving your Ford? What’s she got in the back, luggage?”

“Oh, shitcakes!”

“Well Pete, I knew she was sluttin’ around, but I never would have thought that she would have taken your Ford!”

“Oh Hank, I am indeed a cursed man…”

The above example, with some level of context clues, may indeed be all that we need. Walking through the above dialogue, we see that poor Hank loses his dog Mack to some female dog, and then loses his Ford to his fun and outgoing wife, Susan. After finding out this latter point, after having just been reminded of the former, he exclaims in sorrow, as the last, open-ended, phrase shows, “Oh, shitcakes” (but not simply “Oh shitcakes” – the comma has real significance here, and is not just a way for Pete to catch his breath, or a tear and/or moan).

But why not just “Oh, shit”? Why does he exclaim, and others with him (although not at the same time, and perhaps not over the same reasons), “Oh, shitcakes”?

Perhaps it is because, like being served ‘shitcakes’ instead of cupcakes, he is caught off guard. In our example, he’s assaulted with a reminder and a new bit of bad news (or two bits, if you do not believe that he knew that his wife was fun and outgoing, which, seeing how women are devious, is not too hard to believe).

If we were to try to explain his saying “Oh, shit-cakes”, or “Oh, shit cakes”, we’d have much more trouble than we have with “Oh, shitcakes”. After all, if Pete had yelled out a ‘hurrah’ or three, and asked Hank to try on some of his wife’s underwear with him, then we could use the ‘shit-cakes’ or ‘shit cakes’ explanation – that what first appears to be shit, is really cake (or so the most common and popular explanation goes). But, poor Pete does not say this, so Hank has to sneak into the house later, ending up in a longer night for both of them (Pete having spent most of the night caressing his wife’s side of the bed, and Hank having to wait for Pete to fall asleep, and then creeping in oh so quietly to get the underwear (tops and bottoms), during which he almost knocked over a lamp, but didn’t, but on the bright side, at least the damn dog wasn’t there, as it never really had a hankering (:cough:) for Hank…).

At this point, we can see where this saying came from, and why it is to be used over a simple ‘shit’, at the right time.

Notes:

  1. By ‘saying’, I hear mean both the actual saying or speaking of ‘shitcakes’, as well as the phrase. Perhaps the phrase that I really should have discussed was ‘Oh, shitcakes’, in order to remove any misunderstanding at the very start, but I did not, because I hope to show the way ‘shitcakes’ came about and should be used.
  2. Is “selling like shitcakes” another phrase that occurs? While some may argue that it is, that is unfortunately not the case. This phrase appears to come from “selling like hotcakes”, which means that some thing, which the phrase is referring to, is flying off the shelves, or selling very quickly. One may argue that “selling like shitcakes” is the opposite of this, that the thing is selling very slowly, but because people love shit, this cannot be. If any “selling like shit…” phrase exists in common usage, it is simply the phrase “selling like shit”.

Notes

Created: December 6th 2004
Modified: December 7th 2004
Notes: My thanks to Gavin for pointing out some grammatical mistakes, as well as bringing up some excellent clarification questions.

Tags:
Categories: article