A method and system for generating personalized medical device operational reports

Abstract

The application discloses a kind of personalized medical instrument operation report generation method and system, it is related to operation report generation technical field.The method comprises the following steps: receiving operation report generation request, extracting role permission level, marking access range parameter and visible permission boundary;For each generation request, calculate priority score, periodically update priority score to carry out dynamic sorting scheduling;Extract request task type, filter associated operation index set, judge the life cycle stage where operation index is located, set the display strategy of operation index in generation report;For different user roles, generate multiple versions of operation report, extract common content module and role individual content module and output;For content module, set desensitization level identification, carry out matching display control to each content module.The application realizes the efficient generation, accurate customization and differentiated display of medical instrument operation report under the premise of guaranteeing data security and compliance.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of operation report generation, in particular to a personalized medical instrument operation report generation method and system. BACKGROUND

[0002] With the advancement of smart hospital construction, more and more medical institutions manage medical instruments through information means. As an important basis for supporting medical instrument asset management, use efficiency optimization and maintenance decision, the generation method of operation report directly affects the management quality.

[0003] In related technologies, existing medical instrument operation management mostly generates operation reports by using unified templates, lacks precise visibility control based on user roles and permissions, and is difficult to meet the personalized needs of different medical institutions and different user roles for report content and form. In addition, the priority scheduling mechanism is insufficient, and the report generation order cannot be dynamically optimized according to the request urgency, device risk level and other factors, affecting the timely response of high-priority tasks. In addition, the traditional report generation process lacks intelligent dynamic adjustment mechanism, resulting in redundant or missing report information, affecting management efficiency and decision-making effect, and there is room for improvement. SUMMARY

[0004] The purpose of the present application is to provide a personalized medical instrument operation report generation method and system to solve the problems raised in the background.

[0005] In a first aspect, the present application provides a personalized medical instrument operation report generation method, which adopts the following technical solution:

[0006] Receive operation report generation requests from multiple user terminals, extract role permission levels, and mark access range parameters and visible permission boundaries of the current operation report generation request;

[0007] Calculate the initial priority score for each operation report generation request, periodically update the priority score of each operation report generation request, and perform dynamic sorting and scheduling;

[0008] Extract the request task type contained in the operation report generation request, filter the operation indicator set associated with the task type, and calculate the current weight decay value of each operation indicator;

[0009] Determine the life cycle stage of each operation indicator, combine the weight decay value, and set the display strategy of each operation indicator in the generated report;

[0010] Based on the display strategy, generate multiple versions of operation reports for different user roles, extract common content modules and role individual content modules, and output;

[0011] Setting a desensitization level identifier for each content module in the operation report, and matching and displaying control of each content module according to the user role permission level.

[0012] Preferably, the step of receiving operation report generation requests from multiple user terminals, extracting role permission levels, and marking access range parameters and visible permission boundaries of the current operation report generation request is specifically:

[0013] Receiving operation report generation requests from multiple user terminals about medical machinery, wherein the operation report generation request includes a user role identifier and a request task type;

[0014] Extracting the user role identifier, determining the user's role permission level, and matching the corresponding access range parameter based on the role permission level;

[0015] Based on the access range parameter, a visible permission boundary including a visible module set, an accessible index dimension, and a data sensitivity level upper limit is constructed;

[0016] The access range parameter and the visible permission boundary are bound and marked with the current operation report generation request.

[0017] Preferably, the step of calculating an initial priority score for each operation report generation request, periodically updating the priority score of each operation report generation request, and dynamically sorting and scheduling is specifically:

[0018] Obtaining the user role permission level, target device risk level, and request urgency of each operation report generation request, and forming a priority influence parameter;

[0019] Weighted fusion calculation is performed on the priority influence parameter to obtain the initial priority score of each operation report generation request;

[0020] According to the initial priority score, the operation report generation requests are sorted to form an initial priority queue;

[0021] According to the set periodic time interval, the priority score of the operation report generation request is recalculated to obtain an updated priority score;

[0022] Based on the updated priority score, the initial priority queue is dynamically adjusted to dynamically sort and schedule the operation report generation requests.

[0023] Preferably, the step of extracting the request task type contained in the operation report generation request, screening the operation indicator set associated with the task type, and calculating the current weight decay value of each operation indicator is specifically:

[0024] Extract the request task type contained in the operation report generation request, and filter the operation index set matched with the task type in the preset task type and operation index relationship library;

[0025] Collect the state parameters of the operation index set, and calculate the weight decay coefficient of the operation index based on the state parameters;

[0026] Get the basic weight value Q i of each operation index in the operation index set, mark the weight decay coefficient as S i , and calculate the current weight decay value of each operation index by the formula P i =Q i ×(1-S i ).

[0027] Preferably, the step of collecting the state parameters of the operation index set and calculating the weight decay coefficient of the operation index based on the state parameters is specifically:

[0028] Collect the state parameters of the operation index set, and the state parameters include data update time, index change trend, and task target correlation level;

[0029] Set a data update time threshold, and if the data update time exceeds the set data update time threshold, increase the timeliness weight decay coefficient;

[0030] If the index change trend and the task target correlation level are low, then increase the trend correlation weight decay coefficient;

[0031] Cumulatively count and normalize the timeliness weight decay coefficient and the trend correlation weight decay coefficient to obtain the weight decay coefficient of the standard operation index.

[0032] Preferably, the step of judging the life cycle stage of each operation index and setting the display strategy of each operation index in the report generation according to the weight decay value is specifically:

[0033] Get the usage frequency and activity of each operation index, and judge the current life cycle stage of each operation index according to the usage frequency and activity;

[0034] Based on the life cycle stage, set a basic display priority, and modify the basic display priority according to the weight decay value to obtain a stage priority;

[0035] Based on the stage priority, set the display strategy of the operation index in the report generation, and arrange the display content according to the display strategy when generating the report.

[0036] Preferably, based on the display strategy, a plurality of versions of operation reports are generated for different user roles, common content modules and role-specific content modules are extracted and combined for output, and the steps are specifically as follows:

[0037] Based on the display strategy, the display position, display form, update frequency and visibility parameters of each operation indicator in the generated report are extracted.

[0038] Based on the user role identifier, the corresponding access range parameter and visible permission boundary are queried, and a plurality of versions of operation reports are generated for different user roles.

[0039] Extract the operation indicator modules commonly contained in all role versions as common content modules, and uniformly fill them into the corresponding positions of each version report.

[0040] Based on the differences between the display strategy and the role requirements, exclusive individual content modules are extracted for each user role and filled into the corresponding version report to solve the display conflict.

[0041] Preferably, the content modules in each version of the operation report are set with a desensitization level identifier, and the steps of matching and displaying control of each content module according to the user role permission level are specifically as follows:

[0042] A unique identifier is set for each content module in each version of the operation report, and a corresponding sensitivity level identifier is set according to the sensitivity of each content module to generate a desensitization level content module.

[0043] A mapping rule table is established between the desensitization level and the permission level, and the accessible state of each desensitization level content module by users with different permission levels is defined.

[0044] Iterate through the content modules in each version of the operation report, and according to the sensitivity level identifier and the user role permission level, call the mapping rule table to determine the display mode, which includes complete display, partial display or hiding.

[0045] According to the display mode, an operation report version matching the current user role permission level is generated.

[0046] In a second aspect, the application provides a personalized medical device operation report generation system, which adopts the following technical solution:

[0047] A personalized medical device operation report generation system comprises:

[0048] The permission management module receives operation report generation requests from a plurality of user terminals, extracts role permission levels, and marks the access range parameter and visible permission boundary of the current operation report generation request.

[0049] The priority scheduling module calculates an initial priority score for each operation report generation request, periodically updates the priority scores of the operation report generation requests, and dynamically sorts and schedules the operation report generation requests;

[0050] The index management module extracts a request task type contained in the operation report generation request, filters an operation index set associated with the task type, and calculates a current weight decay value of each operation index;

[0051] The display strategy module determines a life cycle stage of each operation index, sets a display strategy of each operation index in the generated report in combination with the weight decay value, and outputs the display strategy;

[0052] The report generation module generates multiple versions of operation reports for different user roles based on the display strategy, extracts common content modules and role-specific content modules, and outputs the common content modules and the role-specific content modules;

[0053] The desensitization control module sets a desensitization level identifier for each content module in each version of the operation report, and controls matching display of each content module according to a user role permission level.

[0054] In summary, the present application has at least one of the following beneficial technical effects:

[0055] 1. Collect report generation requests from different user terminals, accurately define the data boundary and permission range accessible by the user by extracting role permission level and marking access range parameters, ensure that the report content conforms to the access permission of different roles, prevent information leakage and permission boundary crossing. By calculating the priority score of each request, the scientific management of the report request processing order is realized, the score is updated periodically to reflect the dynamic state of request waiting time, system load, etc., and dynamic sorting and scheduling ensure that high priority requests are processed first, improve system response efficiency and user experience, effectively avoid resource waste, and improve the flexibility and intelligent level of overall operation management. By identifying the task type in the request, accurately filter the relevant operation indicators according to different business needs, avoid report content redundancy, and improve the pertinence and practicality of information. Calculate the weight decay value of the operation indicator, which helps to dynamically reflect the timeliness, data quality and business relevance of the indicator, improve the accuracy and scientificity of the report, and help users make more accurate decision-making judgments. By judging the life cycle stage of the operation indicator, dynamically adjust the display priority and method of the indicator, make the report content more consistent with the actual value and state of the indicator, and further refine the display strategy combined with the weight decay value, ensure that the report content is both comprehensive and concise, improve the readability and decision support function of the report, and promote the rational allocation of resources and attention. Different user roles generate multiple versions of reports to achieve personalized and differentiated display of content, meet the attention points and information needs of different roles; extract common content modules to ensure the consistency of basic information, and highlight exclusive attention in role-specific modules to enhance the pertinence and practicality of the report, improve user satisfaction and operation efficiency, and ensure that each user can efficiently obtain the most relevant operation information, promote the scientificity and refinement of medical device management. By setting the desensitization level for the content module and combining user permission control display, ensure that different permission users see information within their authorized range, improve compliance while meeting individual display needs, achieve refined content access control, and strengthen the security and management effectiveness of the system.

[0056] 2. By quantifying the number of calls and active performance of operation indicators in actual business, the position of the indicators in the life cycle is determined, the importance and stability of the indicators in the current business scenario are revealed, and the report presents more dynamic business content. The life cycle stage of the indicators is converted into a preliminary display priority, and further modified by combining the weight decay value, so that the priority calculation reflects the important stage characteristics of the indicators, and also considers the decay factors such as data real-time and relevance. The stage priority can more accurately reflect the comprehensive value of the indicators at the current time point, which helps to highlight the most meaningful indicators in the limited display space. The stage priority is converted into an executable display strategy, and the content is arranged strictly according to the display strategy when generating the report, which can ensure the logicality and pertinence of the report information layout, improve the efficiency of quickly grasping key information for different reader roles, and enhance the professionalism and readability of the report.

[0057] 3. By assigning a unique identifier and a sensitive level identifier to each content module, accurate positioning and sensitive classification management of the module are realized, so that the system can take appropriate desensitization measures according to the importance and risk level of the content, effectively preventing sensitive data from being leaked in inappropriate permission range. By constructing the mapping relationship between desensitization level and user permission level, the access range of different permission users to different sensitive content is determined, and the standardization and configurability of access control are realized. Using the matching result of sensitive level and permission level, the specific display mode of each module is determined to ensure that different permission users can only access the content within their permission range when viewing the report; through the flexible combination of three modes of full display, partial display and hidden, the information security can be ensured while the valuable content for users is maximized, improving the balance between the usability and security of the report. According to the display mode determination result, the final operation report version matched with the current user permission level is dynamically generated, realizing accurate personalized report delivery, which not only ensures the compliance and safety of information disclosure, but also provides customized content view for different roles, improving the decision support capability and user experience of the report. BRIEF DESCRIPTION OF DRAWINGS

[0058] Fig. 1 is a specific step schematic diagram of an embodiment of a personalized medical device operation report generation method of the present application.

[0059] Fig. 2 is a module connection schematic diagram of an embodiment of a personalized medical device operation report generation system of the present application. DETAILED DESCRIPTION

[0060] The present application will be further described in detail below in conjunction with embodiments and Figs. 1-2 The embodiments of the present application are not limited to the above.

[0061] The application discloses a personalized medical instrument operation report generation method, and specifically comprises the following steps:

[0062] Step S1, receiving operation report generation requests from multiple user terminals, extracting role permission levels, marking access range parameters and visible permission boundaries of the current operation report generation request;

[0063] Step S2, calculating an initial priority score for each operation report generation request, periodically updating the priority scores of the operation report generation requests, and dynamically sorting and scheduling;

[0064] Step S3, extracting the request task type contained in the operation report generation request, screening the operation index set associated with the task type, and calculating the current weight decay value of each operation index;

[0065] Step S4, judging the life cycle stage of each operation index, combining the weight decay value, and setting the display strategy of each operation index in the generated report;

[0066] Step S5, generating multiple versions of operation reports for different user roles based on the display strategy, extracting common content modules and role individual content modules, and outputting;

[0067] Step S6, setting a desensitization level identifier for each content module in each version of the operation report, and performing matching display control on each content module according to the user role permission level.

[0068] In actual application, report generation requests from different user terminals are collected, the role permission level and the access range parameter are extracted, the data boundary and the permission range accessible by the user are accurately defined, it is ensured that the report content conforms to the access permission of different roles, and information leakage and permission boundary crossing are prevented. By calculating the priority score of each request, the scientific management of the report request processing order is realized, the score is updated periodically to reflect the dynamic state of the request waiting time, system load, etc., and dynamic sorting and scheduling ensure that high-priority requests are processed first, improve the system response efficiency and user experience, effectively avoid resource waste, ensure timely response to critical tasks, and improve the flexibility and intelligent level of overall operation management. By identifying the task type in the request, the relevant operation indicators are accurately selected according to different business needs, the report content redundancy is avoided, and the information pertinence and practicability are improved. The weight decay value of the operation indicator is calculated, which helps to dynamically reflect the timeliness, data quality and business relevance of the indicator, improves the accuracy and scientificity of the report, and helps users make more accurate decision-making judgments. By judging the life cycle stage of the operation indicator, the display priority and mode of the indicator are dynamically adjusted, so that the report content is more in line with the actual value and state of the indicator, and the weight decay value is further refined to ensure that the report content is comprehensive and concise, improve the readability and decision support function of the report, and promote the rational allocation of resources and attention. Different user roles generate multiple versions of reports to realize personalized and differentiated display of content, meet the attention points and information needs of different roles; extract common content modules to ensure the consistency of basic information, and highlight exclusive attention in role-specific modules to enhance the pertinence and practicability of the report, improve user satisfaction and operation efficiency, reduce information redundancy, and ensure that each user can efficiently obtain the most relevant operation information, promoting the scientificity and refinement of medical device management. By setting the desensitization level for the content module and combining user permission control display, it is ensured that different permission users see information within their authorized range, improve compliance while meeting individualized display needs, achieve refined content access control, and strengthen the security and management efficiency of the system.

[0069] The steps of receiving operation report generation requests from multiple user terminals, extracting role permission levels, and marking access range parameters and visible permission boundaries of the current operation report generation request are as follows:

[0070] Step S11, receiving operation report generation requests from multiple user terminals about medical machinery, the operation report generation request containing a user role identifier and a request task type;

[0071] Step S12, extracting the user role identifier, judging the role permission level of the user, and matching the corresponding access range parameter based on the role permission level;

[0072] Step S13, based on the access range parameter, constructing a visible permission boundary containing a visible module set, an accessible index dimension, and an upper limit of data sensitivity level;

[0073] Step S14, binding and marking the access range parameter and the visible permission boundary with the current operation report generation request.

[0074] In actual application, by obtaining the user role identifier and the task type, the identity and business target of the request are determined, providing a basis for subsequent personalized permission judgment and task processing, and ensuring the accuracy and effectiveness of the request. By analyzing the user role identifier, the user's permission level in the system is determined, the access range parameter is matched, and the access boundary of the data is accurately controlled, effectively preventing permission boundary crossing and information leakage, and ensuring the security and compliance of the system. The abstract access range parameter is specified to form a detailed permission boundary framework, accurately defining the data range visible and operable by the user in the report, ensuring information security and meeting the business needs of different users. The access range parameter and the permission boundary are bound with the specific request to ensure that each request carries complete permission information throughout the processing flow, enabling dynamic transfer and application of permissions, ensuring that the system can continuously and accurately perform permission control when multiple processes and modules collaborate, preventing permission loss or misuse, and improving the security and consistency of the system, ensuring accurate implementation of personalized services.

[0075] For each operation report generation request, an initialization priority score is calculated, and the priority scores of each operation report generation request are periodically updated for dynamic sorting and scheduling, which is specifically:

[0076] Step S21, obtaining the user role permission level, target device risk level, and request urgency corresponding to each operation report generation request, forming a priority influence parameter;

[0077] Step S22, performing weighted fusion calculation on the priority influence parameter to obtain the initialization priority score of each operation report generation request;

[0078] Step S23, sorting the operation report generation requests according to the initialization priority score to form an initial priority queue;

[0079] Step S24, recalculating the priority score of the operation report generation request according to the set periodic time interval to obtain an updated priority score;

[0080] Step S25, based on the updated priority score, dynamically adjusting the initial priority queue to dynamically sort and schedule the operation report generation requests.

[0081] In actual application, the user role permission level reflects the identity weight of the request initiator in the system, the target device risk level reflects the urgency of device operation safety, and the request emergency level reflects the immediacy of business demand. Quantifying and integrating multiple influencing factors into a unified priority score, the score serves as the basis for request scheduling, providing data support and decision basis for scientific, fair and efficient request processing order. By sorting requests according to the initial priority score, the system can establish a clear processing sequence, prioritize processing of critical requests with higher scores, ensure timely response to important tasks, effectively avoid request disorder backlog, and improve system response speed and service quality, optimizing resource allocation. Periodic updating of the priority score enables the system to adjust the processing order in a timely manner, preventing long-term low-priority requests from being ignored, improving overall fairness and flexibility, and enhancing the system's ability to adapt to changing environments, ensuring real-time and accurate priority evaluation. By dynamically adjusting the priority queue, the system realizes real-time optimization and adjustment of request processing order, ensuring that the most important or urgent requests can obtain processing resources in a timely manner, improving the system's scheduling efficiency and response speed, and reducing request waiting time and resource waste.

[0082] The step of extracting the request task type contained in the operation report generation request, screening the operation index set associated with the task type, and calculating the current weight decay value of each operation index is specifically:

[0083] Step S31, extract the request task type contained in the operation report generation request, and screen the operation index set matched with the task type in the pre-set task type and operation index relationship library;

[0084] Step S32, collect the state parameters of the operation index set, and calculate the weight decay coefficient of the operation index based on the state parameters;

[0085] Step S33, obtain the basic weight value Q of each operation index in the operation index set i , extract the weight decay coefficient S i , and calculate the current weight decay value of each operation index by the formula P i =Q i ×(1-S i ).

[0086] In actual application, the preset task type and operation index relationship library are used as a knowledge mapping tool to establish a fixed association between different business scenarios and their key operation indexes, so that the system can quickly match the core data range after receiving the request, avoid the interference of irrelevant indexes, and thus improve the pertinence and processing efficiency of report generation. By obtaining the state parameters of each operation index and calculating the weight decay coefficient accordingly, the weight decay coefficient can reflect the change of the reference value of the index in business decision-making, ensuring that when the data is outdated, the quality is degraded, or the relevance is reduced, the system can automatically reduce the influence of the index in report generation, and improve the accuracy and reliability of the report conclusion. The long-term importance (basic weight value Q i ) and real-time effectiveness (decay coefficient S i ) of the index are combined to obtain the final current weight decay value P i by formula calculation, so as to dynamically adjust the contribution of the index in report generation, realize scientific allocation of index weight, and ensure that the finally generated operation report can accurately reflect the current business status.

[0087] The step of collecting the state parameters of the operation index set and calculating the weight decay coefficient of the operation index based on the state parameters is specifically:

[0088] Step S321, collect the state parameters of the operation index set, and the state parameters include data update time, index change trend, and task target correlation level;

[0089] Step S322, set a data update time threshold, and if the data update time exceeds the set data update time threshold, increase the timeliness weight decay coefficient;

[0090] Step S323, if the index change trend and the task target correlation level are low, then increase the trend correlation weight decay coefficient;

[0091] Step S324, accumulate and normalize the timeliness weight decay coefficient and the trend correlation weight decay coefficient to obtain the weight decay coefficient of the standard operation index.

[0092] In actual application, the data update time can reflect the freshness of information, the index change trend reveals the fluctuation direction in time series, and the correlation level of the task target measures the matching degree of the index and the current task demand. By introducing a time threshold, the timeliness of the data is directly related to the index weight decay. When the data update time exceeds the threshold, it means that the index may have lost its real-time guiding significance for the current business, so increasing the timeliness weight decay coefficient can automatically reduce its influence in report generation, thereby improving the real-time performance of the report and the decision reference value. When the trend correlation level is low, even if the index itself is new data, its change direction may not contribute to the task results. By increasing the trend correlation weight decay coefficient, the interference of these low correlation indexes on the report conclusion can be reduced, and the report content can be more focused on the core information required by the task target. Through cumulative statistical method, the influence of different decay factors is quantitatively integrated, and through normalization processing, the results are ensured to be highly comparable within a unified numerical interval. The final standard weight decay coefficient can balance the timeliness and correlation of the two factors, so that the weight adjustment considers the necessity of real-time data and also takes into account the degree of fit with the task target, thereby providing accurate and dynamic index weight allocation basis for operation reports.

[0093] The step of determining the life cycle stage of each operation index and setting the display strategy of each operation index in the generated report according to the weight decay value is specifically:

[0094] In step S41, the usage frequency and activity of each operation index are obtained, and the current life cycle stage of each operation index is determined according to the usage frequency and activity;

[0095] In step S42, based on the life cycle stage, the basic display priority is set, and the basic display priority is corrected according to the weight decay value to obtain the stage priority;

[0096] In step S43, based on the stage priority, the display strategy of the operation index in the generated report is set, and the display content is arranged according to the display strategy when the report is generated.

[0097] In actual application, the position of the operation index in the life cycle, such as introduction period, growth period, mature period and recession period, is determined by quantifying the calling frequency and active performance of the operation index in actual business, so as to reveal the importance and stability of the index in the current business scene, and make the report present more dynamic business content. The life cycle stage of the index is converted into a preliminary display priority, and is further corrected by combining a weight decay value, so that the priority calculation reflects not only the important stage characteristics of the index, but also the decay factors such as data real-time and relevance, and the stage priority can more accurately reflect the comprehensive value of the index at the current time point, which helps to highlight the most meaningful index in the limited display space. The stage priority is converted into an executable display strategy, and the content is arranged strictly according to the display strategy when generating the report, which can ensure the logicality and pertinence of the report information layout, improve the efficiency of quickly grasping key information for different reader roles, and enhance the professionalism and readability of the report.

[0098] Based on the display strategy, the steps of extracting common content modules and role-specific content modules and merging and outputting are as follows:

[0099] Step S51, based on the display strategy, extracting the display position, display form, update frequency and visibility parameters of each operation index in the generated report;

[0100] Step S52, based on the user role identifier, querying the corresponding access range parameter and visibility permission boundary, and generating multiple versions of operation reports for different user roles;

[0101] Step S53, extracting the operation index modules commonly contained in all role versions as common content modules, and uniformly filling them into the corresponding positions of each version report;

[0102] Step S54, based on the display strategy and role requirement difference, extracting exclusive individual content modules for each user role, and filling them into the corresponding version report to solve the display conflict.

[0103] In actual application, by converting the display strategy into specific executable display configuration, the layout position, presentation mode (such as chart, text, comparison table), data update rhythm and visibility requirement of each operation index in the report are determined, so that the generation stage ensures that the organization structure of the report content is clear and the information presentation form is unified, and ensures that the subsequent version generation process can be automatically executed, thereby improving the generation efficiency and consistency. By matching the user role identifier with its corresponding access range and visible permission, it is ensured that different role users can only obtain content within their permission range, and by generating multiple versions of reports according to roles, the differentiated needs of management, operation personnel, regulatory agencies and other roles in information granularity and sensitivity can be met, while effectively preventing information leakage and ensuring data security and compliance. By comparing the contents of multiple versions of reports, identifying index modules that are visible to all roles and consistent in demand, and filling them as common content modules, the workload of repeated generation and maintenance is reduced, and the consistency of different role reports on core data is ensured, facilitating cooperation and decision-making based on the same basic data, and improving the overall comparability and authority of the report. According to the specific information needs and concerns of different roles, combined with the display strategy, personalized content modules are extracted, such as management focusing on operation trends and KPIs, and technical personnel focusing on device operation status and maintenance records. By filling the personalized content modules into the corresponding version reports as needed, and resolving conflicts in a standardized manner, the relevance and readability of the report can be ensured, and the value and decision support effect of the report for different role users can be improved.

[0104] The step of setting a desensitization level identifier for each content module in each version of the operation report and matching and displaying control of each content module according to the user role permission level is as follows:

[0105] Step S61, set a unique identifier for each content module in each version of the operation report, set a corresponding sensitivity level identifier according to the sensitivity of each content module, and generate a desensitization level content module;

[0106] Step S62, establish a mapping rule table between desensitization levels and permission levels, and define the accessible state of each desensitization level content module for users with different permission levels;

[0107] Step S63, traverse the content modules in each version of the operation report, call the mapping rule table according to the sensitivity level identifier and the user role permission level, determine the display mode, and the display mode includes complete display, partial display or hidden;

[0108] Step S64, generate an operation report version matching the current user role permission level according to the display mode.

[0109] In actual application, by assigning a unique identifier and a sensitivity level identifier to each content module, accurate positioning and sensitivity classification management of the module are realized, so that the system can take appropriate desensitization measures according to the importance and risk level of the content, effectively preventing sensitive data from being leaked within inappropriate permission range. By constructing the mapping relationship between the desensitization level and the user permission level, the access range of different permission users to different sensitive content is clearly defined, the regularity and configurability of access control are realized, which provides a basis for subsequent dynamic filtering and personalized display of report content, and can flexibly adapt to organizational structure adjustment, compliance requirement changes and other scenarios, improving the maintainability and adaptability of the system. Using the matching result of the sensitivity level and the permission level, the specific display mode of each module is determined to ensure that different permission users can only access the content within their permission range when viewing the report; through the flexible combination of three modes of full display, partial display and hidden display, the content valuable to users can be maximized while ensuring information security, improving the balance between the usability and security of the report. According to the display mode determination result, the final operation report version matching the current user permission level is dynamically generated, realizing accurate personalized report delivery, which not only ensures the compliance and safety of information disclosure, but also provides customized content view for different roles, improving the decision support capability and user experience of the report.

[0110] A personalized medical device operation report generation system, by applying a personalized medical device operation report generation method as described above, comprising:

[0111] A permission management module receives operation report generation requests from multiple user terminals, extracts role permission levels, and marks the access range parameters and visible permission boundaries of the current operation report generation request;

[0112] A priority scheduling module calculates an initial priority score for each operation report generation request, periodically updates the priority scores of each operation report generation request, and performs dynamic sorting and scheduling;

[0113] An index management module extracts the request task type contained in the operation report generation request, filters the operation index set associated with the task type, and calculates the current weight decay value of each operation index;

[0114] A display strategy module determines the life cycle stage of each operation index, sets the display strategy of each operation index in the generated report in combination with the weight decay value;

[0115] A report generation module generates multiple versions of operation reports for different user roles based on the display strategy, extracts common content modules and role-specific content modules, and outputs them;

[0116] The desensitization control module sets a desensitization level identifier for each content module in the version operation report, and controls the matching display of each content module according to the user role permission level.

[0117] In actual application, the permission management module is used to accurately identify the user role permission and bind the access range and visible boundary, so as to ensure that the subsequent data processing is carried out within the compliance and safety range. The priority scheduling module is used to dynamically calculate and update the task priority based on multi-dimensional parameters, so as to realize efficient sorting and scheduling of the operation report generation request. The index management module is used to filter the relevant operation indexes according to the task type and calculate the weight decay value, so as to reflect the effectiveness and reference value of the index in the current task. The display strategy module is used to set the display strategy in combination with the index life cycle stage and the weight decay value, so as to realize accurate arrangement of the report content and optimization of information presentation. The report generation module is used to generate the multi-version operation report according to the display strategy and the user role, so as to realize fusion output of common and individual content. The desensitization control module is used to control the content display mode according to the sensitive level and the permission level mapping rule, so as to protect the information security and meet the differentiated access demand.

[0118] The above are preferred embodiments of the present application, and do not limit the protection scope of the present application, therefore: any equivalent changes made on the structure, shape, principle of the present application shall be covered within the protection scope of the present application.

Claims

1. A method for generating personalized medical device operational reports, the method comprising: The method comprises the following steps: Receiving operation report generation requests from multiple user terminals, extracting role permission levels, marking access range parameters and visible permission boundaries of the current operation report generation request; Calculate the initial priority score for each operation report generation request, periodically update the priority score of each operation report generation request, and dynamically sort and schedule; Extract the request task type contained in the operation report generation request, filter the operation indicator set associated with the task type, and calculate the current weight decay value of each operation indicator, including the following steps: Extract the request task type contained in the operation report generation request, and filter the operation indicator set matched with the task type in the preset task type and operation indicator relationship library; Collect the state parameters of the operation indicator set, including data update time, indicator trend, and task target correlation level; Set a data update time threshold, and if the data update time exceeds the set data update time threshold, increase the timeliness weight decay coefficient; If the trend correlation level of the indicator trend and the task target is low, then increase the trend correlation weight decay coefficient; Cumulatively count and normalize the timeliness weight decay coefficient and the trend correlation weight decay coefficient to obtain the weight decay coefficient of the standard operation indicator; Obtaining a basic weight value Q of each operation index in the operation index set i , the weight attenuation coefficient is marked as S i , the current weight attenuation value of each operation index is calculated by the formula P i =Q i ×(1-S i ) Determine the life cycle stage of each operation indicator, set the display strategy of each operation indicator in the report generation according to the weight decay value, and generate multiple versions of operation reports for different user roles based on the display strategy, extract common content modules and role individual content modules, and output; Set the desensitization level identifier for each content module in each version of the operation report, and control the matching display of each content module according to the user role permission level, including the following steps: Set a unique identifier for each content module in each version of the operation report, set the corresponding sensitivity level identifier according to the sensitivity of each content module, and generate a desensitization level content module; Establish a mapping rule table between the desensitization level and the permission level, and define the accessible state of each desensitization level content module for users with different permission levels; Iterate through the content modules in each version of the operation report, determine the display mode according to the sensitivity level identifier and the user role permission level, and call the mapping rule table to determine the display mode, including full display, partial display, or hidden; Generate an operation report version matching the current user role permission level according to the display mode. The step of receiving operation report generation requests from multiple user terminals, extracting role permission levels, and marking the access range parameters and visible permission boundaries of the current operation report generation request is specifically:

