A method and system for creating a database for a medical system

Abstract

This specification provides a method and system for creating a database for a medical system. The method includes: obtaining a DICOM data structure, the DICOM data structure including at least one data field related to medicine; determining a storage structure corresponding to the DICOM data structure based on input information, the storage structure being used to generate a database instance related to the medical system.

Description

Technical Field

[0001] This manual relates to the medical field, and in particular to a method and system for creating a database for a medical system. Background Technology

[0002] Medical systems such as ultrasound systems and Picture Archiving and Communication Systems (PACS) need to store large amounts of medical imaging data and other medical diagnostic data. This data is typically stored in the Digital Imaging and Communications in Medicine (DICOM) standard format. However, DICOM data is too large, and most of the data is structured with a uniform format. Manually entering each data item one by one during database design and then creating corresponding fields, tables, and views based on the entered data is inefficient and error-prone.

[0003] Therefore, it is desirable to provide a method and system for automatically creating databases based on the DICOM standard. Summary of the Invention

[0004] One embodiment of this specification provides a method for creating a database for a medical system. The method includes: obtaining a DICOM data structure, the DICOM data structure including at least one data field related to medicine; and determining a storage structure corresponding to the DICOM data structure based on input information, the storage structure being used to generate a database instance related to the medical system.

[0005] In some embodiments, the DICOM data structure includes a value representation; the storage structure includes a data type and / or data constraints, and determining the storage structure corresponding to the DICOM data structure based on the input information includes: determining the data type and / or data constraints corresponding to the storage structure based on the value representation corresponding to the input information.

[0006] In some embodiments, the input information includes the relationship between data fields and data tables, and the relationship between data tables; determining the storage structure corresponding to the DICOM data structure based on the input information includes: determining the relationship between data fields and data tables corresponding to the storage structure, and the relationship between data tables, based on the input information.

[0007] In some embodiments, the method further includes: establishing a corresponding view based on the relationship between the data field and the data table, and the relationship between the data tables.

[0008] In some embodiments, the method further includes generating a structured query language based on the storage structure.

[0009] In some embodiments, the method further includes: automatically generating program code for defining corresponding data objects based on the storage structure.

[0010] In some embodiments, the method further includes: obtaining an updated DICOM data structure; and updating the database based on the updated DICOM data structure.

[0011] Another aspect of this specification provides a database creation system for a medical system. The system includes: an acquisition module for acquiring a DICOM data structure, the DICOM data structure including at least one data field related to medicine; and a creation module for determining a storage structure corresponding to the DICOM data structure based on input information, the storage structure being used to generate a database instance of the medical system.

[0012] Another aspect of this specification provides a computer device including a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor, when executing the computer program, implements the database creation method as described above.

[0013] Another aspect of this specification provides a computer-readable storage medium that stores computer instructions, which, when read by a computer, execute the database creation method for a medical system as described above.

[0014] This specification relates to a database creation method, system, and storage medium for a medical system. Based on the DICOM data structure, it can automatically create and maintain a database according to user needs and automatically generate corresponding program code, reducing user workload and improving accuracy and compilation efficiency. Attached Figure Description

[0015] This specification will be further described by way of exemplary embodiments, which will be described in detail with reference to the accompanying drawings. These embodiments are not limiting; in these embodiments, the same reference numerals denote the same structures, wherein:

[0016] Figure 1 This is a schematic diagram illustrating an application scenario of a database creation system for a medical system, based on some embodiments of this specification.

[0017] Figure 2 This is an exemplary block diagram of a database creation system for a medical system, as shown in some embodiments of this specification.

[0018] Figure 3 This is an exemplary flowchart of a database creation method for a medical system according to some embodiments of this specification;

[0019] Figure 4 These are schematic diagrams illustrating exemplary DICOM data structures according to some embodiments of this specification;

[0020] Figure 5 This is a schematic diagram illustrating exemplary value representations according to some embodiments of this specification;

[0021] Figure 6 This is a schematic diagram of an exemplary mapping structure visualization window according to some embodiments of this specification;

[0022] Figure 7 This is an exemplary flowchart of a database creation method for a medical system according to other embodiments of this specification;

[0023] Figure 8 This is an exemplary flowchart of a database update method according to some embodiments of this specification;

[0024] Figure 9 These are schematic diagrams illustrating exemplary data tables and view information according to some embodiments of this specification;

[0025] Figure 10 This is an exemplary flowchart of a method for automatically generating program code definitions for corresponding data objects, as shown in some embodiments of this specification. Detailed Implementation

[0026] To more clearly illustrate the technical solutions of the embodiments in this specification, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some examples or embodiments of this specification. For those skilled in the art, these drawings can be applied to other similar scenarios without creative effort. Unless obvious from the context or otherwise specified, the same reference numerals in the drawings represent the same structures or operations.

[0027] It should be understood that the terms “system,” “device,” “unit,” and / or “module” used herein are one way to distinguish different components, elements, parts, sections, or assemblies at different levels. However, if other terms can achieve the same purpose, they may be replaced by other expressions.

[0028] As indicated in this specification and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" do not specifically refer to the singular and may also include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of expressly identified steps and elements, which do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

[0029] Flowcharts are used in this specification to illustrate the operations performed by the system according to embodiments of this specification. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, the steps can be processed in reverse order or simultaneously. Furthermore, other operations can be added to these processes, or one or more steps can be removed from them.

[0030] Figure 1 This is a schematic diagram illustrating an application scenario of a database creation system for a medical system, based on some embodiments of this specification.

[0031] like Figure 1 As shown, in some embodiments, system 100 may include a medical device 110, a network 120, a terminal device 130, a processing device 140, and a storage device 150. Multiple components in system 100 can be interconnected via network 120. For example, medical device 110 and terminal device 130 can be connected or communicate via network 120. As another example, medical device 110 and processing device 140 can be connected or communicate via network 120.

[0032] The medical device 110 can be used to scan an object within a detection area or scanning area to obtain scan data of the object. In some embodiments, the object may include biological and / or non-biological objects. For example, the object may be living or non-living organic and / or inorganic matter.

[0033] In some embodiments, the medical device 110 may be a non-invasive imaging device for disease diagnosis or research purposes. For example, the medical device 110 may include a single-modal scanner and / or a multimodal scanner. A single-modal scanner may include, for example, an ultrasound scanner, an X-ray scanner, a computed tomography (CT) scanner, a magnetic resonance imaging (MRI) scanner, an ultrasound examination device, a positron emission tomography (PET) scanner, an optical coherence tomography (OCT) scanner, an ultrasound (US) scanner, an intravascular ultrasound (IVUS) scanner, a near-infrared spectroscopy (NIRS) scanner, a far-infrared (FIR) scanner, or any combination thereof. A multimodal scanner may include, for example, an X-ray imaging-magnetic resonance imaging (X-MRI) scanner, a positron emission tomography-X-ray imaging (PET-X-ray) scanner, a single-photon emission computed tomography-magnetic resonance imaging (SPECT-MRI) scanner, a positron emission tomography-computed tomography (PET-CT) scanner, a digital subtraction angiography-magnetic resonance imaging (DSA-MRI) scanner, or the like. The scanners described above are for illustrative purposes only and are not intended to limit the scope of this manual.

[0034] Network 120 may include any suitable network capable of facilitating information and / or data exchange within system 100. In some embodiments, at least one component of system 100 (e.g., medical device 110, terminal device 130, processing device 140, storage device 150) may exchange information and / or data with at least one other component of system 100 via network 120. For example, processing device 140 may acquire scan data or scan images of a scanned object from medical device 110 via network 120. Network 120 may include public networks (e.g., the Internet), private networks (e.g., local area networks (LANs)), wired networks, wireless networks (e.g., 802.11 networks, Wi-Fi networks), Frame Relay networks, virtual private networks (VPNs), satellite networks, telephone networks, routers, hubs, switches, fiber optic networks, telecommunications networks, intranets, wireless local area networks (WLANs), metropolitan area networks (MANs), public switched telephone networks (PSTNs), and Bluetooth. TM Network, ZigBee TM Networks, near field communication (NFC) networks, and any combination thereof. In some embodiments, network 120 may include at least one network access point. For example, network 120 may include wired and / or wireless network access points, such as base stations and / or internet exchange points, through which at least one component of system 100 may connect to network 120 to exchange data and / or information.

[0035] Terminal device 130 can communicate and / or connect to medical device 110, processing device 140, and / or storage device 150. For example, a user can interact with medical device 110 through terminal device 130 to control one or more components of medical device 110. In some embodiments, terminal device 130 may include mobile device 131, tablet computer 132, laptop computer 133, etc., or any combination thereof. For example, mobile device 131 may include a mobile control handle, personal digital assistant (PDA), smartphone, etc., or any combination thereof.

[0036] Processing device 140 can process data and / or information obtained from medical device 110, at least one terminal device 130, storage device 150, or other components of system 100. For example, processing device 140 can acquire and analyze computed tomography images, PET scan images, etc., from medical device 110. Alternatively, processing device 140 can acquire scan data such as scan images and scan times from medical device 110 and store them as a DICOM data structure. In some embodiments, processing device 140 can be a single server or a group of servers. The server group can be centralized or distributed. In some embodiments, processing device 140 can be local or remote. For example, processing device 140 can access information and / or data from medical device 110, at least one terminal device 130, and / or storage device 150 via network 120. Alternatively, processing device 140 can be directly connected to medical device 110, at least one terminal device 130, and / or storage device 150 to access information and / or data. In some embodiments, processing device 140 can be implemented on a cloud platform. For example, cloud platforms can include private clouds, public clouds, hybrid clouds, community clouds, distributed clouds, inter-cloud clouds, multi-clouds, or any combination thereof.

[0037] In some embodiments, the processing device 140 may include one or more processors (e.g., a single-chip processor or a multi-chip processor). By way of example only, the processing device 140 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), an application-specific instruction set processor (ASIP), an image processing unit (GPU), a physical processing unit (PPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), a programmable logic device (PLD), a controller, a microcontroller unit, a reduced instruction set computer (RISC), a microprocessor, or any combination thereof. In some embodiments, the processing device 140 may be part of a medical device 110 or a terminal device 130. For example, the processing device 140 may be integrated within the medical device 110 to determine the target location of the scanned object in the scanned area, abnormal points in the scanned image, and recommended scanning protocols, etc.

[0038] Storage device 150 may store data, instructions, and / or any other information. For example, storage device 150 may store scanned images acquired by medical device 110 and related information. In some embodiments, storage device 150 may store data acquired from medical device 110, at least one terminal device 130, and / or processing device 140, such as scanned images, scan time, patient information, etc. In some embodiments, storage device 150 may store data and / or instructions used by processing device 140 to perform or use in order to accomplish the exemplary methods described herein. In some embodiments, storage device 150 may include mass storage, removable storage, volatile read-write storage, read-only storage (ROM), etc., or any combination thereof. In some embodiments, storage device 150 may be implemented on a cloud platform.

[0039] In some embodiments, storage device 150 may be connected to network 120 to communicate with at least one other component of system 100 (e.g., medical device 110, at least one terminal device 130, processing device 140). At least one component of system 100 may access data stored in storage device 150 (e.g., scanned images of scanned objects, information data, etc.) via network 120. In some embodiments, storage device 150 may be part of processing device 140.

[0040] It should be noted that the above description is provided for illustrative purposes only and is not intended to limit the scope of this specification. Various changes and modifications can be made by those skilled in the art based on the content of this specification. Features, structures, methods, and other features of the exemplary embodiments described herein can be combined in various ways to obtain other and / or alternative exemplary embodiments. For example, storage device 150 may be a data storage device including a cloud computing platform (e.g., public cloud, private cloud, community cloud, and hybrid cloud). However, these changes and modifications will not depart from the scope of this specification.

[0041] Figure 2 This is an exemplary block diagram of a database creation system for a medical system, as shown in some embodiments of this specification.

[0042] like Figure 2 As shown, in some embodiments, the database creation system 200 may include an acquisition module 210, a creation module 220, an update module 230, and a code generation module 240. In some embodiments, the functions corresponding to the system 200 may be executed by the processing device 140, such that the acquisition module 210, creation module 220, update module 230, and code generation module 240 may be modules within the processing device 140.

[0043] The acquisition module 210 can be used to acquire a DICOM data structure. In some embodiments, the DICOM data structure may include at least one data field related to medicine, or any combination thereof. In some embodiments, the acquisition module 210 may acquire the DICOM data structure via a network (such as network 120), a storage device (such as storage device 150), or a user terminal (such as terminal device 130). In some embodiments, the DICOM data structure may include value representation (VR).

[0044] The creation module 220 can be used to determine the storage structure corresponding to the DICOM data structure based on input information. In some embodiments, the input information may include the relationship between data fields and data tables, and the relationship between data tables. In some embodiments, the storage structure can be used to generate a database instance of a medical system. In some embodiments, the storage structure may include data types and / or data constraints. In some embodiments, the creation module 220 can determine the data type and / or data constraints corresponding to the storage structure based on the value representation corresponding to the input information. In some embodiments, the creation module 220 can determine the relationship between data fields and data tables, and the relationship between data tables, based on the input information. In some embodiments, the creation module 220 can establish a corresponding view based on the relationship between data fields and data tables, and the relationship between data tables. In some embodiments, the creation module 220 can generate a structured query language based on the storage structure.

[0045] The update module 230 can be used to obtain the updated DICOM data structure and update the database based on the updated DICOM data structure.

[0046] The code generation module 240 can be used to automatically generate program code for the definition of corresponding data objects based on the storage structure.

[0047] It should be understood that Figure 2The database creation system 200 and its modules shown can be implemented in various ways. For example, in some embodiments, the system and its modules can be implemented by hardware, software, or a combination of both. The hardware portion can be implemented using dedicated logic; the software portion can be stored in memory and executed by an appropriate instruction execution system, such as a microprocessor or dedicated hardware. Those skilled in the art will understand that the methods and systems described above can be implemented using computer-executable instructions and / or included in processor control code, for example, on a carrier medium such as a disk, CD, or DVD-ROM, a programmable memory such as read-only memory (firmware), or a data carrier such as an optical or electronic signal carrier. The systems and modules of this specification can be implemented not only by hardware circuits such as very large-scale integrated circuits or gate arrays, semiconductors such as logic chips, transistors, or programmable hardware devices such as field-programmable gate arrays, programmable logic devices, etc., but also by software, for example, executed by various types of processors, or by a combination of the aforementioned hardware circuits and software (e.g., firmware).

[0048] It should be noted that the above description of the database creation system 200 and its modules is for convenience only and should not be construed as limiting this specification to the scope of the embodiments described. It is understood that those skilled in the art, after understanding the principles of this system, may arbitrarily combine the various modules or construct subsystems connected to other modules without departing from these principles.

[0049] Figure 3 This is an exemplary flowchart of a database creation method for a medical system according to some embodiments of this specification.

[0050] Step 302: Obtain the DICOM data structure. In some embodiments, step 302 may be performed by the processing device 140 or the database creation system 200 (such as the acquisition module 210).

[0051] The DICOM (Digital Imaging and Communications in Medicine) data structure can be a definition document of the DICOM standard. DICOM defines a medical image format that meets clinical needs and can be used for data exchange, and it follows the international standard (ISO 12052) for medical images and related information.

[0052] In some embodiments, the DICOM data structure may include descriptive information about DICOM data items of a complete medical system. In some embodiments, the DICOM data structure may include at least one data field related to medicine. A field is a member that can represent a variable associated with an object or class. In some embodiments, fields may correspond to "columns" of a table, with each field containing information on a specific topic, for example... Figure 4 Each column contains a corresponding Module field, Tag field, Name field, Keyword field, etc.

[0053] In some embodiments, the medical-related module may be a component related to ultrasound or medical image communication, such as an image module, a study module, a series module, etc. In some embodiments, the medical-related tag may be a label in a DICOM data structure used to identify data. In some embodiments, a tag can be represented by 4 bytes, with the first two bytes being the group number and the last two bytes being the element number. For example, in Tag(0008, 0018), 0008 is the group number and 0018 is the element number. Each tag is a unique identifier for each data item. In some embodiments, the name may be a description of the terminology involved in the diagnosis, such as end-to-end distance, examination time, image type, etc.

[0054] In some embodiments, the DICOM data structure may include other medically relevant data fields, such as fields corresponding to all information generated in the diagnosis, including patient data, image data, and device data. In some embodiments, patient data may include patient name, patient ID, patient age, scan site, etc. In some embodiments, image data may include capture time, capture location, patient posture, number of image rows, number of image columns, image resolution, etc. In some embodiments, device data may include the X-ray tube voltage, data acquisition diameter, device serial number, bed height, bed speed, exposure time, X-ray tube current, etc.

[0055] In some embodiments, the DICOM data structure may also include value representation (VR), such as... Figure 4 or Figure 5As shown. The value representation can reflect the data type of the DICOM data structure. For example, value representation types can include code string (CS), short string (SH), long string (LO), short text (ST), long text (LT), unlimited text (UT), application entity (AE), person name (PN), unique identifier (UID or UI), date (DA), time (TM), date time (DT), age string (AS), integer string (IS), decimal string (DS), signed short (SS), unsigned short (US), signed long (SL), unsigned long (UL), attribute tag (AT), and floating single (Floating Single). Strings can be categorized into several types, including FL (Floating Point), FD (Floating Point Double), OB (Other Byte String), OW (Other Word String), OF (Other Float String), SQ (Sequence Items), and UN (Unknown Byte String). Each type has corresponding allowed characters and data lengths. For example... Figure 5 This is an exemplary description of partial value representations, including the definitions, allowed characters, and data lengths of partial value representations such as AE, AS, AT, etc.

[0056] In some embodiments, the acquisition module 210 can acquire the DICOM data structure through a network (such as network 120), a storage device (such as storage device 150), a user terminal (such as terminal device 130), etc.

[0057] In some embodiments, DICOM data structures can be loaded in the form of Excel files, XML files, JSON files, CSV files, etc. Figure 4The image shows a DICOM data structure loaded as an Excel file. In some embodiments, after loading, a mapping structure corresponding to the DICOM data structure can be used in memory to save the data items and their specific descriptions. This information will be displayed in a visualization window using a list box for selection, such as... Figure 6 As shown in the image.

[0058] Step 304: Determine the storage structure corresponding to the DICOM data structure based on the input information. In some embodiments, step 304 may be performed by the processing device 140 or the database creation system 200 (such as creation module 220).

[0059] Input information can be instructions that a user inputs into a terminal (such as terminal device 130) or processor (such as processing device 140) based on their own needs. In some embodiments, input information may include selected input data and custom input data. In some embodiments, selected input data can be achieved by checking boxes in a visual window, selecting from drop-down menus, etc.; custom input data can be achieved by the user manually inputting it in a visual window. This is just an example. Figure 6 In the illustration of the exemplary mapping structure visualization window, users can select the required data in the "Select" column as the data for building the storage structure, or directly enter custom data in the blank rows or columns of the visualization window, such as customizing the relevant data in the blank cells of the column corresponding to the Tag field.

[0060] In some embodiments, the input information may include data related to module fields, label fields, name fields, and value notation fields, or any combination thereof. In some embodiments, the input information may include relationships between data fields and data tables, as well as relationships between data tables.

[0061] A data table refers to the table containing the data to be created. The relationship between data fields and data tables refers to the association between data fields and their corresponding data tables. For example, a label field can uniquely identify each data item in a data table, and the relationship between data fields and data tables ensures the integrity of the database data.

[0062] The relationship between data tables refers to the association between different data tables. In some implementations, this can be a foreign key between tables. A single data table can correspond to multiple foreign keys. The relationship between data tables ensures database data consistency.

[0063] In some embodiments, one or more data tables can be generated based on input information. For example, a data table associated with a selected tag can be automatically created. Different databases may correspond to different data tables; different data structures, such as patient information and examination information, correspond to different databases.

