Access .mdb file to X12 837 file

[Benton]

Could you please look over what I am doing to let me know if I am
creating the X12 837 file correctly?

A branch of our business provides a monthy medical service to over a
1000 customers, and the service is billed to Medicaid each month. The
staff in that department has been entering each month the 1000+
customers one at-a-time into the EDS website form for billing from
Medicaid. Its a very time consuming process. The 2 dozen or so
fields for each customer comes from a database of customer info that
has already been recorded, and that data is printed out and then re-
entered into the website. It would be much simpler and save dozens of
hours each month if we could just turn that database query information
directly into an X12 837 file that EDS will accept.

I have created a table in a Microsoft Access 97 database that contains
the monthly data for each customer. There is also unchanging data
such as our Name, address, monthly cost of the service and the code
for the service.

We are using the C1A3F297.exe program to convert the database into an
X12 837 file that we can then send to EDS.

I have entered the unchanging information into the program in the
Files -> Provider Data.

In the .bcu file I have referenced all the fields from the .mdb file
that need to be in the X12 837 file EXCEPT the information that I
entered into the Provider Data form.

I downloaded Example 41 v2 as a reference. Can I use, do I need to
use, the C1.cfg file from that example in my own data folder?

I have added the path to the database to the C1.ini file from Example
41 v2. Do any other changes need to be made to that file to be added
to my data folder?

Once I have the .bcu file, the C1.cfg and the C1.ini file, along with
the database in my data folder, can I run the program to create the
X12 837 file?

I do have the documentation that came with the program and from your
website. I am a desktop support person, not a programmer or EDI
technician so this data is not something I have worked with before, so
all your help is greatly appreciated.

Will the steps I have outlined work so I can create a test-file to
submit to the EDS website?

Thank-you.

[Com1 Software]

Benton,

The way example 41 works is that it uses a two pass method where there
is an initload table that has the
group,submitter, and carrier data in one record. We use the initload
file to populate the base data if you will.

Provider data is imported in the second pass with the claims data.

To go over:
The Institution and Submitter will be your company, and the providers
will be
people who provide the medical service.

The translator can be set up many ways, depending on how your
operations work and
we can set up a new example that fits you better that example 41.

One thought is that in example 41 we count 100% on the data in the two
tables in the .mdb
to populate everything. You will notice in the C1.INI we have a
purge=all statement
that coupled with the purge command in example.cmd file wipes out the
whole database.

If lets say that in the delivery of your medical services the the
provider is always the same, then
it might make sense to enter data in the provider,and institutional
screens to set things up.

Because you are sending to only medicaid we do the same for the
carrier as well.

The type medical services offered and how that effects the Provider
records is the question we
want to address first.

Regarding running the example, if you have the odbc set up correctly
and the path and directory set in the example.cmd
it should produce an x12 837 file called I0000001.tcf.

To figure out what happened if it did not produce a file is to look a
the different logs that are created. The command log is most useful.

Thanks
Dave

[Com1 Software]

Benton,

We have added Example 46 to the Command Line Translator Examples Page.

http://com1software.com/c1180.htm

In this example we have the claims.mdb that we gain access to via
ODBC.
Create a data source using the ODBC Data Source Administrator. Name
the
data source Example46 and link it to the claims.mdb supplied with the
example.

Data in the institution and provider data screens should be modified
with your companies
information. The insurance carrier should be modified with its proper
name as well. In the
institution data screen there is button for the Insurance Contract
Table. This is where you
will be able to set your submitter information.

This example should be closer to what you need.

Thanks
Dave

[Benton]

Thank-you for this example.

I am using C1A3F297 version 1.15F-26

I downloaded the file and extracted it into the working folder instead
of calling it \example46. The working folder is c:\C1A3F297\cms1500.
I put that path name in the properties of the desktop icon as per the
instructions from the readme.txt file in the example46 file. When I
launch the application, I get an error message and cannot start the
program. The error log was sent to your website.

The database file, CMS1500.mdb, is located in a different folder out
on our network since that is where it will need to reside for the
department that creates it. I did put the path to that file in the
C1.ini file in the [system] section, as instructed in another thread
on this forum.

Do I need to make any changes to the C1.CFG file?

In the C1.bcu file, I will put in the appropriate fields from the
database. Do I change the line sourceodbcdsn=EXAMPLE46 from that
file?

In the file EXAMPLE.cmd, do I change the lines

DIRECTORY=\example\ex46
PATH=\example\ex46

to reflect the working directory where all the files except the
database are located?

In you earlier email you instructed:

"In this example we have the claims.mdb that we gain access to via
ODBC. Create a data source using the ODBC Data Source Administrator.
Name the data source Example46 and link it to the claims.mdb supplied
with the example."

I don't see the ODBC Data Souce Administrator in any of the menus.

I will put in our data in the institution and provider data screens
and complete the submitter and carrier information too.

I am very grateful for all the feedback you are giving me to step me
through this process. This is very helpful to me and I am sure it
will assist many others who are using this software.

[Com1 Software]

Benton,

If your working directory is c:\C1A3F297\cms1500
and you have extracted example 46 to that folder, then you will
need to modify the shortcut you use to run the translator.

It is a good idea to make a copy of your shortcut and then modify it
since
the shortcut that is created by the setup program could be overwritten
when the
setup program is run next time.

You should create a new shortcut to the program exe with the
appropriate parameter for each working folder that you plan on working
with.

Make sure that your shortcut target looks like this:

c:\C1A3F297\c1a3f297.exe \C1A3F297\cms1500

Also make sure that in the example.cmd the path and directory are set
properly.
The Verify button in the Command Editor can also be used to set these
values.

DIRECTORY= \C1A3F297\cms1500
PATH= \C1A3F297\cms1500

There should be nothing to change in the C1.INI.

Regarding the ODBC Data Souce Administrator, it is a Windows
function located under the Control Panel and then in Administrative
Tools you should see
Data Sources (ODBC), that is the ODBC Data Souce Administrator. It
allows us to build
our local computers ODBC connection to your source mdb.

You should be fine with mdb on the network as long as you have the
correct settings for it in the
c1.bcu and in the DSN that you create.

sourcetable=CLAIMS
sourceodbcdsn=EXAMPLE46

You may want to make a couple of ODBC dsns on you computer as well as
additional shortcuts and working folders.
You might have one to run the example and another to run a new test to
move you forward.
It is a good idea to keep your example running well as a baseline to
know that things work.

Thanks
Dave

[danielledlydon]

Just a thought, you might want to consider upgrading to Access 2007.
It handles a lot of what you are trying to do in conjunction with xml
and other processes. We use the Com1 parser with SQL and Access 2007
in a very complex setup.

Best to you,
Danielle Lydon

On Jun 30, 10:34 am, Com1 Software <informat...@com1software.com>
wrote:

[Benton]

Everything seems to configured, and I can click on the Run button and
choose the EXAMPLE.cmd file. It starts running and opens another
small window. I can see the program running in the Task manager. But
it never does anything else, it doesn't show me progress, it never
finishes, it never produces output.

What could be causing this?

Thanks.

-Benton

[Com1 Software]

Benton,

I tried to simulate the hangup you described , however I couldn't.

Usually we tell people to check the command log first to see what
might have happened. Based
on your description you may not have gotten any command log data.

In your windows odbc setup you should have it linked to the examples
CLAIMS.mdb and it should
be located in the \C1A3F297\cms1500 folder.

I have an example of how mine looks:

http://com1software.com/training/odbc004.gif

http://com1software.com/training/odbc001.gif

Where it says Database: h:\example\ex46\CLAIMS.mdb yours should say
Database: c:\C1A3F297\cms1500

Also the other usual things to check are the target in the shortcut
you use to run the translator. It should say:
c:\C1A3F297\c1a3f297.exe \c1a3f297\cms1500

The start in directory should be :
c:\C1A3F297

When you are in the 297 program in HELP, INFORMATION the Data
Directory should be
\c1a3f297\cms1500 and the Base Directory should be \c1a3f297

Also double check your example.cmd using the Verify Button in the
Command Editor.

There should be no modifications to the bcu file.

You should be able to see the claims.mdb data using the View ODBC Data
in the Utilities section of the menu.

Let me know how it goes.

Thanks
Dave