Glen,

I think my problem was an additional cr lf at the end of the HL7
message that was causing HMV grief.

Rodney

>>> "lrs_y_gk_07" <glenk@...> 29/03/2007 15:53 >>>

Get the latest ATTrack Update from

http://www.lrsupport.com.au/downloads
<http://www.lrsupport.com.au/downloads>

(Just get the Zip file might be simplest)

Glen.


--- In alltalk-avp@..., "rodneyebird" <rodney.bird@...>
wrote:
>
> Glen,
>
> The HMV documentation shows a menu item of File>HL7>Extract.. or
Load..
>
> This is not showing on the HMV I have istalled - version 1.0.1.10
>
> Unable to find any reference elsewhere in the group.
>
> Rodney
>



IMPORTANT: This email and any attachments are for the sole use of the
intended recipient. They may contain confidential or privileged
information. This information may not necessarily be the view of St John
of God Health Care Inc (SJGHC). SJGHC does not warrant, represent or
guarantee the accuracy or completeness of the information. SJGHC does
not accept liability for any loss or damage in connection with the
information. If you are not the intended recipient then any use,
reliance, interference with, disclosure, distribution or copying of this
information by you is unauthorised and prohibited. If you have received
this email in error then please notify the sender by return email and
delete all copies. SJGHC does not waive any privilege.

Glen,

The HMV documentation shows a menu item of File>HL7>Extract.. or Load..

This is not showing on the HMV I have istalled - version 1.0.1.10

Unable to find any reference elsewhere in the group.

Rodney

Get the latest ATTrack Update from

http://www.lrsupport.com.au/downloads

(Just get the Zip file might be simplest)

Glen.

--- In alltalk-avp@..., "rodneyebird" <rodney.bird@...> wrote:
>
> Glen,
>
> The HMV documentation shows a menu item of File>HL7>Extract.. or Load..
>
> This is not showing on the HMV I have istalled - version 1.0.1.10
>
> Unable to find any reference elsewhere in the group.
>
> Rodney
>

1) In Notepad create a logon entry and a list of your users in the
following format:



user manager
pass <alltalk server manager password>

crea username=mb1 type=1 name="Mailbox 1" emailpassword="mb101"
crea username=mb2 type=1 name="Mailbox 2" emailpassword="mb201"
...
crea username=mb87 type=1 name="Mailbox 87" emailpassword="mb8701"

... as many as you want....



2) Select all and Copy into clipboard. (ie CTRL-A, CTRL-C)

3) Telnet to the Alltalk server on port 21110, ie at DOS prompt or Run

    TELNET myalltalkserver 21110

4) Paste the clipboard contents of Clipboard (just right-click in the
screen if using windows Telnet).

5)<enter>

6)quit

Each Mailbox will be created in turn.  Errors may occur if you run out of mailboxes during the creation process.

VOILA!

Important!

The Auto Start at logon feature of the Alltalk Scheduler is prevented
from functioning by the increased security protocols in Vista.

YOU MUST ADD a shortcut to alltalk in the All users startup for Alltalk
to automatically start when the user logs on.

Create a new shortcut On the desktop with the command being
"c:\alltalk\alltalk.exe" /s

Now, move the Shortcut into the Start up folder.

Right click on the Vista Start button and select "Explore All users".

Navigate to Programs--> Start up.

Drag the new desktop shortcut into the start up folder.  Vista will
require administrator permission to add the shortcut to Startup

--- In alltalk-avp@..., "lrs_y_gk_07" <glenk@...> wrote:
>
>
> Does Alltalk Work on Vista?
>
> Yes.  It all works fine.
>
> The current release of AVP Does not automatically create the Alltalk
> Printer object.  Updates will be availalbe sortly
>
> Vista View <http://www.galkam.com.au/alltalkonvista.jpg>
>

Dear all,

With the Beta Trials of Alltalk 1.1.1.80, it has been discovered that the Midas.dll used to render the Entity and Site XML information into HTML tables by the AlltalkWI CGI, are not distributed with the  Alltalk Server install.

Problem:

After a client has updated their Organisation and Entity information and uploaded it to the Alltalk server, the client can no longer log onto the Alltalk User Web interface because the user page returns and Interal Server error.

The problem is that when the CGI attempts to convert the Entity and Organisation XML data  into HTML, it expects the Midas.dll (Borland) to be present on the machine.  When the dll is missing, the getUser Action has an unrecoverable error which terminates processing of the request and returns an error message to the clients browser.

Resolution.

Get the midas.dll from http://www.galkam.com.au/zipfiles/midas.dll and save it into the Web servers SYSTEM32 folder.  The next call to the users web interface will be successful.

Reproducing this problem:

1) Update a test client to Alltalk 1.1.1.80 Beta client from http://www.lrsupport.com.au/downloads

2) On the Organisation and People Tab, Click Edit and enter the Organisation (Site) information and Some Entity (People) information.  Click OK

3) Fetch files.  The alltalk Client will upload the client information to the server.

4) Access the alltalk Web interface either as Manager or as the specific client user ID. 

5) If the midas.dll is missing, you will see "Internal Server Error" 

Does Alltalk Work on Vista?

--Updated message - removed private email address from message content.

From: Dr Brian Conway

Sent: Sunday, 21 January 2007 9:10 AM
To: Glen Kleidon
Subject: Re: Equery request

Getting the specialists seems to be hard. Less of them use computers it seems, and they were left out of the Broadband for health and practice improvement incentives. What Argus did was to get the GP Divisions to invite the specialists practicing in the area along to the meeting as well. Argus put on a dinner at the Pub. (The person representing Argus didn't actually know anything about the product!) but from that meeting there were many requests for installation but at that time it was free. The promotion for it was done by the division in terms of getting people to the event. The real drivers for this seems to be the receptionists/practice managers who have to employ an extra person to scan all of the incoming correspondence in. One of them got up and threatened the specialists saying the practices will start to adopt a practice of only allowing the doctors to refer to specialists who have electronic messaging! The fact that Argus can't handle referrals from GPs to specialists never came up. I thought it could but have since found otherwise.

[Glen Kleidon]Tricky that bit isn't it.  Just as well Alltalk does it.

Can Alltalk be used by people without practice management software (PMS), e.g. if they only use a word processor and have an internet connection? I assume this is what AVP does.

[Glen Kleidon] Yes, There is a word plugin for this too (actually it's a bit out of date and needs some work) but otherwise a standard AVP template is fine in MS Word.

Can non PMS people receive and read and print (I.e. do you have a viewer if no PMS?)  

[Glen Kleidon]

There are a couple of add-ons that allow for this including a Fully featured PIT and HL7 viewer and PIT-to-word which automatically converts PIT documents into Word documents as they are received by Alltalk.  RTF are viewable directly from ATMessage Viewer.  SO if you send Rich Text created in Word or you use the RTF save type in AVP Templates, then the person at the other end can just browse into the message Section from ATMsgViewer (turn on Popups in Alltalk Options).

Medical Objects has a word plug-in, 2hippo doesn't need any special software, division report is apparently expanding, they target individual divisions set up in an area and then move on. They are $30 per month to be able to send but can do individual PKI, apparently free to receive, 2Hippo is $27 per month to receive, but free to send,, Promedicus is $15/ week plus 85 cents per message for specialists, but they do have a large client base (13000 doctors) and works on all platforms. healthlink is currently free, Argus free to use but $300 to install. Medical Objects is free to GPs, but they charge specialists $750 per year to send but free to receive. Healthlink free to use and free if x-ray or pathology set it up. Medemail is free but has limitations but I think only uses RTF so could be used by people without PMS but I think it is fiddly, certainly no info other than for MD on the website but have asked for more info. 2hippo obviously got a fair number of people to try it. as I notice there are now a lot of "Pending" users, which means non active, they can still send but not receive, but might be able to receive from those who pay for "outbound packages" or who are sponsored by a specialist. Many of these systems sting the specialists, but I think the smarter strategy is to get the revenue from the hospitals and pathology and X-Ray providers. Its hard enough to get specialists interested, let alone charge them a lot. Allied health seem to be left out in a lot of systems (speech pathology, physio, psychology, occupational therapy, social work, dietitians) and not a lot of them seem to use PMS, but most are using word processing. Also most systems assume that specialists don't make referrals, we do, to other specialists. I would like more specialists on board to be able to do this, I mostly fax referrals currently or hand them to the patient.

if you can get the major hospitals on board in terms of sending Discharge summaries, and outpatient letters,  then there is greater impetus for the GPs and specialists to take up the system. I know Argus and division report are looking at doing this. I currently use the connecting care portal to send some referrals to monash but this is fiddly. If they could receive valid referrals via alltalk from GPs  and specialists this would be a great bonus.

[Glen Kleidon] Barwon health (Geelong hospital) has been doing this since 2001.  The Geelong area is pretty much all on Alltalk/EQuery and creeping along to coast to Warnambool and through Swanhill and Echuca.

Is the license fee for Alltalk/AVP a once off? Is there going to be a charge for sending or receiving or a monthly or annual subscription?

From my point of view Alltalk seems to hold out the most promise, but you will need to solve these issues of every doctor being able to sign in a multi doctor practice. What are the cross platform (OS) capabilities of Alltalk? I'll keep my eye out for meetings.

[Glen Kleidon] No ongoing fees for Alltalk or AVP.  Alltalk is available on Mac/Linux/Sun for downloading (ie receiving) but not currently for sending.

As for multi-doctor AVP already works in this environment for MD2/3 and ZedMed (probably also MedTech32), just not Genie.  Genie has a bit of a strange method for exporting the files – but as mentioned, I need to update AVP to get around this trouble.

Damien has pointed out that the USRL command in Step 2 does not
regenerate the EQK files as expected.
In step 1(c) after >

Ø      Xcopy \\myoldserver\mailboxes\*.aci
  c:\alltalkclients\mailboxes /e

Add

Ø      Xcopy \\myoldserver\mailboxes\*.eqk
  c:\alltalkclients\mailboxes /e



--- In alltalk-avp@..., "lrs_y_gk_07" <glenk@...>
wrote:
>
>
> DRAFT NOTES: 10/01/2007
>
>
>
> Moving your Alltalk Server to a new Machine.
>
>
>
> These notes relate to moving the Server components only.  Remember
that
> the Alltalk client you do most of your sending with may also be on
the
> same machine!
>
>
>
> There are 4 steps:
>
>
>
>     1. "Install" Alltalk server on the new machine    2.
> Re-license the New Server.    3. Move the Web management page.    4.
> Move the client mailboxes and resync the logs.
>
>
>
> 1.    "Install" Alltalk on the new machine.
>
> a.    Copy the c:\alltalkserver folder in its entirety to the new
> machine.
>
> b.    Using RUN or from the dos prompt execute:
>
> C:\alltalkserver\alltalksvc.exe /install
>
> c.     Re-initialise your client files by copying the ACI files
from the
> original machine.  Assuming you want to move the server in exactly
the
> same structure as the original machine execute (adjust to match your
> server names and pathways) :
>
> Ø      Mkdir c:\alltalkclients
>
> Ø      Mkdir c:\alltalkclients\mailboxes
>
> Ø      Xcopy \\myoldserver\mailboxes\*.aci
> c:\alltalkclients\mailboxes /e
>
>    (all on one line)
>
> d.    Note: If you want to change the file structure, make sure
this is
> adjusted in your settings (c:\alltalkserver\settings.txt) file.
>
>
>
>
>
> 2.    Re-license the Server.
>
> a.    In the Windows Management console, start the Alltalk control
> service.  This will reinitialise your security file
> (c:\alltalkserver\_security.inf) showing the PC Code.
>
> b.    Email the PC code to support@...
> <mailto:support@...>  (and the mailbox count from your
> settings file) and LRS will issue you with a new server code.
>
> c.     Overwrite your original security file with the new Security
code:
> All uppercase, no spaces or dashes.
>
> d.    Restart all Alltalk services on the new server.
>
> e.    Test the new server by logging onto the Client service using
> Telnet
>
> Ø      telnet mynewserver 21110
>
> Ø      user manager
>
> Ø      pass <password>
>
> Ø      USRL
>
> f.      This will recreate all of the EQK files and return a list
of the
> users.
>
> g.    Log out by typing quit
>
>
>
>
>
> 3.    Copy the management pages.
>
> a.    Reminder: The Web management pages do not have to reside on
the
> Alltalk Server – as the Web interface is just a client like any
> other Alltalk Client.  In most cases it is convenient to do so
though.
>
> b.    Copy the entire Alltalk folder from
c:\inetpub\wwwroot\alltalk to
> the new server.
>
> c.     Configure the website in IIS Management Console, as per the
other
> machine.  Don't forget that in Win2003 and later, the CGI
> (alltalksvrwi.exe) must be added to the Allowed Scripts and the
Folder
> permissions for the APPS folder must be set to Scripts and
Executables.
> You can also want to change the permissions for settings.inf in the
> _private folder to "All users"
>
> d.    Your Web server certificate can be exported from the original
> machine and reimported to the new server (see Microsoft web site for
> more assistance here).  For Alltalk Certificates, it may be simpler
to
> just regenerate a new one but either way is fine.
>
> e.    On the server console or terminal session add a host entry
> pointing to local host for the "real" hostname of the server (
> Eg alltalk.mydomain.com.au)
>
> Ø       notepad c:\windows\system32\drivers\etc\hosts
>
> Ø       127.0.0.1 localhost alltalk.mydomain.com.au
>
> f.      You should now be able to access the management webpage at
> http://alltalk.mydomain.com.au/alltalk/manage.htm
>
>
>
>
>
> 4.    Moving the Client messages.
>
>
>
> Thoroughly test the new server by setting up a few test clients
pointing
> directly at the new server (override the Remote host settings in the
> profiles).  Once you are happy that you have full functionality on
the
> new server, you can proceed with the final steps.
>
>
>
> The downtime when for the cut over will depend on how you are
> redirecting public access to the new server.
>
>
>
> When using mapped ports on a Firewall (recommended method), and just
> remapping the ports to the new server, it is possible to cut over
to the
> new server with practically no downtime.
>
>
>
> If you are redirecting the traffic by updating the DNS, downtime
will be
> longer depending on how long it takes to move the client messages.
> There is a possibility that the servers will get out of sync if some
> clients are accessing one machine and other are accessing the old
server
> (especially with regards to files being sent).
>
> It probably goes without saying that in either case, it is best to
do
> the change over at off peak times.
>
>
>
> Method for Mapped Port Configuration.
>
>     1. Shut down only the Messenger Service (SMTP Service) on the
> original Server.  This will prevent new messages arriving on this
server
> while cutting over.    2. Update the Mapped ports on the Firewall to
> point at the new server.  The clients will now be accessing the new
> server.    3. Now move all of the messages from the old server to
the
> new server using XCOPY
>
> Ø                Xcopy \\myoldserver\mailboxes\*.eml
> c:\alltalkclients\mailboxes /e /c > c:\alltalkcopy.txt
>
>     1. As files arrive on the new server, clients will immediately
have
> access to them.    2. The copy progress is logged into a file called
> c:\alltalkcopy.txt.  This file needs to be reviewed after
completion to
> track down any error messages.    3. After the copy if completed,
Stop
> the original Alltalk Server.  We just need to resync the logs files.
>     1. Copy the recent logs from the old machine to the new machine
> (c:\alltalkserver\logfiles)    2. For TODAYS log, we need to merge
the
> contents of the original machine and the new machine. There may be
an
> autoresync program available (see this forum or the Alltalk
> Documentation or files), but not at the time of writing this doc.
It is
> fairly simple process but a bit fiddly so be careful: we just need
to
> join the contents of the two log files from today re-sort by date-
time
> order.  You might have a text editor that can sort lines of text.
> Otherwise you might want to use Excel or some other spreadsheet to
do
> it.  You will need to stop the new server for a minute or two while
you
> merge the two logs.  You might use this method:
>
>
>
i.
> Stop the Alltalk Server on the new machine
>
>                                                            ii.
Open
> c:\alltalkserver\logfiles\<todayslog> in NOTEPAD or similar text
editor.
>
>                                                          iii.
Open
> the same log on the original server in the same way
>
>                                                          iv.
Cut and
> past the contents of the old log into the new log
>
>                                                             v.
Sort
> the new log in date-time order – perhaps paste into EXCEL and use
> dataàsort option or your text editor may be able to do it.
>
>                                                          vi.
Save
> the updated log.
>
>                                                        vii.
Restart
> the new server.
>
>     1. ALL DONE.
>
>
>
>
>
> Method for DNS Update.
>
>     1. At a quiet time (AH say).  Shut down the Alltalk Servers on
both
> the Original and new machines.    2. Update the DNS entry in the
> (public) DNS server.    3. Resync the logs files.
>
>
>     1. Copy the recent logs from the old machine to the new machine
> (c:\alltalkserver\logfiles)    2. For TODAYS log, we need to merge
the
> contents of the original machine and the new machine. There may be
an
> autoresync program available (see this forum or the Alltalk
> Documentation or files), but not at the time of writing this doc.
It is
> fairly simple process but a bit fiddly so be careful: we just need
to
> join the contents of the two log files from today re-sort by date-
time
> order.  You might have a text editor that can sort lines of text.
> Otherwise you might want to use Excel or some other spreadsheet to
do
> it.  I have used this method:
>
>
i.
> Open c:\alltalkserver\logfiles\<todayslog> in NOTEPAD or similar
text
> editor.
>
>                                                            ii.
Open
> the same log on the original server in the same way
>
>                                                          iii.
Cut
> and past the contents of the old log into the new log
>
>                                                          iv.
Sort
> the new log in date-time order – perhaps paste into EXCEL and use
> dataàsort option or your text editor may be able to do it.
>
>                                                             v.
Save
> the updated log.
>
>     1. Now move all of the messages from the old server to the new
server
> using XCOPY
>
> Ø                Xcopy \\myoldserver\mailboxes\*.eml
> c:\alltalkclients\mailboxes /e /c > c:\alltalkcopy.txt
>
>
>
>     1. The copy progress is logged into a file called
c:\alltalkcopy.txt.
> This file needs to be reviewed after completion to track down any
error
> messages.    2. After the Copy process is complete and the copy
errors
> (if any) have been sorted out, restart the new Alltalk server.
3. ALL
> DONE.
>
>
>
>
>
> --- In alltalk-avp@..., "zeronemisis0" <zeronemisis@>
> wrote:
> >
> > Hi I need complete instructions for setting up a new server and
> > migrating all mailboxes and setting across.
> >
> > Regards,
> > Damien
> >
>

Hi Glen

two questions I keep meaning to ask

1. I see there is a message viewer in the AllTalk folder - we have a
few clients who don't use any surgery software - they just want to be
able to see the results. Is there a way to use Alltalk itself to manage
results in this way (basically present a list of results, allow deletion
from the list) ?

This was a question posed some time ago.  Potentially yes, it does.  Alltalk Message viewer is actually the POPup message program (in the Options tab) and is able to:
a) present the contents of RTF and Text documents.
b) Display the content headers of HL7 and PIT messages
c) List and hyperlink (ie open to default editor) for any other kind of document

