HL7
Submitted by EastsideVetEmerg on Wed, 16/11/2016 - 15:25
Hi,
Is it possible for two instances of OVPMS on the same network to send IDEXX HL7 requests to the same version of LabLink/eLab without causing chaos.
Idea is that both would send requests to Lablink. Files all get dumped in the same folder. Docload jobs from both instances would then restive the lab results from that folder.
Thanks,
Adrian
Re: HL7
In my test version of LabLink (1.2.25), only a single OpenVPMS instance is supported, so I suspect the answer is no.
But even if it did, it only supports outputting files to a single directory. There isn't a reliable way to distinguish which files belong to which OpenVPMS instance, unless you've set the identifiers so that they won't ever clash. E.g. what if both OpenVPMS A and OpenVPMS B submit an investigation with Id 1001?
Re: HL7
ok - thanks - no worries.
Our identifiers are miles apart so I don't believe this should be an issue. However obviously if only a single instance is supported then it is a no go.
Cheers,
Adrian
Re: HL7
If your identifiers have overlapped at any time, there is still a small chance for investigations to be loaded into the wrong site.
E.g. you may have a investigation with id 10001 at site A, created 12 months ago.
If site B subsequently creates an investigation with id 10001, it could still be loaded at site A, as there are no date checks performed when loading documents.
A potential solution to this would be to insert middleware (e.g Mirth Connect) between the OpenVPMS instances and LabLink to prefix identifiers with an OpenVPMS instance id, to ensure identifiers are unique.
You could then configure the Document Loader Job to only load those files with the relevant prefix. Alternatively, the middleware could move the files to an OpenVPMS instance specific directory.
Of course, it would be simpler if LabLink supported multiple PMS.
Re: HL7
ok - no worries. We will have a discussion about how best to manage this.
Cheers,
Adrian
Re: HL7
2 copies of lablink running on different machines - connecting to different Vetconnect accounts
1 vetlab station might be the issue tho