|
|
|
|
|
by corty
1886 days ago
|
|
I think the "good doctor" starts as soon as the checklist is finished and there is no result yet. I'm not a medical professional, but in other areas, using a checklist is helpful and necessary. You may cut short the known-useless parts if you really know what you are doing. But often, "known-useless" is a fallacy and you waste time on your firm-but-wrong intuition. Which is OK if you just waste your time, but not OK if it is about a patients (life-)time. I think there are "House, M.D."-style situations where the checklist will kill your patient and a quick hunch will save it. But the usual doctor's visit because of an itchy eye isn't. As an IT professional, just think of the number of times where it really was one of point 1, 2 or 3 on the checklist: "is it switched on?" "is it plugged in?" "have you tried turning it off and on again?". Of course those are often useless. But when they are not they do waste far more time than just quickly checking... |
|
I work in a hospital setting and I would say 90+% of the time the issue is diagnosed following a checklist for a particular problem. In the medical field we are taught to think of a 'Differential Diagnosis', or DDx for short, and sort by probability based on the history, age, sex, etc of the patient. Of course in the hospital setting you would also think of 'which of these issues can possibly kill my patient in the next 24hrs' and look for those as well.
So you go down your DDx list and if you run out of diagnoses, go back to the history/patient and think about it some more or consult with your peers.
As far as the "House MD" situations, i haven't run into any of those so i can't comment on that part.