CN113379385B - Clinical research project plan data processing method and device - Google Patents
Clinical research project plan data processing method and device Download PDFInfo
- Publication number
- CN113379385B CN113379385B CN202110653847.XA CN202110653847A CN113379385B CN 113379385 B CN113379385 B CN 113379385B CN 202110653847 A CN202110653847 A CN 202110653847A CN 113379385 B CN113379385 B CN 113379385B
- Authority
- CN
- China
- Prior art keywords
- plan
- completion date
- planned
- expected
- date
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
-
- G—PHYSICS
- G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
- G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
- G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- General Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Health & Medical Sciences (AREA)
- Entrepreneurship & Innovation (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Data Mining & Analysis (AREA)
- Marketing (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Physics & Mathematics (AREA)
- Biomedical Technology (AREA)
- Epidemiology (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Primary Health Care (AREA)
- Public Health (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention relates to a method and a device for processing data of a clinical research project plan, wherein the method comprises the following steps: acquiring template plan data of a clinical study project, wherein the template plan data comprises a plan expected completion date and a plan actual completion date; judging whether the plan expected completion date and the plan actual completion date in the template plan data can be edited or not; if the data can be edited, displaying the edited expected completion date and the actual completion date of the plan; and if the data can not be edited, automatically generating and displaying the planned expected completion date according to a preset time rule, and triggering the planned actual completion date to be updated to the task completion time when the task in the clinical research project or the added task in the center is detected to be completed. By the method and the device, the problem of low management efficiency and accuracy caused by the fact that the clinical research project plan management is carried out on line through documents in a manual mode in the related technology is solved, and the technical effect of online efficient and accurate management of the clinical research project plan is achieved.
Description
Technical Field
The invention relates to the technical field of clinical research project management, in particular to a method and a device for processing clinical research project plan data, computer equipment and a computer readable storage medium.
Background
In the related art, clinical research project plan management is typically conducted on-line and document-by-document in a manual manner. This technical management approach will have the following problems: the clinical research project plan management is not online and is rough; inaccurate, untimely and unintuitive data sources; linkage of planning data is poor; the whole process is manually operated, so that the management efficiency and the accuracy are low; the planned operation records cannot be traced back.
At present, no effective solution is provided for the problem of low management efficiency and accuracy caused by the fact that the clinical research project plan management in the related art is performed on line through documents in a manual mode.
Disclosure of Invention
The present application aims to overcome the defects in the prior art, and provides a method, an apparatus, a computer device and a computer-readable storage medium for processing clinical research project plan data, so as to at least solve the problem of low management efficiency and accuracy caused by the fact that the clinical research project plan management is performed manually online through documents in the related art.
In order to achieve the purpose, the technical scheme adopted by the application is as follows:
in a first aspect, an embodiment of the present application provides a method for processing data of a clinical research project plan, including:
acquiring template plan data of a clinical research project, wherein the template plan data comprises project plan data of the clinical research project and center plan data of a center added in the clinical research project, and the template plan data comprises a plan expected completion date and a plan actual completion date;
judging whether the plan expected completion date and the plan actual completion date in the template plan data are editable or not;
when it is determined that the planned expected completion date and the planned actual completion date in the template planning data are editable, displaying the edited planned expected completion date and the edited planned actual completion date;
when the plan expected completion date and the plan actual completion date in the template plan data are determined to be uneditable, automatically generating and displaying the plan expected completion date according to a preset time rule, and triggering the plan actual completion date to be updated to a task completion time when a task in the clinical research project or a task in the added center is detected to be completed.
In some of these embodiments, upon detecting that a task in the added hub is completed, after triggering the scheduled actual completion date to be updated to a task completion time, the method further comprises:
calculating a project plan completion progress, wherein the project plan completion progress is represented by a ratio of a number of centers that have completed a corresponding task to a total number of centers in the clinical research project, or the project plan completion progress is represented by a ratio of a number of completed tasks to a total number of tasks in the clinical research project.
In some of these embodiments, after displaying the planned expected completion date, the method further comprises:
displaying a planned expected execution time period, wherein a starting time of the planned expected execution time period is an expected planned completion date of a first task of the clinical study or the added center, and an ending time of the planned expected execution time period is an expected planned completion date of a last task of the clinical study or the added center.
In some of these embodiments, displaying the planned expected execution time period includes:
display a marker of expected planned completion dates for each task in the clinical study or the added center.
In some of these embodiments, after displaying the planned expected execution time period, the method further comprises:
when the drag operation of the mark corresponding to the expected plan completion date of the target task is detected, the expected plan completion date of the target task is updated to the date corresponding to the mark after the drag operation.
In some of these embodiments, determining whether the plan expected completion date and the plan actual completion date in the template plan data are editable comprises:
if the template plan data is preset template plan data and a preset date trigger rule exists, determining that the plan expected completion date and the plan actual completion date in the template plan data cannot be edited, wherein the plan expected completion date in the preset template plan data is automatically generated according to the preset time rule, and the preset date trigger rule is used for triggering the plan actual completion date to be updated to task completion time when a task in the clinical research project or a task in the added center is detected to be completed;
and if the template plan data is not the preset template plan data or the preset date trigger rule does not exist, determining that the plan expected completion date and the plan actual completion date in the template plan data can be edited.
In some of these embodiments, after updating the plan expected completion date and the plan actual completion date, the method further comprises:
and recording and storing the updating operation of the planned expected completion date and the planned actual completion date and the occurrence time of the updating operation.
In a second aspect, an embodiment of the present application provides a clinical research project plan data processing apparatus, including:
the system comprises an acquisition unit, a processing unit and a display unit, wherein the acquisition unit is used for acquiring template plan data of a clinical research project, the template plan data comprises project plan data of the clinical research project and center plan data of a center added in the clinical research project, and the template plan data comprises a plan expected completion date and a plan actual completion date;
a judging unit configured to judge whether the planned expected completion date and the planned actual completion date in the template plan data are editable;
a first display unit configured to display the edited planned expected completion date and the edited planned actual completion date when it is determined that the planned expected completion date and the planned actual completion date in the template plan data are editable;
a second display unit, configured to, when it is determined that the planned expected completion date and the planned actual completion date in the template planning data are not editable, automatically generate and display the planned expected completion date according to a preset time rule, and trigger the planned actual completion date to be updated to a task completion time when it is detected that a task in the clinical study item or a task in the added center is completed.
In a third aspect, embodiments of the present application provide a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method for processing clinical study plan data as described in the first aspect above when executing the computer program.
In a fourth aspect, embodiments of the present application provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor, implements the method for processing clinical study plan data as described in the first aspect above.
By adopting the technical scheme, compared with the prior art, the method for processing the clinical research project plan data comprises the steps of obtaining the template plan data of the clinical research project, wherein the template plan data comprises the project plan data of the clinical research project and the center plan data of the center added in the clinical research project, and the template plan data comprises the expected plan completion date and the actual plan completion date; judging whether the plan expected completion date and the plan actual completion date in the template plan data are editable or not; when it is determined that the planned expected completion date and the planned actual completion date in the template planning data are editable, displaying the edited planned expected completion date and the edited planned actual completion date; when the plan expected completion date and the plan actual completion date in the template plan data are determined to be uneditable, the plan expected completion date is automatically generated and displayed according to a preset time rule, and when the fact that the task in the clinical research project or the task in the added center is completed is detected, the plan actual completion date is triggered to be updated to the task completion time, so that the problem that in the related technology, the management efficiency and accuracy are low due to the fact that the clinical research project plan management is performed on line through documents in a manual mode is solved, and the technical effect of online efficient and accurate management of the clinical research project plan is achieved.
The details of one or more embodiments of the application are set forth in the accompanying drawings and the description below to provide a more thorough understanding of the application.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:
fig. 1 is a block diagram of a mobile terminal according to an embodiment of the present application;
FIG. 2 is a flow chart of a method of clinical study plan data processing according to an embodiment of the present application;
FIG. 3a is a schematic diagram of initializing project plan data according to an embodiment of the application;
FIG. 3b is a schematic diagram of initializing central planning data, according to an embodiment of the present application;
FIG. 4 is a schematic illustration of a planned expected execution time period according to an embodiment of the application;
FIG. 5 is a block diagram of a clinical study plan data processing apparatus according to an embodiment of the present application;
fig. 6 is a schematic hardware structure diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application will be described and illustrated below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments provided in the present application without any inventive step are within the scope of protection of the present application.
It is obvious that the drawings in the following description are only examples or embodiments of the present application, and that it is also possible for a person skilled in the art to apply the present application to other similar contexts on the basis of these drawings without inventive effort. Moreover, it should be appreciated that in the development of any such actual implementation, as in any engineering or design project, numerous implementation-specific decisions must be made to achieve the developers' specific goals, such as compliance with system-related and business-related constraints, which may vary from one implementation to another.
Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the specification. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of ordinary skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments without conflict.
Unless defined otherwise, technical or scientific terms referred to herein shall have the ordinary meaning as understood by those of ordinary skill in the art to which this application belongs. Reference to "a," "an," "the," and similar words throughout this application are not to be construed as limiting in number, and may refer to the singular or the plural. The present application is directed to the use of the terms "including," "comprising," "having," and any variations thereof, which are intended to cover non-exclusive inclusions; for example, a process, method, system, article, or apparatus that comprises a list of steps or modules (elements) is not limited to the listed steps or elements, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus. Reference to "connected," "coupled," and the like in this application is not intended to be limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. The term "plurality" as referred to herein means two or more. "and/or" describes an association relationship of associated objects, meaning that three relationships may exist, for example, "A and/or B" may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. Reference herein to the terms "first," "second," "third," and the like, are merely to distinguish similar objects and do not denote a particular ordering for the objects.
The embodiment provides a mobile terminal. Fig. 1 is a block diagram of a mobile terminal according to an embodiment of the present application. As shown in fig. 1, the mobile terminal includes: a Radio Frequency (RF) circuit 110, a memory 120, an input unit 130, a display unit 140, a sensor 150, an audio circuit 160, a wireless fidelity (WiFi) module 170, a processor 180, and a power supply 190. Those skilled in the art will appreciate that the mobile terminal architecture shown in fig. 1 is not intended to be limiting of mobile terminals and may include more or fewer components than shown, or a combination of certain components, or a different arrangement of components.
The following describes each constituent element of the mobile terminal in detail with reference to fig. 1:
the RF circuit 110 may be used for receiving and transmitting signals during information transmission and reception or during a call, and in particular, receives downlink information of a base station and then processes the received downlink information to the processor 180; in addition, the data for designing uplink is transmitted to the base station. In general, RF circuits include, but are not limited to, an antenna, at least one Amplifier, a transceiver, a coupler, a Low Noise Amplifier (LNA), a duplexer, and the like. In addition, the RF circuitry 110 may also communicate with networks and other devices via wireless communications. The wireless communication may use any communication standard or protocol, including but not limited to Global System for Mobile communication (GSM), general Packet Radio Service (GPRS), code Division Multiple Access (CDMA), wideband Code Division Multiple Access (WCDMA), long Term Evolution (LTE), email, short message Service (Short Messaging Service (SMS)), and so on.
The memory 120 may be used to store software programs and modules, and the processor 180 executes various functional applications and data processing of the mobile terminal by operating the software programs and modules stored in the memory 120. The memory 120 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, a phonebook, etc.) created according to the use of the mobile terminal, and the like. Further, the memory 120 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device.
The input unit 130 may be used to receive input numeric or character information and generate key signal inputs related to user settings and function control of the mobile terminal. Specifically, the input unit 130 may include a touch panel 131 and other input devices 132. The touch panel 131, also called a touch screen, can collect touch operations of a user (such as operations of the user on the touch panel 131 or near the touch panel 131 by using any suitable object or accessory such as a finger, a stylus, etc.) thereon or nearby, and drive the corresponding connection device according to a preset program. Alternatively, the touch panel 131 may include two parts, i.e., a touch detection device and a touch controller. The touch detection device detects the touch direction of a user, detects a signal brought by touch operation and transmits the signal to the touch controller; the touch controller receives touch information from the touch sensing device, converts the touch information into touch point coordinates, sends the touch point coordinates to the processor 180, and can receive and execute commands sent by the processor 180. In addition, the touch panel 131 may be implemented by various types such as a resistive type, a capacitive type, an infrared ray, and a surface acoustic wave. The input unit 130 may include other input devices 132 in addition to the touch panel 131. In particular, other input devices 132 may include, but are not limited to, one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.
The display unit 140 may be used to display information input by a user or information provided to the user and various menus of the mobile terminal. The Display unit 140 may include a Display panel 141, and optionally, the Display panel 141 may be configured in the form of a Liquid Crystal Display (LCD), an Organic Light-Emitting Diode (OLED), or the like. Further, the touch panel 131 can cover the display panel 141, and when the touch panel 131 detects a touch operation on or near the touch panel 131, the touch operation is transmitted to the processor 180 to determine the type of the touch event, and then the processor 180 provides a corresponding visual output on the display panel 141 according to the type of the touch event. Although the touch panel 131 and the display panel 141 are shown in fig. 1 as two separate components to implement the input and output functions of the mobile terminal, in some embodiments, the touch panel 131 and the display panel 141 may be integrated to implement the input and output functions of the mobile terminal.
The mobile terminal may also include at least one sensor 150, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor that may adjust the brightness of the display panel 141 according to the brightness of ambient light, and a proximity sensor that may turn off the display panel 141 and/or the backlight when the mobile terminal is moved to the ear. As one of the motion sensors, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally, three axes), detect the magnitude and direction of gravity when stationary, and can be used for applications (such as horizontal and vertical screen switching, related games, magnetometer attitude calibration) for recognizing the attitude of the mobile terminal, and related functions (such as pedometer and tapping) for vibration recognition; as for other sensors such as a gyroscope, a barometer, a hygrometer, a thermometer, and an infrared sensor, which can be configured on the mobile terminal, further description is omitted here.
A speaker 161 and a microphone 162 in the audio circuit 160 may provide an audio interface between the user and the mobile terminal. The audio circuit 160 may transmit the electrical signal converted from the received audio data to the speaker 161, and convert the electrical signal into a sound signal for output by the speaker 161; on the other hand, the microphone 162 converts the collected sound signal into an electric signal, converts the electric signal into audio data after being received by the audio circuit 160, and then outputs the audio data to the processor 180 for processing, and then transmits the audio data to, for example, another mobile terminal via the RF circuit 110, or outputs the audio data to the memory 120 for further processing.
WiFi belongs to a short-distance wireless transmission technology, and the mobile terminal can help a user to receive and send e-mails, browse webpages, access streaming media and the like through the WiFi module 170, which provides wireless broadband internet access for the user. Although fig. 1 shows the WiFi module 170, it is understood that it does not belong to the essential components of the mobile terminal, and it can be omitted or replaced with other short-range wireless transmission modules, such as Zigbee module or WAPI module, etc., as required within the scope not changing the essence of the invention.
The processor 180 is a control center of the mobile terminal, connects various parts of the entire mobile terminal using various interfaces and lines, and performs various functions of the mobile terminal and processes data by operating or executing software programs and/or modules stored in the memory 120 and calling data stored in the memory 120, thereby performing overall monitoring of the mobile terminal. Alternatively, processor 180 may include one or more processing units; preferably, the processor 180 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 180.
The mobile terminal also includes a power supply 190 (e.g., a battery) for powering the various components, which may preferably be logically coupled to the processor 180 via a power management system that may be configured to manage charging, discharging, and power consumption.
Although not shown, the mobile terminal may further include a camera, a bluetooth module, and the like, which will not be described herein.
In this embodiment, the processor 180 is configured to: acquiring template plan data of a clinical research project, wherein the template plan data comprises project plan data of the clinical research project and center plan data of a center added in the clinical research project, and the template plan data comprises a plan expected completion date and a plan actual completion date;
judging whether the plan expected completion date and the plan actual completion date in the template plan data are editable or not;
when it is determined that the planned expected completion date and the planned actual completion date in the template planning data are editable, displaying the edited planned expected completion date and the edited planned actual completion date;
when the plan expected completion date and the plan actual completion date in the template plan data are determined to be uneditable, automatically generating and displaying the plan expected completion date according to a preset time rule, and triggering the plan actual completion date to be updated to a task completion time when a task in the clinical research project or a task in the added center is detected to be completed.
In some of these embodiments, the processor 180 is further configured to: when it is detected that the tasks in the added centers are completed, calculating a project plan completion progress after triggering the plan actual completion date to be updated to a task completion time, wherein the project plan completion progress is represented by a ratio of the number of centers that have completed the corresponding tasks to the total number of centers in the clinical research project, or the project plan completion progress is represented by a ratio of the number of completed tasks to the total number of tasks in the clinical research project.
In some of these embodiments, the processor 180 is further configured to: after displaying the planned expected completion date, displaying a planned expected execution time period, wherein a starting time of the planned expected execution time period is an expected planned completion date for a first task in the clinical study or the added center, and an ending time of the planned expected execution time period is an expected planned completion date for a last task in the clinical study or the added center.
In some of these embodiments, the processor 180 is further configured to: display a marker of expected planned completion dates for each task in the clinical study or the added center.
In some of these embodiments, the processor 180 is further configured to: after displaying the planned expected execution time period, when detecting that drag operation is carried out on a mark corresponding to the expected planned completion date of the target task, updating the expected planned completion date of the target task to the date corresponding to the mark after the drag operation.
In some of these embodiments, the processor 180 is further configured to: if the template plan data is preset template plan data and a preset date trigger rule exists, determining that the plan expected completion date and the plan actual completion date in the template plan data cannot be edited, wherein the plan expected completion date in the preset template plan data is automatically generated according to the preset time rule, and the preset date trigger rule is used for triggering the plan actual completion date to be updated to task completion time when a task in the clinical research project or a task in the added center is detected to be completed;
and if the template plan data is not the preset template plan data or the preset date trigger rule does not exist, determining that the plan expected completion date and the plan actual completion date in the template plan data can be edited.
In some of these embodiments, the processor 180 is further configured to: after updating the planned expected completion date and the planned actual completion date, recording and storing the updating operation of the planned expected completion date and the planned actual completion date and the occurrence time of the updating operation.
The present embodiments provide a method of processing clinical study project plan data. FIG. 2 is a flow chart of a method for processing clinical study plan data according to an embodiment of the application, as shown in FIG. 2, the flow chart includes the following steps:
step S201, acquiring template plan data of a clinical research project, wherein the template plan data comprises project plan data of the clinical research project and center plan data of a center added in the clinical research project, and the template plan data comprises a plan expected completion date and a plan actual completion date;
step S202, judging whether the plan expected completion date and the plan actual completion date in the template plan data can be edited;
step S203, when the plan expected completion date and the plan actual completion date in the template plan data are determined to be editable, displaying the edited plan expected completion date and the edited plan actual completion date;
step S204, when the plan expected completion date and the plan actual completion date in the template plan data are determined to be uneditable, automatically generating and displaying the plan expected completion date according to a preset time rule, and triggering the plan actual completion date to be updated to the task completion time when the task in the clinical research project or the task in the added center is detected to be completed.
Through the steps, template plan data of a clinical research project are obtained, wherein the template plan data comprise project plan data of the clinical research project and center plan data of a center added in the clinical research project, and the template plan data comprise plan expected completion dates and plan actual completion dates; judging whether the plan expected completion date and the plan actual completion date in the template plan data are editable or not; when it is determined that the planned expected completion date and the planned actual completion date in the template planning data are editable, displaying the edited planned expected completion date and the edited planned actual completion date; when the plan expected completion date and the plan actual completion date in the template plan data are determined to be uneditable, the plan expected completion date is automatically generated and displayed according to a preset time rule, and when the fact that the task in the clinical research project or the task in the added center is completed is detected, the plan actual completion date is triggered to be updated to the task completion time, so that the problem that in the related technology, the management efficiency and accuracy are low due to the fact that the clinical research project plan management is performed on line through documents in a manual mode is solved, and the technical effect of online efficient and accurate management of the clinical research project plan is achieved.
According to the embodiment of the application, the online management of the clinical research project plan data based on two dimensionality levels of the project perspective and the center perspective can be realized. And initializing project-level template plan data after the project chief administrator confirms the project, namely the project plan data. And initializing target planning data at the center level after the center is added, namely the center planning data. The template plan data for a clinical study includes project plan data for the clinical study and center plan data for a center added in the clinical study.
As shown in fig. 3a and 3b, the project plan data and the center plan data are initialized, and may include planned expected completion dates (i.e., plan dates in the drawing) and planned actual completion dates (i.e., actual dates in the drawing) of the project plan and the center plan. In addition, various stages and tasks in the project plan and the central plan can be included, and each task corresponds to a planned expected completion date and a planned actual completion date.
After template plan data for a clinical study project is obtained, embodiments of the present application determine whether the plan expected completion date and the plan actual completion date in the template plan data are editable.
As an alternative embodiment, the determining whether the plan expected completion date and the plan actual completion date in the template plan data are editable may include:
if the template plan data is preset template plan data and a preset date trigger rule exists, determining that the plan expected completion date and the plan actual completion date in the template plan data cannot be edited, wherein the plan expected completion date in the preset template plan data is automatically generated according to the preset time rule, and the preset date trigger rule is used for triggering the plan actual completion date to be updated to task completion time when detecting that a task in the clinical research project or a task in the added center is completed;
and if the template plan data is not the preset template plan data or the preset date trigger rule does not exist, determining that the plan expected completion date and the plan actual completion date in the template plan data can be edited.
After editing the clinical research project, firstly, judging whether the acquired template plan data is preset or not, and if not, editing the plan expected completion date and the plan actual completion date; if the date trigger rule is preset, whether the preset date trigger rule exists or not needs to be judged, and whether the planned expected completion date and the planned actual completion date of the plan are allowed to be manually modified or whether the change can be triggered only by task completion or not is defined by a business party according to the date trigger rule; if a date triggering rule exists, the plan expected completion date and the plan actual completion date cannot be edited, the plan expected completion date can only be automatically generated according to the preset time rule, and when the task in the clinical research project or the task in the added center is detected to be completed, the plan actual completion date is triggered to be updated to be the task completion time; if no date trigger rule exists, the plan expected completion date and the plan actual completion date may be edited.
When it is determined that the planned expected completion date and the planned actual completion date in the template plan data are editable, the edited planned expected completion date and the edited planned actual completion date are displayed after being edited.
When the plan expected completion date and the plan actual completion date in the template plan data are determined to be uneditable, automatically generating and displaying the plan expected completion date according to a preset time rule, and triggering the plan actual completion date to be updated to a task completion time when a task in the clinical research project or a task in the added center is detected to be completed.
The preset time rule may be: the day date of the distributor plus 14 days is the planned expected completion date of the central screening plan, plus 34 days is the planned expected completion date of the organization project plan, plus 64 days is the planned expected completion date of the ethical examination plan and the inheritance approval plan, plus 84 days is the planned expected completion date of the contract signing plan, and the like.
PM (project manager), CRA (clinical inspector), CRC (clinical research coordinator) can add or edit project/central hierarchy plans, automatically synchronizing the plan expected completion date to the expected completion date of the corresponding task. CRA (clinical inspector), CRC (clinical study coordinator) update the corresponding dates of the phase at the time of completion of all plans following the clinical study phase.
In some of these embodiments, upon detecting that a task in the added hub is completed, after triggering the scheduled actual completion date to be updated to a task completion time, the method further comprises:
calculating a project plan completion schedule, wherein the project plan completion schedule is represented by a ratio of a number of centers that have completed corresponding tasks to a total number of centers in the clinical study project, or the project plan completion schedule is represented by a ratio of a number of tasks that have completed to a total number of tasks in the clinical study project.
In some embodiments, as shown in fig. 4, after displaying the planned expected completion date, the method further comprises:
displaying a planned expected execution time period, wherein a start time of the planned expected execution time period is an expected planned completion date for a first task of the clinical study or the added center, and an end time of the planned expected execution time period is an expected planned completion date for a last task of the clinical study or the added center.
In some of these embodiments, as shown in FIG. 4, displaying the planned expected execution time period includes:
display a marker of expected planned completion dates for each task in the clinical study or the added center.
In some of these embodiments, after displaying the scheduled expected execution time period, the method further comprises:
when the drag operation of the mark corresponding to the expected plan completion date of the target task is detected, the expected plan completion date of the target task is updated to the date corresponding to the mark after the drag operation.
PM (project manager), CRA (clinical inspector), CRC (clinical research coordinator) can manually drag plan markers in the system to update the corresponding dates.
In some of these embodiments, after updating the plan expected completion date and the plan actual completion date, the method further comprises:
and recording and storing the updating operation of the planned expected completion date and the planned actual completion date and the occurrence time of the updating operation.
In the embodiment of the application, front and back ends are separated, and a dhtmlxGantt technical frame is introduced into a Web end to serve as a Web end display layer. The back end adopts SpringBoot + Java as a development framework and a development language, and provides an interface to a web end to render the planning data in real time according to the Restful Api interface specification. The business system side sends a message to the planning system (for executing the clinical research project planning data processing method in the embodiment of the application) to trigger the modification of the planning date and progress through the rabbitmq when the matter/task is completed.
The method and the device for creating the personalized plan are compatible with the plans required by different project types, initialize different template plans according to different project types, simultaneously support manual creation of the personalized plans, effectively improve management of the project plans, and operate and leave marks on any operation of the plans.
The embodiment of the application can realize the following technical effects:
1. clinical research project plan management based on project and center perspectives is achieved on-line.
2. Data generated during the clinical study (planning date, actual date, operator, planning schedule) is fed back in time during the plan.
3. The clinical research project process is visually displayed, and managers and executors can conveniently master and understand the research plan.
4. Real-time linkage with the planned date after the completion of tasks (items) in the process of clinical research projects is realized.
5. The change operation for the planned start date, the planned end date, the planned actual start date, and the planned actual end date is left with a trace (recording format: by who and when to change the old date to the new date).
It should be noted that the steps illustrated in the above-described flow diagrams or in the flow diagrams of the figures may be performed in a computer system, such as a set of computer-executable instructions, and that, although a logical order is illustrated in the flow diagrams, in some cases, the steps illustrated or described may be performed in an order different than here.
The present embodiment provides a clinical research project plan data processing apparatus, which is used to implement the above embodiments and preferred embodiments, and the description of the apparatus is omitted for brevity. As used below, the terms "module," "unit," "sub-unit," and the like may implement a combination of software and/or hardware of predetermined functions. Although the means described in the embodiments below are preferably implemented in software, an implementation in hardware or a combination of software and hardware is also possible and contemplated.
Fig. 5 is a block diagram showing the configuration of a clinical study plan data processing apparatus according to an embodiment of the present application, which includes, as shown in fig. 5:
an acquiring unit 51, configured to acquire template plan data of a clinical study item, where the template plan data includes item plan data of the clinical study item and center plan data of a center added to the clinical study item, and the template plan data includes a plan expected completion date and a plan actual completion date;
a judging unit 52 configured to judge whether the planned expected completion date and the planned actual completion date in the template plan data are editable;
a first display unit 53 for displaying the edited planned expected completion date and the edited planned actual completion date when it is determined that the planned expected completion date and the planned actual completion date in the template plan data are editable;
a second display unit 54, configured to, when it is determined that the planned expected completion date and the planned actual completion date in the template plan data are not editable, automatically generate and display the planned expected completion date according to a preset time rule, and trigger the planned actual completion date to be updated to a task completion time when it is detected that a task in the clinical study item or a task in the added center is completed.
In some of these embodiments, the apparatus further comprises:
and a calculating unit, configured to calculate a project plan completion progress after triggering the plan actual completion date to be updated to a task completion time when it is detected that the task in the added center is completed, where the project plan completion progress is represented by a ratio of the number of centers that have completed the corresponding task to a total number of centers in the clinical research project, or the project plan completion progress is represented by a ratio of the number of completed tasks to a total number of tasks in the clinical research project.
In some of these embodiments, the apparatus further comprises:
a third display unit for displaying a planned expected execution time period after displaying the planned expected completion date, wherein a start time of the planned expected execution time period is an expected planned completion date of a first task of the clinical study item or the added center, and an end time of the planned expected execution time period is an expected planned completion date of a last task of the clinical study item or the added center.
In some of these embodiments, the third display unit comprises:
a display module for tagging an expected planned completion date for each task in the clinical study or the added center.
In some of these embodiments, the apparatus further comprises:
and the dragging unit is used for updating the expected plan completion date of the target task to the date corresponding to the mark after dragging when detecting that the dragging operation is carried out on the mark corresponding to the expected plan completion date of the target task after the planned expected execution time period is displayed.
In some of these embodiments, the determining unit 52 includes:
a first determining module, configured to determine that the planned expected completion date and the planned actual completion date in the template plan data cannot be edited if the template plan data is preset template plan data and a preset date trigger rule exists, where the planned expected completion date in the preset template plan data is automatically generated according to the preset time rule, and the preset date trigger rule is used to indicate that when it is detected that a task in the clinical research project or a task in the added center is completed, the planned actual completion date is triggered to be updated to a task completion time;
a second determining module, configured to determine that the planned expected completion date and the planned actual completion date in the template plan data are editable if the template plan data is not the preset template plan data or the preset date trigger rule does not exist.
In some of these embodiments, the apparatus further comprises:
and the recording unit is used for recording and storing the updating operation of the planned expected completion date and the planned actual completion date and the occurrence time of the updating operation after updating the planned expected completion date and the planned actual completion date.
The above modules may be functional modules or program modules, and may be implemented by software or hardware. For a module implemented by hardware, the modules may be located in the same processor; or the modules can be respectively positioned in different processors in any combination.
An embodiment provides a computer device. The data processing method for the clinical research project plan in combination with the embodiment of the application can be realized by computer equipment. Fig. 6 is a hardware structure diagram of a computer device according to an embodiment of the present application.
The computer device may comprise a processor 61 and a memory 62 in which computer program instructions are stored.
In particular, the processor 61 may include a Central Processing Unit (CPU), or an Application Specific Integrated Circuit (ASIC), or may be configured to implement one or more Integrated circuits of the embodiments of the present Application.
The memory 62 may be used to store or cache various data files that need to be processed and/or used for communication, as well as possible computer program instructions executed by the processor 61.
In some of these embodiments, the computer device may also include a communication interface 63 and a bus 60. As shown in fig. 6, the processor 61, the memory 62, and the communication interface 63 are connected via a bus 60 to complete mutual communication.
The communication interface 63 is used for implementing communication between modules, devices, units and/or apparatuses in the embodiments of the present application. The communication interface 63 may also enable communication with other components such as: the data communication is carried out among external equipment, image/data acquisition equipment, a database, external storage, an image/data processing workstation and the like.
In addition, in combination with the clinical research project plan data processing method in the above embodiments, the embodiments of the present application may be implemented by providing a computer-readable storage medium. The computer readable storage medium having stored thereon computer program instructions; the computer program instructions, when executed by a processor, implement any of the clinical study project plan data processing methods of the embodiments described above.
The technical features of the embodiments described above may be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the embodiments described above are not described, but should be considered as being within the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (8)
1. A method of processing clinical study project plan data, comprising:
acquiring template plan data of a clinical research project, wherein the template plan data comprises project plan data of the clinical research project and center plan data of a center added in the clinical research project, and the template plan data comprises a plan expected completion date and a plan actual completion date;
judging whether the plan expected completion date and the plan actual completion date in the template plan data are editable or not;
when it is determined that the planned expected completion date and the planned actual completion date in the template planning data are editable, displaying the edited planned expected completion date and the edited planned actual completion date;
when the plan expected completion date and the plan actual completion date in the template plan data are determined to be uneditable, automatically generating and displaying the plan expected completion date according to a preset time rule, and triggering the plan actual completion date to be updated to a task completion time when a task in the clinical research project or a task in the added center is detected to be completed;
calculating a project plan completion progress, wherein the project plan completion progress is represented by a ratio of the number of centers that have completed the corresponding task to a total number of centers in the clinical research project, or the project plan completion progress is represented by a ratio of the number of completed tasks to a total number of tasks in the clinical research project;
wherein determining whether the plan expected completion date and the plan actual completion date in the template plan data are editable comprises:
if the template plan data is preset template plan data and a preset date trigger rule exists, determining that the plan expected completion date and the plan actual completion date in the template plan data cannot be edited, wherein the plan expected completion date in the preset template plan data is automatically generated according to the preset time rule, and the preset date trigger rule is used for triggering the plan actual completion date to be updated to task completion time when a task in the clinical research project or a task in the added center is detected to be completed;
and if the template plan data is not the preset template plan data or the preset date trigger rule does not exist, determining that the plan expected completion date and the plan actual completion date in the template plan data can be edited.
2. The method of claim 1, wherein after displaying the planned expected completion date, the method further comprises:
displaying a planned expected execution time period, wherein a start time of the planned expected execution time period is an expected planned completion date for a first task of the clinical study or the added center, and an end time of the planned expected execution time period is an expected planned completion date for a last task of the clinical study or the added center.
3. The method of claim 2, wherein displaying a scheduled expected execution time period comprises:
display a marker of expected planned completion dates for each task in the clinical study or the added center.
4. The method of claim 3, wherein after displaying the scheduled expected execution time period, the method further comprises:
when the drag operation of the mark corresponding to the expected plan completion date of the target task is detected, the expected plan completion date of the target task is updated to the date corresponding to the mark after the drag operation.
5. The method of any of claims 1-4, wherein after updating the plan expected completion date and the plan actual completion date, the method further comprises:
and recording and storing the updating operation of the planned expected completion date and the planned actual completion date and the occurrence time of the updating operation.
6. A clinical study plan data processing apparatus, comprising:
an acquisition unit, configured to acquire template plan data of a clinical study item, where the template plan data includes item plan data of the clinical study item and center plan data of a center added to the clinical study item, and the template plan data includes a plan expected completion date and a plan actual completion date;
a judging unit configured to judge whether the planned expected completion date and the planned actual completion date in the template plan data are editable;
a first display unit configured to display the edited planned expected completion date and the edited planned actual completion date when it is determined that the planned expected completion date and the planned actual completion date in the template plan data are editable;
a second display unit, configured to, when it is determined that the planned expected completion date and the planned actual completion date in the template planning data are not editable, automatically generate and display the planned expected completion date according to a preset time rule, and when it is detected that a task in the clinical study item or a task in the added center is completed, trigger the planned actual completion date to be updated to a task completion time;
a calculating unit, configured to calculate a project plan completion progress after triggering the plan actual completion date to be updated to a task completion time when it is detected that the task in the added center is completed, where the project plan completion progress is represented by a ratio of a number of centers that have completed a corresponding task to a total number of centers in the clinical research project, or the project plan completion progress is represented by a ratio of a number of completed tasks to a total number of tasks in the clinical research project;
the judging unit is further configured to determine that the planned expected completion date and the planned actual completion date in the template plan data cannot be edited if the template plan data is preset template plan data and a preset date trigger rule exists, where the planned expected completion date in the preset template plan data is automatically generated according to the preset time rule, and the preset date trigger rule is used to indicate that the planned actual completion date is triggered to be updated to a task completion time when it is detected that a task in the clinical research project or a task in the added center is completed; and
and determining that the plan expected completion date and the plan actual completion date in the template plan data are editable if the template plan data is not the preset template plan data or the preset date trigger rule does not exist.
7. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program implements a clinical study plan data processing method as claimed in any one of claims 1 to 5.
8. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out a method of processing clinical study plan data according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110653847.XA CN113379385B (en) | 2021-06-11 | 2021-06-11 | Clinical research project plan data processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110653847.XA CN113379385B (en) | 2021-06-11 | 2021-06-11 | Clinical research project plan data processing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113379385A CN113379385A (en) | 2021-09-10 |
| CN113379385B true CN113379385B (en) | 2023-03-24 |
Family
ID=77574027
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110653847.XA Active CN113379385B (en) | 2021-06-11 | 2021-06-11 | Clinical research project plan data processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113379385B (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110111020A (en) * | 2019-05-16 | 2019-08-09 | 天津飞腾信息技术有限公司 | Retention time restorative procedure, system and medium based on automatic assessment settling time surplus |
| CN111598419A (en) * | 2020-04-30 | 2020-08-28 | 国网浙江省电力有限公司台州供电公司 | Power grid construction management and control method based on Internet and intelligent infrastructure platform system |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7849398B2 (en) * | 2007-04-26 | 2010-12-07 | Xerox Corporation | Decision criteria for automated form population |
| US8160911B2 (en) * | 2009-05-19 | 2012-04-17 | Microsoft Corporation | Project management applications utilizing summary tasks for top-down project planning |
| CN102654911A (en) * | 2011-03-04 | 2012-09-05 | 北京网秦天下科技有限公司 | Method and system for schedule management |
| US20180018614A1 (en) * | 2016-07-15 | 2018-01-18 | Lightning Bolt Solutions, Inc. | Method and apparatus for optimizing constraint-based data |
| CN108428114A (en) * | 2018-03-20 | 2018-08-21 | 网易（杭州）网络有限公司 | Information processing method and device, storage medium, the electronic device of project |
| CN109146302A (en) * | 2018-08-30 | 2019-01-04 | 大冶特殊钢股份有限公司 | Overhaul of the equipments task processing method and system |
| US20200327467A1 (en) * | 2019-04-11 | 2020-10-15 | Tim Davies | Method and system for automated project management workflow and monitoring |
-
2021
- 2021-06-11 CN CN202110653847.XA patent/CN113379385B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110111020A (en) * | 2019-05-16 | 2019-08-09 | 天津飞腾信息技术有限公司 | Retention time restorative procedure, system and medium based on automatic assessment settling time surplus |
| CN111598419A (en) * | 2020-04-30 | 2020-08-28 | 国网浙江省电力有限公司台州供电公司 | Power grid construction management and control method based on Internet and intelligent infrastructure platform system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113379385A (en) | 2021-09-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN104850434B (en) | Multimedia resource method for down loading and device | |
| CN105278937B (en) | A kind of method and device showing pop-up box message | |
| CN107943683B (en) | Test script generation method and device, electronic equipment and storage medium | |
| CN109359324B (en) | BIM-based digital building examination method and device | |
| CN109375907B (en) | Audit flow development method, service audit method, device, equipment and medium | |
| CN104281394A (en) | Method and device for intelligently selecting words | |
| CN108151716A (en) | Flight instruments mapping operating area planing method, device and terminal | |
| CN109309752A (en) | The method and device of mobile terminal and one-handed performance screen | |
| CN110597793A (en) | Data management method and device, electronic equipment and computer readable storage medium | |
| CN106168905A (en) | Text handling method, device and mobile terminal in a kind of mobile terminal | |
| CN105739839B (en) | The selection method and device of multimedia menu item | |
| CN105550316B (en) | The method for pushing and device of audio list | |
| CN112540996A (en) | Service data verification method and device, electronic equipment and storage medium | |
| CN109164965A (en) | Mobile terminal and its method, apparatus and readable storage medium storing program for executing for reducing screen interface | |
| CN114999604A (en) | Visit report generation method and device for clinical research project | |
| CN110413639A (en) | Data check method and device, electronic equipment and computer readable storage medium | |
| CN107465807A (en) | A kind of short message display method and terminal | |
| CN107153715B (en) | Method and device for adding file on page | |
| CN106713627B (en) | Method and device for pushing message in notification bar and mobile terminal | |
| CN109451295A (en) | A kind of method and system obtaining virtual information | |
| CN110753914A (en) | Information processing method, storage medium and mobile terminal | |
| CN107943687B (en) | Equipment sharing method, device, server and storage medium | |
| CN104811898B (en) | A kind of method of acquisition of information, server, terminal and system | |
| CN113379385B (en) | Clinical research project plan data processing method and device | |
| CN115982218A (en) | Method and device for recording inspection traces |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |