External Request Interface

The generic External Request Interfaces communicates to any external interface via email, based on Request Unit settings.  Use this for specific external interfaces in addition to RIS/PACS or other specific interfaces when multiples are required. 

Job Settings

The standard job settings include the Active Flag to indicate that the service is turned on and available to start, the Auto Start flag to have it run as specified once the server starts, and the Server to Run on.  Like all API jobs, VetView strongly recommends you have a dedicated server for API jobs, to avoid impacting any users on production servers.

Additional Settings

You can give your Job Interface a custom name.  Once you have saved, this name will appear on the main Job Interface screen and at the top of the interface settings screen.

The Token Key is used to perform a handshake with the external interface if it accepts a token as part of its security protocols.

The New Request Email field is where any new requests should be sent as  duplicate email. 

Logs

The logs for this job allow you to filter by patient ID and also by date range.

Request Event Queue

This is the list of the requests that are currently queued in the system.  If the system is correctly processing the events, the queue should remain up to date and in sync with VetView.

Outbound Message Log

This section displays the summary of each outbound HL7 message.  Click on a row to view the HL7 code as it was sent.  The letter on the right indicates Success or Failure.

Incoming Message Log

This section contains a summary of any HL7 messages that are sent from the interface without being associated with a Request.

Message Details

This section contains the HL7 code as it was transmitted between VetView and your external RIS/PACS system.

API Documentation

If you want to build your own external interface with VetView for your applications, you can use the VetView API documentation:  Version 2.1 and Greater API Web Services Documentation