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  1998

GP-UK 1998

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

[Hubris]: Adapting EMR Processors to the PCG, genericising Knowledge Service API

From:

"Adrian Midgley" <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Fri, 25 Dec 1998 11:45:59 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (90 lines)

In the near future clinicians will use systems already on the market to read
and write medical records.
The idea of the PCG implies a need to provide identical material to every
clinician, and for this to work it must be presentable at the time it is
relevant.

For instance feedback relating to the number of lumbar spine X rays ordered
by a particular Practice or GP, with the implicit aim of influencing
this[2], would best be presented as a selection bar hovers over the symptom
code for back pain, the node for investigation in the script for handling
back pain as this is reached should it be in use, the Xray ordering menu
choice for spinal Xrays and so on.

The method of choice for constructing such advice documents is to write them
as either plain text, or lightly marked up HTML, the latter has an advantage
in that graphs and diagrams may be of some value[3] and deliver them through
a generic web browser window alongside the EMR.

The advantage of genericising it thus is that a PCG or indeed a national
health service in which exist several different clinical systems could
nevertheless produce consensus documents in a single format, moreover one
which is internationally standard.  Disadvantages appear to be confined to
the commercial interests of suppliers[5], and the need for sufficiently
sophisticated displays[6] on clinicians' desks.

The API Required
-------------------------
Hardly so complicated as an API, in fact what is needed is the capacity for
a clinician, a practice, or a PCG to place a URL in a table with a hook into
the EMR, so that for instance when the EMR processor is about to display an
investigation dialog for back pain, if a URL is entered opposite that, up
comes the relevant page.  From there the HTML can include links to anywhere
appropriate, remaining in the Knowledge Service browser.

The size of screen is significant at this point, as the screen area used by
a dumb terminal or a 14" VGA display is reckoned to be the minimum
acceptable for displaying the EMR, and many users still panic if one full
screen application supplants another.  On a 17" CRT there is plenty of room
for overlapped windows.

Moving on to a display of the EMR in one browser window, from an interface
to the existing EMR engine and database seems an uncontroversial development
but not one for which there is a great rush.

Cascade
-------------
Using HTML it is quite straightforward[7], to supply sets of pages from one
or more central location, which can be supplantd by a locally edited version
which either augments them or indeed contradicts them.  Attempting to remove
the possibility of such contradiction is unwise as the central guidance
would instantly lose any respect, but it would be prudent of each practice
and PCG to apply editorial rules that include a linkage to the centrally
held version by which a user can drill down to get at the first opinion.

It would also be prudent of a central body, the NHSIA or the national
electronic health library, to seek out variant documents and appraise them,
leading in some cases to an editing of their own version and a convergence
toward a wider consensus.  Modemocracy crossfertilising with a universal
data corpus.


============
[1]  One cannot oblige people to read anything, but it would be foolish not
to provide it in an easily readable form at the time when it is most likely
to be useful if read.  Paper guidelines are of little value or effect.
[2]  In theory toward the correct number, in practice toward fewer.
[3]  For instance a frequency histogram of the number of lumbar spine xrays
ordered in a given quarter per practice[4] - the information fed back to N&E
Devon GPs, with a pointer to show where in this the particular practice or
GP falls.
[4]  Oddly enough without any indication of the number of partners in the
practice, in order to preserve a confidentiality some GPs still feel to be
proper and necessary.
[5]  And in fact several of the suppliers are content to work at perfecting
their EMRs, and collaborate with suppliers of Knowledge Services, and this
is probably in their interests as well as their customers' and the State's.
[6]  Although a WinTerminal or other new device could be used,  effectively
this means a 15"-17" CRT screen or equivalent, with a PC running on a LAN.
This is basically the standard device nowadays in most professions.
[7]  Admittedly the magnitude of the task could become a problem to manage,
but the management of it can also be done in a distributed fashion, if the
managers can open their minds to the possibilities of the technology.

--
Adrian Midgley  GP, Exeter



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

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