Agile development platform for medical information system

Abstract

An agile development platform for a medical information system comprises a demand analysis module and a micro-application module, and the demand analysis module is composed of a feature extraction sub-module, a relation capture sub-module, an intention recognition sub-module and a demand map sub-module. According to the agile development platform for the medical information system, through plug-in type front-end application integration, multi-application and version updating rapid implementation, uniform application portal forming, continuous integration, continuous deployment and other practices and frequent testing and feedback, defects can be found and repaired in time, and the development quality is improved.

Description

Technical Field

[0001] The present invention relates to the field of intelligent medical care, and in particular to an agile development platform for medical information systems. Background Art

[0002] Existing development platforms applied in the medical field have very complex and frequently changing requirements, which makes it difficult to manage requirements during the application development process; it is also difficult to ensure the security and privacy of patient information; and it is usually necessary to integrate with multiple devices and legacy systems, which can easily lead to technical obstacles.

[0003] Application Contents

[0004] The purpose of this application is to provide an agile development platform for medical information systems to solve the technical problems described in the background technology.

[0005] An agile development platform for medical information systems, comprising a demand analysis module and a micro-application module, wherein the demand analysis module allocates medical rescue needs to predefined micro-application module categories through a neural network;

[0006] The demand analysis module consists of a feature extraction submodule, a relationship capture submodule, and an intention recognition submodule;

[0007] The feature extraction submodule extracts four key technical features from the developer's requirements, namely, technical terms, functional efficacy, development cycle, and presentation form: Identify and extract technical terminology requirement element TT1 from the developer's requirements through entity recognition (NER), and use machine learning model training to identify medical industry-specific vocabulary and abbreviation requirement element TT2 used by developers in the requirement description; extract keywords and phrases describing functional effects, and associate the requirements with specific medical rescue functional efficacy requirement elements EF through the tags or classification system in the requirement management tool for rapid retrieval and analysis; capture the development cycle requirement element DC keywords, and track and record the start and end time of the development and iteration cycle of each medical rescue module through project planning and timeline management tools; organize and classify the presentation form requirement elements PR of different medical rescue modules through an integrated document management system;

[0008] The relationship capture submodule uses the Word2Vec model to convert each word into a fixed-size vector by training the corpus; set parameters, including vector size, window size, minimum word frequency, and number of worker threads to optimize the model; convert the text into a dense vector form through the BERT model, which generates a dense vector representation that can capture contextual relationships through a multi-layer Transformer encoder; use the generated dense vectors to calculate the similarity or distance between the demand elements, thereby capturing the relationship between the demand elements; further analyze the relationship and interaction between the technical term demand element TT1, the medical industry-specific vocabulary and abbreviation demand element TT2, the functional efficacy demand element EF, the development cycle demand element DC, and the presentation form demand element PR;

[0009] The intention recognition submodule uses the trained inference model to perform inference to determine the user's instructions or query purpose and identify the medical development intention; it enhances the recognition of data annotation difficulties, the recognition of irregular user expressions, and the recognition of implicit intentions;

[0010] Micro-application modules include Vue applications, React applications, H5 applications, and traditional applications;

[0011] The micro-application module mounts the Qiankun micro-front-end technology module.

[0012] Furthermore, the development specifications for the agile development platform for medical information systems also include one or more of Typescript, Less, ESLint, Stylelint, Prettier, Vite, webpack, SPA, and Treeshaking; the interaction specifications for the agile development platform for medical information systems also include one or more of AntdUl, AntV, NaiveUI, ECharts, Wangeditor, Xlcons, and VFonts.

[0013] Furthermore, the agile development platform for medical information systems also includes a service registration center cluster, which is responsible for registration and discovery of services; service providers register their own services with the registration center when starting, and service developers obtain a list of available services from the registration center and call them.

[0014] Furthermore, the service registry cluster also includes: service providers register their own service information with the registry upon startup, including service name, IP address, and port number; service developers query the required service provider address through the registry; monitor the health status of service instances, remove unhealthy instances, and help redirect requests to other healthy service instances when service instances are unavailable; support dynamic addition and removal of service instances; provide configuration management functions, allowing service instances to obtain configuration information from the central configuration storage; support service degradation strategies, and provide alternative solutions when services are unavailable.

[0015] Furthermore, the agile development platform for medical information systems also includes an AP routing gateway unified authentication module to centrally manage user identities, control and monitor user access rights to the system, and the types of accessible resources.

[0016] Furthermore, the unified authentication module of the AP routing gateway also includes: the administrator creates, maintains and revokes user access rights in a central location; records and monitors the login activities and access behaviors of all users; supports multiple authentication methods, including one or more of username / password, OAuth, LDAP, and two-factor authentication; different users and user groups define detailed access rights to ensure that specific users and user groups can only access necessary information and functions.

[0017] Furthermore, the agile development platform for medical information systems also includes service clusters, allowing development teams to develop different services in parallel, with each service being independently deployed.

[0018] Furthermore, the service cluster also includes: each service selects the most suitable technology stack according to demand, and can independently expand each service according to the load of the service; set up a unified authentication mechanism.

[0019] Furthermore, the agile development platform for medical information systems also includes an ELK log system.

[0020] Furthermore, the ELK log system also includes: centralized management of logs of a large number of servers and applications; a full-text search engine that provides distributed multi-user capabilities; a web-based user interface to create interactive dashboards and visual charts for displaying and analyzing log data; and configuration of alarm thresholds in the dashboard. When specific situations occur in the logs, alarms are triggered and the service team and development team are notified.

[0021] Compared with the prior art, the advantages and positive effects of the present invention are: the agile development platform for medical information systems integrates front-end applications in a "plug-in" style, quickly implements multi-application and version updates, forms a unified application portal, and practices such as continuous integration and continuous deployment, as well as frequent testing and feedback, which helps to timely discover and fix defects and improve development quality. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] In order to more clearly illustrate the technical solution of the present invention, the following briefly introduces the drawings used in the description of the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work:

[0023] Figure 1 The present invention is a schematic diagram of the front-end architecture of an embodiment of an agile development platform for medical information systems.

[0024] Figure 2 The present invention is a schematic diagram of the back-end architecture of an embodiment of an agile development platform for medical information systems.

[0025] Figure 3 The present invention is a schematic diagram of a single sign-on process for an embodiment of an agile development platform for a medical information system.

[0026] Figure 4 The present invention is a schematic diagram of the data persistence process of an embodiment of an agile development platform for medical information systems.

[0027] Figure 5 The present invention is an example of a portal framework interface for an agile development platform for medical information systems.

[0028] Figure 6 This is Example 2 of a portal framework interface for an implementation of an agile development platform for a medical information system.

[0029] Figure 7 This is Example 3 of a portal framework interface for an implementation of an agile development platform for a medical information system. DETAILED DESCRIPTION

[0030] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to represent the only configuration in which the concepts described herein may be practiced. The detailed description includes specific details for the purpose of providing a thorough understanding of the various concepts. However, it will be apparent to those skilled in the art that these concepts may be practiced without these specific details. In some instances, a plurality of well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0031] Several aspects of telecommunication systems will now be presented with reference to various apparatus and methods. These apparatus and methods will be described in the following detailed description and illustrated in the accompanying drawings by various blocks, components, circuits, processes, algorithms, etc. (collectively referred to as "elements"). These elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.

[0032] By way of example, an element, or any part of an element, or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gated logic, discrete hardware circuits, and other suitable hardware configured to perform various functionalities described throughout the present disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted as meaning instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, processes, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description languages, or other.

[0033] Accordingly, in one or more example embodiments, the described functions may be implemented in hardware, software, or any combination thereof. If implemented in software, the functions may be stored on a computer-readable medium, or encoded as one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. Storage media may be any available medium accessible by a computer. By way of example and not limitation, such computer-readable media may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the above types, or any other medium that may be used to store computer executable code in the form of instructions or data structures accessible by a computer.

[0034] As the instruction manual Figure 1-7 As shown:

[0035] An agile development platform for medical information systems, comprising a demand analysis module and a micro-application module, wherein the demand analysis module allocates medical rescue needs to predefined micro-application module categories through a neural network;

[0036] The demand analysis module consists of a feature extraction submodule, a relationship capture submodule, and an intention recognition submodule;

