Setup Sequence

The data that supports companies and practices in MedSuite's database is maintained in a number of tables.  A specific table may be said to be either company-specific in that the data is used for all practices in a company, or the table may be said to be practice-specific in that the data is used for a single practice in the company.

Before you can use MedSuite's On Demand Software to enter patients and visits and begin billing, the company-specific and practice-specific tables that support this process will need to be loaded.  This section covers the both the tables that need to be loaded and the sequence in which these tables need to be loaded.  The sequencing of the data load is important since you may find yourself attempting to enter information only to be forced to stop because you are missing other supporting information.  This type of problem is avoided by knowing and understanding the "data dependencies" of the software.

For example, before you enter any names or addresses in any of the company-specific or practice-specific tables, you should have created all of the information you will need in the supporting Postal Codes, Titles, Degrees, and Generations tables.  Otherwise, you may create a Referral without a Postal Code or without a Title.  Then you will have to go back later and correct all of the Referrals that you entered.

When a company becomes a MedSuite client, a database will be set up for that company.  This database will already contain information in the company-specific database tables.  This information comes from the MedSuite "StarterSet" and is the information that we at MedSuite think you need to get started.  This StarterSet information is simply MedSuite's ideas on what the Company-Level tables ought to contain but is yours to do with as you please.  These tables may be kept intact, deleted and replaced, or expanded upon.

There are two important pieces of information in this section of the document.  First, you have been given a list of MedSuite support tables and what they are used for.  Secondly, you have been given the sequence in which these tables should be built so that you will not be constantly forced to stop and address data dependency issues.

The tables should be examined and built in the following sequence: