My question could be rephrased as: Why is it a decision?.
When you pick up the phone and are talking to someone, the system could be showing them the EKG you did, with no intervention on either end.
I realize there is much opportunity there for bad implementation, I'm more interested in understanding the characteristics of a great implementation. Maybe there are reasons to leave it to the discretion of the EMT, but it being easy for the EMT to handle isn't one that I find very satisfying (I find it arbitrary to the implementation).
It's a decision because different hospitals have different specialities. Trauma, stroke, cardiac, etc. The most appropriate facility is a combination of what the patient needs, what they want, and the logistics involved (travel time, relative busyness, etc).
I call the hospital because I want to make sure they got the transmission and are going to be ready for me when I get there. The transmission and the call are generally a couple minutes apart.
There are certainly _plenty_ of places where the workflow in the back of the rig could be improved, but this really isn't one of them.
I get that it isn't a big time taker, so this is just abstract commentary.
This is an obvious opportunity for improvement: I call the hospital because I want to make sure they got the transmission. The ideal case would be that you don't even have to think about whether they have the information or not, the system should handle that with very high reliability.
You've also taken "decision" differently than I meant it. I meant, why do you have to decide to transmit the EKG, not the decision about which hospital to go to. Repeating myself, it would seem to be an improvement if you didn't have to pay any attention to whether the appropriate hospital had access to any readings/recordings that you had (I would think it would be better if it were trivial for someone there to pull them up, of course with high reliability).
I'm not feeling around for some opportunity to innovate/improve, I'm just curious about the factors that such a system has to deal with, and which of those factors are less idea than they could be, and why. That it isn't a big opportunity for improvement is useful feedback in general, but it doesn't really address the curiosity.
When I say I'm confirming they got it, I mean I'm confirming someone actually looked at it. The fact that it was delivered successfully is indeed reported to me.
The act of transmitting the EKG serves to give the hospital a heads up that I'm coming, and that I think this patient needs care right away. I understand you're suggesting a system where every bit of data my monitor collects is available in every hospital in real-time, so I just have to call them up and reference it. My point is that is that the act of sending the EKG is a really miniscule part of the process. You're talking about 5 seconds over the course of a 30 minute event.
I don't think the tradeoffs in complexity and quiet failure modes would be worth it. If I transmit something, I get a confirmation right then that it did or didn't work. If a passive data aggregation system fails (and I'm used to it 'just working'), then I may not notice that it failed.
Have to say, this seems like an area where I'd be very happy there's an experienced human weighing all the various factors and making the judgement call.
After reading the procedure you've described I feel very grateful for our highly developed acute care system, and the dedicated pros who make it all work.
When you pick up the phone and are talking to someone, the system could be showing them the EKG you did, with no intervention on either end.
I realize there is much opportunity there for bad implementation, I'm more interested in understanding the characteristics of a great implementation. Maybe there are reasons to leave it to the discretion of the EMT, but it being easy for the EMT to handle isn't one that I find very satisfying (I find it arbitrary to the implementation).