Digital medical software development method and system supporting medical scientific research scene

By using the content management system to build content models and content entries in medical research scenarios, the efficiency of communication between software R&D personnel and medical personnel is solved, and the rapid delivery and development efficiency of digital medical software is achieved.

CN119025773APending Publication Date: 2024-11-26SHANDONG NORMAL UNIV
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202411065176.5
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-05
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

In medical research scenarios, how to quickly build an effective communication bridge so that software R&D personnel can quickly build content models based on functional needs, and encourage medical personnel to understand the model architecture and fill in software requirements in real time to improve the development efficiency of digital medical software.

Method used

By obtaining target software requirements, selecting content management system, building a primary software interface based on the clarity and types of requirements, and establishing corresponding content models in the content management system, generating templates and content entries, connecting content entries with software interfaces, and converting content into software Function to achieve rapid delivery.

Benefits of technology

It improves the development efficiency of digital medical software, allows software R&D personnel to build content models based on the needs of medical personnel, and fill in new needs in real time to achieve rapid delivery.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119025773A_ABST
    Figure CN119025773A_ABST
Patent Text Reader

Abstract

The invention provides a digital medical software development method and system supporting a medical scientific research scene, and the method comprises the steps: obtaining a target software demand, and selecting a content management system according to the obtained target software demand; constructing a primary software interface and establishing a corresponding content model in the content management system according to the definiteness and types of different requirements; classifying the software modules with similar content formats through the content model and generating a template; creating a corresponding content entry on the template; and connecting the content item with the primary software interface, and converting the content in the content item into a software function to obtain a complete software interface. According to the invention, rapid delivery of the digital medical software supporting the medical scientific research scene based on the content management system CMS can be realized.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention belongs to the field of software development technology, and in particular relates to a digital medical software development method and system that supports medical research scenarios. Background Art

[0002] The statements in this section merely provide background information related to the present invention and do not necessarily constitute prior art.

[0003] Content management system CMS is a software used to manage the creation and modification of digital content. Traditional content management system CMS is mainly used in enterprise content management (ECM) and website content management (WCM), and mainly solves the problem that static web pages are difficult to maintain and update. With the development of Web technology and the introduction of dynamic web pages and database technology, content management system CMS has gradually evolved from a simple file management system to a feature-rich, highly customized software platform, aiming to deepen the interaction, collaboration and integration between application development, technical operation and maintenance, and quality assurance departments. As the concept of CMS continues to deepen in the field of software engineering, it advocates the establishment of a close cooperation mechanism between software developers and technology demanders, and through highly automated "software delivery process" and "architecture change management", it can achieve the acceleration, frequency and reliability improvement of software building, testing and deployment processes. The rise of CMS is essentially a positive response of the software industry to the inherent demand for improving delivery efficiency and quality. It requires breaking the boundaries between traditional developers and technology demanders and promoting close collaboration between the two in the entire life cycle of software development.

[0004] In recent years, with the development of smart medical technology, more and more medical software has gradually participated in various medical research activities, such as medical image analysis, chronic disease care, out-of-hospital diagnosis and treatment, and medical decision-making. Scientific research activities in the medical field are increasingly dependent on interdisciplinary cooperation with computer software developers and joint development with software development companies. Content management systems (CMS) can provide good technology and software platforms for joint development by medical personnel and software developers.

[0005] However, software development based on content management systems (CMS) also faces significant challenges. One of them is how to build an effective communication bridge so that software developers can quickly build content models based on functional requirements. At the same time, how to encourage medical personnel (technology demanders) to understand the model architecture in the early stages of software development, fill in new software requirements and build content items in real time according to the progress of medical research projects, so as to improve the development efficiency of digital medical software, has also become a key technical issue that needs to be urgently resolved in this field. Summary of the invention

[0006] In order to overcome the deficiencies of the above-mentioned prior art, the present invention provides a method and system for developing digital medical software that supports medical research scenarios, which can realize the rapid delivery of digital medical software that supports medical research scenarios based on the content management system CMS.

[0007] To achieve the above objectives, one or more embodiments of the present invention provide the following technical solutions:

[0008] A first aspect of the present invention provides a method for developing digital medical software that supports medical research scenarios.

[0009] A digital medical software development method supporting medical research scenarios, comprising:

[0010] Obtain target software requirements and select a content management system based on the obtained target software requirements;

[0011] According to the clarity and category of different requirements, a primary software interface is constructed and a corresponding content model is established in the content management system; through the content model, software modules with similar content formats are classified and a template is generated; and corresponding content items are created on the template;

[0012] The content item is connected to the primary software interface, and the content in the content item is converted into software functions to obtain a complete software interface.

[0013] The content management system is an interface-free content management system, including Web iny, Jamstack and Contentful.

[0014] Build primary software interfaces based on the clarity of different requirements, including:

[0015] For functions with clear requirements, a module with complete functions is directly generated and a high-fidelity design sample is given; for functions whose requirements are not yet fully clear, only a blank function page is reserved.

[0016] The different types of needs include questionnaires, information queries, form submissions, report generation, text input, image uploads, video embedding, comments, page formats and page content; corresponding content models are established in the content management system based on the different types of needs.

[0017] When there is a need for a questionnaire, a corresponding content model is established in the content management system, including:

[0018] According to the prompt of the model editor in the content management system Web i ny, set the metadata of the content model and the default initial data of the model page; and select the corresponding data type, design layout and set variables in the model editor.

[0019] In the model editor, select the appropriate data type, design layout, and set variables, including:

[0020] For parameter groups / modules with complex nested structures, the parameters are wrapped by selecting the object type; then, by setting the "repeatable" variable, the parameter group / module can be generated in any quantity as required in the content model;

[0021] For parameter groups / modules that need to be reused multiple times in multiple models, first, create a sub-content model and put the reused parameter groups / modules into the sub-content model; then, drag the reference type from the main content model and set the reference to the sub-model so that the parameter groups / modules in the sub-model can be reused by multiple content models.

[0022] When connecting the content item with the primary software interface, there are three different connection methods, specifically:

[0023] When a content item corresponds to a complete web page, the content item is directly stored in the software in the form of a web page through the content management system;

[0024] When a model item corresponds to a web page component, the content item is referenced in the content item of the complete web page to achieve connection and display between the content item and the primary software interface;

[0025] When a model entry contains more complex content and cannot be directly displayed in the form of a web page, a module capable of reading the content entry is created, and the corresponding software function is implemented according to the content in the content module.

[0026] A second aspect of the present invention provides a digital medical software development system that supports medical research scenarios.

[0027] A digital medical software development system supporting medical research scenarios, including:

[0028] The requirement acquisition module is configured to: acquire the target software requirements and select a content management system according to the acquired target software requirements;

[0029] The content model building module is configured to: construct a primary software interface and establish a corresponding content model in the content management system according to the clarity and category of different requirements; classify software modules with similar content formats and generate templates through the content model; and create corresponding content items on the template;

[0030] The connection module is configured to connect the content item with the primary software interface, convert the content in the content item into software functions, and obtain a complete software interface.

[0031] The third aspect of the present invention provides a computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the steps in a method for developing digital medical software that supports medical research scenarios as described in the first aspect of the present invention.

[0032] The fourth aspect of the present invention provides an electronic device, comprising a memory, a processor, and a program stored in the memory and executable on the processor, wherein when the processor executes the program, the steps in a method for developing digital medical software that supports medical research scenarios as described in the first aspect of the present invention are implemented.

[0033] One or more of the above technical solutions have the following beneficial effects:

[0034] The present invention provides a method for developing digital medical software that supports medical research scenarios. According to the clarity and types of different requirements, a primary software interface is constructed and a corresponding content model is established in the content management system; a template is generated through the content model and corresponding content items are created on the template. Software developers can build corresponding content models and reserve modules according to the software design requirements provided by medical personnel; at the same time, medical personnel can fill in new software requirements in real time according to the progress of medical research projects and directly build new content items on the reserved modules, which greatly improves the development efficiency of digital medical software. Therefore, the present invention can achieve rapid delivery of digital medical software that supports medical research scenarios based on the content management system CMS.

[0035] Advantages of additional aspects of the present invention will be given in part in the following description, and in part will become obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings in the specification, which constitute a part of the present invention, are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute improper limitations on the present invention.

[0037] Figure 1 This is a flowchart of a digital medical software development method that supports medical research scenarios in Example 1 of the present invention.

[0038] Figure 2 The following is a design decision flow chart of the content model in the first embodiment of the present invention.

[0039] Figure 3 This is a flow chart of the method for generating a content model in Embodiment 1 of the present invention.

[0040] Figure 4 This is a module diagram of a digital medical software development system that supports medical research scenarios in Example 2 of the present invention. DETAILED DESCRIPTION

[0041] It should be noted that the following detailed descriptions are exemplary and are intended to provide further explanation of the present invention. Unless otherwise specified, all technical and scientific terms used herein have the same meanings as those commonly understood by those skilled in the art to which the present invention belongs.

[0042] It should be noted that the terms used herein are for describing specific embodiments only and are not intended to be limiting of exemplary embodiments according to the present invention.

[0043] In the absence of conflict, the embodiments of the present invention and the features of the embodiments may be combined with each other.

[0044] Embodiment 1

[0045] This embodiment discloses a digital medical software development method that supports medical research scenarios.

[0046] like Figure 1 As shown, a digital medical software development method supporting medical research scenarios includes:

[0047] Step S1: Obtain target software requirements, and select a content management system CMS according to the obtained target software requirements.

[0048] Step S2: construct a primary software interface and establish a corresponding content model in the content management system according to the clarity and category of different requirements; classify software modules with similar content formats and generate templates through the content model; and create corresponding content entries on the templates.

[0049] Step S3: Connect the content item with the primary software interface, convert the content in the content item into software functions, and obtain a complete software interface.

[0050] Specifically, in step S1, when obtaining the target software requirements, the software development team and medical researchers communicate fully through various methods such as exchanging documents, group meetings, one-on-one interviews, etc., so as to fully understand the medical software requirements of the medical research team.

[0051] Then, select the content management system CMS according to the obtained target software requirements. According to whether the presentation layer is provided, the content management system can generally be divided into two categories, namely the traditional content management system with an interface and the content management system without an interface. Among them, the traditional content management system with an interface includes Workpress, Drupal and Sitecore. While storing and managing network content, such systems also provide a presentation layer on each website; users can directly manage the managed content through this presentation layer. The content management system without an interface includes Webiny, Jamstack and Contentful. This system is a back-end content management system. It does not provide a separate presentation layer for each website, but provides content for the website through a more flexible API call method. An interface-less management system has only one global background, which is used to manage all the content stored by the system.

[0052] In this embodiment, Web i ny is selected as the content management system, and subsequent software design is performed.

[0053] Specifically, in step S2, a primary software interface is constructed according to the clarity of different requirements, including:

[0054] Different requirements are divided into clear requirements and unclear requirements according to their clarity. For functions with clear requirements, directly generate modules with complete functions and provide high-fidelity mockups; for functions with unclear requirements, only reserve blank function pages or complete low-fidelity mockups first, and then reserve modules based on known requirements, design approximate input and output parameters, and the corresponding interfaces of the connection logic between modules. The interface between modules is the API interface, and the input and output parameters are the input and output parameters of the API; formally, for a function (y1, y2, ..., y n )=F(x1,x2,...,x m ),x i Is the input parameter, y i That is, the output parameter; the design of the input and output parameters is based on the functions of the functional modules, and the default format of the input and output data of the API interface is JSON.

[0055] Specifically, the types of different needs include questionnaires, information queries, form submissions, report generation, text input, image uploads, video embedding, comments, page formats, and page content, etc. Corresponding content models are established in the content management system according to the types of different needs.

[0056] like Figure 2As shown in the figure, taking the questionnaire as an example, when the software to be developed needs the questionnaire function, its design decision process includes: first, determine whether the specific questionnaire has a similar structure; if the structure is very different, the questionnaires with similar structures are grouped and content models are generated separately; then, for each type of questionnaire, determine the possible format of the questions, such as parameters such as title, description, completion time, and answer methods, such as single choice, multiple choice, drag bar, text fill-in-the-blank, etc.; finally, according to the question format and answer method of each type of questionnaire, complete the generation of the content model in sequence.

[0057] The data types used when designing a model using the model editor in the content management system Webini include: Text: text, used for single-line text such as titles, comments, parameter information, etc.; Long Text: long text, used for multi-line text such as large articles; Rich Text: rich text, used for complex structured text containing different fonts, links and multimedia content; Number: number, used for digital information such as parameter values; Boolean: Boolean value, used for (true / false) value information; Date / Time: date and time, used to provide a module for convenient date / time input; Reference: reference, used to reference entries in other content models; Object: object, used to create complex nested data structures, in which multiple data structures or other objects can be nested; Files: files, used to store files.

[0058] Specifically, Figure 3 As shown, when the developed software needs a questionnaire function, a corresponding content model is established in the content management system, including:

[0059] According to the prompts of the model editor in the content management system Webini, set the metadata of the content model and the default initial data of the model page; and select the corresponding data type, design layout and set variables in the model editor. The metadata of the content model includes the model name, model call API name, model group and model description; the default initial data of the model page includes the page title, introduction and title picture.

[0060] More specifically, in the model editor, select the corresponding data type, design layout and set variables, including:

[0061] For parameter groups / modules with complex nested structures, the parameters are wrapped by selecting an object type; then, by setting the "repeatable" variable, the parameter group / module can be generated in any quantity as required in the content model. The reason for these designs is that some input data has a complex nested structure and will be created repeatedly, such as the questions of a questionnaire survey. Therefore, this type of data structure will be included in an object type in the model. First, this type can support complex nested data structures, and second, this type supports multiple creations of the same data structure in the same model.

[0062] For parameter groups / modules that need to be reused multiple times in multiple models, first, create a sub-content model and put the reused parameter groups / modules into the sub-content model; then, drag the reference type from the main content model and set the reference to the sub-model so that the parameter groups / modules in the sub-model can be reused by multiple content models. The reason for these designs is that since data needs to be reused multiple times, this can make a model abstract and easier for users to understand; it can decouple data logically; and it can be reused multiple times across models.

[0063] Specifically, in step S2, the software modules with similar content formats are classified and a template is generated through the above content model, including:

[0064] Each module corresponds to one (or more) content type and its template, and uses backend technology to implement the functional logic of the module; the functional logic includes processing data addition, deletion, modification and query, managing the relationship between content models and templates, and implementing any specific business rules. Define a clear API interface for the module, which should follow standard specifications such as RESTful or GraphQL to ensure interoperability and scalability.

[0065] Then, create the corresponding content entry on the generated template, namely:

[0066] A content type corresponding to the demand is selected from the established content model, and the title, text, label and classification information of the content item are filled into the content model to obtain the content item corresponding to the demand.

[0067] Specifically, in step S3, the content item is connected to the primary software interface, and the content in the content item is converted into software functions to obtain a complete software interface.

[0068] There are three different connection methods for connecting the content item with the primary software interface, including:

[0069] (1) When a content item corresponds to a complete web page, the content item is directly stored in the software in the form of a web page through the content management system;

[0070] (2) When a model item corresponds to a web page component, the content item is referenced in the content item of the complete web page to achieve connection and display between the content item and the primary software interface;

[0071] (3) When a model entry contains more complex content and cannot be directly displayed in the form of a web page, a module that can read the content entry is created to implement the corresponding software function based on the content in the content module.

[0072] More specifically, for connection methods (1) and (2), medical personnel can complete the subsequent entry and web page content maintenance work; for connection method (3), software developers can adjust and maintain the functions.

[0073] Embodiment 2

[0074] This embodiment discloses a digital medical software development system that supports medical research scenarios.

[0075] like Figure 4 As shown, a digital medical software development system supporting medical research scenarios includes:

[0076] The requirement acquisition module is configured to: acquire the target software requirements and select a content management system according to the acquired target software requirements;

[0077] The content model building module is configured to: construct a primary software interface and establish a corresponding content model in the content management system according to the clarity and category of different requirements; classify software modules with similar content formats and generate templates through the content model; and create corresponding content items on the template;

[0078] The connection module is configured to connect the content item with the primary software interface, convert the content in the content item into software functions, and obtain a complete software interface.

[0079] Embodiment 3

[0080] The purpose of this embodiment is to provide a computer-readable storage medium.

[0081] A computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps in a method for developing digital medical software that supports medical research scenarios as described in Example 1 of the present disclosure.

[0082] Embodiment 4

[0083] The purpose of this embodiment is to provide an electronic device.

[0084] An electronic 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 steps in a method for developing digital medical software supporting medical research scenarios as described in Example 1 of the present disclosure are implemented.

[0085] The steps involved in the apparatuses of the above embodiments 2, 3 and 4 correspond to the method embodiment 1, and the specific implementation methods can refer to the relevant description part of embodiment 1. The term "computer-readable storage medium" should be understood as a single medium or multiple media including one or more instruction sets; it should also be understood to include any medium that can store, encode or carry an instruction set for execution by a processor and enable the processor to execute any method in the present invention.

[0086] Those skilled in the art should understand that the modules or steps of the present invention described above can be implemented by a general-purpose computer device, or alternatively, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. The present invention is not limited to any specific combination of hardware and software.

[0087] Although the above describes the specific implementation mode of the present invention in conjunction with the accompanying drawings, it is not intended to limit the scope of protection of the present invention. Those skilled in the art should understand that various modifications or variations that can be made by those skilled in the art on the basis of the technical solution of the present invention without creative work are still within the scope of protection of the present invention.

Claims

1. A digital medical software development method that supports medical research scenarios. It is characterized in that include: Obtain target software requirements and select a content management system based on the obtained target software requirements; According to the clarity and category of different requirements, a primary software interface is constructed and a corresponding content model is established in the content management system; through the content model, software modules with similar content formats are classified and templates are generated; Creating a corresponding content entry on the template; The content item is connected to the primary software interface, and the content in the content item is converted into software functions to obtain a complete software interface.

2. A digital medical software development method supporting medical research scenarios as claimed in claim 1, It is characterized in that The content management system is a non-interface content management system, including Webiny, Jamstack and Contentful.

3. A digital medical software development method supporting medical research scenarios as claimed in claim 1, It is characterized in that Build primary software interfaces based on the clarity of different requirements, including: For functions with clear requirements, a module with complete functions is directly generated and a high-fidelity design sample is given; for functions whose requirements are not yet fully clear, only a blank function page is reserved.

4. A digital medical software development method supporting medical research scenarios as claimed in claim 1, It is characterized in that The different types of needs include questionnaires, information queries, form submissions, report generation, text input, image uploads, video embedding, comments, page formats and page content; corresponding content models are established in the content management system based on the different types of needs.

5. A digital medical software development method supporting medical research scenarios as claimed in claim 4, It is characterized in that When there is a need for a questionnaire, a corresponding content model is established in the content management system, including: According to the prompt of the model editor in the content management system Webiny, set the metadata of the content model and the default initial data of the model page; and select the corresponding data type, design layout and set variables in the model editor.

6. A digital medical software development method supporting medical research scenarios as claimed in claim 5, It is characterized in that In the model editor, select the appropriate data type, design layout, and set variables, including: For parameter groups / modules with complex nested structures, the parameters are wrapped by selecting the object type; then, by setting the "repeatable" variable, the parameter group / module can be generated in any quantity as required in the content model; For parameter groups / modules that need to be reused multiple times in multiple models, first, create a sub-content model and put the reused parameter groups / modules into the sub-content model; then, drag the reference type from the main content model and set the reference to the sub-model so that the parameter groups / modules in the sub-model can be reused by multiple content models.

7. A digital medical software development method supporting medical research scenarios as claimed in claim 1, It is characterized in that When connecting the content item with the primary software interface, there are three different connection methods, specifically: When a content item corresponds to a complete web page, the content item is directly stored in the software in the form of a web page through the content management system; When a model item corresponds to a web page component, the content item is referenced in the content item of the complete web page to achieve connection and display between the content item and the primary software interface; When a model entry contains more complex content and cannot be directly displayed in the form of a web page, a module capable of reading the content entry is created, and the corresponding software function is implemented according to the content in the content module.

8. A digital medical software development system that supports medical research scenarios. It is characterized in that include: The requirement acquisition module is configured to: acquire the target software requirements and select a content management system according to the acquired target software requirements; The content model building module is configured to: construct a primary software interface and establish a corresponding content model in the content management system according to the clarity and category of different requirements; classify software modules with similar content formats and generate templates through the content model; Creating a corresponding content entry on the template; The connection module is configured to connect the content item with the primary software interface, convert the content in the content item into software functions, and obtain a complete software interface.

9. A computer-readable storage medium having a program stored thereon, It is characterized in that When the program is executed by a processor, the steps in a method for developing digital medical software that supports medical research scenarios are implemented as described in any one of claims 1 to 7.

10. An electronic device comprising a memory, a processor, and a program stored in the memory and executable on the processor, It is characterized in that When the processor executes the program, the steps in the digital medical software development method supporting medical research scenarios as described in any one of claims 1-7 are implemented.

Citation Information

Patent Citations

  • Method for building content management system and device thereof

    CN101446971A

  • Nursing document designer and generating device for field of smart medical treatment

    CN112652371A

  • Medical software architecture and development method

    CN114385119A

  • Medical institution-oriented low-code platform

    CN114816380A

  • Software requirements creating and tracking system and method

    US10466979B1