[0037] The feature extraction submodule extracts four key technical features from the developer's requirements, namely, technical terms, functional efficacy, development cycle, and presentation form: Identify and extract technical terminology requirement elements TT1 from the developer's requirements through entity recognition (NER). These terms usually include specific programming languages, frameworks, libraries, tools or technical concepts, etc. At the same time, use machine learning models to train and identify medical industry-specific vocabulary and abbreviation requirement elements TT2 used by developers in the requirement description; extract keywords and phrases describing functional effects, which usually involve user stories, use case descriptions or functional points, and associate requirements with specific medical rescue functional efficacy requirement elements EF through tags or classification systems in the requirement management tool for rapid retrieval and analysis; capture the development cycle requirement element DC keywords, and track and record the start and end time of the development and iteration cycle of each medical rescue module through project planning and timeline management tools; organize and classify the presentation form requirement elements PR of different medical rescue modules through an integrated document management system;

[0038] The relationship capture submodule uses the Word2Vec model to convert each word into a fixed-size vector by training the corpus; set parameters, including vector size (vector_size), window size (window_size), minimum word frequency (min_count), and number of workers (workers) to optimize the model; convert the text into a dense vector form through the BERT model, which generates a dense vector representation that can capture contextual relationships through a multi-layer Transformer encoder; use the generated dense vector to calculate the similarity or distance between the demand elements, thereby capturing the relationship between the demand elements. For example, cosine similarity can be used to measure the similarity between two vectors. Through operations between vectors, such as vector addition and dot product, the relationship and interaction between the technical term demand element TT1, the medical industry-specific vocabulary and abbreviation demand element TT2, the functional efficacy demand element EF, the development cycle demand element DC, and the presentation form demand element PR are further analyzed;

[0039] The intention recognition submodule uses the trained inference model to perform inference to determine the user's instructions or query purpose and identify the medical development intention; it enhances the functions of identifying data annotation difficulties, identifying irregular user expressions, and identifying implicit intentions;

[0040] Micro-application modules include Vue applications, React applications, H5 applications, and traditional applications;

[0041] The micro-application module mounts the Qiankun micro-front-end technology module. The Qiankun micro-front-end technology module mounts dictionary management, configuration management, role management, menu management, department management, user management, personnel management, report management, message notification, and system monitoring.

[0042] In this embodiment, the agile development platform for medical information systems integrates front-end applications in a "plug-in" style, quickly implements multiple applications and version updates, forms a unified application portal, and practices such as continuous integration and continuous deployment, as well as frequent testing and feedback, which helps to timely discover and fix defects and improve development quality.

[0043] Specifically, the development specifications for the agile development platform of medical information systems also include: Typescript, Less, ESLint, Stylelint, Prettier, Vite, webpack, SPA, and Treeshaking. Improve the readability and maintainability of the code and reduce runtime errors by defining interfaces, classes, and types; maintain the consistency of style and improve the maintainability of style code by using variables and mixins; ensure code quality and avoid potential errors and inconsistent coding styles by customizing rule sets; maintain the consistency and maintainability of style by setting rules for style code; reduce unnecessary formatting disputes and improve code readability by unifying code formats; implement code segmentation, lazy loading, optimize resources, etc. to improve application performance and loading speed; provide a smoother user experience, reduce page loading time, and improve application interactivity; reduce unnecessary code and optimize application loading time and performance.

[0044] Specifically, the interaction specifications for the agile development platform for medical information systems also include: AntdUl, AntV, NaiveUI, ECharts, Wangeditor, Xlcons, and VFonts. It ensures the consistency and accessibility of components, provides clear feedback and guidance, and enables users to have a consistent experience when using the application; provides a set of interaction design principles, including data display, user operation feedback, etc., to ensure the intuitiveness and ease of use of users when exploring and analyzing data; and ensures the consistency of text display effects on different devices and platforms.

[0045] Specifically, the agile development platform for medical information systems also includes a service registration center cluster, which is responsible for service registration and discovery. Service providers register their services with the registration center at startup, and service developers obtain the list of available services from the registration center and call them. Through cluster deployment, the registration center itself has high availability to avoid single point failures. High availability and strict service discovery mechanisms are used to ensure the continuity and reliability of critical medical services.

[0046] Specifically, the service registry cluster also includes: the service provider registers its own service information with the registry at startup, including the service name, IP address, port number, etc. The service developer queries the required service provider address through the registry so that the service can be called; used in conjunction with the load balancing strategy to distribute requests among multiple service instances; monitors the health status of service instances, removes unhealthy instances, ensures that only healthy services are called by developers, and helps redirect requests to other healthy service instances when a service instance is unavailable; supports dynamic addition and removal of service instances to achieve elastic scaling of services; provides configuration management capabilities, allowing service instances to obtain configuration information from the central configuration storage; supports service degradation strategies and provides alternative solutions when services are unavailable.

[0047] Specifically, the agile development platform for medical information systems also includes a unified authentication module for AP routing gateways, which centrally manages user identities, controls and monitors user access rights to the system, and the types of accessible resources. This ensures that all users accessing the platform are authenticated, protects patients' health records and other sensitive data, and ensures that medical staff can access the required information efficiently and securely, ensures compliance with relevant laws and regulations, and improves the security and privacy of medical information.

[0048] Specifically, the unified authentication module of the AP routing gateway also includes: administrators create, maintain and revoke user access rights in a central location to simplify user management and reduce management costs; record and monitor all users' login activities and access behaviors, which is helpful for security audits and accident investigations; support multiple authentication methods, such as username / password, OAuth, LDAP, two-factor authentication, etc., to adapt to different security requirements and user preferences; used in combination with single sign-on technology, allowing users to switch seamlessly between different applications and services without repeated authentication; different users and user groups define detailed access rights to ensure that specific users and user groups can only access necessary information and functions.

[0049] Specific steps for single sign-on for the medical information system agile development platform:

[0050] The third-party application page selects the single sign-on method ticktype, and the third-party token data is transmitted to the front-end single sign-on page; the front-end single sign-on page enters the back-end single sign-on verification; the back-end single sign-on verification performs third-party token verification with the third-party application service, and the third-party application service transmits the verification result to the back-end single sign-on verification; if the verification passes, it will automatically log in and generate access_token identification data to transmit to the front-end single sign-on page. If the verification fails, the access_token identification data will not be generated; the front-end single sign-on page detects the existence of access_token identification data and jumps to the portal.

[0051] Specifically, the agile development platform for medical information systems also includes service clusters, which allow development teams to develop different services in parallel. Each service can be deployed independently, which speeds up development and delivery. The isolation between services ensures that the failure of a single service will not affect the entire system, thereby improving system stability.

[0052] Specifically, the service cluster also includes: each service can choose the most suitable technology stack according to its needs, and each service can be independently expanded according to the load of the service to improve the overall elasticity and processing capacity of the system; a unified authentication mechanism is set up to ensure the security and compliance of all services.

[0053] Specifically, the agile development platform for medical information systems also includes the ELK log system, which uses a combination of Elasticsearch, Logstash, and Kibana tools to collect, process, store, and visualize logs.

[0054] Specifically, the ELK log system also includes: centralized management of logs of a large number of servers and applications, simplifying the log collection and storage process. Provide a full-text search engine with distributed multi-user capabilities to achieve real-time search and analysis of logs; have a web-based user interface to create interactive dashboards and visual charts for displaying and analyzing log data; configure alarm thresholds in the dashboard, and when specific situations appear in the logs, trigger alarms and notify the service team and development team; quickly locate problems and faults to improve operation and maintenance efficiency.

[0055] Specifically, the agile development platform for medical information systems also includes a task management module to assign tasks and responsibilities, so that team members can clearly understand their respective job responsibilities and progress, and promote teamwork. This helps the development team to deliver value efficiently, respond to changes more quickly, and continuously improve product quality.

[0056] Specifically, the task management module also includes: identifying the team's workload and bottlenecks, identifying the team's planned sprints, ongoing tasks, allocating resources and adjusting priorities; development team members independently decide the order of work based on task priorities and dependencies; after changes in requirements, the task management module quickly reallocates tasks and adjusts plans; tracks task progress, generates progress reports, and helps teams and stakeholders understand project status; supports remote access to promote development work for distributed teams or teams that need to work remotely; integrates version control systems, continuous integration / continuous deployment and other tools.

