- This topic has 10 replies, 2 voices, and was last updated 14 years, 9 months ago by
.
-
Topic
-
This is my first x12 interface and I think I may have a corrupt formats file. When I run the testing tool for the x12 tab using the 00410 format, the message goes thru but I get a lot of segment ignored because they are out of order. I can try using that and re-arranging the definition. However, I believe I should be using the HIPAA-00410A1 format which has a v3 variant set up for the 837i. When I run the message thru using this format, I get: Please Wait ……
Command Issued: hcix12test -a -i -d 1 -f len10 -V HIPAA-004010A1 -v v3 -t parse /quovadx/qdx5.6/integrator/live/data/x12test.bin
Command output:
MESSAGE 1
START ENVELOPE
0(0).ISA(0) : >00* *00* *ZZ*123456789 *30*530196602 *091113*0945*U*00401*000100000*1*P*:< 1(0).0(0).GS(0) : >*HC*123456789*530196602*20091113*0945*1*X*004010X096A1<
TRANSACTION SET
unable to get information on X12 message ‘837’ for parse
END TRANSACTION SETS
1(0).2(0).GE(0) : >*1*1< 2(0).IEA(0) : >*1*000100000< The 837 message is not defined in the root format but was added to the site format as part of the v3 variant which we did not set up to my knowledge but came with 5.6 when we got it. Are there newer x12 format files? Does this evidence a corrupt file or set up? We are on 5.6r1 on AIX5.3. Thanx!
-
Replies
-
-
You should have a Companion Guide from the provider of the X12 message. That should tell you what standard is being employed. V1 is for Professional Billing, v2 is for Dental, v3 is for institutional (probably what you want but the Companion Guide should be the authority).
You probably should also have an 837 Implementation Guide. Unfortunately that has to be purchased from Washington Publishing.
Is this one message per envelope (between the ISA and IEA Segments) or are there multiple messages?
If there is just one is there an ST segment after the GS segment and an SE segment before the GE segment?
I have not had success with the one hipaa variant I tried (for a different Transaction Set) so I just used the base. The hipaa variants provided seem to be an attempt to make life easier by mapping the non-hipaa 837 standard to the hipaa standard thereby reducing the complexity of the structure.
However, as I said, I had sufficient issues I just reverted to the base non-hipaa standard.
One additional thing – when you actually move the message through the engine, you need to strip off the envelope as it comes in and then put it back if it goes out as an X12 message. There are provided procs in the tclprocs lib directory I believe and they are documented in Cloverleaf help.
Be aware there is a flaw in the split message (I don’t recall the name of the proc) proc if you want the envelope removed to include the GS/GE segment pairs as well as the ISA/IEA pair (leaving the ST through SE set).
If you need to remove the envelope down to the GS/GE, let me know and I will provide a proc I use to do that.
X12 is another world but not impossible to deal with.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
Thanx Jim! I appreciate the info. I have some specs from the sender (Quadramed) but was hoping not to have to mess with the variants. Guess that will not fly so I appreciate all your help. I will get back to the drawing board Monday and use this invaluable tool if I get stuck. I was reading about the interchange split and build procs so I will have to actually READ the directions! Thanx for all you do for this forum!!
-
-
Well, I added the ‘split’ proc to the IB side, the ‘build’ proc to the OB side, routed the message as a raw wild card and got it to the outbound connection (/dev/null for now). I am still working with the vendor on an ACK process as it seems they have never done a TCP connection but always did a download to file. The only things I see wrong (??) at this point are that the OB message has lost the ISA/IEA segments (goes from GS to GE) and it hangs at a state 11 and will not go out of the recovery database even though I do not have AWAIT REPLIES checked. I suspect the missing segments is related to the ‘split’ proc problem which i will work on. Anyone have an idea why the hang at state 11? Thanx!
-
-
Thanx! The trading partner (Quadramed) does not seem to have a clue on how to do an X12 in TCP/IP mode. I will look into getting a copy of the standards so I can fight with them. Right now, this is just in house until I can get it working. Then, I willchange the OB thread to an ftp folder so the patient accts folks can import it and massage it on line with Emdeon vendor. I have tried to avoid the direct ftp download from Quadramed as i want to be prepared for the future when we need to send directly to the payors. I do not think dup charges will be a problem for now since the file will be manually worked online with the vendor’s web app. The cureent file is a batch and I suspect any future ones will be also. Thanx!
-
-
Nope – that is a bug.
It really is not causing any issues, it just is reported incorrectly.
What is happening is the original message is being copied with the split effective, and that message is being continued, then the original un-split message is being killed as it is no longer needed.
With debug turned on, the verbiage for the Kill is indicating an error when there really is no error.
You can change that echo or I can send you an updated version once I make the change here.
There is a Cloverleaf(R) provided proc called hciX12buildinterchange that puts the envelope back on the split message when you are ready to send it to someone that wants the entire message.
email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.
-
-
-
- The forum ‘Cloverleaf’ is closed to new topics and replies.
