Method, system, device and medium for displaying health record data on a page

Abstract

The present application provides a method, system, device and medium for displaying health record data on a page, belonging to the field of data display technology. The method comprises the following steps: pre-configuring an xsl template table, a table name configuration table, a field configuration table and a health record event table, and associating the four tables using EHR codes; responding to a front-end query request, parsing the request event and request parameters, and querying the health record event table to determine the EHR code based on the request event, querying the xsl template table, the table name configuration table and the field configuration table, and determining the xsl template, table name, field and query conditions; assembling the determined table name, field and query conditions into an executable SQL statement, replacing the parameters in the SQL statement with request parameters and executing the statement; parsing the query results, assembling them into an xml file according to the hierarchy, and then converting them into an html page in combination with the xsl template and returning them to the front-end. The present invention simplifies the development process, improves flexibility and data security, and optimizes user experience.

Description

Technical Field

[0001] The present application belongs to the field of data display technology, and specifically relates to a method, system, device and medium for displaying health record data on a page. Background Art

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

[0003] First, health record data is diverse, covering multiple areas such as medical records, examinations and tests, and physical examinations, involving hundreds of business data tables. Developing separate display pages for each type of record would not only be a huge workload, but also difficult to achieve unified management and maintenance. Second, traditional methods lack flexibility and cannot dynamically configure new display templates, resulting in poor scalability of health record systems, difficulty in adapting to rapidly changing business needs, and high maintenance costs. Third, although relevant standards provide unified specifications for data formats, in actual applications, how to efficiently integrate diverse data and dynamically generate display pages remains a difficult problem that needs to be solved.

[0004] Current next-generation technologies typically use fixed templates or hard-coded methods to display data. While this approach can meet basic needs to a certain extent, it cannot adapt to rapidly changing business needs, especially when dealing with diverse user groups, different application scenarios, and constantly changing health data types. Therefore, a display page method is urgently needed that can simplify the development process, improve the flexibility of health record systems, and meet users' needs for intuitive and unified display of health record data. Summary of the Invention

[0005] In a first aspect, an embodiment of the present application provides a method for displaying health record data on a page, comprising the following steps:

[0006] S1 pre-configure the health file data xsl template table, table name configuration table, field configuration table and health file event table, and use EHR coding to establish an association between the four tables; the table name configuration table includes query conditions;

[0007] S2. Respond to the front-end query request, parse the request event and request parameters, and query the health record event table to determine the EHR code based on the request event. Then, query the xsl template table, table name configuration table, and field configuration table based on the EHR code to determine the xsl template, table name, field, and query conditions.

[0008] S3. Assemble the determined table name, fields, and query conditions into an executable SQL statement, replace the parameters in the SQL statement with the request parameters, execute the SQL query, and return the query results.

[0009] S4. Parse the query results and assemble them into XML files according to the hierarchy. Then, combine them with XSL templates to convert them into HTML pages and return them to the front end.

[0010] Furthermore, the specific steps of step S1 are as follows:

[0011] S11. Pre-configure xsl template table for health record data, the xml template table includes xsl template content, EHR code, xml sample;

[0012] S12. Pre-configure the table name configuration table for health record data, the table name configuration table includes EHR code, data table name, element name and query conditions;

[0013] S13. Pre-configure the field configuration table for health record data, which includes the EHR code, database field name, attribute English name, desensitization rule code and dictionary code;

[0014] S14. Pre-configure the health file event table for health file data. The health file event table includes event classification code, event type, event index and diagnosis disease name, and establishes an association between the health file event table and the EHR code through the event index;

[0015] S15. Configure the xsl template table, table name configuration table, field configuration table and health record event table through EHR coding association.

[0016] Furthermore, 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:

[0017] Constructing an event and EHR code association table, wherein the event and EHR code association table includes a serial number, an event index, an EHR code, and an EHR name;

[0018] The health record event table is linked to the EHR code through the event index.

[0019] Furthermore, the specific steps of step S2 are as follows:

[0020] S21 receives a query request sent by the front end, and parses the event identifier and request parameters from the query request; the request parameters include at least the medical institution code and the patient ID;

[0021] S22. Query the health record event table based on the parsed event identifier to determine the corresponding EHR code;

[0022] 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.

[0023] Furthermore, the specific steps of step S3 are as follows:

[0024] S31. Assemble the determined data table name, database field, and query conditions into an executable SQL statement:

[0025] Use SELECT to guide the database field, FROM to guide the data table name, and WHERE to guide the query condition;

