----- Original Message ----- From: Christopher J. Feahr, OD <[EMAIL PROTECTED]>
> Here's the link to my proposed CPP template/spreadsheet. (thanks, William): > http://www.novannet.com/wedi/CPP_Elements.xls > You may want to hold off on commenting until you have seen a similar CPP > template proposal that Dick Brooks has been working on. Very, very nice...I like it. I look forward to Mr. Brooks' version, too. Just one question: Looking through this I noticed the absence (can you notice an absence?) of some data fields needed for an applications developer (e.g., me). What I am looking to do when I query the registry is to end up with all the data I would need to create a document (837, 270, 276, etc), send an ANSI interchange and have it get to the receiver, then have it pass the receiver's (non-medical) edits; that is, including such things as the applications identifiers. For example, some data fields which occur to me right off the top of my head...(270=Eligibility Inquiry) AcceptsRealTime270 - does this Information Source (payer) accept realtime 270's? AccceptsBatch270 - does this Information Source accept batch 270's? ApplicationID270RealTime - GS ID for payer for 'realtime' 270 ApplicationID270Batch - GS ID for payer's 'batch' 270 BatchLimit270 - maximum number of requests per single 270 in batch mode RealTimeTimeout - if no response to a 270 in 'n' seconds/minutes, give up. BatchTurnaroundTime - if no response to a 270 in 'n' hours/days, consider 'overdue' (Your 'NormalResponseTime" and SessionTimeout fields may cover the Timeout/Turnarounds, but I would like to see it expanded to allow for different times for different documents) Right now I am focused on the 270/271 (like you hadn't figured that out) and can provide a bunch of data fields for inclusion. (A DOCUMENT section in addition to CONNECTION would be just fine). To whom shall we send these suggested additions, or do we just post 'em here and hope for the best? ( Moderator help?) (Note: I sent this to a communications expert with whom I may work and he may comment as well). Michael Mattias Tal Systems, Inc. Racine WI [EMAIL PROTECTED]
