Information technology--Specification and STANDARDization of data elements--Part 3:Basic attributes of data elements
Some standard content:
ICS35.040
National Standard of the People's Republic of China
GB/T18391.3—2001
idtISO/IEC11179-3:1994
Information technology
Specification and standardization of data elementsPart 3: Basic attributes of data elements elements2001-07-16Published
People's Republic of China
General Administration of Quality Supervision, Inspection and Quarantine
2002-03-01Implementation
GB/T18391.3--2001
ISO/IECForeword
1 Scope
2 Referenced standards
3 Definition
4 Data element attribute descriptor
5 Basic attributes of data elements
6 Specification of basic attributes of data elements
Appendix A (Suggestive Appendix)
Appendix B (Suggestive Appendix)
Appendix C (Suggestive Appendix)
Appendix D (Suggestive Appendix)
Additional attributes
Reuse and inheritance of attribute types
Examples of using basic attributes of data elements
Recommendations for using additional registration descriptors for attributes......0...
GB/T18391.3—2001
This standard is equivalent to the international standard ISO/IEC11179-3:1994 "Information technology - Specification and standardization of data elements - Part 3: Basic attributes of data elements".
GB/T18391, under the general title "Specification and standardization of data elements in information technology", includes the following parts: Part 1: Specification and standardization framework of data elements; - Part 2 Classification of data elements;
Part 3: Basic attributes of data elements;
--Part 4: Rules and guidelines for writing data definitions; - Part 5: Naming and identification principles of data elements; - Part 6: Registration of data elements.
Appendix A, Appendix B, Appendix C and Appendix D of this standard are informative appendices. This standard is proposed and managed by the China Standards Research Center. The drafting unit of this standard: China Standards Research Center. The main drafters of this standard: Li Xiaolin, Feng Wei, Liu Zhiting, Xing Liqiang. -
GB/T18391.3-2001
ISO/IEC Foreword
The International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) are global specialized standardization organizations. National organizations that are members of ISO or IEC participate in the development of international standards through various technical committees. Technical committees are formed by organizations that participate in technical activities in various professional fields. ISO and IEC technical committees cooperate in areas of common interest. Official and non-official international organizations that have ties to ISO and IEC can also participate in this work. In the field of information technology, ISO and IEC have formed a joint technical committee, ISO/IECJTC1. The draft international standards adopted by the joint technical committee are submitted to the national groups for voting. The promulgation of an international standard requires at least 75% of the national groups participating in the vote to vote in favor.
International standard ISO/IEC11179-3 was drafted by the Data Management and Exchange Subcommittee (SC32) under the Joint Technical Committee for Information Technology (ISO/IECJTC1). ISO/IEC11179, under the general title "Information technology - Specification and standardization of data elements", includes the following parts: Part 1: Specification and standardization framework of data elements; Part 2: Classification of data elements; Part 3: Basic attributes of data elements; Part 4: Rules and guidelines for writing data definitions; Part 5: Principles for naming and identifying data elements; Part 6: Registration of data elements.
Appendices A, B, C and D of this standard are indicative appendices. GB/T18391.3—2001
This standard specifies the basic attributes of data elements. Introduction
Data processing and electronic data interchange rely heavily on the accuracy, reliability, controllability and verifiability of the data recorded in the database.
One of the prerequisites for the correct and appropriate use and interpretation of data is that both the provider and the user of the data have a common understanding of the meaning and expression of the data elements. In order to have a common understanding of the data elements, it is necessary to define several of their attributes. 1 Scope
National Standard of the People's Republic of China
Information technology
Specification and standardization of data elements
Part 3: Basic affributes of data elements
Information technology-Specificationand standardization of data elements-Part 3.Basic affributes of data elementsGB/T18391.3—2001
idtISO/IEC11179-3:1994
This standard specifies the attributes of data elements, but is limited to a set of basic attributes, and has nothing to do with the usage of these attributes in application systems, databases, data exchange messages, etc.
This standard applies to the following activities:
a) Definition, description and content of data element dictionaries; b) Design and specification of application-oriented data models, databases and message types for the purpose of data exchange; c) Practical application of data in communication and information processing systems; d) Exchange or reference between various data element sets. In order to achieve comprehensive data management functions, this set of basic attributes will inevitably be expanded with additional attributes. This standard does not imply the logical structure or physical structure of the data.
Comprehensive data management functions also require a set of rules and procedures for classifying, defining, identifying, naming and registering data elements. These rules and procedures are beyond the scope of this standard and are specified in other parts of GB/T18391. The technology used to implement data element dictionaries using this standard is not within the scope of this standard. 2 Referenced standards
The provisions contained in the following standards constitute the provisions of this standard through reference in this standard. When this standard was published, the versions shown were valid. All standards will be revised, and parties using this standard should explore the possibility of using the latest versions of the following standards. GB/T1988—1998 Information technology Seven-bit coded character set for information interchange (eqvISO/IEC646:1991) GB/T2659-2000 Codes for country and region names of the world (eqvISO3166-1:1997) GB/T7408—1994 Data elements and exchange formats Information exchange Date and time representation (eqvISO8601:1988) ISO6093:1985 Information processing Characters for information interchange Numerical representation 3 Definitions
This standard uses the following definitions:
3.1 Attribute attribute
A characteristic of an object or entity.
3.2 Attribute value attributevalue
An instance representation of an attribute.
3.3 Data element dataelement
Approved by the General Administration of Quality Supervision, Inspection and Quarantine of the People's Republic of China on July 16, 2001 and implemented on March 1, 2002
GB/T18391.3-2001
A data unit whose definition, identification, expression and allowed values are described by a set of attributes. 3.4 Data element concept dataelementconcept A concept that can be represented in the form of a data element and is independent of any specific representation. 3.5 Data element dictionary dataelementdictionary An information resource that lists and defines all relevant data elements. Note: Data element dictionaries can have various levels, such as ISO/IEC committee level, international association level, industry department level, company level, application system level. 3.6 Data element value dataelementvalue
A value in the set of allowed values for a data element.
4 Data element attribute descriptor
4.1 General Descriptors
Data element attributes should be registered and controlled in a standard way so that data elements in the data element dictionary can be consistent during information exchange and can be compared between different data management environments. Table 1 gives a set of general descriptors for describing data element attributes. The column "Constraint" indicates whether a descriptor is "mandatory" (M), "conditional" (C), or "optional" (O) when describing a data element attribute. Table 1 General Descriptors
Attribute Descriptor
Maximum Number of Instances
Data Type
Maximum Length
Character Set
Generally speaking, data element attributes are registered in the data element dictionary using a character set. The character set used is described as the descriptor character set of the data element attribute. This descriptor is valid at the data element dictionary level and should be clearly defined when exchanged between dictionaries. If a character set used by one (or more) data element attributes is different from the usual case,
2 Assume that data element attributes are registered in the data element dictionary in one language. The language used is described as the descriptor "language" of the data element attribute. This descriptor is valid at the data element dictionary level and should be explicitly stated when exchanged between dictionaries. If one (or more) data element attributes use a language that is different from the language normally used for the entire data element dictionary, this descriptor "language" should be specified. Recommendations on the use of the "language" descriptor are given in Appendix D. 4.2 Mandatory descriptors
The following data element attribute descriptors are Required: Name, see 4.3.
Definition, see 4.4.
Constraints, see 4.5.
Data type, see 4.8.
4.3 Name
A label assigned to a data element attribute. The name shall be unique and shall be expressed in alphanumeric character string format. NOTE: The names of the basic attributes of a data element are listed in Table 2. 2
4.4 Definition
GB/T18391.3--2001
A description of a data element attribute that clearly distinguishes one data element attribute from other data element attributes. Definitions shall be expressed in alphanumeric character string format.
4.5 Constraints
A descriptor indicating whether a data element attribute always or sometimes occurs (i.e. has values). This descriptor can have the following meanings: - Required: The data element attribute must occur. - Conditional: The data element attribute shall occur if the conditions specified in 4.6 exist. - Optional: The data element attribute may or may not occur. 4.6 Conditional
The circumstances under which a data element attribute should occur.
4.7 Maximum number of instances
A descriptor that specifies the maximum number of instances a data element attribute may have in a data element specification. NOTE: The operator "maximum number of instances\" can be implemented as the number of repetitions of the attribute, or as the attribute occurring once but having multiple values assigned (multi-valued attributes). The latter case requires a syntactic convention to distinguish the attribute values from each other. Implementation example 1:
A data management function defines the attribute: "Synonym name" can occur three times in a data element specification. The three "synonymous names" of the data element are named "Product Code" and are expressed as follows: Name
Synonymous Name 1:
Synonymous Name 2:
Synonymous Name 3:
Implementation Example 2:
Product Code
Article Number
Material Code
Product Index Number
A certain data management function determines such an attribute: "Classification Mode" in a data element specification can appear only once but can have two values. The two "Classification Modes" of the data element "Component Body Length" can be expressed as follows; Name
Classification Mode:
4.8 Data Type
IEC Component Type:
IEC Data Element Type Type: Length Value (T03) A descriptor of a specific set of values specified for expressing an attribute value. Examples of data types for attribute values are: "Character", "Order Number", "Integer", "String".
4.9 Maximum Length
Specification of the maximum number of storage units to express a specific value of the data type specified in 4.8. Example: When the "Data Type" instance is specified as "Integer" and the "Maximum Length" descriptor instance value is "3", it means that the attribute value can contain a maximum of 3 digits.
Note: See Appendix D for suggestions on usage.
4.10 Remarks
Notes related to the application of attributes.
5 Basic attributes of data elements
5.1 Use of basic attributes
A data element specification consists of a set of attributes. This standard specifies a set of basic attributes. Basic means that they are often required to define data elements. Basic attributes are useful for various functions, such as: design of information processing systems;
GB/T18391.3—2001
Use
- Design of EDI messages for data exchange;
- Maintenance of a data element dictionary;
- Data management;
- Data governance;
- Design of a data element dictionary;
- Control of a data element dictionary;
- Use of information processing systems.
The attributes specified in this standard are also considered basic in the sense that some additional attributes are required to support the functions listed above.
Basic also means that these attributes are independent of: any application environment;
any function of the data element (e.g., qualifiers, indicators);
any level of abstract meaning (e.g., representation of a general concept like "person's name" or a specific concept like "truck driver's name");
):
Any grouping of data elements;
Any method of designing an information processing system or data exchange messages; Any data element dictionary system.
Basic does not mean that all standard attributes appearing in this standard are required in all cases. The following distinction can be made between these basic attributes:
Required: always required;
Conditional: must appear under certain conditions; Optional: allowed but not required.
5.2 Types of basic attributes
5.2.1 Identification class
Attributes applicable to data element identification.
5.2.2 Definition class
Attributes that describe semantic aspects of data elements.
Note: This Class attributes may be derived from characteristics inherited from data element concepts, objects or entities. 5.2.3 Relationship class
Attributes that describe the relationships between data elements and/or the relationships between data elements and classification schemes, data element concepts, objects or entities. 5.2.4 Representation class
Attributes that describe the representation of data elements.
5.2.5 Management class
Attributes that describe the management and control of data elements. 5.3 Basic attribute table
Table 2 lists the basic attributes grouped according to the categories of 5.2. For the precise definition of these basic attributes, see Chapter 6. "Column\constraint" indicates whether an attribute is "required (M)", "conditional (C)", or "optional (O)" in the data element dictionary. Table 2 Data element attributes
Attribute type
Identification class
Identifier
Data element attribute name
Definition found in
Attribute type
Identification class
Definition class
Relationship class
Representation class
Management class
5.4 Basic attribute model
Registration authority
Synonymous name
Related environment
Classification mode
Keywords
GB/T18391.3-2001
Table 2 (end)
Data element extensibility name
Related data reference
Relationship type
Representation category
Representation form
Data type of data element value
Maximum length of data element value
Minimum length of data element value
Representation format
Allowed values of data element
Competent authority
Registration status
Submitting authority
Definition see
The model described in Figure 1 uses two criteria to group the attributes of data elements. Attributes grouped in the same group share similar cardinality and logical correlation.
Representation category
Representation form
Data type of data element value
Maximum length of data element value
Minimum length of data element value
Representation format
Related environment
Permitted data element values
Synonymous name
Related environment
Cardinal type
(6.2.1)1:1
(6.4.3)1:1
(6.4.4)
(6.4.6)70:1
(6.1. 1)
(6.1.6)0:1
0: element
data element
0:1remarks
competent authority
submitting authority
registration authority
identifier
registration status
classification mode
related data reference
relationship type
0:nkeyword
Figure 1 basic attribute model
(6.5.3)
(6.1.3)
(6.5.2)
(6.3. 3)
Each data element specification may contain 0 or 1 (0:1), 1 and only 1 (11), 0 or more (0:n), 1 or more (1:n) attribute occurrences listed in Table 2.
GB/T 18391.3—2001
For example: a data element specification may contain 0 or 1 "competent authority" attribute, but requires 1 and only 1 "definition" attribute. It may contain 0 or more pairs of "related data reference" and "relationship type" attributes, but requires 1 or more "data element allowed values" attributes. Logical dependency
In addition to having similar cardinality types, attributes may also be dependent on each other, that is, a certain attribute cannot exist without the existence of other attributes:
For example: if either of the attributes "synonymous name" and "related environment" exists, then both of them should exist. Similarly, if either of the attributes "related data reference" and "relationship type" exists, then both of them should exist. On the other hand, even if the attributes "related data reference" and "synonymous name" have the same cardinality type (O:n), they cannot exist in dependence on each other and therefore cannot be grouped together.
5.5 Mandatory
The following data element attributes are mandatory:
name, see 6.1.1
definition, see 6.2.1
representation type, see 6.4.1
representation form, see 6.4.2
data type of data element value, see 6.4.3
maximum length of data element value, see 6.4.4
minimum length of data element value, see 6.4.5
allowed values of data element, see 6.4.7
NOTE: The data management environment may determine that the "constraints" on basic attributes, which are defined as conditional or optional in this International Standard, may have more advanced "constraints" in the local environment.
5.6 Additional attributes
Additional, non-basic data element attributes that are required. For example: regarding the internal representation of the data element in the database or showing the structural relationship of the data element to system and message elements.
See Appendix A for examples.
6 Specification of basic data element attributes
Data elements are described by their attributes, as described in Chapter 5. The basic attributes of these data elements are described in detail in this chapter. Each attribute is described using the mandatory descriptors given in Chapter 4. See Appendix D for suggestions on the use of conditional descriptors. 6.1 Identification class attributes
6.1.1 Name:
Definition:
Constraints:
A single or multiple word designation assigned to a data element. Required
String
Data type:
Remarks:
6.1.2 Name:
Definition:
Constraints:
Conditions:
1. See GB/T18391.5 and GB/T18391.6 for naming principles; 2. If there are naming conventions within a certain application scope, this attribute must be constructed according to these conventions. 3. The environment that controls data elements may require that this attribute is a unique identifier within a data element dictionary
A unique identifier of a data element within a registration agency that is independent of the language. Conditional selection
If the attribute "data element name" (6.1.1) is not unique within a registration agency, then this attribute is required.
The allocation of unique identifiers can be a mandatory part of the registration process of any registration agency. Data type:
Remarks:
6.1.3 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.4 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.5 Name:
Definition:
Constraint:
Data type:
Remarks:
|6.1.6 Name:
Definition:
Constraints:
Data type:
Conditions:
Remarks:
6.2 Define class attributes
6.2.1 Name:
Definition:
Constraints:
GB/T18391.3—2001
1. In order to reference data elements controlled by different registration agencies, this attribute can be qualified by the identification of the registration agency and the attribute "version" (see 6.1.3) to ensure uniqueness. 2. For the relevant conventions and recommendations for establishing and controlling data element identifiers, see GB/T18391.5 and GB/T18391.6.
The identification of a data element specification release in a series of gradually improved data element specifications within a registration agency.
Conditional
This attribute is mandatory when an attribute is updated and the update meets the maintenance rules of the new version established by the registration authority.
1. For rules and recommendations on the use of versions, see GB/T 18391.6. 2. For reasons of data element control and data element reference, the attribute "version" can be used as a qualifier for the attribute "identifier".
Registration authority
An organization authorized to register data elements. Conditional
Each occurrence of the identifier shall specify a registration authority. The string
Combined attributes "registration authority", "identifier" and "version" can be used to uniquely identify a data element. A data element can be registered by more than one registration authority. GB/T 18391.6 gives more detailed information about registration authorities. Synonymous name
A single-word or multi-word designation that is different from a given name but represents the same data element concept. Optional
String
Synonymous names are often familiar names in certain application contexts. If this is the case, the attribute "RelatedContext" (6.1.6) should be used to specify this context. If more synonyms exist, the attributes "SynonymousName" and "RelatedContext\" should be specified as a pair of attributes.
RelatedContext
A description of the application context or application procedure in which the name (or synonym) is used or generated. Conditional
String
This attribute is mandatory for each occurrence of the attribute "SynonymousName" (6.1.5). This attribute is mandatory when the attribute "Name" (6.1.1) is present in an information exchange process. Specifying the attribute "RelatedContext" for the attribute "Name\ (6.1.1) is mandatory for the registration procedures of the Registration Authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. Required1) The specified attribute "relevant environment" is required for the registration process of the registration authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. Required1) The specified attribute "relevant environment" is required for the registration process of the registration authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. Required1 Remarks
Competent authority
Submitting authority
Registration authority
Identifier
Registration status
Classification mode
Related data reference
Relationship type
0:n Keywords
Figure 1 Basic attribute model
(6.5.3)
(6.1.3)
(6.5.2)
(6.3.3)
Each data element specification may contain 0 or 1 (0:1), 1 and only 1 (11), 0 or more (0:n), 1 or more (1:n) attribute events listed in Table 2.
GB/T 18391.3—2001
For example: a data element specification may contain 0 or 1 "competent authority" attribute, but requires 1 and only 1 "definition" attribute. It may contain 0 or more pairs of "related data reference" and "relationship type" attributes, but requires 1 or more "data element allowed values" attributes. Logical dependency
In addition to having similar cardinality types, attributes may also be dependent on each other, that is, a certain attribute cannot exist without the existence of other attributes:
For example: if either of the attributes "synonymous name" and "related environment" exists, then both of them should exist. Similarly, if either of the attributes "related data reference" and "relationship type" exists, then both of them should exist. On the other hand, even if the attributes "related data reference" and "synonymous name" have the same cardinality type (O:n), they cannot exist dependent on each other, and thus they cannot be grouped in the same group.
5.5 Mandatory
The following data element attributes are mandatory:
Name, see 6.1.1
Definition, see 6.2.1
Representation type, see 6.4.1
Representation form, see 6.4.2
Data type of data element value, see 6.4.3
Maximum length of data element value, see 6.4.4
Minimum length of data element value, see 6.4.5
Permitted values of data element, see 6.4.7
Note: The data management environment may determine that the "constraints" on basic attributes, which are defined as conditional or optional in this standard, may have more advanced "constraints" in the local environment.
5.6 Additional attributes
Additional, non-basic data element attributes are required. For example: about the internal expression of data elements in the database or showing the structural relationship between data elements and system and message elements.
For examples, see Appendix A.
6 Specification of basic attributes of data elements
Data elements are described by their attributes, as described in Chapter 5. The basic attributes of these data elements are described in detail in this chapter. Each attribute is described using the mandatory descriptors given in Chapter 4. For suggestions on the use of conditional descriptors, see Appendix D. 6.1 Identification class attributes
6.1.1 Name:
Definition:
Constraints:
A single or multiple word designation assigned to a data element. Required
String
Data type:
Remarks:
6.1.2 Name:
Definition:
Constraints:
Conditions:
1. See GB/T18391.5 and GB/T18391.6 for naming principles; 2. If there are naming conventions within a certain application scope, this attribute must be constructed according to these conventions. 3. The environment that controls data elements may require that this attribute is a unique identifier within a data element dictionary
A unique identifier of a data element within a registration agency that is independent of the language. Conditional selection
If the attribute "data element name" (6.1.1) is not unique within a registration agency, then this attribute is required.
The allocation of unique identifiers can be a mandatory part of the registration process of any registration agency. Data type:
Remarks:
6.1.3 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.4 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.5 Name:
Definition:
Constraint:
Data type:
Remarks:
|6.1.6 Name:
Definition:
Constraints:
Data type:
Conditions:
Remarks:
6.2 Define class attributes
6.2.1 Name:
Definition:
Constraints:
GB/T18391.3—2001
1. In order to reference data elements controlled by different registration agencies, this attribute can be qualified by the identification of the registration agency and the attribute "version" (see 6.1.3) to ensure uniqueness. 2. For the relevant conventions and recommendations for establishing and controlling data element identifiers, see GB/T18391.5 and GB/T18391.6.
The identification of a data element specification release in a series of gradually improved data element specifications within a registration agency.
Conditional
This attribute is mandatory when an attribute is updated and the update meets the maintenance rules of the new version established by the registration authority.
1. For rules and recommendations on the use of versions, see GB/T 18391.6. 2. For reasons of data element control and data element reference, the attribute "version" can be used as a qualifier for the attribute "identifier".
Registration authority
An organization authorized to register data elements. Conditional
Each occurrence of the identifier shall specify a registration authority. The string
Combined attributes "registration authority", "identifier" and "version" can be used to uniquely identify a data element. A data element can be registered by more than one registration authority. GB/T 18391.6 gives more detailed information about registration authorities. Synonymous name
A single-word or multi-word designation that is different from a given name but represents the same data element concept. Optional
String
Synonymous names are often familiar names in certain application contexts. If this is the case, the attribute "RelatedContext" (6.1.6) should be used to specify this context. If more synonyms exist, the attributes "SynonymousName" and "RelatedContext\" should be specified as a pair of attributes.
RelatedContext
A description of the application context or application procedure in which the name (or synonym) is used or generated. Conditional
String
This attribute is mandatory for each occurrence of the attribute "SynonymousName" (6.1.5). This attribute is mandatory when the attribute "Name" (6.1.1) is present in an information exchange process. Specifying the attribute "RelatedContext" for the attribute "Name\ (6.1.1) is mandatory for the registration procedures of the Registration Authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. Required1 Remarks
Competent authority
Submitting authority
Registration authority
Identifier
Registration status
Classification mode
Related data reference
Relationship type
0:n Keywords
Figure 1 Basic attribute model
(6.5.3)
(6.1.3)
(6.5.2)
(6.3.3)
Each data element specification may contain 0 or 1 (0:1), 1 and only 1 (11), 0 or more (0:n), 1 or more (1:n) attribute events listed in Table 2.
GB/T 18391.3—2001
For example: a data element specification may contain 0 or 1 "competent authority" attribute, but requires 1 and only 1 "definition" attribute. It may contain 0 or more pairs of "related data reference" and "relationship type" attributes, but requires 1 or more "data element allowed values" attributes. Logical dependency
In addition to having similar cardinality types, attributes may also be dependent on each other, that is, a certain attribute cannot exist without the existence of other attributes:
For example: if either of the attributes "synonymous name" and "related environment" exists, then both of them should exist. Similarly, if either of the attributes "related data reference" and "relationship type" exists, then both of them should exist. On the other hand, even if the attributes "related data reference" and "synonymous name" have the same cardinality type (O:n), they cannot exist dependent on each other, and thus they cannot be grouped in the same group.
5.5 Mandatory
The following data element attributes are mandatory:
Name, see 6.1.1
Definition, see 6.2.1
Representation type, see 6.4.1
Representation form, see 6.4.2
Data type of data element value, see 6.4.3
Maximum length of data element value, see 6.4.4
Minimum length of data element value, see 6.4.5
Permitted values of data element, see 6.4.7
Note: The data management environment may determine that the "constraints" on basic attributes, which are defined as conditional or optional in this standard, may have more advanced "constraints" in the local environment.
5.6 Additional attributes
Additional, non-basic data element attributes are required. For example: about the internal expression of data elements in the database or showing the structural relationship between data elements and system and message elements.
For examples, see Appendix A.
6 Specification of basic attributes of data elements
Data elements are described by their attributes, as described in Chapter 5. The basic attributes of these data elements are described in detail in this chapter. Each attribute is described using the mandatory descriptors given in Chapter 4. For suggestions on the use of conditional descriptors, see Appendix D. 6.1 Identification class attributes
6.1.1 Name:
Definition:
Constraints:
A single or multiple word designation assigned to a data element. Required
String
Data type:
Remarks:
6.1.2 Name:
Definition:
Constraints:
Conditions:
1. See GB/T18391.5 and GB/T18391.6 for naming principles; 2. If there are naming conventions within a certain application scope, this attribute must be constructed according to these conventions. 3. The environment that controls data elements may require that this attribute is a unique identifier within a data element dictionary
A unique identifier of a data element within a registration agency that is independent of the language. Conditional selection
If the attribute "data element name" (6.1.1) is not unique within a registration agency, then this attribute is required.
The allocation of unique identifiers can be a mandatory part of the registration process of any registration agency. Data type:
Remarks:
6.1.3 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.4 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.5 Name:
Definition:
Constraint:
Data type:
Remarks:
|6.1.6 Name:
Definition:
Constraints:
Data type:
Conditions:
Remarks:
6.2 Define class attributes
6.2.1 Name:
Definition:
Constraints:
GB/T18391.3—2001
1. In order to reference data elements controlled by different registration agencies, this attribute can be qualified by the identification of the registration agency and the attribute "version" (see 6.1.3) to ensure uniqueness. 2. For the relevant conventions and recommendations for establishing and controlling data element identifiers, see GB/T18391.5 and GB/T18391.6.
The identification of a data element specification release in a series of gradually improved data element specifications within a registration agency.
Conditional
This attribute is mandatory when an attribute is updated and the update meets the maintenance rules of the new version established by the registration authority.
1. For rules and recommendations on the use of versions, see GB/T 18391.6. 2. For reasons of data element control and data element reference, the attribute "version" can be used as a qualifier for the attribute "identifier".
Registration authority
An organization authorized to register data elements. Conditional
Each occurrence of the identifier shall specify a registration authority. The string
Combined attributes "registration authority", "identifier" and "version" can be used to uniquely identify a data element. A data element can be registered by more than one registration authority. GB/T 18391.6 gives more detailed information about registration authorities. Synonymous name
A single-word or multi-word designation that is different from a given name but represents the same data element concept. Optional
String
Synonymous names are often familiar names in certain application contexts. If this is the case, the attribute "RelatedContext" (6.1.6) should be used to specify this context. If more synonyms exist, the attributes "SynonymousName" and "RelatedContext\" should be specified as a pair of attributes.
RelatedContext
A description of the application context or application procedure in which the name (or synonym) is used or generated. Conditional
String
This attribute is mandatory for each occurrence of the attribute "SynonymousName" (6.1.5). This attribute is mandatory when the attribute "Name" (6.1.1) is present in an information exchange process. Specifying the attribute "RelatedContext" for the attribute "Name\ (6.1.1) is mandatory for the registration procedures of the Registration Authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. Required3—2001
For example: a data element specification may contain 0 or 1 "competent authority" attribute, but requires 1 and only 1 "definition" attribute. It may contain 0 or more pairs of "related data reference" and "relationship type" attributes, but requires 1 or more "data element allowed values" attributes. Logical Dependencies
In addition to having similar cardinality types, attributes may also be dependent on each other, that is, one attribute cannot exist without the other:
For example: if either of the attributes "synonymous name" and "related environment" exists, then both of them should exist. Similarly, if either of the attributes "related data reference" and "relationship type" exists, then both of them should exist. On the other hand, even if the attributes "related data reference" and "synonymous name" have the same cardinality type (O:n), they cannot exist dependent on each other and therefore cannot be grouped together.
5.5 Mandatory
The following data element attributes are mandatory:
Name, see 6.1.1
Definition, see 6.2.1
Representation type, see 6.4.1
Representation form, see 6.4.2
Data type of data element value, see 6.4.3
Maximum length of data element value, see 6.4.4
Minimum length of data element value, see 6.4.5
Permitted values of data element, see 6.4.7
Note: The data management environment may determine that the "constraints" on basic attributes, which are defined as conditional or optional in this standard, may have more advanced "constraints" in the local environment.
5.6 Additional attributes
Additional, non-basic data element attributes are required. For example: about the internal expression of data elements in the database or showing the structural relationship between data elements and system and message elements.
For examples, see Appendix A.
6 Specification of basic attributes of data elements
Data elements are described by their attributes, as described in Chapter 5. The basic attributes of these data elements are described in detail in this chapter. Each attribute is described using the mandatory descriptors given in Chapter 4. For suggestions on the use of conditional descriptors, see Appendix D. 6.1 Identification class attributes
6.1.1 Name:
Definition:
Constraints:
A single or multiple word designation assigned to a data element. Required
String
Data type:
Remarks:
6.1.2 Name:
Definition:
Constraints:
Conditions:
1. See GB/T18391.5 and GB/T18391.6 for naming principles; 2. If there are naming conventions within a certain application scope, this attribute must be constructed according to these conventions. 3. The environment that controls data elements may require that this attribute is a unique identifier within a data element dictionary
A unique identifier of a data element within a registration agency that is independent of the language. Conditional selection
If the attribute "data element name" (6.1.1) is not unique within a registration agency, then this attribute is required.
The allocation of unique identifiers can be a mandatory part of the registration process of any registration agency. Data type:
Remarks:
6.1.3 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.4 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.5 Name:
Definition:
Constraint:
Data type:
Remarks:
|6.1.6 Name:
Definition:
Constraints:
Data type:
Conditions:
Remarks:
6.2 Define class attributes
6.2.1 Name:
Definition:
Constraints:
GB/T18391.3—2001
1. In order to reference data elements controlled by different registration agencies, this attribute can be qualified by the identification of the registration agency and the attribute "version" (see 6.1.3) to ensure uniqueness. 2. For the relevant conventions and recommendations for establishing and controlling data element identifiers, see GB/T18391.5 and GB/T18391.6.
The identification of a data element specification release in a series of gradually improved data element specifications within a registration agency.
Conditional
This attribute is mandatory when an attribute is updated and the update meets the maintenance rules of the new version established by the registration authority.
1. For rules and recommendations on the use of versions, see GB/T 18391.6. 2. For reasons of data element control and data element reference, the attribute "version" can be used as a qualifier for the attribute "identifier".
Registration authority
An organization authorized to register data elements. Conditional
Each occurrence of the identifier shall specify a registration authority. The string
Combined attributes "registration authority", "identifier" and "version" can be used to uniquely identify a data element. A data element can be registered by more than one registration authority. GB/T 18391.6 gives more detailed information about registration authorities. Synonymous name
A single-word or multi-word designation that is different from a given name but represents the same data element concept. Optional
String
Synonymous names are often familiar names in certain application contexts. If this is the case, the attribute "RelatedContext" (6.1.6) should be used to specify this context. If more synonyms exist, the attributes "SynonymousName" and "RelatedContext\" should be specified as a pair of attributes.
RelatedContext
A description of the application context or application procedure in which the name (or synonym) is used or generated. Conditional
String
This attribute is mandatory for each occurrence of the attribute "SynonymousName" (6.1.5). This attribute is mandatory when the attribute "Name" (6.1.1) is present in an information exchange process. Specifying the attribute "RelatedContext" for the attribute "Name\ (6.1.1) is mandatory for the registration procedures of the Registration Authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. Required3—2001
For example: a data element specification may contain 0 or 1 "competent authority" attribute, but requires 1 and only 1 "definition" attribute. It may contain 0 or more pairs of "related data reference" and "relationship type" attributes, but requires 1 or more "data element allowed values" attributes. Logical Dependencies
In addition to having similar cardinality types, attributes may also be dependent on each other, that is, one attribute cannot exist without the other:
For example: if either of the attributes "synonymous name" and "related environment" exists, then both of them should exist. Similarly, if either of the attributes "related data reference" and "relationship type" exists, then both of them should exist. On the other hand, even if the attributes "related data reference" and "synonymous name" have the same cardinality type (O:n), they cannot exist dependent on each other and therefore cannot be grouped together. Www.bzxZ.net
5.5 Mandatory
The following data element attributes are mandatory:
Name, see 6.1.1
Definition, see 6.2.1
Representation type, see 6.4.1
Representation form, see 6.4.2
Data type of data element value, see 6.4.3
Maximum length of data element value, see 6.4.4
Minimum length of data element value, see 6.4.5
Permitted values of data element, see 6.4.7
Note: The data management environment may determine that the "constraints" on basic attributes, which are defined as conditional or optional in this standard, may have more advanced "constraints" in the local environment.
5.6 Additional attributes
Additional, non-basic data element attributes are required. For example: about the internal expression of data elements in the database or showing the structural relationship between data elements and system and message elements.
For examples, see Appendix A.
6 Specification of basic attributes of data elements
Data elements are described by their attributes, as described in Chapter 5. The basic attributes of these data elements are described in detail in this chapter. Each attribute is described using the mandatory descriptors given in Chapter 4. For suggestions on the use of conditional descriptors, see Appendix D. 6.1 Identification class attributes
6.1.1 Name:
Definition:
Constraints:
A single or multiple word designation assigned to a data element. Required
String
Data type:
Remarks:
6.1.2 Name:
Definition:
Constraints:
Conditions:
1. See GB/T18391.5 and GB/T18391.6 for naming principles; 2. If there are naming conventions within a certain application scope, this attribute must be constructed according to these conventions. 3. The environment that controls data elements may require that this attribute is a unique identifier within a data element dictionary
A unique identifier of a data element within a registration agency that is independent of the language. Conditional selection
If the attribute "data element name" (6.1.1) is not unique within a registration agency, then this attribute is required.
The allocation of unique identifiers can be a mandatory part of the registration process of any registration agency. Data type:
Remarks:
6.1.3 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.4 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.5 Name:
Definition:
Constraint:
Data type:
Remarks:
|6.1.6 Name:
Definition:
Constraints:
Data type:
Conditions:
Remarks:
6.2 Define class attributes
6.2.1 Name:
Definition:
Constraints:
GB/T18391.3—2001
1. In order to reference data elements controlled by different registration agencies, this attribute can be qualified by the identification of the registration agency and the attribute "version" (see 6.1.3) to ensure uniqueness. 2. For the relevant conventions and recommendations for establishing and controlling data element identifiers, see GB/T18391.5 and GB/T18391.6.
The identification of a data element specification release in a series of gradually improved data element specifications within a registration agency.
Conditional
This attribute is mandatory when an attribute is updated and the update meets the maintenance rules of the new version established by the registration authority.
1. For rules and recommendations on the use of versions, see GB/T 18391.6. 2. For reasons of data element control and data element reference, the attribute "version" can be used as a qualifier for the attribute "identifier".
Registration authority
An organization authorized to register data elements. Conditional
Each occurrence of the identifier shall specify a registration authority. The string
Combined attributes "registration authority", "identifier" and "version" can be used to uniquely identify a data element. A data element can be registered by more than one registration authority. GB/T 18391.6 gives more detailed information about registration authorities. Synonymous name
A single-word or multi-word designation that is different from a given name but represents the same data element concept. Optional
String
Synonymous names are often familiar names in certain application contexts. If this is the case, the attribute "RelatedContext" (6.1.6) should be used to specify this context. If more synonyms exist, the attributes "SynonymousName" and "RelatedContext\" should be specified as a pair of attributes.
RelatedContext
A description of the application context or application procedure in which the name (or synonym) is used or generated. Conditional
String
This attribute is mandatory for each occurrence of the attribute "SynonymousName" (6.1.5). This attribute is mandatory when the attribute "Name" (6.1.1) is present in an information exchange process. Specifying the attribute "RelatedContext" for the attribute "Name\ (6.1.1) is mandatory for the registration procedures of the Registration Authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. RequiredThe environment controlling data elements may require this attribute to be a unique identifier within a data element dictionary
A unique identifier of a data element within a registration authority, regardless of the language. Conditional
This attribute is mandatory if the attribute "data element name" (6.1.1) is not unique within a registration authority.
The allocation of unique identifiers may be an optional part of the registration process of any registration authority. Data type:
Remarks:
6.1.3 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.4 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.5 Name:
Definition:
Constraint:
Data type:
Remarks:
|6.1.6 Name:
Definition:
Constraints:
Data type:
Conditions:
Remarks:
6.2 Define class attributes
6.2.1 Name:
Definition:
Constraints:
GB/T18391.3—2001
1. In order to reference data elements controlled by different registration agencies, this attribute can be qualified by the identification of the registration agency and the attribute "version" (see 6.1.3) to ensure uniqueness. 2. For the relevant conventions and recommendations for establishing and controlling data element identifiers, see GB/T18391.5 and GB/T18391.6.
The identification of a data element specification release in a series of gradually improved data element specifications within a registration agency.
Conditional
This attribute is mandatory when an attribute is updated and the update meets the maintenance rules of the new version established by the registration authority.
1. For rules and recommendations on the use of versions, see GB/T 18391.6. 2. For reasons of data element control and data element reference, the attribute "version" can be used as a qualifier for the attribute "identifier".
Registration authority
An organization authorized to register data elements. Conditional
Each occurrence of the identifier shall specify a registration authority. The string
Combined attributes "registration authority", "identifier" and "version" can be used to uniquely identify a data element. A data element can be registered by more than one registration authority. GB/T 18391.6 gives more detailed information about registration authorities. Synonymous name
A single-word or multi-word designation that is different from a given name but represents the same data element concept. Optional
String
Synonymous names are often familiar names in certain application contexts. If this is the case, the attribute "RelatedContext" (6.1.6) should be used to specify this context. If more synonyms exist, the attributes "SynonymousName" and "RelatedContext\" should be specified as a pair of attributes.
RelatedContext
A description of the application context or application procedure in which the name (or synonym) is used or generated. Conditional
String
This attribute is mandatory for each occurrence of the attribute "SynonymousName" (6.1.5). This attribute is mandatory when the attribute "Name" (6.1.1) is present in an information exchange process. Specifying the attribute "RelatedContext" for the attribute "Name\ (6.1.1) is mandatory for the registration procedures of the Registration Authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. RequiredThe environment controlling data elements may require this attribute to be a unique identifier within a data element dictionary
A unique identifier of a data element within a registration authority, regardless of the language. Conditional
This attribute is mandatory if the attribute "data element name" (6.1.1) is not unique within a registration authority.
The allocation of unique identifiers may be an optional part of the registration process of any registration authority. Data type:
Remarks:
6.1.3 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.4 Name:
Definition:
Constraint:
Condition:
Data type:
Remarks:
6.1.5 Name:
Definition:
Constraint:
Data type:
Remarks:
|6.1.6 Name:
Definition:
Constraints:
Data type:
Conditions:
Remarks:
6.2 Define class attributes
6.2.1 Name:
Definition:
Constraints:
GB/T18391.3—2001
1. In order to reference data elements controlled by different registration agencies, this attribute can be qualified by the identification of the registration agency and the attribute "version" (see 6.1.3) to ensure uniqueness. 2. For the relevant conventions and recommendations for establishing and controlling data element identifiers, see GB/T18391.5 and GB/T18391.6.
The identification of a data element specification release in a series of gradually improved data element specifications within a registration agency.
Conditional
This attribute is mandatory when an attribute is updated and the update meets the maintenance rules of the new version established by the registration authority.
1. For rules and recommendations on the use of versions, see GB/T 18391.6. 2. For reasons of data element control and data element reference, the attribute "version" can be used as a qualifier for the attribute "identifier".
Registration authority
An organization authorized to register data elements. Conditional
Each occurrence of the identifier shall specify a registration authority. The string
Combined attributes "registration authority", "identifier" and "version" can be used to uniquely identify a data element. A data element can be registered by more than one registration authority. GB/T 18391.6 gives more detailed information about registration authorities. Synonymous name
A single-word or multi-word designation that is different from a given name but represents the same data element concept. Optional
String
Synonymous names are often familiar names in certain application contexts. If this is the case, the attribute "RelatedContext" (6.1.6) should be used to specify this context. If more synonyms exist, the attributes "SynonymousName" and "RelatedContext\" should be specified as a pair of attributes.
RelatedContext
A description of the application context or application procedure in which the name (or synonym) is used or generated. Conditional
String
This attribute is mandatory for each occurrence of the attribute "SynonymousName" (6.1.5). This attribute is mandatory when the attribute "Name" (6.1.1) is present in an information exchange process. Specifying the attribute "RelatedContext" for the attribute "Name\ (6.1.1) is mandatory for the registration procedures of the Registration Authority.
A statement that expresses the essential characteristics of a data element and distinguishes it from all other data elements. Required
Tip: This standard content only shows part of the intercepted content of the complete standard. If you need the complete standard, please go to the top to download the complete standard document for free.