| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
| WS/T 671-2020 | English | RFQ |
ASK
|
3 days [Need to translate]
|
(National Health and Population Information Data Dictionary)
| Valid |
WS/T 671-2020
|
PDF similar to WS/T 671-2020
Basic data | Standard ID | WS/T 671-2020 (WS/T671-2020) | | Description (Translated English) | (National Health and Population Information Data Dictionary) | | Sector / Industry | Health Industry Standard (Recommended) | | Classification of Chinese Standard | C07 | | Word Count Estimation | 145,122 | | Date of Issue | 2020-05-22 | | Date of Implementation | 2020-12-01 | | Regulation (derived from) | State-health communication (2020) No. 9 | | Issuing agency(ies) | National Health Commission | WS/T 671-2020: (National Health and Population Information Data Dictionary)---This is a DRAFT version for illustration, not a final translation. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.) will be manually/carefully translated upon your order.
National data dictionary for health and population information
ICS 11.020
C 07
WS
People's Republic of China Health Industry Standard
National Health and Population Information Data Dictionary
2020-05-22 release
2020-12-01 Implementation
Issued by the National Health Commission of the People's Republic of China
Table of contents
Foreword...I
1 Scope...1
2 Normative references...1
3 Terms, definitions and abbreviations...1
4 General data element description rules...4
5 General Data Element Representation Class...5
6 Metadata identifier generation rules...5
7 Rules for generating vocabulary concept identifiers...5
8 General Data Element Description...5
9 Vocabulary...104
Appendix A (Normative Appendix) HL7 V3 Data Type...128
Appendix B (Normative Appendix) Correspondence between health information conceptual data model and data dictionary...130
Appendix C (Normative Appendix) Data Dictionary Application Diagram...134
References...135
Index...136
Foreword
This standard was drafted in accordance with the rules given in GB/T 1.1-2009.
Drafting organizations of this standard. PLA Air Force Military Medical University, National Health Commission Statistical Information Center, Huazhong University of Science and Technology
Tongji Medical College, Shanghai Center for Disease Control and Prevention.
The main drafters of this standard. Liu Danhong, Yang Zhe, Lou Miaomiao, Hao Huijuan, Hu Jianping, Li Yuefeng, Zhang Lili, Shen Lining, Xia Tian, Zhang Cheng.
1 Scope
This standard provides general data elements and their descriptions in the field of national health and population, as a guide for the development of data standards in related fields.
This standard applies to the standardization and standardization of information in the national health and population fields, and guides data collection, transmission, aggregation and integration.
The development of various information artifacts used in the process, including data sets, shared documents, etc.
2 Normative references
The following documents are indispensable for the application of this document. For dated reference documents, only the dated version applies to this
file. For undated references, the latest version (including all amendments) applies to this document.
GB/T 2260 Administrative division codes of the People's Republic of China
GB/T 2659 Codes for names of countries and regions in the world
GB/T 3304 Roman alphabet spelling and codes for the names of various ethnic groups in China
GB/T 4658 academic code
GB/T 18391.1 Information Technology Metadata Registration System (MDR) Part 1.Framework (ISO /IEC 11179-1 IDT)
GB/T 18391.3 Information Technology Metadata Registration System (MDR) Part 3.Registration System Metamodel and Basic Attributes (ISO /IEC
11179-3 IDT)
GB/T 30107 Health Informatics HL7 V3 Reference Information Model
GB/T 31287 National Organization Code Application Marking Specification
WS/T 672 National Health and Population Information Conceptual Data Model
ISO 4217 currency codes (Currency codes)
HL7 V3 Standard Data Types-Abstract Specification, Release 2 (HL7 Version 3 Standard. Data Types-Abstract Specification, Release 2)
3 Terms, definitions and abbreviations
The following terms and definitions defined in GB/T 18391-2009 apply to this document. For ease of use, GB/T is repeatedly listed below
Certain terms and definitions in 18391-2009.
3.1 Terms and definitions
3.1.1
Object class
An idea, abstract concept or a collection of things in the real world, it can be identified with clear boundaries and meanings, its characteristics and
Performance follows the same rules.
[GB/T 18391.3-2009, definition 3.3.88]
3.1.2
Attribute
The characteristics of an object or entity.
[GB/T 18391.3-2009, definition 3.1.3]
3.1.3
Definition
Describe a concept and distinguish it from other related concepts.
[GB/T 18391.3-2009, definition 3.1.12]
3.1.4
Data element concept
A concept expressed in the form of data elements whose description has nothing to do with any specific representation.
[GB/T 18391.3-2009, definition 3.3.38]
3.1.5
Data element
A data unit whose definition, identification, representation, and allowable value are defined by a set of attributes.
[GB/T 18391.3-2009, definition 3.3.36]
3.1.5.1
General data element
A data element describing an abstract object class. In specific application scenarios, general data elements can be specialized into a number of specific specification data
yuan.
3.1.5.2
Specified data element
A data element describing a specific object class. Canonical data elements can be generalized into general data elements through abstraction.
3.1.6
Value domain
Set of allowed values
[GB/T 18391.3-2009, definition 3.3.140]
3.1.7
Metadata
Data that defines and describes other data.
[GB/T 18391.3-2009, definition 3.2.18]
3.1.8
Data dictionary
A collection of metadata.
3.1.9
Data set
A collection of data elements in a specific field or topic.
3.1.10
Vocabulary
There is a collection of multiple valid values of a code-type attribute or field.
[GB/T 30107-2013, definition 3.1.54]
3.1.11
Datatype
A collection of distinguishable values. This distinction is characterized by the characteristics of these values and the operations on these values.
[GB/T 18391.3-2009, definition 3.3.53]
3.1.12
Data element representation
The relationship between a data element and its range.
[GB/T 18391.3-2009, definition 3.3.50]
3.1.13
Data element representation class
A class represented by a data element.
[GB/T 18391.3-2009, definition 3.3.51]
3.1.14
Representation class
The type classification of the representation.
[GB/T 18391.3-2009, definition 3.3.126]
3.1.15
Coding system
(Usually) Use short concept identifiers to indicate that the concept is a part of the system, and define a concept representation of a unique concept code set
system.
[GB/T 30107-2013, definition 3.1.10]
3.1.16
Data identifier
The unique identifier of a management item in the registry.
[GB/T 18391.1-2009, definition 3.3.10]
3.1.17
Registration authority
An organization responsible for maintaining a registry.
[GB/T 18391.3-2009, definition 3.3.121]
3.1.18
Registration status
A reference to the status of a management item in the registration life cycle.
[GB/T 18391.3-2009, definition 3.3.125]
3.1.19
Objectidentifier
A globally unique string that identifies an ISO object, consisting of numbers and dots, for example "2.16.840.1.113883.3.1". Correct
The image identifier is a tree structure, the leftmost number represents the root, and the rightmost number represents the leaf.
[HL7 DATA TYPE R2, definition 1.7]
3.2 Abbreviations
The following abbreviations apply to this document.
4 General data element description rules
Common data elements are described by 17 metadata attributes, including 9 common attributes, 4 data element-specific attributes and 4 data element overviews
The unique attributes of Nian are shown in Table 1.
5 General data element representation class
The representation classes of general data elements are shown in Table 2.
6 Metadata identifier generation rules
The metadata identifier is generated by a machine algorithm and does not take the form of leading zero. First, use a random function to generate six random numbers, and then
Check whether the random number generated is repeated. If there are repetitions, regenerate random numbers and check whether they are repeated again until all random numbers are unique.
7 Rules for generating vocabulary concept identifiers
The concepts in the vocabulary are identified by the concept ID. The letters in the concept ID are the first letters and numbers of the English name of the object class to which the concept belongs
It is a meaningless random number, generally six digits, which is unique in this standard. The random number generation rule is the same as the metadata identifier.
8 General data element description
The National Health and Population Information Data Dictionary contains 144 general data elements, which are described below.
8.1 Coding system identifier
A unique identifier assigned to a specific coding system. This identifier is unique within the national health information metadata management system.
When the user needs to classify, name and identify the description object (such as entity) in the form of code, this data element is used to point to the coding system used.
The coding system defines the value range of the codable attributes. The same attribute can use different coding systems, and the code
The form and meaning are only guaranteed to be unique within a coding system. In order to avoid different users from using different
The code system describes the semantic confusion of the codable attributes of the same object class, and the code must be used while communicating
This data element clearly and uniquely points to the coding system used.
This data element is applicable to the description of all coding system identifiers in this data dictionary.
This data element is used in conjunction with all code data elements (CS, CV, CE, CD) in this data dictionary.
All coding systems should have unique identifiers within the scope of their use. For example, HL7 defines and
The maintained vocabulary domain and its designated external terminology systems such as LOINC, ICD, SNOMED CT, etc. have identifiers for use in the development of documents and other artifacts.
8.2 Coding system name
The name given to a specific coding system expresses the theme and content of the coding system.
Because of the flexibility of natural language, the coding system name must be used in conjunction with the coding system identifier, that is, with the help of
The uniqueness of the identifier avoids possible misunderstanding when the user refers to the encoding system used by the name.
The coding system can be used to define the range of all codeable attributes, and different coding systems can be used for the same attribute
The form and meaning of the code are only guaranteed to be unique within a coding system. To avoid different uses
When users use different coding systems to describe the same coding attribute, the semantic confusion must be explained while using the code.
This data element is applicable to the definition of all coding system names in this dictionary.
The unit of measurement may be represented by different symbols in different coding systems. Use a symbol for a unit of measurement
At the time, the identifier and name of the coding system that defines the symbol should be stated.
For data consistency, it is recommended to use the same unit of measurement for the same type of entity to express its quantity, or
At least establish a quantitative conversion relationship between different measurement units for the same type of entity, that is, use UCUM.
8.4 Currency unit code
8.5 Entity Class Code
If codes are used to represent all objective entities, the amount of codes will be extremely large. Therefore, use the class code first
Carry out a high-level macro classification of entities, define an appropriate context for each entity instance, and then proceed
In one step, use the Entity.code property to assign a code value to each entity instance.
|