For PIT and HL7 messages, we had intended to offer the "Stand Alone" version of the HMViewer (Health message viewer) used in ATTrack for the clients to view messages of this type.  There was interest in extending the functionality of this viewer to allow for "Delete" or "Mark as Read" - ie move but not delete. So, it would work so that you could open the PIT or HL7 file into the HMViewer from the Results in AT Message Viewer and then manage the results (ie might be many in a PIT File) from there.

As not everyone will require such functionality, we were expecting to sell this viewer separately for some double figure amount.  There is some interest in doing this but at present we have put it on the back burner until the AVP and Allalk PKI updates are finished. 

Having said that, to add Delete "Mark as Read" functionality into Alltalk Message Viewer and allowing Hyperlinking to the HMViewer from the results view would probably do the job well enough for little effort.  I can probably include these changes in the updates for next week.

2. Is there any way to run alltalk as a service ? The number one cause
of problems for us is doctor's machines that are not logged in.

The simple answer is YES but with a big "HOWEVER"

For Service providers running Alltalk to do bulk transmissions then it is generally fine.  For docotors surgeries, it is generally very bad.

This has been a bone of contention for some years.  Our general opinion is that running Alltalk as a service will actually cause more headaches than it solves. 

The issues are these:

a) More often than not, the download folder is located on a network resource thus SysLocal user cannot be used and a specific user must be logged on to access the network resources.  This is a problem because

• Unless you have a dedicated "alltalk" network user for this purpose, the service is generally gets logged on as whoever happens to be in the surgery the day you install.  When that user either leaves, changes passwords or has permissions changed, the Alltalk client will stop working.  Further because its out of sight, its out of mind and the fact its not working may not be noticed for days.

b) out of sight is out of mind.  For support purposes, it is difficult for the everyday user to even find the computer with Alltalk on it let alone tell if its running, broken, turned off.

c) Often they dont have permission to stop the Alltalk Client service either if a restart is needed.

d) We many not like it much, but most practices run other downloading software which requires that the desktop is logged on, so if it often not warrented.

But instructions for running Alltalk as A Scheduled task instructions are available at http://www.lrsupport.com.au/downloads/alltalkdocs

cheers

Terry Chilvers
Information Systems
SJOG Pathology (WA)

From: Dr Brian Conway

Sent: Tue 16/01/2007 11:39 PM
To: Glen Kleidon
Subject: Re: Alltalk State of Play.

----- Original Message -----

From: Glen Kleidon

To: Dr Brian Conway

Sent: Tuesday, January 16, 2007 2:40 PM

Subject: Alltalk State of Play.

Dear Dr Conway,

 

I thought I would just follow up with you about Alltalk/Genie stuff.

 

Paul Carr has agreed to make the changes for the next version of Genie to support multiple profiles.  This will involved a few changes in the config also as Genie will write Alltalk Messages in the future into the "genie\Alltalk\" folder rather than the "EQuery" folder.

 

In the mean-time, I have also done some updates on Alltalk which will cope with this situation in the future (regardless of Genie changes).  I am still doing the testing at present but I am pretty sure I can get you an update next week. 

 

I am sure that the success of Alltalk at your practice will depend on getting the STVs client list as they are likely to have to most clients in your area although there are likely to be some clients in the Berwick area who have downloading from Dorevitch via the MQLink program.  Dorevitch may be persuaded to issue an Alltalk mailbox instead to these clients where there is a benefit, alternatively we can make a mailbox here for them since you already have an account on our server (RCH).   I have been trying to organise some time with Narre Warren Clinic on prospect Hill, but their IT support person seems to be a ghost-like figure…..

 

Anyway, thought I would just keep you in the picture.

 

 

Glen Kleidon

Last Resort Support

www.lrsupport.com.au

PH 03 9012 7394

 

 

Hi Glen

two questions I keep meaning to ask

1. I see there is a message viewer in the AllTalk folder - we have a
few clients who don't use any surgery software - they just want to be
able to see the results. Is there a way to use Alltalk itself to
manage
results in this way (basically present a list of results, allow
deletion
from the list) ?

2. Is there any way to run alltalk as a service ? The number one
cause
of problems for us is doctor's machines that are not logged in.

cheers

Terry Chilvers
Information Systems
SJOG Pathology (WA)

--- In alltalk-avp@..., "markrose03" <markrose03@...> wrote:
>
> SVHM has had issues with clients not being able to connect getting the
> above message. Other sites have had no issues, so this usually means
> that there is a firewall or other issue. After consultation with Glen,

Yes, Firewall issues are almost invariably the cause of this problem.  It is sometimes difficult to isolate which firewall is actually causing the blockage though as there are so many types and the users arent always aware that they are present (eg Desktop firewall, Windows firewall, Proxy/IAS, Firewall Servers, Hardware firewalls).

> the following command was a good test to see if it was indeed getting
> blocked:
>
> telnet <host> 21110

This is almost a difinitive test - there was a possibility that MS Telnet had in the past been added as an allowed application by the desktop or windows firewall in which case it might have worked, yet Alltalk may still have been blocked.

>
> The site in question was using Nortons, which indeed blocked the port.
> The site changed settings ... all ok now.
>
Incidentally, did you get them to allow 21025 as well?

The message is generated by Alltalk when the TCP Connect IP handshake is not complete within 10 seconds (ie Alltalk asks for a connection and has not received a reply of any kind within 10 seconds).

Other reasons for this message:

a) Routing Issues: Either local Lan or ISP has routing issues between segments of the network.  Eg Datafast had a problem a few years ago routing into Optus from Telstra networks - Packets destined for Telstra we being misrouted and disappearing.  The result was clients on Datafast in Bairnsdale (Vic) could not communicate Australis in Traralgon, yet other ISPs in Bairnsdale could.  The problem was eventually tracked down to a faulty router in Sydney..... Resolution - use

Tracert <Host>

(mostly blocked itself these days) to determine if and where there is a routing issue.  Report to ISP if necessary.

b) Slow link choked by virus or spam traffic (not so much these days).  During a few of the Worm outbreaks a few years back clients on dialup modems (via dial on demand routers) the link was choked with junk Traffic to such an extent real traffic was being delayed long enough to generate the error.

c) DNS fails to respond in timely fashion (rare).  In some cases, DNS requests may not be received in time to make the connetion before the message appears.  To check this use the

Telnet <ip address> 21110

if this works then there is a problem with the local DNS server.

d) Desktop firewalls "Forget" allowed programs.  eg Zone alarm would forget that a particular program like Alltalk or EQuery was allowed to access the internet and inappropriately block it - even when in the past it had worked for many weeks without a problem.

What it is NOT:

If the Alltalk server (application) is down or the actual Server machine is off, Alltalk will detect this as Server "unavailable" (ie gets TCP Connection refused, or TCP Host not found) and skip to the next profile. 

SVHM has had issues with clients not being able to connect getting the
above message. Other sites have had no issues, so this usually means
that there is a firewall or other issue. After consultation with Glen,
the following command was a good test to see if it was indeed getting
blocked:

telnet <host> 21110

The site in question was using Nortons, which indeed blocked the port.
The site changed settings ... all ok now.

It has come to our attention that Alltalk server in the standard
configuration will store duplicate copies of every tracking record
generated in the %systemroot%\System32 folder.

The problem (originally a feature!) was to assist in the change over
from EQuery to Alltalk.  For sites running concurrent copies of
EQuery and Alltalk where the EQ2 Sender (EAddressing) was the primary
transmitter, tracking records could not be generated because
the "sender" is considered a "foreign" client.  In EQ2 the
parameter 'summarydestination' (alternatively 'trackingdestination')
in the settings.inf file was the location for all tracking records to
be written. So for compatibility in this situation, Alltalk will
write copies of every tracking record generated by the system (for
all senders) into the designated folder.  The records are CSV files
containing the name of the file transmitted and the pickup time for
the file.

The problem is however, that if either optional parameter is NOT set,
the duplicate tracking records are written into the "start in"
folder. In the case of Windows services, for the SysLocal user, the
start in folder is %systemroot%\system32.

There are two resolutions:
a) If you decide to keep the extra tracking records (which may be
sensible in some situations), set the summarydestination parameter to
a sensible location.  Note: the tracking files are not managed by the
server after being written so you will need to manage these by some
other process.  You will need to move the csv files from the system32
folder.
b) An update will be available 2nd half of January 2007 (in testing
at time of writing) which will only write duplicates in the case
where either the summarydestination or trackingdestination parameters
are actually set.

The duplicate records can be most easily managed using the "del"
and/or Move command at the DOS prompt as there are likely to be too
many to manage using an explorer view.

