Design C# program to generate text file compatible with ANSI X12 837 standard for EDI

Design C# Program With The Following Requirements: A program to take information from a database with several input tables, map the fields from the input tables to fields in an output table and generate a text file using the names of the fields on the output table combined with the data coming from the input tables. EDI (Electronic Data Interchange) 837 is a standard created by ANSI called X12 837. This standard is used to transmit medical billing information to insurance carriers. It takes information from a table or multiple tables, such as patients names, last names, address, insurance company, doctor who saw the patient, procedure performed on the patient, dates, etc. All this information is placed in the text file with specific codes and the file is prepared to be sent to the insurance company. Programmer must research the standard to understand it. There will be 20 Input tables in the input database, named table 1, table 2, ..... thru table 20. Each table will contain 20 columns labeled Field 1, Field 2, ..... thru Field 20. The type of data to be contained by the fields will be String (Text) There will be an output table in the database called EDI 837 records. The program will take data from the 20 input tables, map/associate it with a code coming from the ANSI X12 837 Standard and place the data from the input tables into the output tables field accordingly. Ex.: Table 1 Contains Field 8 which holds information Billing Provider Address X12 837 Specifications defines 2010AA N3: Street Address Of Billing Provider Translation table should contain a relation between Table 1 Field 8 and Output Table Field 2010AAN3. When the text file is generated, the text file should have the info 2010AAN3StreetAddressOfBillingProvider. Output table must contain all variables listed in X12 837 specification. These variables will get filled up depending on the data in the input tables. Mappings should be saved with a name. Ex. Mapping/Association of Table 1 Field 8 to Output table field 2010AAN3 can be saved and assigned a name. In other cases Table 1 Field 8 can be associated to a different field in Output table and this Mapping/Association table should be saved with a different name. There will be a text file generated from the results of the Mapping table. This text file will come from the results of running the Translation Table. The resulting record will be saved to the Output table and a text file matching the EDI standard for X12 837 should be generated. The final result consists of two parts. Part one.- A program to perform what was described. Program with GUI to used manually by end user Part two.- A DLL to be used with a C# program. DLL must have the methods and procedures needed to accept information passed on to it from another C# application and output information to the same. You can view examples of these files in the following documents (use at your own risk) We are not associated to any of these organizations and cannot distribute their information. Links are mentioned here for illustration only. The Evolution of the ANSI ASC X12N 837 format from the UB-92 Flat file format Page 8 [login to view URL] Company specific - Not affiliated to this company - For instructional use only - BCBSNC Companion Guide to X12 5010 Transactions – 837 Institutional Health Care Claims v.1.1 Page 14 [login to view URL] Company specific - Not affiliated to this company - For instructional use only - 837 Professional EDI Specifications & Companion Guide [login to view URL] Sparcs From New York State Dept Of Health X12-837 INPUT DATA SPECIFICATIONS 2011 [login to view URL]