[0057] Specifically, the agile development platform for medical information systems also includes a relational database cluster, which distributes data and loads among multiple servers. If one server fails, other servers will take over its work, thereby ensuring the continuous operation of the system and improving the system's availability.

[0058] Specifically, the associative database cluster also includes: automatic detection and processing of server failures. When a server fails, the cluster can automatically remove it from the cluster and migrate its data to other servers to ensure data integrity and system continuity; set up data replication and transaction synchronization mechanisms. When the data of one node changes, the data of other nodes will also be updated accordingly to ensure that the data of all nodes is always consistent; distribute workloads among multiple nodes to achieve load balancing and improve the overall performance and response speed of the system; add new server nodes to expand the processing capacity of the cluster; set up data backup areas, and in the event of a catastrophic failure, restore data from backups to protect data from accidental deletion, hardware failures or natural disasters, thereby improving disaster recovery capabilities; have automated management tools to reduce operation and maintenance costs and complexity and improve management efficiency.

[0059] Specifically, the data persistence steps for the medical information system agile development platform are:

[0060] API call; permission judgment, if there is a permission exception, feedback the API call result, if no permission exception is detected, perform Sql injection judgment; if there is an injection exception, feedback the API call result, if no injection exception is detected, automatically fill in the necessary fields such as updateBy, updateTime, createBy, createTime; perform mybatis execution; if there is an execution exception, roll back the transaction and feedback the API call result, if no execution exception is detected, commit the transaction and feedback the result.

[0061] One or more specific embodiments of the present disclosure are described herein. These described embodiments are examples of the currently disclosed technology. In addition, in order to provide a concise description of these embodiments, not all features of the actual embodiments may be described in the specification. It should be understood that in the development of any such actual implementation, as in any engineering or design project, many implementation-specific decisions will be made to achieve the developer's specific goals, such as complying with system-related and business-related constraints, which may vary from embodiment to embodiment. In addition, it should be understood that such development work may be complex and time-consuming, but it is still a routine work of design, production and manufacturing for ordinary technicians who benefit from the present disclosure.

[0062] In addition, it should be understood that reference to "one embodiment" or "an embodiment" of the present disclosure is not intended to be interpreted as excluding the existence of additional embodiments that also include the listed features. For example, any element described with respect to the embodiments herein can be combined with any element of any other embodiment described herein. The numbers, percentages, ratios, or other values ​​described herein are intended to include the value, as well as other values ​​that are "about" or "approximately" the value, as will be understood by those of ordinary skill in the art covered by the embodiments of the present disclosure. Therefore, the values ​​should be interpreted broadly enough to cover values ​​that are at least close enough to the values ​​to perform the desired function or achieve the desired result.

[0063] Those of ordinary skill in the art will recognize that, in light of the present disclosure, equivalent structures do not depart from the spirit and scope of the present disclosure, and that various changes, substitutions, and modifications may be made to the embodiments disclosed herein without departing from the spirit and scope of the present disclosure. Equivalent structures including functional "device plus function" clauses are intended to cover structures described herein as performing the functions described, including structural equivalents that operate in the same manner and equivalent structures that provide the same functions. It is the express intent of the applicant not to invoke "device plus function" or other functional claims with respect to any claim, except for claims in which the term "device for..." appears together with the relevant function. Every addition, deletion, and modification to the embodiments that falls within the meaning and scope of the claims will be included in the claims.

[0064] Without departing from its spirit or characteristics, the present disclosure may be implemented in other specific forms. The described embodiments are considered to be illustrative rather than restrictive. Therefore, the scope of the present disclosure is represented by the appended claims rather than by the foregoing description. Changes within the meaning and scope of the equivalent of the claims will be included within their scope.

Claims

