kyparamedic
Forum Ride Along
- 8
- 0
- 1
I'm heading up our QA/QI committee and am really frustrated with the way we document and the resistance I get at trying to change it. The narratives, in my opinion, are very poor, often consisting of just a few lines. These are on ICU-level transfers, often vented, on multiple drips. We are strictly interfacility and do ground, rotor, and the occasional fixed-wing. We use TripTix by Intermedix and there is heavy emphasis on documenting things in the event log and assessment tabs, which I agree with, as that makes it much easier to capture data, but I still feel that the narrative should give an overall story of the events leading up to their hospitalization and what happened on transport. It's hard to look at the event log and really get much of a sense of that, other than to know what meds were given, what procedures were done, and if the patient got "better, worse or unchanged" as a result. I have a pre-hospital background as do most of our medics, so the medic charting I feel is pretty good, whereas the nurses' is really lacking. Maybe it's just the different backgrounds? Whenever I bring up beefing up the narratives to include more detail or description of what happened on the call, I'm told things like "that's double-charting" or "the more detailed you are, the more it can hurt you in court." There really is a mindset of "less is more" and that if it's in the event log or assessment tab, or anywhere else in the chart, it doesn't need to be mentioned in the narrative. I agree that you don't need to give all the details in the narrative, like that they had a 20ga PIV in the right forearm with normal saline infusing at 100ml/hr, but if you increase that to 150ml/hr, even though it's charted in the event log, it should still be mentioned in the narrative with an explanation. Something as simple as "IV fluid infusion rate increased due to suspected dehydration." Although I think it should really go into even more detail as to why you suspect dehydration. Basically your decision-making should be explained. Just charting that it was done in the event log is not sufficient. Am I wrong here? Any data or things I can use to refute this whole notion that the more you document, the more it can hurt you? I've always been told the complete opposite, but maybe I was told wrong...