|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
Re: <SALES> 837I
Racheal,
xmlLinguist offers a different paradigm. Rather than using a Mercator-like
mapper, you can use XSLT, a very easy language to learn (and there are even
Mercator-like visual mappers around). The beauty of XSLT is in it's flexibility.
You can go to a custom FlatFile, an HTML page, a SQL statement, etc. Plug this
into an EAI system and you can do a whole lot more than typical EDI Translators
without a lot of custom work.
The main point of my response however, as well as one of the key strengths to
xmlLinguist, is it's price. For less than $80 USD, you can be up and running.
There are no "per-server" or "per-cpu" charges either for the automation engine.
And leveraging on common technology (i.e. XML), the learning curve should be
small. Yes, there is a little more work involved (two maps, a stylesheet, and
potentially a schema to make sure the resulting X12 is valid) and thus
xmlLinguist may not be for all. It does though provide a very affordable
solution to a lot.
Bryce K. Nielsen
SysOnyx, Inc. (www.sysonyx.com)
Makers of xmlLinguist, the Text-to-XML Translator
http://www.xmllinguist.com
P.S. I would differ on X12 not being flat though. Of course, I have a very broad
definition of what is "flat", not just "fixed field fixed record length". For
me, pretty much anything I can view in Notepad is flat (i.e. any file of ASCII
to UTF16 characters). I consider XML "flat". CSV files are "flat". etc. Sorry if
that differs from your view on the matter (i.e. this is not meant to be
inflamatory, rather just an explanation of my views).
----- Original Message -----
From: Rachel Foerster
To:
Sent: Thursday, January 15, 2004 3: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
[Non-text portions of this message have been removed]
|
|
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
