Page display method, system and equipment for health record data and medium

Abstract

The invention provides a page display method, system and device for health record data and a medium, and belongs to the technical field of data display, the method comprises the steps that an xsl template table, a table name configuration table, a field configuration table and a health record event table are configured in advance, and EHR codes are used for associating the four tables; in response to a front-end query request, analyzing a request event and a request parameter, querying a health record event table according to the request event to determine an EHR code, querying an xsl template table, a table name configuration table and a field configuration table, and determining an xsl template, a table name, a field and a query condition; assembling the determined table name, field and query condition into an executable SQL statement, replacing the parameter in the SQL statement with the request parameter, and executing; and analyzing a query result, assembling the query result into an xml file according to levels, converting the xml file into an html page in combination with an xsl template, and returning the html page to the front end. The development process is simplified, the flexibility and the data security are improved, and the user experience is optimized.

Description

Technical Field

[0001] This application belongs to the technical field of data display, and particularly relates to a method, system, device, and medium for page display of health record data. Background Art

[0002] With the development of medical informatization, electronic health records, as the core component of health big data, have become increasingly important. However, there are many problems in the existing health record systems in terms of data display methods.

[0003] Firstly, the types of health record data are numerous, covering multiple fields such as medical records, examinations and tests, and health check-ups, involving hundreds of business data tables. If a separate display page is developed for each type of file, not only is the workload huge, but it is also difficult to achieve unified management and maintenance. Secondly, traditional methods lack flexibility and cannot dynamically configure new display templates, resulting in poor scalability of the health record system, difficulty in adapting to rapidly changing business requirements, and high maintenance costs. Thirdly, although relevant standards provide a unified specification for data formats, in actual applications, how to efficiently integrate diverse data and dynamically generate display pages is still an urgent problem to be solved.

[0004] Currently, new-generation technologies usually use fixed templates or hard-coded methods for data display. Although this method can meet basic requirements to a certain extent, it cannot adapt to rapidly changing business needs, especially when facing different user groups, different application scenarios, and continuously updated health data types, it is particularly insufficient. Therefore, there is an urgent need for a display page method that can simplify the development process, improve the flexibility of the health record system, and meet users' requirements for intuitive and unified display of health record data. Summary of the Invention

[0005] In a first aspect, an embodiment of this application provides a method for page display of health record data, including the following steps: S1. Pre-configure an xsl template table, a table name configuration table, a field configuration table, and a health record event table for health record data, and establish associations among the four tables using the EHR code; the table name configuration table includes query conditions; S2. Respond to a front-end query request, parse out the request event and request parameters, query the health record event table according to the request event to determine the EHR code, and then query the xsl template table, the table name configuration table, and the field configuration table according to the EHR code to determine the xsl template, table name, fields, and query conditions; S3. Assemble the determined table name, fields, and query conditions into an executable SQL statement, use the request parameters to replace the parameters in the SQL statement, and then execute the SQL query to return the query result; S4. Parse the query results, assemble them into an XML file according to the hierarchy, and then convert them into an HTML page in combination with the XSL template and return it to the front end.

[0006] Further, the specific steps of step S1 are as follows: S11. Pre-configure an XSL template table for the health record data. The XML template table includes XSL template content, EHR code, and XML sample. S12. Pre-configure a table name configuration table for the health record data. The table name configuration table includes EHR code, data table name, element name, and query conditions. S13. Pre-configure a field configuration table for the health record data. The field configuration table includes EHR code, database field name, attribute English name, desensitization rule code, and dictionary code. S14. Pre-configure a health record event table for the health record data. The health record event table includes event classification code, event type, event index, and diagnosis disease name, and establish an association between the health record event table and the EHR code through the event index. S15. Associate the XSL template table, table name configuration table, field configuration table, and health record event table through the EHR code.

[0007] Further, the specific steps of establishing the association between the health record event table and the EHR code through the event index in step S14 are as follows: Construct an event and EHR code association table. The event and EHR code association table includes serial number, event index, EHR code, and EHR name. Associate the health record event table and the EHR code through the event index.

[0008] Further, the specific steps of step S2 are as follows: S21. Receive the query request sent by the front end, and parse the event identifier and request parameters from the query request. The request parameters at least include medical institution code and patient ID. S22. Query the health record event table according to the parsed event identifier to determine the corresponding EHR code. S23. Use the determined EHR code to query the XSL template table, table name configuration table, and field configuration table to obtain the corresponding XSL template content, data table name, query conditions, and database field information.

[0009] Further, the specific steps of step S3 are as follows: S31. Assemble the determined data table name, database field, and query conditions into an executable SQL statement: Use SELECT to guide the database fields, use FROM to guide the data table name, and use WHERE to guide the query conditions; S32. Replace the placeholder in the query condition part of the SQL statement with the request parameter to generate the final SQL query statement; S33. Execute the SQL query statement to obtain the query result, process the query result and return it.

[0010] Further, the processing of the query result in step S33 specifically includes: Determine the corresponding desensitization rule code according to the database field name in the query result; Use the determined desensitization rule code to query the desensitization rule table to determine the desensitization rule, and mask the database field name in the query result according to the desensitization rule.

[0011] Further, the specific steps of step S4 are as follows: S41. Extract the database field value from the query result according to the field mapping relationship in the field configuration table, and determine the corresponding dictionary code; S42. Use the determined dictionary code to query the dictionary code table to determine the dictionary, and use the determined dictionary to encode the corresponding database field value in the query result to complete the query result parsing; S43. According to the hierarchical attribute of the element name in the table name configuration table, assemble the data of the parsed query result into an xml file, and set the node attribute name of the xml file to be the same as the attribute English name in the field configuration table; S44. Obtain the corresponding xsl template from the xml template table according to the EHR code, and convert the assembled xml file according to the xsl template to generate an html page and return it to the front end.

[0012] In a second aspect, an embodiment of the present application further provides a page display system for health record data, including: A configuration management module, used to pre-configure the xsl template table, table name configuration table, field configuration table and health record event table for health record data, and establish associations among the four tables using the EHR code; the table name configuration table includes query conditions; A request parsing module, used to respond to a front-end query request, parse out the request event and request parameters, query the health record event table according to the request event to determine the EHR code, and then query the xsl template table, table name configuration table and field configuration table according to the EHR code to determine the xsl template, table name, field and query conditions; An SQL generation and execution module, used to assemble the determined table name, field and query conditions into an executable SQL statement, perform parameter substitution in the SQL statement using the request parameter, and then execute the SQL query to return the query result; A data conversion module, which is used to parse the query result, assemble it into an xml file according to the hierarchy, and then convert it into an html page in combination with the xsl template and return it to the front end.

[0013] In a third aspect, an embodiment of the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the program, the steps of the method for displaying a page of health record data as described in the first aspect are implemented.

[0014] In a fourth aspect, an embodiment of the present application further provides a storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method for displaying a page of health record data as described in the first aspect are implemented.

[0015] It can be seen from the above technical solutions that the present application has the following advantages: In the method, system, device and medium for displaying a page of health record data provided by the present application, by pre-configuring the xsl template table, table name configuration table, field configuration table and health record event table and establishing associations using EHR codes, it is avoided to separately develop a display page for each type of health record data, reducing the development workload, shortening the development cycle, and improving the development efficiency; enabling the health record system to dynamically generate SQL statements and query data according to different front-end requests, supporting dynamic parameter replacement, so that it can quickly adapt to business changes and the needs of different users, not only reducing the maintenance cost, but also being able to cope with the needs of business expansion and changes; assembling the query result into an xml file according to the hierarchy and converting it into an html page in combination with the xsl template, realizing an intuitive and unified display of health record data, facilitating users to view and understand, improving the user experience, and enabling users to obtain the required information more quickly and conveniently; managing health record data through configuration tables and EHR codes, making the data display logic centralized and easy to manage and maintain uniformly; desensitizing sensitive data in the query result to protect the privacy and data security of patients; and being able to dynamically update relevant configuration tables to support the display of new types of health record data; by reasonably constructing SQL statements and replacing parameters, optimizing the database query process, improving the response speed and performance, not only improving the user experience, but also improving the overall efficiency of the health record system, ensuring the stable operation of the health record system under high load. Description of the Drawings

[0016] To more clearly illustrate the technical solutions of the present application, the accompanying drawings required for the description will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0017] Figure 1 It is a schematic flowchart of the page display method for the health record data of the present invention.

[0018] Figure 2 It is a schematic diagram of the page display system for the health record data of the present invention. Detailed implementation manners

[0019] In the following, the specific steps of the page display method for health record data will be described in detail, and various embodiments of the present disclosure will be described more comprehensively. The present disclosure can have various embodiments, and adjustments and changes can be made therein. However, it should be understood that there is no intention to limit the various embodiments of the present disclosure to the specific embodiments disclosed herein, but the present disclosure should be understood to cover all adjustments, equivalents, and / or alternative solutions that fall within the spirit and scope of the various embodiments of the present disclosure.

[0020] Exemplarily speaking, with the development of medical informatization, electronic health records, as the core component of health big data, are becoming increasingly important. However, there are many problems in the data display methods of existing health record systems.

[0021] First of all, there are a wide variety of health record data, covering multiple fields such as medical records, examinations and tests, and health check-ups, involving hundreds of business data tables. If a separate display page is developed for each type of file, not only is the workload huge, but it is also difficult to achieve unified management and maintenance. Secondly, traditional methods lack flexibility and cannot dynamically configure new display templates, resulting in poor scalability of the health record system, difficulty in adapting to rapidly changing business requirements, and high maintenance costs. Thirdly, although relevant standards provide a unified specification for data formats, in actual applications, how to efficiently integrate diverse data and dynamically generate display pages is still an urgent problem to be solved.

[0022] Currently, new-generation technologies usually use fixed templates or hard-coded methods for data display. Although this method can meet basic needs to a certain extent, it cannot adapt to rapidly changing business requirements, especially when facing different user groups, different application scenarios, and continuously updated health data types, it is particularly insufficient. Therefore, there is an urgent need for a display page method that can simplify the development process, improve the flexibility of the health record system, and meet users' intuitive and unified display requirements for health record data.

[0023] In view of the above problems, this embodiment provides a method for page display of health record data. Through configuration management and dynamic data processing, the development process is simplified, the flexibility and scalability of the health record system are improved, while ensuring data security and privacy, and enhancing the user experience and system performance.

[0024] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all of the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0025] Please refer to Figure 1 The following is a flowchart of the method for page display of health record data in a specific embodiment. The method includes the following steps: S1. Pre-configure an xsl template table, a table name configuration table, a field configuration table, and a health record event table for health record data, and establish associations among the four tables using the EHR code; the table name configuration table includes query conditions; It should be noted that EHR is the abbreviation of Electronic Health Record, an electronic health record; by pre-configuring the xsl template table, the table name configuration table, the field configuration table, and the health record event table and establishing associations using the EHR code, the cumbersome work of separately developing display pages for each type of health record data is avoided, and the development workload is reduced; S2. Respond to a front-end query request, parse out the request event and request parameters, query the health record event table according to the request event to determine the EHR code, and then query the xsl template table, the table name configuration table, and the field configuration table according to the EHR code to determine the xsl template, the table name, the fields, and the query conditions; It should be noted that it is possible to dynamically generate SQL statements according to different front-end requests and query data, supporting dynamic parameter replacement, so as to quickly adapt to business changes and the needs of different users; S3. Assemble the determined table name, fields, and query conditions into an executable SQL statement, use the request parameters to replace the parameters in the SQL statement, and then execute the SQL query to return the query result; It should be noted that the query results are assembled into an xml file according to the hierarchy and converted into an html page in combination with the xsl template, realizing an intuitive and unified display of health record data, which is convenient for users to view and understand; S4. Parse the query results, assemble them into an xml file according to the hierarchy, and then convert them into an html page in combination with the xsl template and return them to the front-end; It should be noted that by associating the health record data through the configuration table and EHR coding, the data display logic is centralized, enabling unified management and maintenance, and reducing the maintenance cost.

[0026] This embodiment provides an efficient, flexible and secure health record data page display solution through configuration management and dynamic data processing, simplifies the development process, improves the scalability of the health record system, ensures data security, and optimizes the user experience.

[0027] Furthermore, as a refinement and extension of the specific implementation manner of the above embodiment, in order to fully illustrate the specific implementation process in this embodiment, another method for displaying the health record data page is provided, and this method includes the following steps: S1. Pre-configure the xsl template table, table name configuration table, field configuration table and health record event table for the health record data, and establish the association of the four tables using the EHR coding; the table name configuration table includes query conditions; the specific steps of step S1 are as follows: S11. Pre-configure the xsl template table for the health record data, and the xml template table includes xsl template content, EHR coding, and xml sample; It should be noted that among them, the xsl template content is the archive display content in xsl format; the xml template table also includes serial number, EHR name, definition, data status, description, data creator, creation date and time, data updater, and update date and time; S12. Pre-configure the table name configuration table for the health record data, and the table name configuration table also includes EHR coding, data table name, element name, and query conditions; It should be noted that the query condition is a predefined condition with placeholders, supporting dynamic parameter replacement; Among them, the table name configuration table also includes serial number, whether it is the main element, order, data creator, creation date and time, data updater, update date and time, and sorting conditions; S13. Pre-configure the field configuration table for the health record data, and the field configuration table includes EHR coding, database field name, attribute English name, desensitization rule coding, and dictionary coding; It should be noted that the field configuration table also includes serial number, element name, data table name, data creator, creation date and time, data updater, update date and time, database field Chinese name, attribute Chinese name, and dictionary name; S14. Pre-configure the health record event table for the health record data, and the health record event table includes event classification coding, event type, event index, and diagnosis disease name, and establish the association between the health record event table and EHR coding through the event index; It should be noted that the health record event form records the events occurring in the user's health record, and also includes serial number, patient master index ID, patient ID, medical institution code, medical institution name, event number, start date and time, end date and time, total cost, main diagnosis disease code, main diagnosis disease name, whether it is open, reason for not being open, data creator, creation date and time, data updater, and update date and time; The event classification code includes the first-level event classification code and the second-level event classification code; The specific steps for establishing the association between the health record event form and the EHR code through the event index in step S14 are as follows: Construct an event and EHR code association table, and the event and EHR code association table includes serial number, event index, EHR code, and EHR name; Associate the health record event form with the EHR code through the event index; It should be noted that the event and EHR code association table also includes document content, data creator, creation date and time, data updater, and update date and time; S15. Associate the xsl template table, table name configuration table, field configuration table, and health record event form through the EHR code; S2. Respond to the front-end query request, parse out the request event and request parameters, query the health record event form according to the request event to determine the EHR code, and then query the xsl template table, table name configuration table, and field configuration table according to the EHR code to determine the xsl template, table name, fields, and query conditions; The specific steps of step S2 are as follows: S21. Receive the query request sent by the front-end, and parse out the event identifier and request parameters from the query request; The request parameters at least include the medical institution code and the patient ID; S22. Query the health record event form according to the parsed event identifier to determine the corresponding EHR code; S23. Use the determined EHR code to query the xsl template table, table name configuration table, and field configuration table to obtain the corresponding xsl template content, data table name, query conditions, and database field information; S3. Assemble the determined table name, fields, and query conditions into an executable SQL statement, use the request parameters to replace the parameters in the SQL statement, and then execute the SQL query to return the query result; The specific steps of step S3 are as follows: S31. Assemble the determined data table name, database fields, and query conditions into an executable SQL statement: Use SELECT to guide the database fields, use FROM to guide the data table name, and use WHERE to guide the query conditions; S32. Replace the placeholder in the query condition part of the SQL statement with the request parameters to generate the final SQL query statement; S33. Execute the SQL query statement to obtain the query result, process the query result and return it; The processing of the query result in step S33 specifically includes: Determine the corresponding desensitization rule code according to the database field name in the query result; Use the determined desensitization rule code to query the desensitization rule table to determine the desensitization rule, and mask the database field name in the query result according to the desensitization rule; It should be noted that the database fields to be translated and encrypted are processed through the desensitization rule; S4. Parse the query result, assemble it into an xml file according to the hierarchy, and then convert it into an html page in combination with the xsl template and return it to the front end; The specific steps of step S4 are as follows: S41. Extract the database field value from the query result according to the field mapping relationship in the field configuration table, and determine the corresponding dictionary code; S42. Use the determined dictionary code to query the dictionary code table to determine the dictionary, and use the determined dictionary to encode the corresponding database field value in the query result to complete the parsing of the query result; S43. According to the hierarchical attribute of the element name in the table name configuration table, assemble the data of the parsed query result into an xml file, and set the node attribute name of the xml file to be the same as the attribute English name in the field configuration table; S44. Obtain the corresponding xsl template from the xml template table according to the EHR code, and convert the assembled xml file according to the xsl template to generate an html page and return it to the front end.

[0028] To display the health record information of a patient's "inpatient blood transfusion record". Through the configuration and process of this application, the relevant data is extracted from the database and finally displayed to the user in the form of an html page.

[0029] First, configure an xsl template for the "inpatient blood transfusion record" to convert xml data into html format. Then configure the table name configuration table to define the database tables and their field information related to the "inpatient blood transfusion record". As shown in Table 1: Table 1: Table name configuration table for inpatient blood transfusion record

[0030] Then configure the field information related to the "inpatient blood transfusion record", as shown in Table 2: Table 2: Field configuration table for inpatient blood transfusion record

[0031] Reconfigure the health record event table and associate the "Inpatient Blood Transfusion Record" event with the corresponding EHR code, as shown in Table 3: Table 3: Health Record Events of Inpatient Blood Transfusion Record

[0032] When the user queries the "Inpatient Blood Transfusion Record" at the front end, the system will perform the following operations according to the configured EHR code (0106): Query the XSL template and obtain the corresponding XSL template from the database according to the HER code (0106); Query the table information and field information, and obtain the relevant table name and field information from the configuration table according to the HER code (0106); For example: Table name: EHR_BLOOD_TRANSFUSION, Fields: BLOOD_TYPE, TRANSFUSION_DATE, Query condition: org_code=#{org_code} and patient_id= #{patient_id}; Assemble the SQL statement by combining the table name, fields, and query conditions into an SQL statement: SELECT BLOOD_TYPE, TRANSFUSION_DATE FROM EHR_BLOOD_TRANSFUSION WHERE org_code=#{org_code} AND patient_id=#{patient_id}; Replace the parameters provided by the user (such as org_code and patient_id) into the SQL statement, then execute the SQL statement to obtain the data; The returned data is shown in Table 4; Table 4: Query Results of Executing the SQL Statement

[0033] Finally, assemble the queried data into xml format, then use the XSL template to convert the xml data into html format, and return the generated html content to the front end. The user can view the detailed information of the "Inpatient Blood Transfusion Record" in the browser, as shown in Table 5; Table 5: Queried Inpatient Blood Transfusion Records

[0034] Through the execution of the above configurations and steps, the health record data of "Inpatient Blood Transfusion Record" is extracted from the database and converted into an HTML page through XSLT for display to the user; the whole process not only simplifies the development work, but also realizes the function of dynamically configuring new templates, and can flexibly meet the display requirements of different types of health records.

[0035] It should be understood that the sequence numbers of the steps in the above embodiments do not mean the order of execution. The order of execution of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0036] As Figure 2 shown, the following is an embodiment of the page display system for health record data provided by the embodiments of the present disclosure. This system and the page display method for health record data in the above embodiments belong to the same inventive concept. For the details not described in detail in the embodiment of the page display system for health record data, reference can be made to the embodiments of the page display method for health record data.

[0037] The system includes: A configuration management module, which is used to pre-configure an XSL template table, a table name configuration table, a field configuration table, and a health record event table for health record data, and establish the association of the four tables using the EHR code; the table name configuration table includes query conditions; A request parsing module, which is used to respond to a front-end query request, parse out the request event and request parameters, query the health record event table according to the request event to determine the EHR code, and then query the XSL template table, the table name configuration table, and the field configuration table according to the EHR code to determine the XSL template, table name, fields, and query conditions; An SQL generation and execution module, which is used to assemble the determined table name, fields, and query conditions into an executable SQL statement, perform parameter substitution in the SQL statement using the request parameters, and then execute the SQL query to return the query result; A data conversion module, which is used to parse the query result, assemble it into an XML file according to the hierarchy, and then convert it into an HTML page in combination with the XSL template and return it to the front-end.

[0038] Through the interaction and cooperation of the configuration management module, the request parsing module, the SQL generation and execution module, and the data conversion module in this embodiment, the development process is simplified, the flexibility and scalability of the health record system are improved, the data security and privacy are guaranteed, and the user experience and system performance are enhanced.

[0039] The page display method for health record data provided by the embodiments of this application can be applied to an electronic device. Those skilled in the art can understand that the structure of the electronic device involved in the embodiments of the present invention does not constitute a limitation on the electronic device. The electronic device may include more or fewer components than shown in the figure, or combine certain components, or have different component arrangements. In the embodiments of the present invention, the electronic device includes, but is not limited to, a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as, a personal digital processor, a cellular phone, a smart phone, a wearable device, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the embodiments of this application described herein and / or claimed.

[0040] The electronic device may include a processor, an external memory interface, an internal memory, a universal serial bus (USB) interface, a charging management module, a power management module, a battery, a wireless communication module, an audio module, a speaker, a microphone, a sensor module, a key, a camera, a display screen, and a SIM card interface, etc.

[0041] It can be understood that the structure schematically shown in the embodiments of this application does not constitute a specific limitation on the electronic device. In other embodiments of this application, the electronic device may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or have different component arrangements. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0042] The processor may include one or more processing units. For example, the processor may include a central processing unit (CPU), etc., an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0043] Among them, the processor can be the nerve center and command center of the electronic device. The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of fetching and executing instructions.

[0044] A memory can also be set in the processor for storing instructions and data. In some embodiments, the memory in the processor is a cache memory. This memory can save the instructions or data that the processor has just used or recycled. If the processor needs to use the instruction or data again, it can directly call it from this memory. This avoids repeated accesses, reduces the waiting time of the processor, and thus improves the system efficiency.

[0045] The above-mentioned electronic device implements the technical solution of the method for displaying the page of the health record data in the present application, which pre-configures the xsl template table, table name configuration table, field configuration table and health record event table for the health record data, and uses the EHR code to establish the association of the four tables; the table name configuration table includes query conditions; in response to the front-end query request, the request event and request parameters are parsed, and the health record event table is queried according to the request event to determine the EHR code, and then the xsl template table, table name configuration table and field configuration table are queried according to the EHR code to determine the xsl template, table name, field and query conditions; the determined table name, field and query conditions are assembled into an executable SQL statement, and the request parameters are used for parameter substitution in the SQL statement, and then the SQL query is executed to return the query result; the query result is parsed and assembled into an xml file according to the hierarchy, and then combined with the xsl template to be converted into an html page and returned to the front-end, achieving the beneficial effects of simplifying the development process, improving the flexibility and scalability of the health record system, while ensuring data security and privacy, and enhancing the user experience and system performance through configuration management and dynamic data processing.

[0046] In the storage medium provided by the present application, there is a program product capable of implementing the method for displaying the page of the health record data.

[0047] The page display method for health record data includes: pre-configuring an XSL template table, a table name configuration table, a field configuration table, and a health record event table for health record data, and establishing associations among the four tables using EHR codes; the table name configuration table includes query conditions; in response to a front-end query request, parsing out the request event and request parameters, querying the health record event table according to the request event to determine the EHR code, and then querying the XSL template table, the table name configuration table, and the field configuration table according to the EHR code to determine the XSL template, table name, fields, and query conditions; assembling the determined table name, fields, and query conditions into an executable SQL statement, performing parameter substitution in the SQL statement using the request parameters, and then executing the SQL query to return the query result; parsing the query result, assembling it into an xml file hierarchically, and then converting it into an html page in combination with the XSL template and returning it to the front end.

[0048] In some possible implementation manners, the page display method for health record data of the present disclosure may be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to cause the terminal device to execute the steps according to various exemplary embodiments of the present disclosure described in the "Exemplary Method" section of this specification.

[0049] The storage medium of the present disclosure may adopt any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0050] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for page display of health record data, characterized in that, It includes the following steps: S1. Pre-configure an xsl template table, a table name configuration table, a field configuration table, and a health record event table for health record data, and establish associations among the four tables using EHR codes; the table name configuration table includes query conditions; S2. In response to a front-end query request, parse out the request event and request parameters, query the health record event table based on the request event to determine the EHR code, and then query the xsl template table, the table name configuration table, and the field configuration table based on the EHR code to determine the xsl template, table name, fields, and query conditions; S3. Assemble the determined table name, fields, and query conditions into an executable SQL statement, perform parameter substitution in the SQL statement using the request parameters, and then execute the SQL query to return the query result; S4. Parse the query result, assemble it into an xml file in a hierarchical manner, and then convert it into an html page in combination with the xsl template and return it to the front end.

