Importing into the database but..

[denissedonnelly]

When importing the x12 (837 for example) into the database is there the ability to export and recreate the x12 that was imported?

Thanks!

Denisse

[nwlynch]

Yes there is.
What language did you want to use to generate the X12?

I have done it with Excel VBA.

[denissedonnelly]

What I'm trying to accomplish is importing the data into a SQL database and later recreating the same 837 x12 file by exporting it.

I will have to double check but I thought I also wasn't able to successfully import into my SQL database that I was testing with.

[nwlynch]

Yes, once you get it into the DB, you can extract specific X12 claims by using a transaction number that ties the segments all together.

I'd offer some example code if I knew what you were coding the extract application in.

[denissedonnelly]

There were a few different applications I was trying to test but I think with this I didn't have success getting the claims into the database.

I will try again in a couple of hours when I'm done around the house. With the extraction part are you able to do it based on file and not the transaction number?

Thanks for your help as it's much appreciated!

[nwlynch]

Hi,
If you keep track of the file used to create the transaction set that the claim is comprosed of, you can easily pick what you need. I'll check it again for more specific help tomorrow.

Meanwhile, good luck with the importing which should work almost magically if you have adequate rights to the DB.

Cheers,
Neville

[denissedonnelly]

It's my personal database so i have dba rights. I don't recall there being any specifications that can be added to the config file or does the server/database name info need to be added in the command line?

[denissedonnelly]

Please forgive me but I'm honestly not that familiar with Visual Studio. Maybe if I also explain what I'm trying to do that will be helpful as well.

1. I want to import 837s (P, I, and D) into a database to pull some of the data from it and along with adding a couple of segments.
2. Once the additional segments are added I would want to recreate that file with the additional segment.

I was able to import some test files along with identifying the various tables/columns I need to extract some of the data.

My next question is how would I create a 837 export from what was imported and also it is possible to keep the same file name? The import process was very quick.

I do wish i happened to have a file table which also lists the total claims per file as that would be helpful. I'm happy for how this works though. Just wanted try to figure out how to actually create a file from what's in there now.

I believe that was a table created from MDMS17/837Parser's application. Anyway, not making a comparison as this is great too. Just gotta figure out how to export it.

I need to get ready for work but I will check to see if I get any responses later today.

Thanks so much.

[nwlynch]

Hi,
There are stored procedures created by the code that let you grab a whole file worth of segments that can be written out to the file system with whatever name you like.

Unfortunately I don't have the exact information for you right now but you need the Transaction Set ID from when you imported the file and then get the line terminator record with this:
sql = "SELECT TOP 1 SegmentTerminator FROM dbo.Interchange WHERE Id = " & TransactionSetID - 2 & ";"
And get the rest of the segments that were imported from that file with this:
sql = "SELECT [Segment] from dbo.GetTransactionSetSegments(" & TransactionSetID & ",1,1);"

Then I write the records out line by line and add the terminator. I did this because the stored segments don't have the terminator.

Good luck and let me know how you go.

[denissedonnelly]

Was the stored procedure included with it? I don't believe I got any stored procedures with the zip file. I didn't see that. I will look around to see if I can find anything else.

Thanks.

[nwlynch]

Hi,
Sorry, it was a function, not a Stored Procedure and yes it is created when the first Import is run.

Hope that helps.

[nwlynch]

Also, the filename is stored in dbo.Interchange.FileName so you can retrieve the Transaction Set ID as:
select ID from dbo.Interchange where FileName="YourFile.edi";

Then use the Transaction Set ID to retrieve the segments as per my earlier message.

[nwlynch]

If you use SELECT SEGMENT FROM GetTransactionSetSegments(3,1,1);
You will get all of the segments for the file loaded with transaction ID of 3.
Just push them out to a file and you will have a new file from the DB.
If you want to load them into a system, you may have to change service dates etc. to prevent rejections due to duplication.

[denissedonnelly]

That's helpful. I tested it and it pulled the one claim record I tested. What if I wanted to pull the whole claim file? What would I do to replace the first value in the ().

Also have you ever added a segment? The additional segment I was going to add is a REF*LU which would go under the REF table. Is there a feature that will recalculate the values if you add a value?

Thanks again for your help.

[denissedonnelly]

Have you ever had to deal with a file that didnt have st/se lines per claim and instead just one st and one se for the complete file?

Thx

[nwlynch]

Regarding the addition of a REF segment, I've added segments manually and recalculated the line count value on the footer but not programmatically yet. As LU is situational, I'm curious as to how often would you need it?

For the data with one ST/SE set, that just sounds like a set of claims for one provider. You can include or exclude the transaction set control lines with one of the parameters of the getTransactionSetSegments function when you recreate the file.

You can also take segments from a file with one of the programs in the project. I only played with it once though and will have to take a look at it again.

What system are you loading into?