|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: <Sales> XML/EDI Products
A hospital buying medical products, receiving invoices and paying invoices
and also submitting health care claims, inquiring about the status of a
claim, determining patient eligibility prior to admission would need both
supply chain and health care transactions.
Rachel Foerster
CEO & President
Rachel Foerster & Associates, Ltd.
Professionals in Health Care EDI, Privacy & Security
39432 North Avenue
Beach Park, IL 60099
Voice: 847-872-8070
Fax: 847-872-6860
eMail:
http://www.rfa-edi.com
######################################################################
This transmission may be confidential or protected from disclosure and is
only for review and use by the intended recipient. Access by anyone else is
unauthorized. Any unauthorized reader is hereby notified that any review,
use, dissemination, disclosure or copying of this information, or any act or
omission taken in reliance on it, is prohibited and may be unlawful. If you
received this transmission in error, please notify the sender immediately.
Thank you
-----Original Message-----
From: Michael Mattias [mailto:
Sent: Thursday, February 13, 2003 7:46 AM
To: 'EDI-L (E-mail)'
Subject: Re: [EDI-L] <Sales> XML/EDI Products
> Michael,
> You don't have to buy an expensive translator to do the things you are
> talking about. .....
I think that is exactly what I was saying. One of my long-time 'gripes'
about 'EDI software' is, in general, you have to license
(pay for) way, way more capability than you will ever need. Not only that,
but all the 'big guys' offer their products only as
complete suites, requiring the user to learn and maintain a whole system. I
really think this kind of cash and human investment is a
huge barrier to "edi-enabling" for the smaller user.
Suzy User doesn't want to enter a new customer, then enter a new 'trading
partner' in another system: Suzy User wants to enter the
new customer and check the "yes" box next to "Should this customer be set up
as an EDI customer?"
I work with clients in two primary industries: Manufacturing/Distribution
and Healthcare. So what do I care about Ocean-going
freight manifests, or customs declarations, or court filings? For that
matter, how many Real Users (i.e. non-consultants) would
need BOTH the Mfg/Dist transaction sets (850, 810, 856 et al) AND the
healthcare transaction sets (835,270,837 et al)????
Well, if the big guys don't want to look at the little guy market, I will.
I'd like to do this though the applications vendors..
probably because I've seen enough really poorly-designed "EDI Modules" from
vendors of accounting, billing or inventory systems to
know they could have done a whole lot better with some kind of API approach.
Michael Mattias
Tal Systems, Inc.
Racine WI
> -----Original Message-----
> From: Michael Mattias [mailto:
> Sent: Wednesday, February 12, 2003 12:53 PM
> To: EDI-L (E-mail)
> Subject: Re: [EDI-L] <Misc>Flat File Creation - clarification.
>
> 2/11/03
>
> <SHAMELESS COMMERCIALISM>
>
> A couple of months ago I had an idea for a low-cost "generic" tool which
> would convert ANSI ASC X12 EDI into XML and vice versa; the
> idea being to take advantage of all the relatively low cost XML software
> out there to obviate the need for an expensive translator
> for those who only need to handle a couple of transaction sets.
>
> This would take an input file containing ANSI EDI and create an output
> file kind of like..
>
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>, <LIST>, <TECH>, <MISC>, <EVENT>,
<OFF-TOPIC>
Access the list online at: http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
