Method and system for generating personalized medical instrument operation report

Abstract

The invention discloses a personalized medical instrument operation report generation method and system, and relates to the technical field of operation report generation. The method comprises the following steps: receiving an operation report generation request, extracting a role permission level, and marking an access range parameter and a visible permission boundary; calculating a priority score for each generation request, and periodically updating the priority scores to perform dynamic sorting scheduling; extracting a request task type, screening an associated operation index set, judging the life cycle stage of the operation index, and setting a display strategy of the operation index in a generated report; multi-version operation reports are generated according to different user roles, and a common content module and a role personalized content module are extracted and output; and setting desensitization level identifiers for the content modules, and performing matching display control on the content modules. According to the invention, on the premise of ensuring data security and compliance, efficient generation, precise customization and differential display of the medical instrument operation report are realized.

Description

Technical Field

[0001] The present application relates to the technical field of operation report generation, and in particular to a method and system for generating personalized medical device operation reports. Background Art

[0002] With the advancement of smart hospital construction, more and more medical institutions are implementing refined management of medical devices through information technology. Operational reports serve as a crucial basis for supporting medical device asset management, optimizing utilization efficiency, and making maintenance decisions. The way they are generated directly impacts management quality.

[0003] Existing medical device operation management systems often use unified templates to generate operational reports, lacking precise visibility control based on user roles and permissions. This makes it difficult to meet the personalized needs of different medical institutions and user roles for report content and format. Furthermore, the priority scheduling mechanism is insufficient, making it impossible to dynamically optimize the order of report generation based on factors such as request urgency and device risk level, hindering the timely response to high-priority tasks. Furthermore, the traditional report generation process lacks an intelligent dynamic adjustment mechanism, resulting in redundant or missing report information, which impacts management efficiency and decision-making effectiveness, leaving room for improvement. Summary of the Invention

[0004] The purpose of the present invention is to provide a method and system for generating personalized medical device operation reports to solve the problems raised in the above background technology.

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

[0006] Receive operation report generation requests from multiple user terminals, extract role permission levels, and mark the access scope 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 requested task type contained in the operation report generation request, filter the set of operation indicators associated with the task type, and calculate the current weight decay value of each operation indicator;

[0009] Determine the life cycle stage of each operating indicator and, based on the weight decay value, set a display strategy for each operating indicator in the generated report;

[0010] Based on the display strategy, multiple versions of operation reports are generated for different user roles, and common content modules and role-specific content modules are extracted and output;

[0011] Set a desensitization level identification for the content modules in each version of the operation report, and match and display each content module according to the user role permission level.

[0012] Preferably, the steps of receiving operation report generation requests from multiple user terminals, extracting role authority levels, and marking access scope parameters and visible authority boundaries of the current operation report generation request are specifically as follows:

[0013] receiving operation report generation requests for medical machinery from a plurality of user terminals, wherein the operation report generation requests include a user role identifier and a requested task type;

[0014] Extract the user role identifier, determine the user's role authority level, and match the corresponding access scope parameters based on the role authority level;

[0015] Based on the access scope parameters, a visible permission boundary is constructed, which includes a visible module set, accessible indicator dimensions, and an upper limit of the data sensitivity level;

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

[0017] Preferably, the steps of calculating an initial priority score for each operation report generation request, periodically updating the priority score of each operation report generation request, and performing dynamic sorting and scheduling are specifically as follows:

[0018] Obtain the user role authority level, target device risk level, and request urgency corresponding to each operation report generation request to form priority impact parameters;

[0019] Performing weighted fusion calculation on the priority impact parameters to obtain an initialization priority score for each operation report generation request;

[0020] sorting the operation report generation requests according to the initialization priority scores to form an initial priority queue;

[0021] Recalculating the priority score of the operation report generation request according to a set periodic time interval 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 steps of extracting the requested task type contained in the operation report generation request, screening the set of operation indicators associated with the task type, and calculating the current weight decay value of each operation indicator are specifically as follows:

[0024] Extract the requested task type contained in the operation report generation request, and filter the operation indicator set that matches the task type in the preset task type and operation indicator relationship library;

[0025] Collecting state parameters of the set of operating indicators, and calculating weight attenuation coefficients of the operating indicators based on the state parameters;

[0026] Get the basic weight value Q of each operating indicator in the operating indicator set i , extract the weight attenuation coefficient and mark it as S i , through the formula P i =Q i × (1-S i ) Calculate the current weight attenuation value of each operating indicator.

[0027] Preferably, the step of collecting the state parameters of the set of operating indicators and calculating the weight attenuation coefficient of the operating indicators based on the state parameters is specifically as follows:

[0028] Collecting status parameters of the operational indicator set, the status parameters including data update time, indicator change trend, and relevance level with task objectives;

[0029] Set a data update time threshold. If the data update time exceeds the set data update time threshold, increase the timeliness weight attenuation coefficient;

[0030] If the correlation level between the indicator change trend and the task goal is low, then the trend correlation weight attenuation coefficient is increased;

[0031] The timeliness weight attenuation coefficient and the trend correlation weight attenuation coefficient are cumulatively counted and normalized to obtain the weight attenuation coefficient of the standard operating indicator.

[0032] Preferably, the steps of determining the life cycle stage of each operating indicator and setting the display strategy of each operating indicator in the generated report in combination with the weight decay value are as follows:

[0033] Obtain the usage frequency and activity of each operational indicator, and determine the current life cycle stage of each operational indicator based on the usage frequency and activity;

[0034] Based on the life cycle stage, a basic display priority is set, and the basic display priority is modified in combination with the weight decay value to obtain a stage priority;

[0035] Based on the stage priorities, set a display strategy for the operational indicators in the generated report, and arrange the display content according to the display strategy when generating the report.

[0036] Preferably, based on the display strategy, multiple versions of operation reports are generated for different user roles, and the steps of extracting common content modules and role-specific content modules and merging and outputting them are specifically as follows:

[0037] Based on the display strategy, extract the display position, display format, update frequency and visibility parameters of each operating indicator in the generated report;

[0038] Based on the user role identifier, query the corresponding access scope parameters and visible permission boundaries, and generate multiple versions of operation reports for different user roles;

[0039] Extract the operational indicator modules that are common to all role versions as common content modules and fill them uniformly into the corresponding positions of each version report;

[0040] Based on the differences in display strategies and role requirements, exclusive personalized content modules are extracted for each user role and filled into the corresponding version report to resolve display conflicts.

[0041] Preferably, the steps of setting a desensitization level identifier for the content modules in each version of the operation report and performing matching display control on each content module according to the user role authority level are as follows:

[0042] 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 desensitized content module;

[0043] Establish a mapping rule table between desensitization levels and permission levels, and define the access status of users with different permission levels to content modules at each desensitization level;

[0044] Traversing the content modules in each version of the operation report, calling the mapping rule table according to the sensitivity level identifier and the user role authority level, and determining the display mode, wherein the display mode includes full display, partial display or hiding;

[0045] Based on the display mode, an operation report version that matches the current user role authority level is generated.

[0046] In a second aspect, the present application provides a system for generating personalized medical device operation reports, which adopts the following technical solutions:

[0047] A system for generating personalized medical device operation reports, comprising:

[0048] The authority management module receives operation report generation requests from multiple user terminals, extracts role authority levels, and marks the access scope parameters and visible authority boundaries of the current operation report generation request;

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

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

[0051] A display strategy module determines the life cycle stage of each operating indicator and sets the display strategy of each operating indicator in the generated report based on the weight decay value;

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

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

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

[0055] 1. Collect report generation requests from different user terminals. By extracting role permission levels and annotating access scope parameters, the data boundaries and permission scopes accessible to each user are accurately defined, ensuring that report content complies with the access permissions of different roles and preventing information leakage and permission violations. By calculating a priority score for each request, scientific management of the order in which report requests are processed is achieved. The score is periodically updated to reflect dynamic conditions such as request waiting time and system load. Dynamic sorting and scheduling ensure that high-priority requests are processed first, improving system response efficiency and user experience, effectively avoiding resource waste, and enhancing the flexibility and intelligence of overall operations management. By identifying the task type in the request, relevant operational indicators are accurately screened for different business needs, avoiding report content redundancy and improving the relevance and practicality of information. Calculating the weight decay value of the operational indicator helps to dynamically reflect the timeliness, data quality, and business relevance of the indicator, improving the accuracy and scientific nature of the report and helping users make more accurate decisions. By determining the lifecycle stage of operational indicators, the display priority and method of indicators are dynamically adjusted to ensure that the report content is more consistent with the actual value and status of the indicators. The display strategy is further refined in combination with weight decay values ​​to ensure that the report content is both comprehensive and concise, improve the report's readability and decision-making support functions, and promote the rational allocation of resources and attention. Multiple versions of reports are generated for different user roles to achieve personalized and differentiated content display, meeting the concerns and information needs of different roles. Common content modules are extracted to ensure the consistency of basic information, and role-specific modules highlight exclusive concerns, enhancing the relevance and practicality of reports, improving user satisfaction and operational efficiency, ensuring that each user can efficiently obtain the most relevant operational information, and promoting scientific and refined medical device management. By setting desensitization levels for content modules and combining them with user permission control display, users with different permissions are ensured to see information that meets their authorized scope, improving compliance while meeting personalized display needs, achieving refined content access control, and strengthening system security and management efficiency.

[0056] 2. By quantifying the number of calls and active performance of operational indicators in actual business, we can determine their position in the life cycle, reveal the importance and stability of the indicators in the current business scenario, and make the report present content that is more in line with business dynamics. Convert the life cycle stage of the indicator into a preliminary display priority, and further modify it in combination with the weight decay value, so that the priority calculation not only reflects the important stage characteristics of the indicator, but also comprehensively considers decay factors such as data real-time and relevance. The obtained stage priority can more accurately reflect the comprehensive value of the indicator at the current point in time, which helps the report highlight the most meaningful indicators in a limited display space. Convert the stage priority into an executable display strategy, and strictly follow the display strategy for content arrangement when generating the report. This can ensure the logic and pertinence of the report information layout, improve the efficiency of different reader roles in quickly grasping key information, and enhance the professionalism and readability of the report.

[0057] 3. By assigning each content module a unique identifier and sensitivity level, precise module location and sensitivity classification management are achieved. This allows the system to take appropriate desensitization measures based on the importance and risk level of the content, effectively preventing the leakage of sensitive data within inappropriate permissions. By mapping desensitization levels to user permission levels, the access scope of different users with different permissions to different sensitive content is clarified, achieving regularized and configurable access control. Using the matching results of sensitivity levels and permission levels, a specific display mode is determined for each module, ensuring that users with different permissions can only access content within their permission scope when viewing reports. Through the flexible combination of full display, partial display, and hidden modes, information security is ensured while maximizing the preservation of user-valued content, thus improving the balance between report usability and security. Based on the display mode determination results, a final operational report version is dynamically generated that matches the current user permission level, achieving precise and personalized report delivery. This not only ensures the compliance and security of information disclosure, but also provides customized content views for different roles, enhancing the report's decision-making capabilities and user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] Figure 1 It is a schematic diagram of the specific steps of an embodiment of a method for generating a personalized medical device operation report of the present invention.

[0059] Figure 2 The present invention is a module connection diagram of a system for generating personalized medical device operation reports according to an embodiment of the present invention. DETAILED DESCRIPTION

[0060] Below is a combination of the embodiments and Figure 1-Figure 2 The present invention will be described in further detail, but the embodiments of the present invention are not limited thereto.

[0061] The present invention discloses a method for generating a personalized medical device operation report, which specifically includes the following steps:

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

[0063] Step S2: Calculate an 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;

[0064] Step S3: extract the requested task type contained in the operation report generation request, filter the set of operation indicators associated with the task type, and calculate the current weight decay value of each operation indicator;

[0065] Step S4: determining the life cycle stage of each operating indicator and, in combination with the weight decay value, setting a display strategy for each operating indicator in the generated report;

[0066] Step S5: Based on the display strategy, generate multiple versions of operation reports for different user roles, extract common content modules and role-specific content modules, and output them;

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

[0068] In practice, report generation requests from different user terminals are collected. By extracting role permission levels and annotating access scope parameters, the data boundaries and permission scopes accessible to each user are accurately defined, ensuring that report content complies with the access rights of different roles and preventing information leakage and permission violations. By calculating a priority score for each request, the order in which report requests are processed is scientifically managed. The score is periodically updated to reflect dynamic conditions such as request wait time and system load. Dynamic sorting and scheduling ensure that high-priority requests are processed first, improving system response efficiency and user experience, effectively avoiding resource waste, ensuring timely response to critical tasks, and enhancing the flexibility and intelligence of overall operations management. By identifying the task type in the request, relevant operational indicators are precisely selected for different business needs, avoiding report redundancy and improving the relevance and practicality of information. Calculating weight decay values ​​for operational indicators helps dynamically reflect the timeliness, data quality, and business relevance of the indicators, improving the accuracy and scientific nature of reports and helping users make more accurate decisions. By assessing the lifecycle phase of operational indicators, the system dynamically adjusts the indicator's display priority and method, ensuring that report content is more consistent with the indicator's actual value and status. The weight decay value is then combined to further refine the display strategy, ensuring that the report content is both comprehensive and concise, improving the report's readability and decision-making support capabilities, and promoting the rational allocation of resources and attention. Multiple versions of reports are generated for different user roles, enabling personalized and differentiated content display to meet the concerns and information needs of different roles. Common content modules are extracted to ensure consistency of basic information, while role-specific modules highlight specific concerns, enhancing the report's relevance and practicality, improving user satisfaction and operational efficiency, and reducing information redundancy. This ensures that each user can efficiently access the most relevant operational information, promoting scientific and refined medical device management. By setting desensitization levels for content modules and combining them with user permission control display, users with different permissions are ensured to see information consistent with their authorization scope, improving compliance while meeting personalized display needs. This achieves refined content access control and strengthens system security and management efficiency.

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

[0070] Step S11, receiving operation report generation requests for medical machinery from multiple user terminals, wherein the operation report generation requests include a user role identifier and a requested task type;

[0071] Step S12: extract the user role identifier, determine the user's role authority level, and match the corresponding access scope parameters based on the role authority level;

[0072] Step S13: Based on the access scope parameters, construct a visible permission boundary including a visible module set, accessible indicator dimensions, and an upper limit of a data sensitivity level;

[0073] Step S14: Bind and mark the access scope parameter and visible authority boundary with the current operation report generation request.

[0074] In actual use, by obtaining the user role identifier and task type, the identity and business objectives of the request are clarified, providing a basis for subsequent personalized permission judgment and task processing, and ensuring the accuracy and effectiveness of the request. By parsing the user role identifier, the user's permission level in the system is determined, and the access scope parameters are matched, precise control of data access boundaries is achieved, effectively preventing permission violations and information leakage, and ensuring the security and compliance of the system. The abstract access scope parameters are concretized to form a detailed permission boundary framework, accurately defining the scope of data visible and operable by users in reports, which not only ensures information security but also meets the business needs of different users. The access scope parameters and permission boundaries are bound to specific requests to ensure that each request carries complete permission information throughout the entire processing flow, realizing the dynamic transmission and application of permissions, and ensuring that the system can continuously and accurately perform permission control when multiple processes and multiple modules collaborate, preventing permission loss or misuse, improving the security and consistency of the system, and ensuring the precise implementation of personalized services.

[0075] The steps for calculating the initial priority score for each operation report generation request, periodically updating the priority score of each operation report generation request, and performing dynamic sorting and scheduling are as follows:

[0076] Step S21: Obtain the user role authority level, target device risk level, and request urgency corresponding to each operation report generation request to form a priority impact parameter;

[0077] Step S22: performing weighted fusion calculation on the priority impact parameters to obtain an initialization priority score for each operation report generation request;

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

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

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

[0081] In practical 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 operational safety, and the request urgency reflects the immediacy of the business need. These multiple influencing factors are quantified and integrated into a unified priority score. This score serves as the basis for request scheduling, providing data support and a decision-making foundation for a scientific, fair, and efficient request processing sequence. By sorting requests according to their initial priority scores, the system establishes a clear processing sequence, prioritizing critical requests with higher scores, ensuring timely response to important tasks, effectively preventing unordered request backlogs, improving system responsiveness and service quality, and optimizing resource allocation. Periodic updates to priority scores enable the system to adjust the processing order in a timely manner, preventing long-term neglect of low-priority requests. This improves overall fairness and flexibility, enhances the system's adaptability to changing environments, and ensures the real-time and accurate nature of priority assessment. Dynamically adjusting the priority queue enables real-time optimization and adjustment of the request processing order, ensuring that the most important or urgent requests receive processing resources promptly. This improves system scheduling efficiency and responsiveness, and reduces request wait time and resource waste.

[0082] The steps for extracting the requested task type contained in the operation report generation request, filtering the set of operation indicators associated with the task type, and calculating the current weight decay value of each operation indicator are as follows:

[0083] Step S31: extract the requested task type contained in the operation report generation request, and select an operation indicator set that matches the task type from a preset task type and operation indicator relationship library;

[0084] Step S32: collecting state parameters of the operation indicator set, and calculating weight attenuation coefficients of the operation indicators based on the state parameters;

[0085] Step S33: Obtain the basic weight value Q of each operating indicator in the operating indicator set. i , extract the weight attenuation coefficient and mark it as S i , through the formula P i =Q i × (1-S i ) Calculate the current weight attenuation value of each operating indicator.

[0086] In actual application, the preset task type and operation indicator relationship library is used as a knowledge mapping tool to establish a fixed association between different business scenarios and their key operation indicators, so that the system can quickly match the core data range after receiving the request, avoiding the interference of irrelevant indicators, thereby improving the pertinence and processing efficiency of report generation. By obtaining the status parameters of each operation indicator and calculating the weight decay coefficient based on this, the weight decay coefficient can reflect the current reference value changes of the indicator in business decision-making, ensuring that when the data is outdated, the quality is reduced, or the relevance is reduced, the system can automatically reduce the influence of the indicator in report generation, thereby improving the accuracy and reliability of the report conclusions. The long-term importance of the indicator (basic weight value Q i ) and real-time effectiveness (attenuation coefficient S i ) is combined and the final current weight attenuation value P is calculated by the formula i , thereby dynamically adjusting the contribution of indicators in report generation, achieving scientific allocation of indicator weights, and ensuring that the final generated operation report can accurately reflect the current business status.

[0087] The steps of collecting the state parameters of the set of operating indicators and calculating the weight attenuation coefficient of the operating indicators based on the state parameters are specifically as follows:

[0088] Step S321: collecting status parameters of the operational indicator set, wherein the status parameters include data update time, indicator change trend, and relevance level with task objectives;

[0089] Step S322: setting a data update time threshold. If the data update time exceeds the set data update time threshold, increasing the timeliness weight attenuation coefficient.

[0090] Step S323: if the correlation level between the indicator change trend and the task goal is low, then increase the trend correlation weight attenuation coefficient;

[0091] Step S324: performing cumulative statistics and normalization processing on the timeliness weight attenuation coefficient and the trend correlation weight attenuation coefficient to obtain the weight attenuation coefficient of the standard operation indicator.

[0092] In actual application, the data update time can reflect the freshness of information, the indicator change trend reveals its fluctuation direction in the time series, and the correlation level with the task goal measures the degree of match between the indicator and the current task requirements. By introducing a time threshold, a direct correlation is established between the timeliness of the data and the indicator weight decay. When the data update time exceeds the threshold, it means that the indicator may have lost its real-time guidance significance for the current business. Therefore, increasing the timeliness weight decay coefficient can automatically reduce its influence in report generation, thereby improving the real-time nature and decision-making reference value of the report. When the trend correlation level is low, even if the indicator itself is new data, its change direction may not make a substantial contribution to the task results. By increasing the trend correlation weight decay coefficient, the interference of these low-correlation indicators on the report conclusions can be reduced, ensuring that the report content is more focused on the core information required for the task objectives. The impact of different attenuation factors is quantitatively integrated through cumulative statistics, and normalization is used to ensure that the results are highly comparable within a unified numerical range. The final generated standard weight attenuation coefficient can balance the timeliness and relevance factors, so that the weight adjustment takes into account both the necessity of real-time data and the degree of fit with the task objectives, thereby providing an accurate and dynamic basis for indicator weight allocation for operational reports.

[0093] Determine the life cycle stage of each operating indicator and, in combination with the weight decay value, set the display strategy for each operating indicator in the generated report. Specifically,

[0094] Step S41: Obtain the usage frequency and activity of each operating indicator, and determine the current life cycle stage of each operating indicator based on the usage frequency and activity;

[0095] Step S42: Based on the life cycle stage, a basic display priority is set, and the basic display priority is modified in combination with the weight decay value to obtain a stage priority;

[0096] Step S43: Based on the stage priorities, a display strategy for the operation indicators in the generated report is set, and display content is arranged according to the display strategy when the report is generated.

[0097] In actual application, by quantifying the number of calls and active performance of operational indicators in actual business, its position in the life cycle, such as the introduction period, growth period, maturity period, and decline period, is determined, revealing the importance and stability of the indicator in the current business scenario, so that the report can present content that is more in line with business dynamics. The life cycle stage of the indicator is converted into a preliminary display priority, and further modified in combination with the weight decay value, so that the priority calculation reflects the important stage characteristics of the indicator and comprehensively considers decay factors such as data real-time and relevance. The obtained stage priority can more accurately reflect the comprehensive value of the indicator at the current point in time, which helps the report highlight the most reference-worthy indicators in a limited display space. Converting the stage priority into an executable display strategy and strictly arranging the content in accordance with the display strategy when generating the report can ensure the logic and pertinence of the report information layout, improve the efficiency of different reader roles in quickly grasping key information, and enhance the professionalism and readability of the report.

[0098] Based on the display strategy, multiple versions of operation reports are generated for different user roles, and the common content modules and role-specific content modules are extracted and merged for output. Specifically, the steps are:

[0099] Step S51: extracting the display position, display format, update frequency, and visibility parameters of each operating indicator in the generated report based on the display strategy;

[0100] Step S52: Based on the user role identifier, query the corresponding access scope parameters and visible permission boundaries, and generate multiple versions of operation reports for different user roles;

[0101] Step S53: extract the common operation indicator modules in all role versions as common content modules, and fill them uniformly into the corresponding positions of each version report;

[0102] In step S54, based on the display strategy and the difference in role requirements, a dedicated personalized content module is extracted for each user role and filled into the corresponding version report to resolve the display conflict.

[0103] In practice, by translating presentation strategies into specific executable presentation configurations, the report layout, presentation format (e.g., charts, text, comparison tables), data update cadence, and visibility requirements for each operational indicator are clearly defined. This ensures a clear organizational structure and consistent information presentation during the report generation phase, and ensures that subsequent version generation processes can be automated, thereby improving generation efficiency and consistency. By matching user role identifiers with their corresponding access scopes and visibility permissions, users of different roles can only access content within their scope of permissions. By generating multiple versions of reports by role, the differentiated information granularity and sensitivity requirements of different roles, such as management, operations personnel, and regulators, can be met, while effectively preventing information leakage and ensuring data security and compliance. By comparing the content of multiple versions of reports, indicator modules that are visible to all roles and have consistent requirements are identified and uniformly populated as common content modules. This not only reduces the workload of repeated generation and maintenance, but also ensures consistency in core data across reports for different roles, facilitating collaboration and decision-making based on the same underlying data, and enhancing the overall comparability and authority of the reports. Based on the specific information needs and concerns of different roles, personalized content modules are extracted in combination with display strategies. For example, management focuses on operational trends and KPIs, while technical personnel focus on equipment operating status and maintenance records. By filling personalized content modules into the corresponding version of the report as needed and resolving conflicts in a regular manner, the report's pertinence and readability can be ensured, thereby enhancing the report's usage value and decision-making support effect for users of different roles.

[0104] Set a desensitization level for each content module in each version of the operation report, and perform matching display control on each content module based on the user role permission level. The specific steps are 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 based on the sensitivity of each content module, and generate a desensitized content module;

[0106] Step S62: Establish a mapping rule table between desensitization levels and authority levels, defining the accessibility status of users of different authority levels to content modules of each desensitization level;

[0107] Step S63, traversing the content modules in each version of the operation report, calling the mapping rule table according to the sensitivity level identifier and the user role authority level, and determining the display mode, wherein the display mode includes full display, partial display, or hidden;

[0108] Step S64: Generate an operation report version that matches the current user role authority level according to the display mode.

[0109] In actual use, by assigning a unique identifier and sensitivity level identification to each content module, the precise positioning of the module and the management of sensitivity classification are achieved, so that the system can take corresponding desensitization measures according to the importance and risk level of the content, effectively preventing the leakage of sensitive data within the scope of inappropriate permissions. By constructing a mapping relationship between desensitization levels and user permission levels, the access scope of different sensitive content for users with different permissions is clarified, and access control is regularized and configurable, providing a basis for the dynamic filtering and personalized display of subsequent report content. It can flexibly adapt to scenarios such as organizational structure adjustments and changes in compliance requirements, thereby improving the maintainability and adaptability of the system. Using the matching results of sensitivity levels and permission levels, a specific display mode is determined for each module to ensure that users with different permissions can only obtain content within their permission scope when viewing the report; through the flexible combination of the three modes of full display, partial display, and hiding, while ensuring information security, it is possible to retain content that is valuable to users to the maximum extent, thereby improving the balance between the usability and security of the report. Based on the display mode judgment results, the final operation report version that matches the current user's permission level is dynamically generated, achieving accurate personalized report delivery. This not only ensures the compliance and security of information disclosure, but also provides customized content views for different roles, improving the report's decision-making support capabilities and user experience.

[0110] A system for generating a personalized medical device operation report, by applying the above-mentioned method for generating a personalized medical device operation report, comprises:

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

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

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

[0114] A display strategy module determines the life cycle stage of each operating indicator and sets the display strategy of each operating indicator in the generated report based on 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 the content modules in each version of the operation report, and controls the matching display of each content module based on the user role permission level.

[0117] In actual application, the permission management module is used to accurately identify user role permissions and bind access scopes and visible boundaries to ensure that subsequent data processing is carried out within the scope of compliance and security. The priority scheduling module is used to dynamically calculate and update task priorities based on multi-dimensional parameters to achieve efficient sorting and scheduling of operation report generation requests. The indicator management module is used to filter relevant operation indicators by task type and calculate weight decay values ​​to reflect the effectiveness and reference value of the indicators in the current task. The display strategy module is used to set display strategies based on the indicator life cycle stage and weight decay values ​​to achieve precise arrangement of report content and optimization of information presentation. The report generation module is used to generate multiple versions of operation reports based on display strategies and user roles to achieve the integrated output of common and individual content. The desensitization control module is used to control the content display mode according to the sensitivity level and permission level mapping rules to ensure information security and meet differentiated access requirements.

[0118] The above are all preferred embodiments of the present application, and are not intended to limit the scope of protection of the present application. Therefore, any equivalent changes made based on the structure, shape, and principle of the present application should be included in the scope of protection of the present application.

Claims

1. A method for generating a personalized medical device operation report, characterized in that: The following steps are involved: Receive operation report generation requests from multiple user terminals, extract role permission levels, and mark the access scope 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 perform dynamic sorting and scheduling; Extract the requested task type contained in the operation report generation request, filter the set of operation indicators associated with the task type, and calculate the current weight decay value of each operation indicator; Determine the life cycle stage of each operating indicator and, based on the weight decay value, set a display strategy for each operating indicator in the generated report; Based on the display strategy, multiple versions of operation reports are generated for different user roles, and common content modules and role-specific content modules are extracted and output; Set a desensitization level identification for the content modules in each version of the operation report, and match and display each content module according to the user role permission level.

2. The method for generating a personalized medical device operation report according to claim 1, characterized in that: The steps of receiving operation report generation requests from multiple user terminals, extracting role authority levels, and marking access scope parameters and visible authority boundaries of the current operation report generation request are specifically as follows: receiving operation report generation requests for medical machinery from a plurality of user terminals, wherein the operation report generation requests include a user role identifier and a requested task type; Extract the user role identifier, determine the user's role authority level, and match the corresponding access scope parameters based on the role authority level; Based on the access scope parameters, a visible permission boundary is constructed, which includes a visible module set, accessible indicator dimensions, and an upper limit of the data sensitivity level; The access scope parameter and visible permission boundary are bound and marked with the current operation report generation request.

3. The method for generating a personalized medical device operation report according to claim 1, characterized in that: The steps of calculating an initial priority score for each operation report generation request, periodically updating the priority score of each operation report generation request, and performing dynamic sorting and scheduling are specifically as follows: Obtain the user role authority level, target device risk level, and request urgency corresponding to each operation report generation request to form priority impact parameters; Performing weighted fusion calculation on the priority impact parameters to obtain an initialization priority score for each operation report generation request; sorting the operation report generation requests according to the initialization priority scores to form an initial priority queue; Recalculating the priority score of the operation report generation request according to a set periodic time interval 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 requests.