2. The page display method for health record data according to claim 1, wherein The specific steps of step S1 are as follows: S11. Pre-configure an xsl template table for health record data, and the xml template table includes xsl template content, EHR code, and xml sample; S12. Pre-configure a table name configuration table for health record data, and the table name configuration table includes EHR code, data table name, element name, and query conditions; S13. Pre-configure a field configuration table for health record data, and the field configuration table includes EHR code, database field name, attribute English name, desensitization rule code, and dictionary code; S14. Pre-configure a health record event table for health record data, and the health record event table includes event classification code, event type, event index, and diagnosed disease name, and establish an association between the health record event table and the EHR code through the event index; S15. Associate the xsl template table, the table name configuration table, the field configuration table, and the health record event table through the EHR code.

3. The method for page display of health record data according to claim 2, wherein The specific steps of establishing the association between the health record event table and the EHR code through the event index in step S14 are as follows: Construct an event-EHR code association table, and the event-EHR code association table includes serial number, event index, EHR code, and EHR name; Associate the health record event table with the EHR code through the event index.

4. The page display method for health record data according to claim 2, wherein The specific steps of step S2 are as follows: S21. Receive the query request sent by the front end, and parse out the event identifier and request parameters from the query request; the request parameters include at least the medical institution code and the patient ID; S22. Query the health record event table based on the parsed event identifier to determine the corresponding EHR code; S23. Use the determined EHR code to query the xsl template table, the table name configuration table, and the field configuration table to obtain the corresponding xsl template content, data table name, query conditions, and database field information.

5. The page display method of the health record data according to claim 4, wherein The specific steps of step S3 are as follows: S31. Assemble the determined data table name, database fields, and query conditions into an executable SQL statement: Use SELECT to lead the database fields, use FROM to lead the data table name, and use WHERE to lead the query conditions; S32. Replace the placeholder in the query condition part of the SQL statement with the request parameter to generate the final SQL query statement; S33. Execute the SQL query statement to obtain the query result, and return the query result after processing.

6. The method for page display of health record data according to claim 5, characterized in that, The processing of the query result in step S33 specifically includes: Determine the corresponding desensitization rule code according to the database field name in the query result; Use the determined desensitization rule code to query the desensitization rule table to determine the desensitization rule, and mask the database field name in the query result according to the desensitization rule.

7. The method for page display of health record data according to claim 5, wherein The specific steps of step S4 are as follows: S41. Extract the database field value from the query result according to the field mapping relationship in the field configuration table, and determine the corresponding dictionary code; S42. Use the determined dictionary code to query the dictionary code table to determine the dictionary, and use the determined dictionary to encode the corresponding database field value in the query result to complete the parsing of the query result; S43. According to the hierarchical attribute of the element name in the table name configuration table, assemble the data of the parsed query result into an xml file, and set the node attribute name of the xml file to be the same as the attribute English name in the field configuration table; S44. Obtain the corresponding xsl template from the xml template table according to the EHR code, and convert the assembled xml file according to the xsl template to generate an html page and return it to the front end.

8. A page display system for health record data, characterized in that, Including: A configuration management module for pre-configuring an xsl template table, a table name configuration table, a field configuration table, and a health record event table for health record data, and establishing associations among the four tables using the EHR code; the table name configuration table includes query conditions; A request parsing module for responding to a front-end query request, parsing out the request event and request parameters, querying the health record event table according to the request event to determine the EHR code, and then querying the xsl template table, the table name configuration table, and the field configuration table according to the EHR code to determine the xsl template, the table name, the field, and the query condition; An SQL generation and execution module for assembling the determined table name, field, and query condition into an executable SQL statement, performing parameter substitution in the SQL statement using the request parameter, and then executing the SQL query to return the query result; A data conversion module for parsing the query result, assembling it into an xml file according to the hierarchy, and then converting it into an html page in combination with the xsl template and returning it to the front end.

9. An electronic device, characterized in that, Including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein the processor implements the steps of the method for displaying a page of health record data according to any one of claims 1 to 7 when executing the program.

10. A storage medium having a computer program stored thereon, characterized in that, The computer program, when executed by the processor, implements the steps of the method for displaying a page of health record data according to any one of claims 1 to 7.

Images