Re: HHS HIPAA FAQ Analysis Draft #1

["William J. Kammerer" <wkammerer@foresightcorp.com>]

Chris Feahr says "Vision care looks like an excellent place to prototype
the ebXML approach to a real-live, HIPAA standard.  This would also
provide the greatest opportunity for our software developers to preserve
their investment in Web/XML EDI."  He asks "...if the JCC Project is
ready to consider taking it to this level?"

The EWG/X12 Joint core component work group will be jump-starting the
effort begun by the ebXML Core Components group, at least until
UN/CEFACT decides where the work will reside permanently.  See the
"Statement from the CSG on the forward direction for UN/CEFACT's
E-Business standards, at http://www.unece.org/cefact/.  In the meantime,
the JCC will meet at the X12 Trimester meeting scheduled in St. Louis
the week of June 4th.  See "To get things started...." at
http://lists.ebxml.org/archives/ebxml-dev/200105/msg00001.html for the
agenda of the St. Louis meeting.

William J. Kammerer
FORESIGHT Corp.
4950 Blazer Pkwy.
Dublin, OH USA 43017-3305
+1 614 791-1600

Visit FORESIGHT Corp. at http://www.foresightcorp.com/
"accelerating time-to-trade"

---

• From: "Christopher J. Feahr, OD" <chris@optiserv.com>
• To: <wes.rishel@gartner.com>,<PETERBARRY@aol.com>,<wes.rishel@gartner.com>,<zon4@earthlink.net>,<business@wedi.org>
• Date: Wed, 23 May 2001 19:54:25 -0700

the ebXML initiative looks very applicable to problems we are facing in 
Vision.  The present "de-facto standard" for handling the most complex 
payor business model (the one that is most different from the X12 approach) 
is entirely web-based.  The payor who developed this proprietary model has 
been moving steadily toward XML integration between its web-portal 
functions and several commercial Windows-based office management 
applications.  Since we have virtually no other EDI activity happening in 
Vision (and, therefore, no legacy EDI models to worry about migrating 
from)... Vision care looks like an excellent place to prototype the ebXML 
approach to a real-live, HIPAA standard.  This would also provide the 
greatest opportunity for our software developers to preserve their 
investment in Web/XML EDI.

Does anyone know if the JCC Project is ready to consider taking it to this 
level?

-Chris

At 08:42 PM 5/23/01 -0500, Rachel Foerster wrote:
>Peter, et al,
>
>Before you try to design something new as you describe below I would
>recommend you take a look at the recently approved ebXML Message Services
>specifications. It addresses all of what you mention below and the payload
>for an ebXML message can be X12, XML, or whatever is needed. There's no need
>to redesign that which has already been designed by some of the best
>technical minds in the world.
>
>All of the ebXML specifications can be freely downloaded at
>http://www.ebxml.org
>
>Rachel Foerster
>Principal
>Rachel Foerster & Associates, Ltd.
>Strategies for 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: PETERBARRY@aol.com [mailto:PETERBARRY@aol.com]
>Sent: Wednesday, May 23, 2001 4:56 PM
>To: wes.rishel@gartner.com; zon4@earthlink.net; business@wedi.org
>Subject: Re: HHS HIPAA FAQ Analysis Draft #1
>
>
>Dear Wes:
>
>Your comments as usual are very insightful.  I will shortly be drafting
>updates the SNIP DDE paper based on your and other comments.  We have
>planned
>to describe how X12 can be imbedded in an http or even an html envelope with
>security quite effectively.  The only language in earlier drafts that spoke
>to this was in the context of a solution in the computer-to-computer screen
>simulation paragraph, but that paragraph was removed for the time being
>while
>another round of question about it was sent to HHS.  Again, thanks for you
>comments.
>
>Peter
>
>Peter Barry
>Peter T Barry Company
>Ozaukee Bank Building
>1425 West Mequon Road
>Mequon Wisconsin 53092
>(414) 732 5000 (national cell)
>peterbarry@aol.com
>
>------------------------
>In a message dated 5/19/2001 1:09:29 PM Central Daylight Time,
>wes.rishel@gartner.com writes:
>
> > Subj:  RE: HHS HIPAA FAQ Analysis Draft #1
> >  Date:    5/19/2001 1:09:29 PM Central Daylight Time
> >  From:    wes.rishel@gartner.com (Rishel,Wes)
> >  To:  zon4@earthlink.net ('Zon Owen'), business@wedi.org
> >
> >  This is a prodigious piece of work, and a valuable compilation. I would
> > like
> >  to add one small set of comments here, in hopes that this is the right
> >  venue, or that someone will guide me to the right venue.
> >
> >  In the question and answer below it is unwise to use the term "real time"
> >  interchangeable with "DDE". Once a health plan has the ability to
>determine
> >  benefits or process some other transaction "in real time" it may apply to
> >  DDE, where the health plan presents a user interface to a person who
>works
> >  for a provider, or for real time processing of claims sent on a
> >  machine-to-machine basis one at a time. The latter process is not batch
>but
> >  it does require the us of the X12 format.
> >
> >  It is important to recognize that although X12 transactions are almost
> >  always transmitted in batches in healthcare, this is not a technological
> >  limitation of X12 or the Internet. Other industries routinely transmit
>X12
> >  transactions over HTTP (i.e., in "real time") with a level of security
>that
> >  meets all HIPAA requirements.
> >  Do the format requirements apply only to batch transactions and not to
> >  real-time/on-line transactions?
> >
> >  [WEDI WP Codes: DDE]
> >
> >  2/1/2001:
> >
> >  For real-time transactions, data entry screens must adhere to the data
> >  standards but do not have to adhere to the format standards, as long as
>the
> >  data is translated into the X12 format before it is transmitted.
> >
> >  The clarity of this statement could be improved if it described before it
>is
> >  transmitted to whom. Entering the data using DDE is a form of
>transmitting
> >  the data.
> >
>
>**********************************************************************
>To be removed from this list, send a message to: business-leave@wedi.org.
>Please note that it may take up to 72 hours to process your request.
>
>
>**********************************************************************
>To be removed from this list, send a message to: business-leave@wedi.org.
>Please note that it may take up to 72 hours to process your request.


Christopher J. Feahr, OD
Santa Rosa, CA
pager/cell/v-mail: 707-529-2268


**********************************************************************
To be removed from this list, send a message to: business-leave@wedi.org.
Please note that it may take up to 72 hours to process your request.

---