Originally posted by: SystemAdmin

I want to do mapping from XML to EDI flat file. I want to work on a medical transaction. Can any one give me a sample document -
1. an 837 xml input doc.
2. an EDI tree for the 837
3. a specification or mapping doc.
4. an 837 xsd
Thnx in advance.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: jvanboga

By definition EDI/X12 or the 837 is not an xml file/document. You can wrap it in xml but in and of itself it isn't.

So, I'll assume you need to map xml formatted claim data to an 837. If you don't have an 837 type tree you'll need to either buy the HIPAA package or build one (buying the package would make your life a lot easier) As of today you'll need to have the 4010 version of either Institution, Provider or Dental. In the months to come you'll need the newer (5010 version(s)). If you are going to build your own type tree I'd recommend getting a copy of the implementation guide (go to the WEDI web site).

As far as your XML data, you probably want to organize it higher-archichally. First by clearing house or trading partner, then provider (billing, servicing, etc), next by claim (organized something like claim + subscriber + patient if diff than sub + sevice lines).

Hope that helps.

#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: janhess

Build your XML type tree by importing the XML schema. Buy the output typetrees from IBM. I'm sure the mapping is easier than Rep says.
#IBM-Websphere-Transformation-Extender
#DataExchange
#IBMSterlingTransformationExtender

Originally posted by: jvanboga

The mapping shouldn't be that hard if the input data is organized properly. The hard part is...

1. Building a compliant type tree.
2. Building a compliant 837.
3. Building a compliant type tree.

Accepting inbound 837 data from multiple sources is also more difficult than creating an outbound 837 for multiple destinations. In the first case you need to be able to accept any HIPAA compliant 837 and deal with all the allowable variations in interpretation. The second is simply building an 837 that meet the HIPAA compliance requirements.

The difficult part of the outbound 837 is to meet all levels of compliance. If you can do that, in theory, any TP receiving the 837 is required to accept it. In most cases though, there ends up being some give and take on both ends of the transaction.

Again, I'd recommend using the HIPAA package. I also recommend, if you don't already have it/them, getting a copy of the 837 implementation guides. A few years ago they were free from WPC and there was a link at the WEDI site. You may have to pay for them now. They have been a lifesaver in compliance related issues here. If we get a file from someone and it's a problem we point to the section and verse found in the guides to help our TP get it right. I believe we have become a highly credible source of answers for all of our TPs.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender

Originally posted by: SystemAdmin

No problem. I use all my experience from the years I've put in, the classes I took which had to be paid for, all the time it took to build said documents, grab the X837 type tree and give it to you illegally....the moment you upload a check with a substantial amount for a consulting/theft fee.

I'm sure anyone here would be happy to help out if you get stuck or need direction, but what you're asking for a bit much. Ive built maps that used XML for Input/Output, and have worked on 837 maps, and its no joke. You have a long way to go.
#DataExchange
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender