JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for ACB-CLIN-CHEM-GEN Archives


ACB-CLIN-CHEM-GEN Archives

ACB-CLIN-CHEM-GEN Archives


ACB-CLIN-CHEM-GEN@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ACB-CLIN-CHEM-GEN Home

ACB-CLIN-CHEM-GEN Home

ACB-CLIN-CHEM-GEN  2005

ACB-CLIN-CHEM-GEN 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Path results to PROTON

From:

Trevor Gray <[log in to unmask]>

Reply-To:

Trevor Gray <[log in to unmask]>

Date:

Tue, 25 Jan 2005 21:20:57 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (86 lines)

In message
<[log in to unmask]>
, O'Connor John (Royal Devon and Exeter Foundation Trust)
<[log in to unmask]> writes
> This email is directed at labs which send their results to PROTON a
>renal information system used by 50% of Renal Units in the UK. We are under
>immense pressure to release non clinically validated results directly into
>this system, so that patients can be discharged promptly.
>
Dear John,

You are certainly not the only one to be faced with this problem of
proton. I have faced a fifteen year battle to get them to accept
clinical comments on the system. For example, I have asked them how
they know a sample is haemolysed (a canned comment) on their system to
be told they "just know". Because all results are downloaded, they
shred the printed results, although, to be fair, the renal unit staff
are instructed to save any forms with comments on. However, they have
ignored clinical comments pointing out monoclonal gammopathies in the
past so their system is not foolproof.
Proton has another characteristic that means that it sometimes muddles
samples taken close together, because it does not recognise samples with
different laboratory numbers as being different.
Because of these problems, I have refused to release our laboratory EQA
results so that they can contribute to some of the comparisons in the
Renal Registry. Slightly dog-in-the-manger I know, but I have no
confidence that what is stored on their computer is what we originally
reported.
Having got that off my chest, I have to say that the access that we in
the lab. have to their system is really valuable for the clinical
information I can get is vastly superior to the "CRF" put on most
requests. It is an interesting anachronism that the data personally
input by medical staff and used by them, a sort of electronic medical
notepad, may be more useful than the technological filing cabinet for
results which, due to poor programming, misses the useful bits
(comments) and occasionally misfiles the rest.
As far as authorisation is concerned, our renal unit is in a slightly
privileged position in that its samples are fast-tracked by us. (When
they moved to NGH the renal unit got us a new laboratory so I do owe
them one!). All such samples have their results sent to the hospital
computer once they have been technically authorised, and so are
available on the renal wards (flagged unauthorised) although I believe
that they do not get on to Proton until clinically authorised. Results
which are changed at authorisation overwrite the hospital computer
output (although the original is kept in background) so we can do that
safely as it is little different from phoning results off the analyser.
During the day, there is little delay in full clinical authorisation,
but this can obviously stretch at night although we do authorise from
home via a modem at about 10.00 p.m. I agree that clinical
authorisation is useful and would guess that we pick up quite a few
issues each day. The key is to have a good algorithm for picking up
oddities in your laboratory system. This was something that Telepath
with its sophisticated range planes and delta checks could manage. Now
we have Apex and it cannot manage checks on more than two analytes
before the system runs out of flags. As a result we either have to set
it to miss alerts or to put a vast amount into authorisation. For
better or worse we have chosen the former as authoriser fatigue in
ploughing through every renal report can equally result in missing
important results.
So I support your view. Proton is an imperfect tool which has not been
improved despite much prodding. The more people can feed back about its
problems the more likely it is that the software company will adopt
better practices.
Trevor
--
Trevor Gray
Dept. of Clinical Chemistry,
Northern General Hospital,
Sheffield S5 7AU

0114 271 4309

------ACB discussion List Information--------
This is an open discussion list for the academic and clinical
community working in clinical biochemistry.
Please note, archived messages are public and can be viewed
via the internet. Views expressed are those of the individual and
they are responsible for all message content.

ACB Web Site
http://www.acb.org.uk
List Archives
http://www.jiscmail.ac.uk/lists/ACB-CLIN-CHEM-GEN.html
List Instructions (How to leave etc.)
http://www.jiscmail.ac.uk/

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

May 2024
April 2024
March 2024
February 2024
January 2024
December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager