ebXML Messaging Service is a brilliant and extremely pragmatic pieceof standards work

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

"ebXML Messaging Service is a brilliant and extremely pragmatic piece of
standards work..."  (Wes Rishel of Gartner, on the WEDI business forum).

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: "Rishel,Wes" <wes.rishel@gartner.com>
• To: "'rachelf@ix.netcom.com'" <rachelf@ix.netcom.com>, PETERBARRY@aol.com,zon4@earthlink.net, business@wedi.org
• Date: Thu, 24 May 2001 00:30:43 -0400

I agree with Rachel completely. The ebXML Messaging Service is a brilliant
and extremely pragmatic piece of standards work that solves a great number
of the problems of secure use of the Internet for discrete transactions,
such as the HIPAA transactions. Don't be put off by the XML in the name; the
service is neutral as to the syntax of the payload.

The fact that this spec was developed with major contributions from the
vendors of application integration and security middleware products helps to
ensure a speedy roll-out of compliant software. In particular btrade.com and
Group8760 have been involved in doing X12 over the Internet for many years.

In a "First Take" which should be available on Gartner.com on Thursday, I
tell our clients that they should immediately begin to pressure their
vendors to implement the MS.

Health Level-7 is working on a specific profile describing how to use the
ebXML MS for HL7 messages, both in the current "bars and carets" syntax and
the new XML-based stuff.

The only reservation I have about the MS at all is that it is the dependent
on the Collaboration-Protocol Profile and Agreement Specification. The
CPP-CPA is also a good piece of work, but it may be more than people want to
bite off at one time. As I read the spec the reliance on the CPP-CPA is not
absolute, but it will take some education for people to realize that.

-----Original Message-----
From: Rachel Foerster [mailto:rachelf@ix.netcom.com]
Sent: Wednesday, May 23, 2001 6:42 PM
To: PETERBARRY@aol.com; Rishel,Wes; zon4@earthlink.net;
business@wedi.org
Subject: RE: HHS HIPAA FAQ Analysis Draft #1


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.

**********************************************************************
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.

---