X12 and Cloverleaf(R) 5.2

[Jim Kosloskey]

All,

It has been a while since I have done any work with X12 on Cloverleaf(R).

However, I am experiencing a situation wherein I am setting the initial HL segment in the standard 270 Transaction set and I am getting an error message saying the ‘HL segment is not defined for message type 270’.

Maybe I am just rusty, but I would think something as simple as setting the HL-2 (Hierarchical Parent ID Number) to some constant would not cause the error I see.

It is almost like the HL is not in the definition (however it is definitely in the configuration for the message).

We are on Cloverleaf(R) 5.2 so maybe that is an issue.

Can anyone suggest where I am going wrong?

Thanks,

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

Topic

[Charlie Bursell]

Not a lot of info here Jim  🙂

What version?  Where are you setting it, vlate or where?

There is definately an HL segment defined for a “standard” 270.  Perhaps you are addressing it incorrectly?

[Jim Kosloskey]

Charlie,

Cloverleaf(R) 5.2.

The X12 variant I am using is HIPAA-004010/v2.

I am using an Xlate and in that Xlate I successfully build the ST and BHT segments.

When I attempt to COPY =XXX to  0(0).HL.3#735 (Hierarchical Level Code) and then run the tester I get the ST and BHT segments built correctly and an error message “[0:Test] [mid:0x000033c] The # 2 segment encountered ‘HL’ is not defined for message type ‘270’. Segment ignored.”.

I have a dummy frl coming into my Xlate and I am building the X12 message out using literals to get a sample message to play with.

I have checked the messages file in the HCIROOT formats directory for this variant and the HL segment is definitely defined.

So I don’t think I am doing anything really out of the ordinary but I must be doing something incorrectly.

Thanks,

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Charlie Bursell]

Are you sure the correct address is 0(0).HL.3#735?  The 270 I see looks like:

ST

[S2S]

BHT

{

  HL

  [{TRN}] 9

etc.

Which would put the HL at level 1

Other than that I would have to see the Xlate.

If you are doing HIPAA stuff you probably need the verification stuff that comes with our HIPAA package

[Bob Richardson]

Greetings,

Jim, we have a 270 Eligibility interface that uses the X12 standard

HIPAA-004010A1 template and the first HL group is defined as:

1(0).0(0).HL  and then there are other HL groups that follow.

These buggers are tricky – fortunately we have an X12 expert in our group (business analyst) who taught this stuff in a previous life.

Maybe your path is incorrect or you may be referencing the wrong HL segment to populate:  there are multiple groups of HL for each section in a 270 message type.  Try running it through the X12 testing tool (much like the HL7 variant tool).

Hopefully this helps you out.

Good luck, good hunting!

[Jim Kosloskey]

Charlie,

After a fair amount of sluething I discovered that if I attempted to put more than 2 leading numeric characters in the HL field HL-#628 (Hierarchical ID Number) – which is specified in the variant as a 10 character string I get the error I was experiencing.

If I change that, I get by the HL error.

Not a big thing right now but since there does not appear to outwardly be any constraint on the content of that field in Cloverleaf(R) – after all a string is any set of displayable characters isn’t it? – I can expect that will be an issue in real life.

In any case, thanks for your assistance. Your questions got me to probe more and that eventually led to the work around. The sanity check alone is priceless.

Take care,

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Jim Kosloskey]

Bob,

Thanks for the assistance. Between you and Charlie I began to understand there was something going on which was not kosher.

You can see my post in reply to Charlie to see what I discovered.

Unfortunately I do not have an X12 message to use with the X12 Tester. I am trying to build an X12. Once I have that built, I can use the X12 tester to further check my sanity.

Thanks again.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Jim Kosloskey]

Charlie,

Am I correct in assuming the HIPAA validation package is a Tcl package which is available for a charge?

Ken Bartlett is sending me some information regarding Insurenet Direct (R) and perhaps other information related to X12 and HIPAA.

Would the package you refer to likely be either a separate item and/or included in the information Ken will be sending?

I know if we ever get moving down this X12 HIPAA path further than just probing around, certification is a likely necessity.

Thanks for the heads up.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Charlie Bursell]

Jim:

No you are not correct.  It is not a Tcl package it is a 3rd party package and is avaialble as part of our InsureNet package and it is from EDIFECS

However, it is almost impossible to do proper HIPAA without some sort of validation.  Talk to yur Account Rep for more info

[Jim Kosloskey]

Charlie,

I have had a conversation with the Account Rep and he is sending information to me regarding InsureNet (R).

As you have said, my research has indicated certification/validation requirement is almost a certainty. Having that as part of the offering adds intrigue.

Thanks again for the heads up.

Jim Kosloskey

email: jim.kosloskey@jim-kosloskey.com 29+ years Cloverleaf, 59 years IT - old fart.

[Nathan Martin]

Jim,

Quote:

error message “[0:Test] [mid:0x000033c] The # 2 segment encountered ‘HL’ is not defined for message type ‘270’. Segment ignored.”.

This error may have been from the testing tool trying to reparse the translated message for details.  (The HIPAA formats might make message generation easier, but they fail at input.)

Try turning detail level to 0 and saving to a file, then read that file with the X12 format tester and a non-HIPAA variant.  (You’ll notice that the addresses are different between formats.)

Nathan

[Author]

Replies