|
|
|
| You are here: start » integration » houston_vip |
|
|
Houston VIP is a computerised medical patient records software that runs your medical office efficiently and with ease. The electronic medical billing system can expand as your practice grows, or help your existing practice to run more efficiently, thereby meeting and surpassing your needs.
Using the existing ARGUS interface within VIP requires the agent to both;
The ARGUS interface of VIP produces proprietary HL7 messages that other receiving clinical applications may have interoperability issues with, to resolve this incompatibility issue, the agent needs to be configured to re-envelope the message prior to routing it through the ReferralNet network.
The screen shot below displays how the agent needs to be configured to ensure compatibility with the receiving clinical applications. The directory path should match the directory path specified in the Configure Argus Interface section.
* If you are using ReferralNet Agent version 3.3.0 and above, use the Archiving Feature.
In order to get the incoming HL7 correspondence into VIP, the agent needs to apply a transformation prior to saving the message to the nominated incoming folder. This transformation modifies the HL7 enveloping only, not the contents of the encapsulated letter (this is never touched), to satisfy the proprietary requirements of the ARGUS interface.
A preset already exists for this, so simply choose the preset from the drop down and browse to the previously configured incoming folder location specified in the Configure Argus Interface section.
* Don't forget to add and configure the additional action by following the agent backup scheme.
* If you are using ReferralNet Agent version 3.3.0 and above, use the Archiving Feature instead.
Houston VIP supports two explicit HL7 message vendor interfaces, CNS and Argus, with no support for ReferralNet. The ReferralNet agent can however, utilise the existing ARGUS interface to get around this support limitation. If ARGUS is also being used by the site in addition to ReferralNet, then this workaround will not be feasible.




