>Developing a requirements document....how novel!
Hmmm! I guess my comment was really worth 2 paise (1 cent = 48 paise). I don't think we need anything "novel" to carve out sections and fields. It is just that, looking at sections and fields one has to think "back" on what is "required" or intended to be supported, hence the suggestion with a "rider" (if not already done) because I "thought" (didn't confirm) that ebXML-CPP is "probably" the base document. I also referred to what is being done as "information gathering", which will then be used to reshuffle sections and fields. Sorry about that. I'll be more careful commenting next time. Ajay -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rachel Foerster Sent: Monday, May 06, 2002 9:33 PM To: 'WEDI/SNIP Listserve' Subject: RE: CPP Data elements draft for comment Developing a requirements document....how novel! Rachel Foerster Principal Rachel Foerster & Associates, Ltd. Professionals in EDI & Electronic Commerce 39432 North Avenue Beach Park, IL 60099 Phone: 847-872-8070 Fax: 847-872-6860 http://www.rfa-edi.com -----Original Message----- From: Ajay K sanghi [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 12:22 AM To: Michael Mattias/Tal Systems; WEDI/SNIP Listserve Subject: RE: CPP Data elements draft for comment Michael Mattias wrote: <snip> >(A DOCUMENT section in addition to CONNECTION would be just fine). <snip> It's absolutely necessary and many fields (18-27) in RECEIVER section needs to be "generic" and moved to DOCUMENT section (line items type). For example, Fields - Transaction Name, Version, Expected Test Date, Expected Start Date, Data - 837, X098, 09/01/2002, 04/01/2002, Also, more sections may be necessary. I am sure that all this will get "normalised" and that this is just a first step in "gathering" information necessary for HIPAA CPP. My suggestion is to first have a "requirement" document done (use story board), if not already done. For example, in this draft RECEIVER section, it "appears" that no new message beyond 837(s), 270 is required (assuming RECEIVER is the master section). The requirement document will mention if there has to be support for adding "new" message. Once the requirement is done then extracting "sections" and "fields" from it would be "easy". Just my 2 paise, Ajay Ajay K Sanghi Managing Director ABO Software Private Limited B102 Gulmohar Park, New Delhi 110049 Tel: +91 11 6968976, 6512822 Fax: 6518873 Website: http://www.abosoftware.com email: [EMAIL PROTECTED]
