CN113270159A

CN113270159A - Interface display method and device of clinical test electronic data acquisition and management system

Info

Publication number: CN113270159A
Application number: CN202110822355.9A
Authority: CN
Inventors: 张浩威; 罗勇; 毛琇; 杨威; 单少辉; 叶高锋; 袁首
Original assignee: Zhejiang Taimei Medical Technology Co Ltd
Current assignee: Zhejiang Taimei Medical Technology Co Ltd
Priority date: 2021-07-21
Filing date: 2021-07-21
Publication date: 2021-08-17
Anticipated expiration: 2041-07-21
Also published as: CN113270159B

Abstract

The invention provides an interface display method and device of a clinical test electronic data acquisition and management system, wherein the method comprises the following steps: arranging the names of the task data items and the names of the visiting data items to be collected into DOM elements, and rendering to form a data collection table, wherein the data collection table comprises a visiting data name column and a visiting data collection column, and each visiting data collection column corresponds to one universal unique identification code in a plurality of universal unique identification codes; arranging the test item name, the phase name, the period name and the visit name of the clinical test into DOM elements, and rendering to form an index bar, wherein each visit name corresponds to one universal unique identification code in the universal unique identification codes; when the first operation is monitored in the rendering area of the visit name, the visit data acquisition column corresponding to the universal unique identification code of the visit name is analyzed into a virtual DOM element, and then the virtual DOM element is rendered to the area of a column adjacent to the visit data name column.

Description

Interface display method and device of clinical test electronic data acquisition and management system

Technical Field

The invention mainly relates to the technical field of information, in particular to an interface display method and device of a clinical test electronic data acquisition and management system.

Background

In the proceeding stage of the clinical trial, a general visit schedule of the trial needs to be established; the method comprises the visit required by the whole test flow and the configuration of different visit task items aiming at each visit; in the clinical test process, a total visit schedule of the test needs to be formulated to act on the whole test stage; because the subjects in the test flow need to be detected and recorded relatively, and the visiting task items required to be performed in different visits also have differences, different configurations and rapid inspection of the visiting task items need to be performed on the visiting task of the test flow, so that the clinical test can be performed efficiently and accurately.

Disclosure of Invention

The technical problem to be solved by the invention is to provide an interface display method of a clinical test electronic data acquisition and management system, which assists in realizing the efficient and accurate implementation of clinical tests.

In order to solve the technical problem, the invention provides an interface display method of a clinical test electronic data acquisition and management system, wherein the clinical test electronic data comprises test project data, phase data, periodic data visit data and task data, and the method comprises the following steps:

arranging task data item names and visiting data item names to be collected into DOM elements, and rendering to form a data collection table, wherein the data collection table comprises a visiting data name column and a visiting data collection column, the visiting data name column comprises task names, the visiting data collection column comprises task data collection filling frames, and each visiting data collection column corresponds to one universal unique identification code in a plurality of universal unique identification codes; arranging the test item name, the phase name, the period name and the visit name of the clinical test into DOM elements, and rendering to form an index bar, wherein each visit name corresponds to one universal unique identification code in the universal unique identification codes; when a first operation is monitored in the rendering area of the visit name, the visit data acquisition column corresponding to the universal unique identification code of the visit name is analyzed into a virtual DOM element, and then the virtual DOM element is rendered to the area of a column adjacent to the visit data name column.

In an embodiment of the present invention, when a first operation is monitored in a rendering area of the access name, parsing the access data collection column corresponding to the universal unique identification code of the access name into a virtual DOM element, and then rendering to an area of a column adjacent to the access data name column includes: when a first operation is monitored in a rendering area of the visit name, a universal unique identification code corresponding to the visit name is acquired, the universal unique identification code corresponding to each visit data acquisition column in the data acquisition table is compared with the universal unique identification code corresponding to the visit name, a visit data acquisition column corresponding to the universal unique identification code corresponding to the visit name is determined, the visit data acquisition column corresponding to the universal unique identification code is analyzed into a virtual DOM element, and then the virtual DOM element is rendered to an area of a column adjacent to the visit data name column.

In an embodiment of the present invention, the method further includes: analyzing the visit data acquisition column corresponding to the universal unique identification code of the visit name into a virtual DOM element, and then rendering the virtual DOM element to an area of a column adjacent to the visit data name column to generate a page return component; and when the second operation on the page returning component is monitored, re-rendering to form the data acquisition table.

In an embodiment of the present invention, the filling content of the task data collection filling box includes whether to perform the testing task and whether to perform a specific component of the testing task.

In an embodiment of the invention, the method further includes merging adjacent consecutive multiple columns of the access data collection columns into one cycle.

In an embodiment of the present invention, data in each of the access data collection columns has a corresponding index value, and grouping adjacent consecutive access data collection columns into one cycle includes determining whether a plurality of the access data collection columns in which the data is located are adjacent consecutive columns according to the index values.

In an embodiment of the present invention, the method further includes: and receiving the repetition times of the period, copying the plurality of rows of the visit data acquisition rows merged into one period to form DOM elements, and rendering to form a second data acquisition table.

In an embodiment of the present invention, the virtual DOM element is implemented by a JavaScript object.

In an embodiment of the present invention, the interface is run on a Web side.

The invention also provides an interface display device of the clinical test electronic data acquisition and management system, which comprises: a memory for storing instructions executable by the processor; and a processor for executing the instructions to implement the method of any preceding claim.

The invention also provides a computer readable medium having stored thereon computer program code which, when executed by a processor, implements a method as in any of the preceding.

Compared with the prior art, the invention has the following advantages: by establishing the relationship between the access name of the index bar and the access data acquisition column in the access task data acquisition table and by specific operation of the access name of the index bar, the access data acquisition column corresponding to the access name can be quickly rendered to the area of a column adjacent to the access data name column, so that the accuracy of service data can be quickly determined by a user of clinical test data acquisition and system, and the high efficiency and the smooth implementation of clinical tests are facilitated.

Drawings

The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the invention and together with the description serve to explain the principle of the invention. In the drawings:

FIG. 1 is a flow chart of an interface presentation method of a clinical trial electronic data collection and management system according to an embodiment of the present application.

FIG. 2 is a schematic illustration of an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application.

FIG. 3 is a schematic illustration of an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application.

FIG. 4 is a schematic illustration of an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application.

FIG. 5 is a schematic illustration of an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application.

FIG. 6 is a schematic illustration of an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application.

FIG. 7 is a fill-in schematic view of a task data collection box of an interface of a clinical trial electronic data collection and management system according to an embodiment of the present application.

FIG. 8 is a system implementation environment diagram of an interface presentation apparatus of a clinical trial electronic data collection and management system according to one embodiment of the present application.

Detailed Description

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in detail below.

In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention, but the present invention may be practiced in other ways than those specifically described herein, and thus the present invention is not limited to the specific embodiments disclosed below.

As used herein, the terms "a," "an," "the," and/or "the" are not intended to be inclusive and include the plural unless the context clearly dictates otherwise. In general, the terms "comprises" and "comprising" merely indicate that steps and elements are included which are explicitly identified, that the steps and elements do not form an exclusive list, and that a method or apparatus may include other steps or elements.

It should be noted that the terms "first", "second", and the like are used to define the components, and are only used for convenience of distinguishing the corresponding components, and the terms have no special meanings unless otherwise stated, and therefore, the scope of protection of the present application is not to be construed as being limited. Further, although the terms used in the present application are selected from publicly known and used terms, some of the terms mentioned in the specification of the present application may be selected by the applicant at his or her discretion, the detailed meanings of which are described in relevant parts of the description herein. Further, it is required that the present application is understood not only by the actual terms used but also by the meaning of each term lying within.

Flow charts are used herein to illustrate operations performed by systems according to embodiments of the present application. It should be understood that the preceding or following operations are not necessarily performed in the exact order in which they are performed. Rather, various steps may be processed in reverse order or simultaneously. Meanwhile, other operations are added to or removed from these processes.

The embodiment of the application describes an interface display method and device of a clinical test electronic data acquisition and management system.

As shown in fig. 1, in some embodiments, the interface display method of the clinical trial electronic data collection and management system of the present application includes, step 101, arranging task data item names and visit data item names to be collected into DOM elements, and rendering the DOM elements to form a data collection table, where the data collection table includes a visit data name column and a visit data collection column, the visit data name column includes task names, and the visit data collection column includes task data collection filling boxes, where each visit data collection column corresponds to one common unique identification code of a plurality of common unique identification codes; 102, arranging the names of task data items and visiting data items to be collected into DOM elements, and rendering the DOM elements to form a data collection table, wherein the data collection table comprises a visiting data name column and a visiting data collection column, the visiting data name column comprises the names of tasks, the visiting data collection column comprises task data collection filling frames, and each visiting data collection column corresponds to one universal unique identification code in a plurality of universal unique identification codes; 103, when a first operation is monitored in the rendering area of the visit name, analyzing the visit data acquisition column corresponding to the universal unique identification code of the visit name into a virtual DOM element, and then rendering to an area of a column adjacent to the visit data name column.

Specifically, in step 101, the names of the task data items and the names of the visit data items to be collected are arranged into DOM elements and rendered to form a data collection table. The data collection table is illustrated, for example, by 201 in fig. 2, and may also be illustrated, for example, by 301 in fig. 3.

The DOM (Document Object Model) is an interface for editing and manipulating HTML (HyperTextMarkup Language) page elements. The HTML DOM defines the standard steps of accessing and manipulating elements in a page corresponding to an HTML document. The DOM structure includes multiple layers of nodes. The multi-level nodes comprise < html > … </html >, < head > … </head >, < body > … </body >, < ul > … </ul >, < li >, and "list item". Where ul denotes Unordered list. li denotes list. When the Web end operates the form components in the form design area by using the corresponding structure of the DOM, one-time updating needs to be performed through traversing nodes of each layer of the DOM.

In some embodiments, the data collection table includes an access data name column and an access data collection column. The access data name column is illustrated, for example, at 202 in FIG. 2, and may also be illustrated, for example, at 302 in FIG. 3. The interview data acquisition columns are distributed, for example, in the 221 region in fig. 2 or, for example, in the 321 region in fig. 3. The visit data acquisition columns are shown in particular as 203, 204, 205, 206, 207 and 208 in fig. 2. The interview data acquisition columns may also be illustrated, for example, as 307, 311, and 313 in FIG. 3. In practical applications, the visit data acquisition columns may be set increasingly according to needs, for example, in a test with more stages, and at this time, the visit data acquisition columns may reach fifty to sixty columns or more.

Each of the visit data acquisition columns corresponds to a universal Unique identification code (UUID) of a plurality of universal Unique identification codes.

After the number of the access data columns is increased to more columns, for example, to six columns, eight columns or ten columns, a horizontal scroll bar may be arranged in the lower area of the page, and the data of the access columns which are continuously increased are viewed through the scrolling operation of the scroll bar.

The access data name column includes, for example, task names, such as illustrated by 210, 211, and 212 in FIG. 2. The interview data name column may also include basic information related to interviews, such as illustrated at 213 and 214 in FIG. 2. When the number of task items is large, namely the task names are also available, different test task items can be checked through the arrangement of the longitudinal rolling strip. In fig. 3, task names include, for example, 'blood routine examination', 'fibrinolysis system examination', 'blood rheology examination', 'examination of proteins and their metabolites', and the like.

In a clinical trial, a trial project may include several phases, a phase may include several cycles, a cycle may include several visits (or referred to as visits), and a visit may include several tasks.

The visit data collection column includes a task data collection fill box. Task data collection fill boxes are illustrated, for example, at 217, 218, and 219 in FIG. 2. In some embodiments, the fill content of the task data collection fill box includes whether to perform the test task and whether to perform a specific component of the test task. The task data filling boxes of fig. 2 and 3 are filled with a '√' (checkmark) mark, for example, to indicate that the test task needs to be performed within a certain visit period. In a more specific embodiment, the specific content of the test task may be set through a more specific option, for example, after the task data filling box fills out the '√' (checkmark) mark, the specific content of the task item is displayed through a specific operation for setting or selecting.

FIG. 7 is a fill-in schematic view of a task data collection box of an interface of a clinical trial electronic data collection and management system according to an embodiment of the present application. Referring to fig. 7, specific contents of the task item of the blood routine examination may be set. Other data of the visit data, such as basic information related to the visit, specifically, such as the number of days in the interval and the window period, can also be filled or set by selecting the task data filling box and displaying specific setting options after specific operations. Other operation components can be arranged in the page according to needs, such as saving and closing operations. Such as save button 289 in fig. 2.

At step 102, the test item name, the phase name, the period name and the visit name of the clinical test are arranged into DOM elements and rendered to form an index bar. The index field 291 is illustrated in fig. 2, for example, and the index field 291 includes a test item name 271, a phase name 231, a cycle name 241, and visit

names

251, 252, 253, 254. The index bar may also be illustrated, for example, as 391 in FIG. 3, with the index bar 391 including, for example, the

access names

355, 359. The names of the test items, the phase names, and the period names in the index column 391 may be labeled with reference to fig. 2, and are not described herein again. The test item name, the phase name, the period name and the visit name in fig. 2 and fig. 3 are examples, and actually can be set, adjusted, added and modified according to the test requirements. Wherein each of the access names corresponds to a universally unique identification code (UUID) of the plurality of universally unique identification codes. Different test items may actually correspond to different cohorts of clinical test subjects or different test protocols, for example, cohort 1 'in figures 2 and 3, i.e. to the' omeprazole enteric capsule … equivalence test ', and different clinical test items may be determined by the selection or setting of cohort 1' or the test protocol.

In step 103, when a first operation is monitored in the rendering area of the visit name, the visit data collection column corresponding to the universal unique identification code of the visit name is analyzed into a virtual DOM element, and then the virtual DOM element is rendered to an area of a column adjacent to the visit data name column.

FIG. 4 is a schematic illustration of an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application. FIG. 5 is a schematic illustration of an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application.

In fig. 4, when a first operation is monitored in the rendering area of the access name 355, for example, a double click is performed on the access name 355, the access data acquisition column corresponding to the universal unique identification code of the access name 355, specifically, the access data acquisition column 307, is parsed into a virtual DOM element, and then is rendered to an area of a column adjacent to the access data name column.

In fig. 5, when a first operation is monitored in a rendering region of an access name 359, for example, a double click is performed on the access name 359, the access data acquisition column corresponding to the universal unique identification code of the access name 359, specifically, the access data acquisition column 313, is parsed into a virtual DOM element, and then rendered to a region of a column adjacent to the access data name column.

According to the technical scheme, the access name of the index bar and the access data acquisition column in the access task data acquisition table are associated, the access data acquisition column corresponding to the access name can be quickly rendered to the area of a column adjacent to the access data name column through specific operation of the access name of the index bar, a user of clinical test data acquisition and a system can quickly determine whether various test tasks need to be performed or whether various test tasks are performed in a corresponding access stage.

When the visit data acquisition table continuously expands the number of columns due to more stages of clinical trials, such as the aforementioned fifty-to-sixty columns or more, it needs to be determined whether various test tasks need to be performed or whether various test tasks have been performed in the corresponding visit stage, and complicated operations and confirmation are required.

The technical scheme of the application establishes the relationship between the access name of the index bar and the access data acquisition column in the access task data acquisition table, can quickly render the access data acquisition column corresponding to the access name to the area of a column adjacent to the access data name column through specific operation of the access name of the index bar, such as double-click operation or single-click operation, enables clinical test data acquisition and a user of a system to quickly determine whether various test tasks are required or not in a corresponding access stage, namely the technical scheme of the application achieves quick presentation of effective data through reorganization and arrangement of service data (specifically, through switching change of two pages for example), greatly reduces the visual accuracy of operators, improves the service operation accuracy, thereby being beneficial to the smooth and effective implementation of clinical tests.

In some embodiments, when a first operation is monitored in a rendering region of the access name, parsing the access data collection column corresponding to the universally unique identification code of the access name into a virtual DOM element, and then rendering to a region of a column adjacent to the access data name column comprises:

when a first operation is monitored in a rendering area of the visit name, a universal unique identification code corresponding to the visit name is acquired, the universal unique identification code corresponding to each visit data acquisition column in the data acquisition table is compared with the universal unique identification code corresponding to the visit name, a visit data acquisition column corresponding to the universal unique identification code corresponding to the visit name is determined, the visit data acquisition column corresponding to the universal unique identification code is analyzed into a virtual DOM element, and then the virtual DOM element is rendered to an area of a column adjacent to the visit data name column.

Specifically, in some embodiments, the DOM node is simulated by a JavaScript object, and for a page that needs to be displayed, the update of the page may be reflected on the JavaScript object all at first. And displaying the current page on the interface through the virtual DOM element simulated by the JavaScript object. The virtual DOM can only operate the updated nodes, and the updating of the page once only through traversing of nodes of each layer of the DOM is avoided, so that the efficiency of displaying the current page is improved, and the realization of quick checking is facilitated.

In some embodiments of the present application, the interface presentation method of the clinical trial electronic data collection and management system further comprises: analyzing the visit data acquisition column corresponding to the universal unique identification code of the visit name into a virtual DOM element, and then rendering the virtual DOM element to an area of a column adjacent to the visit data name column to generate a page return component; and when the second operation on the page returning component is monitored, re-rendering to form the data acquisition table. The page return component is specifically illustrated by component 342 in fig. 4 and 5. Specifically, when a second operation, such as a single-click operation, is monitored on the component 342, the data collection table, such as the data collection table 301 shown in fig. 3, is re-rendered.

In other embodiments of the present application, the interface presentation method of the clinical trial electronic data collection and management system further comprises grouping adjacent consecutive columns of the access data collection into a cycle.

FIG. 6 is a schematic diagram illustrating an interface display of a clinical trial electronic data collection and management system according to an embodiment of the present application. As shown in FIG. 6, the visit

data acquisition columns

303 and 304 may be merged into one cycle.

In a more specific embodiment, the data in each visit data collection column has a corresponding index value, and grouping adjacent consecutive visit data collection columns into a cycle includes judging whether the visit data collection columns in which the data are located are adjacent consecutive columns according to the index values. Specifically, the determination and setting can be realized by, for example, a 'set period' component in fig. 6.

In some embodiments, the interface display method of the clinical trial electronic data collection and management system further includes receiving the repetition times (or called cycle times) of the period, copying the plurality of columns of the access data collection columns merged into one period to form DOM elements, and rendering to form the second data collection table. As illustrated in fig. 6, after receiving the cycle repetition number 2 (or the cycle number 2) in which the access

data collection columns

303 and 304 are merged, the access data collection wide columns 331 and 332 are formed. Data acquisition wide column 331 includes two access data acquisition columns formed with reference to access

data acquisition columns

303 and 304.

According to the technical scheme, the visit data acquisition columns are quickly and conveniently merged into one period, the visit data acquisition columns merged into the one period can be copied to form DOM elements according to the receiving repetition times (or called as cycle times) of the period, the second data acquisition table is rendered, the visit data acquisition table is quickly expanded according to actual requirements, only one visit data acquisition column can be set without one-time operation, the visit data acquisition table cannot be quickly adjusted according to requirements, the efficiency of clinical test data acquisition and management is improved, and clinical tests can be efficiently carried out conveniently.

In the technical solution of the present application, the interface operates on a Web end, for example, and may specifically be a browser end of a computer, a tablet, or other handheld device. The Web end can be connected with the server end through a network.

The application also provides an interface display device of a clinical trial electronic data acquisition and management system, comprising: a memory for storing instructions executable by the processor; and a processor for executing the instructions to implement the method as previously described.

FIG. 8 illustrates a system implementation environment diagram of an interface presentation apparatus of a clinical trial electronic data collection and management system according to an embodiment of the present application. The interface presentation apparatus 800 of the clinical trial electronic data collection and management system may include an internal communication bus 801, a Processor (Processor) 802, a Read Only Memory (ROM) 803, a Random Access Memory (RAM) 804, and a communication port 805. The interface display device 800 of the clinical trial electronic data acquisition and management system is connected to the network through a communication port and connected to the server side. The internal communication bus 801 may enable data communication between the components of the interface presentation apparatus 800 of the clinical trial electronic data collection and management system. The processor 802 may make the determination and issue the prompt. In some embodiments, the processor 802 may be comprised of one or more processors. The communication port 805 may enable sending and receiving information and data from a network. In fig. 8, the communication port 805 may be connected to a server a 806, a server data storage a 807, a server B808, and a server data storage B809 of the server side through a network to implement transmission of corresponding page data. The interface display apparatus 800 of the clinical trial electronic data collection and management system may also include various forms of program storage units and data storage units, such as a Read Only Memory (ROM) 803 and a Random Access Memory (RAM) 804, capable of storing various data files for use in computer processing and/or communications, as well as possible program instructions for execution by the processor 802. The processor executes these instructions to implement the main parts of the method. The results processed by the processor are communicated to the user device through the communication port and displayed on the user interface.

The interface display apparatus 800 of the clinical trial electronic data collection and management system can be implemented as a computer program, stored in a memory, and recorded in the processor 802 for execution, so as to implement the interface display method of the clinical trial electronic data collection and management system of the present application.

The present application also provides a computer readable medium having stored thereon computer program code which, when executed by a processor, implements the interface presentation method of the clinical trial electronic data collection and management system as described above.

Aspects of the present application may be embodied entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in a combination of hardware and software. The above hardware or software may be referred to as "data block," module, "" engine, "" unit, "" component, "or" system. The processor may be one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), digital signal processing devices (DAPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), processors, controllers, microcontrollers, microprocessors, or a combination thereof. Furthermore, aspects of the present application may be represented as a computer product, including computer readable program code, embodied in one or more computer readable media. For example, computer-readable media may include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips … …), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD) … …), smart cards, and flash memory devices (e.g., card, stick, key drive … …).

The computer readable medium may comprise a propagated data signal with the computer program code embodied therein, for example, on a baseband or as part of a carrier wave. The propagated signal may take any of a variety of forms, including electromagnetic, optical, and the like, or any suitable combination. The computer readable medium can be any computer readable medium that can communicate, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device. Program code on a computer readable medium may be propagated over any suitable medium, including radio, electrical cable, fiber optic cable, radio frequency signals, or the like, or any combination of the preceding.

Similarly, it should be noted that in the preceding description of embodiments of the application, various features are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure aiding in the understanding of one or more of the embodiments. This method of disclosure, however, is not intended to require more features than are expressly recited in the claims. Indeed, the embodiments may be characterized as having less than all of the features of a single embodiment disclosed above.

Although the present application has been described with reference to the present specific embodiments, it will be recognized by those skilled in the art that the foregoing embodiments are merely illustrative of the present application and that various changes and substitutions of equivalents may be made without departing from the spirit of the application, and therefore, it is intended that all changes and modifications to the above-described embodiments that come within the spirit of the application fall within the scope of the claims of the application.

Claims

1. An interface display method of a clinical trial electronic data acquisition and management system, wherein the clinical trial electronic data comprises trial project data, phase data, periodic data visit data and task data, and the method comprises the following steps:

arranging task data item names and visiting data item names to be collected into DOM elements, and rendering to form a data collection table, wherein the data collection table comprises a visiting data name column and a visiting data collection column, the visiting data name column comprises task names, the visiting data collection column comprises task data collection filling frames, and each visiting data collection column corresponds to one universal unique identification code in a plurality of universal unique identification codes;

arranging the test item name, the phase name, the period name and the visit name of the clinical test into DOM elements, and rendering to form an index bar, wherein each visit name corresponds to one universal unique identification code in the universal unique identification codes;

when a first operation is monitored in the rendering area of the visit name, the visit data acquisition column corresponding to the universal unique identification code of the visit name is analyzed into a virtual DOM element, and then the virtual DOM element is rendered to the area of a column adjacent to the visit data name column.

2. The interface presentation method of a clinical trial electronic data collection and management system as claimed in claim 1, wherein when a first operation is monitored in the rendering area of the visit name, parsing the visit data collection column corresponding to the universally unique identification code of the visit name into a virtual DOM element, and then rendering to an area of a column adjacent to the visit data name column comprises:

3. The interface presentation method for a clinical trial electronic data collection and management system as claimed in claim 1, further comprising:

analyzing the visit data acquisition column corresponding to the universal unique identification code of the visit name into a virtual DOM element, and then rendering the virtual DOM element to an area of a column adjacent to the visit data name column to generate a page return component;

and when the second operation on the page returning component is monitored, re-rendering to form the data acquisition table.

4. The interface presentation method for a clinical trial electronic data collection and management system as claimed in claim 1, wherein the filling of the task data collection box includes whether the trial task is performed and whether the specific component of the trial task is performed.

5. An interface presentation method for a clinical trial electronic data collection and management system as claimed in claim 1, further comprising merging adjacent consecutive columns of said access data collection into a cycle.

6. The interface presentation method for a clinical trial electronic data collection and management system according to claim 5, wherein the data in each of the access data collection columns has a corresponding index value, and grouping adjacent consecutive access data collection columns into a cycle comprises determining whether the access data collection columns in which the data is located are adjacent consecutive columns according to the index values.

7. An interface presentation method for a clinical trial electronic data collection and management system as claimed in claim 5, the method further comprising:

and receiving the repetition times of the period, copying the plurality of rows of the visit data acquisition rows merged into one period to form DOM elements, and rendering to form a second data acquisition table.

8. The interface presentation method for a clinical trial electronic data collection and management system according to claim 1, wherein the virtual DOM elements are implemented by JavaScript objects.

9. The method for presenting an interface to a clinical trial electronic data collection and management system of claim 1, wherein the interface is run on a Web site.

10. An interface display device of a clinical trial electronic data acquisition and management system, comprising:

a memory for storing instructions executable by the processor; and

a processor for executing the instructions to implement the method of any one of claims 1-9.

11. A computer-readable medium having stored thereon computer program code which, when executed by a processor, implements the method of any of claims 1-9.