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

Help for ACB-IT Archives


ACB-IT Archives

ACB-IT Archives


ACB-IT@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

ACB-IT Home

ACB-IT Home

ACB-IT  August 2005

ACB-IT August 2005

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Catalogue of Investigations in Laboratory Medicine

From:

Bartlett Bill <[log in to unmask]>

Reply-To:

IT working group of the Association of Clinical Biochemists <[log in to unmask]>

Date:

Mon, 22 Aug 2005 19:26:47 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (391 lines)

In reply to the does Bill Bartlett's group still exist the answer is yes
and no. The original group as established by Ian Barne's who was then on
NCAB included Rick, James Paton and others does not meet as such. We
were particularly looking at the message content for requesting and
reporting and asked to produce a specification against a very tight time
frame.   Through various machinations there now exists a  Pathology
Messaging Requesting and Reporting group that is chaired by Simon Withey
under the Connecting for Health Banner. The output of the previous group
formed the starting point for this new group. It is composed of
Connecting for Health bods, commercial reps, James Paton and I attend
regularly with Ian Barnes and Rick Jones being kept in touch by e-mail,
Mike Catchpole of the HPA is protecting there interests.. The primary
role of this group relates to message content, but also is feeding into
the bigger picture by highlighting issues around Lab med that impact on
the Care Record and vice versa. Issues such as rendering of reports,
carrying of images,  minimum data sets, which data sets should and
should not be reported, general business processes around requesting and
reporting are all frequent topics for discussion. 

James Paton and Stephen Pill (GP) have been appointed  as National
Clinical Advisors on Pathology reporting and requesting.  

It appears that much of the functionality of that people might be expect
as part of the National System will really be existing at the local
level. There are many issues surrounding what will or will not be
available in the NHCRS centrally and also about the content of the
secondary uses services and functionality. I am told the EPR will exist
at a local level. What level of content/functionality that will be
restricted to the so called local level and whether the local level
means Cluster or Trust or  confuses  leaves me scratching my head a bit.


We certainly need to have as many forward thinking people as possible
active at the cluster level to ensure that we don not have systems
thrown at us that will define the way we work in such a way that it
restricts our opportunities to move forward. If I was particularly
cynical I would suggest that there is more profit for the LSPs if they
can force us to adopt old revamped technology than in investment in the
type of systems we would like to see in place. I hear a lot more about
what is happening in the Southern cluster than I do about the North
West. It is interesting to note that while the LSP contracts do not
include Pathology as core, requesting and reporting are. That is to say
that the LSPs have a contract that to provide systems that control our
inputs and what we can output. Rendering reports is an  just one
horrifyingly important issue that we need to consider and stand up and
shout about. I think that we all agree as lab specialist we do not
produce numbers, we produce reports. Thos reports are formatted often in
a way that we believe imparts information and knowledge  in a format
that we wish to our users to view it. While the informed users and
specialist user may be able to apply their own knowledge base to the
report not all will have this ability and hence the reason for
Laboratory Consultant, algorithms, expert systems etc that put together
the reports.  Deconstructing reports into a series of codes and numbers
that can be reconstructed by receiving systems may seem attractive to
some users, software providers and network managers, however if the
reconstruct does not reflect the format of the  original report
(admittedly in some cases it might be better) you can change the sense
of the original reports. If you cannot carry images (e.g. graphs) but
only the constitutive data which can be used to construct them  you can
again change the original sense of the report. For instance by changing
the magnitude of an axis on a tumour marker graph you can visually
change the impact of a change in consecutive results.  I am banging the
drum for an image of reports to be carried  alongside coded data to
enable best of both worlds. Of course this has ramification in terms of
message size and thus bandwidth. 

There are a whole raft of issues around requesting and reporting
functionality that are being addressed by various individuals at local
levels that will have a major impact on service delivery. Your Trust may
be purchasing systems from an LSP with ordering functionality that you
have had no role in specifying.  

 On another point if things become national (e.g. catalogues handbooks)
we need to ensure an infrastructure is in place that is not so ponderous
and complex that it stifles innovation and change. It can take may
months currently to get a new code in the bounded code list. Systematic
problems such as this require resource to manage the bottlenecks.

Regards

Bill Bartlett

PS this started as a two liner. Sorry seems to have turned into a rant.




-----Original Message-----
From: IT working group of the Association of Clinical Biochemists
[mailto:[log in to unmask]] On Behalf Of Muir Gray
Sent: 20 August 2005 08:09
To: [log in to unmask]
Subject: Re: Catalogue of Investigations in Laboratory Medicine

Where do westand with the nat lab handbook


On 16/8/05 09:44, "Jonathan Kay" <[log in to unmask]> wrote:

> This is very important. Let's just check which forum we want to use to

> discuss it...
> 
> College rep is James Paton.
> 
> It's multidisciplinary.
> 
> Does Bill Bartlett's group still exist?
> 
> Lead at CfH is Ian Arrowsmith
> 
> I'd prefer it to be national, but it's currently Southern Cluster.
> 
> There is an identified "Wave 1 of early adopters". We are one at the 
> Nuffield Orthopaedic Centre.
> 
> Jonathan
> 
> 
> On 16 Aug 2005, at 09:32, O'Connor John (Royal Devon and Exeter 
> Foundation Trust) wrote:
> 
>> Morning Chaps
>> 
>> I thought that the following offering from the Fujitsu Alliance on 
>> the naming of things might provoke a discussion thread on the SIG. 
>> But before I release it to the wider world, I thought it prudent to 
>> air it on mailbase first. It may become a national template so it is 
>> of relevance to all.
>> 
>> Cheers
>> John
>> 
>> 
>> 
>> 
>>> 
>>> 
>>> 
>>> Subject: Viewing of Southern Cluster Pathology Catalogue
>>> 
>>> 
>>> 
>>> Dear Pathology clinicians,
>>> 
>>> 
>>> 
>>> Based on the last 2 weeks of discussions and recommendation from the

>>> Southern Cluster Clinical Advisory Group and representative members 
>>> from the cluster Pathology steering group, we have taken 2 key 
>>> actions to ensure that NHS/FJA/Cerner will move together 
>>> successfully through our deployment programme for R0 - we have:
>>> 
>>> 
>>> 
>>> (1)     Revised the content configuration and layout of the
catalogue
>>> (with inclusion of some of the earlier comments from last week)
>>> 
>>> (2)     Provided a viewing opportunity of this catalogue for R0
>>> deployment
>>> trusts (Path Labs)
>>> 
>>> 
>>> 
>>> Background:
>>> 
>>> 
>>> 
>>> * The signed agreement between the NHS and FJA was that for R0, the 
>>> Southern Cluster will use an existing Cerner Millennium build and 
>>> configuration that is the Homerton and Newham hospitals. Their 
>>> current catalogue contained around 600+ investigations. After 
>>> analysis of this catalogue against our previous CSP catalogue, PBCL 
>>> catalogue, and the below mentioned national catalogue, we had 
>>> recognised that the existing catalogue is clearly not sufficient to 
>>> maintain current business processes for many of the trusts. We have 
>>> taken input from a number of these resources to build a catalogue 
>>> which we aim will meet most of the NHS business needs (see content 
>>> below).
>>> * The NHS CfH is also concurrently trying to complete an NHS version

>>> of the Path catalogue for the purposes of standardising the content 
>>> across the country - this is nearing completion. While not formally 
>>> released, FJA had been given a provisional viewing of this to 
>>> facilitate our rapid deployment programme. The NHS authority 
>>> themselves concurs with our experience that no catalogue will ever 
>>> be complete, without ongoing maintenance. Cerner will be adopting 
>>> the full NHS catalogue as we move to the next phase (or as and when 
>>> the NHS catalogue is finally completed and released). Future 
>>> maintenance will be based against the NHS standards. No formal date 
>>> is set for this NHS release, but is anticipated for later this year.

>>> This national catalogue is based on a SNOMED CT naming convention, 
>>> which is the NHS mandated standard.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> OBJECTIVE:
>>> 
>>> 
>>> 
>>> *       To provide a viewing opportunity by the R0 deployment sites
>>> 
>>> *       To try and clarify any queries
>>> 
>>> 
>>> 
>>> Special note:
>>> 
>>> 
>>> 
>>> * Any new content recommendation, we will be submitting this to the 
>>> NHS authority to be considered for inclusion in their National 
>>> Pathology catalogue - please note that we have drawn our content 
>>> from the proposed NHS Path catalogues. So if an item is not in our 
>>> catalogue, it is not likely to be in the National Catalogue. The NHS

>>> will need to know this as they need to ensure that all Clusters' 
>>> needs are met through their final catalogue releases.
>>> * Our maintenance of content will be against NHS catalogue content 
>>> releases
>>> 
>>> 
>>> 
>>> General explanations about the catalogue:
>>> 
>>> 
>>> 
>>> 
>>> 
>>> The content of the attached catalogue are drawn from:
>>> 
>>> 
>>> 
>>> *         The proposed NHS national catalogue for pathology
>>> investigations
>>> (this is the enhanced version of the current PBCL catalogue, later 
>>> to be formally released by the NHS. It extends the range of 
>>> procedures to secondary care settings)
>>> 
>>> *         Best practice data collection from the Common Solution
>>> Project
>>> from hospital trusts and its sub-departments
>>> 
>>> *         Cerner's internal catalogue from their content drawn from
>>> various existing deployment sites in UK
>>> 
>>> *         Newham and Homerton input
>>> 
>>> *         Provisional input from the SCCAG and Path Steering group
>>> 
>>> 
>>> 
>>> The naming convention of the catalogue:
>>> 
>>> 
>>> 
>>> *         The naming convention is based on SNOMED CT (fully
specified
>>> names) - the reason is to eliminate any ambiguities during the 
>>> review process
>>> 
>>> *         When viewing, please think of proper/generic chemical
names
>>> of
>>> the test to ease locating the test within the catalogue (eg. 
>>> "Dilantin level" is not in the catalogue, but "Phenytoin level" is)
>>> 
>>> *         The SNOMED naming convention will be adopted by all the
LSPs
>>> across the other clusters to minimise training needs of clinicians 
>>> as they move across clusters, which they invariably do during their 
>>> working careers.
>>> 
>>> *         Synonyms, or clinically common descriptors will be built
>>> within
>>> the catalogue to ease searching (most of this will be based on 
>>> SNOMED recommendations, and some others are common clinically 
>>> accepted acronyms).
>>> 
>>> 
>>> *         Where a SNOMED CT concept does not exist, we will use the
>>> current naming convention in Cerner until one is determined by the 
>>> NHS.
>>> The key is that we will provide the investigation to maintain 
>>> current processes
>>> 
>>> 
>>> 
>>> Deployment:
>>> 
>>> 
>>> 
>>> * The content of this list contains the entire catalogue which will 
>>> be loaded into the Cerner database. This does not mean all tests 
>>> will need to be provided at all sites. This only allows the trusts 
>>> to pick and choose the tests to be made available or hidden away 
>>> from viewing locally because the trust labs do not provide that 
>>> service.
>>> 
>>> 
>>> 
>>> Summary:
>>> 
>>> 
>>> 
>>>             We wish to provide a successful viewing opportunity for 
>>> the NHS R0 deployment sites. We will try to capture queries 
>>> associated with this catalogue. Please note that we are working 
>>> closely with the NHS authority to ensure that their National 
>>> Catalogue will in the future contain all the necessary content. Any 
>>> content we identify which are not currently available within the 
>>> National Path catalogue we will submit to the Authority for 
>>> inclusion in their later releases. We will be releasing the Cerner 
>>> Radiology catalogue within the next day or 2 for final viewing, so 
>>> please let me have contact names of any Radiology clinicians who you

>>> know need to be included.
>>> 
>>> 
>>> 
>>> Queries to send to:
>>> 
>>> 
>>> 
>>> [log in to unmask] <mailto:[log in to unmask]>
>>> 
>>> 
>>> 
>>> NOTE: ALL QUERIES ARE TO BE SUBMITTED BY CLOSE OF PLAY NEXT THURSDAY

>>> (25th August 2005)
>>> 
>>> 
>>> 
>>> Kind regards,
>>> 
>>> 
>>> 
>>> Wyman Kwong
>>> 
>>> 
>>> 
>>> Healthcare Domain
>>> 
>>> Fujitsu Alliance
>>> 
>>> Contact No.: +44 (0) 7867821276
>>> 
>>> Web: <http://uk.fujitsu.com>
>>> 
>>> 
>>> 
>>> This email is only for use of its intended recipient. Its contents 
>>> are confidential and may be privileged. Fujitsu Services does not 
>>> guaranteethat this email has not been intercepted and amended or 
>>> that it is virus-free.
>>> 
>>> 
>>> 
>>> 
>>> 
>>> ********************************************************************
>>> **
>>> ****
>>> *
>>> This e-mail is confidential and privileged. If you are not the 
>>> intended recipient please accept our apologies; please do not 
>>> disclose, copy or distribute information in this e-mail or take any 
>>> action in reliance on its
>>> contents: to do so is strictly prohibited and may be unlawful. 
>>> Please inform us that this message has gone astray before deleting 
>>> it. Thank you for your co-operation.
>>> ********************************************************************
>>> **
>>> ****
>>> * <<FINAL PATHOLOGY ORDER CATALOGUE APB1.xls>>
>> <FINAL PATHOLOGY ORDER CATALOGUE APB1.xls>


**********************************************************************
This email contains proprietary information some or all of which may be legally privileged. It is for the intended recipient(s) only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail. If you are not the intended recipient you must not use, disclose, distribute, copy, print, or rely on this e-mail.
This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
**********************************************************************

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

April 2024
February 2024
January 2024
June 2023
May 2023
January 2023
December 2022
May 2022
April 2022
March 2022
February 2022
January 2022
December 2021
October 2021
September 2021
May 2021
April 2021
March 2021
February 2021
January 2021
November 2020
June 2020
May 2020
April 2020
March 2020
February 2020
June 2019
May 2019
April 2019
March 2019
February 2019
December 2018
February 2018
December 2017
November 2017
October 2017
September 2017
June 2017
May 2017
March 2017
February 2017
January 2017
December 2016
November 2016
May 2016
April 2016
March 2016
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
May 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 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
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 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
December 2006
November 2006
October 2006
September 2006
August 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
September 2004
August 2004
July 2004
May 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
July 2003
June 2003
May 2003
April 2003
February 2003
January 2003
December 2002
November 2002
August 2002
October 2001
August 2001
May 2001
March 2001
February 2001
December 2000
November 2000
June 2000
March 2000
February 2000
September 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 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