[0064] A storage structure can be a representation of the logical structure of data in a computer. In some embodiments, the storage structure can be used to generate database instances related to a medical system. In some embodiments, the storage structure corresponding to a DICOM data structure can be determined based on information such as label fields, name fields, value notation fields, and module fields corresponding to the input information.

[0065] In some embodiments, the storage structure may include data types and / or data constraints.

[0066] Data constraints can be restrictions on the character format for each data type, such as limiting the length of characters or the symbols used. For example, CS (Code String) is a code string that can only use uppercase letters, 0-9, spaces, and underscores, and its length is limited to a maximum of 16 characters.

[0067] In some embodiments, the data type and / or data constraints corresponding to the storage structure can be determined based on the value representation corresponding to the input information. The same data may have different data types and data constraints in different types of data structures. For example, the processing device 140 can generate the name of the data item in the storage structure based on the selected tag and the name of the data item corresponding to that tag in the DICOM data structure, extract the data type and data constraint information of VR in the DICOM data structure, and generate the data type and data constraints corresponding to the data item in the storage structure. In some embodiments, other information in the DICOM data structure based on the input information (such as the selected tag) can be concatenated and saved as annotation information for the corresponding data item in the storage structure.

[0068] In some embodiments, the relationship between data fields corresponding to the storage structure and data tables, as well as the relationship between data tables, can be determined based on input information.

[0069] By determining the relationships between data fields and data tables, and between data tables, we can determine the logical relationships between data in a single data table, as well as the relationships between database data tables (i.e., between the main table and sub-tables).

[0070] In some embodiments, corresponding views can be created based on the relationships between data fields and data tables, as well as the relationships between data tables.

[0071] A view can be a virtual data entity derived from one or more data tables (or views). Views do not occupy memory space, do not store data, and their structure and content are derived from the data tables. In some embodiments, a view can reflect the relationships between data fields and data tables, as well as the relationships between data tables themselves. By creating views, the relationships between data fields and data tables, as well as the relationships between data tables, can be further illustrated, facilitating users to query and modify key data, while also allowing users to access only a portion of the data, thus improving data security.

[0072] In some embodiments, corresponding data tables and / or views can be established based on user-selected input data and / or custom input data, with the data tables and views corresponding to storage structures. In some embodiments, data definition information obtained from different input sources (such as data types, data constraints, and annotation information corresponding to the storage structure) can be integrated into the same data table and view, and a database definition file (such as a JSON file) can be generated for storage.

[0073] In some embodiments, a structured query language can be generated based on the storage structure. Structured Query Language (SQL) is a language used for database querying and programming, and may include, for example, Data Query Language (DQL), Data Manipulation Language (DML), Transaction Control Language (TCL), Data Control Language (DCL), Data Definition Language (DDL), Cursor Control Language (CCL), etc.

[0074] In some embodiments, structured query languages ​​such as DDL and DML can be generated based on the storage structure. These structured query languages ​​can then be imported into any database management system that supports the corresponding structured query language standard to automatically generate the corresponding database instance. For example... Figure 9 As shown, after importing Structured Query Language into the "Database Script Text Box" on the right, a corresponding database instance can be automatically generated. This database can include multiple tables such as t_study and t_patient.

[0075] A Database Management System (DBMS) is a large software application that manipulates and manages databases. It allows users to define the database's data structure and access constraints, and to perform operations such as adding and deleting data. For the steps involved in generating a Structured Query Language (SCL) application, please refer to [link to DBMS documentation]. Figure 7 The details and related descriptions will not be repeated here.

[0076] In some embodiments, program code related to data object definitions and operations can be automatically generated based on the storage structure. In some embodiments, a data object may include a composite data object consisting of multiple data fields corresponding to one or more databases. In some embodiments, the program code may include program code related to operations such as database creation, adding, modifying, and deleting view fields. In some embodiments, the data object may be determined based on the view established above.

[0077] In some embodiments, based on a user-defined object, its field data can be extracted and associated with code variables. The software development tool then automatically generates the corresponding data object definition program code based on this information. For more information on program code generation, please refer to [link to relevant documentation]. Figure 10 The details and related descriptions will not be repeated here.

[0078] In some embodiments, an updated DICOM data structure can be obtained, and the database, such as a created medical system database, can be updated based on the updated DICOM data structure.

[0079] In some embodiments, database updates can be implemented based on the updated DICOM data structure by updating (e.g., modifying or adding) old field data, deleting obsolete field data, etc. For more information on database updates, please refer to [link to relevant documentation]. Figure 8 The details and related descriptions will not be repeated here.

[0080] It should be noted that the above description of process 300 is for illustrative purposes only and does not limit the scope of this specification. Those skilled in the art can make various modifications and changes to process 300 under the guidance of this specification. However, these modifications and changes remain within the scope of this specification.

[0081] Figure 7 This is an exemplary flowchart of a database creation method for a medical system according to other embodiments of this specification.

[0082] In some specific embodiments, the processing device (such as processing device 140) can be the control terminal of a medical device (such as medical device 110), through which the following steps regarding the creation of the database are implemented:

[0083] Step 702: Obtain the DICOM data structure.

[0084] In some embodiments, a processing device (such as processing device 140) or a database creation system 200 (such as acquisition module 210) can acquire DICOM data structures from a network (such as network 120), a storage device (such as storage device 150), a terminal device (such as terminal device 130), etc.

[0085] Step 704: Determine the input information based on the mapping structure corresponding to the DICOM data structure.

[0086] In some embodiments, the processing device (such as processing device 140) or the database creation system 200 (such as acquisition module 210) can load the DICOM data structure in the form of Excel files, XML files, JSON files, CSV files, etc. After loading, a mapping structure corresponding to the DICOM data structure is used in memory to save the data items with their specific description information. In some embodiments, the mapping structure can be presented in a table format in a visual window (such as a Graphical User Interface, GUI), such as... Figure 6 As shown in the figure. In some embodiments, users can input information by selecting an input method based on the visualization window, such as selecting the corresponding tag, or customize the input data information (such as tag data, data constraints, data type, the relationship between tag fields and data tables, the relationship between data tables, etc.) in the visualization window.

[0087] Step 706: Based on the value representation corresponding to the input information, determine the data type and / or data constraints corresponding to the storage structure.

[0088] In some embodiments, a processing device (such as processing device 140) or a database creation system 200 (such as creation module 220) may determine the data type and / or data constraints corresponding to the storage structure based on input information. In some embodiments, the processing device (such as processing device 140) or the database creation system 200 (such as creation module 220) may, based on input information, generate the Name corresponding to the data item in the storage structure according to the Name in the DICOM data structure or manually entered, extract the data type and data constraints of VR in the DICOM data structure, generate the data type and data constraints corresponding to the data item in the storage structure, and collect other information to concatenate and save as annotation information corresponding to the data item in the storage structure.

[0089] Step 708: Establish the storage structure based on the relationship between data fields and data tables, as well as the relationship between data tables.

[0090] In some embodiments, a processing device (such as processing device 140) or a database creation system 200 (such as creation module 220) can integrate the data corresponding to all input fields, bind them with data table or view information, and construct complete data table or view definition information to establish a storage structure. In some embodiments, the complete data table or view definition information described above can be stored in a database definition file (such as a JSON file).

[0091] Step 710: Generate a structured query language based on the storage structure.

[0092] In some embodiments, a processing device (such as processing device 140) or a database creation system 200 (such as creation module 220) may generate DDL and DML files based on storage structures, such as the definition information of data tables or views, and save them as SQL script files.

[0093] Step 712: Generate the corresponding database instance based on Structured Query Language.

[0094] In some embodiments, a processing device (such as processing device 140) or a database creation system 200 (such as creation module 220) can import SQL script files into any database management system that supports the SQL standard to generate a corresponding database instance, such as... Figure 9 As shown in the image.

[0095] Figure 8 This is an exemplary flowchart of a database update method according to some embodiments of this specification. In some embodiments, Figure 8 The process 800 shown can be executed by a processing device (such as processing device 140) or a database creation system 200 (such as update module 230).

[0096] Step 802: Obtain the updated DICOM data structure.

[0097] In some embodiments, a processing device (such as processing device 140) or a database creation system 200 (such as update module 230) can obtain an updated DICOM data structure from a storage device (such as storage device 150), the Internet, or the like.

[0098] Step 804: Load the database definition file.

[0099] A database definition file can refer to a file containing complete definition information for a data table or view. In some embodiments, the database definition file may include a JSON file generated based on the storage structure. In some embodiments, the database definition file may refer to the definition file generated in step 302. In some embodiments, the corresponding complete database tables and views can be generated in memory by parsing the database definition file.

[0100] Step 806: Determine the data to be updated based on the mapping structure corresponding to the DICOM data structure.

[0101] In some embodiments, the corresponding DICOM data items bound to the data tables and views corresponding to the database definition file can be found from the updated DICOM data structure list based on the mapping structure to determine the corresponding data to be updated.

[0102] Step 808: Update the corresponding field data.

[0103] In some embodiments, the data to be updated can be updated based on the updated DICOM data structure. For example, if a data item in the DICOM data structure has been modified, the data bound to that data item in the complete data table and view generated based on the JSON definition file will be updated along with it; if a DICOM data item has been deprecated, the data bound to that data item in the complete data table and view can be deleted manually or automatically as needed.

[0104] Step 810: Update the database definition file.

[0105] In some embodiments, a new database definition file can be generated based on the new database definition information described above.

[0106] Step 812: Generate the corresponding structured query language based on the updated database definition file.

[0107] In some embodiments, SQL scripts such as DDL and DML for the corresponding database can be generated based on the information defined in the updated database definition file, and these scripts can be saved to an SQL script file in the standard SQL format.

[0108] Step 814: Generate the corresponding database instance based on Structured Query Language.

[0109] In some embodiments, the new SQL script file described above can be imported into the database management system to generate a corresponding new database instance.

[0110] After a DICOM standard update, some original data items may be deleted or modified, or new data items may be added. Using the database update method provided in the embodiments of this specification, when the DICOM data structure is updated, only the DICOM standard archive file needs to be modified, and then the DICOM standard reloaded. Simultaneously, the previously saved database definition file is loaded, and the corresponding information is modified to update the database. This reduces operations and improves database update efficiency.

[0111] In some embodiments, data items stored in the system may be migrated from the DICOM standard to other types of medical information standards, such as the HL7 health information exchange standard. In this case, data items defined by the HL7 standard can be included in the archive file to replace the DICOM standard archive file, and then the above process can be repeated without having to design the database script from scratch.

[0112] It should be noted that the above descriptions of processes 700 and 800 are for illustrative purposes only and do not limit the scope of this specification. Those skilled in the art can make various modifications and changes to processes 700 and / or 800 under the guidance of this specification. However, such modifications and changes remain within the scope of this specification.

[0113] Figure 10 This is an exemplary flowchart illustrating a method for automatically generating corresponding data object definitions according to some embodiments of this specification. In some embodiments, Figure 10 The process 1000 shown can be executed by a processing device (such as processing device 140) or a database creation system 200 (such as code generation module 240).

[0114] In some specific embodiments, the processing device (such as processing device 140) can be the control terminal of a medical device (such as medical device 110), which can automatically generate corresponding program code based on the storage structure, specifically:

[0115] Step 1002: Select the data table and / or view for which you want to create the code.

[0116] In some embodiments, the operator may select the data table or view from existing data tables or views from which access codes need to be generated. For example, the user may select the corresponding data table and / or view from a data definition file.

[0117] Step 1004: Map the field information to programming language data types.

[0118] In some embodiments, the target programming language corresponding to the program code, such as C++ or JAVA, can be selected first, and the field information corresponding to the selected table or view can be mapped to the data type corresponding to the target programming language. For example, if the field of the data table is of type varchar and the target programming language is C++, then the field of the data table can be mapped to the string data type.

[0119] Step 1006: Generate the data member code corresponding to the field.

[0120] In some embodiments, data member code corresponding to the field is generated based on the mapped programming language data type. For example, the processing device 140 can generate code variables with the same names as the fields in the selected target programming language from the field information of the selected table or view, and generate the corresponding types of the data table fields according to the specifications of the programming language. For example, a field in a table corresponds to a data member of a class.

[0121] Step 1008: Generate the program code for the data table or view.

[0122] In some embodiments, once all fields of a data table or view have been processed, all data members can be encapsulated to generate program code (i.e., entity code) in the corresponding programming language. For example, if the target programming language is C++, the generated structure is JAVA.

[0123] In some embodiments, users (such as software developers) can compile the corresponding software development project based on the generated code.

[0124] In some embodiments of this specification, (1) based on the organized DICOM data structure, the corresponding data table or view can be automatically created by checking the boxes in the program. This process only requires checking some check boxes or selecting specific items from the drop-down box, which can quickly and accurately complete the creation of the database; (2) in this method, through simple operations, the fields of the standard DICOM data structure and the database fields can be bidirectionally bound, which facilitates the maintenance and repeated use of the database by the database administrator; (3) this method can automatically create the structure entity code of the corresponding data table or view with one click, replacing the inefficient and cumbersome manual coding and improving the compilation efficiency.

[0125] The basic concepts have been described above. Obviously, for those skilled in the art, the detailed disclosure above is merely illustrative and does not constitute a limitation of this specification. Although not explicitly stated herein, those skilled in the art may make various modifications, improvements, and corrections to this specification. Such modifications, improvements, and corrections are suggested in this specification and therefore remain within the spirit and scope of the exemplary embodiments described herein.

[0126] Furthermore, this specification uses specific terms to describe embodiments thereof. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic associated with at least one embodiment of this specification. Therefore, it should be emphasized and noted that references to "an embodiment," "one embodiment," or "an alternative embodiment" in different locations throughout this specification do not necessarily refer to the same embodiment. Moreover, certain features, structures, or characteristics in one or more embodiments of this specification can be appropriately combined.

[0127] Furthermore, unless expressly stated in the claims, the order of processing elements and sequences, the use of numbers and letters, or other names described in this specification are not intended to limit the order of the processes and methods described herein. Although various examples have been discussed in the foregoing disclosure of some embodiments of the invention that are currently considered useful, it should be understood that such details are for illustrative purposes only, and the appended claims are not limited to the disclosed embodiments; rather, the claims are intended to cover all modifications and equivalent combinations that conform to the spirit and scope of the embodiments described herein. For example, while the system components described above can be implemented using hardware devices, they can also be implemented solely using software solutions, such as installing the described system on existing servers or mobile devices.

[0128] Similarly, it should be noted that, in order to simplify the description disclosed herein and thus aid in the understanding of one or more embodiments of the invention, the foregoing description of embodiments in this specification may sometimes combine multiple features into a single embodiment, drawing, or description thereof. However, this method of disclosure does not imply that the subject matter of this specification requires more features than those mentioned in the claims. In fact, the embodiments contain fewer features than all the features of a single embodiment disclosed above.