Glen Kleidon.
Last Resort Support.

DRAFT NOTES: 10/01/2007

Moving your Alltalk Server to a new Machine.

These notes relate to moving the Server components only.  Remember that the Alltalk client you do most of your sending with may also be on the same machine!

There are 4 steps:

1. "Install" Alltalk server on the new machine
2. Re-license the New Server.
3. Move the Web management page.
4. Move the client mailboxes and resync the logs.

1.    "Install" Alltalk on the new machine.

a.    Copy the c:\alltalkserver folder in its entirety to the new machine.

b.    Using RUN or from the dos prompt execute:

C:\alltalkserver\alltalksvc.exe /install

c.     Re-initialise your client files by copying the ACI files from the original machine.  Assuming you want to move the server in exactly the same structure as the original machine execute (adjust to match your server names and pathways) :

Ø      Mkdir c:\alltalkclients

Ø      Mkdir c:\alltalkclients\mailboxes

Ø      Xcopy \\myoldserver\mailboxes\*.aci c:\alltalkclients\mailboxes /e

  (all on one line)

d.    Note: If you want to change the file structure, make sure this is adjusted in your settings (c:\alltalkserver\settings.txt) file.

2.    Re-license the Server.

a.    In the Windows Management console, start the Alltalk control service.  This will reinitialise your security file (c:\alltalkserver\_security.inf) showing the PC Code.

b.    Email the PC code to support@... (and the mailbox count from your settings file) and LRS will issue you with a new server code.

c.     Overwrite your original security file with the new Security code: All uppercase, no spaces or dashes.

d.    Restart all Alltalk services on the new server.

e.    Test the new server by logging onto the Client service using Telnet

Ø      telnet mynewserver 21110

Ø      user manager

Ø      pass <password>

Ø      USRL

f.      This will recreate all of the EQK files and return a list of the users.

g.    Log out by typing quit

3.    Copy the management pages. 

a.    Reminder: The Web management pages do not have to reside on the Alltalk Server – as the Web interface is just a client like any other Alltalk Client.  In most cases it is convenient to do so though.

b.    Copy the entire Alltalk folder from c:\inetpub\wwwroot\alltalk to the new server.

c.     Configure the website in IIS Management Console, as per the other machine.  Don't forget that in Win2003 and later, the CGI (alltalksvrwi.exe) must be added to the Allowed Scripts and the Folder permissions for the APPS folder must be set to Scripts and Executables.  You can also want to change the permissions for settings.inf in the _private folder to "All users"

d.    Your Web server certificate can be exported from the original machine and reimported to the new server (see Microsoft web site for more assistance here).  For Alltalk Certificates, it may be simpler to just regenerate a new one but either way is fine.

e.    On the server console or terminal session add a host entry pointing to local host for the "real" hostname of the server ( Eg alltalk.mydomain.com.au)

Ø       notepad c:\windows\system32\drivers\etc\hosts

Ø       127.0.0.1 localhost alltalk.mydomain.com.au

f.      You should now be able to access the management webpage at http://alltalk.mydomain.com.au/alltalk/manage.htm

4.    Moving the Client messages.

Thoroughly test the new server by setting up a few test clients pointing directly at the new server (override the Remote host settings in the profiles).  Once you are happy that you have full functionality on the new server, you can proceed with the final steps.

The downtime when for the cut over will depend on how you are redirecting public access to the new server.

When using mapped ports on a Firewall (recommended method), and just remapping the ports to the new server, it is possible to cut over to the new server with practically no downtime. 

If you are redirecting the traffic by updating the DNS, downtime will be longer depending on how long it takes to move the client messages.  There is a possibility that the servers will get out of sync if some clients are accessing one machine and other are accessing the old server (especially with regards to files being sent).

It probably goes without saying that in either case, it is best to do the change over at off peak times.

Method for Mapped Port Configuration.

1. Shut down only the Messenger Service (SMTP Service) on the original Server.  This will prevent new messages arriving on this server while cutting over.
2. Update the Mapped ports on the Firewall to point at the new server.  The clients will now be accessing the new server.
3. Now move all of the messages from the old server to the new server using XCOPY

Ø                Xcopy \\myoldserver\mailboxes\*.eml c:\alltalkclients\mailboxes /e /c > c:\alltalkcopy.txt

4. As files arrive on the new server, clients will immediately have access to them.
5. The copy progress is logged into a file called c:\alltalkcopy.txt.  This file needs to be reviewed after completion to track down any error messages.
6. After the copy if completed, Stop the original Alltalk Server.  We just need to resync the logs files. 
   1. Copy the recent logs from the old machine to the new machine (c:\alltalkserver\logfiles)
   2. For TODAYS log, we need to merge the contents of the original machine and the new machine. There may be an autoresync program available (see this forum or the Alltalk Documentation or files), but not at the time of writing this doc.  It is fairly simple process but a bit fiddly so be careful: we just need to join the contents of the two log files from today re-sort by date-time order.  You might have a text editor that can sort lines of text.  Otherwise you might want to use Excel or some other spreadsheet to do it.  You will need to stop the new server for a minute or two while you merge the two logs.  You might use this method:

                                                             i.      Stop the Alltalk Server on the new machine

                                                          ii.      Open c:\alltalkserver\logfiles\<todayslog> in NOTEPAD or similar text editor.

                                                        iii.      Open the same log on the original server in the same way

                                                        iv.      Cut and past the contents of the old log into the new log

                                                           v.      Sort the new log in date-time order – perhaps paste into EXCEL and use dataàsort option or your text editor may be able to do it.

                                                        vi.      Save the updated log.

                                                      vii.      Restart the new server.

