I saw this posting on the EDI-L mailing list. It sounds like this guy could use the WEDi/SNIP CPP - our "Electronic Trading Partner Agreement." All that EDI contact information he talks about will be in the CPP, along with EDI addresses, companion documents and anything else that can be mechanized. Too bad (for him) it's initially targeted for HealthCare - though think of the possibilities: there's nothing we're doing in the ID & Routing SIG recommendations, really, that other industries couldn't use.
By the way, thanks to Ronald Bowron for the Noridian Medicare links. Noridian's Medicare Part B "Companion" document is available at http://www.noridianmedicare.com/provider/edi/tech_docs_6_hipaa.html, and there's nothing in there that couldn't be mechanized - i.e., represented in an XML document so it could be used to customize translators and comm packages, or at a minimum, displayed with a stylesheet. I would like to collect more sample companion documents so we know all the types of stuff in them - can subscribers to this list share theirs? I'm currently working on getting a volunteer from one of the EDI productivity tool vendors to share their expertise in designing a XML'ized companion document. Please write me privately if you're interested in working on this sub-project. William J. Kammerer Novannet, LLC. +1 (614) 487-0320 ----- Original Message ----- From: "Dan Mehlhorn" <[EMAIL PROTECTED]> To: "New EDI-L" <[EMAIL PROTECTED]> Sent: Monday, 11 March, 2002 03:19 PM Subject: [EDI-L] <MISC> Pet Peeve My pet peeve is that when companies change EDI contact persons, they don't contact their EDI trading partners to inform them of the new person's name, phone number, and E-mail address. Dan Mehlhorn System Programmer/EDI Administrator Crescent Electric Supply Co.
