Title: RE: req vs. situation - companion documents


Our regional SNIP organization is working on a companion guide for claims and we are attempting to develop that list.  We are about 2/3rds through the professional claim.  We will make it public once it is complete.

Kris Owens
Senior IS Project Manager - HIPAA Project
Presbyterian Healthcare Services
Albuquerque, NM
505.923.8108
[EMAIL PROTECTED]

"Complex systems evolve from simple rules"





-----Original Message-----
From: Christopher J. Feahr, OD [mailto:[EMAIL PROTECTED]]
Sent: Monday, July 15, 2002 5:48 PM
To: '[EMAIL PROTECTED]'
Subject: Re: req vs. situation - companion documents


Janie,
One more comment on companion guides:  Most of the "situations" that, if
TRUE, trigger the required use of a situational segment are situations that
are present and observable right in the transaction.  Situations like "a
payor simply requires it", however, will have to be spelled out in a
companion guide.  I like to think of these as "soft situational" fields, as
opposed to "hard situationals" such as "use this element if segment X has a
value of Y".  The regular IG is adequate for the "hard situational" fields
and each payor's Companion guide should probably address ALL of the "soft"
ones.

(I wonder if anyone has made a list of "soft" situational elements that
could form the basis for a "standard" companion guide template?)

Regards,
Chris

At 01:01 PM 7/11/2002 -0700, Janie Miller wrote:
>Probably ignorant questions, but I must clarify for my own sanity:
>
>In a companion document, is it HIPAA compliant for a covered entity to
>"require" certain "situational" loops/segments/data elements of its trading
>partner(s)?  What about when the covered entity wants to "require" certain
>specific data in "NOT USED" description fields?
>
>
>
>**********************************************************************
>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.
>
>======================================================
>The WEDI SNIP listserv to which you are subscribed is not moderated.  The
>discussions on this listserv therefore represent the views of the
>individual participants, and do not necessarily represent the views of the
>WEDI Board of Directors nor WEDI SNIP.  If you wish to receive an official
>opinion, post your question to the WEDI SNIP Issues Database at
>http://snip.wedi.org/tracking/.
>Posting of advertisements or other commercial use of this listserv is
>specifically prohibited.

Christopher J. Feahr, OD
http://visiondatastandard.org
[EMAIL PROTECTED]
Cell/Pager: 707-529-2268       



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

======================================================
The WEDI SNIP listserv to which you are subscribed is not moderated.  The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP.  If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/.

Posting of advertisements or other commercial use of this listserv is specifically prohibited.



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

=====================================================
The WEDI SNIP listserv to which you are subscribed is not moderated. The discussions on this listserv therefore represent the views of the individual participants, and do not necessarily represent the views of the WEDI Board of Directors nor WEDI SNIP. If you wish to receive an official opinion, post your question to the WEDI SNIP Issues Database at http://snip.wedi.org/tracking/.
Posting of advertisements or other commercial use of this listserv is specifically prohibited.



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