Brian,
In the case of example 21 we have a pre-configured database for
the Institution and the insurance carrier data. This allows you to
edit the institution and insurance carrier data using the 297s
administration
screens. As a result you would want to keep your databases in separate
folders for each
provider. In example 21 we are looking at one provider and one
insurance carrier. In the C1.INI
you will see that it says
[system]
purgesystem=carriergroup
When the purge is run the insurance carrier and the institution data
along with their insurance contract table
data is not purged.
On the other hand Example 52 uses a different purge than example 21 in
the C1.INI
[system]
purgesystem=all
This clears the entire database in a folder and thus the ability to
let the source file build everything
in your database. This allows you the ability to have multiple
unrelated providers being processed
within a single folder by just copying the new source file to the file
named specified in the c1.acu.
Since example 52 is using the ACU to convert an X12 837 file, we take
advantage of the fact that
the 837 has enough information to build our databases correctly.
In some of our other example we do use the purgesystem=all. In these
examples we are typically doing a two pass
bcu where the first file the BCU process is the institution, provider,
and insurance carrier data and the secon pass file has
the claim data. The reason we split the process, was to be efficient,
but there is no other reason that a single CSV file
can't be set up to contain all the data you would be needed to build a
single pass bcu that would use purgesystem=all.
Hope that helps to start to answering some of your questions.
Thanks
Dave