[0026] S32. Use the request parameters to replace the placeholders in the query condition part of the SQL statement to generate the final SQL query statement;

[0027] S33. Execute the SQL query statement to obtain the query results, process the query results and return them.

[0028] Furthermore, the processing of the query result in step S33 specifically includes:

[0029] Determine the corresponding desensitization rule code based on the database field name in the query result;

[0030] Use the determined desensitizing rule code to query the desensitizing rule table to determine the desensitizing rule, and mask the database field names in the query results according to the desensitizing rule.

[0031] Furthermore, the specific steps of step S4 are as follows:

[0032] S41 extracts the database field value from the query result according to the field mapping relationship in the field configuration table and determines the corresponding dictionary code;

[0033] S42 uses the determined dictionary encoding query dictionary encoding table to determine the dictionary, and uses the determined dictionary to encode the corresponding database field value in the query result to complete the query result parsing;

[0034] S43. According to the hierarchical attributes of the element name in the table name configuration table, the parsed query result data is assembled into an XML file, and the node attribute name of the XML file is set to be consistent with the English name of the attribute in the field configuration table;

[0035] S44. Obtain the corresponding xsl template from the xml template table according to the EHR code, convert the assembled xml file according to the xsl template, generate an html page, and return it to the front end.

[0036] In a second aspect, the present application also provides a page display system for health record data, including:

[0037] 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 use EHR coding to establish the association between the four tables; the table name configuration table includes query conditions;

[0038] The request parsing module is used to respond to the front-end query request, parse the request event and request parameters, and query the health record event table to determine the EHR code based on the request event. Then, based on the EHR code, it queries the xsl template table, table name configuration table, and field configuration table to determine the xsl template, table name, field, and query conditions.

[0039] The SQL generation and execution module is used to assemble the determined table name, fields and query conditions into an executable SQL statement, and use the request parameters to replace the parameters in the SQL statement, and then execute the SQL query and return the query results;

[0040] The data conversion module is used to parse the query results, assemble them into XML files according to the hierarchy, and then convert them into HTML pages based on the XSL template and return them to the front end.

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

[0042] 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 page display method of health record data as described in the first aspect are implemented.

[0043] It can be seen from the above technical solutions that this application has the following advantages:

[0044] The page display method, system, device and medium of health record data provided by this application pre-configures the xsl template table, table name configuration table, field configuration table and health record event table, and uses EHR coding to establish associations, thereby avoiding the need to develop a separate display page for each type of health record data, reducing development workload, shortening development cycle, and improving 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 maintenance costs, but also being able to cope with business expansion and changes; assembling the query results into xml files according to the hierarchy, and converting them into html pages in combination with xsl templates, realizing health The intuitive and unified display of health record data makes it easier for users to view and understand, improves the user experience, and enables users to obtain the required information more quickly and conveniently; the health record data is managed through configuration tables and EHR codes, so that the data display logic is centralized and easy to manage and maintain in a unified manner; by desensitizing sensitive data in query results, the patient's privacy and data security are protected; and the relevant configuration tables can be dynamically updated to support the display of new health record data types; through reasonable SQL statement construction and parameter replacement, the database query process is optimized, the response speed and performance are improved, which not only improves the user experience, but also improves the overall efficiency of the health record system, ensuring the stable operation of the health record system under high load conditions. BRIEF DESCRIPTION OF THE DRAWINGS

[0045] In order to more clearly illustrate the technical solution of the present application, the following is a brief introduction to the drawings required for the description. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0046] Figure 1 This is a flow chart of the method for displaying health record data on a page according to the present invention.

[0047] Figure 2 Schematic diagram of the page display system of the health record data of the present invention. DETAILED DESCRIPTION

[0048] In the specific steps of the page display method for health record data, which will be described in detail below, various embodiments of the present disclosure will be described more comprehensively. The present disclosure may have various embodiments, and adjustments and changes may 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 rather that the present disclosure should be understood to cover all adjustments, equivalents and / or alternatives that fall within the spirit and scope of the various embodiments of the present disclosure.

[0049] For example, with the development of medical informatization, electronic health records, as a core component of health big data, are becoming increasingly important. However, existing health record systems have many problems in data display methods.

[0050] First, health record data is diverse, covering multiple areas such as medical records, examinations and tests, and physical examinations, involving hundreds of business data tables. Developing separate display pages for each type of record would not only be a huge workload, but also difficult to achieve unified management and maintenance. Second, traditional methods lack flexibility and cannot dynamically configure new display templates, resulting in poor scalability of health record systems, difficulty in adapting to rapidly changing business needs, and high maintenance costs. Third, although relevant standards provide unified specifications for data formats, in actual applications, how to efficiently integrate diverse data and dynamically generate display pages remains a difficult problem that needs to be solved.

[0051] Current next-generation technologies typically use fixed templates or hard-coded methods to display data. While this approach can meet basic needs to a certain extent, it cannot adapt to rapidly changing business needs, especially when dealing with diverse user groups, different application scenarios, and constantly changing health data types. Therefore, a display page method is urgently needed that can simplify the development process, improve the flexibility of health record systems, and meet users' needs for intuitive and unified display of health record data.

[0052] To address the above issues, this embodiment provides a page display method for health record data. Through configurable management and dynamic data processing, it simplifies the development process, improves the flexibility and scalability of the health record system, while ensuring data security and privacy, and improving user experience and system performance.

[0053] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0054] See also Figure 1 FIG. 1 is a flow chart of a method for displaying health record data on a page in a specific embodiment, the method comprising the following steps:

[0055] S1 pre-configure the health file data xsl template table, table name configuration table, field configuration table and health file event table, and use EHR coding to establish an association between the four tables; the table name configuration table includes query conditions;

[0056] It should be noted that EHR is the abbreviation of Electronic Health Record. By pre-configuring the XSL template table, table name configuration table, field configuration table and health record event table, and using EHR codes to establish associations, the tedious work of developing display pages for each type of health record data is avoided, thus reducing the development workload.

[0057] S2. Respond to the front-end query request, parse the request event and request parameters, and query the health record event table to determine the EHR code based on the request event. Then, query the xsl template table, table name configuration table, and field configuration table based on the EHR code to determine the xsl template, table name, field, and query conditions.

[0058] It should be noted that it can dynamically generate SQL statements and query data based on different front-end requests, and support dynamic parameter replacement, so as to quickly adapt to business changes and different user needs;

[0059] S3. Assemble the determined table name, fields, and query conditions into an executable SQL statement, replace the parameters in the SQL statement with the request parameters, execute the SQL query, and return the query results.

[0060] It should be noted that the query results are assembled into XML files according to the hierarchy and converted into HTML pages in combination with XSL templates, which enables an intuitive and unified display of health record data, making it easier for users to view and understand;

[0061] S4. Parse the query results, assemble them into an XML file according to the hierarchy, and then convert them into an HTML page using an XSL template and return it to the front end;

[0062] It should be noted that by associating health record data through configuration tables and EHR codes, the data display logic is centralized, allowing for unified management and maintenance, reducing maintenance costs.

[0063] This embodiment provides an efficient, flexible and secure health record data page display solution through configurable 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.

[0064] Furthermore, as a refinement and extension of the specific implementation of the above embodiment, in order to fully illustrate the specific implementation process in this embodiment, another page display method for health record data is provided, which includes the following steps:

[0065] S1 pre-configure the health file data xsl template table, table name configuration table, field configuration table and health file event table, and use EHR coding to establish an association between the four tables; the table name configuration table includes query conditions; Step S1 specific steps are as follows:

[0066] S11. Pre-configure xsl template table for health record data, the xml template table includes xsl template content, EHR code, xml sample;

[0067] It should be noted that the xsl template content is the file display content in xsl format; the xml template table also includes the serial number, EHR name, definition, data status, description, data creator, creation date and time, data updater and update date and time;

[0068] S12. Pre-configure the table name configuration table for health record data, the table name configuration table also includes EHR code, data table name, element name and query conditions;

[0069] It should be noted that the query conditions are predefined conditions with placeholders and support dynamic parameter replacement;

[0070] The table name configuration table also includes the serial number, whether it is a primary element, the order, the data creator, the creation date and time, the data updater, the update date and time, and the sorting conditions;

[0071] S13. Pre-configure the field configuration table for health record data, which includes the EHR code, database field name, attribute English name, desensitization rule code and dictionary code;

[0072] It should be noted that the field configuration table also includes the 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;

[0073] S14. Pre-configure the health file event table for health file data. The health file event table includes event classification code, event type, event index and diagnosis disease name, and establishes an association between the health file event table and the EHR code through the event index;

[0074] It should be noted that the health record event table records events that occur in the user's health record, and also includes the serial number, patient primary 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 opening, data creator, creation date and time, data updater and update date and time;

[0075] Event classification codes include event classification primary codes and event classification secondary codes;

[0076] The specific steps for establishing the association between the health record event table and the EHR code through the event index in step S14 are as follows:

[0077] Constructing an event and EHR code association table, wherein the event and EHR code association table includes a serial number, an event index, an EHR code, and an EHR name;

[0078] Linking the health record event table with EHR codes through event indexing;

[0079] 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;

[0080] S15. Configure the xsl template table, table name configuration table, field configuration table, and health record event table through EHR coding association;

[0081] S2. Respond to the front-end query request, parse the request event and request parameters, and 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; the specific steps of step S2 are as follows:

[0082] S21 receives a query request sent by the front end, and parses the event identifier and request parameters from the query request; the request parameters include at least the medical institution code and the patient ID;

[0083] S22. Query the health record event table based on the parsed event identifier to determine the corresponding EHR code;

[0084] 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;

[0085] S3. Assemble the determined table name, field, and query conditions into an executable SQL statement, replace the parameters in the SQL statement with the request parameters, execute the SQL query, and return the query results. The specific steps of step S3 are as follows:

[0086] S31. Assemble the determined data table name, database field, and query conditions into an executable SQL statement:

[0087] Use SELECT to guide the database field, FROM to guide the data table name, and WHERE to guide the query condition;

[0088] S32. Use the request parameters to replace the placeholders in the query condition part of the SQL statement to generate the final SQL query statement;

[0089] S33 executes the SQL query statement to obtain the query results, processes the query results and returns;

[0090] The processing of the query results in step S33 specifically includes:

[0091] Determine the corresponding desensitization rule code based on the database field name in the query result;

[0092] Use the determined desensitization rule code to query the desensitization rule table to determine the desensitization rule, and mask the database field names in the query results according to the desensitization rule;

[0093] It should be noted that the database fields that need to be translated and encrypted are processed through desensitization rules;

[0094] S4. Parse the query results and assemble them into an XML file according to the hierarchy. Then, combine the XSL template to convert it into an HTML page and return it to the front end. The specific steps of step S4 are as follows:

[0095] S41 extracts the database field value from the query result according to the field mapping relationship in the field configuration table and determines the corresponding dictionary code;

[0096] S42 uses the determined dictionary encoding query dictionary encoding table to determine the dictionary, and uses the determined dictionary to encode the corresponding database field value in the query result to complete the query result parsing;

[0097] S43. According to the hierarchical attributes of the element name in the table name configuration table, the parsed query result data is assembled into an XML file, and the node attribute name of the XML file is set to be consistent with the English name of the attribute in the field configuration table;

[0098] S44. Obtain the corresponding xsl template from the xml template table according to the EHR code, convert the assembled xml file according to the xsl template, generate an html page, and return it to the front end.

[0099] For example, a patient's "hospitalization blood transfusion record" health record information needs to be displayed. 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.

[0100] First, configure an XSL template for "Inpatient Blood Transfusion Records" to convert XML data into HTML format. Then configure the table name configuration table to define the database table and field information related to "Inpatient Blood Transfusion Records." For example, as shown in Table 1:

[0101] Table 1: Table name configuration table for hospitalization blood transfusion records

[0102]

[0103] Next, configure the field information related to "Inpatient Blood Transfusion Record", as shown in Table 2:

[0104] Table 2: Field configuration table for hospitalization blood transfusion records

[0105]

[0106] Then configure the health record event table and associate the "hospitalization blood transfusion record" event with the corresponding EHR code, as shown in Table 3:

[0107] Table 3: Health record events for hospitalization blood transfusion records

[0108]

[0109] When the user queries "Inpatient Blood Transfusion Record" on the front end, the system will perform the following operations based on the configured EHR code (0106):

[0110] Query the XSL template and obtain the corresponding XSL template from the database according to the HER code (0106);

[0111] Query table information and field information. According to the HER code (0106), obtain the relevant table name and field information from the configuration table; for example: table name: EHR_BLOOD_TRANSFUSION, fields: BLOOD_TYPE, TRANSFUSION_DATE, query conditions: org_code=#{org_code}and patient_id=#{patient_id};

[0112] Assemble SQL statements, assemble table names, fields, and query conditions into SQL statements:

[0113] SELECT BLOOD_TYPE, TRANSFUSION_DATE

[0114] FROM EHR_BLOOD_TRANSFUSION

[0115] WHERE org_code=#{org_code}AND patient_id=#{patient_id};

[0116] Replace the user-provided parameters (such as org_code and patient_id) into the SQL statement, and then execute the SQL statement to obtain the data; the returned data is shown in Table 4;

[0117] Table 4: Query results of executing SQL statements

[0118]

[0119] Finally, the queried data is assembled into XML format, and then the XSL template is used to convert the XML data into HTML format. The generated HTML content is returned to the front end, and the user can view the detailed information of "Inpatient Blood Transfusion Record" in the browser, as shown in Table 5;

[0120] Table 5: In-hospital blood transfusion records

[0121]

[0122] Through the execution of the above configuration and steps, the health record data of "hospitalization blood transfusion record" is extracted from the database and converted into HTML page through XSLT and displayed to the user; the whole process not only simplifies the development work, but also realizes the function of dynamically configuring new templates, which can flexibly respond to different types of health record display needs.

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

[0124] like Figure 2 As shown, the following is an embodiment of the page display system for health record data provided by the embodiment of the present disclosure. This system and the page display method for health record data of the above-mentioned embodiments belong to the same inventive concept. For details not fully described in the embodiment of the page display system for health record data, please refer to the embodiment of the page display method for health record data mentioned above.

[0125] The system includes:

[0126] 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 use EHR coding to establish the association between the four tables; the table name configuration table includes query conditions;

[0127] The request parsing module is used to respond to the front-end query request, parse the request event and request parameters, and query the health record event table to determine the EHR code based on the request event. Then, based on the EHR code, it queries the xsl template table, table name configuration table, and field configuration table to determine the xsl template, table name, field, and query conditions.

[0128] The SQL generation and execution module is used to assemble the determined table name, fields and query conditions into an executable SQL statement, and use the request parameters to replace the parameters in the SQL statement, and then execute the SQL query and return the query results;

[0129] The data conversion module is used to parse the query results, assemble them into XML files according to the hierarchy, and then convert them into HTML pages based on the XSL template and return them to the front end.

[0130] This embodiment simplifies the development process and improves the flexibility and scalability of the health record system through the interactive collaboration of the configuration management module, request parsing module, SQL generation and execution module, and data conversion module, while ensuring data security and privacy, and improving user experience and system performance.

[0131] The page display method of health record data provided in the embodiment of the present application can be applied to electronic devices. Those skilled in the art will understand that the electronic device structure involved in the embodiment of the present invention does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently. In the embodiment 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 can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices 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 the present application described and / or required herein.

[0132] 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 button, a camera, a display, and a SIM card interface, etc.

[0133] It is understood that the structures illustrated in the embodiments of the present application do not constitute specific limitations on the electronic device. In other embodiments of the present application, the electronic device may include more or fewer components than shown, or combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0134] A processor may include one or more processing units, such as a central processing unit (CPU), 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). Different processing units may be independent devices or integrated into one or more processors.

[0135] The processor can be the nerve center and command center of the electronic device. The controller can generate operation control signals based on the instruction opcode and timing signal to complete the control of instruction fetching and execution.

[0136] The processor may also include a memory for storing instructions and data. In some embodiments, the memory in the processor is a cache memory. This memory can store instructions or data that the processor has just used or is reusing. If the processor needs to use the instruction or data again, it can directly call it from the memory. This avoids repeated accesses, reduces processor latency, and thus improves system efficiency.

[0137] The above-mentioned electronic device implements the page display method of the health record data of 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 EHR code to establish an association between the four tables; the table name configuration table includes query conditions; responds to the front-end query request, parses the request event and request parameters, and queries the health record event table according to the request event to determine the EHR code, and then queries 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; assembles the determined table name, field and query conditions into an executable SQL statement, and uses the request parameters to replace the parameters in the SQL statement, and then executes the SQL query and returns the query result; parses the query result, and assembles it into an xml file according to the hierarchy, and then combines the xsl template to convert it into an html page and return it to the front end. The technical solution achieves the benefits of simplifying the development process through configuration management and dynamic data processing, improving the flexibility and scalability of the health record system, while ensuring data security and privacy, and improving user experience and system performance.

[0138] The storage medium provided in this application stores a program product that can implement a page display method for health record data.

[0139] The page display method of 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 using EHR coding to establish an association between the four tables; the table name configuration table includes query conditions; responding to a front-end query request, parsing the request event and request parameters, and 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, field and query conditions; assembling the determined table name, field and query conditions into an executable SQL statement, and using request parameters to replace parameters in the SQL statement, and then executing the SQL query and returning the query result; parsing the query result, and 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.

[0140] In some possible implementations, the page display method of health record data disclosed herein can be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps described in the above "Exemplary Method" section of this specification according to various exemplary implementations of the present disclosure.

