Search results for query: *

Thanks, gibson! - PETE

A 997 can be generated for each interchange. A compliance error (e.g. missing required information, indicator w/out data, missing segments, etc.) at the detail segment level will only cause the functional group to be rejected, not the whole interchange...unless, of course, you send only one...

I'm not sure which is standard. It depends on the method the client uses to transmit. If they use some sort of FTP or a Mailbox (like Advantis) and they pay a fee (usually per Kilo-Character), then usually they drop the carriage return and make it one long string. But, I speak from experience...

Hey Olliver, Check out Washington Publishing company's website: http://www.wpc-edi.com/hipaa/HIPAA_40.asp down towards the bottom, you will find the 837 guide. I think you can download it for free, or pay $70 for a bound copy. It will have all the looping information and structure codes in...

It sounds like you got this problem figured out...but next time, you will run into fewer naming convention issues if you use a prefix that describes the object. For example, you could have called your query "qryData" and you could have called your module "modData" then you...

This really won't help your problem directly, but as a general rule of thumb, avoid using spaces in naming conventions. Use an underscore if you really want the space there. VB sometimes has problems with spaces in unexpected places. You should be aware that the rumor is that Microsoft is...

No. I still haven't found any examples. Thanks, - PETE

I am in the health care industry. Clients pass to us 834 transaction sets. We are new to the HIPAA EDI process. I am wondering if there are any instances where the AK901 or AK501 fields will read "E"? What instances? Thanks, Pete