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: Re: Computer system problems and testing approaches

From:

"Mike Wells" <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 1 Jul 1996 09:49:03 GMT0BST

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (113 lines)

Alan Midgley wrote
> From:          [log in to unmask]
> Subject:       Re: Re: Computer system problems and testing approaches
> Date:          28 Jun 1996 20:10:38 GMT
and produced a starter kit for what he (and I on your behalf) wants.
Can I ask GP-UK to provide help with putting some glosses on
this? And please PLEASE do not interpret my questions as challenges.
I am not trying to score points, but to indicate how some perfectly
reasonable requirements may affect HOW things are done, and may even
be mutually incompatible with other, perfectly reasonable
requirements, in which case the User Community needs to reach
agreement on what gets watered down.

> Mike Wells wants what we want it to do, not how:-
>
> I want a narrative of the entire history of the patient in order of
> happening, neatly typed with a little bit of laying out to make it easier to
> read.

Who will type it?  And When?   Is it free text, with markers defining
what sort of information it is, that are inserted by whoever
types in, (Gerard are you listening), or is it to be entered into
some sort of pre-defined sheet.  Or would you like both?

If more than one person can do the typing ( and I cannot see how you
could manage if only one person can), what arrangements woud you like
for controllong access, and for resolving clashes when two or more
people wish to update the records simulataneously.
    It matters you see, because this is a decision on what you want to
do, that will seriously affect how you do it?
>
> I want it to be foldable into an outline, displayable by topics or
> problems, searchable on free text.

I see no particular problems with any/all of that.  There may have to
be debate about the speed of the search engine (or more accurately,
how long you are prepared to wait for a search to complete) and on
what you will do about spelling and fuzzy matching.
>
> When I open a patient's notes I wish to be presented INSTANTLY with the
> text of the last encounter, while this is being transferred to my brain I
> want the patient's summary to assemble behind it, with the problem list and
> current treatment appearing similarly behind and to the sides ready for
> attention by clicking on them (or otherwise activating thaose bits of
> record)
Fine.

>
> Somewhere about this whole lot I want the equivalent of a sticky note,
> which can be placed right on top to be seen first thing, and I want this
> note to be un-audit-trailed, ephemeral, unattributable, deniable,
> temporary.  (but everything else in the system the opposite of those
> attributes)
I think there might be problems here!  Who will be able to put the
'sticky note' there?  How will you know whether to believe the note or
not?  The reason for asking is that the mechanism for associating the
sticky note will need to be ever so carefully designed.  The note
cannot go IN the record, because it has to be all the things that the
records are not, so it must be associated with the record, but not be
part of it.


>
> When I go home I want the system to be seething with thought and activity,
> looking for things to claim payment for, and thinking up hints for me about
> difficult medical problems, which it can deliver with coffee in the morning.

I like it.  Of course, the engine that does all this will need to be
totally tamper proof, since presumably it has access to the records
in order to do its job.  Who will be able to fire up this engine, and
who will be able to see its results.  In particular, what steps are
needed to ensure that it is not possible to breach patient privacy,
by starting up lots of searches which home in on a single patient;
or is this seen as an accepatable risk?
>
> I want the ability to run ordinary programs alongside the clinical system
> (eg I want a non-dedicated word-processor, networked fax, e-mail, separate
> reference database)

That is what modern systems are supposed to be about.  There will
need to be thought given to ensuring that these sub-systems do not
provide all manner of security loop-holes, and any access they might
make to the underlying data base will need to be controlled and
audited.
>
> Whenever I run a search to produce a list of patients with {a|b&&c|d} I
> want one click on a name to take me to the notes of that patient.
>
Sounds reasonable to me.  Who is the 'I' who runs the search?  How
important is it that there is control over the type of search, and
over the number of patients in the cells that result?  Again, it
matters.  If there is not control, then we have a security loop-hole.
the result

> That the sort of thing you want Mike?

Very helpful.  We should do this more often!!

Mike Wells



>
==========================================================
Professor Mike Wells
Department of Physics,    The University of Leeds
Leeds LS2 9JT,            United Kingdom
Phone: 0113-233-2339      E-Mail   [log in to unmask]
==========================================================


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

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