Software development method based on industry domain B end and clinical research and scientific research management platform thereof

Abstract

The invention discloses a software development method based on an industry domain B end and a clinical research and scientific research management platform thereof on a development framework of a digital base and a non-business function state, and the method comprises the following steps: S1, creating software which is managed by the B end and executes specific functions, and setting basic management parameters; s2, creating an industry domain system D corresponding to software development; s3, creating a corresponding software domain scene architecture system X formed based on the industry domain D; s4, constructing a global framework based on the software domain scene architecture system X; s5, constructing a complex business level based on a software global framework page; s6, creating a page layout based on the complex business hierarchy; s7, creating general pages and special pages such as business forms, tables, cards and lists based on the page layout; s8, creating a business process based on business forms, tables, cards, listing and other use pages and special pages; and S9, an auditing step of creating general pages and special pages such as business forms, tables, cards and lists based on the business process.

Description

Technical Field

[0001] This invention relates to the field of computer information systems, and more specifically, to an industry-domain B2B software development method and its clinical research management platform. Background Technology

[0002] B2B software development typically includes stages such as requirements analysis, design, coding, testing, delivery, and maintenance. However, facing constantly evolving business needs from B2B clients, developers must frequently modify the code, leading to high difficulty and risk in B2B software development. Development often becomes a repetitive cycle within these six stages, making it difficult to complete. Furthermore, existing B2B software is generally developed based on relatively singular business scenarios for enterprises (institutions), such as office automation, customer relations, resource planning, business execution, human resources, and supply chain management scenarios, or even more singular business management scenarios like performance allocation and financial auditing. This results in a single enterprise (institution) deploying dozens of application systems. Chinese hospitals have developed a large number of decentralized, independent software applications related to single business scenarios involving medical scientific research and management, such as disease-specific databases, biobanks, research laboratories, bioinformatics analysis, drug clinical trials, and various research management software. Similarly, many "research information silos" exist within hospitals. China's hospital clinical research and scientific research management digital platform system has not yet been established. The fragmented development of its clinical research business applications has resulted in the separation of functions and data among the developed software. The digital platform has not been systematically built based on the three different industry domains of management, research and support, which lags behind the inherent requirements of high-quality development of public hospitals. Furthermore, there is a lack of applicable unified digital platform for multi-center cooperation and communication in clinical research and scientific research management among different hospitals.

[0003] An industry is a collection of economic activities categorized according to certain characteristics, such as scientific research, finance, healthcare, education, manufacturing, and agriculture. An industry domain is the overall layout and ecosystem of an enterprise or institution within a specific organization, and it dynamically changes as business develops, encompassing all links and participants in the industrial chain. Therefore, an industry domain is a broader scenario, potentially involving resources and activities from numerous different industries. A key difference between B2B and B2C software lies in its greater emphasis on overall system construction, involving how to create a digital business system based on an industry domain within an organization and determine the interaction methods between domains. In B2B, business processes and logical rules can only be broken down into data barriers between industry domains through effective data management methods such as integration, cleansing, and transformation when executed within the complex multi-scenario business within the industry domain. Currently, the digitalization of clinical research and scientific research management lacks synergy and remains separate. Hospitals often focus solely on building integrated big data centers for clinical research, neglecting a holistic digital layout and ecosystem for clinical research and management. They haven't created complex business applications centered on clinical research within a unified digital foundation, based on industry domain systems and multi-scenario architectures. This results in numerous "research data silos," a lack of data oversight tools, and frequent instances of academic fraud. The digitalization of the research ecosystem—including research data, tools, interaction, services, and support—is fragmented and isolated from a systematic solution for the digitalization of scientific research management centered on clinical research. Furthermore, there is a lack of consensus within the industry domain and its scenarios regarding the digitalization of clinical research and management platforms.

[0004] Clinical research encompasses the diagnosis, treatment, and prevention of diseases, while research management involves the planning, organization, coordination, implementation, and supervision of research activities. Clinical research is a crucial core component of research management, and research management provides support for clinical research. The two are mutually synergistic, mutually reinforcing, and interdependent; neither can be neglected. The digital construction of clinical research management platforms requires a complete and integrated systematic solution. Clinical research management platforms are an important type of B2B software related to the development of Chinese hospitals and the biopharmaceutical industry. However, clinical research management in Chinese hospitals generally suffers from fragmented management, low levels of digitalization, and data silos. Furthermore, given the lack of consensus within the industry domain and its specific scenarios, a systematic solution for the digital construction of research management centered on clinical research has not yet been developed. According to the "Information Function Guidelines for the Operation and Management of Public Hospitals" formulated by the National Health Commission in 2022, the hospital industry domain includes nine major domains: business activities, comprehensive management, finance, assets, human resources, matters, operation and management decision-making, data foundation, and basic management and integration, which correspond to 45 levels and 163 business scenarios. However, there are only two scattered and single business scenarios, clinical research business and research project management, for which there are no information function guidelines. Therefore, a systematic and digital function guideline for the industry domain and its domain scenarios of the clinical research and research management platform still needs to be created.

[0005] No-code technology primarily employs visual programming, drag-and-drop editing, form-driven, model-driven, and low-code or no-code platforms to create B2B applications, building applications through visual interfaces and pre-built modules. While no-code technology is a crucial method for B2B software development, it still presents several challenges. These include: modularly built programs are unsuitable for complex applications; development still requires programming skills; customization capabilities are limited; scalability and maintainability are poor; and no-code platforms pose data security issues. Furthermore, like traditional programming development, no-code software development begins with the analysis of business requirements, focusing on aspects such as business processes, data management, and functional and non-functional needs. It doesn't develop software based on the enterprise's industry domain architecture and scenario, making information, application, and resource silos within the industry domain difficult to avoid. Clinical research and scientific research management platforms, with their high deployment requirements in dedicated and private clouds, highly specialized nature, broad range of business areas, and complex business processes and logical rules, are unsuitable for development using existing no-code technologies.

[0006] Therefore, to solve the aforementioned challenges in B2B software development, it is necessary to develop a software development methodology based on an industry-domain-oriented B2B platform that allows users to independently create complex business applications by following a guided step-by-step guide, while still meeting the requirements of a general digital foundation for creating complex applications without business functionality. This B2B software development methodology will then be applied to the creation of clinical research and scientific research management platforms that have high data quality requirements, broad professional scope, and diverse application needs, thereby contributing to the high-quality development of Chinese hospitals and the biopharmaceutical industry. Summary of the Invention

[0007] To address the shortcomings of existing technologies, the present invention aims to provide a software development method for B-end users to independently create complex business applications based on industry domains. This method enables B-end users to independently create complex business applications that conform to multiple scenarios within an industry domain, following a guided development framework on a single digital foundation and without business functionality. B-end users can also directly modify business applications based on new business needs, enabling the addition, modification, and deletion of application functions in the B-end software system. This allows B-end users to rapidly and dynamically achieve systematic, autonomous, agile, and flexible development of B-end software systems according to the dynamic changes in multiple scenarios and complex business needs within the industry domain. The problem of information, application, and resource silos within industry domain software systems will also be resolved.

[0008] The document also proposes a systematic solution for constructing a digital research management platform centered on clinical research. First, the clinical research management platform comprises four major management domains: a management center domain, a management affairs domain, a management collaboration domain, and a management resource domain. Second, the research domains of the clinical research management platform mainly involve three core platform domains: unregistered (IIT) projects, registered (GCP) projects, and platform projects. The hospital's clinical research application scenario architecture is built around these three research domains, each with its own complex clinical research business scenarios. Furthermore, the support domains of the clinical research management platform include five major domains: research data, research tools, research interaction, research services, and research support. These domains involve dozens of professional fields, providing an organically integrated and unified research ecosystem support system for the hospital's clinical research. The creation of these three major categories and twelve major domains, along with the complex business applications within their respective domain scenarios, constitutes a systematic solution for the construction path of the clinical research management platform. As a result, the dispersed business applications in hospital scientific research can be systematically centralized and integrated according to the three industry domains of management, research and support, data barriers can be broken down and data supervision can be implemented.

[0009] To achieve the above objectives, this invention provides the following technical solution: a software development method for B-end enterprises to independently create complex business applications based on industry domains. This method constructs a development framework without business functions on a digital foundation equipped with infrastructure such as storage, middleware, cloud computing, artificial intelligence, IoT, blockchain, and security. B-end enterprises (institutions) independently define software that performs specific functions and create complex applications according to the guidance of the step-by-step instructions. The main steps include:

[0010] S1: Create software that performs specific functions and is managed by the B-end, and set basic parameters;

[0011] S2, Create the industry domain system D corresponding to software development;

[0012] S3, create a corresponding software domain scenario architecture system X based on industry domain D;

[0013] S4, construct a global framework based on the software domain scenario architecture system X;

[0014] S5, builds complex business layers based on the software global framework page;

[0015] S6, create page layouts based on complex business hierarchies;

[0016] S7 allows you to create general and special pages for business forms, tables, cards, and lists based on page layout.

[0017] S8 allows you to create business processes based on common and special pages such as business forms, tables, cards, and lists.

[0018] S9 is an approval process for creating business forms, tables, cards, and lists, including general and special pages, based on business processes.

[0019] In summary, this invention offers the following advantages: During software development, a business-function-free development framework is first constructed on a digital foundation equipped with infrastructure such as storage, middleware, cloud computing, artificial intelligence, IoT, blockchain, and security. B-end enterprises (institutions) then create industry domain systems corresponding to specific functions within this business-function-free development framework, determining the software domain scenario architecture. Under the corresponding industry domain system, the functional guidelines of that industry domain scenario serve as the basis for hierarchical classification and layering, guiding B-end enterprises (institutions) to independently create complex business applications according to the operational steps. This allows business personnel in non-technical departments of the software development department to create the required applications within a specific organization's industry domain system, based on their department's business needs and following the guided steps, as long as they clearly understand their business applications. Different departments within an enterprise (institution) can create applications at different times. Because they are developed on the same digital foundation and business-function-free framework, and created within corresponding industry domains and domain scenarios, the applications can interconnect in real time, effectively avoiding information, application, and resource silos.

[0020] This development methodology creates industry-domain-based B2B software. Software vendors primarily focus on building development frameworks without business functionalities on a digital foundation equipped with infrastructure such as storage, middleware, cloud computing, artificial intelligence, IoT, blockchain, and security. B2B enterprises and institutions, on the other hand, focus on their complex business operations and develop business applications according to the guided steps within the industry domain system and domain scenario architecture. For example, hospitals building clinical research and scientific research management platforms primarily focus on creating domain scenario architectures and corresponding business applications within three major categories and twelve industry domain systems. Through creation guidelines, hospitals systematically and independently develop software to achieve agile creation, updating, modification, and deletion of complex business applications for clinical research and scientific research management, significantly shortening software development and deployment cycles and saving software development and maintenance costs. This systematic solution not only helps build a healthy ecosystem for hospital clinical research and scientific research management, promotes continuous innovation in clinical research, and improves the efficiency of hospital scientific research management, but also helps enhance the level and competitiveness of hospital scientific research, contributing to the progress of Chinese medicine and the development of biomedicine. Attached Figure Description

[0021] Figure 1 This is a flowchart illustrating a software development methodology for independently creating complex business applications for B-end clients across multiple industry scenarios.

[0022] Figure 2A schematic diagram illustrating a systematic solution for the digital construction of an industry-specific clinical research management platform. Detailed Implementation

[0023] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0024] like Figure 1 As shown, on a development framework with a digital foundation and no business functions, this software development system aims to enable B-end enterprises to independently create complex business applications that meet the needs of multiple scenarios in the industry domain by guiding them through the creation of complex business applications.

[0025] The aforementioned digital infrastructure can be deployed in various ways, including dedicated cloud, private cloud, public cloud, hybrid cloud, edge cloud, and multi-cloud.

[0026] The aforementioned digital base has storage infrastructure that meets the requirements of high availability, high performance computing, high scalability, high sharing, high reliability, big data analysis, and intelligent operation and maintenance.

[0027] In addition to storage facilities, the digital infrastructure also has a middleware facility that meets the characteristics of high concurrency, low latency, microservice architecture, and containerization, including an organizational middleware, business middleware, technology middleware, data middleware, algorithm middleware, and R&D middleware.

[0028] In addition to storage facilities, the digital infrastructure also features cloud computing facilities that meet the characteristics of ultra-large scale, virtualization, versatility, on-demand service, low cost, fault tolerance, customizability and flexibility.

[0029] In addition to storage facilities, the digital base also has artificial intelligence facilities that meet the requirements of large models, large storage, algorithm libraries, sensors and various intelligent frameworks.

[0030] In addition to storage facilities, the digital base also has blockchain facilities that meet the requirements of distributed networks, consensus algorithms, encryption algorithms, smart contracts and various development tools.

[0031] In addition to storage facilities, the digital base also features IoT facilities that meet the requirements of efficient network connectivity, sensing technology, network transmission, and mobile device interaction.

[0032] In addition to storage facilities, the digital base also has network security facilities that meet the requirements of firewalls, intrusion detection systems, data encryption, access control, data backup and recovery, and security auditing.

[0033] A development framework built on a digital foundation, without any business function state, meets the needs of B-end enterprises and institutions to create business applications.

[0034] The aforementioned no-business-function state development framework's front-end user interface allows business applications to independently set up, display information, and receive user input step by step;

[0035] The aforementioned no-business-function state development framework's backend business logic and data access layers respectively satisfy tasks such as handling business logic, data storage, and system integration. The backend services can be developed using various technologies and frameworks.

[0036] The aforementioned no-business-function state development framework database meets the needs of both relational and non-relational databases;

[0037] The aforementioned no-business-function state development framework interface satisfies data exchange and integration, and provides various interface services;

[0038] The aforementioned no-business-function state development framework plugins and modules reduce the coupling between components, satisfying the requirements of application scalability, reusability, and maintainability;

[0039] The aforementioned no-business-function state development framework meets the security and permission requirements for user authentication, access control, and other functions.

[0040] The aforementioned development framework for non-business function status logging and monitoring is designed to help identify and resolve potential security risks, system failures, or non-compliant operations.

[0041] The aforementioned development framework documentation for non-business function states helps facilitate the access and use of user manuals, operation guides, system architecture, and other related documents.

[0042] In actual development, the development framework for B2B software without business functions can be selected according to different business needs and technology choices.

[0043] Taking the creation of a hospital clinical research management platform as an example, the specific operation steps are as follows:

[0044] S1, on the development framework of digital base and no business function state, creates software that performs specific functions managed by B-end, sets basic parameters, and the software should be able to directly or indirectly reflect its main characteristics of performing specific functions composed of relevant industry domains. B-end can create, edit or delete software name, icon, code, link, status, permission, route and basic management parameter settings.

[0045] The software name is created based on the business scope of the enterprise's (institution's) business within the industry domain system D. For example... Figure 2 As shown, software named Clinical Research and Scientific Research Management Platform was created to meet the needs of clinical research and scientific research management in the hospital.

[0046] The creation of the basic software settings includes setting the internal organizational structure of the enterprise; setting the professional titles and job structure of technical personnel; setting role responsibilities and permissions; setting user authentication, account and sub-account permissions; setting basic platform information, security and communication parameters; setting platform homepage management parameters; setting platform colors and font sizes; and setting permissions for specific functions, operations and data access.

[0047] The basic software settings described above are an important foundation for B-end users to independently create complex business applications by following the step-by-step guide. These basic settings can be further refined or expanded according to the specific needs and business characteristics of the enterprise (institution).

[0048] S2 creates the industry domain system D corresponding to the software development. The industry domain system D consists of domains on the software user end, management end, and joint end. The B end creates, edits, or deletes the domain name, icon, code, link, status, sorting, permissions, and route respectively.

[0049] based on Figure 2 As shown, this is the clinical research management platform.

[0050] The platform's industry domain system (D) comprises twelve major industry domains: Management Center Domain, Management Items Domain, IIT Project Domain, GCP Project Domain, Platform Project Domain, Research Data Domain, Research Tools Domain, Research Interaction Domain, Research Services Domain, Research Support Domain, Management Cooperation Domain, and Management Resources Domain. Among these, the Management Center Domain, Management Items Domain, Management Cooperation Domain, and Management Resources Domain are the management-related industry domains for clinical research on the platform. The IIT Project Domain, GCP Project Domain, and Platform Project Domain are the research-related industry domains for clinical research on the platform, and are also the core domains of the platform. The Research Data Domain, Research Tools Domain, Research Interaction Domain, Research Services Domain, and Research Support Domain are the five essential and organically integrated support-related industry domains for clinical research on the platform. These three categories and twelve industry domains are unified under the clinical research management platform, forming an ecosystem for collaborative development and innovation in hospital scientific research, and establishing a systematic solution for the digital construction path of the clinical research management platform based on industry domains.

[0051] S3, create a corresponding software domain scenario architecture system X based on industry domain D. The industry domain scenario architecture system X consists of the architecture of software user end, management end and joint end. B end can create, edit or delete the names, icons, codes, links, status, sorting, permissions, routes, etc. of hierarchical, classified and layered architectures.

[0052] based on Figure 2 As shown, the industry domain system and domain scenario architecture X of the clinical research management platform consists of multiple business application scenarios corresponding to each industry domain of the platform, specifically:

[0053] The aforementioned management center domain is one of the management-related industry domains for clinical research on the platform. Its corresponding business application scenarios include user center, research office, scientific review, ethical review, and scientific metrics. The user center provides access control and management; the research office improves the efficiency of clinical research; scientific review ensures the quality of research projects; ethical review protects the rights of research subjects and guarantees the legality of research; and scientific metrics provide performance evaluation and incentives. These inherent logical connections constitute the central hub function of the clinical research platform management.

[0054] The aforementioned management scope is the second industry domain for clinical research management on the platform. Its corresponding business application scenarios include project execution, application, funding usage, output, and technology transfer. Project execution ensures research proceeds according to plan; application is standardized and resources are allocated rationally; funding usage is effectively managed to prevent violations and waste; output promotes the sustainable development of scientific and technological activities; and technology transfer drives technological innovation and economic development. These management aspects constitute the entire process of scientific research management, and each aspect is indispensable.

[0055] The IIT project domain is one of the research-related industry domains for clinical research on the platform. Its corresponding business application scenarios include application management, project initiation management, intelligent CRF, process management, and project acceptance. Application management filters out valuable research projects; project initiation management ensures sufficient resource support for research; intelligent CRF ensures accurate and effective collection of research data; process management is a crucial evidence-gathering stage in research implementation; and project acceptance guarantees research quality and effectiveness. These stages ensure the full lifecycle management and quality of clinical research.

[0056] The GCP project domain mentioned above is the second industry domain in the platform's clinical research category. Its corresponding business application scenarios include trial management, drug management, project implementation, treatment processes, and remote monitoring. Trial management ensures research is conducted according to protocol; drug management ensures the safety, efficacy, and compliance of drugs; project implementation ensures accurate and complete data; treatment processes involve diagnosing and treating subjects; and remote monitoring is the remote monitoring and auditing of the research process. These elements ensure the scientific rigor, compliance, and efficiency of drug trials.

[0057] The platform project domain is the third research-related industry domain in the platform's clinical research. Corresponding business application scenarios include major projects, key personnel, key disciplines, key laboratories, and research wards. Major projects lead the progress of clinical research; key personnel support the team's strength to drive research breakthroughs; key disciplines are the foundation and support of clinical research; key laboratories are the base for conducting high-level research; and research wards are important practice venues for clinical research. This system is the fundamental guarantee for high-level clinical research and innovative development.

[0058] The research data domain is one of the industry domains supporting clinical research on the platform. Its corresponding business application scenarios include data standards, two-way verification, source datasets, disease cohorts, and disease-specific data. Data standards form the foundation of the research data domain; two-way verification helps identify missing or biased clinical data; source datasets are the original source sets of clinical research data; disease cohorts are tools for studying specific disease populations; and disease-specific data are single-disease databases. These data are organically combined to form a research data production system.

[0059] The aforementioned research tools domain is the second industry domain supporting clinical research on the platform. Its corresponding business application scenarios include biosamples, laboratory centers, bioinformatics analysis, electronic literature, and medical statistics. Biosamples provide traceable and compliant research materials; laboratory centers provide advanced experimental operation platforms; bioinformatics analysis extracts life science data from massive datasets; electronic literature provides journal retrieval and access; and medical statistics provides the collection, processing, analysis, and interpretation of research data. These tools work together indispensablely.

[0060] The aforementioned research interaction domain is the third industry domain supporting clinical research on the platform. Corresponding business application scenarios include academic exchange, scientific and technological training, disciplinary alliances, hospital alliances, and pharmaceutical and medical device alliances. Academic exchange promotes information dissemination and technological innovation; scientific and technological training promotes the popularization of new research methods and tools; disciplinary alliances promote resource sharing and innovative development within the same field; hospital alliances integrate resource advantages to expand research scale; and pharmaceutical and medical device alliances promote the transformation and application of research results. These interactive exchanges form a broad platform for scientific and technological innovation.

[0061] The aforementioned research services domain is the fourth industry domain supporting clinical research on the platform. Corresponding business application scenarios include data application, research assistance, technical collaboration, research design, and writing / translation. Data application ensures the authenticity and compliance of data sources; research assistance improves research efficiency; technical collaboration allows for the sharing of technical resources to conduct research projects; research design ensures the feasibility and effectiveness of research; and writing / translation ensures the standardized and professional presentation of research results. These services provide comprehensive, one-stop support for clinical research.

[0062] The aforementioned research support domain is the fifth industry domain supporting clinical research on the platform. Corresponding business application scenarios include instruments and equipment, reagents and consumables, scientific and technological innovation centers, clinical research institutes, and journal editing and review. Instruments and equipment ensure accurate experimental operations; reagents and consumables ensure reliable experimental results; scientific and technological innovation centers lead innovation, attract talent, and promote the transformation of research results; clinical research institutes serve as a bridge connecting basic research and clinical practice; and journal editing and review support the reliability and academic quality of research results. This constitutes a comprehensive, shared, and systematic research support.

[0063] The aforementioned management collaboration domain is the third industry domain in the platform's clinical research management category. Corresponding business application scenarios include international collaboration, SMO companies, patent agencies, conference services, and media promotion. International collaboration enhances research quality and international influence; SMO companies support research compliance and adherence to protocols; patent agencies efficiently apply for and maintain patents to promote innovation and commercialization; conference services provide one-stop services such as planning, organization, and venue provision; and media promotion and dissemination of results enhance brand awareness. These collaborations are conducive to attracting and utilizing more external resources.

[0064] The aforementioned management resource domain is the fourth industry domain in the platform's clinical research management, corresponding to business application scenarios such as expert resources, policies and regulations, scientific and technological evaluation, scientific and technological archives, and project audits. Expert resources ensure the quality of reviews and decision support; policies and regulations ensure the compliance and legality of scientific and technological activities; scientific and technological evaluation provides a basis for the effective allocation of research resources; scientific and technological archives ensure the traceability and verifiability of research activities; and project audits ensure the compliance and effectiveness of fund usage. The rational use of these resources improves the level of scientific research management.

[0065] The various clinical research business application scenarios under the industry domain system and domain scenario architecture X of the hospital clinical research scientific research management platform are an important foundation for hospitals to carry out scientific research activities. These scenarios can be further refined or expanded according to the specific needs and business characteristics of hospital clinical research.

[0066] S4. Construct a global framework based on the software domain scenario architecture system X. Specifically, the B-end uses the industry domain system D and scenario architecture X to create, edit, or delete global components and floating elements of the global framework page for hierarchical, categorized, and layered business scenarios.

[0067] Global components include the navigation bar, top bar, page tab bar, content module title bar, and operation area, etc.

[0068] Overlay elements include global tooltips, dialog pop-ups, side drawers, and fixed elements, etc.

[0069] On the B-end, based on the industry domain system D and the scenario architecture X, the grid and responsive rules of the global framework page for hierarchical, categorized, and layered business scenarios can be created, edited, or deleted.

[0070] Determine the grid column width (px) and number of columns;

[0071] Grid column width = (page width - total column spacing width - total margin width) / number of columns;

[0072] Determine the minimum and maximum supported width (px) of the page, and determine the responsive logic for non-responsive pages and components.

[0073] S5 constructs a complex business hierarchy based on the software's global framework page. The specific software user end, management end, and joint end all include complex hierarchies such as major categories, subcategories, medium categories, and minor categories. The B end can create, edit, or delete hierarchical names, icons, codes, links, statuses, sorting, permissions, routes, etc. of the hierarchical, classified, and layered levels.

[0074] S6 allows for the creation of page layouts based on complex business hierarchies. Specifically, B-end users can create, edit, or delete hierarchical, categorized, and layered page layouts composed of multiple components, page types, and adaptation methods, using grid settings, page segmentation, and module layout.

[0075] S7 allows for the creation of general and special pages for business forms, tables, cards, and lists based on page layout. Specifically, B-end users can create, edit, or delete general and special pages such as hierarchical, categorized, and layered forms, tables, cards, and lists.

[0076] For B-end users, form pages are created to accommodate input and options, and these forms are categorized into single-page, step-by-step, and pop-up forms.

[0077] The B-side creates a table page to hold the table, including elements such as table fields, buttons, labels, filters, operations, and page numbers;

[0078] For B-end users, card-style pages are created to house quick functions and data charts, including elements such as titles, information, and actions.

[0079] The B2B page creation is similar to a table, but with far fewer fields, and includes both vertically arranged and multi-column card-style list pages. Once the general page is created, B2B enterprises can edit or delete it.

[0080] B-end businesses create special pages specific to their business environment. These include dashboard pages, calendar pages, Gantt charts, log pages, architecture pages, code pages, device pages, line pages, and monitoring views. Once created, these special pages can be edited or deleted by the B-end enterprise.

[0081] S8 allows for the creation of business processes based on general and special pages of business forms, tables, cards, and lists. Specifically, B-end users can create, edit, or delete hierarchical, categorized, and layered business processes required by N complete management applications, including process name, process object, process purpose, applicable scenarios, business logic, process input, process output, and process boundaries.

[0082] The B-end also allows for the creation, editing, or deletion of swimlanes across three dimensions: functional departments, business stages, and business processes.

[0083] S9 is based on the business process to create business forms, tables, cards, and lists. The approval steps for general and special pages are as follows: the B-end can create, edit, or delete approval nodes and their branch conditions at different levels, categories, and layers.

[0084] Configure the approvers, time limits, forms, methods, and buttons for each node;

[0085] Implement approval functions such as sequential signing, concurrent signing, alternative signing, additional signing, and deduction of signatures for general pages such as business forms, tables, cards, and lists, as well as other special pages;

[0086] It can also perform business review operations such as copying, rejecting, assigning, transferring, delegating, redirecting, retrieving, canceling, expediting and terminating.

[0087] The above are merely preferred embodiments of the present invention. The scope of protection of the present invention is not limited to the above embodiments. All technical solutions falling within the scope of the present invention's concept are within the scope of protection of the present invention. It should be noted that for those skilled in the art, any improvements and modifications made without departing from the principle of the present invention should also be considered within the scope of protection of the present invention.

Claims

1. A method for developing B2B software based on an industry domain, characterized in that... On a digital foundation equipped with storage, middleware, cloud computing, artificial intelligence, IoT, blockchain, and security infrastructure, a development framework is built without business functionality. B-end users independently define software to perform specific functions and create applications following the guided steps, including the following main steps: S1: Create software that performs specific functions and is managed by the B-end, and set basic parameters; S2, Create the industry domain system D corresponding to software development; S3, create a corresponding software domain scenario architecture system X based on industry domain D; S4, construct a global framework based on the software domain scenario architecture system X; S5, builds complex business layers based on the software global framework page; S6, create page layouts based on complex business hierarchies; S7 allows you to create general and special pages for business forms, tables, cards, and lists based on page layout. S8 allows you to create business processes based on common and special pages such as business forms, tables, cards, and lists. S9 is an approval process for creating business forms, tables, cards, and lists, including general and special pages, based on business processes.

2. The industry-domain B2B software development method according to claim 1, characterized in that: The software can directly or indirectly reflect its main characteristics of performing specific functions by being composed of relevant industry domains. The B-end can create, edit or delete basic parameters, names, icons, codes, links, status, permissions and routes of the software.

3. The industry-domain B2B software development method according to claim 2, characterized in that: The industry domain system D includes domains consisting of software user terminals, management terminals, and joint terminals. The B terminals respectively perform creation, editing, or deletion operations on the name, icon, code, link, status, sorting, permissions, and route of the industry domains.

4. The industry-domain B2B software development method according to claim 3, characterized in that: The software domain scenario architecture system X includes an architecture consisting of a software user terminal, a management terminal, and a joint terminal. The B terminal can create, edit, or delete the names, icons, codes, links, statuses, sorting, permissions, and routes of the hierarchical, categorized, and layered architectures.

5. The industry-domain B2B software development method according to claim 4, characterized in that: In step S4, the B-end performs creation, editing, or deletion operations on global components and floating elements of hierarchical, categorized, and layered global framework pages based on the software domain scenario architecture system X. The global components include a navigation bar, a top bar, a page tab bar, content module title bars, and an operation area; The floating elements include global prompts, dialog pop-ups, side drawers, and fixed elements; The B-end, based on the software domain scenario architecture system X, performs creation, editing, or deletion operations on the grid and responsive rules of the hierarchical, categorized, and layered global framework pages.

6. The industry-domain B2B software development method according to claim 5, characterized in that: In step S5, the software user terminal, management terminal, and joint terminal all include major categories, subcategories, intermediate categories, and minor categories. The B terminal respectively performs creation, editing, or deletion operations on the hierarchical names, icons, codes, links, statuses, sorting, permissions, and routes of the hierarchical, classified, and layered levels.

7. The industry-domain B2B software development method according to claim 6, characterized in that: In step S6, the B-end performs creation, editing, or deletion operations on hierarchical, categorized, and layered page layouts composed of multiple components, page types, and adaptation methods through grid settings, page cutting, and module layout.

8. The industry-domain B2B software development method according to claim 7, characterized in that: In step 7, the B-end performs creation, editing, or deletion operations on hierarchical, categorized, and layered forms, tables, cards, lists, general pages, and special pages.

9. The industry-domain B2B software development method according to claim 8, characterized in that: In step S8, the B-end performs creation, editing, or deletion operations on the hierarchical, categorized, and layered business processes required for N complete management applications. The B-end also allows for the creation, editing, or deletion of swimlanes across three dimensions: functional departments, business stages, and business processes.

10. The industry-domain B2B software development method according to claim 9, characterized in that: In step S9, the B-end performs creation, editing, or deletion operations on the hierarchical, categorized, and layered approval nodes and their branch conditions, respectively. Configure the approvers, time limits, forms, methods, and buttons for each node; Implement functions for sequential signing, concurrent signing, alternative signing, additional signing, and deduction of signatures for general and special pages; It also performs business review operations such as copying, rejecting, assigning, transferring, delegating, redirecting, retrieving, canceling, expediting, and terminating.

11. A clinical research management platform, characterized in that, The platform comprises a digital ecosystem for clinical research management across three major categories and twelve industry domains, along with their respective complex business applications. The platform's industry domain system (D) includes the following domains: Management Center Domain, Management Items Domain, IIT Project Domain, GCP Project Domain, Platform Project Domain, Research Data Domain, Research Tools Domain, Research Interaction Domain, Research Services Domain, Research Support Domain, Management Cooperation Domain, and Management Resources Domain. Among these, the Management Center Domain, Management Items Domain, Management Cooperation Domain, and Management Resources Domain are the management-related industry domains for clinical research on the platform. The IIT Project Domain, GCP Project Domain, and Platform Project Domain are the three research-related industry domains for clinical research on the platform, and are also the core domains of the platform. The remaining five domains are support-related industry domains that organically integrate and unify the platform's clinical research, thereby creating a systematic solution for the digital construction path of the clinical research management platform based on these industry domains.

12. The clinical research management platform according to claim 11, characterized in that, The management center domain is one of the management industry domains for clinical research on the platform, and the corresponding business application scenarios include user center, scientific research office, scientific review, ethical review, and scientific and technological evaluation.

13. The clinical research management platform according to claim 11, characterized in that, The management matters domain is the second industry domain for management of clinical research on the platform, and the corresponding business application scenarios include project execution, matters application, fund use, results output, and technology transfer.

14. The clinical research management platform according to claim 11, characterized in that, The IIT project domain is one of the research-related industry domains for clinical research on the platform, and the corresponding business application scenarios include application management, project initiation management, intelligent CRF, process management, and project acceptance.

15. The clinical research management platform according to claim 11, characterized in that, The GCP project domain is the second research-related industry domain of the platform's clinical research, and the corresponding business application scenarios include trial management, drug management, project implementation, diagnosis and treatment process, and remote monitoring.

16. The clinical research management platform according to claim 11, characterized in that, The platform project domain is the third research-related industry domain of the platform's clinical research, and the corresponding business application scenarios include major projects, key talents, key disciplines, key laboratories, and research wards.

17. The clinical research management platform according to claim 11, characterized in that, The research data domain is one of the industry domains supporting clinical research on the platform. The corresponding business application scenarios include data standards, two-way verification, source datasets, disease cohorts, and disease-specific data.

18. The clinical research management platform according to claim 11, characterized in that, The research tools domain is the second industry domain supporting clinical research on the platform, and the corresponding business application scenarios include biological samples, experimental centers, bioinformatics analysis, electronic documents, and medical statistics.

19. The clinical research management platform according to claim 11, characterized in that, The research interaction domain is the third industry domain supporting clinical research on the platform, and the corresponding business application scenarios include academic exchanges, scientific and technological training, discipline alliances, hospital alliances, and pharmaceutical and medical device alliances.

20. The clinical research management platform according to claim 11, characterized in that, The research service domain is the fourth industry domain supporting clinical research on the platform, and the corresponding business application scenarios include data application, research assistance, technical cooperation, research design, and writing and translation.

21. The clinical research management platform according to claim 11, characterized in that, The research support domain is the fifth industry domain supporting clinical research on the platform, and the corresponding business application scenarios include instruments and equipment, reagents and consumables, scientific and technological innovation centers, clinical research institutes, and journal editing and review.

22. The clinical research management platform according to claim 11, characterized in that, The management collaboration domain is the third industry domain in the management category of the platform's clinical research. The corresponding business application scenarios include international cooperation, SMO companies, patent agency, conference services, and media promotion.

23. The clinical research management platform according to claim 11, characterized in that, The management resource domain is the fourth industry domain in the management of clinical research on the platform, and the corresponding business application scenarios include expert resources, policies and regulations, technology assessment, technology archives, and project auditing.

Images