Exam management system that provides a dashboard

Abstract

The present invention relates to a test management system that manages the process of commissioning and conducting test work in the life sciences field through a dedicated application, and includes an administrator terminal used by the administrator of the company that manufactures and provides the dedicated application; a CRO master terminal used by administrators including team leaders and sales representatives of the CRO company that has been commissioned to perform the test work; a CRO terminal used by the person in charge of conducting the test at the CRO company; a client terminal used by the person in charge at the customer company that has commissioned the CRO company to perform the test work; and a server that provides the administrator terminal, CRO master terminal, CRO terminal, and client terminal with a dedicated application, provides various functions related to the test through the dedicated application, and enables real-time sharing of data and information. According to the present invention, tests can be conducted easily and quickly, and have the effect of contributing to the convenience of CRO companies and customer companies involved in the test.

Description

[Technical Field]

[0001] The present invention relates to test management technology in the biotechnology field, and more specifically, to technology for sharing and managing the test process in real time between a client that has commissioned a contract and a test analysis organization (CRO: Contract Research Organization). [Background Art]

[0002] Currently, the South Korean pharmaceutical market is advancing evidence-based research on many products and attempting to enhance brand value based on the research results. However, in reality, such tests require considerable effort from researchers and a large budget, making implementation difficult under the current circumstances. In addition, tests on many currently marketed products generally take forms such as post-marketing surveillance, investigator-initiated trials, and pharmaceutical company-initiated trials, and the current situation is that advancing diverse types of research is difficult.

[0003] For example, in order to obtain approval for a Phase I clinical trial at a biopharmaceutical company, an Investigational New Drug (IND) application is submitted to a relevant authority (e.g., the Korean Ministry of Food and Drug Safety, KFDA). As submission materials for an IND application, a non-clinical test performance report covering a comprehensive scope is generally submitted. Non-clinical tests (in vivo and in vitro tests) submitted for an IND application must comply with Good Laboratory Practice (GLP) regulations, and whether the research complied with GLP regulations must be stated in the research report. These important elements must be sufficiently discussed in advance, and whether they have been implemented must be confirmed between the test requester and the test implementer. In addition, it is necessary to confirm whether each test complies with the guidelines of regulatory authorities, and it is also necessary to be able to verify the identity of the person in charge who evaluates the research results and makes a final judgment on safety.

[0004] To reduce the costs associated with testing and streamline the testing process, pharmaceutical companies are increasingly outsourcing their testing operations to Contract Research Organizations (CROs), which are testing or analytical laboratories that contract with these organizations to carry out the testing work on their behalf.

[0005] In Japan, the current state of CROs (Contract Research Organizations) is diverse, ranging from large foreign-owned companies to small businesses. Due to the nature of their work, which involves providing contracted services using human resources, CROs of various sizes exist, including those operating as sole proprietorships.

[0006] Large-scale foreign-owned CROs use their own management software to share and report test results and other relevant documents in real time with their client companies. However, because this proprietary management software is tailored to the specific CRO company, it lacks versatility, and the absence of direct communication features such as chat functions makes it difficult for clients to contact the CRO's representatives.

[0007] Furthermore, for small and medium-sized CRO companies, developing proprietary software for trial management is burdensome in terms of both human resources and investment, and it is difficult to quickly produce software tailored to their specific needs. [Overview of the project] [Problems that the invention aims to solve]

[0008] This invention was made to solve the above-mentioned problems, and its purpose is to provide a test management system that allows clients who request test services and CRO companies (organizations that undertake and conduct tests) to share the progress of the tests in real time and report the results.

[0009] The object of the present invention is not limited to the object described above, and other objections not described can be clearly understood by a person of the ordinary skill from the following description. [Means for solving the problem]

[0010] To achieve this objective, the present invention relates to a test management system for managing the process of commissioning and conducting test work in the life sciences field through a dedicated application, and includes an administrator terminal which is used by the administrator of the company that manufactures and provides the dedicated application; a CRO master terminal which is used by administrators including team leaders and sales representatives of the CRO company that has been commissioned to perform the test work; a CRO terminal which is used by the person in charge of conducting the test at the CRO company; a client terminal which is used by the person in charge at the customer company that has commissioned the CRO company to perform the test work; and a server which provides the dedicated application to the administrator terminal, the CRO master terminal, the CRO terminal, and the client terminal, provides various functions related to the test through the dedicated application, and enables real-time sharing of data and information, wherein the server grants different permissions to the administrator terminal, the CRO master terminal, the CRO terminal, and the client terminal that log in through the dedicated application, and provides different functions according to those permissions, and the server provides a dashboard function which visualizes and displays information related to test management on the screen through the dedicated application.

[0011] When providing the dashboard function, the server may also provide an individual project dashboard function that displays information including the progress and results of individual projects under which testing is conducted.

[0012] The server may provide the individual project dashboard function to all of the administrator terminal, the CRO master terminal, the CRO terminal, and the client terminal.

[0013] The server may, when providing the dashboard function, also provide a project-wide integrated management dashboard function that displays the progress and results of the entire project under which the test is being conducted in an integrated manner.

[0014] The server may provide the integrated project management dashboard function to the CRO master terminal only. [Effects of the Invention]

[0015] According to the present invention, by sharing the life sciences testing contract process in real time, testing can be conducted easily and quickly, which has the effect of contributing to the convenience of CRO companies and client companies involved in the testing.

[0016] Furthermore, according to the present invention, by providing key information related to the trial in a dashboard format, users can check information such as the progress and results of the project at a glance, thus contributing to user convenience. In particular, CRO managers can gain insights when managing and operating non-clinical CRO projects through the integrated project management dashboard, which facilitates quick decision-making and processing of tasks. [Brief explanation of the drawing]

[0017] [Figure 1] A block diagram showing the schematic structure of a test management system according to one embodiment of the present invention. [Figure 2] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 3] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 4] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 5] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 6] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 7] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 8] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 9] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 10] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 11] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 12] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 13] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 14] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 15] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 16] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 17] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 18] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 19] This is an example screen of the dedicated application provided in the test management system according to an embodiment of the present invention. [Figure 20]This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 21] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 22] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 23] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 24] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 25] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 26] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 27] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 28] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 29] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 30] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 31] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 32] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 33] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 34]This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 35] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 36] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 37] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 38] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 39] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 40] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 41] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 42] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 43] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 44] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 45] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 46] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 47] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 48]This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 49] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 50] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 51] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 52] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 53] This is an example of a screen for a dedicated application provided in a test management system according to one embodiment of the present invention. [Figure 54] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 55] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 56] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 57] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 58] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 59] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 60] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 61]This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 62] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Figure 63] This is an example of a dashboard screen in a dedicated application provided by a test management system according to one embodiment of the present invention. [Modes for carrying out the invention]

[0018] The present invention can be modified in various ways and may have various embodiments; therefore, specific embodiments are shown in the drawings and described in detail. However, it should be understood that this is not intended to limit the present invention to specific embodiments, but rather to include all modifications, equivalents, or substitutions that fall within the spirit and art of the invention.

[0019] The terminology used in this application is used solely to describe specific embodiments and is not intended to limit the invention. A singular expression includes plural expressions unless the context clearly indicates otherwise. In this application, terms such as “includes” or “having” are intended to indicate the existence of features, figures, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood not to preemptively exclude the possibility of the existence or addition of one or more other features, figures, steps, actions, components, parts, or combinations thereof.

[0020] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as they would be generally understood by a person of ordinary skill in the art to which this invention pertains. Terms as defined in commonly used dictionaries should be interpreted as having the meaning consistent with their meaning in the context of the relevant art, and should not be interpreted in an ideal or overly formal sense unless explicitly defined herein.

[0021] When explaining with reference to the attached drawings, the same reference numerals will be used for identical components, regardless of the reference numerals, and redundant explanations will be omitted. In the description of the present invention, if a specific explanation of related prior art is deemed to unnecessarily obscure the gist of the invention, such detailed explanation will be omitted.

[0022] The present invention relates to a cloud-based software and a test management system that manages the process of requesting and carrying out test work in the life sciences field through a dedicated application.

[0023] Figure 1 is a block diagram showing the schematic structure of a test management system according to one embodiment of the present invention.

[0024] Referring to Figure 1, the test management system according to one embodiment of the present invention includes an administrator terminal 110, a CRO master terminal 120, a CRO terminal 130, a client terminal 140, and a server 200.

[0025] The administrator terminal 110 is a terminal used by the administrator of a company that develops and provides dedicated applications. The administrator terminal 110 can be implemented in various ways as a terminal capable of communicating via a wired wireless network. For example, the administrator terminal 110 can be implemented as various devices such as a desktop computer or a laptop computer.

[0026] The CRO master terminal 120 is a terminal used by administrators, including team leaders and sales representatives, of the Contract Research Organization (CRO) company that has been commissioned to perform the testing work. In one embodiment of the present invention, the CRO master terminal 120 can be implemented using one or more units. For example, the CRO master terminal 120 can be implemented as various devices such as a desktop computer or a laptop computer.

[0027] The CRO terminal 130 is a terminal used by personnel responsible for conducting tests at a CRO (Contract Research Organization) company. In one embodiment of the present invention, the CRO terminal 130 can be implemented using one or more units. For example, the CRO terminal 130 can be implemented as various devices such as a desktop computer or a laptop computer.

[0028] The client terminal 140 is a terminal used by a representative of a client company that has requested testing services from a CRO company. In one embodiment of the present invention, the client terminal 140 can be implemented using one or more devices. For example, the client terminal 140 can be implemented as various devices such as a desktop computer or a laptop computer.

[0029] Server 200 provides dedicated applications to administrator terminal 110, CRO master terminal 120, CRO terminal 130, and client terminal 140, and provides various functions related to testing through these dedicated applications, as well as service functions to share data and information in real time.

[0030] Server 200 can grant different permissions to administrator terminals 110, CRO master terminal 120, CRO terminal 130, and client terminals 140, which log in through a dedicated application, and provide different functions according to those permissions.

[0031] Server 200 provides a dashboard function that visualizes and displays information related to test management on the screen through a dedicated application.

[0032] When providing dashboard functionality, server 200 can provide individual project dashboard functionality that displays information including the progress and results of individual projects under testing.

[0033] Server 200 can provide individual project dashboard functionality to all of the administrator terminals 110, CRO master terminal 120, CRO terminal 130, and client terminal 140.

[0034] When providing dashboard functionality, server 200 can offer a comprehensive project management dashboard function that displays the progress and results of the entire project under test in an integrated manner.

[0035] Server 200 can provide the integrated project management dashboard function only to the CRO master terminal 120.

[0036] Server 200 can generate IDs for the CRO master, CRO, and client on the administrator terminal 110, input information for the CRO company and client company, and provide functions for the maintenance of the dedicated application.

[0037] Server 200 can input project information to be tested into the CRO master terminal 120 to generate projects, monitor the detailed progress of each project, and provide a chat function for communication between one or more CRO terminals and one or more client terminals.

[0038] Server 200 can input project subcategory information into CRO terminal 130, upload project-related documents, and provide a chat function for communication between one or more CRO master terminals and one or more client terminals.

[0039] Server 200 can monitor project progress on client terminal 140, download documents uploaded by CRO terminal 130, and provide a chat function for communication between one or more CRO master terminals and one or more CRO terminals.

[0040] In the present invention, the server 200 can grant different functions and permissions to the administrator terminal 110, CRO master terminal 120, CRO terminal 130, and client terminal 140, which log in to the dedicated application.

[0041] Server 200 can grant administrator terminals 110, used by personnel of the dedicated application development company that develops and manages the dedicated application, the functions and permissions to input information of the CRO company and client company, register and generate IDs for personnel of each company, check login records, and record maintenance history. At this time, administrator terminal 110 is unable to view content created by the CRO master terminal 120 and CRO terminal 130, and is unable to view all test content and chat content contracted and implemented between the CRO company and the client company.

[0042] Once a purchase agreement is concluded between the CRO company and the custom application development company, a custom application incorporating feedback from the CRO company is developed. Subsequently, the custom application development company receives the client company information from the CRO company and requests and receives the names and email addresses of all CRO personnel and CRO masters who are responsible for the trial. The custom application development company also generates IDs for the CRO personnel and CRO masters using the received names and email addresses and automatically sends invitation emails to those email addresses. Upon receiving the email, the personnel generate a password, obtain login privileges, and complete registration.

[0043] Furthermore, once a testing outsourcing contract is concluded between the CRO company and the client company, the CRO company requests the dedicated application development company to generate the client's ID. The administrator then enters the client's company information and generates the ID using the client's email address. Simultaneously with the ID generation, an invitation email is automatically sent to the client's email address. The client receives the email, generates a password to obtain login privileges, and completes the registration. In other words, the administrator creates the ID and grants it to the user for use. The client also receives an email from the administrator and only sets the password. In other words, only the user (client) knows the password.

[0044] Figures 2 to 53 show example screens (UI / UX) of a dedicated application provided by a test management system according to one embodiment of the present invention.

[0045] Figure 2 shows an example of the login screen for a dedicated application.

[0046] In Figure 2, when logging in to the administrator terminal 110, the user can enter an administrator ID and password. If an administrator ID and password configured to grant administrator privileges are entered, the user will be logged in as an administrator.

[0047] Figures 3 to 13 show examples of screens (UI / UX) of a dedicated application provided to an administrator terminal in a test management system according to one embodiment of the present invention.

[0048] Figure 3 shows an example of a dedicated application screen provided to the administrator terminal 110, with a menu displayed on the left side of the screen. When "All Users" is selected from the menu, a list is displayed that allows management of all users, including the CRO Master (CRO_MASTER), CROs, and clients. Functions are provided to modify or delete each user's information. In this way, the present invention allows all users to be viewed at a glance by displaying them in a list.

[0049] Figure 4 shows an example screen from the example screen in Figure 3, where the "Client Companies" menu is selected. It displays a list of client companies and provides functions to input, modify, and delete client company information. An "Add Client Company" button is located at the top right of the screen in Figure 4. When this button is selected, a screen is provided, as shown in Figure 5, where the information of a new client company can be entered and added to the list.

[0050] Figure 6 shows an example screen when the "CRO Companies" menu is selected, displaying a list of CRO companies that conduct trials and providing functions to input, modify, and delete information about CRO companies. An "Add CRO Company" button is located at the top right of the screen in Figure 6. When this button is selected, a screen is provided, as shown in Figure 7, where the user can input information about a new CRO company and add it to the list.

[0051] Figure 8 shows an example screen when the "Client Registration" menu is selected, providing functions for entering information to generate a Client ID, verifying the ID, and sending an email invitation for password (PW) generation.

[0052] In Figure 8, once all input fields are filled in and the "Enter" button is selected, an invitation is sent to the email address, as shown in Figure 9. Furthermore, if the "Register" button is selected in the email, an input window is provided for setting the password to be used for that ID account.

[0053] Figure 10 shows an example screen when the "CRO Registration" menu is selected, providing functions for inputting information to generate a CRO ID, verifying the ID, and sending an email invitation for password (PW) generation. Similar to the client member registration example in Figures 8 and 9, in the case of CRO member registration, an email for password registration is sent to the email address entered in Figure 10. Once the password is registered via email, the ID and password are registered and member registration is completed.

[0054] Figure 11 shows an example screen when the "CRO Master Registration" menu is selected, providing functions for inputting information to generate a CRO Master ID, verifying the ID, and sending an email invitation for password (PW) generation. Similar to the client member registration shown in the example screens in Figures 8 and 9, in the case of CRO Master member registration, an email for password registration is sent to the email address entered in Figure 11. Once the password is registered via email, the ID and password are registered and member registration is completed.

[0055] Figure 12 shows an example screen when the "Activity History" menu is selected, providing a function to manage the activity history for maintenance purposes.

[0056] Figure 13 shows an example screen when the "Maintenance Report" menu is selected, providing a function to input event and resolution information for maintenance history management and manage it in a report format.

[0057] Figures 14 to 31 show examples of the UI / UX of a dedicated application provided to a CRO master terminal in a test management system according to one embodiment of the present invention.

[0058] In Figure 2, when logging in to the CRO master terminal 120, the user can enter a CRO master ID and password. If a CRO master ID and password configured to grant CRO master privileges are entered, the user will be logged in as a CRO master.

[0059] Figure 14 shows an example of the dedicated application screen provided to the CRO Master terminal 120 when logged in as a CRO Master, with a menu displayed on the left side of the screen. When "All Users" is selected from the menu, it provides a function to view and manage the IDs and contact information of all CRO Masters, CROs, and personnel belonging to the same CRO company. For example, it can provide functions to modify and delete information due to changes in team members.

[0060] Figure 15 shows an example screen where the "Client & Project Status" menu is selected, displaying a list of client information entered by the administrator terminal 110. When the rightmost ">" option is selected on this screen, the system provides project list information for the client in question, as shown in Figure 16.

[0061] In Figure 16, a function is provided to input project information and view the project list. When the rightmost ">" display is selected, the details of the project are displayed. In other words, when a project contract arises for a client in the client list in Figure 15, a function is provided to input the project information in the example screen in Figure 16. When the "Add Project" button at the top right of Figure 16 is selected, a function is provided to input and generate new project information, as shown in Figure 17.

[0062] In the example screen shown in Figure 18, when the "Add Project" button, which is the project creation button, is selected, a screen is provided, as shown in Figure 19, that generates a project contracted with a client company and allows the user to specify the person in charge of the project.

[0063] Figure 19 provides a function to select a project manager, where project managers can be designated, and only the designated project managers can create test results and upload documents for that project.

[0064] Figures 20 to 26 show example screens for project details.

[0065] As shown in Figures 20 to 26, in the example screen where the "Client & Project Status" menu is selected, when a project is selected from the project list and the ">" button is selected, the detailed information screen for that project is displayed. Such project details are created on the CRO terminal 130. Monitoring can also be performed using a viewer on the CRO master terminal 120.

[0066] Figure 20 shows an example screen when the "Test Article" tab is selected in the project details; Figure 21 shows an example screen when the "Test & Progress" tab is selected in the project details, displaying test-related content and progress; and Figure 22 shows an example screen when the "Equipment & Material" tab is selected in the project details.

[0067] Figure 23 shows an example screen when the "Test Method" tab is selected in the project details, and Figure 24 shows an example screen when the "Test Results" tab is selected in the project details.

[0068] Figure 25 shows an example screen when the "Project Team" tab is selected in the project details, and Figure 26 shows an example screen when the "Documents" tab is selected in the project details.

[0069] Figure 27 shows an example screen when the "Activity Report" menu is selected, displaying a dashboard-style screen. Within this menu, the screen can be reconfigured according to the CRO company's situation.

[0070] In Figure 27, Total Project represents the total number of projects implemented for a specific client company, Project Completion Status represents the number of projects in progress or completed, Project Completion Time represents the number of days required from contract signing to project completion, and Contract Number for Each Description represents the number of contracts for each test item provided.

[0071] Figure 28 shows an example screen when the "History" menu is selected, and it provides a function to display the login records of the CRO personnel (CRO master and members with CRO IDs) and clients.

[0072] Figure 29 shows an example screen when the "Test Preparation List" menu is selected, providing a function to input a list of all ongoing tests at the CRO company. Providing this menu function makes it easier to extract values ​​for each test from the dashboard, and eliminates the need to enter the experiment name each time test details are entered on the CRO terminal 130, thus contributing to convenience.

[0073] In Figure 29, the "Name of Test Description" item represents the provided test item, the "Date of Set-up" item represents the date the test setup was completed, the "Application" item represents the scope to which the set test may apply, the "Responsible Person / Team" item represents the name of the person in charge or team, and the "Note of Last Update" item indicates the update to the latest revision.

[0074] Figure 30 shows an example screen when the "Chat" menu is selected, illustrating the chat menu that provides the chat function.

[0075] In the example shown in Figure 30, a client list displaying client information is shown. When a client you want to chat with is selected and the rightmost ">" button is selected, a chat function is provided that allows you to chat as shown in Figure 31. At this time, it is possible to provide a function for multiple people to chat, such as the CRO, CRO master, and clients of the same CRO company.

[0076] Figures 32 to 51 show examples of the UI / UX of a dedicated application provided to a CRO terminal in a test management system according to one embodiment of the present invention.

[0077] In Figure 2, when logging in to the CRO terminal 130, a screen is provided where the CRO ID and password can be entered. When a CRO ID and password configured to grant CRO privileges are entered, the user is logged into the CRO.

[0078] Figure 32 shows an example of the dedicated application screen provided to the CRO terminal 130 when logged into the CRO, with a menu displayed on the left side of the screen. When "Client & Project Status" is selected from the menu, a list of clients and projects handled by the CRO are displayed. When the ">" button on the right is selected, as shown in Figure 33, a list of projects for which the CRO has been designated as the project manager is displayed. When the ">" button on the right is selected, a screen for entering detailed information about the project is provided, as shown in Figure 34. In this case, the project information is what the CRO Master entered when the project was created. In Figure 34, a list of projects for all clients contracted with the CRO company is displayed, but when the ">" button is selected, only the projects handled by the CRO are displayed. In other words, when the ">" button is selected, the list of projects handled by the CRO is displayed, and detailed information about the selected project is provided.

[0079] Figure 34 shows an example screen when the "Test Article" tab is selected on the project details screen, displaying a list of test article information. If the "Add Test Article" button on the right is selected, a screen for entering test article information is provided, as shown in Figure 35.

[0080] In Figure 34, the "Test Articles" item refers to test specimens that undergo cell treatment, animal administration, or chemical reaction.

[0081] The Necessary items indicate the substances required for the samples to carry out the contracted test. After the test contract is signed, the test design must be agreed upon between the test requester and the test implementer. Therefore, the required amount of samples for the test is calculated in advance, and based on this calculated amount, the agreed-upon Safety Factor is applied to determine the number and concentration of sample vials to be provided.

[0082] The "Recombinant Gene" item indicates whether confirmation of genetic modification is required when the test substance is a virus or cell containing genetic material, or genetic material such as DNA or RNA. Of these, living modified organisms (LMOs) may cause environmental problems or affect human health, so it is important to keep records and manage them safely. When conducting experiments using LMOs, facilities must notify or obtain approval according to their safety management level, and LMOs that pose a high risk to human health or the environment require further approval from the facility.

[0083] The Bio Safety Level (BSL) item indicates the level of biosafety. BSL (Biological Safety Level) ranges from Level 1 to Level 4 and is a standard for classifying necessary facilities or equipment based on the degree of hazardous pathogens. It is classified according to the standards of the World Health Organization (WHO) and the U.S. Centers for Disease Control and Prevention (CDC). Each BSL level requires adherence to specific requirements regarding laboratory practices, safety equipment, and facility construction.

[0084] The Conc.[mg / mL] item indicates the concentration of the sample. Samples must be received at or above the highest concentration at the time of administration; concentrations below that may be diluted before processing.

[0085] The Volume[mL / vial] item indicates the volume per vial of the sample.

[0086] The Received[Vials] field indicates the number of vials delivered. For samples with a high risk of human and animal infection, accurate records of the number of vials received, used, and remaining are paramount for management purposes, and this invention provides a field in which such vial numbers can be recorded.

[0087] The Used[Vials] item indicates the number of used vials.

[0088] The Label Number field shows the information printed on the label, allowing you to verify the product number and lot number.

[0089] The Storage Condition item indicates the sample storage environment. After the sample is delivered, it must be stored in accordance with the pre-agreed storage environment until before testing. Failure to comply with this will reduce the reliability of the test results and decrease the validity of the result values.

[0090] Figure 36 shows the screen when the "Test & Progress" tab is selected on the project details screen, displaying test-related information and progress. In other words, it provides a way to quickly grasp the progress of the test, thereby reducing communication work such as email and telephone. Also, due to the characteristics of the bio and pharmaceutical fields, cell and animal tests often require long periods of observation and measurement, and this helps CROs and clients to carry out their work smoothly during such long schedules. If the "Add Test" button on the right is selected, a screen is provided where test details, progress, test method, test results, etc. can be entered, as shown in Figure 37.

[0091] In Figure 36, the Test Description item shows the list of test items agreed upon between the test requester and the test implementer.

[0092] The Test Article Arrival Date field indicates the date the test sample was received, the Test Start Date field indicates the start date of the test, and the Test Completion Date field indicates the completion date of the test.

[0093] The Preliminary Report Issued Date field indicates the issue date of the preliminary report, the Customer Feedback Receipt Date field indicates the date feedback was received from the customer who requested the test on the draft report, and the Final Report Issued Date field indicates the issue date of the final report.

[0094] The Progress item is determined through agreement between the CRO company and the client company based on the importance of the work, and the progress towards that value is expressed in 10% increments.

[0095] The "Testing Status" field indicates whether the contract is in progress or completed.

[0096] Figure 38 shows an example screen when the "Equipment & Material" tab is selected on the project details screen, providing a function to display and input information about the equipment and materials used in the test.

[0097] In Figure 38, under "Cell," the "Cell line" item indicates a cell line. A cell line refers to individual cells with identical genetic information and is primarily used in bio-processes for mass production. It is immortal, allowing for long-term culture and easy mass cultivation.

[0098] The "Strain" item indicates a cell line. Cell lines are derived from cell lines, have a finite lifespan, and exhibit characteristics such as a limited number of cell divisions, making them suitable for vaccine development.

[0099] The Source field indicates the distributing or supplying organization that provides the test animals.

[0100] The "Culture" field indicates the name or composition of the culture medium in which the cells are cultured.

[0101] The Primary Passage No. field indicates the number of passages from the time the cells are isolated from the tissue until they become stable.

[0102] The "Sub Cultivation No." field indicates the number of subcultures performed on stored cells before they stabilized for testing. If the number of subcultures exceeds a certain level, mutations may occur in the cells, allowing for the pre-determining of the maximum number of subcultures per cell type.

[0103] The Cell Density [cells / flask] item indicates the amount of cells in a single culture flask, and accurate test results can be derived when an appropriate level of cells is distributed within the flask.

[0104] The Culture Condition [Temp. & Air] item indicates the temperature and gas composition conditions inside the incubator.

[0105] In Figure 38, under "Animal," the "Animal" item indicates the name of an animal.

[0106] The Species entry indicates an animal species, which is scientifically classified and named according to its genetic makeup and characteristics.

[0107] The "Strain" entry is a sub-concept for an animal species, indicating that it is developed through inbreeding, genetic modification, or selective breeding.

[0108] The Source field indicates the distributor or supplier that provides the biological resources used in the experiment.

[0109] The Age field indicates the age of the test animal, and the Weight field indicates the weight of the test animal. Through these fields, it is possible to confirm whether the weight is within the normal range and to use this as a baseline to track changes in the animal's weight during the study period.

[0110] The "Number of Female" column indicates the number of female test animals.

[0111] The Pregnancy Status item indicates whether a female animal is pregnant. Pregnancy brings about internal and behavioral changes, which can alter the response mechanisms when a drug is administered, and therefore can affect the outcome.

[0112] The "Number of Male" column indicates the number of male test animals, and the "Health Status" column indicates the health status of the test animals.

[0113] The Acclimatization [Days] item indicates the animal acclimatization period, which is the time from when the animal arrives at the testing site until it stabilizes.

[0114] The Housing and Care Condition item describes the living environment of the test animals.

[0115] In Figure 38, the information listed under "Equipment" allows verification, as needed, whether the equipment was regularly calibrated and inspected, or whether there were any problems with the equipment. Furthermore, clearly indicating the use of appropriate equipment under "Equipment" helps maintain the reliability of the test.

[0116] In Figure 38, under "Equipment," the Product Name field indicates the equipment name, the Supplier field indicates the equipment supplier, the Product No. field indicates the product number, and the Lot No. field indicates the lot number.

[0117] In Figure 38, you can check the information on the reagents and consumables used under the "Laboratory Reagents and Consumables" section to ensure that you used products of an appropriate level for the test.

[0118] In Figure 38, under the "Laboratory Reagents and Consumables" section, the Product Name field indicates the product name, the Supplier field indicates the supplier name, the Product No. field indicates the product number, and the Lot No. field indicates the lot number.

[0119] In Figure 38, when the "Add Cell" button is selected, a screen is provided where the cell information used in the experiment can be entered, as shown in Figure 39.

[0120] Furthermore, when the "Add Animal" button is selected in Figure 38, a screen is provided where information about the animal used in the experiment can be entered, as shown in Figure 40.

[0121] Furthermore, when the "Add Equipment" button is selected in Figure 38, a screen is provided, as shown in Figure 41, where information about the equipment (machinery) used in the test can be entered.

[0122] Furthermore, when the "Add Reagents and Consumables" button is selected in Figure 38, a screen is provided, as shown in Figure 42, where information about the reagents and consumables used in the test can be entered.

[0123] Thus, this invention allows for a dual check of suitability by both the client and the CRO by verifying detailed information such as the cell line, strain, and species of the test organism cells and animals. Furthermore, it enables verification of information regarding the equipment and materials used, allowing for rapid confirmation through uploaded maintenance documents matched with the lot number, and emphasizing transparency regarding the materials used by filling in detailed information. Additionally, it allows verification by product number whether the appropriate grade of reagents for cell administration and animal in vivo administration were used. For example, if only the reagent name is listed, it is difficult to verify the grade information.

[0124] Figure 43 shows an example screen when the "Test Method" tab is selected on the project details screen, providing information about the test method. Specifically, it displays the information entered in the "Test & Progress" tab, and provides a function to modify the information here. In this way, the present invention provides a function to clearly present guidelines for test methods. For example, it is possible to determine whether the guidelines are appropriate for obtaining IND approval, and in the case of tests targeting organisms such as cells and animals, there may be some reproduction errors, but it is possible to check how many times the experiment was repeated, and it is possible to check how many flasks were used in one batch experiment and how many configuration experiments (duplicate, triplicate) were performed.

[0125] In Figure 43, under Test Method (Cell), the Cell line item indicates the cell line name. This item can specify either the cell line name or the cell system, as the cell system may sometimes be considered part of the cell line.

[0126] The "Test Methods" section describes the test method.

[0127] The Practice Guideline item indicates whether or not the test conformed to the regulatory body's standards, and through this item, the reliability of the test method and the reproducibility of the test can be determined.

[0128] The Cell Density[cells / flask] item indicates the amount of cells in the test flask (flask).

[0129] The Flask Number field indicates the number of test flasks. This field allows us to determine how many times the same repeated process was performed in one batch of testing.

[0130] In the "Treated TA Conc. [mg / mL]" item, TA stands for Test Article and indicates the concentration of the sample at the time of processing.

[0131] The "Treated TA Amount [mL / flask]" item indicates the amount of test sample treated in the flask.

[0132] The Experimental Replication item indicates the number of test repetitions, and this item allows for verification of reproducibility.

[0133] In Figure 43, under Test Method (Animal), the Animal item indicates the animal used, the Test Method item indicates the test method, the Practice Guideline item indicates whether or not it complied with the regulatory body's standards, the Number of Animal item indicates the number of animals used in the test, the Treated TA Conc. [mg / mL] item indicates the concentration of the treated sample (TA: Test Article), and the Treated TA Amount [mL / animal] item indicates the volume of the treated sample.

[0134] In Figure 43, under Test Method (Chemical), the Chemical Reaction item indicates the name of the chemical reaction used to derive the test result, and the Test Method item indicates the test method.

[0135] The Quvette Number field indicates the number of cuvettes (containers in which chemical reactions occur and which meet the standards for absorbance measurement). In other words, this field allows us to confirm how many times the same repeated treatment was performed in one batch of testing.

[0136] The "Treated TA Conc. [mg / mL]" item indicates the concentration of the treated sample, the "Treated TA Amount [mL / animal]" item indicates the volume of the treated sample, and the "Treated Reagent Conc. [mg or Mm / Quvette]" item indicates the concentration of the reagent treated per cuvette.

[0137] The Experimental Replication item indicates the number of test iterations, and this item allows for verification of reproducibility.

[0138] Figure 44 shows an example screen when the "Test Results" tab is selected on the project details screen, displaying the experimental results. Specifically, it uploads and displays the information entered in the "Test & Progress" tab, and provides a function to modify the information and input test results here. In bioprocessing, generally, substances produced in the upstream (culture process) have impurities removed in the downstream (purification process), and the extent to which impurities are removed from the final product to maintain quality follows the standards recommended or established by the Korea Food and Drug Administration. In this invention, it is possible to quickly confirm the Pass / Fail status against this standard. At this time, the standard value can be set by the laboratory for research purposes, or it can be set more strictly than the recommendation of the Korea Food and Drug Administration.

[0139] In Figure 44, the Test Description item is the name of the test item, and the Test Result item shows the test result.

[0140] The Criteria section lists the standard values ​​that the client company has set in advance. These can be set by the client company that commissioned the test, or they can follow the non-clinical trial standards established by the regulatory body.

[0141] The Status item indicates whether or not the target value is met, and the Completed[Y / N] item indicates whether or not the test has been completed.

[0142] Figure 45 shows an example screen when the "Project Team" tab is selected on the project details screen. It provides a screen where information about the client company can be displayed and edited in a list, and information including the job title, role, and mobile phone number of project team members can be displayed and edited in a list.

[0143] In Figure 45, under "Client Company," the Company Name field is the name of the client company, the Address field is the office address of the client company, the Homepage field is the homepage address where the client company's information is posted, and the Business Type field indicates the type of products or business area that the client company operates in.

[0144] In Figure 45, under "Project Team," the Name field shows the name of the person in charge, the Position field shows their job title / position, the Role field shows their role, and the Phone No. field shows their phone number.

[0145] Figure 46 is an example screen that provides a function to edit information about project team members, as shown in the example screen in Figure 45.

[0146] Figure 47 shows an example screen when the "Documents" tab is selected on the project details screen, providing a screen where documents and files can be uploaded. If the "Add Mandatory Document" button is selected, it provides the functionality to upload a mandatory document, as shown in Figure 48. If the "Add Supplementary Document" button is selected, it provides the functionality to upload a supplementary document, as shown in Figure 49.

[0147] In Figure 47, the "Document Name" field in "Mandatory Document" shows the name of the document that was promised to be provided in advance at the time of the contract, and the "Description" field shows a description of the document.

[0148] In Figure 47, the Document Name field in "Supplementary Documents" indicates documents other than those promised to be provided, and the Description field indicates a description of the document.

[0149] Figure 50 shows an example screen where the "Dashboard" tab is selected on the project details screen, providing a dashboard screen. In this example screen, a dashboard is shown that represents progress analysis, test completion time, etc., using bar graphs, but this is not the only way to provide a dashboard; dashboards can be provided in various formats and configurations.

[0150] In Figure 50, Total Test shows the number of tests performed, Progress Analysis shows the progress of the tests, Test Completion Time shows the time elapsed from sample receipt to test completion, Summarized Results shows the number of tests that met the baseline, and Completion Status by Test Description shows the number of tests that were completed.

[0151] Figure 51 shows an example screen when the "Chat" menu is selected, illustrating the chat menu that provides the chat function.

[0152] In the example shown in Figure 51, a client list displaying client information is shown. When a client you want to chat with is selected and the rightmost ">" button is selected, a chat function is provided that allows you to start a chat, as shown in Figure 52. At this time, it is possible to provide a function for multiple people to chat, such as the CRO, CRO master, and clients of the same CRO company.

[0153] Figures 52 and 53 show examples of the UI / UX of a dedicated application provided to a client terminal in a test management system according to one embodiment of the present invention.

[0154] In Figure 2, when logging in to client terminal 140, a screen is provided where the client ID and password can be entered. When a client ID and password configured to grant client privileges are entered, the client is logged in.

[0155] Figure 53 shows an example screen that, when a client logs in, displays the client's project list in the "Project Status" menu, and when a project is selected from the project list, displays detailed information about that project.

[0156] Furthermore, in the case of client terminal 140, similar to the CRO master terminal 120 and CRO terminal 130 mentioned above, a "Chat" menu is provided that offers a chat function allowing multiple people to chat with each other.

[0157] Figures 54 to 63 show examples of dashboard screens in a dedicated application provided by a test management system according to one embodiment of the present invention.

[0158] Figure 54 shows an example screen where the Dashboard tab is selected, and it is an example screen showing an individual project dashboard that displays information including the progress and results of individual projects.

[0159] Referring to Figure 54, the individual project dashboard displays information such as the total number of tests, progress analysis, test completion time, number of results meeting the criteria, and completion status by test description in various graphs.

[0160] Figure 55 shows an example of a dashboard-style screen provided in the "Activity Report" menu of the CRO master terminal 120, which displays the progress and results of the entire project in which the test is being conducted.

[0161] Referring to Figure 55, the integrated project management dashboard displays information such as the total number of projects, the number of completed or ongoing projects (Project Completion Status), the number of days required from project contract to completion (Project Completion Time), and the number of contracts for each test item (Contract Number for Each Description) in various graphs, which are visual representations.

[0162] In this invention, when the server 200 provides a dashboard function, the dashboard can be provided based on or linked to the entered data. For example, in Figure 20, a dashboard screen can be provided based on the data entered for each item of a project. Alternatively, in Figure 37, during the process of entering data for each contract, the start date and the final completion date, which is the report issuance date, are entered. At this time, the person in charge's information is also entered, so the required time for each test item or project can be checked, and the number of days required for each person in charge can also be checked. In this manner, the server can extract information from the entered data and provide a dashboard.

[0163] This invention makes it possible to understand the work speed and volume of individual employees, identify bottlenecks in specific employees, appropriately distribute tasks, and perform team resource management such as rewarding employees who achieve outstanding results.

[0164] Figure 56 shows an example of a dashboard screen displaying test result analysis information.

[0165] Figure 56 shows a dashboard displaying success / failure (Pass / Fail) analysis graphs for project test items, charts summarizing test results for each individual project, and a graph showing the percentage of organizations providing standard value setting guidelines. For example, if a client requests a test expecting success (PASS) but experiences a high frequency of failures (FAIL), they can understand the cause through the dashboard.

[0166] The graph showing the percentage of organizations providing standard value setting guidelines indicates the proportion of each organization's guidelines that the provided test items comply with.

[0167] Figure 57 shows an example of a dashboard screen displaying the required time.

[0168] Figure 57 shows a dashboard displaying bar graphs showing the number of days required to complete each contracted test item, the total number of days required for the project, and the average number of days required to complete each test item. From this dashboard, patterns for each required time can be identified, and the difference between the estimated time and the actual time can be checked by looking at the data. If the difference is large, the cause can be identified. Furthermore, based on the data, the estimated time required for each test item can be provided to the client before the contract is signed.

[0169] Figure 58 shows an example of a dashboard screen displaying schedule management.

[0170] Figure 58 shows a dashboard displaying graphs showing confirmation of sample receipt and transmission, progress of contracted test items, and the number and percentage of completed test items under contract.

[0171] The sample reception and transmission confirmation graphs show the percentages for before transmission, in transit, and received, while the progress of contracted test items is displayed as a bar graph. Additionally, a graph showing the number and percentage of completed test items under contract displays the percentages for ongoing tests and completed tests.

[0172] Figure 59 shows an example of a dashboard screen displaying sales strategies.

[0173] Figure 59 shows a dashboard displaying bar graphs showing the total number of contracts for each test item, the total number of contracts for each company, and the number of contracts for specific test items per quarter. Customer management and sales strategies can be established through such dashboards.