[0141] The storage medium of the present disclosure can adopt any combination of one or more readable media. The readable medium can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, a system, device or component of electricity, magnetism, light, electromagnetic, infrared, or semiconductor, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with 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 thereof.

[0142] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be readily apparent to one 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 is not limited to the embodiments shown herein but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for displaying health record data on a page, characterized in that: The steps include: S1 pre-configure the health file data xsl template table, table name configuration table, field configuration table and health file event table, and use EHR coding to establish an association between the four tables; the table name configuration table includes query conditions; Step S1 specific steps are as follows: S11. Pre-configure an xsl template table for health record data, the xsl template table includes xsl template content, EHR code, xml sample; S12. Pre-configure the table name configuration table for health record data, the table name configuration table includes EHR code, data table name, element name and query conditions; S13. Pre-configure the field configuration table for health record data, which includes the EHR code, database field name, attribute English name, desensitization rule code and dictionary code; S14. Pre-configure the health file event table for health file data. The health file event table includes event classification code, event type, event index and diagnosis disease name, and establishes an association between the health file event table and the EHR code through the event index; The specific steps for establishing the association between the health record event table and the EHR code through the event index in step S14 are as follows: Constructing an event and EHR code association table, wherein the event and EHR code association table includes a serial number, an event index, an EHR code, and an EHR name; Linking the health record event table with EHR codes through event indexing; S15. Configure the xsl template table, table name configuration table, field configuration table, and health record event table through EHR coding association; S2. Respond to the front-end query request, parse the request event and request parameters, and query the health record event table to determine the EHR code based on the request event. Then, query the xsl template table, table name configuration table, and field configuration table based on the EHR code to determine the xsl template, table name, field, and query conditions. S3. Assemble the determined table name, fields, and query conditions into an executable SQL statement, replace the parameters in the SQL statement with the request parameters, execute the SQL query, and return the query results. S4. Parse the query results and assemble them into an XML file according to the hierarchy. Then, combine the XSL template to convert it into an HTML page and return it to the front end. The specific steps of step S4 are as follows: S41 extracts the database field value from the query result according to the field mapping relationship in the field configuration table and determines the corresponding dictionary code; S42 uses the determined dictionary encoding query dictionary encoding table to determine the dictionary, and uses 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 attributes of the element name in the table name configuration table, the parsed query result data is assembled into an XML file, and the node attribute name of the XML file is set to be consistent with the English name of the attribute in the field configuration table; S44. Obtain the corresponding xsl template from the xsl template table according to the EHR code, convert the assembled xml file according to the xsl template, generate an html page, and return it to the front end.

2. The method for displaying health record data on a page according to claim 1, characterized in that: The specific steps of step S2 are as follows: S21 receives a query request sent by the front end, and parses 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, table name configuration table and field configuration table to obtain the corresponding xsl template content, data table name, query conditions and database field information.

3. The method for displaying health record data on a page according to claim 2, characterized in that: 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 field, FROM to guide the data table name, and WHERE to guide the query condition; S32. Use the request parameters to replace the placeholders in the query condition part of the SQL statement to generate the final SQL query statement; S33. Execute the SQL query statement to obtain the query results, process the query results and return them.

4. The method for displaying health record data on a page according to claim 3, characterized in that: The processing of the query results in step S33 specifically includes: Determine the corresponding desensitization rule code based on the database field name in the query result; Use the determined desensitizing rule code to query the desensitizing rule table to determine the desensitizing rule, and mask the database field names in the query results according to the desensitizing rule.

5. A page display system for health record data, based on the page display method for health record data according to any one of claims 1 to 4, characterized in that: include: 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 use EHR coding to establish the association between the four tables; the table name configuration table includes query conditions; The request parsing module is used to respond to the front-end query request, parse the request event and request parameters, and query the health record event table to determine the EHR code based on the request event. Then, based on the EHR code, it queries the xsl template table, table name configuration table, and field configuration table to determine the xsl template, table name, field, and query conditions. The SQL generation and execution module is used to assemble the determined table name, fields and query conditions into an executable SQL statement, and use the request parameters to replace the parameters in the SQL statement, and then execute the SQL query and return the query results; The data conversion module is used to parse the query results, assemble them into XML files according to the hierarchy, and then convert them into HTML pages based on the XSL template and return them to the front end.

6. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the program, the steps of the page display method for health record data as described in any one of claims 1 to 4 are implemented.

7. A storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method for displaying health record data on a page as claimed in any one of claims 1 to 4 are implemented.

Images