[0129] In some embodiments, numbers describing the quantity of components and attributes are used. It should be understood that such numbers used in the description of embodiments are modified in some examples with the terms "approximately," "approximately," or "generally." Unless otherwise stated, "approximately," "approximately," or "generally" indicates that the numbers are allowed to vary by ±20%. Accordingly, in some embodiments, the numerical parameters used in the specification and claims are approximate values, which may be changed depending on the characteristics required by individual embodiments. In some embodiments, numerical parameters should take into account specified significant digits and employ a general method of digit reservation. Although the numerical ranges and parameters used to confirm their breadth of range in some embodiments of this specification are approximate values, in specific embodiments, such values ​​are set as precisely as feasible.

[0130] For each patent, patent application, patent application publication, and other material such as articles, books, specifications, publications, and documents referenced in this specification, the entire contents of which are incorporated herein by reference. This excludes historical application documents that are inconsistent with or conflict with the content of this specification, as well as documents that limit the broadest scope of the claims in this specification (currently or subsequently appended to this specification). It should be noted that in the event of any inconsistency or conflict between the descriptions, definitions, and / or terminology used in the supplementary materials to this specification and the content of this specification, the descriptions, definitions, and / or terminology used in this specification shall prevail.

[0131] Finally, it should be understood that the embodiments described in this specification are merely illustrative of the principles of the embodiments described herein. Other variations may also fall within the scope of this specification. Therefore, alternative configurations of the embodiments described herein are intended to be illustrative rather than limiting, and should be considered consistent with the teachings of this specification. Accordingly, the embodiments described herein are not limited to those explicitly introduced and described herein.

Claims

1. A method for creating a database for a medical system, executed by at least one processor, characterized in that, The method includes: Obtain the DICOM data structure, which is a definition file of the DICOM standard. The DICOM data structure includes at least one data field related to medicine, including a module field, a label field, a name field, and a keyword field. The DICOM data structure is loaded using a preset method, and the data items and their specific description information are saved in memory using a mapping structure corresponding to the DICOM data structure. The mapping structure corresponding to the DICOM data structure is displayed through a visualization window; The system acquires input information from the user through the visualization window. This input information includes label data, data constraints, data types, the relationship between the data fields and data tables, and the relationship between data tables. Different databases correspond to different data tables, and data with different structures correspond to different databases. Based on the input information, a storage structure corresponding to the DICOM data structure is determined; this storage structure is used to generate database instances related to the medical system. The program code that automatically generates the corresponding data object definition based on the storage structure includes program code related to at least one operation of objects related to database creation, adding, modifying, or deleting view fields.

2. The method according to claim 1, characterized in that, The DICOM data structure includes value representation; The storage structure includes data types and / or data constraints, and the step of determining the storage structure corresponding to the DICOM data structure based on input information includes: Based on the value representation corresponding to the input information, determine the data type and / or data constraints corresponding to the storage structure.

3. The method according to claim 1, characterized in that, The step of determining the storage structure corresponding to the DICOM data structure based on the input information includes: Based on the input information, the relationship between the data fields corresponding to the storage structure and the data table, as well as the relationship between the data tables, are determined.

4. The method according to claim 3, characterized in that, The method further includes: Based on the relationships between the data fields and the data tables, as well as the relationships between the data tables, corresponding views are created.

5. The method according to claim 1, characterized in that, The method further includes: Data definition information from different input sources is integrated into the same data table and view, and a database definition file is generated for storage. The data definition information includes the data type, data constraints, and comment information corresponding to the storage structure; and / or A structured query language is generated based on the storage structure.

6. The method according to claim 1, characterized in that, The method further includes: Obtain the updated DICOM data structure; Based on the mapping structure corresponding to the DICOM data structure, the data to be updated is determined; Update the corresponding field data; Update the DICOM data structure; Based on the updated database definition file, generate the corresponding structured query language; and Based on the structured query language, a corresponding database instance is generated.

7. A database creation system for a medical system, characterized in that, The system includes: The acquisition module is used to acquire a DICOM data structure, which is a definition file of the DICOM standard. The DICOM data structure includes at least one data field related to medicine, including a module field, a label field, a name field, and a keyword field. Create a module for The DICOM data structure is loaded using a preset method, and the data items and their specific description information are saved in memory using a mapping structure corresponding to the DICOM data structure. The mapping structure corresponding to the DICOM data structure is displayed through a visualization window; The system acquires input information from the user through the visualization window. This input information includes label data, data constraints, data types, the relationship between the data fields and data tables, and the relationship between data tables. Different databases correspond to different data tables, and data with different structures correspond to different databases. Based on the input information, a storage structure corresponding to the DICOM data structure is determined; this storage structure is used to generate a database instance for the medical system. The program code that automatically generates the corresponding data object definition based on the storage structure includes program code related to at least one operation of objects related to database creation, adding, modifying, or deleting view fields.

8. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the method as described in any one of claims 1-6.

9. A computer-readable storage medium storing computer instructions, wherein when a computer reads the computer instructions in the storage medium, the computer performs the method as described in any one of claims 1-6.

Images