> -----Original Message-----
> From: Accident and Emergency Academic List
> [mailto:[log in to unmask]] On Behalf Of Helen Deborah Vecht
> Sent: 06 June 2005 16:09
> To: [log in to unmask]
> Subject: Drips and transfers, was Re: Assessment tool for
> transfer of medical patients
>
>
> "Dunn Matthew Dr. (RJC) A & E - SwarkHosp-TR"
> <[log in to unmask]>typed
>
>
> > > I have had experience of technicians stating they were
> not supposed
> > > to manage patients with intravenous infusions, when transferring
> > > patients from a MIU to A&E.
> > >
> > > Clearly, there will be patients who are suitable for a satellite
> > > hospital, who have IVIs in progress.
> > >
> > > Will they need paramedics?
> > > Is my experience out of date?
> > > What is the current practice?
>
> > Unfortunately for the original poster, this thread (as
> often happens)
> > seems to have taken on a life of its own without answering the
> > original question. As a general point: this is discussing transfers
> > within the same city. I don't know about times in Bristol,
> but if two
> > departments are more than 30 minutes apart, then I would
> worry about
> > reducing one of them to the status of minor injuries unit.
> In deciding
> > which patients to transfer, inability to tolerate 30 minutes off a
> > drip is something I would generally consider a relative
> > contraindication to transfer until more stable.
>
> Even if the transfer time is only a few minutes, I suspect
> that the actual time off a drip would be measured in hours
> for routine transfers, if infusions needed to be stopped for
> transfer. This is probably not critical, but represents
> rather mediocre care, hence my concern.
Care to enlighten us on this - especially if both ends of the journey
are in the same trust ( and using and accepting the validity of the
same infusion charts and drug charts)
Surely it's disconnect when the crew come to collect and establish a
further infusion ( assuming it's prescribed ) as parto f the intial set
of interventions on arrival
--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.322 / Virus Database: 267.4.0 - Release Date: 01/06/2005
|