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: Meduser/system 2000/ premiere/ to Vamp data conversion

From:

"Laurie Slater" <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Sun, 1 Nov 1998 14:05:45 -0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (78 lines)

We migrated to Vamp Vision in 1995, from a rather simple and
wonderfully robust DOS based system called Medi-pro. In those
days the system and data files for 4000 patients sat in a single
directory and took up < 50mb of hard disk space. You could zip
them up and download the whole system onto a PC at home in 5mins
or so. If there was a software bug the GP who wrote the system
would send a fix on a single floppy by return post - ah sweet
nostalgia!

If I had known Vision then as I do now, I would have done things
very differently. It is a large and complex system which is
flexible enough to let you use it in very different ways. You
need to know where and how you are going to store data before you
start. So:

1. Familiarise yourself firstly with the consultation module. Ask
them to supply you a stand alone version that you can play with
at home. I would recommend at least 1 month before you make
policy decisions.

2. Use the opportunity to draw up data entry protocols for your
practice (be very specific, i.e. what data, who enters it, when,
on what machine, who checks that it is being done properly etc.)
Decide this amongst yourselves at a dedicated practice meeting -
involve everybody. Consider developing your own read code
formulary (they should supply a cut down database of commonly
used codes if you ask).

3. Initially we transferred all our read codes straight into the
medical history section, which was a mistake albeit an aesthetic
one. If you plan to go paperless and use the system in
consultation I would advise using the designated storage areas.
Initially it may be harder to find stuff, but will pay dividends
as you accumulate data.

4. Do not ignore priorities on medical histories. They are
essential and you should use them from day 1. There should be a
mechanism whereby you can decide on priorities for various
diagnoses and for these to be allocated automatically on data
transfer.

5. Talk to Alison Young who is both knowledgeable and sensible.
Do not settle for less! (Hi Alison!!)

I expect things have moved on a lot since we went through the
hoop, but if I told you that this was not a monstrous
undertaking - but I 'd be lying! However, as alluded to by the
Risk oracle in a parallel thread, your pain will be reduced in
direct proportion to the time you invest in preparing the
transfer and the money you set aside for training yourself and
your team.

Good luck! Do let me know I can be of further help.


Laurie Slater
[log in to unmask]


-----Original Message-----
From:	[log in to unmask]
[mailto:[log in to unmask]] On Behalf Of John Wilkinson
Sent:	31 October 1998 17:38
To:	[log in to unmask]
Subject:	Meduser/system 2000/ premiere/ to Vamp data conversion

 << File: vcard.vcf >> Has anybody done this? We may well end up
doing it and we need to know
how much it's going to hurt so we can brace ourselves. ( 16
terminal
network on thin-net/novell, used mainly as a big expensive
FP10 ----
hopefully will become paperless supernerd site later).



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

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