Chapter 24 - BoardingTable of ContentsChapter 26 - Desktop


VPF is a separate Software package that may be integrated with V/BOSS to enhance some basic V/BOSS features. For information 
on the basic features which VPF options relate to, see the chapters noted.
      A. Take Home Instructions
        B. Instruction Files
                1. |*PATIENT*|
                2. Breed Instructions
                3. Pharmacy Instructions
                4. Link/Copy Instructions
        C. Patient Medical Records
        F. Check-In Notes/Report
        G. POS Billing
                1. Procedure Lookup
                2. Species Specific Billing Screens
                3. Cascading Windows
                4. Billing Defer Cycle Mode
        H. Recalls
                1. Patient Screen Defaults
                2. Rules
                3. Bracketed Recalls
                4. Upper/Lower Case Parsing
                5. FINAL Recalls 

A. Take Home Instructions

Screen #1

With this option you may give clients individualized instructions for them to take home with their pets. There are several ways to access this function:

  1. From the patient screen press <FlO> then <F9> for Take Home Instructions. The above screen will display. After entering the instructions, press <F9> to save them. NOTE: This does NOT enter the patient into the WIP system, it just saves the instruction to be printed at the conclusion of a POS billing.
  2. After creating a WIP for a patient you may access take home instructions from the WIP listing screen. Highlight the correct patient using the up and down arrows. Then press <F7> for Take Home Instructions. Enter the instructions and make sure to press <F9> to save them. In order to access take home instructions by the following methods, the abbreviation Wins must exist and have a [Y] as the abbreviation text. See ABBREVIATIONS for information on adding abbreviations.
  3. As discussed in the PHARMACY chapter, an Invoicing Interface will display when creating a pharmacy label (if the abbrev. Plab is set up properly). If you book a procedure in this window and press <F9> to save Wip, you will be asked if you wish to update the patient's take home instructions. If you do, answer [Y], otherwise press [N].
  4. From billing, if you press <F9> to Save WIP you will be asked if you wish to update the patient's take home instructions. Also, if you defer the billing to be saved in WIP you will be given this opportunity. Answer [Y] to do so or else [N].
  5. When you check a Patient into Boarding the Patient1s bill is updated and saved in Work In Progress. As above, the system will ask if you would like to update the Patient's take home instructions. Answer [Y] or [N].

If an instruction file already exists that you would like to use for a Take Home Instruction, you may type (+XxXXXXXx] replacing the X's with the instruction file name. This may be typed on any line of the Take Home Instructions, BUT MUST be alone on the line and start in the first position of whatever line it is on. Do not put a space between the + and the name of the file. After typing the filename, press <Enter>. The instruction will then be imported.

Instruction Files that are to be used in this way should have the word [END] at the beginning of the first blank line after the last written line of the instruction. The Link and Copy functions discussed in the next section are supported with the function.

The insertions that take place when the |*COMMAND*| function is used (referred to on the following page) work in Take Home Instructions also.

If you want these instructions to be transferred to and stored in the Patient's Medical Records, the abbreviation .Wicp must exist and have a [Y] as the abbreviation text. See ABBREVIATIONS for information on adding abbreviations.

