HP3000-L Archives

February 1997, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Neil Harvey <[log in to unmask]>
Reply To:
Neil Harvey <[log in to unmask]>
Date:
Sun, 23 Feb 1997 16:15:02 +0200
Content-Type:
text/plain
Parts/Attachments:
text/plain (70 lines)
We use EDI to receive medical claims, and send responses.

The messages are few, clearly defined, and fairly stable, and we took
the route of using EDI software on UNIX to handle the comms between us
and the VANS, and we ftp the files to the HP3000 where a Cobol program
"flattens" them into useful input data.

We found that the EDI software was not always very good at this
flattening process, and required as much effort to set up and maintain
as writing our own Cobol program.

We do use the EDI software to re-package and send responses, since these
are infinitely simpler.

I don't do much EDI stuff myself, but in conversation with my
colleagues, it smacks of a standard designed by a committee, to suit
no-one exactly, and compromise everybody.

I would like to think that we could throw it out and replace it with
ftp/e-mail, but whenever this is mentioned, one million bean counters
throw up their hands in horror.

Oh well.

Regards

Neil




> -----Original Message-----
> From: HP-3000 Systems Discussion [SMTP:[log in to unmask]] On
> Behalf Of Patrick Thrapp
> Sent: 20 February 1997 04:47
> To:   [log in to unmask]
> Subject:      EDI & the HP3000 Questions
>
> What I am looking for is some uses of EDI which ultimately end up on
> the
> HP3000.  As I see it there is the communication software to get the
> data
> to or from the VAN.  This can be a simple as a shell with file
> transfer
> capabilities, to 'viewers/browsers' that let the user 'view' the
> transferred data logically.  I have heard that these systems also
> allow
> the user to create data maps to create 'flat' files.  Armed with these
> 'flat' files one can create uploaders into propriety systems.  In our
> case an IMAGE database.   Seems to me all EDI is, is a well defined
> system for defining data and its flow.   This is like trying to hit a
> moving target.  I mean imagine trying to maintain code for the tax
> code.  You'd always be behind.  There has to be some kind of volume to
> warrant the time spent to do business this way.  So question.  DO many
> of you here use EDI?  If so, do you have support programs/systems to
> do
> some of the task?  Is it a never-ending battle to maintain?  Are
> trading
> partners vastly different in reference to the correspondence your
> trying
> to capture?  I sorry if I sound confused.  It is because I am.  This
> is
> a daunting task where I don't seem to know quite where to begin.  I
> thank all of those that help in advance.
>
> --
> woof woof,
> Patrick Thrapp    http://www.wolfenet.com/~pthrapp
> Ignorance is curable.  Stupidity is for life.

ATOM RSS1 RSS2