2. The method of claim 1, wherein, Receiving operation report generation requests from multiple user terminals about medical machinery, the operation report generation request containing user role identification and request task type; Extract the user role identification, determine the role permission level of the user, and match the corresponding access range parameter based on the role permission level; Based on the access range parameter, build a visible permission boundary containing a visible module set, an accessible indicator dimension, and a data sensitivity level upper limit; ​ Binding mark the access range parameter and visible permission boundary with the current operation report generation request.

3. The method of claim 1, wherein the personalized medical device operational report is generated based on the at least one of the plurality of medical device operational parameters. The step of calculating the initialization priority score for each operation report generation request, periodically updating the priority score of each operation report generation request, and dynamically scheduling is specifically: Obtain the user role permission level, target device risk level and request urgency corresponding to each operation report generation request to form a priority influence parameter; Weighted fusion calculation is performed on the priority influence parameter to obtain the initialization priority score of each operation report generation request; According to the initialization priority score, the operation report generation request is sorted to form an initial priority queue; According to the set periodic time interval, the priority score of the operation report generation request is recalculated to obtain an updated priority score; Based on the updated priority score, the initial priority queue is dynamically adjusted to dynamically sort and schedule the operation report generation request.

4. The method of claim 1, wherein, The step of judging the life cycle stage of each operation indicator, and setting the display strategy of each operation indicator in the generated report in combination with the weight decay value is specifically: Obtain the usage frequency and activity of each operation indicator, and judge the current life cycle stage of each operation indicator according to the usage frequency and activity; Based on the life cycle stage, set a basic display priority, and modify the basic display priority in combination with the weight decay value to obtain a stage priority; Based on the stage priority, set the display strategy of the operation indicator in the generated report, and arrange the display content according to the display strategy when generating the report.

5. The method of claim 1, wherein the personalized medical device operational report is generated based on the at least one of the plurality of medical device operational parameters. The step of generating multiple versions of operation reports for different user roles based on the display strategy, extracting common content modules and role-specific content modules and merging and outputting is specifically: Based on the display strategy, extract the display position, display form, update frequency and visibility parameter of each operation indicator in the generated report; Based on the user role identifier, query the corresponding access range parameter and visible permission boundary, and generate multiple versions of operation reports for different user roles; Extract the operation indicator modules commonly contained in all role versions as common content modules, and uniformly fill them into the corresponding positions of each version report; Based on the display strategy and role demand difference, extract exclusive individual content modules for each user role and fill them into the corresponding version report to solve the display conflict.

6. A system for generating individualized medical device operational reports, comprising: The application of the personalized medical instrument operation report generation method according to any one of claims 1-5 comprises: The permission management module receives operation report generation requests from multiple user terminals, extracts role permission levels, and marks the access range parameter and visible permission boundary of the current operation report generation request; The priority scheduling module calculates the initialization priority score for each operation report generation request, periodically updates the priority score of each operation report generation request, and dynamically schedules; The indicator management module extracts the request task type contained in the operation report generation request, filters the operation indicator set associated with the task type, and calculates the current weight decay value of each operation indicator. The display strategy module judges a life cycle stage of each operation index, sets a display strategy of each operation index in generating a report in combination with the weight decay value; The report generation module generates multiple versions of operation reports for different user roles based on the display strategy, extracts common content modules and role individual content modules, and outputs; The desensitization control module sets a desensitization level identifier for each content module in each version of operation report, and controls matching display of each content module according to a user role permission level.

Images