Page 1 of 1

Tying Transactions to the original Claim from the Transaction Export

Posted: Thu Nov 01, 2018 5:27 pm
by Pcuezze
Hello all! I am a database novice and not a regular Medisoft User. I am handling the issue for my wife's practice so go easy on me!

As part of a transaction, we are converting to accrual accounting. The firm doing it is trying to reconcile transactions from the Transaction Export report. (we want to export the data into FileMaker where I am much more comfortable) We are really struggling to find how records with a Procedure Code of “INSPAY” or “INSADJ” tie back to the original claim (with a CPT populated in the procedure code). As you can see from the linked spreadsheet, no single field or even a combination of fields can be used to tie the adjustments and payments to the original claim (I narrowed it to just one Chart Number for ease of understanding). Are we doing something wrong or is there no stock way to export the unique record identifier? There must be some Key Field establishing a relationship (between a Claim and each Transaction) because when we pull up a claim in Medisoft, you can see all the transaction associated with that claim and ONLY the transactions associated with that claim. Thanks in advance for any help you can give me.

PS, I am running the database on a replicated server at my house and have installed the Advantage Data Architect but do not see any kind of parent/child fields in the tables themselves, I assume such relationships are stored in the data library which is getting over my head for sure. But if there is a simple way to view relationships between fields, I'd love to know how to do that as well). May thanks in advance! Patrick

http://www.kcmpcare.com/wp-content/uplo ... -test.xlsx

Re: Tying Transactions to the original Claim from the Transaction Export

Posted: Fri Nov 02, 2018 11:42 am
by Gavin Walker
The applied payments and adjustments are link to the charges in MWTRN through the MWPAX table.

Re: Tying Transactions to the original Claim from the Transaction Export

Posted: Mon Nov 05, 2018 9:27 am
by Pcuezze
Got it. Thank you. Is there some reason they use a bridge table this way versus just associating a unique "Charge Number" to each "Transaction"? Does it make the database more efficient somehow? Thanks again for your help. I was able to export the pax table, build it all in Filemaker and generate a unique ID. Just seemed odd to me..

Re: Tying Transactions to the original Claim from the Transaction Export

Posted: Mon Nov 05, 2018 7:35 pm
by Gavin Walker
Well the database was designed about 24 years ago, so I am sure it must have seemed like a good idea at the time. :D