4. The method for generating a personalized medical device operation report according to claim 1, characterized in that: The steps of extracting the requested 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 are specifically as follows: Extract the requested task type contained in the operation report generation request, and filter the operation indicator set that matches the task type in the preset task type and operation indicator relationship library; Collecting state parameters of the set of operating indicators, and calculating weight attenuation coefficients of the operating indicators based on the state parameters; Get the basic weight value Q of each operating indicator in the operating indicator set i , extract the weight attenuation coefficient and mark it as S i , through the formula P i =Q i × (1-S i ) Calculate the current weight attenuation value of each operating indicator.

5. The method for generating a personalized medical device operation report according to claim 4, characterized in that: The step of collecting the state parameters of the set of operating indicators and calculating the weight attenuation coefficient of the operating indicators based on the state parameters is specifically as follows: Collecting status parameters of the operational indicator set, the status parameters including data update time, indicator change trend, and relevance level with task objectives; Set a data update time threshold. If the data update time exceeds the set data update time threshold, increase the timeliness weight attenuation coefficient; If the correlation level between the indicator change trend and the task goal is low, then the trend correlation weight attenuation coefficient is increased; The timeliness weight attenuation coefficient and the trend correlation weight attenuation coefficient are cumulatively counted and normalized to obtain the weight attenuation coefficient of the standard operating indicator.

6. The method for generating a personalized medical device operation report according to claim 1, characterized in that: The steps of determining the life cycle stage of each operating indicator and setting the display strategy of each operating indicator in the generated report in combination with the weight decay value are specifically as follows: Obtain the usage frequency and activity of each operational indicator, and determine the current life cycle stage of each operational indicator based on the usage frequency and activity; Based on the life cycle stage, a basic display priority is set, and the basic display priority is modified in combination with the weight decay value to obtain a stage priority; Based on the stage priorities, set a display strategy for the operational indicators in the generated report, and arrange the display content according to the display strategy when generating the report.

7. The method for generating a personalized medical device operation report according to claim 1, characterized in that: The steps 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 them are specifically as follows: Based on the display strategy, extract the display position, display format, update frequency and visibility parameters of each operating indicator in the generated report; Based on the user role identifier, query the corresponding access scope parameters and visible permission boundaries, and generate multiple versions of operation reports for different user roles; Extract the operational indicator modules that are common to all role versions as common content modules and fill them uniformly into the corresponding positions of each version report; Based on the differences in display strategies and role requirements, exclusive personalized content modules are extracted for each user role and filled into the corresponding version report to resolve display conflicts.

8. The method for generating a personalized medical device operation report according to claim 1, characterized in that: The steps of setting a desensitization level identifier for the content modules in each version of the operation report and matching and displaying each content module according to the user role permission level are specifically as follows: 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 desensitized content module; Establish a mapping rule table between desensitization levels and permission levels, and define the access status of users with different permission levels to content modules at each desensitization level; Traversing the content modules in each version of the operation report, calling the mapping rule table according to the sensitivity level identifier and the user role authority level, and determining the display mode, wherein the display mode includes full display, partial display or hiding; Based on the display mode, an operation report version that matches the current user role authority level is generated.

9. A system for generating personalized medical device operation reports, characterized in that: A method for generating a personalized medical device operation report according to any one of claims 1 to 8 is applied, comprising: The authority management module receives operation report generation requests from multiple user terminals, extracts role authority levels, and marks the access scope parameters and visible authority boundaries of the current operation report generation request; The priority scheduling module calculates the initial priority score for each operation report generation request, periodically updates the priority score of each operation report generation request, and performs dynamic sorting and scheduling; The indicator management module extracts the requested task type contained in the operation report generation request, filters the set of operation indicators associated with the task type, and calculates the current weight decay value of each operation indicator; A display strategy module determines the life cycle stage of each operating indicator and sets the display strategy of each operating indicator in the generated report based on the weight decay value; 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; The desensitization control module sets a desensitization level identifier for the content modules in each version of the operation report, and controls the matching display of each content module based on the user role permission level.

Images