CN111292820B - Medical informatization data standard system rapid construction system, method and server - Google Patents

Medical informatization data standard system rapid construction system, method and server Download PDF

Info

Publication number
CN111292820B
CN111292820B CN202010383216.6A CN202010383216A CN111292820B CN 111292820 B CN111292820 B CN 111292820B CN 202010383216 A CN202010383216 A CN 202010383216A CN 111292820 B CN111292820 B CN 111292820B
Authority
CN
China
Prior art keywords
medical
standard
service
primary
business
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN202010383216.6A
Other languages
Chinese (zh)
Other versions
CN111292820A (en
Inventor
林德南
郑静
曲建明
高忠军
蒲立新
徐一彬
何明杰
王爽
范计朋
刘先波
周滨
李春红
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Shenzhen Medical Science Information Center
CHENGDU GOLDISC UESTC MULTIMEDIA TECHNOLOGY CO LTD
Original Assignee
Shenzhen Medical Science Information Center
CHENGDU GOLDISC UESTC MULTIMEDIA TECHNOLOGY CO LTD
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Shenzhen Medical Science Information Center, CHENGDU GOLDISC UESTC MULTIMEDIA TECHNOLOGY CO LTD filed Critical Shenzhen Medical Science Information Center
Priority to CN202010383216.6A priority Critical patent/CN111292820B/en
Publication of CN111292820A publication Critical patent/CN111292820A/en
Application granted granted Critical
Publication of CN111292820B publication Critical patent/CN111292820B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H10/00ICT specially adapted for the handling or processing of patient-related medical or healthcare data
    • G16H10/60ICT specially adapted for the handling or processing of patient-related medical or healthcare data for patient-specific data, e.g. for electronic patient records
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
    • GPHYSICS
    • G16INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16HHEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H80/00ICT specially adapted for facilitating communication between medical practitioners or patients, e.g. for collaborative diagnosis, therapy or health monitoring

Landscapes

  • Health & Medical Sciences (AREA)
  • Engineering & Computer Science (AREA)
  • Medical Informatics (AREA)
  • Epidemiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Public Health (AREA)
  • Biomedical Technology (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Pathology (AREA)
  • Medical Treatment And Welfare Office Work (AREA)

Abstract

The invention discloses a system, a method and a server for quickly constructing a medical informatization data standard system, wherein the system for quickly constructing the medical informatization data standard system comprises a plurality of medical service ends, a primary service form is established, the attributes of each data item in the service form are perfected and submitted to the medical standard ends; the medical standard end establishes a standard form, the standard end matches the standard form with the primary business form, a business domain data set of the primary business form is perfected, each data item attribute in the business form is corrected, and a final business form is generated; the medical platform terminals are used for generating a primary medical data acquisition standard business list and sending the primary medical data acquisition standard business list to the standard terminals; and the medical standard terminal corrects the attributes of each data item in the primary medical data acquisition standard business sheet, generates a final medical data acquisition standard business sheet and sends the final medical data acquisition standard business sheet to the medical platform terminal. The invention has the advantage of quickly constructing the medical informatization data standard system.

Description

Medical informatization data standard system rapid construction system, method and server
Technical Field
The invention relates to the technical field of information management, in particular to a system, a method and a server for quickly constructing a medical informatization data standard system.
Background
Standardization is an important condition for realizing medical informatization, and is also a foundation for building medical informatization. The method is a precondition for ensuring interconnection and intercommunication and interoperation of information systems of a hospital, and is also a key for realizing data exchange, information resource sharing and service cooperation. Only through standardized means such as unified technical standards, strict service operation and standard management requirements and the like, the informatization construction can be guaranteed to be rule-based and legal, and an organic whole is formed, so that the smoothness and the sharing of information can be realized.
The current medical health informatization construction has the following standard problems: 1. the complexity of information technology determines the breadth and the system of information standardization. At present, a plurality of standards are issued and implemented, but a proper medical health information standard system cannot be formed, and the phenomena of more dispersed types and non-matching exist. Some release basic standards, have not correspondent operation standards, some have made the technical standard, have not corresponding administrative standard; or only the top layer is standard, and the bottom layer and the middle layer which are matched are not standard, so that the phenomena of loosening, messiness and fragmentation are formed. Lack of standard management of the whole elements, the whole flow and the whole process results in no proper reference execution. So that the situation is not taken. Meanwhile, Shenzhen currently lacks an electronic medical record data set, data elements, value domain codes and data exchange standards, and is difficult to support the construction of an electronic medical record library; the management standard, the technical standard, the data standard and the operation and maintenance standard of public health and social health general medical treatment are lacked, and the electronic health record data management in the whole life cycle is difficult to form; the requirement of interconnection and intercommunication of inspection and inspection information is difficult to meet due to the lack of inspection and inspection project coding standards. 2. The standardization of health information is a huge and complex system project, and although a great number of various standards are established and released in recent years, few standards which restrict the rapid development of hospital informatization are solved. The number of issued standards is large, and the standards capable of repairing and solving urgent problems are few. Particularly, the current relevant standards of information exchange and information sharing are a problem which troubles the 'old and difficult' of hospital information standardization, and are still pending, and the information exchange standards which are interconnected and intercommunicated are not put at the important position of standard research and development in the past years, so that the problems of regional medical service collaboration, cross-border application and the like are influenced. Some medical institutions adopt local standards, and some institutions adopt countries, which brings problems to the practical application of the standards. Maintaining the uniformity of the standard version is an important prerequisite for promoting the informatization work of medical care and health.
Disclosure of Invention
The invention aims to provide a system and a method for quickly constructing a medical health informatization data standard system, which are used for establishing an interconnected and intercommunicated information exchange standard based on standard management of full elements, full flow and full process to form electronic health archive data management of a full life cycle and have the advantage of quickly constructing the medical informatization data standard system.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows: the method for quickly constructing the medical informatization data standard system comprises the following steps,
s1: the medical service user sorts the service domain data set according to the actual service flow of the system, establishes a primary service form, perfects the attributes of each data item in the service form, submits the improved primary service form to a medical standard end through a medical service end, and executes S2;
s2: the medical standard end establishes a standard form according to the service standard requirement corresponding to the medical service user, the standard end matches the standard form with the primary service form, the standard end interacts with the medical service end, the service domain data set of the primary service form is perfected, the attribute of each data item in the service form is corrected, a final service form is generated, and the medical service end sends the final service form to the medical platform end and executes S3;
s3: the medical platform side completes the service domain data set of the final service form according to the construction condition of the medical platform or the cooperative needs of medical services, generates a primary medical data acquisition standard service form and sends the primary medical data acquisition standard service form to the standard side, and S4 is executed;
s4: matching the standard form with the primary medical data acquisition standard business sheet by the medical standard end, interacting the standard end with the medical platform end, correcting the attributes of each data item in the primary medical data acquisition standard business sheet to generate a final medical data acquisition standard business sheet, sending the final medical data acquisition standard business sheet to the medical service end by the medical platform end, and executing S5;
s5: and the medical service end and the medical platform end collect medical information according to the final medical data collection standard service sheet.
Further, each data item attribute in the S1 includes a data element identifier (DE), a definition, a length, a data type, and an allowable value.
Further, the step S2 specifically includes the following steps,
s21: the medical standard end establishes a standard form according to the service standard requirement corresponding to the medical service user, and executes S22;
s22: matching the standard form with the primary business form by the medical standard terminal, judging whether the attributes of each data item in the business form are abnormal or not, if so, executing S23, otherwise, executing S24;
s23: the medical standard terminal counts the data items with abnormal attributes in the service form, generates a service error report and sends the service error report to the medical service terminal, the medical service terminal modifies the data items in the service form according to the service error report, sends the modified primary service form to the standard terminal, and executes S24;
s24: and the medical standard end matches the standard form with the primary business form, perfects the business domain data set of the primary business form, generates a final business form and sends the final business form to the medical business end, and S3 is executed.
Further, the S4 includes the following steps,
s41: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S43;
s42: the medical standard terminal counts data items with abnormal attributes in the primary medical data acquisition standard business sheet, generates a platform error report and sends the platform error report to the medical business terminal, the medical platform terminal modifies the primary medical data acquisition standard business sheet according to the platform error report, sends the modified primary medical data acquisition standard business sheet to the standard terminal, and executes S43;
s43: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S44;
s44: and the medical standard terminal generates a final medical data acquisition standard business sheet and sends the final medical data acquisition standard business sheet to the medical platform terminal, and the medical platform terminal sends the final medical data acquisition standard business sheet to the medical service terminal to execute S5.
The medical informatization data standard system rapid construction system comprises,
each medical service user sorts a service domain data set according to the actual service flow of the system, establishes a primary service form, perfects the attribute of each data item in the service form, and submits the perfected primary service form to a medical standard end through a corresponding medical service end;
the medical standard end is used for establishing a standard form according to a service standard requirement corresponding to a medical service user, the standard end matches the standard form with the primary service form, the standard end interacts with the medical service end, a service domain data set of the primary service form is perfected, each data item attribute in the service form is corrected, a final service form is generated, and the medical service end sends the final service form to one or more corresponding medical platform ends;
the medical platform terminals are used for perfecting the service domain data set of the final service form according to the construction condition of the medical platform or the cooperative needs of medical services, generating a primary medical data acquisition standard service form and sending the primary medical data acquisition standard service form to the standard terminal;
the medical standard end matches the standard form with the primary medical data acquisition standard business sheet, the standard end interacts with the medical platform end, the attributes of all data items in the primary medical data acquisition standard business sheet are corrected, and a final medical data acquisition standard business sheet is generated and sent to the medical platform end;
the medical platform end is also used for sending the final medical data acquisition standard business sheet to the corresponding medical platform end;
and the interaction end is used for supporting the interaction between the plurality of medical service ends and the medical standard end, the interaction between the plurality of medical platform ends and the medical standard end, and the interaction between the plurality of medical service ends and the plurality of medical platform ends.
Further, the medical standard terminal generates a final business form by adopting the following method,
s21: matching the standard form with the primary business form by the medical standard terminal, judging whether the attributes of each data item in the business form are abnormal or not, if so, executing S22, otherwise, executing S23;
s22: the medical standard terminal counts the data items with abnormal attributes in the service form, generates a service error report and sends the service error report to the medical service terminal, a medical service user modifies the data items in the service form according to the service error report through the medical service terminal, sends the modified primary service form to the standard terminal, and executes S23;
s23: and the medical standard end matches the standard form with the primary business form, perfects the business domain data set of the primary business form, generates a final business form and sends the final business form to the medical business end.
Further, the medical standard terminal generates a final medical data acquisition standard business sheet by adopting the following method,
s41: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S43;
s42: the medical standard terminal counts data items with abnormal attributes in the primary medical data acquisition standard business sheet, generates a platform error report and sends the platform error report to the medical business terminal, a medical platform user modifies the primary medical data acquisition standard business sheet according to the platform error report through the medical platform terminal, sends the modified primary medical data acquisition standard business sheet to the standard terminal, and executes S43;
s43: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S44;
s44: and the medical standard terminal generates a final medical data acquisition standard business sheet and sends the final medical data acquisition standard business sheet to the medical platform terminal, and the medical platform terminal sends the final medical data acquisition standard business sheet to the medical service terminal.
Furthermore, the interaction end supports a plurality of medical Service ends and medical standard ends, a plurality of medical platform ends and medical standard ends, and a plurality of medical Service ends and a plurality of medical platform ends by adopting a Web Service technology.
The medical informatization data standard system quickly constructs a server, including,
the interaction unit is used for interacting with the external user side, receiving a primary service form uploaded by the external user side, a modified primary service form, a primary medical data acquisition standard service sheet and a modified primary medical data acquisition standard service sheet, and transmitting a service error report, a final service form, a platform error report and a final medical data acquisition standard service sheet to the user side;
the standard establishing unit is used for establishing a standard form according to the service standard requirement corresponding to the medical service user;
and the matching unit is used for matching the standard form with the primary business form, judging whether the attributes of all data items in the business form are abnormal or not and generating a business error report, matching the standard form with the primary medical data acquisition standard business form, judging whether the attributes of all data items in the primary medical data acquisition standard business form are abnormal or not and generating a platform error report, and generating a final medical data acquisition standard business form.
Furthermore, the interaction unit adopts a Web Service technology to interact with an external user terminal.
Drawings
FIG. 1 is a schematic diagram showing steps of a method for rapidly constructing a medical informatization data standard system according to the invention;
FIG. 2 is a schematic diagram of a standard form established by a medical standard terminal according to a service standard requirement corresponding to a medical service user according to the present invention;
FIG. 3 is a schematic diagram of the present invention for illustrating a business error report generated by a medical standards end;
FIG. 4 is a schematic diagram of a medical informatization data standardization system rapid construction system of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention are clearly and completely described below with reference to fig. 1 to 4 of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1
Referring to fig. 1, a method for quickly constructing a medical informatization data standard system comprises the following steps,
s1: the medical service user sorts the service domain data set according to the actual service flow of the system, establishes a primary service form, perfects the attributes of each data item in the service form, submits the improved primary service form to a medical standard end through a medical service end, and executes S2;
it is worth mentioning that the attributes of each data item in S1 include a data element identifier (DE), a definition, a length, a data type, an allowable value, and the like;
s2: the medical standard end establishes a standard form according to the service standard requirement corresponding to the medical service user, the standard end matches the standard form with the primary service form, the standard end interacts with the medical service end, the service domain data set of the primary service form is perfected, the attribute of each data item in the service form is corrected, a final service form is generated, and the medical service end sends the final service form to the medical platform end and executes S3;
it should be noted that, in this embodiment, the service standard corresponding to the medical service user is a related standard issued by the country;
it should be further noted that, in this embodiment, the medical standard end establishes the standard form according to the service standard requirement corresponding to the medical service user, that is, the medical standard end, the plurality of medical service ends and the plurality of medical platform ends interact with each other, determine corresponding standard contents according to the related standards issued by the country, and finally standardize and summarize the form contents of each medical service to form a corresponding data standard system.
S3: the medical platform side completes the service domain data set of the final service form according to the construction condition of the medical platform or the cooperative needs of medical services, generates a primary medical data acquisition standard service form and sends the primary medical data acquisition standard service form to the standard side, and S4 is executed;
s4: matching the standard form with the primary medical data acquisition standard business sheet by the medical standard end, interacting the standard end with the medical platform end, correcting the attributes of each data item in the primary medical data acquisition standard business sheet to generate a final medical data acquisition standard business sheet, sending the final medical data acquisition standard business sheet to the medical service end by the medical platform end, and executing S5;
s5: and the medical service end and the medical platform end collect medical information according to the final medical data collection standard service sheet.
S2 specifically includes the following steps,
in conjunction with fig. 2, S21: the medical standard end establishes a standard form according to the service standard requirement corresponding to the medical service user, and executes S22;
s22: matching the standard form with the primary business form by the medical standard terminal, judging whether the attributes of each data item in the business form are abnormal or not, if so, executing S23, otherwise, executing S24;
s23: the medical standard terminal counts the data items with abnormal attributes in the service form, generates a service error report and sends the service error report to the medical service terminal, the medical service terminal modifies the data items in the service form according to the service error report, sends the modified primary service form to the standard terminal, and executes S24;
s24: and the medical standard end matches the standard form with the primary business form, perfects the business domain data set of the primary business form, generates a final business form and sends the final business form to the medical business end, and S3 is executed.
S4 includes the following steps of,
s41: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S43;
in conjunction with fig. 3, S42: the medical standard terminal counts data items with abnormal attributes in the primary medical data acquisition standard business sheet, generates a platform error report and sends the platform error report to the medical business terminal, the medical platform terminal modifies the primary medical data acquisition standard business sheet according to the platform error report, sends the modified primary medical data acquisition standard business sheet to the standard terminal, and executes S43;
s43: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S44;
s44: and the medical standard terminal generates a final medical data acquisition standard business sheet and sends the final medical data acquisition standard business sheet to the medical platform terminal, and the medical platform terminal sends the final medical data acquisition standard business sheet to the medical service terminal to execute S5.
In this embodiment, the medical service end is a CT room, the medical platform end is a file room, and the primary service form collected by the medical service end includes the name, sex, age, diagnosis date, and diagnosis doctor of the patient. The medical standard end establishes a standard form according to the corresponding service standard requirement, and the medical platform end judges whether to perfect the service domain data set of the final service form according to the data management requirement.
In another embodiment, the medical service end is a medical equipment supplier, the medical platform is a hospital, and the primary service form collected by the medical service end includes equipment name, equipment usage, equipment manufacturer, equipment production date, equipment supplier information, and the like. The medical standard end establishes a standard form according to corresponding service standard requirements, and the hospital judges whether to perfect the service domain data set of the final service form according to management requirements.
Example 2
Referring to fig. 4, a medical informatization data standardization system rapid construction system includes,
each medical service user sorts a service domain data set according to the actual service flow of the system, establishes a primary service form, perfects the attribute of each data item in the service form, and submits the perfected primary service form to a medical standard end through a corresponding medical service end;
it is worth mentioning that each data item attribute includes a data element identifier (DE), a definition, a length, a data type, an allowable value, and the like;
with reference to fig. 2, the medical standard terminal is configured to establish a standard form according to a service standard requirement corresponding to a medical service user, the standard terminal matches the standard form with the primary service form, the standard terminal interacts with the medical service terminal to perfect a service domain data set of the primary service form, modify attributes of each data item in the service form, generate a final service form, and the medical service terminal sends the final service form to one or more corresponding medical platform terminals;
it should be noted that, in this embodiment, the service standard corresponding to the medical service user is a related standard issued by the country;
the medical platform terminals are used for perfecting the service domain data set of the final service form according to the construction condition of the medical platform or the cooperative needs of medical services, generating a primary medical data acquisition standard service form and sending the primary medical data acquisition standard service form to the standard terminal;
the medical standard end matches the standard form with the primary medical data acquisition standard business sheet, the standard end interacts with the medical platform end, the attributes of all data items in the primary medical data acquisition standard business sheet are corrected, and a final medical data acquisition standard business sheet is generated and sent to the medical platform end;
the medical platform end is also used for sending the final medical data acquisition standard business sheet to the corresponding medical platform end;
it should be noted that, in this embodiment, one medical service end may interact with one, two, or more medical platform ends, and one medical platform end may interact with one, two, or more medical service ends.
And the interaction end is used for supporting the interaction between the plurality of medical service ends and the medical standard end, between the plurality of medical platform ends and the medical standard end and between the plurality of medical service ends and the plurality of medical platform ends.
It is worth to be noted that the interaction end supports interaction between a plurality of medical Service ends and medical standard ends, between a plurality of medical platform ends and medical standard ends, and between a plurality of medical Service ends and a plurality of medical platform ends by adopting a Web Service technology.
The medical standards end adopts the following method to generate a final business form,
s21: matching the standard form with the primary business form by the medical standard terminal, judging whether the attributes of each data item in the business form are abnormal or not, if so, executing S22, otherwise, executing S23;
s22: the medical standard terminal counts the data items with abnormal attributes in the service form, generates a service error report and sends the service error report to the medical service terminal, a medical service user modifies the data items in the service form according to the service error report through the medical service terminal, sends the modified primary service form to the standard terminal, and executes S23;
s23: and the medical standard end matches the standard form with the primary business form, perfects the business domain data set of the primary business form, generates a final business form and sends the final business form to the medical business end.
The medical standard terminal generates a final medical data acquisition standard business sheet by adopting the following method,
s41: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S43;
s42: the medical standard terminal counts data items with abnormal attributes in the primary medical data acquisition standard business sheet, generates a platform error report and sends the platform error report to the medical business terminal, a medical platform user modifies the primary medical data acquisition standard business sheet according to the platform error report through the medical platform terminal, sends the modified primary medical data acquisition standard business sheet to the standard terminal, and executes S43;
s43: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S44;
s44: and the medical standard terminal generates a final medical data acquisition standard business sheet and sends the final medical data acquisition standard business sheet to the medical platform terminal, and the medical platform terminal sends the final medical data acquisition standard business sheet to the medical service terminal.
In this embodiment, the medical service end is a CT room, the medical platform end is a file room, and the primary service form collected by the medical service end includes the name, sex, age, diagnosis date, and diagnosis doctor of the patient. The medical standard end establishes a standard form according to the corresponding service standard requirement, and the medical platform end judges whether to perfect the service domain data set of the final service form according to the data management requirement.
In another embodiment, the medical service end is a medical equipment supplier, the medical platform is a hospital, and the primary service form collected by the medical service end includes equipment name, equipment usage, equipment manufacturer, equipment production date, equipment supplier information, and the like. The medical standard end establishes a standard form according to corresponding service standard requirements, and the hospital judges whether to perfect the service domain data set of the final service form according to management requirements.
Example 3
The medical informatization data standard system quickly constructs a server, including,
the interaction unit is used for interacting with the external user side, receiving a primary service form uploaded by the external user side, a modified primary service form, a primary medical data acquisition standard service sheet and a modified primary medical data acquisition standard service sheet, and transmitting a service error report, a final service form, a platform error report and a final medical data acquisition standard service sheet to the user side;
it should be noted that the interaction unit interacts with the external user end by using the Web Service technology.
The standard establishing unit is used for establishing a standard form according to the service standard requirement corresponding to the medical service user;
and the matching unit is used for matching the standard form with the primary business form, judging whether the attributes of all data items in the business form are abnormal or not and generating a business error report, matching the standard form with the primary medical data acquisition standard business form, judging whether the attributes of all data items in the primary medical data acquisition standard business form are abnormal or not and generating a platform error report, and generating a final medical data acquisition standard business form.
The matching unit generates a final medical data acquisition standard business form by adopting the following method,
s22: matching the standard form with the primary business form by the medical standard terminal, judging whether the attributes of each data item in the business form are abnormal or not, if so, executing S23, otherwise, executing S24;
s23: the medical standard terminal counts the data items with abnormal attributes in the service form, generates a service error report and sends the service error report to the medical service terminal, the medical service terminal modifies the data items in the service form according to the service error report, sends the modified primary service form to the standard terminal, and executes S24;
s24: matching the standard form with the primary business form by the medical standard end, perfecting a business domain data set of the primary business form, generating a final business form, sending the final business form to the medical business end, and executing S3;
s3: the medical platform side completes the service domain data set of the final service form according to the construction condition of the medical platform or the cooperative needs of medical services, generates a primary medical data acquisition standard service form and sends the primary medical data acquisition standard service form to the standard side, and S41 is executed;
s41: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S43;
s42: the medical standard terminal counts data items with abnormal attributes in the primary medical data acquisition standard business sheet, generates a platform error report and sends the platform error report to the medical business terminal, a medical platform user modifies the primary medical data acquisition standard business sheet according to the platform error report through the medical platform terminal, sends the modified primary medical data acquisition standard business sheet to the standard terminal, and executes S43;
s43: matching the standard form with a primary medical data acquisition standard business form by a medical standard terminal, judging whether the attributes of each data item in the primary medical data acquisition standard business form are abnormal, if so, executing S42, and if not, executing S44;
s44: and the medical standard terminal generates a final medical data acquisition standard business sheet.
It should be noted that, in this embodiment, the hardware structure of the processor may include a Central Processing Unit (CPU), and may further include other general purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The controller also includes a memory. The memory may be an internal storage unit of the processor, such as a hard disk or a memory of the processor. The memory may also be an external storage device of the processor, such as a plug-in hard disk provided on the processor, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like. The memory may also include both internal and external storage for the processor. The memory is used for storing computer programs and other programs and data required by the processor. The memory may also be used to temporarily store data that has been output or is to be output.

Claims (5)

1. The method for quickly constructing the medical informatization data standard system is characterized by comprising the following steps,
s1: the medical service user sorts the service domain data set according to the actual service flow of the system, establishes a primary service form, perfects the attributes of each data item in the service form, submits the improved primary service form to a medical standard end through a medical service end, and executes S2;
s2: the medical standard end establishes a standard form according to the service standard requirement corresponding to the medical service user, the standard end matches the standard form with the primary service form, the standard end interacts with the medical service end, the service domain data set of the primary service form is perfected, the attribute of each data item in the service form is corrected, a final service form is generated, and the medical service end sends the final service form to the medical platform end and executes S3;
s3: the medical platform side completes the service domain data set of the final service form according to the construction condition of the medical platform or the cooperative needs of medical services, generates a primary medical data acquisition standard service form and sends the primary medical data acquisition standard service form to the standard side, and S4 is executed;
s4: matching the standard form with the primary medical data acquisition standard business sheet by the medical standard end, interacting the standard end with the medical platform end, correcting the attributes of each data item in the primary medical data acquisition standard business sheet to generate a final medical data acquisition standard business sheet, sending the final medical data acquisition standard business sheet to the medical service end by the medical platform end, and executing S5;
s5: and the medical service end and the medical platform end collect medical information according to the final medical data collection standard service sheet.
2. The method for quickly constructing the standard system of medical informatization data according to claim 1, characterized in that the attributes of each data item in the S1 include data element identifier (DE), definition, length, data type and allowable value.
3. The method for quickly constructing a standardized system of medical information-based data according to claim 2, wherein the step S2 includes the following steps,
s21: the medical standard end establishes a standard form according to the service standard requirement corresponding to the medical service user, and executes S22;
s22: matching the standard form with the primary business form by the medical standard terminal, judging whether the attributes of each data item in the business form are abnormal or not, if so, executing S23, otherwise, executing S24;
s23: the medical standard terminal counts the data items with abnormal attributes in the service form, generates a service error report and sends the service error report to the medical service terminal, the medical service terminal modifies the data items in the service form according to the service error report, sends the modified primary service form to the standard terminal, and executes S24;
s24: and the medical standard end matches the standard form with the primary business form, perfects the business domain data set of the primary business form, generates a final business form and sends the final business form to the medical business end, and S3 is executed.
4. The medical informatization data standard system rapid construction server is characterized by comprising,
the interaction unit is used for interacting with the external user side, receiving a primary service form uploaded by the external user side, a modified primary service form, a primary medical data acquisition standard service sheet and a modified primary medical data acquisition standard service sheet, and transmitting a service error report, a final service form, a platform error report and a final medical data acquisition standard service sheet to the user side;
the standard establishing unit is used for establishing a standard form according to the service standard requirement corresponding to the medical service user;
and the matching unit is used for matching the standard form with the primary business form, judging whether the attributes of all data items in the business form are abnormal or not and generating a business error report, matching the standard form with the primary medical data acquisition standard business form, judging whether the attributes of all data items in the primary medical data acquisition standard business form are abnormal or not and generating a platform error report, and generating a final medical data acquisition standard business form.
5. The medical informatization data standard system rapid construction server according to claim 4, wherein the interaction unit adopts a Web Service technology to interact with an external user terminal.
CN202010383216.6A 2020-05-08 2020-05-08 Medical informatization data standard system rapid construction system, method and server Active CN111292820B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010383216.6A CN111292820B (en) 2020-05-08 2020-05-08 Medical informatization data standard system rapid construction system, method and server

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010383216.6A CN111292820B (en) 2020-05-08 2020-05-08 Medical informatization data standard system rapid construction system, method and server

Publications (2)

Publication Number Publication Date
CN111292820A CN111292820A (en) 2020-06-16
CN111292820B true CN111292820B (en) 2020-08-21

Family

ID=71022716

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010383216.6A Active CN111292820B (en) 2020-05-08 2020-05-08 Medical informatization data standard system rapid construction system, method and server

Country Status (1)

Country Link
CN (1) CN111292820B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114388142B (en) * 2022-03-23 2022-06-21 成都瑞华康源科技有限公司 Value domain code mapping rapid processing method

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102184204A (en) * 2011-04-28 2011-09-14 常州大学 Auto fill method and system of intelligent Web form
CN104461907A (en) * 2014-12-30 2015-03-25 成都金盘电子科大多媒体技术有限公司 Health information data set standard conformance automated testing method and system
CN104991785A (en) * 2015-08-03 2015-10-21 江苏优聚思信息技术有限公司 Standardized clinical data service support system and method
CN108572944A (en) * 2017-11-24 2018-09-25 北京金山云网络技术有限公司 A kind of document structure tree method, apparatus, electronic equipment and storage medium
CN110335647A (en) * 2019-06-21 2019-10-15 上海市精神卫生中心(上海市心理咨询培训中心) A kind of clinical data standards system and standardized data acquisition method
CN110875095A (en) * 2019-09-27 2020-03-10 长沙瀚云信息科技有限公司 Standardized clinical big data center system
CN110957015A (en) * 2019-12-02 2020-04-03 南开大学 Missing value filling method for electronic medical record data

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9844333B2 (en) * 2009-03-24 2017-12-19 International Business Machines Corporation Remote delivery and monitoring of health care
CN102968752A (en) * 2012-11-08 2013-03-13 段缨 Check inspection report push system and method
CN104156415B (en) * 2014-07-31 2017-04-12 沈阳锐易特软件技术有限公司 Mapping processing system and method for solving problem of standard code control of medical data
WO2018169795A1 (en) * 2017-03-13 2018-09-20 Chartspan Medical Technologies, Inc. Interoperable record matching process

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102184204A (en) * 2011-04-28 2011-09-14 常州大学 Auto fill method and system of intelligent Web form
CN104461907A (en) * 2014-12-30 2015-03-25 成都金盘电子科大多媒体技术有限公司 Health information data set standard conformance automated testing method and system
CN104991785A (en) * 2015-08-03 2015-10-21 江苏优聚思信息技术有限公司 Standardized clinical data service support system and method
CN108572944A (en) * 2017-11-24 2018-09-25 北京金山云网络技术有限公司 A kind of document structure tree method, apparatus, electronic equipment and storage medium
CN110335647A (en) * 2019-06-21 2019-10-15 上海市精神卫生中心(上海市心理咨询培训中心) A kind of clinical data standards system and standardized data acquisition method
CN110875095A (en) * 2019-09-27 2020-03-10 长沙瀚云信息科技有限公司 Standardized clinical big data center system
CN110957015A (en) * 2019-12-02 2020-04-03 南开大学 Missing value filling method for electronic medical record data

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
中医医院护理管理信息基本数据集体系框架构建;赵瑜 等;《医学信息学杂志》;20170525;第38卷(第5期);第39-42页 *

Also Published As

Publication number Publication date
CN111292820A (en) 2020-06-16

Similar Documents

Publication Publication Date Title
EP1994484B1 (en) Platform for interoperable healthcare data exchange
CN104240170B (en) It is a kind of realizing the high-end electronic medical records system of intelligent medical treatment
US20060224405A1 (en) System and method for completing treatment authorization request forms
US20030074248A1 (en) Method and system for assimilating data from disparate, ancillary systems onto an enterprise system
US11810676B2 (en) Verified permissioned blockchains
US20060261145A1 (en) Systems and methods for managing electronic prescriptions
CN101803293A (en) Healthcare semantic interoperability platform
CN109947854B (en) Block chain-based electronic medical record processing method, device, equipment and medium
Gazzarata et al. A standardized SOA for clinical data interchange in a cardiac telemonitoring environment
CN104537103A (en) Data processing method and device
CN104205099A (en) A method and system for centralized issue tracking
CN101299265A (en) Method and system for transferring health care data
CN104992393A (en) Electronic diagnosis and treatment sheet generation method under O2O mode and network hospital platform
US10847256B2 (en) System and computer program for healthcare information management in a multi-party healthcare network
CN108595571A (en) A kind of Data Integration management method, device, system and user terminal
CN102129634A (en) Digital certificate management system and digital certificate management method
CN111292820B (en) Medical informatization data standard system rapid construction system, method and server
CN104881438A (en) Network hospital platform, specialist platform, method for requesting emergency specialist consultation based on specialist platform
Liu et al. An integrated e-service model for electronic medical records
CN114519084A (en) Block chain-based medical data inspection method, device, equipment and medium
CN108447548A (en) Patient medical image archiving method and system
Barthell et al. Disparate systems, disparate data: integration, interfaces, and standards in emergency medicine information technology
US20160267230A1 (en) Touchless processing
US20090254369A1 (en) System and method for providing health care services using smart health cards
US20080275733A1 (en) Method for evaluation of patient identification

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant