Title: Replacing our current eligibility file with the 271



As part of our health plan implementation for HIPAA, we plan to begin using the 271 first as an unsolicited roster to replace the eligibility file we currently send to our trading partners.  During the process of mapping our current file to the 271, we have discovered that there are a number of fields we currently send to our trading partners that are not accomodated on the 271.  We are in the process of evaluating the affect of the absence of these fields on the process of doing business with our trading partners.  However, we are wondering if others are finding the same issues and what conclusions they are drawing.

Examples of some of the fields not included in the 271 are:

  1. a transaction code indicating that the record is an add, update, term, or unchanged record.
  2. A relationship code indicating the member's relationship to the subscriber
  3. A termination reason code
  4. A product line indicator
  5. A current benefit package indicator
  6. Rider type code (multiple indicators)
  7. PCP provider group affiliation
  8. Other coverage carrier indicator

Are other organizations encountering similar issues?  If so, how are you resolving them?


Thanks,
Ellen Tatge
IS Project Manager
Presbyterian Healthcare Services
505/923-6882






**********************************************************************
To be removed from this list, go to: http://snip.wedi.org/unsubscribe.cfm?list=business
and enter your email address.



--- PRESBYTERIAN HEALTHCARE SERVICES DISCLAIMER ---

This message originates from Presbyterian Healthcare Services or one of its affiliated organizations. It contains information, which may be confidential or privileged, and is intended only for the individual or entity named above. It is prohibited for anyone else to disclose, copy, distribute or use the contents of this message. All personal messages express views solely of the sender, which are not to be attributed to Presbyterian Healthcare Services or any of its affiliated organizations, and may not be distributed without this disclaimer. If you received this message in error, please notify us immediately at [EMAIL PROTECTED]

Reply via email to