[0174] Figure 60 shows an example of a dashboard screen displaying team resource management.

[0175] Figure 60 shows a dashboard displaying bar graphs showing the number of projects completed by each CRO representative, the number of clients each CRO representative is responsible for, and the cumulative annual number of working days per CRO representative. Through such a dashboard, it is possible to evaluate whether work is being appropriately distributed among team resources and whether bottlenecks are occurring.

[0176] Figure 61 shows an example of a dashboard screen displaying sample analysis for commissioned testing.

[0177] In Figure 61, the current status of project orders, categorized by therapeutic agent, is displayed as a bar graph. Additionally, the development stage of ordered trial samples is shown in a graph indicating the proportion of drug discovery and preclinical trials. Furthermore, the current status of sample storage locations is displayed as a bar graph. Through this dashboard, the current status of laboratory storage locations can be understood based on the analysis of ordered samples.

[0178] Figure 62 shows an example of a dashboard screen displaying procurement and equipment management.

[0179] Figure 62 shows a dashboard displaying bar graphs showing the average delivery time for each major procurement company, the calibration status of laboratory equipment, and the number of pieces of equipment and materials handled by each person in charge. Through such a dashboard, equipment, facilities, and materials can be managed, and the procurement situation can be understood to manage the supply chain.

[0180] Figure 63 shows an example of a dashboard screen displaying test quality control.

[0181] Figure 63 shows a dashboard where the blank histogram distribution for a specific test item, the negative, positive, and control data for that specific test item, and the variability of inter-test replication are displayed as bar graphs.

[0182] Since the blank value (background value), negative control, and positive control are measured each time a test is performed, regardless of the type of sample, the consistency and reliability of the provided testing service can be understood through the deviation of these values, which in turn represents the quality of the service provided.

[0183] If the control deviation is high in each experiment as shown in the dashboard provided by this invention, it may be necessary to investigate the cause. For example, it may be necessary to check whether there is a problem with the test execution method of a particular experimenter.

[0184] Thus, in this invention, by automatically changing the graph in the dashboard according to the input value at the same time as data input, real-time test management is possible through the dashboard, enabling rapid management decisions.

[0185] Furthermore, according to the present invention, lead times (arrival date - order date) of reagents and consumables can be analyzed through the dashboard, and vendors can be evaluated, including whether or not to continue the business relationship. The expected experimental execution schedule can also be predicted through analysis of the supply chain. Moreover, by organically incorporating the results of supply chain management into business schedule management and viewing them as relationships that influence each other, meaningful results can be derived between individual items.

[0186] According to the present invention, it is possible to record the date of correction or validation of management equipment or devices, and to provide a function that automatically notifies the person in charge via email or text message when the time to perform this periodically approaches.

[0187] Even if the samples differ for each contract, blank values ​​(background values) or control values ​​must be measured each time according to the test method established for most tests. In this invention, deviations from these values ​​can be checked to confirm the consistency and reliability of each test item, i.e., the services provided by the CRO company.

[0188] Although the present invention has been described above using several preferred embodiments, these embodiments are illustrative and not limiting. A person with ordinary skill in the art to which the present invention pertains will understand that various changes and modifications are possible without departing from the spirit of the invention and the scope of rights presented in the appended claims.

Claims

1. A test management system that manages the process of requesting and conducting test work in the life sciences field through a dedicated application, The administrator terminal is a terminal used by the administrator of the company that develops and provides the aforementioned dedicated application, The CRO master terminal is a terminal used by administrators, including the team leader and sales representatives of the CRO company that was commissioned to perform the testing work, The CRO terminal is a terminal used by the person in charge of conducting the tests at the aforementioned CRO company, The client terminal is a terminal used by the person in charge at the client company that commissioned the aforementioned CRO company to perform testing work, A server that provides the administrator terminal, the CRO master terminal, the CRO terminal, and the client terminal with the dedicated application, provides various functions related to testing through the dedicated application, and enables real-time sharing of data and information, A test management system that includes this.

2. The test management system according to claim 1, characterized in that the server grants different permissions to the administrator terminal, the CRO master terminal, the CRO terminal, and the client terminal that log in through the dedicated application, and provides different functions according to those permissions.

3. The test management system according to claim 2, characterized in that the server generates IDs for the CRO master, CRO, and client on the administrator terminal, inputs information for the CRO company and client company, and provides functions for the maintenance of the dedicated application.

4. The test management system according to claim 3, characterized in that the server inputs project information for conducting tests to the CRO master terminal to generate a project, monitors the detailed progress of each project, and provides a chat function between one or more CRO terminals and one or more client terminals.

5. The test management system according to claim 4, characterized in that the server inputs information regarding project subcategories to the CRO terminal, uploads project-related documents, and provides a chat function between one or more CRO master terminals and one or more client terminals.

6. The test management system according to claim 5, characterized in that the server monitors the progress of the project on the client terminal, downloads documents uploaded by the CRO terminal, and provides a chat function between one or more CRO master terminals and one or more CRO terminals.

7. The test management system according to claim 2, characterized in that the server provides a dashboard function that visualizes and displays information related to test management on a screen through the dedicated application.

8. The test management system according to claim 7, characterized in that the server, when providing the dashboard function, provides an individual project dashboard function that displays information including the progress and results of individual projects on which tests are to be conducted.

9. The test management system according to claim 8, characterized in that the server provides the individual project dashboard function to all of the administrator terminal, the CRO master terminal, the CRO terminal, and the client terminal.

10. The test management system according to claim 7, characterized in that the server provides a whole-project integrated management dashboard function that displays the progress and results of the entire project on which the test is being conducted in an integrated manner when providing the dashboard function.

11. The test management system according to claim 10, characterized in that the server provides the integrated project management dashboard function to the CRO master terminal only.

Images