RE: [ebxml-cppa] WEDi/SNIP Electronic Trading Partner Agreements forHIPAA

[Dale Moberg <dmoberg@cyclonecommerce.com>]

Hi,

We are still wrapping up details connected with 2.0, and
we have active commitments to work on:

1. Oasis CPPA Negotiation protocol
2. BTP role capability and agreement representation.

All other possible work items are still being
prioritized, such as what are the requirements
for agreements concerning Core Component
"Contexts"

We do have several futures projects that might
be relevant to the e-TPA initiative you describe.

3. We want to attempt to provide support for
specific business process or service flow representations
beyond BPSS. 
4. We want to be able to discuss security
and transport bindings for other "protocol profiles"
beyond ebXML Messaging.

There is no data type restriction
for payloads within ebXML, so I do not anticipate use
of EDI style syntaxes for the payload data to be an issue.

Do you know whether HIPAA/WEDi/SNIP 
intends to adopt or create a way 
of specifying business processes? Will there just
be document names? 

We might still be able to work
out conventions for that use case and subsume it
under future project 3; we will need
to decide how to refer to Service and Action names,
and what to say about the ProcessSpecification, for example.

It might be worthwhile to start a discussion
mailing thread devoted to exploring your requirements.
Do you think that would be useful?

Bye
Dale Moberg
TC Chair

-----Original Message-----
From: William J. Kammerer [mailto:wkammerer@novannet.com]
Sent: Wednesday, March 06, 2002 3:29 PM
To: OASIS ebxml-cppa
Subject: [ebxml-cppa] WEDi/SNIP Electronic Trading Partner Agreements
for HIPAA


The WEDi/SNIP ID & Routing group, a Special Interest Group under the
Business Issues Sub-working Group of the WEDI HIPAA SNIP Task Group, at
http://snip.wedi.org/, is developing recommendations for the
"auto-discovery" of trading partners (payers, providers, third-party
administrators, etc.) and their technical capabilities.  We plan to
devise an Electronic Trading Partner Agreement (e-TPA) which can be
located by Trading Partner ID of any participant involved in HIPAA
Health Care EDI - either through a DNS-based "directory" of our own
design, or possibly UDDI or the OASIS ebXML Registry.

Enacted in August 1996, the Health Insurance Portability and
Accountability Act (HIPAA) is a U.S. federal law which is intended to
improve the availability and portability of health coverage and to
reduce the costs and administrative burdens of healthcare through the
use of standardized Electronic Data Interchange (EDI). Toward that end,
the legislation requires payers, clearinghouses and providers to
standardize electronic transactions in a confidential and secure
environment within two years following the publication of the final
rules.

In summary, pretty much all health care insurance companies and large
providers (such as hospitals) are under the gun to meet an October 2003
deadline for being able to do the "business" side of health care using
ANSI ASC X12 EDI.  This includes supporting electronic Claims, Claims
Status, Payments, Eligibility Benefit inquiries, and Service Reviews.
HIPAA EDI is the "Y2K problem" of the U.S. health care industry - though
its implementation deadline has now been extended twice!

We would like to use as much as possible from the OASIS ebXML CPP for
developing our e-TPA.  We already know that many HIPAA scenarios involve
"legacy" (e.g., non-Internet) protocols and packaging (e.g., EDIINT or
straight unadulterated EDI).  Even if you can't help us out with the
imminent (within the year) needs of the Healthcare community, we would
still want our own e-TPA to have as much compatibility as possible with
whatever is going on in ebXML.  Dick Brooks participates both in the
WEDi/SNIP ID & Routing group and in ebXML, and will serve as our liaison
to the OASIS CPPA TC.

We already suspect that directly supporting "legacy" protocols and
packaging would probably entail changes beyond the CPP-CPA 2.0 version.
Considering that HIPAA potentially covers hundreds of thousands of
health care providers and thousands of payers (including the U.S. Dept.
of HHS Medicare), and could make the U.S. Healthcare the first real
beneficiary of Open-EDI, it stands to reason this is a great opportunity
to make the CPPA more widely applicable.  We trust that our proposal to
work together in extending the CPP is well-received by this Technical
Committee - even if HIPAA payloads themselves are stinky old X12 EDI!

Please see http://www.novannet.com/wedi/ for more information on the
WEDi/SNIP ID & Routing group, including our listserve archives.

William J. Kammerer
Novannet, LLC.
+1 (614) 487-0320



----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>