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:

Re: [Hubris]: the advantages of a document per patient

From:

Gerard Freriks <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Mon, 16 Mar 1998 01:17:07 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (134 lines)

Hi,

Wellcome in the bandwagon of the Document Paradigm.

(And. Don't tell me you never heard thoughts, like yours, before in this
list  :-)

By the way.
Databases stay handy when one has a birthday and name but not the
PatientNumber which is used as an index to the patientfiles.

In order to process all those patientfiles we need markup (XML) to make
information out of the data.
And all those labels will have to have names/terms and defined uses.

For the Document  Paradigm to succeed we need an uniform set of
Terminologies and Rules based on a General Domainmodel.
MedSpeak for short.
MedSpeak is a limited set of Domains (or Contexts) each with a limited set
of Terminologies describing Concepts and a set of rules.

Greetings

Gerard

ps: The future knowlegde is in Documents now.


At 5:40 PM +0100 9/6/97, Adrian Midgley wrote:
>All GP clinical record systems at present in widespread use
>use a database management system which lumps the various
>individual items of the records of each patient together.
>
>Some of the more avanced ones use a relational database,
>and some of the most successful and effective do not appear
>to use the relational model.
>
>The result is that if a problem develops with part of the
>database it is very likely to affect all patients.
>
>If this merely a matter of a polite notice appearing from
>the program that it was temporarily unable to provide
>details of previous immunisations (say) or the old
>addresses, and that it had identified the nature of the
>problem and was rectifying it behind the scenes but would
>meanwhile do its best to present the rest of the
>information held, this would be fairly tolerable.
>Unfortunately the error message tends to be less informative
>and placatory, and the program rather than failing
>gracefully into a limpalong mode while it sorts its
>troubles out - crashes.
>
>Reindexing a modern GP database proceeds fast, but the more
>elegant and Read code based the design the larger the
>data tables are likely to be and therefore the time
>required is liable to be long now and will be progressively
>longer in the future as records expand.
>
>The converse approach, as practiced in Surgery manager, of
>dividing information into many many tables and thus storing
>much of the meaning by context rather than explicit codes,
>could offer rapid repairs of the individual tables, and
>holds out the promise of a graceful degradation in
>performance if one or more tables is damaged, but in
>practice there has been insufficient attention paid to
>reporting the location of the failure and therefore the
>standad help-line advice of "reindex it all" is liable to
>be what one does.
>
>More complete diagnostic facilities would ease the task of
>the help-line,  thus rendering it less important that one
>is unable to get beyond queue position one or obtain a
>reply to e-mails.
>
>Given that the help-line service seems to be the one most
>difficult for all suplliers to satisfy their customers on
>increased diagnostic acumen built into the products would
>seem to be a useful advance.
>
>However, documents...
>---------------------------------
>Placing substantially the whole of the individual patient's
>record in a single file, group of files or even directory
>and presenting the internal structure through a suitably
>defined viewer, and altering it with a suitable series of
>commands through such a viewer seems to have much to
>commend it.
>
>One might lose an individual patient's notes, but would
>expect to retrieve them from backup, and meanwhile have no
>troubles with others.
>
>They could be encrypted, contain links to pictures or the
>images themselves, and in general be used as the
>word-processed documents they are.
>
>They could also rather conveniently be copied to another
>location, and a viewer provided - along the lines of
>Microsoft's Word viewer which permits inspection and
>extraction but not alteration.  If the format and the
>viewer were good then the supplier might reasonably hope to
>spread its use further.
>
>So Why Databases
>-----------------------------
>Well, firstly they were what was to hand.
>Secondly, the major impetus from the College and DoH
>was to run a card index, and although even then Grep and
>its ilk were effective search tools for disparate files,
>there is no doubt that a database is quicker for searching
>organised data.
>
>However, now with stunningly fast hardware, and with clever
>search engines and document indexing systems, and with the
>examples of marking up systems in use widely - the time has
>come to recreate teh electronic pateint record.
>
>
>
>--- OffRoad 1.9r registered to Adrian Midgley


Gerard Freriks,huisarts, MD
C. Sterrenburgstr 54
3151JG Hoek van Holland
the Netherlands  		Telephone: (+31) (0)174-384296/ Fax: -386249
				Mobile   : (+31) (0)6-54792800
ARS LONGA, VITA BREVIS




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

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