Rachel,

Mine was basically an 820 file about payments made.
Basically I import the text file into a temporary table
and then run a cursor through the table to strip out the
data into the proper columns.

Jan
 


-----Original Message-----
From: "Rachael Malberg" <[email protected]>
To: [email protected] (RBASE-L Mailing List)
Date: Thu, 26 Feb 2009 08:15:44 -0600
Subject: [RBASE-L] - Re: General EDI question


EDI stands for Electronic Data Interchange (ie take data from one database, 
plop it into a text file, and then suck that file into (import) an other 
database) .  The text file data is in some sort of format (tab delimited, 
fixed width, comma seperated with a double quote text qualifier (the csv 
type), and so on.. and the fields will be in a strict order and often they 
have data formats for dates (yyyy/mm/dd or dd-m-yy or some other odd combo), 
numbers, names, address, what ever the primary system defines (if you can be 
that primary system more power to you). 
 
Also they may require header or footer infomation letting the system know 
how many records they are importing and where they came from.  To me the 
ickiest part of some EDIs (like Jan's 820 and 852 which are from insurance 
co's regarding claims) is you may only need to send/load 50 fields of data 
but the EDI file spec calls for 800 fields which means you need to 
create/import an EDI file with 800 fields written to it.  So you have 
understand what all 800 fields are and which 50 you will actually include 
data you have/need.
 
So I too have been requested to add a process to import and process an 820 
for a DME (which is sometimes call an EOB) but it is a file from an 
insurance co telling a provider how much they have paid, denied, and 
adjusted and was wondering Jan if you've already done that fun, would you 
mind sharing?
 
~Rach
----- Original Message ----- 
From: jan johansen 
To: RBASE-L Mailing List 
Sent: Wednesday, February 25, 2009 8:07 PM
Subject: [RBASE-L] - Re: General EDI question



Karen, 
I created a routine in 7.6 last year for a client to input 
EDI types 820 and 852. 
However, that being said, each company seems to have 
their own "standard" so I'm not sure there is a universal one. 
Jan 

Reply via email to