7. ALL DONE.

Method for DNS Update.

1. At a quiet time (AH say).  Shut down the Alltalk Servers on both the Original and new machines.
2. Update the DNS entry in the (public) DNS server.
3. Resync the logs files. 

1. Copy the recent logs from the old machine to the new machine (c:\alltalkserver\logfiles)
2. For TODAYS log, we need to merge the contents of the original machine and the new machine. There may be an autoresync program available (see this forum or the Alltalk Documentation or files), but not at the time of writing this doc.  It is fairly simple process but a bit fiddly so be careful: we just need to join the contents of the two log files from today re-sort by date-time order.  You might have a text editor that can sort lines of text.  Otherwise you might want to use Excel or some other spreadsheet to do it.  I have used this method:

                                                             i.      Open c:\alltalkserver\logfiles\<todayslog> in NOTEPAD or similar text editor.

                                                          ii.      Open the same log on the original server in the same way

                                                        iii.      Cut and past the contents of the old log into the new log

                                                        iv.      Sort the new log in date-time order – perhaps paste into EXCEL and use dataàsort option or your text editor may be able to do it.

                                                           v.      Save the updated log.

4. Now move all of the messages from the old server to the new server using XCOPY

Ø                Xcopy \\myoldserver\mailboxes\*.eml c:\alltalkclients\mailboxes /e /c > c:\alltalkcopy.txt

5. The copy progress is logged into a file called c:\alltalkcopy.txt.  This file needs to be reviewed after completion to track down any error messages.
6. After the Copy process is complete and the copy errors (if any) have been sorted out, restart the new Alltalk server.
7. ALL DONE.

Hi I need complete instructions for setting up a new server and
migrating all mailboxes and setting across.

Regards,
Damien

This is a known problem with MD/AVP.

The problem is that when the progress notes are automatically inserted
by Medical Directors letter writer, they are inserted with the Arial
Font used in the progress notes editor instead of the font defined in
the template (which is Courier New).

This bug has been lodged with HCN for a fix in MD (Enquiry ID: 554973).

As mentioned elsewhere in this forum, the AVP print driver only
supports monospace fonts like Courier, FixedSys, Lucida Console,
SansMono and Terminal) and is easliy confused by mixed Fonts and
different sizes on the same line.

As per the AVP History notes
http://www.lrsupport.com.au/downloads/alltalkdocs/avp_patient_history.d
oc the resolution is:

After opening the template and selecting the recipient, highlight all
of the progress notes and change the font to Courier New.  Hopefully
HCN will fix this problem soon. Alternatively the new AVP printer
driver when released will fix this problem.

(draft notes at
http://www.lrsupport.com.au/downloads/alltalkdocs/avp_patient_history_d
raft.doc)

--- In alltalk-avp@..., "lrs_y_gk_07" <glenk@...> wrote:
>
> Submitted By: Unknown
>
> When I send a Medical Directory History (using the
AlltalkHistoryV1.5
> template), but the progress notes print a few letters for each word
on
> separate lines and it prints out on 2-3 pages instead of how it
> appears in MD.
>
> What causes this problem?
>

Submitted By: Unknown

When I send a Medical Directory History (using the AlltalkHistoryV1.5
template), but the progress notes print a few letters for each word on
separate lines and it prints out on 2-3 pages instead of how it
appears in MD.

What causes this problem?

Ah yes,

The AVP templates are at best "Basic" looking.

The reason is that the current windows Printer Driver used by AVP is
the "Generic Text Only" driver.  This driver only understands
monospace fonts.  If you use variable pitch fonts (like Arial/verdana
etc), the text becomes garbled and is unusable.  (See the notes in
this forum regarding MD History letters).

Future releases of AVP will use a more advanced PS2 driver which will
make the templates more pleasing to the eye - and like give some
degree of enhancements (bold underline etc).

HOWEVER - you have misunderstood one of the steps in the process.  AVP
will use the Letterhead documents you define using the Letterhead
facility.  Click on Edit-->Letterheads. This will load the template
editor.  You can customise and create letterheads as much as you like
so long as you maintain the fields.  This is the document that is
printed.  There is no need to type the letter twice.

In MD template editory, you can change the "Letter Head:" setting to
use one of your customised Letterheads or change your default
letterhead.

Glen.


--- In alltalk-avp@..., "lrs_y_gk_07" <glenk@...> wrote:
>
> Submitted By: Unknown
>
> Dear LRS,
>
> I have just installed the AVP templates in medical Director - They
look
> AWFUL!!!
>
> I dont think I want to print these out to give to the paitent and I
> dont want to have to type it in twice.
>
> Something really needs to be done.....
>

Submitted By: Unknown

Dear LRS,

I have just installed the AVP templates in medical Director - They look
AWFUL!!!

I dont think I want to print these out to give to the paitent and I
dont want to have to type it in twice.

Something really needs to be done.....

This file is your Proof of Signature and is equivalent to the paper
copy used for Medicare Claiming purposes.  This is the document you
need to give to Medicare should you ever be audited.

I have asked for clarification from Medicare about this matter, but in
my opinion the legal copy is the sign.eml, not the electronic record in
your practice software.  I'll post the response from Medicare when I
get it.

I would expect that it would be extremely rare that Medicare would
demand to see the file, given that APV includes the Serial Number and
common Name of the signing certificate inside the Referral Letter, but
technically speaking only the sign.eml file contains the digitial
signature.  This requirement is not specific to Alltalk of course: the
same applies to other methods of electronic referral by Secure email
(Outlook mailboxes, Argus Interbase database).

