US$479.00 · In stock Delivery: <= 4 days. True-PDF full-copy in English will be manually translated and delivered via email. WS/T 545-2017: Technical specification for telemedicine information system Status: Valid
Standard ID | Contents [version] | USD | STEP2 | [PDF] delivered in | Standard Title (Description) | Status | PDF |
WS/T 545-2017 | English | 479 |
Add to Cart
|
4 days [Need to translate]
|
Technical specification for telemedicine information system
| Valid |
WS/T 545-2017
|
PDF similar to WS/T 545-2017
Basic data Standard ID | WS/T 545-2017 (WS/T545-2017) | Description (Translated English) | Technical specification for telemedicine information system | Sector / Industry | Health Industry Standard (Recommended) | Classification of Chinese Standard | C07 | Word Count Estimation | 19,186 | Date of Issue | 2017-07-25 | Date of Implementation | 2017-12-01 | Regulation (derived from) | State-Health-Communication (2017) 8 | Issuing agency(ies) | National Health and Family Planning Commission of the People's Republic of China |
WS/T 545-2017: Technical specification for telemedicine information system---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.
Technical specification for telemedicine information system
ICS 11.020
C 07
WS
People's Republic of China Health Industry Standard
Technical Specifications of Telemedicine Information System
2017-07-25 released
2017-12-01 implementation
Issued by the National Health and Family Planning Commission of the People's Republic of China
Table of contents
Foreword...II
1 Scope...1
2 Normative references...1
3 Terms and definitions...1
4 Abbreviations...1
5 General technical requirements...2
6 System Function...5
7 Information Resource Specification...8
8 Infrastructure specifications...9
9 Safety regulations...13
10 Performance requirements...16
Foreword
This standard was drafted in accordance with the rules given in GB/T 1.1-2009.
The main drafting organizations of this standard. China-Japan Friendship Hospital, the First Affiliated Hospital of Zhengzhou University, the Statistical Information Center of the National Health and Family Planning Commission, Guizhou
State and Provincial Health Information Center, Zhejiang Digital Medical and Health Technology Research Institute.
The main drafters of this standard. Xu Shuqiang, Zhang Tieshan, Yang Kun, Zhao Jie, Zhai Yunkai, Tang Xuejun, Zhang Lili, Yan Gang, Lan Wenyue, Chen
Maohua, Sheng Huiping.
Technical Specifications of Telemedicine Information System
1 Scope
This standard specifies the overall technical requirements, system functions, information resource specifications, infrastructure specifications, and security regulations for telemedicine information systems.
Fan and performance requirements, etc.
This standard applies to the medical institution of one party (hereinafter referred to as the inviting party) inviting other medical institutions (hereinafter referred to as the inviting party) to use the Internet
Communication and computer technology are medical activities that provide technical support to patients and medical staff in this medical institution.
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 article
Pieces. For undated references, the latest version (including all amendments) applies to this document.
WS 363 Health Information Data Metadirectory (all parts)
WS 364 Health information data element range code (all parts)
WS 365 Basic data set of health records of urban and rural residents
WS 445 Basic data set of electronic medical records (all parts)
WS/T 447-2014 Technical specifications for hospital information platform based on electronic medical records
WS/T 500 (all parts) Specification for shared electronic medical records
WS/T 529 Basic functional specification of telemedicine information system
The basic structure and data standards of electronic medical records (for trial implementation), former Ministry of Health,.2009
3 Terms and definitions
The terms and definitions defined in WS/T 529 apply to this document.
4 Abbreviations
The following abbreviations apply to this document.
5 General technical requirements
5.1 Overall framework
The overall framework of the telemedicine information system mainly includes the application of the telemedicine information system, the services of the telemedicine information system, and information resources.
Source center, information exchange layer, basic measures, standard specifications, and security assurance are shown in Figure 1.
Figure 1 The overall framework of the telemedicine information system
5.2 Technical architecture
The technical framework of the telemedicine information system is shown in Figure 2.
Figure 2 Technical architecture of telemedicine information system
5.2.1 Application layer
The application layer of the telemedicine information system consists of telemedicine service applications and telemedicine supervision. Through a unified telemedicine service portal
Access, which can realize remote consultation, remote image diagnosis, remote pathological diagnosis, remote ECG diagnosis, remote monitoring, remote surgery teaching, remote
For remote medical services such as medical education, each application can realize "plug and play"; through the functions provided by the remote medical supervision module,
Various monitoring functions such as analysis, statistics, and decision-making of the operation of telemedicine systems at all levels.
5.2.2 Service layer
The services provided by the service layer of the telemedicine information system include registration services, remote services, storage services and electronic medical record file services.
It is used to directly interact with the telemedicine business logic layer through the telemedicine data transmission object, and centralize the processing of the business logic of the system.
Message exchange and message transmission between services run through each service layer. Message exchange between services needs to be based on common exchange standards and industry exchanges.
Change the standard.
5.2.3 Resource layer
The resources provided by the resource layer of the telemedicine information system include structured data, unstructured (document, audio and video data) data, structure
Document data, application service resources, etc. Mainly used to support the management and coordination of cross-regional telemedicine work; support cross-regional telemedicine
Construction of the effectiveness of medical treatment work; assisting decision-making to carry out data statistical analysis services; providing support for the National Telemedicine Supervision and Resource Service Center and various districts
Regional telemedicine supervision and resource service centers, as well as the interconnection between regional telemedicine supervision and resource service centers, provide information services
Service.
5.2.4 Switch and access layer
5.2.4.1 Telemedicine information resource exchange layer
Including. Enterprise Service Bus ESB, Service Integration SMP, General File Transfer GTP, Data Integration ETL, Unified Media Control Unit
MCU. According to the business process, the information exchange layer exchanges data with other information systems through data interfaces or message transmission to achieve information sharing.
Sharing, data reporting and other functions. Mainly used to meet the information exchange and collaborative application of clinical information across hospitals and regions; for medical service funding
Source registration, application, authorization, management, and monitoring to realize service-based information resource sharing and exchange;
Data standard business information collection, and file-based data exchange services for external systems; used to meet the requirements of telemedicine data warehouse construction
Data integration requirements for data collection, processing, and conversion in the design process; used to meet the cross-hospital and cross-regional interaction of audio and video information,
In accordance with the requirements of peacetime and wartime integration, the video conference system for emergency command of public health emergencies is integrated. Solve the problem that hospitals rely on regional telemedicine supervision
Information interconnection and intercommunication in the process of carrying out telemedicine business with the resource service center.
5.2.4.2 Telemedicine information resource access layer
5.2.4.2.1 Emergency command system
The telemedicine information system is connected to the emergency command system, and the video site is used to connect to the hospital network to provide audio and video of the scene and the treatment process
Dynamic information, realize the linkage of information sharing and handling in emergency response, which can not only enable patients to obtain diagnosis and treatment through remote video, but also help doctors
The nurses report the latest situation of the patient to the command center at any time and analyze any potential new diseases.
5.2.4.2.2 Medical and health information system
Mainly include electronic medical record system, hospital information system, laboratory information system, clinical information system, ECG diagnosis system, image diagnosis
Systems, pathological diagnosis systems and other medical information systems. Through the connection of telemedicine information system and medical information system, cross-hospital
Information sharing and business collaboration between.
The telemedicine information system is connected with the regional health information platform to provide real-time information on telemedicine supervision and business services, and share the original health information.
Health archives and electronic medical record information enable the regional health information platform to have comprehensive management functions for telemedicine services.
For example, a medical institution has established a hospital information integration platform for data sharing, and it will be integrated with the telemedicine information system through the platform mechanism.
Docking, reducing the number of data interfaces, and realizing information sharing and business collaboration across hospitals.
5.2.4.2.3 Medical information collection equipment
Medical information collection equipment mainly includes multi-parameter vital signs monitors, digital imaging equipment, digital electrocardiographs, ventilators and other
Other medical information collection equipment is mainly used to collect patient's vital signs, blood sugar, blood pressure and other data.
5.3 Software architecture requirements
The basic requirements include.
--The software architecture of the telemedicine information system should be based on the idea of service-oriented architecture; the system adopts the B/S model structure, rooted in
According to different application environments, the system is deployed with network optimization schemes;
--Comply with existing standard framework agreements and adopt industry agreements; adopt open standard design and be compatible with other medical systems and equipment
Prepare; meet future development and leave sufficient room for expansion for future business expansion;
--All components closely related to SOA reusability, such as service interfaces, must adopt mature technical standards and specifications; there is no final
The factual standards or norms of the verdict shall be used as an optional technical reference;
--The telemedicine information system requires message routing function, can have business process management, and can support telemedicine business flow
Workflow with programming and manual participation.
5.4 Software technical requirements
5.4.1 Basic requirements
The basic requirements include.
--The system should support business operations related to telemedicine services and may have the function of supporting business process orchestration;
--The system should support information sharing and interaction with the information systems of various hospitals, and have medical information and data access functions;
--The system should provide management tools that can manage all business system integration nodes and monitor the development of the entire telemedicine business;
--The system should support user authorization and authentication, support data tamper-proof and privacy data confidentiality, and support business process tracking and auditing,
System log recording and viewing, support message reliability transmission and message tracking, etc.; the system has a good backup function to meet
High reliability requirements;
--Single sign-on. Provides secure integration of various application systems and data. Users only need to log in once to access other related applications.
Use systems and databases;
--The telemedicine information system should provide a secondary development environment and provide the packaging of basic public business components.
5.4.2 Interaction information requirements
The interactive information should support the relevant health data standards promulgated by countries such as WS 363 and WS 364.
5.5 Integration capability requirements
Specific requirements include.
--Take Web Service technology as the preferred technology for SOA service development technology, and require compliance with WS -I Basic Profile 1.0
Relevant guidelines;
--The system should support mainstream international and domestic standards and norms for the exchange of health information;
--The security management of Web Service-based services should follow the WS -Security specification in the Web Service service specification, other
The form of service must also provide security.
6 System function
6.1 Basic functions
6.1.1 Basic requirements
Basic functions should include registration management services for patients, medical service personnel, medical and health institutions (departments), and medical and health terms.
The system shall provide unique identification for these entities. Form various registries for various entities (such as patient registry, medical service personnel registration)
Database, institution registry, term and dictionary registry), each registry has the ability to manage and solve the problem of a single entity having multiple identifiers.
6.1.2 Patient Registration Service
Basic functions include.
--With the function of new patient registration;
--With patient information update function;
-Possess the function of invalidating patient identity
-Possess the patient identity merge function
--With patient information query function.
6.1.3 Medical service personnel registration service
Basic functions include.
-Possess the new medical and health personnel registration function;
--Have medical and health personnel information update function;
--With the function of invalidating the identity of medical and health personnel
--With the function of merging medical and health personnel's identity;
--Have medical and health personnel information inquiry function.
6.1.4 Registration of medical and health institutions (departments)
Basic functions include.
-Possess the registration function of newly-added medical and health institutions (departments);
--Have the information update function of medical and health institutions (departments);
--Have the function of stopping medical and health institutions (departments);
--With information query function of medical and health institutions (departments).
6.1.5 Registration of medical and health terms
Basic functions include.
--With the function of batch import and export of terms and dictionaries;
-Possess the classification browsing function of terms and dictionaries;
--Have the function of maintaining the relationship between terminology and dictionary;
-Version management with terms and dictionaries;
-Maintain the mapping relationship between terms and dictionaries;
--It has the function of synchronizing terms and dictionaries with other systems.
6.2 Telemedicine data integration function
6.2.1 Data collection function
Features include.
--Support the collection of medical data, and obtain data from medical application systems or databases.
--Support to obtain the patient's image data according to the DICOM standard, and perform storage, reproduction and corresponding post-processing operations.
--Support the conversion of pathological slices into virtual digital slices composed of complete digital images, including at least 20x and 40x microscopic images.
Support pathological virtual digital slice upload.
--Support to collect electrophysiological data from electrophysiological examination equipment, and carry out non-destructive data transmission, storage and reproduction. Electrophysiological map support
Transmission of electrophysiological examination data through Internet, mobile network, telephone line, etc. Electrophysiological map data can be stored as XML,
Common data formats such as DICOM.
--Support the real-time transmission of vital signs data such as bedside monitors.
--In this specification, services and interfaces related to data collection are temporarily not specified.
6.2.2 Application function
Basic functions include.
--Application form submission
--Have the application form receiving function;
-Possess the application form inquiry function.
6.3 Remote medical data storage service function
According to the classification of telemedicine case data, storage services include. basic patient information storage, electronic medical record information storage,
Health file information storage library, consultation information storage library, image data storage library, teaching resource storage library. Basic functions include.
--With the function of receiving documents, images and video data;
--With the function of registering documents, images and video data to the index library;
--It has the function of providing users with documents, images, and video data.
6.4 Remote medical data management function
6.4.1 Data management function
Manage the patient's entire course of disease files, including file creation, cancellation, and territorial change.
6.4.2 Document registration function
Document registration maintains the metadata of each registered document according to the content of the document, and includes the address stored in the document library. Document registration
Documents (collections) can be returned based on specific query conditions of document users.
6.4.3 Event registration function
In order to realize the sharing and exchange of case data and information in the telemedicine information system, it is necessary to take the telemedicine patient as the unit to obtain information from the patient
Register the event information of health service activities and establish an event catalog. Each entry in the directory consists of key information describing the event,
In actual operation, the metadata related to the event in the document should be extracted for registration. At the same time, the event information will be used as the relationship between the patient and the document.
The association relationship of the user can easily obtain related documents through events.
6.4.4 Index Service Function
Basic functions include.
--With static document registration function, static documents include. patient's case data information, and document items involved in event information
Record and summary information;
--Support the function of querying and displaying related medical static document indexes based on medical events or patient information.
6.5 Telemedicine data retrieval function
It is used to browse and consult various data such as documents, image pictures, medical records, etc.
6.5.1 Data assembly service function
The assembly service generates multiple patient data result sets by calling different system components, and combines these result sets into a certain output grid
formula.
6.5.2 Data standardization service function
The standardization service modifies the specific input string into a code string conforming to the standardization. Both the format and actual meaning of the data can be converted.
6.5.3 Data access service function
The data access service provides query and access services to the data of a single patient's case file or document set.
6.6 Information feedback function of telemedicine results
Basic functions include.
--With the function of receiving result information;
-Possess the result information inquiry function.
6.7 Information security and privacy protection functions
6.7.1 User management and authorization services
Basic functions include.
--With user role creation function;
--With user authorization function;
--With the function of customizing access rules and accessing data according to the rules;
-Possess the function of recording user authority operation log.
6.7.2 Information Security Service
The telemedicine information system should provide a unified information security service, and the user can ensure that the system passes authentication and authorization when interacting with information
information security.
6.7.3 Privacy protection service
The telemedicine information system should provide patient privacy data protection services.
6.7.4 Audit trail service
The telemedicine information system should provide a log of all information access or information update operations, and provide data audit and operation tracking services.
Service.
7 Information Resource Specification
7.1 Basic Information Library
7.1.1 Basic requirements
The basic information database of the telemedicine information system includes basic patient information, medical and health service personnel information, and medical institution (department) information.
Information, medical and health terms. The basic information database is generated by the registration service of the telemedicine information system, which provides a unified, complete and accurate
Accurate basic information and provide unique identification for these entities.
7.1.2 Basic patient information database
The basic patient information complies with WS 445, including data elements such as client identification, demography, contact, address, communication, and medical insurance.
7.1.3 Information database of medical and health service personnel
The registration information of medical and health service personnel complies with WS 445, including the data element of health service personnel.
7.1.4 Information database of medical and health institutions (departments)
The information of medical and health institutions (departments) follows WS 445, including data elements of health service institutions.
7.1.5 Medical and health terminology and dictionary library
The terminology and dictionary database of the telemedicine information system follow the relevant health data standards promulgated by countries such as WS 363, WS 364, and WS 445.
Refer to the relevant data standards of the international health industry.
7.2 Telemedicine data database
7.2.1 Document Repository
The document repository is responsible for storing clinical documents based on activities and standards in a clear, safe and durable manner. File storage
The contents of the repository comply with WS 365 and WS 445.
According to the content type of clinical documents, the document repository selects the appropriate document registration to register these documents, and the document retrieval
Request a response. Electronic medical record sharing documents comply with WS/T 500.
7.2.2 Image Storage Library
The medical image storage requirements fully comply with the current international standards such as DICOM3.0, HL7, etc., and comply with the IHE framework. The entire system
It has high security, high reliability, high compatibility and sustainable scalability. Realize image receiving, transfer, and printing, support image
Lossy and lossy compression storage mode.
7.2.3 Video Storage Library
The video storage library (including image storage and post-processing, report and management of the case library) must be completely based on the WEB architecture to facilitate future
Maintenance and distance education.
In terms of data management, it should have greater flexibility. It can centrally manage all the materials in the distance education project, and it can also
Divided by type or subject and managed separately, the large material library can be divided into multiple small material libraries.
7.2.4 Document Registry
The document registry shall provide document index information in the document repository, and the content shall comply with the original Ministry of Health’s Basic Architecture and Data Standards for Electronic Medical Records
(Trial)" H.01 document label, H.02 service object label, H.03 demography, H.04 contact,
H.05 address, H.06 communication, H.07 medical insurance, H.08 health service organization, H.09 health service provider, H.10 event summary data group.
According to the content type of clinical documents, there can be a set of different types of registries in the document registry.
Used when storing.
8 Infrastructure specifications
8.1 Telemedicine network
8.1.1 The principles of network construction are as follows.
--Reliability. The stability and reliability of the network system is the key guarantee for the normal operation of the application system.
Use network products, reasonably design network architecture, formulate reliable network backup strategies, and ensure that the network has the ability to self-heal from failures.
Maximum support for the normal operation of the system;
--Openness. It supports open protocols such as international general standard netwo...
Tips & Frequently Asked Questions:Question 1: How long will the true-PDF of WS/T 545-2017_English be delivered?Answer: Upon your order, we will start to translate WS/T 545-2017_English as soon as possible, and keep you informed of the progress. The lead time is typically 2 ~ 4 working days. The lengthier the document the longer the lead time. Question 2: Can I share the purchased PDF of WS/T 545-2017_English with my colleagues?Answer: Yes. The purchased PDF of WS/T 545-2017_English will be deemed to be sold to your employer/organization who actually pays for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. If you need your currency to be printed on the invoice, please write an email to [email protected]. In 2 working-hours, we will create a special link for you to pay in any currencies. Otherwise, follow the normal steps: Add to Cart -- Checkout -- Select your currency to pay.
|