An agile development platform for medical information systems

Abstract

A rapid development platform for medical information systems, comprising: a requirements analysis module, a micro-application module. The requirements analysis module consists of a feature extraction sub-module, a relationship capture sub-module, an intent recognition sub-module, and a requirements graph sub-module. The rapid development platform for medical information systems enables rapid implementation of multi-application and version updates through "plug-in" front-end application integration, forms a unified application portal, practices such as continuous integration and continuous deployment, and frequent testing and feedback, which help to promptly detect and fix defects and improve development quality.

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 they usually need to be integrated 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 sub-module uses the Word2Vec model to convert each word into a vector of a fixed size through a training corpus; sets parameters including vector size, window size, minimum word frequency, and number of worker threads to optimize the model; converts the text into a dense vector form through the BERT model, and the BERT model generates a dense vector representation that can capture context relationships through multiple layers of Transformer encoders; uses the generated dense vectors to calculate the similarity or distance between requirement elements, thereby capturing the relationships between requirement elements; further analyzes the relationships and interactions between the technical term requirement element TT1, the medical industry-specific vocabulary and abbreviation requirement element TT2, the functional efficacy requirement element EF, the development cycle requirement element DC, and the presentation form requirement element PR.

[0009] The intent recognition sub-module uses a trained inference model for inference to determine the user's instruction or query purpose and identify the medical development intent; enhances the functions of difficult data annotation recognition, non-standard user expression recognition, and implicit intent recognition.

[0010] The micro-application module includes Vue applications, React applications, H5 applications, and traditional applications.

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

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

[0013] Furthermore, the medical information system agile development platform also includes a service registry cluster responsible for service registration and discovery; service providers register their services with the registry when starting up, and service developers obtain the list of available services from the registry and make calls.

[0014] Furthermore, the service registry cluster also includes: when a service provider starts up, it registers its service information with the registry, including the service name, IP address, and port number; service developers query the addresses of required service providers through the registry; monitor the health status of service instances, remove unhealthy instances, and when a service instance becomes unavailable, help redirect requests to other healthy service instances; support the dynamic addition and removal of service instances; provide a configuration management function that allows service instances to obtain configuration information from the central configuration store; support service degradation policies and provide alternative solutions when the service is unavailable.

[0015] Furthermore, the agile development platform for the medical information system also includes an AP routing gateway unified authentication module, which centrally manages user identities, controls and monitors the permissions of users to access the system, and the types of accessible resources.

[0016] Furthermore, the AP routing gateway unified authentication module also includes: administrators create, maintain, and revoke user access permissions in a central location; record and monitor all user login activities and access behaviors; support multiple authentication methods, including one or more of username / password, OAuth, LDAP, and two-factor authentication; define detailed access permissions for different users and user groups to ensure that specific users and user groups can only access necessary information and functions.

[0017] Furthermore, the agile development platform for the medical information system also includes a service cluster that allows development teams to develop different services in parallel, with each service deployed independently.

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

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

[0020] Furthermore, the ELK logging system also includes: centrally manage the logs of a large number of servers and applications; provide a full-text search engine with distributed multi-user capabilities; have a web-based user interface to create interactive dashboards and visualization charts for displaying and analyzing log data; configure alarm thresholds in the dashboard, and when specific situations occur in the logs, trigger alarms and notify the service team and development team.

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

[0022] To more clearly illustrate the technical solution of the present invention, the following will briefly introduce the accompanying drawings used in the description of the embodiments of the present invention. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings:

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

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

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

[0026] Figure 4 It is a schematic diagram of the data persistence process of an embodiment of an agile development platform for a medical information system.

[0027] Figure 5 It is an example one of the portal framework interface of an embodiment of an agile development platform for a medical information system.

[0028] Figure 6 It is an example two of the portal framework interface of an embodiment of an agile development platform for a medical information system.

[0029] Figure 7 It is an example three of the portal framework interface of an embodiment of an agile development platform for a medical information system. Detailed implementation manners

[0030] The following detailed description presented 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 can be practiced. For the purpose of providing a thorough understanding of the various concepts, the detailed description includes specific details. However, it will be apparent to those skilled in the art that these concepts can be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form to avoid obscuring such concepts.

[0031] Aspects of a telecommunications system will now be presented with reference to various apparatuses and methods. These apparatuses 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 can be implemented using electronic hardware, computer software, or any combination thereof. Whether such elements are implemented as hardware or software depends upon the particular application and 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 a microprocessor, a microcontroller, a graphics processing unit (GPU), a central processing unit (CPU), an application processor, a digital signal processor (DSP), a reduced instruction set computing (RISC) processor, a system on a chip (SoC), a baseband processor, a field programmable gate array (FPGA), a programmable logic device (PLD), a state machine, gated logic, discrete hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in the processing system can execute software. Software should be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software components, applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

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

[0034] As shown in the accompanying Figures 1-7 specification:

[0035] A medical information system agile development platform includes a requirements analysis module and a micro-application module. The requirements analysis module distributes medical rescue requirements to predefined micro-application module categories through a neural network.

[0036] The requirements analysis module consists of a feature extraction sub-module, a relationship capture sub-module, and an intent recognition sub-module;

[0037] The feature extraction sub-module extracts four key technical features from the developer's requirements: technical terms, functional effects, development cycle, and presentation form. Through named entity recognition (NER), it identifies and extracts the technical term requirement elements TT1 in the developer's requirements, which usually include specific programming languages, frameworks, libraries, tools, or technical concepts. At the same time, it uses a machine learning model to train and recognize the medical industry-specific vocabulary and abbreviation requirement elements TT2 used by the developer in the requirement description. It extracts the keywords and phrases describing the functional effects, which usually involve user stories, use case descriptions, or functional points, and associates the requirements with the specific medical rescue functional effect requirement elements EF through the tags or classification system in the requirements management tool for quick retrieval and analysis. It captures the keywords of the development cycle requirement elements DC and tracks and records the start and end times of the development and iteration cycles of each medical rescue module through the project planning and timeline management tool. It organizes and classifies the presentation form requirement elements PR of different medical rescue modules through the integrated document management system;

[0038] The relationship capture sub-module uses the Word2Vec model to convert each word into a fixed-size vector through the training corpus. It sets parameters, including vector size (vector_size), window size (window_size), minimum word frequency (min_count), and number of worker threads (workers) to optimize the model. Through the BERT model, it converts the text into a dense vector form. The BERT model generates a dense vector representation that can capture context relationships through multiple layers of Transformer encoders. Using the generated dense vectors, it calculates the similarity or distance between requirement elements to capture the relationships between requirement elements. For example, it can use cosine similarity to measure the similarity between two vectors, and through operations between vectors, such as vector addition and dot product, it further analyzes the relationships and interactions between the technical term requirement elements TT1, medical industry-specific vocabulary and abbreviation requirement elements TT2, functional effect requirement elements EF, development cycle requirement elements DC, and presentation form requirement elements PR;

[0039] The intent recognition sub-module uses the trained inference model for inference to determine the user's instruction or query purpose and identify the medical development intent. It enhances functions such as difficult data annotation recognition, non-standard user expression recognition, and implicit intent recognition;

[0040] The micro-application module includes Vue applications, React applications, H5 applications, and traditional applications;

[0041] The micro-application module mounts the Qiankun micro-frontend technology module, and the Qiankun micro-frontend 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 the medical information system realizes the integration of multiple applications and version updates quickly through the "plugin"-style front-end application integration, forms a unified application portal, and practices such as continuous integration and continuous deployment, as well as frequent testing and feedback, help to discover and fix defects in a timely manner and improve the development quality.

[0043] Specifically, the development specifications for the agile development platform of the medical information system also include: Typescript, Less, ESLint, Stylelint, Prettier, Vite, webpack, SPA, Treeshaking. By defining interfaces, classes, and types, it improves the readability and maintainability of the code and reduces runtime errors; by using variables and mixins, it maintains the consistency of styles and improves the maintainability of style code; by customizing the rule set, it ensures the code quality and avoids potential errors and inconsistent coding styles; by setting the rules for style code, it maintains the consistency and maintainability of styles; by unifying the code format, it reduces unnecessary format arguments and improves the readability of the code; it realizes code splitting, lazy loading, resource optimization, etc., improves the performance and loading speed of the application; provides a smoother user experience, reduces the page loading time, and improves the interactivity of the application; reduces unnecessary code and optimizes the loading time and performance of the application.

[0044] Specifically, the interaction specifications for the agile development platform of the medical information system also include: AntdUl, AntV, NaiveUI, ECharts, Wangeditor, Xlcons, 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; it provides a set of interaction design principles, including data display, user operation feedback, etc., and ensures the intuitiveness and ease of use of users when exploring and analyzing data; it ensures that the text display effects are consistent on different devices and platforms.

[0045] Specifically, the agile development platform for the medical information system also includes a service registry cluster, which is responsible for service registration and discovery. Service providers register their services with the registry when starting up, and service developers obtain the list of available services from the registry and make calls. Through cluster deployment, the registry itself has high availability and avoids single-point failures; through high availability and a strict service discovery mechanism, it ensures the continuity and reliability of critical medical services.

[0046] Specifically, the service registry cluster also includes: when a service provider starts up, it registers its service information with the registry, including service name, IP address, port number, etc. Service developers can query the addresses of required service providers through the registry, so as to be able to call the services; it is used in combination with a load balancing strategy to distribute requests among multiple service instances; it monitors the health status of service instances, removes unhealthy instances, and ensures that only healthy services are called by developers. When a service instance is unavailable, it helps redirect requests to other healthy service instances; it supports the dynamic addition and removal of service instances to achieve elastic scaling of services; it provides a configuration management function that allows service instances to obtain configuration information from a central configuration store; it supports service degradation strategies and provides alternative solutions when services are unavailable.

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

[0048] Specifically, the AP routing gateway unified authentication module also includes: administrators can create, maintain, and revoke user access permissions at a central location, simplifying user management and reducing management costs; it records and monitors all users' login activities and access behaviors, which helps with security audits and incident investigations; it supports multiple authentication methods, such as username / password, OAuth, LDAP, two-factor authentication, etc., to meet different security requirements and user preferences; it is used in combination with single sign-on technology, allowing users to seamlessly switch between different applications and services without having to re-authenticate; detailed access permissions are defined for different users and user groups to ensure that specific users and user groups can only access necessary information and functions.

[0049] Specifically, the steps for single sign-on of the agile development platform for the medical information system are as follows:

[0050] On the third-party application page, select the single sign-on method ticktype, and transmit the third-party token data 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 automatically logs in and generates the access_token identification data and transmits it to the front-end single sign-on page. If the verification fails, the access_token identification data is not generated; when the front-end single sign-on page detects the existence of the access_token identification data, it jumps to the portal.

[0051] Specifically, the agile development platform for the medical information system also includes a service cluster, which allows the development team to develop different services in parallel. Each service can be independently deployed, accelerating the development and delivery speed. The isolation between services ensures that the failure of a single service does not affect the entire system, improving the system's stability.

[0052] Specifically, the service cluster also includes: each service can select the most suitable technology stack according to requirements, and each service can be independently scaled according to its load, improving 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 the medical information system also includes an ELK logging system, which uses a combination of Elasticsearch, Logstash, and Kibana tools to achieve log collection, processing, storage, and visualization.

[0054] Specifically, the ELK logging system also includes: centrally managing the logs of a large number of servers and applications, simplifying the log collection and storage process. Providing a full-text search engine with distributed multi-user capabilities to achieve real-time search and analysis of logs; having a web-based user interface to create interactive dashboards and visualization charts for displaying and analyzing log data; configuring alarm thresholds in the dashboard to trigger an alarm and notify the service team and development team when specific situations occur in the logs; quickly locating problems and faults, improving the operation and maintenance efficiency.

[0055] Specifically, the agile development platform for the medical information system also includes a task management module, which assigns tasks and responsibilities. Team members can clearly understand their respective job responsibilities and progress, promoting teamwork. It helps the development team deliver value efficiently, respond to changes faster, and continuously improve product quality.

[0056] Specifically, the task management module also includes: identifying the workload and bottlenecks of the team, identifying the tasks that the team is planning and executing sprints on, allocating resources and adjusting priorities; development team members independently determine the work order based on the priority and dependencies of tasks; after the requirements change, the task management module quickly reassigns tasks and adjusts the plan; tracking task progress and generating progress reports to help the team and stakeholders understand the project status; supporting remote access to facilitate the development work of distributed teams or teams that need to work remotely; integrating tools such as version control systems and continuous integration / continuous deployment.

[0057] Specifically, the agile development platform for the medical information system further includes a relational database cluster. By distributing data and load among multiple servers, if one server fails, other servers will take over its work to ensure the continuous operation of the system and improve the availability of the system.

[0058] Specifically, the relational database cluster further includes: automatically detecting and handling 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; setting up data replication and transaction synchronization mechanisms. When the data of one node changes, the data of other nodes will be updated accordingly to ensure that the data of all nodes always remains consistent; distributing the workload among multiple nodes to achieve load balancing and improve the overall performance and response speed of the system; being able to add new server nodes to expand the processing capacity of the cluster; setting up a data backup area. In case of a catastrophic failure, recover data from the backup to protect the data from accidental deletion, hardware failures, natural disasters, etc., and enhance the disaster recovery ability; having automated management tools to reduce operation and maintenance costs and complexity and improve management efficiency.

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

[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 necessary fields such as updateBy, updateTime, createBy, createTime, etc.; 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] This document describes one or more specific embodiments of the present disclosure. These described embodiments are examples of the currently disclosed technology. In addition, 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 embodiment-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. Moreover, it should be understood that such development work may be complex and time-consuming, but it is still routine work for those of ordinary skill in the art who benefit from the present disclosure in terms of design, fabrication, and manufacturing.

[0062] In addition, it should be understood that references to "one embodiment" or "an embodiment" of the present disclosure are not to be construed as excluding the existence of additional embodiments that also incorporate the recited features. For example, any element described with respect to an embodiment herein can be combined with any element of any other embodiment described herein. The numbers, percentages, ratios, or other values recited herein are intended to include that value, as well as other values that are "about" or "approximately" the recited value, as would be understood by a person of ordinary skill in the art as encompassed by embodiments of the present disclosure. Accordingly, the recited values should be interpreted to be broad enough to encompass at least values that are sufficiently close to the recited value to perform the desired function or achieve the desired result.

[0063] A person of ordinary skill in the art should recognize that, given the present disclosure, equivalent structures do not depart from the spirit and scope of the present disclosure, and various changes, substitutions, and modifications can be made to the embodiments disclosed herein without departing from the spirit and scope of the present disclosure. Equivalent structures that include functional "means-plus-function" clauses are intended to cover structures described herein as performing the recited function, including structural equivalents that operate in the same manner and equivalent structures that provide the same function. The applicant's express intention is not to invoke "means-plus-function" or other functional recitations for any claim, except for claims in which the term "means for..." appears in conjunction with a related function. Every addition, deletion, and modification to an embodiment 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 embodied in other specific forms. The described embodiments are considered to be illustrative rather than restrictive. Accordingly, 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 equivalents of the claims will be included within its scope.

Claims

1. A medical information system agile development platform, characterized in that It includes a requirements analysis module and a micro-application module. The requirements analysis module distributes medical rescue requirements to predefined micro-application module categories through a neural network. The requirements analysis module consists of a feature extraction sub-module, a relationship capture sub-module, and an intent recognition sub-module. The feature extraction sub-module extracts four key technical features from the developer's requirements: technical terms, functional efficacy, development cycle, and presentation form. Through entity recognition, it identifies and extracts the technical term requirement element TT1 in the developer's requirements. At the same time, it uses a machine learning model to train and identify the medical industry-specific vocabulary and abbreviation requirement element TT2 used by the developer in the requirement description. It extracts keywords and phrases describing the functional effects and associates the requirements with specific medical rescue functional efficacy requirement elements EF through the tags or classification system in the requirements management tool for quick retrieval and analysis. It captures the keywords of the development cycle requirement element DC and tracks and records the start and end times of the development and iteration cycles of each medical rescue module through the project planning and timeline management tool. It organizes and classifies the presentation form requirement elements PR of different medical rescue modules through the integrated document management system. The relationship capture sub-module uses the Word2Vec model to convert each word into a fixed-size vector through a training corpus. It sets parameters, including vector size, window size, minimum word frequency, and number of worker threads, to optimize the model. Through the BERT model, it converts the text into a dense vector form. The BERT model generates a dense vector representation that can capture context relationships through multiple layers of Transformer encoders. It uses the generated dense vectors to calculate the similarity or distance between requirement elements, thereby capturing the relationships between requirement elements. It further analyzes the relationships and interactions among the technical term requirement element TT1, the medical industry-specific vocabulary and abbreviation requirement element TT2, the functional efficacy requirement element EF, the development cycle requirement element DC, and the presentation form requirement element PR. The intent recognition sub-module uses a trained inference model for inference to determine the user's instruction or query purpose and identify the medical development intent. It enhances the functions of difficult data annotation recognition, non-standard user expression recognition, and implicit intent recognition. The micro-application module includes Vue applications, React applications, H5 applications, and traditional applications. The micro-application module is mounted with the Qiankun micro-frontend technology module.

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

3. The agile development platform for a medical information system 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 when starting up, and service developers obtain the list of available services from the registry and make calls.

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

5. The agile development platform for a medical information system according to any one of claims 1-2, characterized in that, It also includes an AP routing gateway unified authentication module, which centrally manages user identities, controls and monitors the permissions of users to access the system, as well as the types of accessible resources.

6. The agile development platform for a medical information system according to claim 5, characterized in that The AP routing gateway unified authentication module also includes: administrators create, maintain, and revoke user access permissions in a central location; record and monitor all user login activities and access behaviors; support multiple authentication methods, including one or more of username / password, OAuth, LDAP, and two-factor authentication; define detailed access permissions 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 a medical information system according to any one of claims 1-2, characterized in that, It also includes a service cluster, which allows development teams to develop different services in parallel, with each service deployed independently.

8. The agile development platform for a medical information system according to claim 7, wherein The service cluster also includes: each service selects the most suitable technology stack according to requirements and can independently scale each service according to the load of the service; set up a unified authentication mechanism.

9. The agile development platform for a medical information system according to any one of claims 1-2, characterized in that, It also includes an ELK logging system.

10. The agile development platform for a medical information system according to claim 9, characterized in that, The ELK logging system also includes: centrally manage the logs of a large number of servers and applications; provide a full-text search engine with distributed multi-user capabilities; have a web-based user interface to create interactive dashboards and visualization charts for displaying and analyzing log data; configure alarm thresholds in the dashboard, and when specific situations occur in the logs, trigger alarms and notify the service team and the development team.

Images