Dear Johnnie:

I think the two replies copied below from Jonathan and Chris answer the 
question well.  In your question you say "Upon submission of the request, the 
fields from the screen are gathered on an internal machine that picks up the 
requests for the web site, and it goes off to various systems to gather the 
data needed."  Paragraph 8.9 is intended to say this fits DDE just fine.  
Operating under the DDE exception, it is quite acceptable to enter only the 
minimum data needed for the request such that the remaining data is 
obtainable from the plan's files.  Hope this helps.

Peter

Peter Barry
Peter T Barry Company
Ozaukee Bank Building
1425 West Mequon Road
Mequon Wisconsin 53092
(414) 732 5000 (national cell)
[EMAIL PROTECTED]

------------------------------------
Subj:    Re: Question about DDE requests:
Date:   7/16/2001 2:56:47 PM Central Daylight Time
From:   [EMAIL PROTECTED] (Christopher J. Feahr, OD)
To: [EMAIL PROTECTED] (Wilson, Johnnie L.), [EMAIL PROTECTED] 
('[EMAIL PROTECTED]'), [EMAIL PROTECTED] ('[EMAIL PROTECTED]')

Johnnie,
If I understand your question, you seem to be asking whether the *Request* 
for information in a DDE environment *must* contain all the standard data 
fields, fully populated... even when most of that data is already in the 
payor system, and could be retrieved internally if the requester provides 
claim# and policy#.  If this is your question, then it is my understanding 
that the payor can omit data elements from the requester's screens if he 
already the data (from some prev. transaction).  But in general, it is 
recommended that you have the DDE terminal DISPLAY all of that non-keyed 
data so that the provider using the DDE service can verify its accuracy. 
The provider who is using the DDE terminal (or browser-form) is ultimately 
responsible for the accuracy of all info that is transmitted from it to the 
payor.
-Chris
--------------------------
In a message dated 7/16/2001 5:06:47 PM Central Daylight Time, 
[EMAIL PROTECTED] writes:

> Subj:  RE:Question about DDE requests:
>  Date:    7/16/2001 5:06:47 PM Central Daylight Time
>  From:    [EMAIL PROTECTED]
>  To:  [EMAIL PROTECTED]
>  CC:  [EMAIL PROTECTED] (translations wedi org), [EMAIL PROTECTED] (
> Business wedi org)
>  
>  
>  If I understand your system flow from your info, the 276/277 applies from a
>  data content only perspective.  You have the request from the human filling
>  out the screen  (a logical 276) and the response going back to the user  (a
>  logical 277).  If you have not already, you need to review the 
> implementation
>  guides to compare the data content to the data content in each guide.  For
>  example, if the guide says field xyz in required and must be accepted as 
one
>  of the valid search criteria.. the web screen must support it.
>  
>  
>  
>  Thanks!
>  
>  Jonathan Showalter
>  Omaha NE  USA
>  402-343-3381
>  [EMAIL PROTECTED]
>  ------------------( Forwarded letter 1 follows )--------------------
>  Date: Mon, 16 Jul 2001 13:25:34 -0400
>  To: translations.wedi.org[translations]@wedi.org,
>   Business.wedi.org[Business]@wedi.org
>  From: Johnnie.L.Wilson[jwilson]@trigon.com
>  Sender: [EMAIL PROTECTED]
>  Subject: Question about DDE requests:
>  
>  This question refers to a DDE type request being issued from an internet
>  site via a web browser.  A sample page may deal with a service such as a
>  provider inquiring about the details of a claim (276 request).  For this
>  kind of inquiry, the only data currently needed to find this information
>  under the current implementation is the members policy number and the claim
>  number.  Upon submission of the request, the fields from the screen are
>  gathered on an internal machine that picks up the requests for the web 
site,
>  and it goes off to various systems to gather the data needed.  The data
>  brought back to the provider will be 277 compliant from a content
>  perspective.  If for instance the request to gather the data is a database
>  call, the only data necessary might be the claim number or a combination of
>  the claim number and policy number.  In this scenario, the concept of a 276
>  request transaction doesn't seem to fit into this architecture.  How does a
>  277 transaction fit into a web based model for these kinds of  scenarios?
>  
>  
>  Johnnie Wilson
>  Distributed Systems
>  Trigon HealthCare, Inc.
>  804-354-7494
>  [EMAIL PROTECTED]

**********************************************************************
To be removed from this list, send a message to: [EMAIL PROTECTED]
Please note that it may take up to 72 hours to process your request.

Reply via email to