If your Take Home Instructions are being stored in the Medical Records, you may wish to use the special comment feature. With this feature you may write comments in the take home instructions that WILL NOT print on the receipt with the rest of the instruction. To use this feature simply type [/*] immediately BEFORE any comments that you do not want printed (remember, do NOT type brackets!). These symbols may be at the beginning of a line or anywhere in the middle of a line, but KEEP IN MIND that each line that should not be printed MUST contain these symbols. Printing will stop at the [/*] and resume at the next line unless there is another [/*]. You may wish to experiment with this until you are familiar with how it works. When these comments are stored in the Medical Records they will be displayed in yellow on color monitors if you are using the abbreviation .Cmpx (see ABBREVIATIONS).

B. Instruction Files

1. |*COMMAND*|

As discussed in the INSTRUCTIONS and PROCEDURES chapters, you may attach instruction files to procedures to be printed whenever the procedure is booked in Billing. With VPF you may cause certain information to be inserted into any instruction when they are printed on receipts. Please see INSTRUCTIONS, Section N. for further information.

2. Breed Instructions

Instructions may be created that will automatically print on receipts for all Patients of the breed(s) specified. At the time the receipt is printed, V/BOSS will look in the instruction file for a match on the first eight characters of the breed. For example, an instruction named "DSH" would print for this breed of cat, or an instruction called "GREAT DA" would print for all Great Danes. However, if the instruction were named "GREATDN" it would not print unless that's how the breed was entered on the Patient screen.

3. Pharmacy Instructions

You may create instructions that are to be printed on Pharmacy Labels. When adding or modifying an instruction press <F3> to display the number and length of the lines on your pharmacy labels.

This feature and the "USE XXXXXXXX" feature are described in more detail in PHARMACY.

4. Link/Copy Instruction Files

Instruction Files may be as long as fifteen lines. If you need to make a longer instruction, you may create multiple instructions and "hook" them together, using the link or copy options. The link function allows you to "hook" two instructions together. The copy function allows you to "hook" together as many instructions as you specify. The first or lead instruction MUST be attached to a procedure.

To use: First add into the instruction files all the instructions to be "hooked" together (see INSTRUCTIONS for help in adding). On the lead instruction leave one blank line at the end if you are only "hooking" two together. If you are "hooking" more than two to each other, leave that number of blank lines at the end of the lead instruction. These blank lines will be used to type in the link or copy commands.

To link two instructions: On the last line of the lead instruction type LINK xxxxxxxx. Replace the x's with the file name of the second instruction. For example, you might have one instruction file named SPAY and a second named SPAY2. To link them together (so they will print together on the client's receipt), on the last line of SPAY type LINK SPAY2. See the example below.

These are the last six lines of the instruction SPAY.


The above would cause SPAY2 to be printed on the receipt directly below the file SPAY. The word [END] should be typed on the first blank line after the last line of text in SPAY2 (or the final instruction of any linked/copied instruction set).

If you would like to "hook" three instruction files together, you should use the copy function. We will use SPAYl, SPAY2 and SPAY3 for examples. On the next to the last blank line of the first instruction (SPAYl) you would type [COPY SPAY2) on the last line you would type [COPY SPAY3]


C. Templates

You may create templates in the Client Information System of the V/BOSS master record (00000). These templates may be inserted into patients' records without having to re-key everything for each patient.


Screen #2

1. To create the templates, go to the client search screen (<F5>) and enter [00000]<Enter>. You will now be in the V/BOSS master record. Press <FlO> for Info.

Each individual template must be given a name. The name MUST be on the first line of the page and MUST include [~###] and a word or words to identify the template, for example [URINALYSIS]. You MUST replace the #'5 with a 3-digit number that matches the page number that you are on. For instance, if you are entering the template on page 001 of the information system the template must be named 001. The name must be on the first line of the template and start in the first position of that line. The exception to this is when you have a template that needs more than eight lines, so you must continue on another page or pages. In that case you must still enter [~###] on the first line and positions of the additional page(s) but you will use the number that corresponds to the first page of the template in question. The next template after a "spanned" template should contain the number that matches the page number that it starts on.

Screen #3

Use the following bracket types to insert the information you wish to track:

{ } will insert numerical information.

[ ] will insert alpha or numeric information.

(DD/DD/DD] will insert current date when this field is bypassed.

[] used with no spaces in between them will insert a blank line.

These brackets must be used when you create your templates. However, if you would like different deliminators to appear in the Patient records you may create the abbreviation .cl[] (see ABBREVIATIONS.)

2. To use in a patient record, find the patient and press <FlO> for other, then <FlO> again for Med.Rec. Type the number (name) for the template that you wish to have inserted into this record (e.g. 001, etc.). Fill in as necessary. You may only fill in the areas enclosed by brackets.

If you are on a blank page of a Patient's Medical Records, you may hold down <Ctrl> and press [T] to lookup the available templates. Use the <Up> or <Down> arrows to scroll through the templates. If you wish to insert one, press <Enter> while viewing it. <Fl> exits from template lookup without selecting one.

D. Line Wrap

When making comments or notations within the Client or Patient information Systems, the lines that you type will "wrap". That is, you may continue to type without pressing <Enter> at the end of a line and the system will put the last word on the line where it will fit instead of just cutting it off, similar to a word processor. Within the Medical Records, line wrap also goes from page to page and is fully implemented when using abbreviations. This feature also exists in the Instruction files and Take Home Instructions. Closing quotation marks, and ? are understood.

Instead of this:

It was noted during examination that the patient had several sm
all welts.

The system will write like this:

It was noted during examination that the patient had several
small welts.

E. Patient Medical Records

Some Medical Records features require VPF. These features are discussed in detail in Chapter 8.

If you use the Medical Records extensively, much higher performance may be achieved in processing the Medical Records (especially for slower terminals and remote stations) by setting the terminals' Memory Occupation to 3 in the ID Records (see ID RECORD).

Medical Records include a separate Major Problem Listing. Viewing of the Major Problem List is available from the Patient's Recall screen, Clinical Records screen, Work in Progress and Medical Records. From Medical Records ONLY, you may press <F4> to modify (or enter) Major Problems. |*PATIENT*| is supported in the Medical Records.

Screen #4

F. Check-In Notes/Report

Check-in notes or instructions are for you to enter pertinent information concerning the reason for a Patient's visit. You may then choose to print an individual Patient Check-in report or a Check-in report which will include all Patient's with an appointment on the date you specify.

Check-in notes may be entered for a Patient in three places.

1) When an appointment is made you may press <F2> when at the comment field to enter Check-in notes. 2) From the Work In Progress screen highlight the Patient, press <F7> and [I]. 3) From the Patient Screen press <FlO> Other then <F2> Check In. Be sure to save your notes when finished by pressing <F9>.

To print a Check-in report for an individual Patient, go to that Patient record, press <F2> Print Profile and [2] Check-in Report. To print Check-in Reports for all Patient's with appointments on a particular day, from the Main menu select [A] Appointments. Press <F2> Print Schedule then [2] Daily Check-in Report. You may then choose to print the report for appointments with one doctor or all.

The Check-In report includes the Patient profile, Major problems, the last 3 pages of the Medical Records and pertinent Clinical Records. If you would like ALL Medical Records printed on the report, add the abbreviation .Mall with text of [Y] (see ABBREVIATIONS). The Check-In notes are deleted when a POS Billing transaction is completed.

G. POS Billing

If enough free memory is available, you may access Inventory from POS Billing by holding down <Ctrl> and pressing [V].

1. Procedure Lookup

Vpf allows you to narrow down a Procedure Code search to a particular category if desired. This function is available in all places that Procedure lookup is allowed. When the Procedure Lookup window is displayed, press <F3> to enter the desired category before entering a starting letter.

Screen #5

You may cause the Category window to automatically display when the Lookup window is accessed. To do so you must add the abbreviation .Vppw to your system (see ABBREVIATIONS). The text of this abbreviation determines the default search mode.


1 = by Procedure Code (this is the default if .Vppw does not exist)

2 = by Procedure Name

3 = Category first, then by Procedure Code

4 = Category first, then by Procedure Name

When using the Procedure Lookup Window, nested Procedures will be flagged with a blinking [n]. If you need to view the nested items, highlight the nested Procedure, then hold down <Ctrl> and press [N].

2. Species Specific Billing Screens

If you wish, you may cause different Procedures to display on the Billing Screens depending on the Patient species. You assign Procedures to display on the Billing screens through Procedure Maintenance. The field "PROC TABLE P0S" determines if a Procedure displays, where it displays, and which species it displays for. The number is the Table Position (place on the Billing screen) and immediately following that is the species indicator. Species indicator choices are K, F, E, A, B, P, G, S, 0, and *. The * denotes a default entry. That is, if the Procedure should display for ALL species you would put [*] beside the table position number.

The best way to design your Billing screens is to make copies of the pages that follow which show the Billing screens. Label each one for a different species. Using your Procedure List, fill in the codes of Procedures that you wish to be displayed. It is possible to fill in every table position (although we recommend leaving the lines under Dispensing blank). If, during a transaction, you need to type in a code that does not display, move the cursor to a Procedure that you will not use during this transaction. Hold down <Ctrl> and press [B]. This will cause the line to be blank (only for this transaction) so you may type in a Procedure Code of your choice. Keep in mind that you may also create cascading windows (See the next section).

Screen #6

Screen #7

Screen #8

3. Cascading Windows

Below is an example of what a cascading Window is:

Screen #9

cascading windows can be very useful for groups of similar Procedures such as series of vaccinations, surgeries such as Spays/Neuters, Heartworm tests, etc. If a cascading window has been created, as in the above example, when you choose the top level Procedure, e.g., RABIES VACCS., the cascade displays so that you may choose the specific Procedure for the Patient. You may also choose to have one cascading window lead into another one, and so forth, up to four windows deep.

To create a cascading window you will use the Nesting Table Maintenance. Do not confuse this with the type of nesting that shows a breakdown on the receipt of what a Procedure included. Although the process of creating the Cascades is essentially the same, it performs a different function. You must first add all the Procedures that will be in the Cascading window. Then you must add a Top level procedure. This will be the one that causes the cascade to display. The Top level procedure code MUST contain AT LEAST ONE [*] and be six characters long. For example, [RABIE*]. The [*] is what distinguishes a Nesting table that is for cascading from a Nesting table for receipt purposes. If the cascade is to be a displayed Procedure (rather than typed at a blank line) the Top level Procedure should have a table position and species indicator, NOT any of the Procedures that will be nested (and cascaded). Pictured below and on the next page is how to create the Top Level Procedure and how to create the cascade Nesting Table.

Screen #10

Screen #11

Keep in mind:

  1. All Procedures involved in a cascade MUST exist in the Procedure File BEFORE nesting can be done.
  2. The Top Level Procedure Code MUST have at least one [*] at the end of it. The Top Level Procedure code MUST be 6 characters. This Procedure does not need to have a price.
  3. The only Procedure involved in the cascade that should have a table position is the TOP Level.
  4. If the Top level code is in a table position, it must also have a species indicator.

To cause one cascade to lead to another, the Top level Procedure code must have more that one [*] at the end. You will nest another Procedure that contains at least one [*]. For example:

Top Level Procedure: FOOD**

Nested: DOGFD*


You would then nest specific foods under DOGFD* and CATFD*. The result at Billing would be as follow:

Screen #12

When creating nests within nests, the very Top level Procedure Code MUST have the greatest number of [*]'s. Each subsequent Top level code should have one less [*].

4. Billing Defer Cycle Mode

This option from the Utilities Menu allows you to bill out all Deferred patients at one time. The transactions will be completed as not paid. Receipts will be printed. When the Clients come in to pay you will need to Post the Payments through Receivables. This can be useful at times of year when there is heavy Boarding. Not for general use.

H: Recalls

1. Patient Screen Defaults

Shown below are the default fields available for update by the system on the Patient Screen.

Screen #13

V/BOSS comes set up to update these fields with the dates that corresponding Procedures (with Rules set-up) are performed. You may add other fields to these defaults. Up to fifteen fields are available for update. Fields 16 and 46 are for Procedures that must have Rules established to clear recalls and perform other functions (such as print certificates) but are not to update the Patient Screen with a date.

As an example, we will add the combination Feline Leukemia/FIV test as a Patient screen default.

Things to keep in mind:

  1. You may not have a blank field in between used fields. For example, the FELFIV test must be put in field 38 above, it cannot be in field 39 or below.
  2. Any defaults that should appear on both the Canine and Feline screens, must be across from each other on this table as in the case of RABIE* and STOOL*.
  3. If you add defaults here, you must also enter Procedures and Rules that explain to the system what Procedures update and clear the field in question.

To add the FELFIV test, use the arrow keys to highlight field 38. The cursor will be in an area to the left of the table. Type [FELFIV] at the cursor position. It will be entered into field 38. Press <F2> to update. Add the Procedure(s) which will be used when you administer this test and which should update field 38. Also add a corresponding Rule (see below). It is best to keep the Procedure(s) and Rule(s) in the same format, for instance, if only one Procedure is needed, make it's code [FELFIV]. Also name the Rule [FELFIV].

2. Rules

Basic information about Rules and each field within a Rule should be reviewed in RECALLS. With Vpf you have the ability not only to modify Rules but to add and delete them as well. Access to the Rules Menu is through Procedure Maintenance or Recalls. Then choose Intelligence Rules (or Nodes).

Situations in which a Rule is needed:

  1. If a Procedure generates a recall and a different Procedure should CLEAR the recall, a rule will need to be added to cause this to happen.
  2. If you add a field to the Patient Screen defaults, you must add a Rule so that the system knows what Procedure(s) update that field.
  3. If you add different Procedures to update an existing Patient field and/or clear recalls a new rule is needed.

Having Rules allows you almost unlimited flexibility in recall generation and clearing. For example, if you want puppies to receive a follow-up Parvo vaccination six months after receiving their final Distemper series vaccination. And if you then want a Distemper/Parvo booster six months after that, you may easily generate postcards at the appropriate times for these Procedures and have them clear each other out correctly. In this example, you would attach 180 Recall Days to the Procedure code for the final vaccination in the Puppy series. The Recall Text might be [Parvo Booster]. The Procedure Code for the Parvo Booster would also have 180 Recall Days, but the Recall Text would be [Annual Booster] or something similar. You would also need two rules. One Rule, PARVO*, would show that PARVO* and DHL*** (or whatever format your Distemper Boosters are in) would clear PARVO* Procedures. Another Rule would need to show that the Distemper Boosters are cleared by other Distemper Booster Procedure3 and also by PARVO* Procedures. See the following pages.

Screen #14

Screen #15

You may print Rules by either doing <Ctrl>[P] to print screen while viewing a Rule, or you may print all the Rules by choosing [P]rint from the Rules Menu. To see if a Rule already exists, you may choose [L]ist from the Rules menu or [T]ry a Rule from Utilities.

To delete a rule, from the Intelligence Nodes menu, arrow to Maintenance then arrow to delete or type [D]. Enter the rule to be deleted. The system will prompt, "DELETE Are YOU SURE?". Ensure that this is the correct rule to delete and type [Y] if it is or [N] if it is not.

A special rule may be added to cause a recall or recalls to be cleared by billing out any Procedure. Essentially this would mean that a recall could be cleared by a visit. This can be very useful if you want to send out recheck or fecal recalls but do not want to continue to send cards if the client returns for ANY reason. To do this, you should Add a Rule called [Visit] (note, this is not ALL capital letters). It does not need to update a Patient screen field, so enter [16] for Patient field. Enter [00] for Proc Type. Then enter whatever Procedure codes that should have their recalls cleared by a visit. When finished press <F2> for Done.

3. Bracketed Recalls

Occasionally, recalls for annual vaccinations and lab tests that should appear on the same card, are off by enough days to generate separate cards a week or so apart (typically due to leap year, different number of days in months, Patient illness, etc.). To enable V/BOSS to compensate for this condition, you may add an abbreviation, .Rbkt, which will extend your lead time by a percentage of the lead time. For example, if the schedule attached to a Procedure has a lead time of 30 days and .Rbkt indicates 10% bracketing, the lead time will be extended to 33 days. An important condition that should be remembered is that a recall must be due within the original lead time in order for the additional days to be used.

When adding the abbreviation, the text should contain the percentage value that you wish to use. Do NOT type a [%].


Screen #16

After .Rbkt has been added, the Recall Schedules will display the bracketing effects.

Screen #17

4. Upper/Lower Case Parsing

Adding the abbreviation .Vpar causes V/BOSS to print Client/Patient names, addresses, etc. in standard case rather than all upper case letters on Recalls and Mail Merges. The abbreviation text should be [Y].

5. FINAL Recall

With Vpf you may generate a final notice for Clients who have received the maximum number of Recall postcards and still not responded. This notice may be another postcard (written by you) or a letter (also written by you). When setting up your Recall Schedules you should enter FINAL days also. This will be the number of days after the Procedure DUE DATE that the Final notice will be generated.

Things to keep in mind:

  1. The Final notice date must be AFTER the date that the last regular follow-up card is sent. So the Final Days MUST be greater than (# Follow-up days x # Follow-up cards)
  2. All scheduled cards MUST be sent BEFORE the Final Notice is generated.
  3. We recommend that the Final Notices be generated once a month or every two weeks.

Running this Program is very similar to doing a Mail Merge. You will be processing a data file in V/BOSS that is stored in your Word Processor. You will create a document file in the Word Processor that you will then merge with the data file.

When ready to process the Final Notices, FIRST DO A BACKUP!!!!! These notices may not be rerun like the Recalls. If a problem develops and you did not do a backup, WE WILL BE UNABLE TO HELP YOU!!! DO A BACKUP IMMEDIATELY BEFORE RUNNING THIS PROGRAM!!!

Everyone should be off the system during Processing of the file. After doing the backup, from the Main Menu select [R] Recalls then [9] Final Recall Notice.

Enter the name of the data file. For Lyrix, [/usr/lyrix/FINAL.DAT). Do NOT type the brackets, but DO type the slashes! For Word Perfect, [/usr/wp5/FINAL.DAT]. Enter [Y] in response to "Shall I Continue??". After Phase 1 is completed, you will be prompted, "Produce File in U Upper Case or L Standard Case?". Enter [U] or [L]. When Phase 2 is complete you will see:

FINAL RECALL Processing Complete
HIGHEST Recall Count = X
Any Key to continue

Press <Enter> to return to the Menu. At this point, others may access V/BOSS.

Access your Word Processor. A sample document called "finalnotice" came with your system. You MUST make a copy of this document FIRST.

Lyrix: Choose Edit. Highlight "finalnotice" and press <Enter>. When the file is displayed, press <Esc> and then [x] in quick succession. Give the copy a name. DO NOT NAME IT FINAL or FINAL.DAT! You will be returned to the original file. Do <Esc>[q] to get out of it. Now you may edit the copy you just created. You must NOT disturb the top part of the document which contains the variables. Arrow or Page Down to the body of the letter. You may modify the body of the letter to suit your needs, including making it a postcard rather than a letter. You should use the variables listed below to personalize your notice. Be sure to type them exactly as they appear in this list. (Blank lines between groups of variables are shown here just to make it easier for you to select the correct variable. There SHOULD NOT be blank lines between the variables in the top part of any merge document!)

Variable: What will be inserted:
_customer Client Number
_name Client first and last name
_greeting Client last name and title
_title Client title
_c-first Client first name
_c-last Client last name
_address Client street address
_address2 Client second address line
_city-s-zip City, State Zip
_city City
_state State
_zip Zip Code
_telephone Client Home Telephone Number
_bus-tele Client Business Telephone Number
_bus-name Client Business Name
_c-lst-vis Client Last Visit date
_c-date-reg Date Customer was registered
_c-status Client Status (active, inactive)
_cust-ar Accounts Receivable for Client
_c-tot-sales Customer Total Sales
_c-ytd-sales Customer Year to Date Sales
_patient Patient Number
_pet-name Patient Name
_pet-sex M, F, MC, MN, FS, FN
_pet-sex-l he, she
_pet-sex-2 him, her
_pet-sex-3 his, hers
_pet-sex-4 his, her
_pet-species dog, cat, or species if other
_pet-breed Breed
_pet-birth Patient Birth Date
_pet-lst-vis Patient Last Visit
_pet-d-reg Date Patient Registered
_pet-status (A)ctive, (I)nactive, (D)eceased
_pet-seen-by Last Provider Patient Saw
_pet-tot-sales Patient Total Sales
_pet-ytd-sales Patient Year-to-Date Sales
_recall-i 1st Recall due
_recall-2 2nd Recall due
_recall-3 3rd Recall due
_recall-4 4th Recall due
_recall-S 5th Recall due

Do NOT use these last 5 variables in any other Merge document. DO NOT use the "finalnotice" as a guide for any other Merge document.

To Merge and Print the notices, see MAILINGS-LYRIX, Section 4-Merging and Printing.

Word Perfect: Press <F5> to List Files. Accept the directory /usr/wp5/*. Highlight the file "finalnotice". Press [8] to Copy. Give the copy a name. DO NOT NAME IT FINAL or FINAL.DAT! Press <F7> to exit. Then List Files again and Retrieve the copy you just made so that you may edit it. You may edit the letter to suit your needs (including making it a postcard). Be sure to use the Merge codes on the following page. To insert them, hold down <Shift> and press <F9>. Then type [F], then the number that corresponds to the variable you want inserted, then <Enter>.


To Merge and print the notices, see MAILINGS-WORD PERFECT, Section 5- Merging and Printing.


1~ Client Number
2~ Client first & last name
3~ Client title & last name
4~ Client title
5~ Client first name
6~ Client last name
7~ Client first address line
8~ Client second address line
9~ City, State Zip Code
10~ City
11~ State
12~ Zip Code
13~ Client home telephone number
14~ Client business telephone number
15~ Client business name
16~ Client last visit date
17~ Client date registered
18~ Client status (Active, Inactive)
19~ Client Accounts Receivable value
20~ Client Total sales
21~ Client Year-to-date sales
22~ Patient number
23~ Patient name
24~ Patient sex (M, F, MC, MN, FS, FN)
25~ he, she
26~ him, her
27~ his, hers
28~ his, her
29~ Patient species
30~ Patient breed
31~ Patient birth date
32~ Patient last visit date
33~ Patient date registered
34~ Patient status (Active, Inactive, Deceased)
35~ Last Provider Patient saw
36~ Patient Total sales
37~ Patient Year-to-date sales
38~ 1st Recall Due
39~ 2nd Recall Due
40~ 3rd Recall Due
41~ 4th Recall Due
42~ 5th Recall Due

Chapter 24 - BoardingTable of ContentsChapter 26 - Desktop

home page