BD Pyxis API Job

The BD Pyxis job connects VetView to Pyxis supported CDMs. This job works in tandem with the internal VetView CDM settings to catch and process prescription requests and patient profiles sent to the machine, and to bill patients appropriately.

Job Settings

The standard job settings are used for the Pyxis interface. The Active Flag indicates that this job is available to start. Auto Start ensures it will begin running when the server is rebooted.

VetView strongly recommends that API jobs run on a dedicated server, to avoid impacting any users on production servers.

The job can be set to run as often as once a minute, or fewer times if you have a slower system that takes longer to process requests.

Port Settings

The CDM should have a dedicated IP address on your network so that VetView can communicate with it. The machine as well as your VetView server should have the appropriate ports open to listen for communications.

Additional Settings

These settings determine the format of the HL7 message that VetView will sent to the CDM. Contact BD Pyxis if you are unsure of what the assigned receiving facility and application should be.

Pyxis machines also give you the option of including a Faculty member in the send/receive message, and sorting by client's last name or patient name on the list.

Billing Options

The CDM can apply billing charges directly. These settings allow you to determine how and where these charges are applied. Bill on Any Open Order will apply the charges to the most recent open order, even if it's not associated with an open episode. Receiving Units show the available units in the system to which you may credit the revenue on the line item of the order.

Control Drug Machine Log

You can filter by Patient ID or Dates on the log.

Any HL7 messages will appear in the Charge Message Log.

Open Orders are automatically sent to the CDM, and the communications will appear in the Order Status Message Log.

VetView Wiki

Most recent releases of VetView: Version 5.0.4 (Released 3/10/2025) and 4.2.10 Hotfix (2/28/2025)

Contents

Browser not supported