You are reading it correctly. 
 
The code in the lower left corner of the boxes is the X12 usage - not the X12N usage.  Essentially, in the overall X12 standard these elements are considered optional but X12N has designated them as required within this implementation of the transaction set.  If you look at the detail text for these elements, you will notice that in the right hand column under the attributes title the "O"  as well - again indicating the X12 usage while the left most column states "Required" as the X12N usage.
 
-----Original Message-----
From: Bard, Greg [mailto:[EMAIL PROTECTED]
Sent: Friday, March 07, 2003 9:56 AM
To: WEDI SNIP Transactions Workgroup List
Subject: FW: TRANSACTION 834 QUESTION ON IMPLEMENTATION GUIDE

I was teaching a class on how to read the Implementation Guides and ran across something that I hope this ListServ can clarify.

 

In the Data Element Diagram, INS03 is bolded which means it is required.  It indicates it is required but the attribute (requirement Designator) states it is an ‘O’ which I though meant Optional.  Same applies to INS05- Indicates it is required but Attribute is defined as Optional.

 

 

Greg Bard

NASCO

HIPAA Privacy and Security Project Manager

(W) 678.441.6059

(F)  678.441.6359

[EMAIL PROTECTED]

 

 

______________________________________________________________________________________

CONFIDENTIALITY NOTICE

The information in this message (and the documents attached to it, if any) is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, distribution or any action taken, or omitted to be taken in reliance on it is prohibited and may be unlawful. If you have received this message in error, please delete all electronic copies of this message (and the documents attached to it, if any), destroy any hard copies you may have created and notify me immediately. Thank you.

 

 

 

 

 

---
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/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time.

You are currently subscribed to wedi-transactions as: [EMAIL PROTECTED]
To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED]
If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org
---
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/. These listservs should not be used for commercial marketing purposes or discussion of specific vendor products and services. They also are not intended to be used as a forum for personal disagreements or unprofessional communication at any time.

You are currently subscribed to wedi-transactions as: [EMAIL PROTECTED]
To unsubscribe from this list, go to the Subscribe/Unsubscribe form at http://subscribe.wedi.org or send a blank email to [EMAIL PROTECTED]
If you need to unsubscribe but your current email address is not the same as the address subscribed to the list, please use the Subscribe/Unsubscribe form at http://subscribe.wedi.org

Reply via email to