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: Data conversion/transfer: a proposal

From:

[log in to unmask] (Adrian Midgley)

Reply-To:

[log in to unmask]

Date:

Mon, 1 Jun 1998 15:05:02 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (69 lines)

>From: Mary Hawking <[log in to unmask]>
>Subject: Re: Data conversion/transfer: a proposal
>Date: Mon, 1 Jun 1998 07:19:59 +0100

>>It has been a requirement since RFA 1 for systems to be able to
output their 
>>data in to an ASCII file for which documentation must be available. 

>Is there a requirement to be able to import data from an ASCII file as
>well? and if so, is there any difference in the ASCII files generated
by
>different systems?

Alas, that one was never written in.  Bizarre IMHO.
However, work is going on in which at least one Meditellite is 
involved on sorting out a way of importing partial records from one 
system into another.

Given that the target is only to do better than retyping (or 
scanning and correcting the scannos) the printout from the last 
practice into an encounter entry it should be very easy to achieve 
something.

I think that the database approach to GP records ignores the 
unclassified morass of interesting material and marginal notes which 
makes up an important and very human-usable part of the record.
Each area of the EMR could do well to have a single memo field or 
plain format file associated with it, so that one would have a 
series of lines of summary info for instance, with a bucket at the 
bottom.  Yes, people would put things in the bucket that should be 
coded and classified, but 
 - getting them on the record means they can be processed 
  with electronic assistance
- code can be devised to inspect the bucket either periodically, in 
  the background, or on entry, to note such terms as asthma and MI 
  and for the bucket wizard to suggest an appropriate place to paste 
  these into the formatted EMR.
- an item in the bucket is clearly distinguished as being from 
  somewhere else or otherwise less true than the ones we enter in our 
  own coded areas.  About like hospital letters filed _with_ the 
  notes, rather than in them.

The treatment history bucket for instance might contain a list of 
OTC drugs and other preparations the patient has had.

Another approach to handling the data format incompatibility problem 
of course is to leave the data where it is in its original format, 
and publish it over the web in response to an interrogation which 
carries a code confirming the patient is registered to the inquiring 
practice.
The host practice system would then present the patient record in 
its normal format on a browser view, allowing each of us the 
occasional opportunity to view each other's systems form the comfort 
of our own desks.
Of course, it would be no time before peple startd writing screen 
scraping code, or Java/Script or whatever which presented the info 
in a common tagged format........... and then we can get on with a 
platform independent medical record displayed in a platform 
independent fashion using common standards which allow infinite 
variation by the individual programmers and users.

Bring on the bucket though, as the first step.


--- OffRoad 1.9r registered to Adrian Midgley


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

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