Dear Frank: If a data element is required, it has to be on a DDE screen.
Situational is more difficult. If it is situational, it has to be on a DDE screen if the situation might pertain. The thought was that the situation would be determined by the medical encounter, not by whether the specific plan needs or wants the information--the idea of standard data content would be that it is the same for all plans, not different one plan to another. For a plan to omit a data element or a code value on the grounds that it does not need or want it, although another plan might want it, would undermine the concept of standardization. This seems simple enough but the Implementation Guides include situations defined as whether the data are necessary for the plan to process the transaction. This has given rise to "Companion Guides" which seem very much like tailoring standards to the desires of plans. Presumably, if a plan can adjust the standard to its needs through a companion guide, you would think it could adjust its DDE screens to be the same. So situational is not a DDE question; the statement still stands that the field must be on a DDE screen if the situation might pertain, that is, same data content means same as what the standard requires. Rather the question is, what is the data content of the standard and how that might be adjusted by situations determined by the plan rather than the medical instance. The variances described in the WEDI paper were that a plan might target a type of provider in the design of its screens such that the screens are comprehensive of the possible needs of that provider type. We have a major revision of the DDE paper now in special committee and soon to begin the approval process first through Business Issues and then Transactions groups. I am hoping it will be released to Business Issues at the end of next week. Its status would remain "unapproved draft" until approved by WEDI. It goes into considerable depth on equal treatment, same data content (especially richer data), and other issues. Peter Peter Barry Peter T Barry Company Independent Consulting Health Care and Information Systems Ozaukee Bank Building 1425 West Mequon Road Mequon Wisconsin 53092 (414) 732 5000 (national cell) [EMAIL PROTECTED] ------------------------ In a message dated 8/28/2002 11:01:42 AM Central Daylight Time, [EMAIL PROTECTED] writes: > Subj: Clarification Regarding DDE > Date: 8/28/2002 11:01:42 AM Central Daylight Time > From: [EMAIL PROTECTED] (Romano, Frank) > Reply-to: <A HREF="mailto:[EMAIL PROTECTED]";>[EMAIL PROTECTED] </A> > To: [EMAIL PROTECTED] > > My understanding that is that if we have a field on the Web screen, it > must > be data content compliant. However, if we do not utilize a field (required > or situational) on the Web screen as part of our business process, we do not > have to incorporate this field on the Web screen. Example, in enrollment, > the 834 has a situation Country element. If I do not need this to process > my enrollment transaction via the Web, I do not need to display this element > for potential data (even if I default). > > Can someone confirm my assumption. > > Thanks > Frank > ********************************************************************** To be removed from this list, go to: http://snip.wedi.org/unsubscribe.cfm?list=Business and enter your email address. The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/. Posting of advertisements or other commercial use of this listserv is specifically prohibited.