1. An agile development platform for medical information systems, characterized in that: It includes a demand analysis module and a micro-application module. The demand analysis module allocates medical rescue needs to predefined micro-application module categories through a neural network; The demand analysis module consists of a feature extraction submodule, a relationship capture submodule, and an intention recognition submodule; The feature extraction submodule extracts four key technical features from the developer's requirements, namely, technical terms, functional efficacy, development cycle, and presentation form: Identify and extract technical terminology requirement element TT1 from the developer's requirements through entity recognition (NER), and use machine learning model training to identify medical industry-specific vocabulary and abbreviation requirement element TT2 used by developers in the requirement description; extract keywords and phrases describing functional effects, and associate the requirements with specific medical rescue functional efficacy requirement elements EF through the tags or classification system in the requirement management tool for rapid retrieval and analysis; capture the development cycle requirement element DC keywords, and track and record the start and end time of the development and iteration cycle of each medical rescue module through project planning and timeline management tools; organize and classify the presentation form requirement elements PR of different medical rescue modules through an integrated document management system; The relationship capture submodule uses the Word2Vec model to convert each word into a fixed-size vector by training the corpus; set parameters, including vector size, window size, minimum word frequency, and number of worker threads to optimize the model; convert the text into a dense vector form through the BERT model, which generates a dense vector representation that can capture contextual relationships through a multi-layer Transformer encoder; use the generated dense vectors to calculate the similarity or distance between the demand elements, thereby capturing the relationship between the demand elements; further analyze the relationship and interaction between the technical term demand element TT1, the medical industry-specific vocabulary and abbreviation demand element TT2, the functional efficacy demand element EF, the development cycle demand element DC, and the presentation form demand element PR; The intention recognition submodule uses the trained inference model to perform inference to determine the user's instructions or query purpose and identify the medical development intention; it enhances the recognition of data annotation difficulties, the recognition of irregular user expressions, and the recognition of implicit intentions; Micro-application modules include Vue applications, React applications, H5 applications, and traditional applications; The micro-application module mounts the Qiankun micro-front-end technology module.

2. The agile development platform for medical information systems according to claim 1, characterized in that: The development specifications for the agile development platform for medical information systems also include one or more of Typescript, Less, ESLint, Stylelint, Prettier, V ite, webpack, SPA, and Treeshaking; the interaction specifications for the agile development platform for medical information systems also include one or more of AntdUl, AntV, NaiveUI, ECharts, Wangeditor, Xlcons, and VFonts.

3. The agile development platform for medical information systems according to any one of claims 1-2, characterized in that: It also includes a service registry cluster, which is responsible for service registration and discovery. Service providers register their services with the registry at startup, and service developers obtain a list of available services from the registry and make calls.

4. The agile development platform for medical information systems according to claim 3, characterized in that: The service registry cluster also includes: service providers register their service information with the registry at startup, including service name, IP address, and port number; service developers query the required service provider address through the registry; monitor the health status of service instances, remove unhealthy instances, and help redirect requests to other healthy service instances when service instances are unavailable; support dynamic addition and removal of service instances; provide configuration management functions, allowing service instances to obtain configuration information from the central configuration storage; support service degradation strategies, and provide alternative solutions when services are unavailable.

5. The agile development platform for medical information systems according to any one of claims 1-2, characterized in that: It also includes a unified authentication module for AP routing gateways to centrally manage user identities, control and monitor user access rights to the system, and the types of accessible resources.

6. The agile development platform for medical information systems according to claim 5, characterized in that: The AP routing gateway unified authentication module also includes: administrators create, maintain and revoke user access rights in a central location; record and monitor all user login activities and access behaviors; support multiple authentication methods, including username / password, OAuth, LDAP, and two-factor authentication. Detailed access rights are defined for different users and user groups to ensure that specific users and user groups can only access necessary information and functions.

7. The agile development platform for medical information systems according to any one of claims 1-2, characterized in that: It also includes service clusters, which allow development teams to develop different services in parallel, with each service deployed independently.

8. The agile development platform for medical information systems according to claim 7, characterized in that: The service cluster also includes: each service selects the most suitable technology stack according to needs, and can independently expand each service according to the load of the service; set up a unified authentication mechanism.

9. The agile development platform for medical information systems according to any one of claims 1-2, characterized in that: Also includes the ELK logging system.

10. The agile development platform for medical information systems according to claim 9, characterized in that: The ELK log system also includes: centralized management of logs of a large number of servers and applications; a full-text search engine that provides distributed multi-user capabilities; a web-based user interface to create interactive dashboards and visual charts for displaying and analyzing log data; and alarm thresholds configured in the dashboard. When specific situations occur in the logs, alarms are triggered and the service team and development team are notified.

Images