Medical equipment configuration management method, system, storage medium and medical equipment

Abstract

The present invention is applicable to the field of medical device technology and provides a medical device configuration management method, system, storage medium, and medical device. The method includes: responding to a user's selection operation instruction for a target configuration file, reading and parsing all parameter configuration items in the target configuration file, and displaying the current values ​​of all parameter configuration items in a structured manner on a configuration preview interface; performing anomaly detection when parsing the target configuration file, and highlighting the abnormal parameter items in the configuration preview interface when abnormal parameter items are detected; responding to a user's modification operation instruction for a parameter configuration item in the target configuration file, receiving the user's selected parameter configuration value to update the target configuration file; and responding to a user's configuration application instruction for the target configuration file, loading the updated configuration parameters into the medical device. The present invention solves the problems of low efficiency in existing parameter configuration selection and the inability to timely understand configuration file changes.

Description

Technical Field

[0001] The present invention relates to the technical field of medical equipment, and in particular to a medical equipment configuration management method, system, storage medium and medical equipment. Background Art

[0002] With the rapid development of medical technology, the sophistication and complexity of modern medical equipment have increased significantly, and their functionality is highly dependent on diverse parameter configurations. Currently, most medical devices (such as monitors and medical equipment) are equipped with parameter configuration files, allowing users to differentiate parameters such as heart rate, blood oxygen, and blood pressure based on clinical needs. However, existing technologies have the following significant drawbacks in practical applications:

[0003] First, the visualization and interaction efficiency of configuration parameters are insufficient. The configuration parameters of medical equipment are usually scattered across multiple independent setting interfaces, and medical staff need to enter different interfaces one by one to view specific parameter values. For example, the heart rate parameters and blood oxygen parameters of the monitor are located in different submenus, and users cannot preview all configuration contents in a unified view. When the device stores multiple sets of configuration files, medical staff need to repeatedly load different configurations and switch multiple interfaces for manual verification. The operation is cumbersome and inefficient, especially in emergency diagnosis and treatment scenarios, which may delay treatment.

[0004] Secondly, there is a lack of a configuration anomaly detection mechanism. In the existing technology, when the configuration file is missing or exceeds the limit due to equipment failure, storage error or human error, the device system usually automatically replaces it with the default configuration, but lacks the active prompt function for abnormal parameters. Medical staff cannot be notified of configuration anomalies in a timely manner, which may cause the device to operate with incorrect parameters without an alarm. For example, if the blood oxygen parameter value exceeds the preset range (such as setting it to 120 instead of the reasonable range of 0-100), although the system automatically corrects it to the default value, there is no abnormality mark on the interface, which can easily cause medical staff to misjudge, posing potential medical risks and even leading to clinical disputes.

[0005] Furthermore, the parameter presentation lacks intuitiveness. Existing configuration management interfaces often display parameter names and values ​​in a text list format, which differs significantly from the graphical layout of the device's actual parameter setting interface. Medical staff must repeatedly compare the text list with the parameter setting interface, making it difficult to quickly determine whether key parameter configurations meet clinical requirements, increasing the possibility of human misinterpretation.

[0006] Therefore, improving the efficiency of parameter configuration selection for medical devices, avoiding the risks associated with configuration anomalies, and ensuring that medical staff are informed of configuration file changes in a timely manner have become pressing challenges in current medical device design. Solving these issues is crucial for improving the user experience of medical devices and ensuring patient safety. Summary of the Invention

[0007] Based on this, the purpose of the present invention is to provide a medical device configuration management method, system, storage medium and medical device to fundamentally solve the problems of low efficiency of existing parameter configuration selection and inability to timely understand configuration file changes.

[0008] A medical device configuration management method according to an embodiment of the present invention is applied to a medical device having a display interface, wherein the display interface of the medical device provides a configuration management interface, the configuration management interface including a configuration selection interface and a configuration preview interface, the method comprising:

[0009] Displaying identification information of multiple configuration files stored in the medical device in the configuration selection interface;

[0010] In response to a user's selection operation instruction for a target configuration file, read and parse all parameter configuration items in the target configuration file, and display the current values ​​of all parameter configuration items in the target configuration file in a structured manner in a configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device;

[0011] When parsing the target configuration file, the target configuration file is detected for anomalies, and when an abnormal parameter item is detected, the abnormal parameter item is highlighted in the configuration preview interface, and the abnormal configuration value corresponding to the abnormal parameter item is replaced with the default configuration value associated with the abnormal parameter item;

[0012] In response to a modification operation instruction of a parameter configuration item in a target configuration file by a user in a configuration preview interface, receiving a parameter configuration value selected by the user to update the target configuration file;

[0013] In response to the user's configuration application instruction for the target configuration file, the configuration parameters in the updated target configuration file are loaded into the operating environment of the medical device.

[0014] In addition, a medical device configuration management method according to the above embodiment of the present invention may also have the following additional technical features:

[0015] Furthermore, the step of reading and parsing all parameter configuration items in the target configuration file includes:

[0016] Read and identify the format of the target configuration file, wherein the format includes XML format, JSON format and INI format;

[0017] Select a corresponding target parser according to the format of the target configuration file;

[0018] The target configuration file is read using the selected target parser, and parsed according to the grammatical rules of the format of the target configuration file to extract all parameter configuration items in the target configuration file.

[0019] Furthermore, the target configuration file adopts a segmented structure, and each segment contains at least one parameter configuration item;

[0020] The step of parsing according to the grammatical rules of the format of the target configuration file includes:

[0021] defining a set of parsing states, each of the parsing states corresponding to a specific syntax element in the target configuration file;

[0022] Determine the next parsing state based on the current parsing state and the currently read character or line content;

[0023] During the state transition process, corresponding parsing operations are performed to gradually complete the parsing of the target configuration file, wherein the parsing operations include extracting at least one of a paragraph name, a parameter name, and a parameter value.

[0024] Furthermore, the step of parsing according to the grammatical rules of the format of the target configuration file includes:

[0025] Determining the start and end tags of paragraphs in the target configuration file according to the grammatical rules of the format of the target configuration file;

[0026] Identify all paragraphs in the target configuration file based on the paragraph start and end tags;

[0027] In each of the above paragraphs, analyze and identify each parameter configuration item one by one.

[0028] Furthermore, the step of parsing according to the grammatical rules of the format of the target configuration file includes:

[0029] When the target configuration file is in XML format, identifying tags, attributes and content based on XML syntax rules, and extracting names and values ​​of parameter configuration items therefrom;

[0030] When the target configuration file is in JSON format, objects, arrays, and key-value pairs are identified based on JSON syntax rules, and the names and values ​​of parameter configuration items are extracted therefrom;

[0031] When the target configuration file is in INI format, based on the INI file syntax rules, the sections, keys and values ​​are identified, and the names and values ​​of the parameter configuration items are extracted therefrom.

[0032] Furthermore, the step of displaying the current values ​​of all parameter configuration items in the target configuration file in a structured manner in the configuration preview interface includes:

[0033] Reading and parsing a target configuration file, and converting data in the target configuration file into a data structure processable by the medical device, wherein the data structure includes an array, a list, a tree structure, or a hash table;

[0034] Constructing a user interface element for configuring the preview interface according to the data structure, wherein the user interface element includes at least one of a table, a tree control, a group box, a tab, and a foldable panel;

[0035] Bind the current values ​​of the parameter configuration items in the data structure to the user interface elements, and display the current values ​​of all parameter configuration items on the user interface elements.

[0036] Furthermore, the step of constructing user interface elements of the configuration preview interface according to the data structure includes:

[0037] Create corresponding group display areas according to the group information of the parameter configuration items in the data structure;

[0038] Create corresponding tree nodes according to the hierarchical relationship of parameter configuration items in the data structure;

