In article <[log in to unmask]>, Ahmad Risk
<[log in to unmask]> writes
>> >If your computer system does not mail merge patients details etc
>> >onto a word document, change it!
>
>> The Vamp Medical system doesn't, does it?
>
>I don't know a thing about VM (except that it is naff, allegedly!),
>but ViSion does.
>
VAMP Users may not be as voluble in their praise of their system as Emis
users (remarks in another thread) but the VAMP system is about the most
used nationally. It works, does what is expected, is written to the
relevant RFA standards and is one of the well used links systems.
Although I will admit that from remarks from the IT dept at my local
FHSA it may generate more transmission problems: maybe because it is the
most used local system.
The VAMP Medical system cannot communicate directly with Word for
Windows because it is not windows software. It is not even DOS software.
This, of course, frees it from the risks of DOS/Windows based virus
attacks. It also makes searching arround the Operating System rather
difficult as the command set is completely different thus freeing it
from clumsy fumbling.
VAMP medical itself does have a simple word processor that uses merge
marks for many items of patient data. It does not have all (any of?) the
features of Windows products. It is quite capable of printing letters
for groups of patients for eg. smear recall.
The way to transfer data from VAMP Medical to Windows wordprocessors is
to run VAMP in a "Window" using Terminal or PC Workstation (PCWS) and
use the cut & paste features of windows. For larger quantities of data
file transfer procedures exist but these are quite specialised and have
been unintelligible to people in the past!
Isn't that so Ahmed? :-)
I have considered migrating to Vision but I feel I can get more out of
my VAMP Medical system at present and thus cannot justify the cost.
--
David J Brown
Rather Senior Lurker but quite infrequent poster.
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
