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

Abstract

The invention is suitable for the technical field of medical equipment, and provides a medical equipment configuration management method and system, a storage medium and medical device.The method comprises the steps that in response to a selection operation instruction of a user for a target configuration file, all parameter configuration items in the target configuration file are read and analyzed, displaying the current values of all the parameter configuration items in a configuration preview interface in a structured mode; performing anomaly detection when the target configuration file is analyzed, and highlighting an abnormal parameter item in the configuration preview interface when the abnormal parameter item is detected; receiving a parameter configuration value selected by a user to update the target configuration file in response to a modification operation instruction of the user on the parameter configuration item in the target configuration file; and in response to a configuration application instruction of a user on the target configuration file, loading the updated configuration parameters into the medical equipment. The problems that the existing parameter configuration selection efficiency is low and the change of the configuration file cannot be known in time are solved.

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 precision and complexity of modern medical equipment have been significantly improved, and its functions are highly dependent on diversified parameter configurations. At present, most medical devices (such as monitors, medical equipment, etc.) are equipped with parameter configuration files, allowing users to differentiate multiple parameters such as heart rate, blood oxygen, blood pressure, etc. according to clinical needs. However, the existing technology has the following significant defects in practical applications: First, the visualization and interaction efficiency of configuration parameters are insufficient. The configuration parameters of medical equipment are usually scattered in 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.

[0003] Secondly, there is a lack of a configuration anomaly detection mechanism. In the prior art, when a configuration file is missing or exceeds a limit due to equipment failure, storage error, or human error, the device system is usually automatically replaced with the default configuration, but there is a lack of active prompting for abnormal parameters. Medical staff are unable to promptly learn of configuration anomalies, 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 being set to 120 instead of a reasonable range of 0-100), the system automatically corrects it to the default value, but there is no abnormal mark on the interface, which can easily cause medical staff to misjudge, posing potential medical risks and even causing clinical disputes.

[0004] In addition, the parameter presentation method lacks intuitiveness. The existing configuration management interface mostly uses a text list to display parameter names and values, which is quite different from the graphical layout of the device's actual parameter setting interface. Medical staff need to repeatedly compare the text list with the parameter setting interface, making it difficult to quickly identify whether the key parameter configuration meets clinical needs, increasing the possibility of human misreading.

[0005] Therefore, how to improve the efficiency of parameter configuration selection for medical devices, avoid the risks brought by abnormal configuration, and ensure that medical staff can be informed of changes in configuration files in a timely manner has become an urgent problem to be solved in the current design of medical devices. Solving these problems is of great significance to improving the user experience of medical devices and ensuring the safety of patients. Summary of the invention

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

[0007] 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 a configuration management interface is provided in the display interface of the medical device, wherein the configuration management interface includes a configuration selection interface and a configuration preview interface, and the method includes: 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, all parameter configuration items in the target configuration file are read and parsed, and the current values ​​of all parameter configuration items in the target configuration file are displayed in a structured manner in a configuration preview interface, and the configuration parameters of the target configuration file are not loaded into the operating environment of the medical device; When parsing the target configuration file, anomaly detection is performed on the target configuration file, 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 a 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 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.

[0008] 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: Furthermore, 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; According to the format of the target configuration file, select a corresponding target parser; The target configuration file is read using the selected target parser, and is 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.

[0009] 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 comprises: 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 character or line content currently read; 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.

[0010] Furthermore, the step of parsing according to the grammatical rules of the format of the target configuration file includes: Determine the start tag and the end tag of a paragraph 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 start and end tags of the paragraphs; In each of the above paragraphs, parse and identify each parameter configuration item one by one.

[0011] Furthermore, 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, based on XML syntax rules, tags, attributes and contents are identified, and names and values ​​of parameter configuration items are extracted therefrom; When the target configuration file is in JSON format, objects, arrays, key-value pairs are identified based on JSON syntax rules, and 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, paragraphs, keys and values ​​are identified, and the names and values ​​of parameter configuration items are extracted therefrom.

[0012] 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: Reading and parsing the target configuration file, converting the data in the target configuration file into a data structure that can be processed 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 of a configuration 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 page, 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.

[0013] Furthermore, the step of constructing a user interface element of the configuration preview interface according to the data structure includes: According to the grouping information of the parameter configuration items in the data structure, create a corresponding group display area; Create corresponding tree nodes according to the hierarchical relationship of parameter configuration items in the data structure; 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; Create corresponding display controls according to the type of parameter configuration items in the data structure.

[0014] Furthermore, the step of constructing a user interface element of the configuration preview interface according to the data structure also includes: Obtain display style information of parameter configuration items used in the parameter setting interface of medical equipment; Set the display style of the user interface elements in the configuration preview interface according to the obtained display style information.

[0015] Furthermore, the step of binding the current value of the parameter configuration item in the data structure with 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 value of a parameter configuration item is modified 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.

[0016] Another embodiment of the present invention aims to provide a medical device configuration management system, which is applied to a medical device having a display interface, wherein a configuration management interface is provided in the display interface of the medical device, wherein the configuration management interface includes a configuration selection interface and a configuration preview interface, and the system includes: 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 respond 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 the configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device; The target configuration file anomaly detection module 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, 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, and receive a parameter configuration value selected by the user to update the target configuration file; 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.

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

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

[0019] The medical equipment configuration management method provided in 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 a structured display method is adopted 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 by highlighting, error prompts, etc., thereby solving the problems of low efficiency of existing parameter configuration selection and inability to timely understand changes in the configuration file. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 is a flow chart of a medical device configuration management method in a first embodiment of the present invention; Figure 2 is a structural diagram of a medical device configuration management system in a second embodiment of the present invention; Figure 3 is a structural diagram of a medical device in a third embodiment of the present invention; The following specific implementations will further illustrate the present invention in conjunction with the above-mentioned drawings. DETAILED DESCRIPTION

[0021] In order to facilitate the understanding of the present invention, the present invention will be described more fully below with reference to the relevant drawings. Several embodiments of the present invention are given in the drawings. However, the present invention can be implemented in many different forms and is not limited to the embodiments described herein. On the contrary, the purpose of providing these embodiments is to make the disclosure of the present invention more thorough and comprehensive.

[0022] 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 a central element. When an element is considered to be "connected to" another element, it may be directly connected to the other element or there may be a central element at the same time. The terms "vertical", "horizontal", "left", "right" and similar expressions used herein are for illustrative purposes only.

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

[0024] Embodiment 1 See also Figure 1 , which shows a medical device configuration management method in a first embodiment of the present invention. For the sake of convenience, only the part related to the embodiment of the present invention is shown. The medical device configuration management method provided by the embodiment of the present invention includes: Step S10, displaying identification information of multiple configuration files stored in the medical device in the configuration selection interface; In one embodiment of the present invention, the medical device configuration management method is applied to a medical device with a display interface, and the medical device includes a processor, a memory, a display screen, an input device (such as a touch screen, a button, a knob, etc.) and related hardware and software modules. Specifically, a configuration management interface is provided in the display interface of the medical device, and the configuration management interface includes a configuration selection interface and a configuration preview interface.

[0025] Among them, the configuration selection interface displays the identification information (such as file name, configuration name, version number, etc.) of all configuration files stored in the memory of the medical device in the form of a list, table or icon. At this time, the user can select a target configuration file for preview or application through an input device such as a touch screen, button or knob. The configuration preview interface is used to display the current values ​​of all parameter configuration items in the target configuration file in a structured manner without loading the target configuration file. Specifically, multiple configuration files are stored in the memory of the medical device, and each configuration file contains a set of parameter configuration items and their values. The configuration file is stored in XML, JSON, INI, CSV or a custom binary format. The configuration file may contain metadata, such as creation time, modification time, version number, author, applicable device model, applicable patient type, clinical application scenario, etc. When the user selects a target configuration file in the configuration selection interface, the processor of the medical device reads the content of the configuration file from the memory. The reading process includes operations such as file opening, data reading, and file closing.

[0026] 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, and not loading the configuration parameters of the target configuration file into the operating environment of the medical device; 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: Read and identify the target configuration file format, including XML format, JSON format and INI format; Select the corresponding target parser according to the format of the target configuration file; Use the selected target parser to read the contents of the target configuration file, parse it according to the grammatical rules of the format of the target configuration file, and extract all parameter configuration items in the target configuration file.

[0027] 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: Define a set of parsing states, each of which corresponds to a specific syntax element in the target configuration file; Determine the next parsing state based on the current parsing state and the character or line content currently read; During the state transition process, corresponding parsing operations are performed to gradually complete the parsing of the target configuration file, and the parsing operations include extracting at least one of a paragraph name, a parameter name, and a parameter value.

[0028] Further, the steps of parsing according to the syntax rules of the target configuration file format include: Determine the start tag and end tag of paragraphs in the target configuration file according to the syntax rules of the target configuration file format; Identify all paragraphs in the target configuration file according to the start tag and end tag of the paragraphs; Within each paragraph, parse and identify each parameter configuration item one by one.

[0029] Further, the steps of parsing according to the syntax rules of the target configuration file format include: When the target configuration file is in XML format, based on XML syntax rules, identify tags, attributes, and content, and extract the names and values of parameter configuration items therefrom; When the target configuration file is in JSON format, based on JSON syntax rules, identify objects, arrays, key-value pairs, and extract the names and values of parameter configuration items therefrom; When the target configuration file is in INI format, based on INI file syntax rules, identify paragraphs, keys, and values, and extract the names and values of parameter configuration items therefrom.

[0030] Specifically, when the medical device obtains a user's selection operation instruction for the target configuration file, read the first few bytes (or the first few lines) of the target configuration file, identify the feature information of the file format therefrom, and determine the file format according to 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 is met, 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 use in subsequent steps.

[0031] Further, 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.

[0032] Further, create a data structure for storing the parsing results (such as a parameter list, a parameter dictionary, or a segment dictionary, etc.) to store the information of all the parsed parameter configuration items. Further, initialize the state of the parser (such as "start", "read paragraph name", "read key name", etc.); then initialize the variables such as the current paragraph and the current parameter configuration item; then read the paragraph identifier of the target configuration file according to the format characteristics of the target configuration file and the grammatical rules of the format of the target configuration file, specifically the start tag and the end tag; then identify the corresponding paragraph according to the paragraph identifier; then, in the paragraph content, read and parse each parameter configuration item one by one, specifically, such as identifying the name and value of the parameter configuration item; if the target configuration file format supports it, other attributes such as the data type, unit, value range, default value, etc. of the parameter configuration item can also be identified. Further, according to the format of the target configuration file and the characteristics of the parser, read and parse the content in the target configuration file 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 from them; 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 from them; when the target configuration file is in INI format, the parser identifies paragraphs, keys, and values ​​based on INI file syntax rules, and extracts the names and values ​​of parameter configuration items from them. Specifically, the parser maintains a state variable internally to indicate the current parsing state (such as "waiting for paragraph start", "reading paragraph name", "reading key name", "reading key value", etc.). The parser decides the next operation to be performed (such as extracting paragraph name, extracting key name, extracting key value, state transition, etc.) based on the current state and the currently read characters or line content. The parser switches between different states according to predefined grammatical rules (such as XML tag rules, JSON key-value pair rules, INI paragraph and key-value rules). During the state transition process, the corresponding parsing operation is performed, including extracting paragraph names, extracting parameter names, extracting parameters, extracting other attributes of parameters (such as data types, units, ranges, etc., if defined in the configuration file), and finally storing the extracted parameter information (parameter configuration items) in the data structure. At this time, the reading and parsing steps are repeated section by section until all paragraphs and parameter configuration items in the configuration file are parsed, and the parsing of the entire target configuration file is completed. After the parsing is completed, the parser returns the data structure storing the parsing results. Further, during the parsing process, if the configuration file format does not meet the specifications (such as XML tag mismatch, JSON lacks a colon, INI lacks an equal sign, etc.), and the configuration file contains invalid characters or data types, the parsing is stopped, error information (such as error type, error location, error cause, etc.) is recorded, and an error prompt is displayed to the user (such as displaying an error message on the configuration preview interface).

[0033] 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 in the "key=value" format, and the parameter sequence number and parameter value are read. Specifically, read one character at a time until "=" is encountered, and the content between these characters is the attribute name. After encountering "=", the parsing state is converted to "ATTR_VALUE (read attribute value)", and then the attribute value is read until the quotation mark (single or double quotation mark) paired with the quotation mark at the beginning of the attribute value is encountered, and the parsing state is converted to "CONTENT"; if the current parsing state is "CONTENT" and the character currently read is "<", the next character is further judged: if the next character is " / ", the parsing state is converted to "waiting for closing tag"; otherwise, the parsing state is converted to "TAG_NAME", and nested tags are processed recursively; 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 they match, the parsing of the current tag is completed; repeat the above steps until all characters in the target configuration file are read. At this time, the name of each tag is used as the paragraph name (or the paragraph name is determined according to the predefined rules); the attribute name and attribute value in the tag, or the text content of the tag, are used as the name and value of the parameter configuration item.

[0034] 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 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 "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 in the format of "key:value", 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 to read the next key-value pair. If "}" is encountered, it means that the current object has been parsed. If the current parsing state is "IN_ARRAY", it means that an array has been parsed. At this time, the array elements are parsed and the parsing state is converted to "EXPECT_VALUE (expected read value)"; if the current parsing state is "EXPECT_COLON" and the character currently read is ":", the parsing state is converted to "EXPECT_VALUE (expected read value)"; if the current parsing state is "EXPECT_VALUE", the type of value (string, number, Boolean value, null, nested object or array) is determined according to the character currently read, and the corresponding parsing is performed; if a comma ", " is encountered, the next array element is read. If "] " is encountered, it means that the current array has been parsed. If a string, number, Boolean value, or null is encountered, its value is read directly. If a nested object or array is encountered, the JSON parsing process is recursively called for parsing. Then repeat the above steps until all characters in the target configuration file are read. At this time, 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 according to the definition of the configuration file, is used as the section name.

[0035] 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 starts 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 is "IN_SECTION" and the line currently read contains "=", the parsing state is converted to "IN_KEY"; if the current parsing state is "IN_KEY", the string on the left of the equal sign is extracted as the key name, and the parsing state is converted to "IN_VALUE"; if the current parsing state is "IN_VALUE", the string on the right of the equal sign (until the end of the line or comment) is extracted as the key value; if a blank line or comment line (such as a line starting with ";") is encountered, it is ignored. Then repeat the above steps until all lines in the target configuration file are read. At this time, each section name is used as a 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.

[0036] After parsing, the information of the parameter configuration item is stored in a data structure inside the medical device, which includes a parameter list or a parameter dictionary or a segment dictionary. The parameter list is a list in which each element is a parameter configuration item object, including the parameter name, value, type, unit, paragraph, etc. The parameter dictionary is a dictionary whose key is the parameter name and whose value is the parameter configuration item object. The segment dictionary is a nested dictionary in which the key of the outer dictionary is the paragraph name and the value is another dictionary (the parameter dictionary under the paragraph).

[0037] 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: Reading and parsing the target configuration file, converting the data in the target configuration file into a data structure that can be processed 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 of a configuration 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 page, 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.

[0038] Specifically, after the medical device parses the read target configuration file, it converts the data therein into a data structure that can be processed by the medical device. The parsing process includes performing syntax analysis on the target configuration file to check whether the target configuration file conforms to the predefined format specification; if the target configuration file passes the syntax analysis, at least one of 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 is extracted; if the target configuration file does not pass 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 the memory, which can be an array, a list, a tree structure, or a hash table, etc.

[0039] Furthermore, according to the parsed data structure, the user interface elements of the configuration preview interface are dynamically constructed. The step of constructing the user interface elements of the configuration preview interface according to the data structure includes: According to the grouping information of the parameter configuration items in the data structure, create a corresponding group display area; Create corresponding tree nodes according to the hierarchical relationship of parameter configuration items in the data structure; 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; Create corresponding display controls according to the type of parameter configuration items in the data structure.

[0040] Specifically, according to the grouping information of the parameter configuration items, create corresponding group boxes (GroupBox), tab pages (TabPage), foldable panels (CollapsiblePanel), etc., and display the parameter configuration items in each group display area. If there is a hierarchical relationship between the parameter configuration items, create a tree control (TreeView), each node represents a parameter category or a parameter configuration item. If there are a large number of parameter configuration items, they are automatically displayed in pages according to the size of the display area, and page turning controls (buttons, page numbers) are provided. According to the type of parameter configuration items, create corresponding display controls, where the display controls include: a numeric input box for displaying and editing numeric type parameter configuration items; a drop-down list for displaying and editing enumeration type parameter configuration items; a switch control or check box for displaying and editing Boolean type parameter configuration items; a text box for displaying and editing text type parameter configuration items; a date / time selector for displaying and editing date / time type parameter configuration items.

[0041] Furthermore, the step of constructing the user interface elements of the configuration preview interface according to the data structure also includes: Obtain display style information of parameter configuration items used in the parameter setting interface of medical equipment; According to the acquired display style information, the display style of the user interface element in the configuration preview interface is set, wherein the display style includes at least one of font, font size, color, background color, alignment, bold, and italic.

[0042] 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 keep the styles of the two consistent. The construction process uses code to dynamically generate user interface elements, or generates user interface elements by reading user interface description files (such as XML).

[0043] Furthermore, the above step of binding the current value of the parameter configuration item in the data structure with 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 value of a parameter configuration item is modified 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.

[0044] Furthermore, the display order information of the parameter configuration items is stored in the medical device, and when constructing the user interface elements of the configuration preview interface, the display order of each parameter configuration item is determined according to the display order information. At the same time, the display priority of the parameter configuration item can also be obtained; the parameter configuration items with high display priority are preferentially displayed in the configuration preview interface. Further, when the configuration preview interface is initialized, the display state saved when the configuration preview interface was closed last time is automatically loaded, and the display state includes: the folding / expanding state of the group; the currently displayed page; the expanding / folding state of the tree structure. Among them, it should be pointed out that in the embodiment of the present invention, the current values ​​of all parameter configuration items in the target configuration file are displayed in a structured manner, so that all parameter configuration items can be viewed only in the configuration preview interface, avoiding the configuration parameters of the existing medical device are usually scattered in multiple independent setting interfaces, resulting in insufficient visualization and interaction efficiency of the configuration parameters. And by synchronously setting the display style information of the parameter configuration items used in the parameter setting interface of the medical device to the display style in the configuration preview interface, it is easy for medical staff to get started and reduce the complexity of the configuration layout. Further, during the entire preview process, the medical device will not load any parameter value in the target configuration file into the operating environment of the medical device. This means that the preview operation will 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, rather than the parameter values ​​currently used by the medical device, which avoids the problem of frequent loading of different parameter configuration files and switching multiple interfaces for manual verification due to the low efficiency of existing parameter configuration selection.

[0045] Step S30, when parsing the target configuration file, performing anomaly detection on the target configuration file, and when an abnormal parameter item is detected, highlighting the abnormal parameter item in the configuration preview interface, and replacing the abnormal configuration value corresponding to the abnormal parameter item with a default configuration value associated with the abnormal parameter item; In one embodiment of the present invention, the step of performing anomaly detection on the target configuration file includes: Pre-storing one or more anomaly detection rule bases in the medical device, each rule base containing one or more sets of rules for detecting a specific type of anomaly; When parsing the target configuration file, 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 there are any anomalies; 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.

[0046] The anomaly detection rules include at least one of the following: Parameter value range rules specifically limit the value range of each parameter configuration item, including the minimum and maximum values. If the value of a parameter configuration item exceeds the value range, it is judged as abnormal; The parameter relationship rules specifically define the logical relationship between different parameter configuration items, which specifically include mutually exclusive relationships, dependent relationships, and inclusion relationships. The mutually exclusive relationship means that two or more parameter configuration items cannot be set to specific values ​​at the same time; the dependent relationship means that the value of one parameter configuration item depends on the value of another parameter configuration item; the 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 the parameter configuration items does not meet the parameter relationship rules, it is determined to be abnormal; Parameter type rule: specifically defines the data type of each parameter configuration item, including numeric type, enumeration type, Boolean type, text type, and date / time type. If the data type of the value of the parameter configuration item does not conform to the parameter type rule, it is considered abnormal. 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 abnormal. 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 judged as abnormal; Custom rules: Allow users to customize anomaly detection rules according to specific needs, where custom rules are defined using scripting language or graphical interface.

[0047] 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, and the step of determining whether there is an anomaly includes: reading all rules in an anomaly detection rule base, the rule base being stored in the medical device in a structured data format; 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; 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; According to the definition of the target rule, calculate or judge whether the current parameter configuration item meets the requirements of the target rule; If the requirements of the target rule are not met, it is determined that the current parameter configuration item is abnormal, and the abnormal information is recorded, wherein the abnormal information includes at least one of the name of the abnormal parameter configuration item, the abnormal type, the violated rule, the current value, and the recommended value; If the requirements of the target rule are met, continue to check the next rule until all rules are checked; If all rules are checked and no exceptions are found, the current parameter configuration item is considered normal.

[0048] Specifically, if the rule execution result indicates that the parameter configuration item is abnormal, the abnormal information is stored in the abnormal list. In the configuration preview interface, the display control (such as a text box, a drop-down list, etc.) corresponding to the parameter configuration item is found and highlighted. The highlighting method includes: changing the background color (such as changing to red), changing the font color (such as changing to red) or style (such as bold), adding special icons (such as warning icons, error icons), displaying prompt information (such as displaying error prompt text next to the control, or popping up bubble prompts), and flashing display. At the same time, the default value of the parameter configuration item is found. The default value can come from the default value defined in the abnormal detection rule, the default value table predefined in the medical device, or the default value defined by the parameter configuration item itself. Then replace the current value of the parameter configuration item with the found default value. Update the copy of the configuration file in memory and update the abnormal value to the default value. Update the display of the parameter configuration item on the configuration preview interface so that it is displayed as the default value. If there is a two-way data binding between the configuration preview interface and the parameter configuration item, the interface will be automatically updated after the default value is updated. If there is no two-way data binding, the display of the interface control needs to be manually updated. Then continue to traverse other rules in the rule base until all rules are checked. After all parameter configuration items are checked, the exception information can be summarized and displayed in specific areas of the configuration preview interface (such as the top status bar, sidebar) The total number of exceptions, the distribution of exception types, and other information. A "show only exception items" filtering function can be provided to facilitate users to quickly view all abnormal configurations.

[0049] Step S40, 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 one embodiment of the present invention, after the configuration preview interface is loaded, the medical device will continue to monitor the user's operations on the interface, especially the interactive operations on the parameter configuration item display area. The monitored operations include but are not limited to: mouse clicks, keyboard inputs, touch screen gestures (such as clicks, slides), knob rotations, etc.

[0050] 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, switching 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 type of control. The identification process can be achieved in the following ways: Control association: When each parameter configuration item display control (such as a text box or drop-down list) is created, it is associated with the corresponding parameter configuration item data (such as through the control's ID, label, or custom properties).

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

[0052] Coordinate calculation: For touch screen or mouse operation, you can calculate which parameter configuration item's display area the coordinate is in based on the coordinate triggered by the event.

[0053] Among them, after identifying the target parameter configuration item, the medical device will switch the display control of the parameter configuration item to the edit mode. Different control types have different forms of editing mode. The value input box is a text box where the cursor enters the text box, allowing the user to enter a new value through the keyboard, or adjust the value by clicking the fine-tuning button (plus / minus), or adjusting the value by sliding the slider; the drop-down list is to expand the drop-down list to display all optional values, allowing the user to select a new option by clicking; the switch control is to allow the user to switch the state of the switch (on / off) by clicking; the check box is to allow the user to check or uncheck the check box by clicking; the text box is a text box where the cursor enters the text box, allowing the user to enter or edit text through the keyboard; the pop-up box / sidebar is a special editing dialog box or sidebar that pops up, which contains more detailed parameter information and editing controls, allowing the user to make more detailed modifications. In edit mode, the medical device will continue to monitor the user's input operations and capture the new parameter values ​​entered by the user in real time. Different control types receive input in different ways. Numeric input boxes receive numbers, decimal points, negative signs and other characters input from the keyboard, or receive adjustment events of fine-tuning buttons and sliders; drop-down lists receive user selection events for options in the drop-down list; switch controls / check boxes receive user click events and switch the state of the control based on the click events; and text boxes receive text characters input from the keyboard.

[0054] After receiving the new parameter value input by the user, the medical device can immediately perform input verification to ensure the legitimacy of the new value. The verification types include: type verification, checking whether the new value conforms to the data type of the parameter configuration item (such as numeric value, string, Boolean value, etc.); range verification, checking whether the new value is within the allowable range of the parameter configuration item (such as minimum value, maximum value); format verification, checking whether the new value conforms to the predefined format requirements (such as date format, time format, email format, etc.); and association verification, checking whether the new value conflicts with the values ​​of other parameter configuration items (such as mutually exclusive relationships, dependencies). If the verification fails, the medical device can refuse to accept the new value and keep the original value of the parameter configuration item unchanged; or display an error prompt message to the user (such as displaying error prompt text next to the control, popping up a bubble prompt, changing the border color of the control, etc.); or automatically correct the new value to the closest legal value. If the new parameter value entered by the user passes the verification, the medical device will update the new value to the memory copy of the target configuration file. It should be pointed out that at this time, only the data structure in the memory (such as arrays, lists, tree structures, etc.) is modified, rather than directly modifying the configuration file on the 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 the memory copy is updated. If there is no two-way data binding, you need to manually update the display of the interface control to display the new parameter value.

[0055] 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 the editing of other parameter configuration items; the editing mode ends at this time, and the control returns to the normal display state.

[0056] It should be pointed out that medical devices can provide a batch modification function, allowing users to select multiple parameters at one time and then perform unified modification operations. Medical devices can provide Undo and Redo functions, allowing users to undo the most recent one or more modification operations, or redo the undone modification operations. The Undo / Redo function can be implemented through design patterns such as command mode and memo mode. After the modification is completed, you can choose not to update the target configuration file. When you click "Apply", the updated configuration parameters are loaded into the medical device. Or provide a "Save" button, and after clicking the Save button, the data in the memory copy is written to the target configuration file.

[0057] 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; 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", "Effective", etc.; 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 subjected to a comprehensive abnormality check. This is to ensure that the configuration file is still safe and valid even after the user modifies the configuration, and to avoid abnormal device operation caused by loading an incorrect configuration. The process and method of abnormality detection are the same as those described above and will not be repeated here. If an abnormality is detected, the loading process is stopped, and an error prompt 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.

[0058] 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 quickly roll back to the previous configuration when loading a new configuration fails or a problem occurs, so as to ensure the continuous operation of the device. The backup method can be to save the current configuration parameters to a separate backup file or to 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: Direct modification of memory variables: If the configuration parameters correspond directly to the memory variables of the medical device runtime, new values ​​can be written directly to these variables.

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

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

[0061] Send control commands: If the configuration parameters need to be set through specific control commands, you can send control commands to the relevant hardware modules.

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

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

[0064] 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. The monitoring content includes: whether the loading of each parameter configuration item is successful, whether hardware or software errors occur during the loading process, and whether the loading time has timed out. The error handling includes: if a parameter configuration item fails to load, the loading process is stopped immediately and rolled back to the previous configuration (using the backup configuration or keeping 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 screen, indicator light, sound, etc.

[0065] After all parameter configuration items are loaded, the key parameters can be verified again to ensure that the loaded configuration is consistent with the updated target configuration file. The verification method can be: reading the parameter value of the medical device during operation and comparing it with the value in the target configuration file. Or through a specific test program or self-test program, check whether the function and performance of the device meet expectations. After the configuration is loaded successfully, the new configuration parameters take effect and the medical device runs according to the new configuration. At the same time, the medical device records the detailed information of each configuration loading, including the loading time, the loaded configuration file, the loading result (success / failure), the reason for failure, the loaded parameter value, etc., and stores it in the log file to facilitate subsequent troubleshooting and auditing.

[0066] 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 a structured display method is adopted 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 (missing, out of range, conflict, incompatibility, etc.) can be discovered in time, and the medical staff can be informed by highlighting, error prompts, etc., which solves the problems of low efficiency of existing parameter configuration selection and inability to timely understand changes in the configuration file.

[0067] Embodiment 2 See also Figure 2 , is a schematic diagram of the structure of a medical device configuration management system provided by the second embodiment of the present invention. For the convenience of explanation, only the part 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: A configuration selection interface display module 11, used to display identification information of multiple configuration files stored in the medical device in the configuration selection interface; The configuration preview interface display module 12 is used to respond to the user's selection operation instruction for the 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 the configuration preview interface, and does not load the configuration parameters of the target configuration file into the operating environment of the medical device; 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; The parameter configuration item modification module 14 is used to respond to the modification operation instruction of the user on the parameter configuration item in the target configuration file in the configuration preview interface, and receive the parameter configuration value selected by the user to update the target configuration file; The configuration file configuration application module 15 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.

[0068] Furthermore, in one embodiment of the present invention, configuring the preview interface display module 12 includes: A format identification unit, used for reading and identifying the format of the target configuration file, wherein the format includes XML format, JSON format and INI format; A parser selection unit, configured to select a corresponding target parser according to the format of the target configuration file; The parsing unit is used to read the content of the target configuration file using the selected target parser, and parse it according to the grammatical rules of the format of the target configuration file to extract all parameter configuration items in the target configuration file.

[0069] Further, 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; The parsing unit comprises: A parsing state definition subunit, used to define a set of parsing states, each of which corresponds to a specific syntax element in the target configuration file; A parsing state determination subunit, used to determine the next parsing state according to the current parsing state and the character or line content currently read; The first parsing operation subunit is used to perform corresponding parsing operations during the state conversion 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.

[0070] Furthermore, in one embodiment of the present invention, the parsing unit includes: A paragraph mark determination subunit, used to determine the start mark and the end mark of a paragraph in the target configuration file according to the grammatical rules of the format of the target configuration file; A paragraph identification subunit, for identifying all paragraphs in the target configuration file according to the start tag and the end tag of the paragraph; The second parsing operation subunit is used to parse and identify each parameter configuration item one by one in each of the paragraphs.

[0071] Furthermore, in one embodiment of the present invention, the parsing unit is used to: When the target configuration file is in XML format, based on XML syntax rules, tags, attributes and contents are identified, and names and values ​​of parameter configuration items are extracted therefrom; When the target configuration file is in JSON format, based on JSON syntax rules, objects, arrays, key-value pairs are identified, and 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, paragraphs, keys and values ​​are identified, and the names and values ​​of parameter configuration items are extracted therefrom.

[0072] Furthermore, in one embodiment of the present invention, the configuration preview interface display module 12 includes: A configuration file reading and parsing unit, used to read and parse the target configuration file, and convert the data in the target configuration file into a data structure that can be processed 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, used to construct a user interface element of the configuration 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 page, and a foldable panel; The configuration preview interface display unit is used to bind the current value of the parameter configuration item in the data structure with the user interface element, and display the current value of all parameter configuration items on the user interface element.

[0073] Furthermore, in one embodiment of the present invention, the user interface element construction unit includes: 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; 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; A paging display subunit, used for automatically displaying parameter configuration items in pages according to the number of parameter configuration items in the data structure and the size of the display area; 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.

[0074] Furthermore, in one embodiment of the present invention, the user interface element construction unit further includes: A display style information acquisition subunit, used to obtain display style information of parameter configuration items used in the parameter setting interface of the medical device; 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.

[0075] Further, in one embodiment of the present invention, configuring the 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.

[0076] 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 may be made to the corresponding contents in the aforementioned method embodiment.

[0077] Embodiment 3 Another aspect of the present invention also 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 in the above embodiment is implemented.

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

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

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

[0081] 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 a structured display method is adopted 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 (missing, out of range, conflict, incompatibility, etc.) can be discovered in time, and the medical staff can be informed by highlighting, error prompts, etc., which solves the problems of low efficiency of existing parameter configuration selection and inability to timely understand changes in the configuration file.

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

[0083] 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 assigned to 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 a processing unit, or each unit can exist physically separately, 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.

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

[0085] More specific examples (non-exhaustive list) of readable storage media include the following: an electrical connection with one or more wirings (electronic device), a portable computer disk case (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 a paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium, followed by editing, deciphering or, if necessary, processing in another suitable manner, and then stored in a memory.

[0086] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or a combination thereof: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0087] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0088] The above-described embodiments only express several implementation methods of the present invention, and the description thereof is relatively specific and detailed, but it cannot be understood as limiting the scope of the present invention. It should be pointed out that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present invention, and these all belong to the protection scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the attached 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, wherein the configuration management interface includes a configuration selection interface and a configuration preview interface, wherein: 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, all parameter configuration items in the target configuration file are read and parsed, and the current values ​​of all parameter configuration items in the target configuration file are displayed in a structured manner in a configuration preview interface, and the configuration parameters of the target configuration file are not loaded into the operating environment of the medical device; When parsing the target configuration file, anomaly detection is performed on the target configuration file, 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 a 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 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.

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; According to the format of the target configuration file, select a corresponding target parser; The target configuration file is read using the selected target parser, and is 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 comprises: 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 character or line content currently read; 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 comprises: Determine the start tag and the end tag of a paragraph 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 start and end tags of the paragraphs; In each of the above paragraphs, parse and identify each parameter configuration item one by one.

5. 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 comprises: When the target configuration file is in XML format, based on XML syntax rules, tags, attributes and contents are identified, and names and values ​​of parameter configuration items are extracted therefrom; When the target configuration file is in JSON format, objects, arrays, key-value pairs are identified based on JSON syntax rules, and 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, paragraphs, keys and values ​​are identified, and the names and values ​​of parameter configuration items are extracted therefrom.

6. The medical device configuration management method according to claim 1, characterized in that: 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 the target configuration file, converting the data in the target configuration file into a data structure that can be processed 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 of a configuration 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 page, 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.

7. The medical device configuration management method according to claim 6, characterized in that: The step of constructing a user interface element of the configuration preview interface according to the data structure includes: According to the grouping information of the parameter configuration items in the data structure, create a corresponding group display area; Create corresponding tree nodes according to the hierarchical relationship of parameter configuration items in the data structure; 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; Create corresponding display controls according to the type of parameter configuration items in the data structure.

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

9. The medical device configuration management method according to claim 6, characterized in that: The step of binding the current value of the parameter configuration item in the data structure with the user interface element comprises: 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 value of a parameter configuration item is modified 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.

10. 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, wherein the configuration management interface includes a configuration selection interface and a configuration preview interface, wherein: 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 respond 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 the configuration preview interface, without loading the configuration parameters of the target configuration file into the operating environment of the medical device; The target configuration file anomaly detection module 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, 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, for responding 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; 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.

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

12. A medical device, characterized in that: The medical device 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 as described in any one of claims 1 to 9 is implemented.

Images