[0039] Automatically display parameter configuration items in pages according to the number of parameter configuration items in the data structure and the size of the display area;

[0040] Create corresponding display controls based on the type of parameter configuration items in the data structure.

[0041] Furthermore, the step of constructing user interface elements of the configuration preview interface according to the data structure further includes:

[0042] Obtain the display style information of the parameter configuration items used in the parameter setting interface of the medical device;

[0043] Set the display style of the user interface elements in the configuration preview interface based on the obtained display style information.

[0044] Furthermore, the step of binding the current value of the parameter configuration item in the data structure with the user interface element includes:

[0045] Establish a two-way data binding relationship between each parameter configuration item in the data structure and the corresponding user interface element in the configuration preview interface;

[0046] When the current value of a parameter configuration item in the data structure changes, the display of the corresponding user interface element in the configuration preview interface is automatically updated;

[0047] When the user modifies the value of a parameter configuration item according to the user interface element in the configuration preview interface, the current value of the corresponding parameter configuration item in the data structure is automatically updated.

[0048] Another embodiment of the present invention is also intended to provide a medical device configuration management system, which is applied to a medical device having a display interface, wherein the display interface of the medical device provides a configuration management interface, wherein the configuration management interface includes a configuration selection interface and a configuration preview interface, and the system includes:

[0049] A configuration selection interface display module, used to display identification information of multiple configuration files stored in the medical device in the configuration selection interface;

[0050] a configuration preview interface display module, configured to read and parse all parameter configuration items in the target configuration file in response to a user's selection operation instruction for the target configuration file, and display the current values ​​of all parameter configuration items in the target configuration file in a structured manner in the configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device;

[0051] A target configuration file anomaly detection module is used to detect anomalies in the target configuration file when parsing the target configuration file. When an abnormal parameter item is detected, the abnormal parameter item is highlighted in the configuration preview interface, and the abnormal configuration value corresponding to the abnormal parameter item is replaced with the default configuration value associated with the abnormal parameter item.

[0052] A parameter configuration item modification module is used to respond to a modification operation instruction of a parameter configuration item in a target configuration file by a user in a configuration preview interface, receive a parameter configuration value selected by the user to update the target configuration file;

[0053] The configuration file configuration application module is used to load the configuration parameters in the updated target configuration file into the operating environment of the medical device in response to the user's configuration application instruction for the target configuration file.

[0054] Another embodiment of the present invention aims to provide a storage medium storing a program, which implements the medical device configuration management method as described above when executed by a processor.

[0055] Another embodiment of the present invention aims to provide a medical device comprising a memory, a processor, and a program stored in the memory and executable on the processor, wherein the processor implements the medical device configuration management method as described above when executing the program.

[0056] The medical device configuration management method provided by the embodiment of the present invention provides a configuration preview interface, so that the current values ​​of all parameter configuration items can be viewed without loading, and adopts a structured display method to facilitate quick search and comparison; at the same time, by automatically performing anomaly detection when parsing the configuration file, various abnormal situations of the configuration file can be discovered in time, and medical staff can be informed through highlighting, error prompts, etc., thereby solving the problems of low efficiency of existing parameter configuration selection and inability to timely understand configuration file changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 is a flow chart of a medical device configuration management method in a first embodiment of the present invention;

[0058] Figure 2 is a structural diagram of a medical device configuration management system in a second embodiment of the present invention;

[0059] Figure 3 is a structural diagram of a medical device in a third embodiment of the present invention;

[0060] The following specific embodiments will further illustrate the present invention in conjunction with the above-mentioned drawings. DETAILED DESCRIPTION

[0061] To facilitate understanding of the present invention, the present invention will be described more fully below with reference to the accompanying drawings. The drawings illustrate several embodiments of the present invention. However, the present invention may be implemented in many different forms and is not limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and comprehensive understanding of the present invention.

[0062] It should be noted that when an element is referred to as being "fixed to" another element, it may be directly on the other element or there may be an intermediate element. When an element is referred to as being "connected to" another element, it may be directly connected to the other element or there may be an intermediate element. The terms "vertical," "horizontal," "left," "right," and similar expressions used herein are for illustrative purposes only.

[0063] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one skilled in the art to which this invention pertains. The terms used in this specification of the present invention are for the purpose of describing specific embodiments only and are not intended to limit the present invention. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed items.

[0064] Example 1

[0065] See also Figure 1, which shows a medical device configuration management method in a first embodiment of the present invention. For ease of description, only the parts related to the embodiment of the present invention are shown. The medical device configuration management method provided by the embodiment of the present invention includes:

[0066] Step S10, displaying identification information of multiple configuration files stored in the medical device in the configuration selection interface;

[0067] In one embodiment of the present invention, the medical device configuration management method is applied to a medical device with a display interface, which includes a processor, memory, a display screen, input devices (such as a touch screen, buttons, knobs, etc.), and related hardware and software modules. Specifically, the medical device's display interface provides a configuration management interface, which includes a configuration selection interface and a configuration preview interface.

[0068] The configuration selection interface displays the identification information (e.g., file name, configuration name, version number, etc.) of all configuration files stored in the medical device's memory in a list, table, or icon format. The user can then select a target configuration file for preview or application using input devices such as a touchscreen, buttons, or knobs. The configuration preview interface displays the current values ​​of all parameter configuration items in the target configuration file in a structured manner, even without loading the target configuration file. Specifically, the medical device's memory stores multiple configuration files, each containing a set of parameter configuration items and their values. Configuration files are stored in XML, JSON, INI, CSV, or a custom binary format. Configuration files may include metadata such as creation time, modification time, version number, author, applicable device model, applicable patient type, and clinical application scenario. When the user selects a target configuration file in the configuration selection interface, the medical device's processor reads the contents of the configuration file from memory. This reading process includes operations such as opening the file, reading data, and closing the file.

[0069] Step S20, in response to the user's selection operation instruction for the target configuration file, reading and parsing all parameter configuration items in the target configuration file, and displaying the current values ​​of all parameter configuration items in the target configuration file in a structured manner in the configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device;

[0070] In one embodiment of the present invention, when the medical device obtains the user's selection operation instruction for the target configuration file, it reads and parses all parameter configuration items in the target configuration file. Specifically, the steps include:

[0071] Read and identify the target configuration file format, including XML format, JSON format and INI format;

[0072] Select the corresponding target parser according to the format of the target configuration file;

[0073] Use the selected target parser to read the contents of the target configuration file, parse it according to the grammatical rules of the target configuration file format, and extract all parameter configuration items in the target configuration file.

[0074] Furthermore, the target configuration file adopts a segmented structure, and each segment contains at least one parameter configuration item; the step of parsing according to the grammatical rules of the format of the target configuration file includes:

[0075] Define a set of parsing states, each of which corresponds to a specific syntax element in the target configuration file;

[0076] Determine the next parsing state based on the current parsing state and the currently read character or line content;

[0077] During the state transition process, corresponding parsing operations are performed to gradually complete the parsing of the target configuration file. The parsing operations include extracting at least one of a paragraph name, a parameter name, and a parameter value.

[0078] Furthermore, the step of parsing according to the grammatical rules of the format of the target configuration file includes:

[0079] Determine the start and end tags of paragraphs in the target configuration file according to the grammatical rules of the target configuration file format;

[0080] Identify all paragraphs in the target configuration file based on their start and end tags;

[0081] In each paragraph, parse and identify each parameter configuration item one by one.

[0082] Furthermore, the step of parsing according to the grammatical rules of the format of the target configuration file includes:

[0083] When the target configuration file is in XML format, it identifies tags, attributes, and content based on XML syntax rules, and extracts the names and values ​​of parameter configuration items from them;

[0084] When the target configuration file is in JSON format, it identifies objects, arrays, and key-value pairs based on JSON syntax rules, and extracts the names and values ​​of parameter configuration items from them;

[0085] When the target configuration file is in INI format, the section, key, and value are identified based on the INI file syntax rules, and the name and value of the parameter configuration item are extracted from it.

[0086] Specifically, when the medical device receives the user's selection operation instruction for the target configuration file, it reads the first few bytes (or the first few lines) of the target configuration file, identifies the feature information of the file format from them, and determines the file format based on the feature information of the file content. Specifically, if the file starts with "<?xml", or starts with "<" and the subsequent characters conform to the naming rules of XML tags, it is determined to be in XML format. If the file starts with "{", or "[", it is determined to be in JSON format. If the file starts with "[", or contains multiple "=" (equal signs), and the strings on both sides of the equal sign conform to the naming rules of key names and key values, it is determined to be in INI format. If none of the above conditions are met, it can try to identify according to the features of the custom format, or prompt the user to manually specify the file format. And store the identified file format information (such as an enumeration value or a string) in a variable for subsequent steps to use.

[0087] Furthermore, according to the identified file format, select the corresponding target parser. Usually, an XML parser (such as a SAX-based parser, a DOM-based parser, or a custom XML parser) is selected for XML format files. Usually, a JSON parser is selected for JSON format files. Usually, an INI parser is selected for INI format files. Each parser implements a specific parsing algorithm and can correctly extract the information in the configuration file according to the syntax rules of the corresponding format.

[0088] Furthermore, a data structure (such as a parameter list, parameter dictionary, or segmented dictionary, etc.) is created to store the information of all parsed parameter configuration items. Furthermore, the state of the parser is initialized (such as "start", "read paragraph name", "read key name", etc.); then, variables such as the current paragraph and the current parameter configuration item are initialized; then, according to the format characteristics of the target configuration file and the grammatical rules of the target configuration file format, the paragraph identifiers of the target configuration file, specifically the start tag and the end tag, are read; then, based on the paragraph identifiers, the corresponding paragraphs are identified; then, in the paragraph content, each parameter configuration item is read and parsed one by one, specifically, the name and value of the parameter configuration item are identified; if the target configuration file format supports it, other attributes such as the data type, unit, value range, and default value of the parameter configuration item can also be identified. Furthermore, based on the format of the target configuration file and the characteristics of the parser, the content of the target configuration file is read and parsed character by character or line by line. When the target configuration file is in XML format, the parser identifies tags, attributes, and content based on XML syntax rules, and extracts the names and values ​​of parameter configuration items. When the target configuration file is in JSON format, the parser identifies objects, arrays, and key-value pairs based on JSON syntax rules, and extracts the names and values ​​of parameter configuration items. When the target configuration file is in INI format, the parser identifies sections, keys, and values ​​based on INI file syntax rules, and extracts the names and values ​​of parameter configuration items. Specifically, the parser maintains a state variable internally that represents the current parsing state (e.g., "waiting for section start," "reading section name," "reading key name," "reading key value," etc.). Based on the current state and the currently read character or line content, the parser determines the next action to perform (e.g., extracting section name, key name, key value, state transition, etc.). The parser transitions between different states based on predefined syntax rules (such as XML tag rules, JSON key-value pair rules, and INI paragraph and key-value rules). During state transitions, it performs corresponding parsing operations, including extracting paragraph names, parameter names, parameters, and other parameter attributes (such as data types, units, and ranges, if defined in the configuration file). The extracted parameter information (parameter configuration items) is ultimately stored in a data structure. The parsing process repeats the segment-by-segment reading and parsing steps until all segments and parameter configuration items in the configuration file have been parsed, completing the parsing of the entire target configuration file. Upon completion, the parser returns a data structure storing the parsed results. Furthermore, if the parsing process encounters a non-compliant configuration file format (such as mismatched XML tags, missing colons in JSON, missing equal signs in INI), or if the configuration file contains invalid characters or data types, parsing stops, error information is recorded (such as error type, error location, and error cause), and an error message is displayed to the user (such as on the configuration preview interface).

[0089] Specifically, for XML format file parsing, the steps include starting from the beginning of the target configuration file, initializing the parsing state to "START (waiting for the tag to start)", reading the target configuration file character by character, and performing the following state transitions and operations according to the current parsing state and the currently read character: If the current parsing state is "START" and the currently read character is "<", the parsing state is converted to "TAG_NAME (read tag name)"; if the current parsing state is "TAG_NAME" and the currently read character is a space or ">", the string before the currently read character is used as the tag name, and according to the currently read character: if the currently read character is a space, the parsing state is converted to "ATTR_NAME (read attribute name)"; if the currently read character is ">", the parsing state is converted to "CONTENT (read tag content)"; if the current parsing state is "ATTR_NAME", the attribute is parsed according to the "key=value" format, and the parameter sequence number and parameter value are read. Specifically, it is read character by character until "=" is encountered. At this time, the content between these characters is the attribute name. Upon encountering an "=", the parsing state is switched to "ATTR_VALUE (read attribute value)". The attribute value is then read until a quotation mark (single or double) matching the quotation mark that begins the attribute value is encountered, and the parsing state is switched to "CONTENT". If the current parsing state is "CONTENT" and the currently read character is "<", the next character is further determined: if the next character is " / ", the parsing state is switched to "waiting for closing tag". Otherwise, the parsing state is switched to "TAG_NAME", and nested tags are recursively processed. If the current parsing state is "CLOSING_TAG (read closing tag)", the closing tag name is read and compared with the most recently opened tag name. If a match occurs, parsing of the current tag is completed. The above steps are repeated until all characters in the target configuration file have been read. At this point, the name of each tag is used as the paragraph name (or the paragraph name is determined according to predefined rules). The attribute name and attribute value within the tag, or the text content of the tag, are used as the name and value of the parameter configuration item.

[0090] Specifically, for JSON format file parsing, the steps include starting from the beginning of the target configuration file, initializing the parsing state to "START (initial state)"; reading the target configuration file character by character, and performing the following state transitions and operations based on the current parsing state and the currently read character: If the current parsing state is "START" and the currently read character is "{", the parsing state is converted to "IN_OBJECT (parsing object (key-value pair collection))"; if the current parsing state is "START" and the currently read character is "[", the parsing state is converted to "IN_ARRAY (parsing array)"; if the current parsing state is "IN_OBJECT", the key-value pair is parsed according to the "key: value" format, and the parsing state is converted to "EXPECT_COLON (expecting to read a colon)"; specifically, in the "IN_OBJECT" parsing state, read the key name (string); read the colon (:); read the key value (which can be a string, a number, a Boolean value, null, a nested object or an array); if a comma "," is encountered, continue reading the next key-value pair. If a "}" is encountered, the current object is parsed. If the current parsing status is "IN_ARRAY," an array is being parsed. The array element is parsed and the parsing status is changed to "EXPECT_VALUE." If the current parsing status is "EXPECT_COLON" and the character currently read is ":," the parsing status is changed to "EXPECT_VALUE." If the current parsing status is "EXPECT_VALUE," the type of the value (string, number, Boolean, null, nested object, or array) is determined based on the character currently read and parsed accordingly. If a comma "," is encountered, the next array element is read. If a "]" is encountered, the array is parsed. If a string, number, Boolean, or null value is encountered, its value is read directly. If a nested object or array is encountered, the JSON parsing process is recursively invoked for parsing. The above steps are repeated until all characters in the target configuration file have been read. At this point, the key name of each object is used as the name of the parameter configuration item, and the key value is used as the value of the parameter configuration item. The key name of the currently parsed object, or as defined in the configuration file, is used as the section name.

[0091] Specifically, for INI format file parsing, the steps include starting from the beginning of the target configuration file, initializing the parsing state to "START (initial state)"; reading the target configuration file line by line, and performing the following state transitions and operations according to the current parsing state and the currently read line content: If the current parsing state is "START" and the currently read line content begins with "[", the parsing state is converted to "IN_SECTION (parsing paragraph)" and the string in the square brackets is extracted as the paragraph name; if the current parsing state is "START" and the currently read line content begins with "[", the parsing state is converted to "IN_SECTION (parsing paragraph)" and the string in the square brackets is extracted as the paragraph name; if the current parsing state is "START" and the currently read line content If the current parsing state contains an "=", the parsing state is changed to "IN_KEY (parsing key name)". If the current parsing state is "IN_SECTION" and the current line contains an "=", the parsing state is changed to "IN_KEY". If the current parsing state is "IN_KEY", the string to the left of the equal sign is extracted as the key name, and the parsing state is changed to "IN_VALUE (parsing key value)". If the current parsing state is "IN_VALUE", the string to the right of the equal sign (until the end of the line or a comment) is extracted as the key value. Blank lines or comments (such as lines starting with ";") are ignored. The above steps are repeated until all lines in the target configuration file have been read. At this point, each section name is used as the section identifier, the key name of each key-value pair is used as the name of the parameter configuration item, and the key value is used as the value of the parameter configuration item.

[0092] After parsing, the parameter configuration item information is stored in a data structure within the medical device. This data structure includes, for example, a parameter list, a parameter dictionary, or a segment dictionary. A parameter list is a list in which each element is a parameter configuration item object, containing information such as the parameter's name, value, type, unit, and section. A parameter dictionary is a dictionary whose keys are parameter names and whose values ​​are parameter configuration item objects. A segment dictionary is a nested dictionary in which the outer dictionary's keys are segment names and its values ​​are another dictionary (the parameter dictionary for that segment).

[0093] In one embodiment of the present invention, the step of displaying the current values ​​of all parameter configuration items in the target configuration file in a structured manner in the configuration preview interface includes:

[0094] Reading and parsing a target configuration file, and converting data in the target configuration file into a data structure processable by the medical device, wherein the data structure includes an array, a list, a tree structure, or a hash table;

[0095] Constructing a user interface element for configuring the preview interface according to the data structure, wherein the user interface element includes at least one of a table, a tree control, a group box, a tab, and a foldable panel;

[0096] Bind the current values ​​of the parameter configuration items in the data structure to the user interface elements, and display the current values ​​of all parameter configuration items on the user interface elements.

[0097] Specifically, after parsing the read target configuration file, the medical device converts the data therein into a data structure that the medical device can process. The parsing process includes performing syntax analysis on the target configuration file to check whether the target configuration file conforms to the predefined format specifications. If the target configuration file passes the syntax analysis, at least one of the following information is extracted: the name, identifier, current value, data type, unit, value range, default value, and group information of all parameter configuration items in the target configuration file. If the target configuration file fails the syntax analysis, an error message is generated and displayed in the configuration preview interface. The parsed data is stored in a data structure in memory, which can be an array, list, tree structure, hash table, etc.

[0098] Furthermore, according to the parsed data structure, the user interface elements of the configuration preview interface are dynamically constructed. The steps of constructing the user interface elements of the configuration preview interface according to the data structure include:

[0099] Create corresponding group display areas according to the group information of the parameter configuration items in the data structure;

[0100] Create corresponding tree nodes according to the hierarchical relationship of parameter configuration items in the data structure;

[0101] Automatically display parameter configuration items in pages according to the number of parameter configuration items in the data structure and the size of the display area;

[0102] Create corresponding display controls based on the type of parameter configuration items in the data structure.

[0103] Specifically, based on the grouping information of the parameter configuration items, corresponding group boxes (GroupBox), tab pages (TabPage), foldable panels (CollapsiblePanel), etc. are created, and the parameter configuration items within each group display area are displayed. If there is a hierarchical relationship between the parameter configuration items, a tree control (TreeView) is created, with each node representing a parameter category or a parameter configuration item. If there are a large number of parameter configuration items, they are automatically paged according to the size of the display area, and page turning controls (buttons, page numbers) are provided. Based on the type of parameter configuration item, corresponding display controls are created, including: numeric input boxes for displaying and editing numeric parameter configuration items; drop-down lists for displaying and editing enumeration parameter configuration items; switch controls or check boxes for displaying and editing Boolean parameter configuration items; text boxes for displaying and editing text parameter configuration items; and date / time selectors for displaying and editing date / time parameter configuration items.

[0104] Furthermore, the step of constructing user interface elements of the configuration preview interface according to the data structure also includes:

[0105] Obtain the display style information of the parameter configuration items used in the parameter setting interface of the medical device;

[0106] The display style of the user interface element in the configuration preview interface is set according to the acquired display style information, where the display style includes at least one of font, font size, color, background color, alignment, boldness, and italics.

[0107] The style information of the medical device parameter setting interface is obtained and used to set the user interface elements of the configuration preview interface to maintain the same style. The construction process uses code to dynamically generate user interface elements or reads user interface description files (such as XML) to generate user interface elements.

[0108] Furthermore, the step of binding the current value of the parameter configuration item in the data structure to the user interface element includes:

[0109] Establish a two-way data binding relationship between each parameter configuration item in the data structure and the corresponding user interface element in the configuration preview interface;

[0110] When the current value of a parameter configuration item in the data structure changes, the display of the corresponding user interface element in the configuration preview interface is automatically updated;

[0111] When the user modifies the value of a parameter configuration item according to the user interface element in the configuration preview interface, the current value of the corresponding parameter configuration item in the data structure is automatically updated.

[0112] Furthermore, the medical device stores display order information for parameter configuration items. When constructing the user interface elements of the configuration preview interface, the display order of each parameter configuration item is determined based on this display order information. The display priority of the parameter configuration items can also be obtained; parameter configuration items with higher display priority are preferentially displayed in the configuration preview interface. Furthermore, when the configuration preview interface is initialized, the display state saved when the configuration preview interface was last closed is automatically loaded. This display state includes: the collapsed / folded state of the group; the currently displayed page; and the expanded / folded state of the tree structure. It should be noted that in this embodiment of the present invention, by displaying the current values ​​of all parameter configuration items in the target configuration file in a structured manner, all parameter configuration items can be viewed solely within the configuration preview interface. This avoids the inefficient visualization and interaction of configuration parameters that are typically scattered across multiple independent setting interfaces in existing medical device configurations. Furthermore, by synchronizing the display style information for parameter configuration items used in the medical device's parameter setting interface with the display style in the configuration preview interface, medical personnel are facilitated and the complexity of the configuration layout is reduced. Furthermore, during the entire preview process, the medical device does not load any parameter values ​​from the target configuration file into the device's operating environment. This means that the preview operation does not change the current operating status or configuration parameters of the medical device. The preview interface displays the parameter values ​​stored in the target configuration file, not the parameter values ​​currently used by the medical device. This avoids the inefficient parameter configuration selection problem that requires frequent loading of different parameter configuration files and switching between multiple interfaces for manual verification.

[0113] Step S30: When parsing the target configuration file, perform anomaly detection on the target configuration file, and when an abnormal parameter item is detected, highlight the abnormal parameter item in the configuration preview interface, and replace the abnormal configuration value corresponding to the abnormal parameter item with the default configuration value associated with the abnormal parameter item;

[0114] In one embodiment of the present invention, the step of performing anomaly detection on the target configuration file includes:

[0115] One or more anomaly detection rule bases are pre-stored in the medical device, each rule base containing one or more sets of rules for detecting a specific type of anomaly;

[0116] When parsing the target configuration file, the system checks the parameter configuration items in the target configuration file one by one according to the rules in the anomaly detection rule base to determine whether there are any anomalies.

[0117] If an abnormal parameter item is detected, abnormal information is recorded, where the abnormal information includes at least one of an identifier of the abnormal parameter item, an abnormal type, an abnormal value, and an association rule.

[0118] The anomaly detection rules include at least one of the following:

[0119] Parameter value range rules specifically define the value range of each parameter configuration item, including minimum and maximum values. If the value of a parameter configuration item exceeds the specified value range, it is considered abnormal;

[0120] Parameter relationship rules specifically define the logical relationships between different parameter configuration items, including mutually exclusive relationships, dependency relationships, and inclusion relationships. A mutually exclusive relationship means that two or more parameter configuration items cannot be set to specific values ​​at the same time; a dependency relationship means that the value of one parameter configuration item depends on the value of another parameter configuration item; and an inclusion relationship means that the value of one parameter configuration item must be included in the set of values ​​of another parameter configuration item. If the relationship between parameter configuration items does not comply with the parameter relationship rules, it is determined to be an exception.

[0121] Parameter type rules: specifically define the data type of each parameter configuration item, including numeric, enumeration, Boolean, text, and date / time types. If the data type of the value of a parameter configuration item does not conform to the parameter type rules, it is considered an exception;

[0122] Parameter combination rules: specifically define the validity of the combination of multiple parameter configuration items. If the combination of multiple parameter configuration items is not within the predefined valid combination, it is considered an exception;

[0123] Parameter change rate rule: specifically limits the change range of parameter configuration items within a period of time. If the change range of the value of the parameter configuration item exceeds the change range limit, it is determined to be abnormal;

[0124] Custom rules: Allow users to customize anomaly detection rules according to specific needs. Custom rules are defined using scripting language or graphical interface.

[0125] Furthermore, according to the rules in the anomaly detection rule base, the parameter configuration items in the target configuration file are checked one by one to determine whether an anomaly exists. The steps include:

[0126] reading all rules in an anomaly detection rule base, the rule base being stored in the medical device in a structured data format;

[0127] For each parameter configuration item in the target configuration file, traverse each rule in the anomaly detection rule base in turn to determine whether the current parameter configuration item is applicable to the target rule;

[0128] If the current parameter configuration item is applicable to the target rule, the current value of the parameter configuration item and the values ​​of other related parameter configuration items are obtained according to the definition of the target rule;

[0129] According to the definition of the target rule, calculate or judge whether the current parameter configuration item meets the requirements of the target rule;

[0130] If the requirements of the target rule are not met, the current parameter configuration item is determined to be abnormal, and abnormal information is recorded, wherein the abnormal information includes at least one of the name of the abnormal parameter configuration item, the abnormality type, the violated rule, the current value, and the recommended value;

[0131] If the requirements of the target rule are met, the next rule will be checked until all rules have been checked;

[0132] If all rules are checked and no exceptions are found, the current parameter configuration item is considered normal.

[0133] Specifically, if the rule execution results indicate a parameter configuration item is abnormal, the abnormality information is stored in an abnormality list. The corresponding display control (such as a text box or drop-down list) is found on the configuration preview interface and highlighted. This highlighting can be achieved by changing the background color (e.g., to red), changing the font color (e.g., to red) or style (e.g., bold), adding a special icon (e.g., a warning icon or an error icon), displaying a prompt (e.g., displaying error text next to the control or a pop-up bubble prompt), or flashing the display. The default value for the parameter configuration item is also searched. The default value can come from the default value defined in the anomaly detection rule, a predefined default value table for the medical device, or the default value defined in the parameter configuration item itself. The current value of the parameter configuration item is then replaced with the found default value. The in-memory copy of the configuration file is updated, updating the abnormal value to the default value. The display of the parameter configuration item on the configuration preview interface is updated to show the default value. If there is a two-way data binding between the configuration preview interface and the parameter configuration item, the interface will automatically update after the default value is updated. If there is no two-way data binding, the interface control display must be manually updated. The system then continues to iterate over other rules in the rule base until all rules have been checked. After all parameter configuration items have been checked, the system summarizes the anomaly information and displays the total number of anomalies, anomaly type distribution, and other information in specific areas of the configuration preview interface (such as the top status bar or sidebar). A "show only anomaly items" filter is available to facilitate quick viewing of all anomaly configurations.

[0134] Step S40, in response to a modification operation instruction of a parameter configuration item in a target configuration file by a user in the configuration preview interface, receiving a parameter configuration value selected by the user to update the target configuration file;

[0135] In one embodiment of the present invention, after the configuration preview interface is loaded, the medical device will continuously monitor user operations on the interface, particularly interactions with the parameter configuration item display area. These monitored operations include, but are not limited to, mouse clicks, keyboard input, touchscreen gestures (e.g., clicks and swipes), and knob rotations.

[0136] When a user triggers a modification operation in the display area of ​​a parameter configuration item (such as clicking a text box, selecting a drop-down list, toggling a switch control, etc.), the medical device will identify the target parameter configuration item that the user wants to modify based on the location of the trigger event and the control type. The identification process can be achieved in the following ways:

[0137] Control association: When creating a display control for each parameter configuration item (such as a text box or drop-down list), it is associated with the corresponding parameter configuration item data (such as through the control's ID, label, or custom properties).

[0138] Event bubbling / capture: Use the event bubbling or capture mechanism to search upward from the control that triggers the event to find the parent element associated with the parameter configuration item.

[0139] Coordinate calculation: For touch screen or mouse operations, the coordinates triggered by the event can be used to calculate the display area of ​​the parameter configuration item in which the coordinates are located.

[0140] After identifying the target parameter configuration item, the medical device switches the display control for that parameter configuration item to edit mode. The edit mode manifests differently for different control types. A numeric input box displays a text box where the cursor enters, allowing the user to enter a new value via the keyboard, adjust the value by clicking a fine-tuning button (plus / minus), or adjust the value by sliding a slider. A drop-down list expands the drop-down list to display all available values, allowing the user to select a new option by clicking. A switch control allows the user to toggle the switch state (on / off) by clicking. A checkbox allows the user to check or uncheck a checkbox by clicking. A text box displays a text box where the cursor enters, allowing the user to enter or edit text via the keyboard. A pop-up box / sidebar displays a dedicated edit dialog box or sidebar containing more detailed parameter information and editing controls, allowing the user to make more detailed modifications. In edit mode, the medical device continuously monitors the user's input and captures new parameter values ​​entered by the user in real time. Different control types receive input in different ways. Numeric input boxes accept characters such as numbers, decimal points, and negative signs entered from the keyboard, or receive adjustment events of fine-tuning buttons and sliders. Drop-down lists receive events in which users select options in the drop-down list. Switch controls / checkboxes receive click events from the user and toggle the control state based on the click event. Text boxes receive text characters entered from the keyboard.

[0141] After receiving a new parameter value entered by the user, the medical device can immediately perform input validation to ensure the validity of the new value. Validation types include: type validation, which checks whether the new value conforms to the parameter configuration item's data type (e.g., numeric, string, Boolean, etc.); range validation, which checks whether the new value is within the parameter configuration item's allowable range (e.g., minimum and maximum values); format validation, which checks whether the new value conforms to predefined format requirements (e.g., date format, time format, email format, etc.); and association validation, which checks whether the new value conflicts with other parameter configuration items (e.g., mutually exclusive relationships, dependencies). If a validation fails, the medical device can reject the new value and retain the original parameter configuration item; display an error message to the user (e.g., displaying error text next to the control, pop-up notification bubble, changing the control border color, etc.); or automatically correct the new value to the closest legal value. If the new parameter value entered by the user passes validation, the medical device updates the new value to the in-memory copy of the target configuration file. It is important to note that only in-memory data structures (e.g., arrays, lists, tree structures, etc.) are modified, not the configuration file on disk. If there is a two-way data binding between the configuration preview interface and the parameter configuration item, the interface will automatically update to display the new parameter value after updating the memory copy. If there is no two-way data binding, you need to manually update the display of the interface control to make it show the new parameter value.

[0142] When the user completes the parameter modification and triggers the confirmation operation (such as clicking the "OK" button, pressing the Enter key, clicking other controls, etc.); or the user cancels the parameter modification (such as clicking the "Cancel" button, pressing the Esc key, etc.); or the user switches to editing other parameter configuration items; the editing mode ends at this time, and the control returns to the normal display state.

[0143] It's important to note that medical devices can provide a batch modification function, allowing users to select multiple parameters at once and then modify them collectively. Medical devices can also offer Undo and Redo functions, allowing users to undo the most recent modification or redo undone modifications. This undo / redo functionality can be implemented using design patterns such as the Command pattern and the Memento pattern. After completing modifications, users can choose not to update the target configuration file. Clicking "Apply" loads the updated configuration parameters into the medical device. Alternatively, a "Save" button can be provided, which, upon clicking, writes the data in the memory copy to the target configuration file.

[0144] Step S50, in response to the user's configuration application instruction for the target configuration file, loading the configuration parameters in the updated target configuration file into the operating environment of the medical device;

[0145] In one embodiment of the present invention, the user triggers a configuration application instruction in the configuration management interface. The triggering method may be clicking buttons such as "Apply", "Load", and "Take Effect"; selecting "Apply Configuration" or similar options in the menu; or using shortcut keys. After the medical device receives the configuration application instruction, it starts to execute the configuration loading process. Before loading the configuration, the updated target configuration file is again fully checked for anomalies. This is to ensure that the configuration file is still safe and valid even after the user modifies the configuration, and to avoid abnormal operation of the device due to loading an incorrect configuration. The process and method of anomaly detection are the same as those described above and will not be repeated here. If an anomaly is detected, the loading process is stopped, and an error message is displayed to the user, informing him that there is an abnormal configuration item, and suggesting that the user modify it, while keeping the device running under the previous configuration.

[0146] Before loading a new configuration, the current operating configuration parameters of the medical device are backed up to the memory. The purpose of the backup is to be able to quickly roll back to the previous configuration when loading the new configuration fails or a problem occurs, ensuring the continuous operation of the device. The backup method can be to save the current configuration parameters to a separate backup file or add a new configuration version to the historical configuration list. When loading configuration parameters, according to the parameter configuration items in the updated target configuration file, their values ​​are loaded one by one into the operating environment of the medical device. The loading method depends on the hardware and software architecture of the medical device and may include the following:

[0147] Direct modification of memory variables: If configuration parameters directly correspond to memory variables in the medical device runtime, new values ​​can be written directly to these variables.

[0148] Calling API interfaces: If the medical device provides API interfaces for configuring parameter settings, new parameter values ​​can be set by calling these interfaces.

[0149] Modify registers: If configuration parameters are associated with hardware registers, the parameter values ​​can be modified by reading and writing registers.

[0150] Send control commands: If configuration parameters need to be set through specific control commands, control commands can be sent to related hardware modules.

[0151] Updating runtime data structures: If configuration parameters are stored in specific runtime data structures (such as configuration tables), these data structures can be updated.

[0152] The loading process should ensure atomicity or transactionality, that is, either all parameters are loaded successfully or none are loaded, to avoid inconsistent device status caused by partial loading.

[0153] At the same time, during the process of loading configuration parameters, it is necessary to closely monitor the loading status and perform necessary error handling. Monitoring includes: whether each parameter configuration item is loaded successfully, whether hardware or software errors occur during the loading process, and whether the loading time has timed out. Error handling includes: if a parameter configuration item fails to load, the loading process is immediately stopped and the previous configuration is rolled back (using a backup configuration or maintaining the original configuration). If a hardware or software error occurs during the loading process, the error information is recorded and an attempt is made to reload or roll back the configuration. If the loading time exceeds the preset timeout, the loading is interrupted and the configuration is rolled back. At this time, the user is prompted with the cause of the loading failure and handling suggestions through the display, indicator lights, sound, etc.

[0154] After all parameter configuration items are loaded, key parameters can be re-verified to ensure that the loaded configuration is consistent with the updated target configuration file. Verification can be performed by reading the parameter values ​​of the medical device during operation and comparing them with the values ​​in the target configuration file. Alternatively, specific test procedures or self-test procedures can be used to check whether the device's functions and performance meet expectations. After the configuration is successfully loaded, the new configuration parameters take effect and the medical device operates according to the new configuration. At the same time, the medical device records detailed information for each configuration load, including the load time, the loaded configuration file, the load result (success / failure), the reason for failure, the loaded parameter values, etc., and stores them in a log file to facilitate subsequent troubleshooting and auditing.

[0155] In summary, the medical device configuration management method in the above-mentioned embodiment of the present invention provides a configuration preview interface, so that the current values ​​of all parameter configuration items can be viewed without loading, and adopts a structured display method to facilitate quick search and comparison; at the same time, by automatically performing anomaly detection when parsing the configuration file, various abnormal conditions of the configuration file (missing, out of range, conflict, incompatibility, etc.) can be discovered in time, and medical staff can be informed through highlighting, error prompts, etc., thereby solving the problems of low efficiency of existing parameter configuration selection and inability to timely understand configuration file changes.

[0156] Example 2

[0157] See also Figure 2 , is a schematic diagram of the structure of a medical device configuration management system provided by a second embodiment of the present invention. For ease of explanation, only the portion related to the embodiment of the present invention is shown. The system is applied to a medical device having a display interface. The display interface of the medical device provides a configuration management interface. The configuration management interface includes a configuration selection interface and a configuration preview interface. The system includes:

[0158] A configuration selection interface display module 11 is used to display identification information of multiple configuration files stored in the medical device in the configuration selection interface;

[0159] The configuration preview interface display module 12 is configured to read and parse all parameter configuration items in the target configuration file in response to a user's selection operation instruction for the target configuration file, and display the current values ​​of all parameter configuration items in the target configuration file in a structured manner in the configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device;

[0160] The target configuration file anomaly detection module 13 is used to perform anomaly detection on the target configuration file when parsing the target configuration file, and when an abnormal parameter item is detected, highlight the abnormal parameter item in the configuration preview interface, and replace the abnormal configuration value corresponding to the abnormal parameter item with the default configuration value associated with the abnormal parameter item;

[0161] The parameter configuration item modification module 14 is configured to respond to a modification operation instruction of a parameter configuration item in a target configuration file by a user in the configuration preview interface, receive a parameter configuration value selected by the user to update the target configuration file;

[0162] The configuration file configuration application module 15 is configured to load the configuration parameters in the updated target configuration file into the operating environment of the medical device in response to a configuration application instruction of the target configuration file issued by the user.

[0163] Furthermore, in one embodiment of the present invention, configuring the preview interface display module 12 includes:

[0164] A format recognition unit, configured to read and recognize the format of the target configuration file, wherein the format includes XML format, JSON format, and INI format;

[0165] A parser selection unit, configured to select a corresponding target parser according to the format of the target configuration file;

[0166] The parsing unit is configured to read the contents of the target configuration file using a selected target parser, parse the target configuration file according to the syntax rules of the format of the target configuration file, and extract all parameter configuration items in the target configuration file.

[0167] Furthermore, in one embodiment of the present invention, the target configuration file adopts a segmented structure, and each segment contains at least one parameter configuration item;

[0168] The parsing unit includes:

[0169] a parsing state definition subunit, configured to define a set of parsing states, each of the parsing states corresponding to a specific syntax element in the target configuration file;

[0170] A parsing state determination subunit, for determining the next parsing state based on the current parsing state and the character or line content currently read;

[0171] The first parsing operation subunit is used to perform corresponding parsing operations during the state transition process to gradually complete the parsing of the target configuration file, wherein the parsing operation includes extracting at least one of a paragraph name, a parameter name, and a parameter value.

[0172] Furthermore, in one embodiment of the present invention, the parsing unit includes:

[0173] a paragraph mark determination subunit, configured to determine a start mark and an end mark of a paragraph in the target configuration file according to a grammatical rule of the format of the target configuration file;

[0174] a paragraph identification subunit, configured to identify all paragraphs in the target configuration file based on the start and end tags of the paragraphs;

[0175] The second parsing operation subunit is used to parse and identify each parameter configuration item one by one in each of the paragraphs.

[0176] Furthermore, in one embodiment of the present invention, the parsing unit is configured to:

[0177] When the target configuration file is in XML format, identifying tags, attributes and content based on XML syntax rules, and extracting names and values ​​of parameter configuration items therefrom;

[0178] When the target configuration file is in JSON format, objects, arrays, and key-value pairs are identified based on JSON syntax rules, and the names and values ​​of parameter configuration items are extracted therefrom;

[0179] When the target configuration file is in INI format, based on the INI file syntax rules, the sections, keys and values ​​are identified, and the names and values ​​of the parameter configuration items are extracted therefrom.

[0180] Furthermore, in one embodiment of the present invention, the configuration preview interface display module 12 includes:

[0181] a configuration file reading and parsing unit, configured to read and parse a target configuration file, and convert the data in the target configuration file into a data structure processable by the medical device, wherein the data structure includes an array, a list, a tree structure, or a hash table;

[0182] A user interface element construction unit, configured to construct a user interface element for configuring the preview interface according to the data structure, wherein the user interface element includes at least one of a table, a tree control, a group box, a tab, and a foldable panel;

[0183] The configuration preview interface display unit is used to bind the current values ​​of the parameter configuration items in the data structure with the user interface elements and display the current values ​​of all parameter configuration items on the user interface elements.

[0184] Furthermore, in one embodiment of the present invention, the user interface element construction unit includes:

[0185] The group display area creation subunit is used to create a corresponding group display area according to the group information of the parameter configuration items in the data structure;

[0186] The tree node creation subunit is used to create corresponding tree nodes according to the hierarchical relationship of the parameter configuration items in the data structure;

[0187] The paging display subunit is used to automatically display the parameter configuration items in pages according to the number of parameter configuration items in the data structure and the size of the display area;

[0188] The display control creation subunit is used to create a corresponding display control according to the type of the parameter configuration item in the data structure.

[0189] Furthermore, in one embodiment of the present invention, the user interface element construction unit further includes:

[0190] A display style information acquisition subunit for acquiring display style information of parameter configuration items used in the parameter setting interface of the medical device;

[0191] The display style setting subunit is used to set the display style of the user interface elements in the configuration preview interface according to the acquired display style information.

[0192] Furthermore, in one embodiment of the present invention, configuring the preview interface display unit includes:

[0193] A data binding relationship establishment subunit is used to establish a two-way data binding relationship between each parameter configuration item in the data structure and the corresponding user interface element in the configuration preview interface;

[0194] The user interface element update display subunit is used to automatically update the display of the corresponding user interface element in the configuration preview interface when the current value of the parameter configuration item in the data structure changes;

[0195] The data structure data updating subunit is used to automatically update the current value of the corresponding parameter configuration item in the data structure when the user modifies the value of the parameter configuration item according to the user interface element in the configuration preview interface.

[0196] The medical equipment configuration management system provided in the embodiment of the present invention has the same implementation principle and technical effects as those of the aforementioned method embodiment. For the sake of brief description, for matters not mentioned in the device embodiment, reference can be made to the corresponding content in the aforementioned method embodiment.

[0197] Example 3

[0198] Another aspect of the present invention provides a medical device, see Figure 3 , shown is a medical device in the third embodiment of the present invention, including a memory 20, a processor 10, and a program 30 stored in the memory 20 and executable on the processor. When the processor 10 executes the program 30, the medical device configuration management method as described in the above embodiment is implemented.

[0199] In some embodiments, the processor 10 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or other data processing chip, used to run program codes or process data stored in the memory 20, such as executing access restriction programs.

[0200] The memory 20 includes at least one type of readable storage medium, including flash memory, hard disk, multimedia card, card-type memory (such as SD or DX memory), magnetic memory, magnetic disk, optical disk, etc. In some embodiments, the memory 20 can be an internal storage unit of the medical device, such as the hard disk of the medical device. In other embodiments, the memory 20 can also be an external storage device of the medical device, such as a SmartMedia Card (SMC), Secure Digital (SD) card, or flash memory card equipped with the medical device. Furthermore, the memory 20 can include both an internal storage unit and an external storage device of the medical device. The memory 20 can be used not only to store application software installed in the medical device and various types of data, but also to temporarily store data that has been output or is about to be output.

[0201] It should be pointed out that Figure 3 The structure shown does not constitute a limitation on the medical device. In other embodiments, the medical device may include fewer or more components than shown in the figure, or combine certain components, or arrange the components differently.

[0202] In summary, the medical device in the above-mentioned embodiment of the present invention provides a configuration preview interface, so that the current values ​​of all parameter configuration items can be viewed without loading, and adopts a structured display method to facilitate quick search and comparison; at the same time, by automatically performing anomaly detection when parsing the configuration file, various abnormal conditions of the configuration file (missing, out of range, conflict, incompatibility, etc.) can be discovered in time, and medical staff can be informed through highlighting, error prompts, etc., thereby solving the problems of low efficiency of existing parameter configuration selection and inability to timely understand configuration file changes.

[0203] An embodiment of the present invention further provides a storage medium on which a program is stored. When the program is executed by a processor, the medical device configuration management method as described in the above embodiment is implemented.

[0204] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example for illustration. In actual applications, the above-mentioned functions can be distributed and completed by different functional units or modules as needed, that is, the internal structure of the storage device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the implementation method can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units. In addition, the specific names of the functional units and modules are only for the convenience of distinguishing each other and are not used to limit the scope of protection of this application.

[0205] Those skilled in the art will appreciate that the logic and / or steps represented in the flowcharts or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any storage medium for use by an instruction execution system, apparatus, or device (e.g., a computer-based system, a system including a processor, or other system that can fetch and execute instructions from an instruction execution system, apparatus, or device), or for use in conjunction with such instruction execution system, apparatus, or device. For purposes of this specification, a "storage medium" can be any device that can contain, store, communicate, propagate, or transmit a program for use by an instruction execution system, apparatus, or device, or in conjunction with such instruction execution system, apparatus, or device.

[0206] More specific examples (a non-exhaustive list) of readable storage media include the following: an electrical connection with one or more wires (electronic device), a portable computer disk cartridge (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disk read-only memory (CDROM). In addition, the storage medium may even be paper or other suitable medium on which the program is printed, since the program can be obtained electronically, for example, by optically scanning the paper or other medium, and then editing, deciphering, or processing in another suitable manner as necessary, and then storing it in a memory.

[0207] It should be understood that various components of the present invention may be implemented using hardware, software, firmware, or a combination thereof. In the aforementioned embodiments, multiple steps or methods may be implemented using software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented using hardware, as in another embodiment, any one or a combination of the following technologies known in the art may be used: a discrete logic circuit having logic gate circuits for implementing logic functions on data signals, an application-specific integrated circuit having suitable combinational logic gate circuits, a programmable gate array (PGA), a field-programmable gate array (FPGA), etc.

[0208] Throughout this specification, reference to terms such as "one embodiment," "some embodiments," "examples," "specific examples," or "some examples" means that a specific feature, structure, material, or characteristic described in connection with that embodiment or example is included in at least one embodiment or example of the present invention. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiment or example. Furthermore, the specific features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

[0209] The above-described embodiments merely illustrate several embodiments of the present invention, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art would be able to make various modifications and improvements without departing from the spirit of the present invention, all of which fall within the scope of protection of the present invention. Therefore, the scope of protection of the present invention shall be determined by the appended claims.

Claims

1. A medical device configuration management method, applied to a medical device having a display interface, wherein the display interface of the medical device provides a configuration management interface, the configuration management interface including a configuration selection interface and a configuration preview interface, characterized in that: The method comprises: Displaying identification information of multiple configuration files stored in the medical device in the configuration selection interface; In response to a user's selection operation instruction for a target configuration file, read and parse all parameter configuration items in the target configuration file, and display the current values ​​of all parameter configuration items in the target configuration file in a structured manner in a configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device; When parsing the target configuration file, the target configuration file is detected for anomalies, and when an abnormal parameter item is detected, the abnormal parameter item is highlighted in the configuration preview interface, and the abnormal configuration value corresponding to the abnormal parameter item is replaced with the default configuration value associated with the abnormal parameter item; In response to a modification operation instruction of a parameter configuration item in a target configuration file by a user in a configuration preview interface, receiving a parameter configuration value selected by the user to update the target configuration file; In response to a user's configuration application instruction for the target configuration file, loading configuration parameters in the updated target configuration file into the operating environment of the medical device; The step of displaying the current values ​​of all parameter configuration items in the target configuration file in a structured manner in the configuration preview interface includes: Reading and parsing a target configuration file, and converting data in the target configuration file into a data structure processable by the medical device, wherein the data structure includes an array, a list, a tree structure, or a hash table; Constructing a user interface element for configuring the preview interface according to the data structure, wherein the user interface element includes at least one of a table, a tree control, a group box, a tab, and a foldable panel; Bind the current values ​​of the parameter configuration items in the data structure to the user interface elements, and display the current values ​​of all parameter configuration items on the user interface elements; The step of binding the current value of the parameter configuration item in the data structure to the user interface element includes: Establish a two-way data binding relationship between each parameter configuration item in the data structure and the corresponding user interface element in the configuration preview interface; When the current value of a parameter configuration item in the data structure changes, the display of the corresponding user interface element in the configuration preview interface is automatically updated; When the user modifies the value of a parameter configuration item according to the user interface element in the configuration preview interface, the current value of the corresponding parameter configuration item in the data structure is automatically updated.

2. The medical device configuration management method according to claim 1, characterized in that: The step of reading and parsing all parameter configuration items in the target configuration file includes: Read and identify the format of the target configuration file, wherein the format includes XML format, JSON format and INI format; Select a corresponding target parser according to the format of the target configuration file; The target configuration file is read using the selected target parser, and parsed according to the grammatical rules of the format of the target configuration file to extract all parameter configuration items in the target configuration file.

3. The medical device configuration management method according to claim 2, characterized in that: The target configuration file adopts a segmented structure, and each segment contains at least one parameter configuration item; The step of parsing according to the grammatical rules of the format of the target configuration file includes: defining a set of parsing states, each of the parsing states corresponding to a specific syntax element in the target configuration file; Determine the next parsing state based on the current parsing state and the currently read character or line content; During the state transition process, corresponding parsing operations are performed to gradually complete the parsing of the target configuration file, wherein the parsing operations include extracting at least one of a paragraph name, a parameter name, and a parameter value.

4. The medical device configuration management method according to claim 3, characterized in that: The step of parsing according to the grammatical rules of the format of the target configuration file includes: Determining the start and end tags of paragraphs in the target configuration file according to the grammatical rules of the format of the target configuration file; Identify all paragraphs in the target configuration file based on the paragraph start and end tags; In each of the above paragraphs, analyze and identify each parameter configuration item one by one.

5. The medical equipment configuration management method according to claim 3, characterized in that: The step of parsing according to the grammatical rules of the format of the target configuration file includes: When the target configuration file is in XML format, identifying tags, attributes and content based on XML syntax rules, and extracting names and values ​​of parameter configuration items therefrom; When the target configuration file is in JSON format, objects, arrays, and key-value pairs are identified based on JSON syntax rules, and the names and values ​​of parameter configuration items are extracted therefrom; When the target configuration file is in INI format, based on the INI file syntax rules, the sections, keys and values ​​are identified, and the names and values ​​of the parameter configuration items are extracted therefrom.

6. The medical equipment configuration management method according to claim 1, characterized in that: The step of constructing user interface elements of the configuration preview interface according to the data structure includes: Create corresponding group display areas according to the group information of the parameter configuration items in the data structure; Create corresponding tree nodes according to the hierarchical relationship of parameter configuration items in the data structure; Automatically display parameter configuration items in pages according to the number of parameter configuration items in the data structure and the size of the display area; Create corresponding display controls based on the type of parameter configuration items in the data structure.

7. The medical device configuration management method according to claim 1, characterized in that: The step of constructing user interface elements of the configuration preview interface according to the data structure further includes: Obtain the display style information of the parameter configuration items used in the parameter setting interface of the medical device; Set the display style of the user interface elements in the configuration preview interface based on the obtained display style information.

8. A medical device configuration management system, applied to a medical device having a display interface, wherein the display interface of the medical device provides a configuration management interface, the configuration management interface including a configuration selection interface and a configuration preview interface, characterized in that: The system comprises: A configuration selection interface display module, used to display identification information of multiple configuration files stored in the medical device in the configuration selection interface; a configuration preview interface display module, configured to read and parse all parameter configuration items in the target configuration file in response to a user's selection operation instruction for the target configuration file, and display the current values ​​of all parameter configuration items in the target configuration file in a structured manner in the configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device; A target configuration file anomaly detection module is used to detect anomalies in the target configuration file when parsing the target configuration file. When an abnormal parameter item is detected, the abnormal parameter item is highlighted in the configuration preview interface, and the abnormal configuration value corresponding to the abnormal parameter item is replaced with the default configuration value associated with the abnormal parameter item. A parameter configuration item modification module is used to respond to a modification operation instruction of a parameter configuration item in a target configuration file by a user in a configuration preview interface, receive a parameter configuration value selected by the user to update the target configuration file; a configuration file configuration application module, configured to load configuration parameters in the updated target configuration file into the operating environment of the medical device in response to a user's configuration application instruction for the target configuration file; The configuration preview interface display module includes: a configuration file reading and parsing unit, configured to read and parse a target configuration file, and convert the data in the target configuration file into a data structure processable by the medical device, wherein the data structure includes an array, a list, a tree structure, or a hash table; A user interface element construction unit, configured to construct a user interface element for configuring the preview interface according to the data structure, wherein the user interface element includes at least one of a table, a tree control, a group box, a tab, and a foldable panel; A configuration preview interface display unit is used to bind the current values ​​of the parameter configuration items in the data structure with the user interface elements and display the current values ​​of all parameter configuration items on the user interface elements; The configuration preview interface display unit includes: A data binding relationship establishment subunit is used to establish a two-way data binding relationship between each parameter configuration item in the data structure and the corresponding user interface element in the configuration preview interface; The user interface element update display subunit is used to automatically update the display of the corresponding user interface element in the configuration preview interface when the current value of the parameter configuration item in the data structure changes; The data structure data updating subunit is used to automatically update the current value of the corresponding parameter configuration item in the data structure when the user modifies the value of the parameter configuration item according to the user interface element in the configuration preview interface.

9. A storage medium storing a program, characterized in that: When the program is executed by a processor, the medical device configuration management method according to any one of claims 1 to 7 is implemented.

10. A medical device, characterized in that: The medical device configuration management method comprises a memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, the medical device configuration management method according to any one of claims 1 to 7 is implemented.

Images