|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: <SALES> 837I
You know, Rachel, I used to think this translation technique (EDI ->
XML -> XSLT -> internal xml - or even flatfile - or the reverse
transform) was a stretch. Or rather, an example of XML marketing hype
driving product design.
But after I've seen all these postings on this listserve about the
contortions you've got to go through to get the popular drag-'n'-drop
GUI mappers to do most anything, I've started to change my mind. It
sounds like with xmlLinguist you can do your mapping with an XSL
Transform (XSLT). The argument is compelling. You can now use standard
programming languages and XSLT to do the heavy lifting. Instead of being
beholden to the few expensive folks who know the idiosyncrasies of a
particular (expensive) translator, you can bring in off the street any
programming monkey who knows XML and how to manipulate it with XSLT,
Java, VB or Perl.
William J. Kammerer
Novannet, LLC.
Columbus, US-OH 43221-3859
+1 (614) 487-0320
----- Original Message -----
From: "Rachel Foerster" <
To: <
Sent: Thursday, 15 January, 2004 05:11 PM
Subject: RE: [EDI-L] <SALES> 837I
Omigod, translate flat file into XML and then use XSL to get it into a
highly complex 837 institutional claim transaction that complies with
both X12 and the HIPAA implementation guide. Anyone want to place bets
on the final result?
Also, X12 is most certainly NOT a flat file. Flat file typical implies
fixed field fixed record length. Rather, X12 is a data stream or binary
file of ASCII text characters, except of course, if one uses a
transaction with the BIN segment and flops into the BIN non-ASCII files,
such as image files, CAD files, etc.
Rachel Foerster
Rachel Foerster & Associates, Ltd.
Voice: 847-872-8070
email: <mailto:
-----Original Message-----
From: Bryce K. Nielsen [mailto:
Sent: Wednesday, January 14, 2004 9:57 PM
To:
Subject: Re: [EDI-L] <SALES> 837I
There are a lot of different any-to-any tools that would do this for
you. You will probably need to be a bit more specific though in the
details of the project. Mainly being load, OS, and automation need. Also
pricing may be an issue. Most mapping tools range greatly in price.
If you can run this on Windows and cost is a major issue, SysOnyx offers
a light weight, affordable tool called xmlLinguist at
http://www.xmllinguist.com. The map editor retails at $79.95 and the
automation engine is free. xmlLinguist translates a flatfile into XML
and visa-versa. EDI X12 documents are also considered "flatfile". Thus,
you can translate the propriatary billing file into XML, apply a
stylesheet to get it into the 837I format, then translate that back into
the flat, X12 format. Like this:
billingfile -> xmlLinguistMap into XML -> XML Stylesheet to 837
structure -> xmlLinguistMap into 837 file.
And through the free automation engine, this can be automated via a
VBScript or a commandline EXE. The key with xmlLinguist is affordability
and leveraging a relatively well known transformation language, XSL.
With very little out-of-pocket expense, you're up and running.
Bryce K. Nielsen
SysOnyx, Inc. (www.sysonyx.com)
Makers of xmlHack, the Simple XML Editor
http://www.sysonyx.com/products/xmlhack
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
