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

Help for GP-UK Archives


GP-UK Archives

GP-UK Archives


GP-UK@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

GP-UK Home

GP-UK Home

GP-UK  1996

GP-UK 1996

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Free Pharmacy Link for GPs - Complete

From:

Ross Anderson <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 12 Nov 1996 08:59:09 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (130 lines)

> PRS seem to have gone to great lengths to satisfy issues of
> data security and confidentiality

I've never heard of them. If they are serious about security then
why haven't they been in touch with us?

Does their system follow the BMA security policy? Are scripts
digitally signed? If not, what's to stop them being altered?  If so,
then how do they propose to manage signing keys? Will their trust
structure adopt the approach of one of the crypto pilots (and if so
which), or will it introduce yet another key management system?

> This software manages repeat script processing between GP and
> pharmacy and works with the underlying clinical system...
> using Reuters "Encounter" screen scraper

So the software is inside the practice's trust perimeter. What tests
have been done to ensure that it isn't a threat to either safety or
privacy? Even if it doesn't accidentally copy the personal health
information of other patients, how do you know it doesn't have bugs
that could subtly corrupt the practice database?  Has it been
evaluated under ITSEC, and if so to what level?

> Script manager connects to PRS's database using Racal Healthnet and the
> infrastructure already in place  to support GH-HA links. The system
> currently only handles repeat scripts but PRS say it will be extended to
> cover acute scripts.

Does this mean that the PRS database now becomes yet another large
aggregate of personal health information outside clinical control?
How well protected is this database anyway? It says:

> All the data flowing through the system is stored on PRSs central
> database which sits on a dedicated DEC alpha array in Racals ultra high
> security data centre in Runcorn.

That tells me nothing. Are they running on an ITSEC evaluated system?
Even if technical security measures are good, then what controls are
in place to prevent the information being passed to third parties?
They may say that

> they don't intend to use the data for purposes other than the
> provision of the services described

but is there an enforceable contract with anybody? Who will audit it,
and who will be responsible for reappointing the auditors (PRS)?

Suppose that the police ask for information on patient X. Will PRS
supply it quietly or fight it noisily? Will the patient - or his GP -
even learn that the police have been added to their access control list?

> Where the patient has requested that their scripts are transmitted to a
> "Health Plus" pharmacy the repeat is produced and transmitted

When the patient is asked for consent, what sort of information will be
supplied on the risks (answers to all the above questions)?

> Data is encrypted and identifiers are transmitted
> separately link by a code which would be meaningless  to  anyone
> intercepting the data.

If the encryption is sound, then why de-identify the data as well?
What algorithm is used - Red Pike or 3DES?  How are pharmacists'
decryption keys managed - does the government (or PRS) have a copy of
them? Has the key management protocol been subjected to formal
verification?

How meaningless would the code really be? Would it be like the
combination of postcode, date of birth and Soundex code of surname
used to pass around information on HIV sufferers without their
consent, or merely the combination of date of birth and postcode used
to index information on hospital treatment in the HES system? In both
those cases, the system owners were loudly confident in the privacy
protection that their stupid mechanisms gave. (In the case of HIV
data they still are.)

> Patients wishing to use the system will be expected to "register"
> with a particular "Health Plus" Pharmacy" to which the script will
> be forwarded

So if there's a long queue at Boots, I can't just go down the road ...

> The script will carry a bar code on the right hand tear off portion of
> the form and this will be used in conjunction with a bar coded patient
> held card and to link the paper and electronic script, finally by
> scanning the pack bar code a complete audit trail and check that
> prescription and items dispensed match is provided.

So we are not dispensing with paper; we are running paper and
electronic systems in parallel. That's nice. But who will end up
bearing the extra cost, and how will PRS make their money? What is
the business model?

On Ewan's description, the net effect of the system appears to be:

(1) some work is saved at the practice but at the cost of getting
    the patient to carry yet another card around. The cost of
    administering a card base is nontrivial and this appears to fall
    on the GP. There seems to be an expectation that HAs will pay up
    in the expectation of better compliance. Will they?

(2) a large database of personal health information is created that
    appears to be under the control of PRS rather than one of the
    clinical professions. It doesn't even appear to have an explicit
    contract with the Department that forbids it from selling data
    other than to the originators of that data, as Clearing has (and
    I'm not completely happy with Clearing)

(3) reliance is placed on a number of encryption and de-identification
    mechanisms which we haven't seen. Experience is that such
    mechanisms always have bugs and need to be subjected to capable and
    hostile review. This is not just my view - it is that of GCHQ as
    well

(4) There is a lot of work going on at present to try and hammer out
    agreement on crypto standards and build a trust infrastructure. I
    am concerned that the introduction of somebody's home brew
    encryption solution will muddy the waters and make everything more
    complex.

I think we need to be told a lot more before we can be expected to
recommend this to patients,

Ross




%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

March 2024
October 2023
August 2023
June 2023
May 2023
February 2023
June 2022
October 2021
January 2021
October 2020
September 2020
August 2020
July 2020
June 2020
March 2020
January 2020
December 2019
September 2019
July 2019
June 2019
May 2019
March 2019
February 2019
January 2019
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 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
1997
1996


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