You MUST keep these files for at least the time required by Medicare.
As part of your AVP install plan, alway ensure that your practice
backup procedures includes your Alltalk "Non Health Message" folder.
Note, backing up a single folder is far simpler than backing up the
Interbase Database or MS Outlooks mailbox folders (especially if you
dont have control over the Mail server which might have old messages
purged after x months).

Glen.

--- In alltalk-avp@..., "lrs_y_gk_07" <glenk@...> wrote:
>
> Submitted By: Unknown.
>
> Whenever I get a signed PIT or HL7 message from one of my referrers,
a
> file with the same name (but with sign.eml) appeneded appears in my
> Messages ("other") folder.
>
> When I open the file up (in eg MS outlook Express), I can see it is a
> digitially signed email containing the referral I already have in my
MD
> Holding folder.
>
> What am I supposed to do with this other file?
>

Submitted By: Unknown.

Whenever I get a signed PIT or HL7 message from one of my referrers, a
file with the same name (but with sign.eml) appeneded appears in my
Messages ("other") folder.

When I open the file up (in eg MS outlook Express), I can see it is a
digitially signed email containing the referral I already have in my MD
Holding folder.

What am I supposed to do with this other file?

The Alltalk AVP FAQ has a good discussion of this:
http://www.lrsupport.com.au/avp_faq.htm

Why not just use secure Email?
The main reason are these:

+Secure email is in the wrong format for Health Messages. Recipients
will need to apply the message manually to the patients record.
+You generally need to install certificates for all of your
recipients in a third party application or address book. [GK IE
outlook AND Practice software]
+It is often easy to "forget to" Secure or Sign your email!
+There is no guarantee of delivery and no way to automatically apply
any acknowlegements to the patients record.
+There has been very poor update of PKI because existing solutions
are generally cumbersome and difficult to manage and maintain.

AVP overcomes these problems by:
+Letters and referrals are converted into Health messages understood
by your practice software and can be automatically applied to the
patients record (even creating the record for you).
+Alltalk will automatically aquire PKI certificates for the
recipients where present. In other cases the messages are delivered
via existing encryption technologies without compromising digital
signature.
+Only one address book entry is required - the one in your practice
software. When a recipient changes encryption certificates, Alltalk
will automatically re-aquire the new one.
+More than 1600 practices are able to accept your messages TODAY with
no changes at their end.
+You cant just "forget" to secure or sign the document. AVP documents
are always secure and using AVP templates, Referrals are
always "signed" by default.
+To ensure the recipient knows that they arent required to keep the
paper copy, AVP includes Signing Certficiate information inside the
electronic message. For those patients who feel more comfortable with
a paper copy, AVP prints a reminder at the bottom of the page that a
digitally signed electronic message has been generated.


--- In alltalk-avp@..., "lrs_y_gk_07" <glenk@...>
wrote:
>
> Submitted by: Unknown
>
> Why do people feel it necessary to have different applications on
their
> desktop to do send Secure (PKI) messages when Microsoft Outlook
already
> does it.
>
> All these different packages that people are trying to peddle seem
like
> a waste of time and money especially when it seems to me that
everyone
> already has it for free on their desktop.
>

Sorry, the link was not correctly displayed:

Try this.

http://www.lrsupport.com.au/alltalkdocs/Bulk_file_Transfer.pdf


--- In alltalk-avp@..., "lrs_y_gk_07" <glenk@...>
wrote:
>
> The bulk File transport Utility is the PREFERRED method for moving
> files from network locations into the Alltalk outbound folders.
>
> Alltalk provides a bulk file transport service allowing the client
to
> automatically pick up files from different folders or network
> locations, automatically address and transmit them to their
intended
> Alltalk recipient mailbox.
>
> The Bulk Transfer utility provides methods for identifying the
> recipient by file and/or folder name or by the use of header text
> within the file.  You can apply rules from the level of folders
down
> to individual files within a folder.
>
> It also provides a method for Requiring an Acknowledgement from the
> recipient.  For Pit Files, BFT adds '-- ACK --' onto any of the
> spacer lines 009, 019 or 029.  When Alltalk downloads a PIT file
with
> the "-- ACK --" trigger, Alltalk will automatically create an
> Acknowledgement (by reversing the Sender and Recipient data on PIT
> lines 121 and 123) and inserts the wording:
>   "This indicates that the following message has been delivered
>   to <recipient address> but does not confirm it has been read
>   or understood."
> into the result content.  It then puts the acknowlegment into the
> outbound folder.  Note: this assumes Single Result PIT files at
> present and should not be used on mulitple result PIT files.
> There is no method for Auto Acknowledge HL7 messages at present due
> to the increased complexity of the messages (what version of HL7,
> what message type, is it encapsulated PIT, TX or HT records, what
hl7
> field is the sender which of the 20 methods identifies the actual
> recipient doctor??? etc etc).  At least some level of hl7
> acknowlegement will be available in Alltalk 1.2.1.0.
>
> For a detailed discussion of the Bulk File Transport Editor go
> to "http://www.lrsupport.com.au/alltalkdocs/Bulk file Transfer.pdf"
>
>
>
>
>
>
>
>
> --- In alltalk-avp@..., "lrs_y_gk_07" <glenk@>
> wrote:
> >
> > Submitted by: Unknown
> >
> > In the Alltalk tools Menu there is 2 references to the "Bulk File
> > Transport" utility.
> >
> > What is this for and how do I use it?
> >
>

Submitted by: Unknown

Why do people feel it necessary to have different applications on their
desktop to do send Secure (PKI) messages when Microsoft Outlook already
does it.

All these different packages that people are trying to peddle seem like
a waste of time and money especially when it seems to me that everyone
already has it for free on their desktop.