|DotNet Class HL7Connect.Cda.ANY|
Defines the basic properties of every data value. This is conceptually an abstract type, meaning that no proper value can be just a data value without belonging to any concrete type. Every public concrete type is a specialization of this general abstract DataValue type.
However exceptional values (nullFlavored values) may be of type ANY, except for the exceptional values that imply the nullFlavor INV, since this requires a type to be meaningful. Note that not all nullFlavors may be used with the type ANY (see section 7.1.4 for more details
|If the value is not a proper value, indicates the reason.|
Though the nullFlavor concept has some relationship with the UML/OCL null, it is not the same thing, and the relationship and differences between the two must be understood to properly implement this specification. For further discussion, see section 7.1.4 (Null and NullFlavor). Note that nullFlavor includes the concept of a UML null value, and also includes potentially fully populated instances that do not conform to the requirements placed on the instance (also known as "exceptional instances"). Both nonNull and nullFlavored values SHALL always be valid according to the rules expressed in this specification.
If populated, the value of this attribute SHALL be taken from the HL7 NullFlavor code system. -- NullFlavor that applies to the property. Note that nfNull means Not Null
|This property allows a sending system to identify the role that the attribute plays in processing the instance that is being represented.|
If populated, the value of this attribute SHALL be taken from the HL7 UpdateMode code system. -- Update mode. Should always be umNull in a CDA document
|Signals the imposition of one or more sets of constraints on the datatype. The sole purpose of specifying that a constraint that has been used to further constrain the datatype is to support validation of the instance: a validation engine can look up the rules expressed for the specified flavors and confirm that the instance conforms to the rules for the flavor. No other processing should depend on the content of the flavor attribute. |
No other semantic or computational use SHALL depend on the value of this property. If this value is populated, the datatype flavor(s) SHALL be a valid constraint on the type of the value.
There is further discussion about the use of Data Type flavors and flavorId in section A.3
|A literal string representation of the data, where one is defined in the specification|