Greetings Vicki,
First of all, to answer your original questions:
* Is the 271 transaction intended to cover routine eligibility
extracts or rosters?
= The "transaction" is intended to cover both plus more.
Note the key distinction between a transaction and an
Implementation Guide; which I've further explained a bit
below.
* Is a 271 transaction only generated in response to a 270
transaction?
= In general, No; for HIPAA, Yes. Again see the explanation
that follows.
X12 transaction standards (e.g., 271, 837, 835) are intended to be as
encompassing as possible to the widest possible variations of business
needs for Electronic Data Interchange (EDI). As such, they have lots
of optional fields and uses. Which of these optional fields are
populated and with what contents are historically determined by
'trading partner agreements'. Trading partner agreements are usually
quite specific to the organization pairs actually exchanging
information on a situation-by-situation basis. Thus, uses of the X12
transaction standards can vary considerably; with all such uses being
'standard compliant'.
The X12N Implementation Guides are intended to constrain the use of
the X12 transaction standards to a single set of fields and contents
for each transaction: both HIPAA and non-HIPAA. Thus, for example,
there are three Implementation Guides (X098, X096, X097) which define
three different uses of X12 transaction standard 837 for the purposes
of transmitting claims (professional, institutional, dental). In
particular response to your queries, the Implementation Guide (X092)
for Eligibility specifies that a 271 transaction is used in response
to a 270 query. This Implementation Guide has also been adopted for
use under HIPAA.
Thus, the 271 transaction standard may be used in many ways, but if
you're attempting purely HIPAA compliance, then you must follow the
HIPAA Implementation Guides; which thus far only specify the use of
the 271 in response to a 270. As an example of a use of the 271 in
support of a roster, take a look at Implementation Guide X040 -- which
is not [yet] HIPAA.
There are a few more small points that could be made, but I hope the
above is enough to provide the answers you requested along with some
background. Do keep asking as other issues arise in the ever
fascinating :-) world of HIPAA and EDI.
Dave Feinberg
Co-Chair, HIPAA Implementation Work Group
Insurance Subcommittee (X12N)
Accredited Standards Committee X12
Voting Member, HL7 and X12
Rensis Corporation [A Consulting Company]
206-617-1717
[EMAIL PROTECTED]
----- Original Message -----
From: "Siegfried, Victoria" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Friday, August 17, 2001 11:47 AM
Subject: Purpose of 271 transaction
I have 2 basic questions on the purpose and use of the 271 transaction
that
I have not seen specifically addressed in the implementation guide:
* Is the 271 transaction is intended to cover routine eligibility
extracts or rosters?
* Is a 271 transaction only generated in response to a 270
transaction?
Vicki Siegfried
Business Consultant
Coventry Health Care
HIPAA / EDI Team
(724) 778-5931
**********************************************************************
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.
