// Specify SEF file to load. oschema = (edischema) oedidoc.loadschema(spath + sseffilename, SchemaTypeIDConstants. Schema_Standard_Exchange_Format);
|
|
- Christopher Wood
- 5 years ago
- Views:
Transcription
1 using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; using Edidev.FrameworkEDI; 1 namespace csharp_tran70x279a1 public partial class frmtran279 : Form public frmtran279() InitializeComponent(); private void btntranslate_click(object sender, EventArgs e) edidocument oedidoc; edischema oschema; edischemas oschemas; edidatasegment osegment; string ssegmentid = ""; string sloopsection = ""; int narea = 0; string shlcode = ""; string svalue = ""; string sqlfr = ""; string spath = AppDomain.CurrentDomain.BaseDirectory; string sedifilename = "270_005010X279A1.X12"; string sseffilename = "270_005010X279A1.SemRef.EVAL0.SEF"; //EVALUATION SEF FILE // Create the top level application object "edidocument". oedidoc = new edidocument(); // This makes certain that Framework EDI only uses the SEF file provided, // and that it does not use its built in Standard Reference table to translate // the EDI document oschemas = (edischemas) oedidoc.getschemas(); oschemas.enablestandardreference = false; // The FORWARD ONLY cursor increases the performance of processing the EDI // document (see Technical Note 3 below). oedidoc.cursortype = DocumentCursorTypeConstants.Cursor_ForwardOnly; // Specify SEF file to load. oschema = (edischema) oedidoc.loadschema(spath + sseffilename, SchemaTypeIDConstants. Schema_Standard_Exchange_Format); // Specify EDI document to read. oedidoc.loadedi(spath + sedifilename); // Gets the first data segment in the EDI document. osegment = (edidatasegment) oedidoc.firstdatasegment; // Loop that will traverse through the EDI document from top to bottom. This // is required for FORWARD ONLY cursor. while (osegment!= null) // Data segments are uniquely identified by their segment Identifier (ID). // The loop section and the area (or table) properties of the data segment
2 // are read for each iteration of the loop. ssegmentid = osegment.id; sloopsection = osegment.loopsection; narea = osegment.area; 2 Qualifier (I01) (I02) Qualifier (I03) (I05) (I05) (I07) Number (I11) (I12) (I13) (I15) if (narea == 0) // Data segments that are not designated an area (i.e. area = 0) // are control segments that are part of the Interchange or // Functional Group envelopes, and are not part of the Transaction Set. if (ssegmentid == "ISA") svalue = osegment.get_dataelementvalue(1, 0); svalue = osegment.get_dataelementvalue(3, 0); svalue = osegment.get_dataelementvalue(4, 0); svalue = osegment.get_dataelementvalue(5, 0); svalue = osegment.get_dataelementvalue(6, 0); svalue = osegment.get_dataelementvalue(7, 0); svalue = osegment.get_dataelementvalue(8, 0); svalue = osegment.get_dataelementvalue(9, 0); svalue = osegment.get_dataelementvalue(10, 0); svalue = osegment.get_dataelementvalue(11, 0); svalue = osegment.get_dataelementvalue(12, 0); svalue = osegment.get_dataelementvalue(13, 0); // Authorization Information // Authorization Information // Security Information // Security Information (I04) // Interchange ID Qualifier // Interchange Sender ID (I06) // Interchange ID Qualifier // Interchange Receiver ID // Interchange Date (I08) // Interchange Time (I09) // Repetition Separator (I65) // Interchange Control Version // Interchange Control Number listbox1.items.add("interchange Control Number: " + svalue); svalue = osegment.get_dataelementvalue(14, 0); // Acknowledgment Requested svalue = osegment.get_dataelementvalue(15, 0); svalue = osegment.get_dataelementvalue(16, 0); // Usage Indicator (I14) // Component Element Separator else if (ssegmentid == "IEA") svalue = osegment.get_dataelementvalue(1, 0); Functional Groups (I16) (I12) // Number of Included // Interchange Control Number (479) (142) (124) (455) else if (ssegmentid == "GS") svalue = osegment.get_dataelementvalue(1, 0); svalue = osegment.get_dataelementvalue(3, 0); // Functional Identifier Code // Application Sender's Code // Application Receiver's Code svalue = osegment.get_dataelementvalue(4, 0); // Date (373) svalue = osegment.get_dataelementvalue(5, 0); // Time (337) svalue = osegment.get_dataelementvalue(6, 0); // Group Control Number (28) listbox1.items.add("group Control Number: " + svalue); svalue = osegment.get_dataelementvalue(7, 0); // Responsible Agency Code svalue = osegment.get_dataelementvalue(8, 0); // Version / Release / Industry
3 Identifier Code (480) 3 Included (97) else if (ssegmentid == "GE") svalue = osegment.get_dataelementvalue(1, 0); // Number of Transaction Sets // Group Control Number (28) // ssegmentid == "GE" else if (narea == 1) // Data segments in area 1 are processed here. if (sloopsection == "") if (ssegmentid == "ST") // Transaction Set Header svalue = osegment.get_dataelementvalue(1, 0); // Transaction Set Identifier Code (143) // Transaction Set Control Number (329) listbox1.items.add("transaction Set Control Number: " + svalue); svalue = osegment.get_dataelementvalue(3, 0); // Implementation Convention Reference (1705) Code (1005) Code (353) (640) else if (ssegmentid == "BHT") // Beginning of Hierarchical Transaction svalue = osegment.get_dataelementvalue(1, 0); // Hierarchical Structure svalue = osegment.get_dataelementvalue(3, 0); // Transaction Set Purpose // Reference Identification listbox1.items.add("submitter Transaction Identification: " + svalue); svalue = osegment.get_dataelementvalue(4, 0); // Date (373) svalue = osegment.get_dataelementvalue(5, 0); // Time (337) svalue = osegment.get_dataelementvalue(6, 0); // Transaction Type Code // ssegmentid == "BHT" // sloopsection == "" else if (narea == 2) // Data segments in area 2 are processed here. if (sloopsection == "") Segments (96) Number (329) if (ssegmentid == "SE") // Transaction Set Trailer svalue = osegment.get_dataelementvalue(1, 0); // Number of Included // Transaction Set Control // ssegmentid == "SE"
4 4 else // // The semantic meaning of the loop "HL" is dependent on the value of the // code qualifier in data element "735" of the data segment "HL". The value // of the qualifier has the following semantic meaning for the loop: // "20" INFORMATION SOURCE // "21" INFORMATION RECEIVER // "22" SUBSCRIBER // "23" DEPENDENT // if (sloopsection == "HL" && ssegmentid == "HL") (735) shlcode = osegment.get_dataelementvalue(3, 0); // sloopsection == "HL" && ssegmentid == "HL" if (shlcode == "20") // Information Source Detail Proc_270_Area_2_Loop_Hl2000A(oSegment); else if (shlcode == "21") // Information Receiver Detail Proc_270_Area_2_Loop_Hl2000B(oSegment); else if (shlcode == "22") // Subscriber Detail Proc_270_Area_2_Loop_Hl2000C(oSegment); else if (shlcode == "23") // Dependent Detail Proc_270_Area_2_Loop_Hl2000D(oSegment); // shlcode == "23" // // narea == 2 // Get the next data segment in the document. edidatasegment.set(ref osegment, osegment.next()); // osegment!= null // Hierarchical Level Code // Destroy objects. Not required because objects are automatically destroyed // when the procedure goes off scope. oschema.dispose(); oschemas.dispose(); oedidoc.dispose(); MessageBox.Show("Done"); //btntranslate_click
5 5 // ***************************** // * Information Source Detail * // ***************************** void Proc_270_Area_2_Loop_Hl2000A(ediDataSegment osegment) string svalue = ""; string sloopsection = osegment.loopsection; string ssegmentid = osegment.id; (734) if (sloopsection == "HL") //2000A INFORMATION SOURCE LEVEL if (ssegmentid == "HL") // Information Source Level svalue = osegment.get_dataelementvalue(1, 0); // Hierarchical ID Number (628) // Hierarchical Parent ID Number svalue = osegment.get_dataelementvalue(3, 0); // Hierarchical Level Code (735) svalue = osegment.get_dataelementvalue(4, 0); // Hierarchical Child Code (736) // ssegmentid == "HL" (1035) (66) else if (sloopsection == "HL;NM1") // 2100A INFORMATION SOURCE NAME if (ssegmentid == "NM1") // Information Source Name svalue = osegment.get_dataelementvalue(1, 0); // Entity Identifier Code (98) // Entity Type Qualifier (1065) svalue = osegment.get_dataelementvalue(3, 0); // Name Last or Organization Name listbox1.items.add("information Source Name: " + svalue); svalue = osegment.get_dataelementvalue(4, 0); // Name First (1036) svalue = osegment.get_dataelementvalue(5, 0); // Name Middle (1037) svalue = osegment.get_dataelementvalue(6, 0); // Name Prefix (1038) svalue = osegment.get_dataelementvalue(7, 0); // Name Suffix (1039) svalue = osegment.get_dataelementvalue(8, 0); // Identification Code Qualifier svalue = osegment.get_dataelementvalue(9, 0); // Identification Code (67) // ssegmentid == "NM1" // sloopsection // Proc_270_Area_2_Loop_Hl2000A // ******************************* // * Information Receiver Detail * // ******************************* void Proc_270_Area_2_Loop_Hl2000B(ediDataSegment osegment) string svalue = ""; string sloopsection = osegment.loopsection; string ssegmentid = osegment.id; string sqlfr = ""; (734) if (sloopsection == "HL") // 2000B INFORMATION RECEIVER LEVEL if (ssegmentid == "HL") // Information Receiver Level svalue = osegment.get_dataelementvalue(1, 0); // Hierarchical ID Number (628) // Hierarchical Parent ID Number
6 svalue = osegment.get_dataelementvalue(3, 0); // Hierarchical Level Code (735) svalue = osegment.get_dataelementvalue(4, 0); // Hierarchical Child Code (736) 6 // ssegmentid == "HL" else if (sloopsection == "HL;NM1") // 2100B INFORMATION RECEIVER NAME (1035) (66) if (ssegmentid == "NM1") // Information Receiver Name svalue = osegment.get_dataelementvalue(1, 0); // Entity Identifier Code (98) // Entity Type Qualifier (1065) svalue = osegment.get_dataelementvalue(3, 0); // Name Last or Organization Name listbox1.items.add("information Receiver Name: " + svalue); svalue = osegment.get_dataelementvalue(4, 0); // Name First (1036) svalue = osegment.get_dataelementvalue(5, 0); // Name Middle (1037) svalue = osegment.get_dataelementvalue(6, 0); // Name Prefix (1038) svalue = osegment.get_dataelementvalue(7, 0); // Name Suffix (1039) svalue = osegment.get_dataelementvalue(8, 0); // Identification Code Qualifier svalue = osegment.get_dataelementvalue(9, 0); // Identification Code (67) else if (ssegmentid == "REF") // Information Receiver Additional Identification svalue = osegment.get_dataelementvalue(1, 0); // Reference Identification // Reference Identification else if (ssegmentid == "N3") // Information Receiver Address Information svalue = osegment.get_dataelementvalue(1, 0); // Address Information (166) // Address Information (166) else if (ssegmentid == "N4") // Information Receiver Geographic Location svalue = osegment.get_dataelementvalue(1, 0); // City Name (19) // State or Province Code (156) svalue = osegment.get_dataelementvalue(3, 0); // Postal Code (116) svalue = osegment.get_dataelementvalue(4, 0); // Country Code (26) svalue = osegment.get_dataelementvalue(7, 0); // Country Subdivision Code (1715) else if (ssegmentid == "PRV") // Information Receiver Provider Information svalue = osegment.get_dataelementvalue(1, 0); // Provider Code (1221) // Reference Identification svalue = osegment.get_dataelementvalue(3, 0); // Reference Identification // ssegmentid == "PRV" // sloopsection == "HL;NM1" // Proc_270_Area_2_Loop_Hl2000B // ********************* // * Subscriber Detail * // *********************
7 void Proc_270_Area_2_Loop_Hl2000C(ediDataSegment osegment) string svalue = ""; string sloopsection = osegment.loopsection; string ssegmentid = osegment.id; string sqlfr = ""; 7 (734) (509) if (sloopsection == "HL") // 2000C SUBSCRIBER LEVEL if (ssegmentid == "HL") // Subscriber Level svalue = osegment.get_dataelementvalue(1, 0); // Hierarchical ID Number (628) // Hierarchical Parent ID Number svalue = osegment.get_dataelementvalue(3, 0); // Hierarchical Level Code (735) svalue = osegment.get_dataelementvalue(4, 0); // Hierarchical Child Code (736) else if (ssegmentid == "TRN") // Subscriber Trace svalue = osegment.get_dataelementvalue(1, 0); // Trace Type Code (481) // Reference Identification listbox1.items.add("trace Assigning Entity Identification: " + svalue); svalue = osegment.get_dataelementvalue(3, 0); // Originating Company Identifier svalue = osegment.get_dataelementvalue(4, 0); // Reference Identification // ssegmentid == "TRN" (1035) (66) else if (sloopsection == "HL;NM1") // 2100C SUBSCRIBER NAME if (ssegmentid == "NM1") // Subscriber Name svalue = osegment.get_dataelementvalue(1, 0); // Entity Identifier Code (98) // Entity Type Qualifier (1065) svalue = osegment.get_dataelementvalue(3, 0); // Name Last or Organization Name listbox1.items.add("subscriber Name: " + svalue); svalue = osegment.get_dataelementvalue(4, 0); // Name First (1036) svalue = osegment.get_dataelementvalue(5, 0); // Name Middle (1037) svalue = osegment.get_dataelementvalue(6, 0); // Name Prefix (1038) svalue = osegment.get_dataelementvalue(7, 0); // Name Suffix (1039) svalue = osegment.get_dataelementvalue(8, 0); // Identification Code Qualifier svalue = osegment.get_dataelementvalue(9, 0); // Identification Code (67) else if (ssegmentid == "REF") // Subscriber Additional Identification sqlfr = osegment.get_dataelementvalue(1, 0); // Reference Identification if (sqlfr == "18") // Plan Number // Reference Identification listbox1.items.add("subscriber Plan Number: " + svalue); else if (sqlfr == "1L") // Group or Policy Number // Reference Identification
8 listbox1.items.add("subscriber Group or Policy Number: " + svalue); 8 else if (ssegmentid == "N3") // Subscriber Address Information svalue = osegment.get_dataelementvalue(1, 0); // Address Information (166) // Address Information (166) else if (ssegmentid == "N4") // Subscriber Geographic Location svalue = osegment.get_dataelementvalue(1, 0); // City Name (19) // State or Province Code (156) svalue = osegment.get_dataelementvalue(3, 0); // Postal Code (116) svalue = osegment.get_dataelementvalue(4, 0); // Country Code (26) svalue = osegment.get_dataelementvalue(7, 0); // Country Subdivision Code (1715) else if (ssegmentid == "PRV") // Subscriber Provider Information svalue = osegment.get_dataelementvalue(1, 0); // Provider Code (1221) // Reference Identification svalue = osegment.get_dataelementvalue(3, 0); // Reference Identification else if (ssegmentid == "DMG") // Subscriber Demographic Information svalue = osegment.get_dataelementvalue(1, 0); // Date Time Period Format // Birth Date listbox1.items.add("subscriber Birth Date: " + svalue); svalue = osegment.get_dataelementvalue(3, 0); // Gender Code (1068) listbox1.items.add("subscriber Gender: " + svalue); Code (1073) (1069) else if (ssegmentid == "INS") // Multiple Birth Sequence Number svalue = osegment.get_dataelementvalue(1, 0); // Yes/No Condition or Response // Individual Relationship Code svalue = osegment.get_dataelementvalue(17, 0); // Number (1470) else if (ssegmentid == "HI") // Subscriber Health Care Diagnosis Code svalue = osegment.get_dataelementvalue(1, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(1, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(2, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(2, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(3, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(3, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(4, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(4, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(5, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(5, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(6, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(6, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(7, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(7, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(8, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(8, 2); // Industry Code (1271)
9 else if (ssegmentid == "DTP") // Subscriber Date svalue = osegment.get_dataelementvalue(1, 0); // Date/Time Qualifier (374) // Date Time Period Format svalue = osegment.get_dataelementvalue(3, 0); // Date Time Period (1251) listbox1.items.add("subscriber Date: " + svalue); 9 // ssegmentid == "DTP" else if (sloopsection == "HL;NM1;EQ") // 2110C SUBSCRIBER ELIGIBILITY OR BENEFIT INQUIRY (235) if (ssegmentid == "EQ") // Subscriber Eligibility or Benefit Inquiry svalue = osegment.get_dataelementvalue(1, 0); // Service Type Code (1365) svalue = osegment.get_dataelementvalue(2, 1); // Product/Service ID Qualifier listbox1.items.add("service Qualifier: " + svalue); svalue = osegment.get_dataelementvalue(2, 2); // Product/Service ID (234) listbox1.items.add("procedure Code: " + svalue); svalue = osegment.get_dataelementvalue(2, 3); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(2, 4); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(2, 5); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(2, 6); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(3, 0); // Coverage Level Code (1207) svalue = osegment.get_dataelementvalue(5, 1); // Diagnosis Code Pointer (1328) svalue = osegment.get_dataelementvalue(5, 2); // Diagnosis Code Pointer (1328) svalue = osegment.get_dataelementvalue(5, 3); // Diagnosis Code Pointer (1328) svalue = osegment.get_dataelementvalue(5, 4); // Diagnosis Code Pointer (1328) else if (ssegmentid == "AMT") sqlfr = osegment.get_dataelementvalue(1, 0); // Amount Qualifier Code (522) if (sqlfr == "R") // Subscriber Spend Down Amount listbox1.items.add("subscriber Spend Down Amount: " + svalue); Billed Amount else if (sqlfr == "PB") // Subscriber Spend Down Total listbox1.items.add("subscriber Spend Down Total Billed Amount: " + svalue); Information else if (ssegmentid == "III") // Subscriber Eligibility or Benefit Additional Inquiry svalue = osegment.get_dataelementvalue(1, 0); // Code List Qualifier Code (1270) // Industry Code (1271) listbox1.items.add("subscriber Eligibility Category Code: " + svalue); else if (ssegmentid == "REF") // Subscriber Additional Identification sqlfr = osegment.get_dataelementvalue(1, 0); // Reference Identification
10 if (sqlfr == "9F") //Referral Number // Reference Identification listbox1.items.add("referral Number: " + svalue); else if (sqlfr == "G1") //Prior Authorization Number // Reference Identification listbox1.items.add("prior Authorization Number: " + svalue); 10 else if (ssegmentid == "DTP") // Subscriber Eligibility/Benefit Date sqlfr = osegment.get_dataelementvalue(1, 0); // Date/Time Qualifier (374) if (sqlfr == "102") //Isuue // Date Time Period Format svalue = osegment.get_dataelementvalue(3, 0); // Date Time Period (1251) listbox1.items.add("subscriber Eligibility Issue Date: " + svalue); else if (sqlfr == "291") //Plan // Date Time Period Format svalue = osegment.get_dataelementvalue(3, 0); // Date Time Period (1251) listbox1.items.add("subscriber Eligibility Plan Date" + svalue); // ssegmentid == "DTP" // sloopsection == "HL;NM1;EQ" // Proc_270_Area_2_Loop_Hl2000C // ******************** // * Dependent Detail * // ******************** void Proc_270_Area_2_Loop_Hl2000D(ediDataSegment osegment) string svalue = ""; string sloopsection = osegment.loopsection; string ssegmentid = osegment.id; string sqlfr = ""; if (sloopsection == "HL") // 2000D DEPENDENT LEVEL (734) if (ssegmentid == "HL") // Dependent Level svalue = osegment.get_dataelementvalue(1, 0); // Hierarchical ID Number (628) // Hierarchical Parent ID Number svalue = osegment.get_dataelementvalue(3, 0); // Hierarchical Level Code (735) svalue = osegment.get_dataelementvalue(4, 0); // Hierarchical Child Code (736) else if (ssegmentid == "TRN") // Dependent Trace
11 (509) svalue = osegment.get_dataelementvalue(1, 0); // Trace Type Code (481) // Reference Identification listbox1.items.add("dependent Trace No: " + svalue); svalue = osegment.get_dataelementvalue(3, 0); // Originating Company Identifier svalue = osegment.get_dataelementvalue(4, 0); // Reference Identification // ssegmentid == "TRN" 11 else if (sloopsection == "HL;NM1") // 2100D DEPENDENT NAME (1035) if (ssegmentid == "NM1") // Dependent Name svalue = osegment.get_dataelementvalue(1, 0); // Entity Identifier Code (98) // Entity Type Qualifier (1065) svalue = osegment.get_dataelementvalue(3, 0); // Name Last or Organization Name svalue = osegment.get_dataelementvalue(4, 0); // Name First (1036) listbox1.items.add("dependent Name: " + svalue); svalue = osegment.get_dataelementvalue(5, 0); // Name Middle (1037) svalue = osegment.get_dataelementvalue(6, 0); // Name Prefix (1038) svalue = osegment.get_dataelementvalue(7, 0); // Name Suffix (1039) else if (ssegmentid == "REF") // Dependent Additional Identification sqlfr = osegment.get_dataelementvalue(1, 0); // Reference Identification if (sqlfr == "18") // Plan Number // Reference Identification listbox1.items.add("dependent Plan Number: " + svalue); else if (sqlfr == "1L") // Group or Policy Number // Reference Identification listbox1.items.add("dependent Group or Policy Number: " + svalue); else if (ssegmentid == "N3") // Dependent Address Information svalue = osegment.get_dataelementvalue(1, 0); // Address Information (166) // Address Information (166) else if (ssegmentid == "N4") // Dependent Geographic Location svalue = osegment.get_dataelementvalue(1, 0); // City Name (19) // State or Province Code (156) svalue = osegment.get_dataelementvalue(3, 0); // Postal Code (116) svalue = osegment.get_dataelementvalue(4, 0); // Country Code (26) svalue = osegment.get_dataelementvalue(7, 0); // Country Subdivision Code (1715) else if (ssegmentid == "PRV") // Dependent Provider Information
12 svalue = osegment.get_dataelementvalue(1, 0); // Provider Code (1221) // Reference Identification svalue = osegment.get_dataelementvalue(3, 0); // Reference Identification else if (ssegmentid == "DMG") // Dependent Demographic Information svalue = osegment.get_dataelementvalue(1, 0); // Date Time Period Format // Birth Date listbox1.items.add("dependent Birth Date: " + svalue); svalue = osegment.get_dataelementvalue(3, 0); // Gender Code (1068) listbox1.items.add("dependent Gender: " + svalue); 12 Code (1073) (1069) else if (ssegmentid == "INS") // Dependent Relationship svalue = osegment.get_dataelementvalue(1, 0); // Yes/No Condition or Response // Individual Relationship Code listbox1.items.add("dependent Relationship: " + svalue); svalue = osegment.get_dataelementvalue(17, 0); // Number (1470) else if (ssegmentid == "HI") // Dependent Health Care Diagnoses Codes svalue = osegment.get_dataelementvalue(1, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(1, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(2, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(2, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(3, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(3, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(4, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(4, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(5, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(5, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(6, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(6, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(7, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(7, 2); // Industry Code (1271) svalue = osegment.get_dataelementvalue(8, 1); // Code List Qualifier Code (1270) svalue = osegment.get_dataelementvalue(8, 2); // Industry Code (1271) else if (ssegmentid == "DTP") // Dependent Date svalue = osegment.get_dataelementvalue(1, 0); // Date/Time Qualifier (374) // Date Time Period Format svalue = osegment.get_dataelementvalue(3, 0); // Date Time Period (1251) // ssegmentid == "DTP" else if (sloopsection == "HL;NM1;EQ") // 2110D DEPENDENT ELIGIBILITY OR BENEFIT INQUIRY (235) if (ssegmentid == "EQ") // Dependent Eligibility or Benefit Inquiry svalue = osegment.get_dataelementvalue(1, 0); // Service Type Code (1365) listbox1.items.add("dependent Benefit Service Type Code: " + svalue); svalue = osegment.get_dataelementvalue(2, 1); // Product/Service ID Qualifier
13 Information svalue = osegment.get_dataelementvalue(2, 2); // Product/Service ID (234) svalue = osegment.get_dataelementvalue(2, 3); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(2, 4); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(2, 5); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(2, 6); // Procedure Modifier (1339) svalue = osegment.get_dataelementvalue(5, 1); // Diagnosis Code Pointer (1328) svalue = osegment.get_dataelementvalue(5, 2); // Diagnosis Code Pointer (1328) svalue = osegment.get_dataelementvalue(5, 3); // Diagnosis Code Pointer (1328) svalue = osegment.get_dataelementvalue(5, 4); // Diagnosis Code Pointer (1328) else if (ssegmentid == "III") // Dependent Eligibility or Benefit Additional Inquiry svalue = osegment.get_dataelementvalue(1, 0); // Code List Qualifier Code (1270) // Industry Code (1271) else if (ssegmentid == "REF") // Dependent Additional Identification svalue = osegment.get_dataelementvalue(1, 0); // Reference Identification // Reference Identification else if (ssegmentid == "DTP") // Dependent Eligibility/Benefit Date svalue = osegment.get_dataelementvalue(1, 0); // Date/Time Qualifier (374) // Date Time Period Format svalue = osegment.get_dataelementvalue(3, 0); // Date Time Period (1251) // ssegmentid == "DTP" // sloopsection 13 // Proc_270_Area_2_Loop_Hl2000D
namespace csharp_gen837x223a2 { public partial class Form1 : Form { public Form1() { InitializeComponent(); }
using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Text; using System.Windows.Forms; using Edidev.FrameworkEDI; 1 namespace
More informationnamespace Gen837X222A1 { public partial class Form1 : Form { public Form1() { InitializeComponent(); }
using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Text; using System.Windows.Forms; using Edidev.FrameworkEDI; 1 namespace
More informationstring spath; string sedifile = "277_005010X228.X12"; string sseffile = "277_005010X228.SemRef.EVAL0.SEF";
using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Text; using System.Windows.Forms; using Edidev.FrameworkEDI; 1 namespace
More informationnamespace csharp_gen277x214 { public partial class Form1 : Form { public Form1() { InitializeComponent(); }
using System using System.Collections.Generic using System.ComponentModel using System.Data using System.Drawing using System.Text using System.Windows.Forms using Edidev.FrameworkEDI 1 namespace csharp_gen277x214
More informationC:\EDIdEv\Examples\HIPAA\5010\VbNet\vbNet_Tran834X220A1\Form1.vb Imports Edidev.FrameworkEDI
Imports Edidev.FrameworkEDI 1 Public Class Form1 Private Sub btntranslate_click(byval sender As System.Object, ByVal e As System.EventArgs) Handles btntranslate.click Dim oedidoc As edidocument Dim oschemas
More informationprivate string sconnection = ConfigurationManager.ConnectionStrings["Development"].ConnectionString
using System; using System.Configuration; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Data.SqlClient; using System.Drawing; using System.Text; using System.Windows.Forms;
More informationprivate string sconnection = ConfigurationManager.ConnectionStrings["Development"].ConnectionString
using System; using System.Configuration; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Data.SqlClient; using System.Drawing; using System.Text; using System.Windows.Forms;
More information// Specify SEF file to load. edischema oschema = oedidoc.loadschema(spath + sseffilename, SchemaTypeIDConstants. Schema_Standard_Exchange_Format);
using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms; using Edidev.FrameworkEDIx64;
More informationC:\EDIdEv\Examples\HIPAA\5010\VbNet\vbNet_Gen834X220A1\Form1.vb Imports Edidev.FrameworkEDI
Imports Edidev.FrameworkEDI 1 Public Class Form1 Private Sub btngenerate_click(byval sender As System.Object, ByVal e As System.EventArgs) Handles btngenerate.click Dim oedidoc As edidocument Dim oschemas
More informationC:\EDIdEv\Examples\HIPAA\5010\VbNet\vbNet_Gen837X222A1\Form1.vb Imports Edidev.FrameworkEDI
Imports Edidev.FrameworkEDI 1 Public Class Form1 Private Sub btngenerate_click(byval sender As System.Object, ByVal e As System.EventArgs) Handles btngenerate.click Dim oedidoc As edidocument Dim oschemas
More informationC:\EDIdEv\Examples\HIPAA\5010\VbNet\vbNet_Gen277X214\Form1.vb Imports Edidev.FrameworkEDI
Imports Edidev.FrameworkEDI 1 Public Class Form1 Private Sub btngenerate_click(byval sender As System.Object, ByVal e As System.EventArgs) Handles btngenerate.click Dim oedidoc As edidocument Dim oschema
More information270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response
Companion Document 270/271 270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Basic Instructions This section provides information to help you prepare for the ANSI ASC X12.281 Eligibility,
More informationC:\EDIdEv\Examples\HIPAA\5010\VbNet\vbNet_Gen835X221A1\Form1.vb Imports Edidev.FrameworkEDI
Imports Edidev.FrameworkEDI 1 Public Class Form1 Private Sub btngenerate_click(byval sender As System.Object, ByVal e As System.EventArgs) Handles btngenerate.click Dim oedidoc As edidocument Dim oschemas
More information270/271 Companion Document ASC X12N. Health Care Eligibility and Benefit Inquiry and Response Version 4010A1 Addenda October 2002
Purpose of This Document 270/271 Companion Document ASC N Health Care Eligibility and Benefit Inquiry and Response Version 4010A1 Addenda October 2002 This companion guide has been written to assist those
More informationRefers to the Technical Reports Type 3 Based on ASC X12 version X /277 Health Care Claim Status Inquiry and Response
HIPAA Transaction Standard Companion Guide For Availity Health Information Network Users Refers to the Technical Reports Type 3 Based on ASC X12 version 005010X212 276/277 Health Care Claim Status Inquiry
More informationIntegration Guide for Data Originators of Claim Status. Version 1.1
Integration Guide for Data Originators of Claim Status Version 1.1 December 23, 2010 Integration Guide for Data Originators of Claim Status Revision History Date Version Description Author November 25,
More informationCabinet for Health and Family Services Department for Medicaid Services
KyHealth Choices 277 Health Care Payer Unsolicited Claim Status (ASC X12N 277) Companion Guide Version 2.3 Version 003070 Cabinet for Health and Family Services Department for Medicaid Services August
More informationVendor Specifications 270/271 Eligibility Benefit Inquiry and Response ASC X12N Version for. State of Idaho MMIS
Vendor Specifications 270/271 Eligibility Benefit Inquiry and Response ASC X12N Version 5010 for State of Idaho MMIS Date of Publication: 7/27/2017 Document : TL419 Version: 8.0 Revision History Version
More informationSHARES 837P Companion Guide
SHARES 837P Companion Guide Contents Introduction... 2 SHARES 837 Guidelines... 2 SHARES Interchange Requirements... 2 Transaction Segment Delimiters and Terminators... 2 Claim Matching... 2 Service Line
More informationHIPAA 276/277 Companion Guide Cardinal Innovations Prepared for Health Care Providers
Cardinal Innovations Prepared for Health Care Providers, February 2017 Table of Contents Preface... 4 1. Transaction Instruction (TI) Introduction... 5 1.1 Scope... 5 1.2 Overview... 5 1.3 References...
More informationUSVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270
USVI HEALTH ELIGIBILITY/BENEFIT INQUIRY 5010 Companion Guide 270 Date of Publication: 12/04/2012 Version: 1.1 DISCLAIMER The DXC Technology Companion Guide for USVI Medicaid is subject to change prior
More information276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions
Companion Document 276/277 276/277 Health Care Claim Status Request/ Response Real-Time This companion document is for informational purposes only to describe certain aspects and expectations regarding
More information816 Organizational Relationships
816 Organizational Relationships Functional Group ID=OR Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction
More information276 Health Care Claim Status Request Educational Guide
276 Health Care Claim Status Request Educational Guide June 2010 - Version 1.1 Disclaimer INGENIX is still under development stages and frequent changes within this document are expected. This documentation
More informationWest Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270
West Virginia HEALTH ELIGIBILITY/BENEFIT INQUIRY Companion Guide 270 Date of Publication: 01/01/2014 Document Number: Version: 2.0 DISCLAIMER The Molina Healthcare Companion Guide for West Virginia is
More information270/271 Benefit Eligibility Inquiry/Response Transactions Companion Guide ANSI ASC X12N 270/271 (Version 4010A)
270/271 Benefit Eligibility Inquiry/Response Transactions ANSI ASC X12N 270/271 (Version 4010A) State of Washington Department of Social & Health Services Prepared by: CNSI 3000 Pacific Avenue S.E. Suite
More informationUnsolicited 277 Trading Partner Specification
Unsolicited 277 Trading Partner Specification Revision Summary: Revision Date Summary of Changes Number 1.0 3/20/2007 NPI changes in loop 2100C AmeriHealth U277 Unsolicited Health Care Claim Status Notification
More information278 Health Care Service Review and Response
278 Health Care Service Review and Response Overview 2 Blue Card Inquiries (Blue Exchange) 2 Health Care Services Review Processing 2 Frequency of Data Exchange 2 Acknowledgements 2 Data Retention 3 Batch
More informationPennsylvania PROMISe Companion Guide
Pennsylvania Companion Guide Unsolicited 277 Claim Response Version 5010 September 2010 Version 1 Pennsylvania PROMISe Unsolicited 277 Claim Companion Guide This page intentionally left blank. September
More information276/ /277 Health Care Claim Status Request and Response Real-Time. Basic Instructions. Companion Document
Companion Document 276/277 276/277 Health Care Claim Status Request and Response Real-Time Basic Instructions This section provides information to help you prepare for the ANSI ASC X12.316 Health Care
More information276/277 Health Care Claim Status Request/ Response Real-Time. Section 1 276/277 Claim Status Request/Response: Basic Instructions
Companion Document 276/277 276/277 Health Care Claim Status Request/ Response Real-Time This companion document is for informational purposes only to describe certain aspects and expectations regarding
More information/277 Companion Guide. Refers to the Implementation Guides Based on X12 version Companion Guide Version Number: 1.1
5010 276/277 Companion Guide Refers to the Implementation Guides Based on X12 version 005010 Companion Guide Version Number: 1.1 November 26, 2012 1 Disclosure It is the sole responsibility of the provider/vendor
More informationIt is recommended that separate transaction sets be used for different patients.
ASC X12N 278 (004010X094A1) Health Care Services Request For Review And Response Companion Guide Notes The ISA segment terminator, which immediately follows the component element separator, must consist
More informationWest Virginia HMO Rosters Companion Guide 834
West Virginia HMO Rosters Companion Guide 834 Version 1.8 Created Modified March 09, 2015 March 09, 2015 I TABLE OF CONTENTS Record of change... 3 Companion Guide Purpose... 3 Overview... 3 Scope... 4
More information5010 Upcoming Changes:
HP Systems Unit I N D I A N A H E A L T H C O V E R A G E P R O G R A M S 5010 Upcoming Changes: 837 Dental Claims Transaction Based on Version 5, Release 1 ASC X12N 005010X224 Revision Information Revision
More information837 Professional Health Care Claim. Section 1 837P Professional Health Care Claim: Basic Instructions
anthemeap.com Companion Document 837P This companion document is for informational purposes only to describe certain aspects and expectations regarding the transaction and is not a complete guide. The
More information837 Healthcare Claim Companion Guide ANSI ASC X12N (Version 4010A) Professional, Institutional, and Dental
837 Healthcare Claim Companion Guide ANSI ASC X12N (Version 4010A) Professional, Institutional, and Dental State of Washington Department of Social & Health Services Prepared by: CNSI 3000 Pacific Avenue
More informationStandard Companion Guide
HealthSmart Benefit Solutions, Inc. Standard Companion Guide Refers to the Implementation Guide Based on X12 Version 00X220A1 Benefit Enrollment and Maintenance () January 2012 Companion Guide Version
More information271 Health Care Eligibility Benefit Inquiry Response Educational Guide
271 Health Care Eligibility Benefit Inquiry Response Educational Guide June 2010 - Version 1.1 Disclaimer INGENIX is still under development stages and frequent changes within this document are expected.
More information860 Purchase Order Change Request (Buyer Initiated) X12 Version Version: 2.0
860 Purchase Order Change Request (Buyer Initiated) X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 02/08/2017 1/26/2017 Purchase Order Change Request
More informationCOMMONWEALTH CARE ALLIANCE CCA COMPANION GUIDE
COMMONWEALTH CARE ALLIANCE CCA 5010 837 COMPANION GUIDE PREFACE This Companion Guide is v5010 and ASC X12N compatible and adopted under HIPAA clarifies and specifies the data content when exchanging electronically
More informationSYSCO only provide the customer address of a certain type of customers.
816 Organizational Relationships Functional Group ID=OR Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Organizational Relationships Transaction
More information816 Organizational Relationships
816 Organizational Relationships X12/V4010/816: 816 Organizational Relationships Version: 1.0 Final Company: Oshkosh Corporation Publication: 3/1/2013 Modified: 2/24/2013 2/24/2013 Oshkosh Corporation
More informationCALCULATOR APPLICATION
CALCULATOR APPLICATION Form1.cs using System; using System.Collections.Generic; using System.ComponentModel; using System.Data; using System.Drawing; using System.Linq; using System.Text; using System.Windows.Forms;
More informationKentucky HIPAA HEALTH CARE PAYER UNSOLICITED CLAIM STATUS Companion Guide Unsolicited 277. Version 1.1
Kentucky HIPAA HEALTH CARE PAYER UNSOLICITED CLAIM STATUS Companion Guide Unsolicited 277 Version 1.1 Released August 4, 2004 RECORD OF CHANGE VERSION NUMBER DATE REVISED DESCRIPTION OF CHANGE PERSONS
More information834 Companion Document to the 5010 HIPAA Implementation Guide
Published: 1/3/2012 Updated: 12/15/2014 834 Companion Document to the 5010 HIPAA Implementation Guide Version 3.00.00 Virtual Benefits Administrator Companion Document Audience Companion documents are
More informationIt is recommended not to exceed 99 patient requests per Information Receiver Loop (2000B).
ASC X12N 270/271 (004010X092A1) Health Care Eligibility Benefit Inquiry and Response Companion Guide Notes The ISA segment terminator, which immediately follows the component element separator, must consist
More informationFlorida Blue Health Plan
FLORIDA BLUE HEALTH PLAN COMPANION GUIDE Florida Blue Health Plan ANSI 276/277- Health Care Claim Status Inquiry and Response Standard Companion Guide Refers to the Technical Report Type Three () of 005010X212A1
More information837 Dental Health Care Claim
Companion Document 837D 837 Dental Health Care Claim Basic Instructions This section provides information to help you prepare for the ANSI ASC X12N 837 Health Care transaction for dental claims. The remaining
More information850 Purchase Order X12 Version Version: 2.0
850 Purchase Order X12 Version 4010 Version: 2.0 Author: Advance Auto Parts Company: Advance Auto Parts Publication: 12/03/2016 Revision History Date Version Description Author 1/15/2013 NA Original publication
More information816 Organizational Relationships
816 Organizational Relationships X12/V4010/816: 816 Organizational Relationships Version: 1.0 Final Company: Oshkosh Corporation Publication: 7/8/2015 Modified: 7/8/2015 Table of Contents 816 Organizational
More informationFlorida Blue Health Plan
FLORIDA BLUE HEALTH PLAN COMPANION GUIDE Florida Blue Health Plan ANSI 270/271- Health Care Eligibility and Benefit Inquiry and Response Standard Companion Guide Refers to the Technical Report Type Three
More informationMOLINA MEDICAID SOLUTIONS
MOLINA MEDICAID SOLUTIONS SUBMITTER S COMPION GUIDE FOR CSI MOLINA MEDICAID SOLUTIONS Submitter s Companion Guide for the Claims Status Inquiry System (CSI) Refers to the Implementation Guides Based on
More informationANSI ASC X12N 277 Claims Acknowledgement (277CA)
ANSI ASC X12N 277 Claims Acknowledgement (277CA) Acute Care Long Term Care Encounters COMPANION GUE February 28, 2012 Texas Medicaid & Healthcare Partnership Page 1 of 23 Print Date: 1/10/2013 Table of
More information270/ /271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time. Basic Instructions. Companion Document
Companion Document 270/271 270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time Basic Instructions This section provides information to prepare for the ANSI ASC X12.281
More informationRefers to the Technical Reports Type 3 Based on ASC X12 version X223A2
HIPAA Transaction Standard Companion Guide For Availity Health Information Network Users Refers to the Technical Reports Type 3 Based on ASC X12 version 005010X223A2 837 Health Care Claim Institutional
More information834 Benefit Enrollment and Maintenance
Companion Document 834 834 Benefit Enrollment and Maintenance This companion document is for informational purposes only to describe certain aspects and expectations regarding the transaction and is not
More informationAttachment-F FSCJ Current System Technical Specifications
Attachment-F FSCJ Current System Technical Specifications The College utilizes PeopleSoft HCM 9.2 for Benefits Administration. The below describes the process currently utilized that may potentially have
More informationEDS SYSTEMS UNIT. Companion Guide: 837 Dental Claims Transaction
EDS SYSTEMS UNIT I N D I A N A H E A L T H C O V E R A G E P R O G R A M S Companion Guide: 837 Dental Claims Transaction L I B R A R Y R E F E R E N C E N U M B E R : C L E L 1 0 0 1 3 [ A S C X 1 2 N
More informationHIPAA Transaction Health Care Claim Acknowledgement Standard Companion Guide (277CA, X214)
(underwritten by Dean Health Plan) HIPAA Transaction Health Care Claim Acknowledgement Standard Companion Guide (277CA, 005010X214) Instructions related to Transactions based on ASC X12 Implementation
More information997 Functional Acknowledgment (Inbound)
997 Functional Acknowledgment (Inbound) Functional Group ID=FA Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Functional Acknowledgment Transaction
More information855 Purchase Order Acknowledgment
855 Purchase Order Acknowledgment Functional Group ID= PR Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Purchase Order Acknowledgment Transaction
More information270/ /271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time. Basic Instructions. Companion Document
Companion Document 270/271 270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time Basic Instructions This section provides information to prepare for the ANSI ASC X12.281
More informationMedical Associates Health Plans and Health Choices
Medical Associates Health Plans and Health Choices 270/271 HIPAA Transaction Companion Guide HIPAA V5010X279A1 VERSION: 2.0 DATE: 06/21/2016 1 Disclosure Statement This material contains confidential,
More informationGovX Purchase Order. X12/V5010/850: 850 Purchase Order
850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 9/19/2018 Added new value UP in PO106 Added TD512 segment Table
More informationHIPAA Transaction 278 Request for Review and Response Standard Companion Guide
FLORIDA BLUE HEALTH PLAN COMPANION GUIDE HIPAA Transaction 278 Request for Review and Response Standard Companion Guide Refers to the Technical Reports Type 3 Based on ASC X12 version 005010X217 Companion
More information837 Health Care Claim Companion Guide. Professional and Institutional
837 Health Care Claim Companion Guide Professional and Institutional Revised December 2011 Table of Contents Introduction... 3 Purpose... 3 References... 3 Additional information... 4 Delimiters Supported...
More information875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005
875 - Grocery Products Purchase Order Author: DOT FOODS, INC. Publication: March 3, 2005 DOT FOODS, INC. Distributor 875 Page 1 875 Grocery Products Purchase Order Functional Group=OG This Draft Standard
More informationInbound ANSI X Version 04010
Inbound ANSI X12 850 Version 04010 For CLP License Ordering Version: ANSI X12 850 4010 Author: Adobe EDI Modified: 06/09/2010 CLP_X12_ANSI8504010_060910.ecs 1 For internal use only 850 Purchase Order Functional
More information270/ /271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time. Basic Instructions. Companion Document
Companion Document 270/271 270/271 Health Care Eligibility, Coverage, or Benefit Inquiry and Response Real-Time Basic Instructions This section provides information to prepare for the ANSI ASC X12.281
More information850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008
850 - Purchase Order Author: DOT FOODS, INC. Publication: September 24, 2008 850 Purchase Order Functional Group=PO Purpose: This Draft Standard for Trial Use contains the format and establishes the data
More informationPGW EDI Implementation Guideline
PGW EDI Implementation Guideline For Transaction Set 814 Reinstatement POR Request and Response X12 v4010 814 Reinstatement Request and Response Rev 1.0 July 28, 2015 Contents 814 General Request, Response
More information5010 Upcoming Changes: 837 Professional Claims and Encounters Transaction
HP Systems Unit I N D I A N A H E A L T H C O V E R A G E P R O G R A M S 5010 Upcoming Changes: 837 Professional Claims and Encounters Transaction Based on Version 5, Release 1 ASC 12N 005010222 and ASC12N005010222A1
More information276 STATUS REQUEST - Inbound Translation
INTECHANGE CONTOL HEADE 276 TATU EQUET - Inbound Translation ANI 276 Name Allowable Data Values IG IA01 Auth Infmation 00 No auth info present 03 Additional data infmation B3 2 2 The following group of
More informationGovX Purchase Order. X12/V5010/850: 850 Purchase Order
850 Purchase Order X12/V5010/850: 850 Purchase Order Company: GovX.com 1 4/12/2013 Purchase Order - 850 10/16/2015 Added TD5 segment 1/7/2016 Added new value UP in PO106 2 Table of Contents 850 Purchase
More informationJR Simplot Agribusiness Ship Notice/Manifest
JR Simplot Agribusiness - 856 Ship Notice/Manifest X12/V4010/856: 856 Ship Notice/Manifest Version: 1.0 Company: JR Simplot Modified: 8/28/2018 Table of Contents 856 Ship Notice/Manifest.....................................................................................................................
More information850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes:
850 Purchase Order X12/V4010/850: 850 Purchase Order Version: 1.0 Final Publication: 1/21/2009 Notes: Table of Contents 850 Purchase Order...1 ISA Interchange Control Header...3 GS Functional Group Header...5
More informationPGW EDI Implementation Guideline
PGW EDI Implementation Guideline For Transaction Set 814 Drop (ESP or LDC Initiated) Request and Response X12 v4010 814 Drop Request and Response Rev 1.7 Nov 16, 2015 Contents 814 General Request, Response
More informationConcurrent Session 204 Transactions and Code Sets: Its All in the Guides
Concurrent Session 204 Transactions and Code Sets: Its All in the Guides The HIPAA Summit West June 21, 2001 San Francisco, CA Gary Beatty gary@wpc-edi.com Washington Publishing Company Chair X12 Insurance
More informationEDI Specifications Guide. 856 Customer Advance Ship Notice
856 Customer Advance Ship Notice 856 Ship Notice/Manifest - Functional Group=SH VER. 4010 FISHER SCIENTIFIC This Standard contains the format and establishes the data contents of the Fisher Scientific
More informationPGW EDI Implementation Guideline
PGW EDI Implementation Guideline For Transaction Set 814 Change (ESP Initiated) Request and Response X12 v4010 814 Change Request and Response Rev 1.4 May 6, 2014 Contents 814 General Request, Response
More informationTransaction Set 850 Version 4010VICS, Electronic Purchase Order
back to Vendor Guide Transaction Set 850 Version 4010VICS, Electronic Purchase Order Segment: ISA - INTERCHANGE CONTROL HEADER Level: ENVELOPE PURPOSE: To start and identify an interchange of one or more
More information850 Purchase Order. Version: X12
850 Purchase Order Version: 004010 X12 Company: DOT FOODS, INC. Publication: 5/18/2012 850 Purchase Order Functional Group= PO Purpose: This Draft Standard for Trial Use contains the format and establishes
More informationInbound X Version 04010
Inbound X12 850 Version 04010 For Value Incentive Plan (VIP) License Ordering Version: ANSI ASC X12 850 4010 Author: Adobe EDI Company: Adobe Systems Inc Modified: 8/31/2015 850 Purchase Order Functional
More information837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE
837 PROFESSIONAL CLAIMS AND ENCOUNTERS TRANSACTION COMPANION GUIDE OCTOBER 19, 2012 A S C X 1 2 N 8 3 7 (0 0 5 0 10 X 222A1) VERSION 3.0 TABLE OF CONTENTS 1.0 Overview 3 2.0 Introduction 4 3.0 Data Exchange
More informationPartnership HealthPlan of California
Partnership HealthPlan of California HIPAA Transaction Companion Guide CORE: 276/277 Health Care Claim Status Request and Response ASC X12 version 005010 Disclosure Statement This document is subject to
More information521 Income or Asset Offset
521 Income or Asset Offset Functional Group ID=AO Introduction: This Draft Standard for Trial Use contains the format and establishes the data contents of the Income or Asset Offset Transaction Set (521)
More informationAssurant Health HIPAA Transaction Standard Companion Guide
Assurant Health HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 270/271 Health Care Eligibility Benefit Inquiry and Response CORE v5010 Master
More informationEMBLEMHEALTH HIPAA Transaction Standard Companion Guide
EMBLEMHEALTH HIPAA Transaction Standard Companion Guide Refers to the X12N Implementation Guide 005010X222A1: 837P Health Care Claim Professional Transaction HIPAA Readiness Disclosure Statement The Health
More informationAnthem Blue Cross and Blue Shield. 834 Companion Guide
Anthem Blue Cross and Blue Shield 834 Companion Guide for ANSI ASC X12N 834 Benefit Enrollment and Maintenance Transactions Incoming to the Electronic Enrollment System (EES) Anthem Blue Cross and Blue
More informationEDI Functional Acknowledgment
EDI 997 - Functional Acknowledgment VERSION: 1.0 FINAL Author: Created: Best Buy E-Business July 09, 2003 12:24 PM 997 EDI X12 4030 Document.rtf 1 For internal only 997 Functional Acknowledgment Functional
More informationCSIS 1624 CLASS TEST 6
CSIS 1624 CLASS TEST 6 Instructions: Use visual studio 2012/2013 Make sure your work is saved correctly Submit your work as instructed by the demmies. This is an open-book test. You may consult the printed
More informationHIPAA Transaction Standard Companion Guide. Refers to the Implementation Guides Based on ASC X12 version CORE v5010 Companion Guide
Gold Coast Health Plan CORE Companion Guide 270-271 HIPAA Transaction Standard Companion Guide Refers to the Implementation Guides Based on ASC X12 version 005010 CORE v5010 Companion Guide August 2018
More informationKentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837
Kentucky HIPAA HEALTH CARE CLAIM: DENTAL Companion Guide 837 Version 1.4 Final RECORD OF CHANGE VERSION NUMBER DATE REVISED DESCRIPTION OF CHANGE PERSONS INVOLVED 1.0 10/25/02 Creation and first view by
More information7/4/2011 Page 1 Retek850.xls
The following control characters will be sent in the document. Changes can be made if requested. ASCII HEX Segment Terminator CR x0d Element Separator * x2a Segment: ISA - INTERCHANGE CONTROL HEADER Level:
More information850 Delhaize America Direct Store Delivery CAO Purchase Order Version 5010
850 Delhaize America Direct Store Delivery CAO Purchase Order Version 5010 Introduction: Functional Group ID=PO The transaction set can be used to provide for customary and established business and industry
More information835 Health Care Claim Payment and Remittance Advice Companion Guide X091A1
835 Health Care Claim Payment and Remittance Advice Companion Guide 004010 X091A1 Version 1.3 March 1, 2008 1-March-2008 TABLE OF CONTENTS 1 Introduction... 1 1.1 Purpose... 1 2 Transmission and Data Retrieval
More information997 Functional Acknowledgment
997 Functional Acknowledgment Macy s VICS Version 5010 VICS Document Mapping Effective 09/01/08 The following is an outline of what is required when sending or receiving VICS 997 Functional Acknowledgments.
More informationANSI X (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010
ANSI X12 867 (Product Transfer and Resale Report) Outbound (from Eclipse) Version 4010 Eclipse 867 4010 (Vendor) 1 10/12/2012 867 Product Transfer and Resale Report Functional Group=PT Purpose: This Draft
More informationHIPAA Transaction Standard Companion Guide. ASC X12N Version X220A1 834 Benefit and Enrollment Maintenance
HIPAA Transaction Standard Companion Guide ASC X12N Version 005010X220A1 834 Benefit and Enrollment Maintenance Guide Version 1.2 September 2, 2018 Preface This Companion Document to the ASC X12N Implementation
More information