0002392: Urist McDoctor cancels surgery: must recover wounded!

(0008780)
Footkerchief (manager)
2010-06-20 09:31

This is probably the same problem as the one I described at 0002388:0008750. Do you still get this problem after deconstructing and reconstructing all your traction benches?

(0009355)
Keldor314 (reporter)
2010-06-30 03:26

This appears to be a separate issue from 2392, since traction benches are not involved (the doctor decided to use a table - maybe it does an equivalent function?) and since there was no actual cancellation message - the doctor simply stops the surgery and carries the patient back to bed.

Removing the tables and traction benches "solves" the problem by causing the surgery to have to be performed in a bed, though this is certainly not an optimal solution, given that we know that surgery in bed raises the chance for complications, ect.

(0009358)
Footkerchief (manager)
2010-06-30 05:48

It was more directly described at 0000318:0008034 -- if you remove all your tables and rebuild them, that should fix the problem. Does it?

(0009636)
Keldor314 (reporter)
2010-07-04 23:25

There's that one too that I noticed, but in my case, they were making it all the way to the table and beginning the surgery task for a little while before changing their minds and carrying the patient back to a random bed.

(0009637)
Footkerchief (manager)
2010-07-05 00:51
edited on: 2010-07-05 00:51

Well, does it reproduce at all? If so, does it still reproduce after rebuilding all your tables?

(0009643)
zhukov5 (reporter)
2010-07-05 06:14

I have this too, only it is with a patient that is carrying an infant. The patient gets picked up and drops the infant. The patient then decides to recover the infant RIGHT NOW resulting in "surgery canceled: patient not resting". I have never had a surgeon attempt his trade on a patient that did not carry an infant, perhaps just through chance.

Issue History
Date Modified	Username	Field	Change
2010-06-20 02:00	Keldor314	New Issue
2010-06-20 09:31	Footkerchief	Note Added: 0008780
2010-06-20 09:31	Footkerchief	Tag Attached: AWAITING UPDATE
2010-06-28 07:47	Footkerchief	Relationship added	duplicate of 0002388
2010-06-28 07:47	Footkerchief	Status	new => resolved
2010-06-28 07:47	Footkerchief	Resolution	open => duplicate
2010-06-28 07:47	Footkerchief	Assigned To	=> Footkerchief
2010-06-30 03:26	Keldor314	Note Added: 0009355
2010-06-30 03:26	Keldor314	Status	resolved => needs feedback
2010-06-30 03:26	Keldor314	Resolution	duplicate => reopened
2010-06-30 05:48	Footkerchief	Note Added: 0009358
2010-06-30 13:08	Footkerchief	Assigned To	Footkerchief =>
2010-06-30 13:08	Footkerchief	Status	needs feedback => new
2010-07-04 23:25	Keldor314	Note Added: 0009636
2010-07-05 00:51	Footkerchief	Note Added: 0009637
2010-07-05 00:51	Footkerchief	Note Edited: 0009637	View Revisions
2010-07-05 06:14	zhukov5	Note Added: 0009643
2010-07-13 22:01	Footkerchief	Status	new => resolved
2010-07-13 22:01	Footkerchief	Resolution	reopened => duplicate
2010-07-13 22:01	Footkerchief	Assigned To	=> Footkerchief
2010-07-13 22:12	Footkerchief	Relationship deleted	0002388
2010-07-13 22:12	Footkerchief	Relationship added	duplicate of 0001244
2010-08-10 00:11	Dwarfu	Tag Detached: AWAITING UPDATE

Notes
(0008780) Footkerchief (manager) 2010-06-20 09:31	This is probably the same problem as the one I described at 0002388:0008750. Do you still get this problem after deconstructing and reconstructing all your traction benches?

(0009355) Keldor314 (reporter) 2010-06-30 03:26	This appears to be a separate issue from 2392, since traction benches are not involved (the doctor decided to use a table - maybe it does an equivalent function?) and since there was no actual cancellation message - the doctor simply stops the surgery and carries the patient back to bed. Removing the tables and traction benches "solves" the problem by causing the surgery to have to be performed in a bed, though this is certainly not an optimal solution, given that we know that surgery in bed raises the chance for complications, ect.

(0009358) Footkerchief (manager) 2010-06-30 05:48	It was more directly described at 0000318:0008034 -- if you remove all your tables and rebuild them, that should fix the problem. Does it?

(0009636) Keldor314 (reporter) 2010-07-04 23:25	There's that one too that I noticed, but in my case, they were making it all the way to the table and beginning the surgery task for a little while before changing their minds and carrying the patient back to a random bed.

(0009637) Footkerchief (manager) 2010-07-05 00:51 edited on: 2010-07-05 00:51	Well, does it reproduce at all? If so, does it still reproduce after rebuilding all your tables?

(0009643) zhukov5 (reporter) 2010-07-05 06:14	I have this too, only it is with a patient that is carrying an infant. The patient gets picked up and drops the infant. The patient then decides to recover the infant RIGHT NOW resulting in "surgery canceled: patient not resting". I have never had a surgeon attempt his trade on a patient that did not carry an infant, perhaps just through chance.