]> Communication Standards Ontology based on BFO Frank Oemig Common root relationship for all other CSO relationships. 1 1 1 There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons. There may be an alternate mechanism for gaining access to this information. NoInformation No information whatsoever can be inferred from this exceptional value. This is the most general exceptional value. It is also the default exceptional value. NotApplicable Known to have no proper value (e.g., last menstrual period for a male). The different specialisations of NullFlavor provides some information, why no real information has been transmitted. Other The actual value is not an element in the value domain of a variable. (e.g., concept not provided by required code system). NegativeInfinity Negative infinity of numbers. PositiveInfinity Positive infinity of numbers. Unencoded The actual value has not yet been encoded within the approved valueset for the domain. Unknown A proper value is applicable, but not known. AskedButUnknown Information was sought but not found (e.g., patient was asked but didn't know) TemporarilyNotAvailable Information is not available at this time but it is expected that it will be available later. NotAsked SufficientQuantity The specific quantity is not known, but is known to be non-zero and is not specified because it makes up the bulk of the material. Trace The content is greater than zero, but too small to be quantified. This is an indication represented as the last character whether the information has been truncated or not This is an indication represented as the last character whether the information has been truncated or not This is an indication represented as the last character whether the information has been truncated or not Required Required, but may be empty Optional Conditional Conditional is retained for backward compatibility Withdrawn X: not used element Required Required not permitted Required Data Elements: Data Elements that shall be included and are mandatory elements. The Value Field shall contain valid data as defined by the elements VR and VM as specified in PS 3.6. The Length of the Value Field shall not be zero. Absence of a valid Value in a Type 1 Data Element is a protocol violation. Conditional Data Elements: Data Elements that shall be included under certain specified conditions. Type 1C elements have the same requirements as Type 1 elements under these conditions. It is a protocol violation if the specified conditions are met and the Data Element is not included. When the specified conditions are not met, Type 1C elements shall not be included in the Data Set. Required Data Elements:Data Elements that shall be included and are mandatory Data Elements. However, it is permissible that if a Value for a Type 2 element is unknown it can be encoded with zero Value Length and no Value. If the Value is known the Value Field shall contain that value as defined by the elements VR and VM as specified in PS 3.6. These Data Elements shall be included in the Data Set and their absence is a protocol violation. Conditional Data Elements: Type 2C elements that have the same requirements as Type 2 elements under certain specified conditions. It is a protocol violation if the specified conditions are met and the Data Element is not included. When the specified conditions are not met, Type 2C elements shall not be included in the Data Set. Optional Data Elements: Data Elements that are optional Data Elements. Absence of a Type 3 element from a Data Set does not convey any significance and is not a protocol violation. Type 3 elements may also be encoded with zero length and no Value. The meaning of a zero length Type 3 Data Element shall be precisely the same as that element being absent from the Data Set. Frank Oemig Frank Oemig (DISS) Communication Standards Ontology (CSO) 18.09.2009 basic concepts + details from HL7 v2.x, V3 and DICOM