Create a Vet List

before you can process your vet list in pulse or the mobile app, you must first build it in pulse, or set it up in with the \k switch (which sends the list to pulse) important configuring s requires advanced veterinary knowledge as well as the guidance of animal health experts the steps outlined below assume that you are working with an expert pulse/dairycomp user and your vet expand the sections below to learn more create a vet list in pulse you can generate s in pulse from multiple locations dairy reports/worklists docid\ unglsr18amy6xyamsfdnh use this tab to generate reports or worklists saved from the gallery template gallery docid 2ph37i7mwsj79bzcm4wca use the gallery to check out available report and worklist options report/worklist builder docid\ i7vcqxla9mwqwnm o exz this tool allows you to build custom reports and worklists using an easy drag & drop interface see build a vet list docid\ qqserhwpvobzyhzmlvma3 for step by step instructions for building a custom vet list create vet lists in dairycomp step 1 define vet list options in dairycomp use the \5 command to define options, such as vet codes ( ) and vet check ( ) reasons the order of the items is important, as the vetlist command flags the first vetcode encountered as the reason for the vet check for instance, if an animal has multiple vet codes in its record, including vc 3 ( ) and vc 6 ( ), the will use vc 3 as the reason for the check step 2 save vetlist command(s) in dairycomp (recommended) save your common vetlist commands for easy reuse in dairycomp using the alter\3 command for example, you can save vetlist vitems for vc>0 hldat< by as "vlist" step 3 run vetlist command(s) in dairycomp the vetlist command resets the veterinary codes by first looking at the animal's record and checking if a veterinary code exists if there is no veterinary code present, dairycomp examines the items in the animal's record to see if they meet any of the conditions in the veterinary code table (such as days in milk and or fresh), or in the command (such as pen=2 4) prior to being able to send your to pulse , you must run your vetlist command(s) if you saved your vetlist command as an abbreviation, such as "vlist", use the abbreviation to quickly run the command step 4 create pulse vet list in dairycomp for customers who are familiar with the vas product, you may already know how to create and send a vet list to handhelds the command is similar when creating a vet list to send to pulse set up the command as shown in the example below start with the server command to define what you want the vet list to do use the \v switch to identify the list as a vet list (in the mobile app) use the \k switch to tell dairycomp 305 to send the list to pulse important the way to define which items display in a hospital list differs between and platform items are defined in dairycomp using the entry tab in server configuration ( server\3 ) platform items are included in the hospital list command in one of two ways directly in the command for example server id identifier pen dim days in milk rpro reproductive code dcc days carrying calf/pregnant for pen=99 \hk as a separate command for example server hpitems for pen=99 \hk where the hpitems command is defined as id pen dim rpro dcc step 5 send your vet lists to pulse important be aware that if dairycomp 305 sends multiple versions of the same list to pulse in one day, the most recent list overwrites the earlier ones but does not affect any progress or changes made against the list unlike the product, which requests each worklist during a refresh, pulse does not request worklists from on‑premise dairycomp instead, dairycomp must manually send worklists to pulse this ensures that on‑premise users control the lists that are sent out to pulse mobile app you can send platform worklists from dairycomp manually or schedule dairycomp to send them automatically follow the instructions below to proceed send lists manually follow these steps to send worklists from dairycomp to pulse manually go to the dairycomp command line type platform\k and press enter this command instructs dairycomp to find all platform enabled (\k) server commands and generate the corresponding worklist files the worklist files are then sent to pulse the next time it synchronizes data from dairycomp schedule dairycomp to send lists if you prefer not to do a manual send each time you want to update your pulse lists, you can set up a dairycomp scheduled task that automatically executes the platform\k command at a convenient daily or weekly interval please contact vas support http //platform docs vas com/default htm#cshid=1004 if you need help scheduling this type of task in dairycomp