CN111126941B - Careplan processing method and device, electronic equipment and storage medium - Google Patents
Careplan processing method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN111126941B CN111126941B CN201911159422.2A CN201911159422A CN111126941B CN 111126941 B CN111126941 B CN 111126941B CN 201911159422 A CN201911159422 A CN 201911159422A CN 111126941 B CN111126941 B CN 111126941B
- Authority
- CN
- China
- Prior art keywords
- care
- plan
- executed
- task
- care plan
- 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/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
Landscapes
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Engineering & Computer Science (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Operations Research (AREA)
- Economics (AREA)
- Marketing (AREA)
- Data Mining & Analysis (AREA)
- Quality & Reliability (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Medical Treatment And Welfare Office Work (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention discloses a care plan processing method, a care plan processing device, electronic equipment and a storage medium. The care plan processing method comprises the following steps: acquiring a care plan; judging the category to which the care plan belongs when the starting condition of the care plan is satisfied; when the care plan is an aperiodic care plan, one or more care tasks to be executed, which need to be executed in the execution period, are generated at the beginning of each execution period, all the care tasks to be executed are displayed, and one care task to be executed in the current execution period is eliminated after an instruction for completing the care task is received in the current execution period. The caretaking plan processing method can process the non-periodic caretaking plan, automatically decompose the non-periodic caretaking plan into corresponding caretaking tasks to be displayed, solve the problem that the current plan decomposition system cannot decompose the non-periodic caretaking plan, improve the working efficiency and facilitate a carer to monitor the completion condition of the caretaking plan.
Description
Technical Field
The present invention relates generally to a care plan processing method, apparatus, electronic device, and storage medium.
Background
Whether in a medical institution or a pension institution, the system can provide complete and high-quality service for patients or nursing objects, and a standard and scientific workflow is not available. PDCA (Plan, do, check, process Act) is widely used in the medical and aged areas, and planning is the beginning of all activities. How to accurately and effectively implement the plan is independent of informationized support.
At present, the automatic decomposition into specific tasks for workers to execute through planning is realized in many fields including medical treatment and aged care, the working efficiency is greatly improved, and the problems of time consumption and incapability of ensuring accuracy caused by manual decomposition in the past are solved. However, in the field of care, there are many living care or other personalized care plans that are merged together by, among other things, physician orders, which are not characterized as being performed at a fixed time as the physician orders, and which, if generated in a manner that the physician orders are processed, cause significant confusion to caregivers. In addition, for the aged care institutions, the work of caring the aged is very heavy, a caretaker spends a lot of time planning each aged, and there is no method capable of helping to reduce the error rate of the plan by realizing the technology of automatically judging the rationality of the plan through a system, especially for the aged applying for long-term care insurance patches, if the service items in the planned plan are not in the specified catalogue, the application of the patches is affected, and a certain influence is brought to the aged.
The above information disclosed in the background section is only for enhancement of understanding of the background of the invention and therefore it may contain information that does not form the prior art that is already known to a person of ordinary skill in the art.
Disclosure of Invention
In the summary, a series of concepts in a simplified form are introduced, which will be further described in detail in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
It is a primary object of the present invention to overcome at least one of the above-mentioned drawbacks of the prior art, and to provide a care plan treatment method comprising:
acquiring a care plan;
judging the category to which the care plan belongs when the starting condition of the care plan is satisfied;
when the care plan is an aperiodic care plan, one or more care tasks to be executed, which need to be executed in the execution period, are generated at the beginning of each execution period, all the care tasks to be executed are displayed, and one care task to be executed in the current execution period is eliminated after an instruction for completing the care task is received in the current execution period.
According to a specific embodiment of the present invention, generating a care task to be performed, which needs to be performed in each execution cycle, at the beginning of the execution cycle includes:
acquiring the duration of the execution period of the care plan, taking the plan starting time as the starting time of the first execution period, and calculating the number of the execution periods and the starting time and the ending time of each execution period according to the plan starting time, the plan ending time and the duration of the execution period;
each time the start time of an execution cycle is reached, a care task to be performed that needs to be performed in the execution cycle is generated.
According to a specific embodiment of the invention, whether the current time is greater than or equal to the end time of the execution period of the care task to be executed is judged, if yes, the care task to be executed is converted into an overdue task to be displayed.
According to a specific embodiment of the present invention, the care plan processing method further includes:
when the care plan is an on-demand care plan, generating a care task to be executed with the empty plan execution time at the plan starting time, displaying the care task to be executed, and immediately regenerating a new care task to be executed until the care plan is finished after the care task to be executed is executed.
According to a specific embodiment of the present invention, the care plan processing method further includes:
when the care plan is a regular care plan, a care task to be executed, which needs to be executed at a specific time point of the day, is generated from the plan starting time to the plan ending time at the beginning of each day, and is displayed at the beginning of each day, and the care task of the day is eliminated after receiving an instruction for completing the care task in the day.
According to a specific embodiment of the present invention, the step of obtaining a care plan comprises:
it is determined whether the service item of the care plan has been historically performed at the service frequency in the care plan, and if not, it is likely that the service frequency is unreasonable.
According to a specific embodiment of the present invention, the step of obtaining a care plan further comprises:
when the cared object can enjoy the nursing subsidy, judging whether the service item of the care plan is in the subsidy catalog, and if the service item is not in the subsidy item, prompting that the service item is not subsidy.
The invention also provides a care plan processing device, which comprises:
the plan acquisition module is used for acquiring a care plan;
the category judging module is used for judging the category to which the care plan belongs when the starting condition of the care plan is met;
and the non-periodic plan decomposition module is used for generating one or more care tasks to be executed in each execution period at the beginning of the execution period and displaying all the care tasks to be executed when the care plan is a non-periodic care plan, and eliminating one care task to be executed in the current execution period after receiving an instruction for completing the care task in the current execution period.
The present invention also proposes a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the care plan processing method described above.
The invention also proposes an electronic device comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the care plan processing method described above via execution of the executable instructions.
As can be seen from the technical scheme, the care plan processing method has the following advantages and positive effects:
the careplan processing method can process the non-periodic careplan, automatically decompose the non-periodic careplan into the corresponding caretasks to be displayed, solve the problem that the current plan decomposition system cannot decompose the non-periodic careplan, improve the working efficiency and facilitate a nursing staff to monitor the completion condition of the careplan.
Drawings
Various objects, features and advantages of the present invention will become more apparent from the following detailed description of the preferred embodiments of the invention, when taken in conjunction with the accompanying drawings. The drawings are merely exemplary illustrations of the invention and are not necessarily drawn to scale. In the drawings, like reference numerals refer to the same or similar parts throughout. Wherein:
FIG. 1 is a flow chart illustrating a care plan processing method according to an exemplary embodiment;
FIG. 2 is a schematic diagram of a care plan processing apparatus, shown in accordance with an exemplary embodiment;
FIG. 3 is a schematic diagram of an electronic device, according to an example embodiment;
fig. 4 is a schematic diagram of a storage medium according to an exemplary embodiment.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. However, the exemplary embodiments can be embodied in many forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The same reference numerals in the drawings denote the same or similar structures, and thus detailed descriptions thereof will be omitted.
Fig. 1 is a flowchart of a care plan processing method in the present embodiment. The care plan processing method includes steps S1 to S6.
S1: acquiring a care plan; step S1 includes steps S11 to S12;
s11: a care plan is formulated by inputting a plan name, a care subject name, a service item name, a service frequency, a plan start time, and a plan end time.
The care object attributes are pre-entered in the care plan management system. The caretaker attributes include information on name, age, sex, height, weight, medical history, address, physical condition, whether or not care subsidies can be enjoyed, and the like. And selecting the care objects to be cared at the care plan management system, and inputting corresponding service items at a plan making interface of the care objects. The parameters of the service item include the service item name, the service frequency, the scheduled start time, and the scheduled end time. The service frequency is a service frequency of the service item, for example, 2 times per day, 1 time per week, and the like. The scheduled start time may be a day of the week, i.e., it is selected to start by a certain day. The planned ending time may also be a date, i.e. it is selected to end a certain day.
The care plan management system may be configured to search for the historical care data of the service item by the service item name or the service item code corresponding to the service item name when the service item name is completely entered, count all service frequencies and the frequency of each service frequency occurrence in the historical care data if the historical care data of the service item is provided, and perform weighted calculation according to the service frequencies and the frequency of each service frequency occurrence to obtain the recommended frequency. For example, the service frequency having the largest number of occurrences may be set as the recommended frequency, or the median of these service frequencies may be set as the recommended frequency. The service frequency of the historical care object closest to the attribute of the care object can be obtained as the recommended frequency according to the attribute of the care object. And finally, pushing the recommended frequency to a frequency filling column of the planning interface.
When selecting service items, the corresponding frequency is recommended, and the self-selection operation can be reduced. The recommended frequency is written into the frequency filling column for modification. When the recommended frequency is modified, the modified frequency is set as the recommended frequency when the care plan of the service item is next formulated for the care object.
S12: checking the rationality of the care plan, if not, sending out a prompt, and if so, entering into a step S13; step S12 includes steps S121 to 122.
S121: it is determined whether the service item of the care plan has been historically executed at the service frequency in the care plan, if so, step S122 is entered, otherwise, the service frequency may not be justified.
For example, all past service frequencies corresponding to the service items of the care plan can be searched from the historical care database, if the service frequency of the service item in the current care plan does not exist in the service frequencies, the service frequency of the care plan is likely to be unreasonable, for example, the service frequency of the care plan is far greater than the actually required service frequency, and the situation can be found.
S122: when the care target can enjoy the nursing patch, it is judged whether or not the service item of the care plan is in the patch catalog, if not, the service item is prompted to have no patch, and if so, the process proceeds to step S13.
The care patch may be, for example, a long-term care insurance patch. The caretaker who enjoys the nursing patch can obtain the patch in the care items specified in the patch catalog. Firstly, judging whether the care object can enjoy the nursing patches according to the care object attribute, and judging whether the nursing items exist in the corresponding patch catalogs if the care object attribute records that the care object can enjoy the nursing patches. If the subsidy list does not exist, the service project is not subsidy, and prompt is needed to be timely carried out so as to avoid the hyperbranched of nursing cost.
S13: storing the care plan;
when the care plan is reasonable, or when the care plan is not reasonable but still confirms to be executed according to the care plan, the care plan is stored. In this embodiment, the care plan is stored in a schedule table, and the schedule table includes fields including: 1. a nursing object, 2, a plan name, 3, a plan state, 4, a service item, 5, a plan starting time, 6, a plan ending time, 7 and a frequency rule. The plan status may thus indicate the status that the plan is in, e.g., a pending plan, an executing plan, and a completed plan. The plan state of the care plan newly stored in the plan table is set as the plan to be executed. The frequency rule is used for indicating the frequent execution degree of the care task corresponding to the care plan. The category information is used to indicate the category of the care plan, while the category of the plan can also be divided according to frequency rules. The categories of care plans are classified into on-demand plans, periodic plans, and unscheduled plans.
A care plan for which care tasks have no execution time is planned as needed, and the care tasks in the care plan are executed only when the care object needs.
The care plan for which care tasks need to be performed at a specific point in time is regularly planned. For example, at 9 per day: care plan for 00 blood pressure volumes.
The unscheduled plan is not necessarily performed at a particular point in time for its care tasks, but only a care plan that is completed within the execution period. For example, a care plan with mental-comfort is performed three times per week.
S2: when the start condition of the care plan is satisfied, the start of the care plan is triggered, and the process proceeds to step S3.
The start condition of the care plan may be that the time reaches the plan start time as the start condition, and execution of the care plan is started when the time reaches the plan start time. The starting condition of the care plan may also be a care plan starting instruction issued by a care target or a care worker, and the care plan is started immediately after the care plan management system receives the instruction.
In the present embodiment, the schedule table is scanned every predetermined time interval, and it is searched whether or not there is a care plan whose plan start time is equal to or exceeds the current time and whose plan state is a plan to be executed. The predetermined time interval may be 24 hours. If the plan starting time is equal to or exceeds the current time and the plan state is the plan to be executed, triggering to start the plan.
S3: judging the category to which the care plan belongs;
after the care plan is started, the category to which the care plan belongs is judged, and a corresponding care plan decomposition engine is called according to the category to which the care plan belongs to generate a care task.
Determining the category of care plans may be determined according to frequency rules in the schedule. Whether the care plan is a periodic care plan, an aperiodic care plan, or an on-demand care plan can be obtained according to the frequency rules.
Only one plan execution time point for executing the care task in the frequency rule of the regular care plan;
the frequency rule of the non-periodic care plan has a duration of the execution period and a number of care tasks per execution period.
The frequency rules for on-demand care plans are null.
The step of determining the category to which the care plan belongs may include S31 to S32.
S31: judging whether the care plan is an aperiodic care plan according to the frequency rule, if so, entering a step S4, otherwise, entering a step S32;
s32: and judging whether the care plan is an on-demand care plan according to the frequency rule, if so, entering a step S5, otherwise, entering a step S6.
S4: when the care plan is an aperiodic care plan, generating all care tasks to be executed, which need to be executed in the execution period, at the beginning of each execution period, displaying the care tasks to be executed, and eliminating one care task to be executed in the current execution period after receiving an instruction for completing the care task in the current execution period; step S4 includes steps S41 to S46.
S41: the starting time and the ending time of each execution period of the care plan are acquired, and all care tasks to be executed, which need to be executed in one execution period, are generated when the current time reaches the starting time of the execution period.
In this embodiment, a task table is previously established. All tasks are stored in the task table. The task table comprises 1, a plan name, 2, a task name, 3, a task state, 4, a service item, 5, a plan execution time, 6 and an actual execution time. The task name may be determined from the service content of the service item. Each service item is pre-associated with a task name, and a task name is automatically generated from the service item when decomposing the care plan. The task state of all the care tasks newly stored in the task table is set as the care task to be executed.
According to the frequency rule of the non-periodic care plan, the duration of the execution period of the care plan is obtained, then the plan starting time is taken as the starting time of the first execution period, and the number of the execution periods, the starting time and the ending time of each execution period are calculated according to the plan starting time, the plan ending time and the duration of the execution period.
Whenever the starting time of an execution period is reached, the care task to be executed, which needs to be executed in the execution period, is decomposed and stored into a task table. For example, three mental tasks are generated when three mental tasks are needed to be performed every week.
S42: and displaying all the care tasks to be executed in the current execution period.
After each execution cycle begins to decompose the care tasks, the care tasks to be executed are displayed. These care tasks to be performed may be sent to the mobile terminal of the caregiver for display. The mobile terminal can be an electronic device such as a mobile phone, a tablet computer and the like. Or it may be that the care tasks to be performed are sent to the care facility's display screen for viewing by the caregiver.
S43: and eliminating one care task to be executed in the current execution period after receiving an instruction for completing the care task in the current execution period.
After the caretaker finishes a care task, a command for finishing the care task is sent to the care plan management system through the mobile terminal, and the command can be sent to the care plan management system by clicking a button for finishing the task correspondingly arranged in a display area of the care task in the mobile terminal.
After receiving an instruction, the care plan management system eliminates the care task corresponding to the instruction from the mobile terminal of the nursing staff and changes the task state of the care task in the task list into an executed task.
S44: judging whether the current time is greater than or equal to the end time of the execution period of the care task to be executed, if so, entering a step S45, otherwise, repeating the step S44;
s45: and converting the care task to be executed into overdue task for display.
And periodically scanning all the care tasks to be executed in the task table, and if the care tasks with the task states of the care tasks to be executed and the current time being greater than or equal to the ending time of the execution period are found in the task table, modifying the task states of the care tasks to be overdue, and modifying the care tasks to be executed in the mobile terminal of the nursing staff to be overdue tasks to be displayed.
S46: and ending the care plan when the current time is greater than or equal to the plan ending time.
When the schedule is scanned, if the schedule state is found that the schedule end time of the care schedule being executed or to be executed is smaller than the current time, the schedule state of the care schedule is marked as ended.
In a specific embodiment, the careplan for non-periodic execution is 1 week 3 care tasks, and no point of day is specified to execute the care tasks, the plan engine generates 3 care tasks to be executed in the database, the states of the tasks are to be executed, the plan execution time is [ monday 00:00-monday 23:59 ], the caretaker can see the 3 tasks through the APP of the mobile terminal, if the tasks are not executed today, the 3 tasks are continuously displayed on the APP in the open day; if the 3 care tasks are performed 1, the rest 2 are displayed on the next day until the care tasks are all performed; if the care task is not performed, the APP displays that the care task is overdue; by the time of the next monday, the planning engine continues to generate 3 tasks to be performed and repeats the above process. The decomposition is continued until the planned ending time point, and the planned ending time point is exceeded, and the state of the plan is modified to be ended.
S5: when the care plan is an on-demand care plan, generating a care task to be executed with the empty plan execution time at the plan starting time, displaying the care task to be executed, and immediately regenerating a new care task to be executed until the care plan is finished after the care task to be executed is executed. Step S5 includes steps S51 to S54.
S51: generating a care task to be executed with the planned execution time being empty at the planned starting time of the care plan;
and generating a care task to be executed with the planned execution time being empty at the planned starting time of the care plan, and storing the care task into a task table.
S52: displaying the care task to be executed;
these care tasks to be performed may be sent to the mobile terminal of the caregiver for display. The mobile terminal can be an electronic device such as a mobile phone, a tablet computer and the like. Or it may be that the care tasks to be performed are sent to the care facility's display screen for viewing by the caregiver.
S53: after receiving the instruction to complete the care task, the care task to be executed is eliminated and then a care task to be executed is regenerated, and the process proceeds to S52.
After the carer finishes the care task, the mobile terminal sends an instruction for finishing the care task to the care plan management system, wherein a button for finishing the task is correspondingly arranged in a display area of the care task in the mobile terminal, and the instruction can be sent to the care plan management system by clicking the button. A new care plan is generated immediately after a care plan is completed.
S54: and ending the care plan when the current time is greater than or equal to the plan ending time.
When the schedule is scanned, if the schedule state is found that the schedule end time of the care schedule being executed or to be executed is smaller than the current time, the schedule state of the care schedule is marked as ended. At the same time, a new care plan to be performed is not being generated.
In a specific embodiment, decomposing an on-demand care plan, firstly generating a care task to be executed in a database, wherein the planned execution time of the care task is empty, and a carer can see the task to be executed at any time through the APP; if the plan to be executed is executed, the state is changed into executed, the planning engine generates a care task to be executed again, and a carer can see the care task to be executed through the APP, so that the characteristics of on-demand execution are met; the decomposition continues until the planned ending time point, after which the state of the plan is modified to be ended.
S6: when the care plan is a regular care plan, a care task to be executed, which needs to be executed at a specific time point of the day, is generated from the beginning of each day between the plan starting time and the plan ending time, and the care task to be executed is displayed at the beginning of each day, and the care task of the day is eliminated after receiving an instruction for completing the care task in the day. Step S6 includes steps S61 to S66.
S61: generating a care task to be executed, which needs to be executed at a specific time point of the day, every day from the plan starting time of the care plan, and displaying the care task to be executed.
After the planned starting time is started, a care task to be executed, which needs to be executed at a specific time point of the day, is stored in the task table every day. For example, a performance deadline of 9 per day is generated: 00 to be subjected to care tasks.
S62: the care task to be performed is displayed beginning on the same day.
These care tasks to be performed may be sent to the mobile terminal of the caregiver for display. The mobile terminal can be an electronic device such as a mobile phone, a tablet computer and the like. Or it may be that the care tasks to be performed are sent to the care facility's display screen for viewing by the caregiver.
S63: and eliminating the care task to be executed on the same day after receiving the instruction for completing the care task.
After the caretaker performs the care task on the same day, the mobile terminal sends an instruction for completing the care task to the care plan management system, wherein a button for completing the task is correspondingly arranged in a display area of the care task in the mobile terminal, and the instruction can be sent to the care plan management system by clicking the button.
After receiving an instruction, the care plan management system eliminates the care task corresponding to the instruction from the mobile terminal of the nursing staff and changes the task state of the care task in the task list into an executed task.
S64: judging whether the current time is greater than or equal to the planned execution time of the care task to be executed, if so, entering a step S65, otherwise, repeating the step S64;
s65: and converting the care task to be executed into overdue task for display.
And periodically scanning all the care tasks to be executed in the task table, and if the care tasks with the task states of the care tasks to be executed and the current time being greater than or equal to the scheduled execution time are found in the task table, modifying the task states of the care tasks to be overdue, and simultaneously modifying the care tasks to be executed in the mobile terminal of the nursing staff to be overdue tasks to be displayed.
S66: and ending the care plan when the current time is greater than or equal to the plan ending time.
When the schedule is scanned, if the schedule state is found that the schedule end time of the care schedule being executed or to be executed is smaller than the current time, the schedule state of the care schedule is marked as ended.
Referring to fig. 2, the present invention also proposes a care plan processing apparatus 1, which includes: a plan acquisition module 11, a category judgment module 12, and an aperiodic plan decomposition module 13.
The plan acquisition module 11 is used to acquire care plans.
The category judgment module 12 is used for judging the category to which the care plan belongs when the starting condition of the care plan is satisfied.
The non-periodic plan decomposition module 13 is configured to, when the care plan is a non-periodic care plan, generate, at the beginning of each execution period, one or more care tasks to be performed in the execution period, and display all the care tasks to be performed, and after receiving an instruction to complete the care task in the current execution period, eliminate one care task to be performed in the current execution period.
Further, the aperiodic plan decomposition module 13 further includes a period division module and a task generation module.
The period dividing module is used for obtaining the duration of the execution period of the care plan, taking the plan starting time as the starting time of the first execution period, and calculating the number of the execution periods and the starting time and the ending time of each execution period according to the plan starting time, the plan ending time and the duration of the execution period;
the task generating module is used for generating a care task to be executed, which needs to be executed in an execution period, every time the starting time of the execution period is reached.
Further, the unscheduled plan decomposition module 13 also includes an overdue conversion module.
The overdue conversion module is used for judging whether the current time is greater than or equal to the end time of the execution period of the care task to be executed, and if so, converting the care task to be executed into the overdue task to be displayed.
Further, the care plan processing apparatus 1 further includes an on-demand plan decomposition module 14.
The on-demand plan decomposition module is used for generating a to-be-executed care task with the empty plan execution time at the plan starting time and displaying the to-be-executed care task when the care plan is an on-demand care plan, and regenerating a new to-be-executed care task immediately after the to-be-executed care task is executed until the care plan is ended.
Further, the care plan processing apparatus 1 further includes a periodic plan decomposition module 15.
The periodic plan decomposition module is used for generating a care task to be executed, which needs to be executed at a specific time point of the day, from the plan starting time to the plan ending time when the care plan is a periodic care plan, displaying the care task to be executed at the day starting time, and eliminating the care task of the day after receiving an instruction for completing the care task in the day.
Further, the plan acquisition module 11 further includes a rationality judgment module;
the rationality judging module is used for judging whether the service items of the care plan are executed at the service frequency in the care plan historically or not, and if not, prompting that the service frequency is possibly unreasonable.
Further, the plan acquisition module 11 further includes a subsidy judgment module.
The subsidy judging module is used for judging whether the service item of the care plan is in the subsidy catalog or not when the cared object can enjoy the care subsidy, and prompting that the service item is not subsidy if the service item is not in the subsidy item.
An electronic device 800 according to such an embodiment of the invention is described below with reference to fig. 3. The electronic device 800 shown in fig. 3 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 3, the electronic device 800 is embodied in the form of a general purpose computing device. Components of electronic device 800 may include, but are not limited to: the at least one processing unit 810, the at least one memory unit 820, and a bus 830 connecting the various system components, including the memory unit 820 and the processing unit 810.
Wherein the storage unit stores program code that is executable by the processing unit 810 such that the processing unit 810 performs steps according to various exemplary embodiments of the present invention described in the above section of the "exemplary method" of the present specification.
The storage unit 820 may include readable media in the form of volatile storage units, such as Random Access Memory (RAM) 8201 and/or cache memory 8202, and may further include Read Only Memory (ROM) 8203.
The electronic device 800 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), one or more devices that enable an insurer to interact with the electronic device 800, and/or any device (e.g., router, modem, etc.) that enables the electronic device 800 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 850. Also, electronic device 800 may communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet, through network adapter 860. As shown, network adapter 860 communicates with other modules of electronic device 800 over bus 830. It should be appreciated that although not shown, other hardware and/or software modules may be used in connection with electronic device 800, including, but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a usb disk, a mobile hard disk, etc.) or on a network, and include several instructions to cause a computing device (may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the care plan processing method according to the embodiments of the present disclosure.
In an exemplary embodiment of the present disclosure, a computer-readable storage medium having stored thereon a program product capable of implementing the care plan processing method of the present specification is also provided. In some possible embodiments, the various aspects of the invention may also be implemented in the form of a program product comprising program code for causing a terminal device to carry out the steps according to the various exemplary embodiments of the invention as described in the "exemplary methods" section of this specification, when said program product is run on the terminal device.
Referring to fig. 4, a program product 900 for implementing the care plan processing method described above, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and which may be run on a terminal device, such as a personal computer, is described according to an embodiment of the present invention. However, the program product of the present invention is not limited thereto, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium would include the following: an electrical connection having one or more wires, a portable disk, a hard disk, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The computer readable signal medium may include a data signal propagated in baseband or as part of a carrier wave with readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Program code for carrying out operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the insurer computing device, partly on the insurer device, as a stand-alone software package, partly on the insurer computing device, partly on a remote computing device, or entirely on a remote computing device or server. In the case of remote computing devices, the remote computing device may be connected to the insurance client computing device through any kind of network, including a Local Area Network (LAN) or Wide Area Network (WAN), or may be connected to an external computing device (e.g., connected over the internet using an internet service provider).
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit in accordance with embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
Furthermore, although the steps of the methods in the present disclosure are depicted in a particular order in the drawings, this does not require or imply that the steps must be performed in that particular order or that all illustrated steps be performed in order to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step to perform, and/or one step decomposed into multiple steps to perform, etc.
From the above description of embodiments, those skilled in the art will readily appreciate that the example embodiments described herein may be implemented in software, or may be implemented in software in combination with the necessary hardware. Thus, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (may be a CD-ROM, a U-disk, a mobile hard disk, etc.) or on a network, including several instructions to cause a computing device (may be a personal computer, a server, a mobile terminal, or a network device, etc.) to perform the method according to the embodiments of the present disclosure.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any adaptations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
Although the invention has been disclosed with reference to certain embodiments, numerous variations and modifications may be made to the described embodiments without departing from the scope and scope of the invention. It is to be understood, therefore, that the invention is not to be limited to the specific embodiments disclosed and that it is to be defined by the scope of the appended claims and their equivalents.
Although the invention has been disclosed with reference to certain embodiments, numerous variations and modifications may be made to the described embodiments without departing from the scope and scope of the invention. It is to be understood, therefore, that the invention is not to be limited to the specific embodiments disclosed and that it is to be defined by the scope of the appended claims and their equivalents.
Claims (9)
1. A care plan processing method comprising:
acquiring a care plan;
judging the category to which the care plan belongs when the starting condition of the care plan is satisfied;
when the care plan is an aperiodic care plan, generating one or more care tasks to be executed, which need to be executed in the execution period, at the beginning of each execution period, displaying all the care tasks to be executed, and eliminating one care task to be executed in the current execution period after receiving an instruction for completing the care task in the current execution period;
when the care plan is an on-demand care plan, generating a care task to be executed with the empty plan execution time at the plan starting time, displaying the care task to be executed, and immediately regenerating a new care task to be executed until the care plan is finished after the care task to be executed is executed.
2. A care plan processing method as recited in claim 1, wherein generating a care task to be performed that needs to be performed in each execution period at the beginning of the execution period comprises:
acquiring the duration of the execution period of the care plan, taking the plan starting time as the starting time of the first execution period, and calculating the number of the execution periods and the starting time and the ending time of each execution period according to the plan starting time, the plan ending time and the duration of the execution period;
each time the start time of an execution cycle is reached, a care task to be performed that needs to be performed in the execution cycle is generated.
3. A care plan processing method as claimed in claim 2, characterized in that it is determined whether the current time is greater than or equal to the end time of the execution cycle in which the care task to be executed is located, and if so, the care task to be executed is converted into an overdue task to be displayed.
4. A care plan processing method as recited in claim 1, wherein said care plan processing method further comprises:
when the care plan is a regular care plan, a care task to be executed, which needs to be executed at a specific time point of the day, is generated from the plan starting time to the plan ending time at the beginning of each day, and is displayed at the beginning of each day, and the care task of the day is eliminated after receiving an instruction for completing the care task in the day.
5. A care plan processing method as recited in claim 1, wherein the step of obtaining a care plan comprises:
it is determined whether the service item of the care plan has been historically performed at the service frequency in the care plan, and if not, it is likely that the service frequency is unreasonable.
6. A care plan processing method as recited in claim 1, wherein the step of obtaining a care plan further comprises:
when the cared object can enjoy the nursing subsidy, judging whether the service item of the care plan is in the subsidy catalog, and if the service item is not in the subsidy item, prompting that the service item is not subsidy.
7. A care plan processing apparatus comprising:
the plan acquisition module is used for acquiring a care plan;
the category judging module is used for judging the category to which the care plan belongs when the starting condition of the care plan is met;
the non-periodic plan decomposition module is used for generating one or more care tasks to be executed, which need to be executed in each execution period, at the beginning of the execution period when the care plan is a non-periodic care plan, displaying all the care tasks to be executed, and eliminating one care task to be executed in the current execution period after receiving an instruction for completing the care task in the current execution period;
and the on-demand plan decomposition module is used for generating a to-be-executed care task with the empty plan execution time at the plan starting time and displaying the to-be-executed care task when the care plan is the on-demand care plan, and regenerating a new to-be-executed care task immediately after the to-be-executed care task is executed until the care plan is ended.
8. A computer-readable storage medium, on which a computer program is stored, characterized in that the computer program, when executed by a processor, implements the care plan processing method of any one of claims 1 to 6.
9. An electronic device, comprising:
a processor; and
a memory for storing executable instructions of the processor;
wherein the processor is configured to perform the care plan processing method of any one of claims 1 to 6 via execution of the executable instructions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911159422.2A CN111126941B (en) | 2019-11-22 | 2019-11-22 | Careplan processing method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911159422.2A CN111126941B (en) | 2019-11-22 | 2019-11-22 | Careplan processing method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111126941A CN111126941A (en) | 2020-05-08 |
| CN111126941B true CN111126941B (en) | 2023-06-16 |
Family
ID=70496439
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911159422.2A Active CN111126941B (en) | 2019-11-22 | 2019-11-22 | Careplan processing method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111126941B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111708625A (en) * | 2020-06-16 | 2020-09-25 | 中国建设银行股份有限公司 | Multi-user task execution method, device, equipment and storage medium |
| CN112862263A (en) * | 2021-01-18 | 2021-05-28 | 长沙市到家悠享网络科技有限公司 | Task execution supervision method, device, equipment and storage medium |
| CN116344016B (en) * | 2023-04-23 | 2024-04-26 | 深圳作为科技有限公司 | Timing task execution method of networking nursing machine and related system |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0619916A (en) * | 1992-06-30 | 1994-01-28 | Fuji Xerox Co Ltd | Plan notifying device |
| JP2005250627A (en) * | 2004-03-02 | 2005-09-15 | Hu-Tech Co Ltd | Memory auxiliary system |
| JP2006139625A (en) * | 2004-11-12 | 2006-06-01 | Update:Kk | Care service support system |
| KR20140069603A (en) * | 2012-11-29 | 2014-06-10 | 박원일 | Control apparatus and method for displaying user's plan for providing task display in time domain |
| CN104575215A (en) * | 2013-10-09 | 2015-04-29 | 郑夙芬 | 3D nursing situational simulation digital learning system |
| CN104956391A (en) * | 2012-09-13 | 2015-09-30 | 帕克兰临床创新中心 | Clinical dashboard user interface system and method |
| CN109615317A (en) * | 2018-11-20 | 2019-04-12 | 泰康保险集团股份有限公司 | The generation method and device of work plan |
Family Cites Families (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP4296245B2 (en) * | 2002-02-14 | 2009-07-15 | 博志 山崎 | Medical work support apparatus and system |
| TW200808267A (en) * | 2006-08-15 | 2008-02-16 | Coretech Kuowledge Inc | Medical care supporting system |
| US20110246220A1 (en) * | 2010-03-31 | 2011-10-06 | Remcare, Inc. | Web Based Care Team Portal |
| US20120303404A1 (en) * | 2011-03-14 | 2012-11-29 | ClearCare, Inc. | System and apparatus for generating work schedules |
| US20130290052A1 (en) * | 2012-04-30 | 2013-10-31 | Frank SETTINO | Methods and systems for managing renovation of a property |
| GB2515991A (en) * | 2013-03-19 | 2015-01-14 | Paul Clark | Online calendar access device for elderly people |
| JP2017513125A (en) * | 2014-03-28 | 2017-05-25 | コーニンクレッカ フィリップス エヌ ヴェＫｏｎｉｎｋｌｉｊｋｅ Ｐｈｉｌｉｐｓ Ｎ．Ｖ． | Smartphone-based multiple patient work list (SPWL) |
| CN104361444B (en) * | 2014-11-05 | 2018-06-05 | 苏永静 | The method and its system of a kind of arrangement of nursing shifts |
| US20170091421A1 (en) * | 2015-09-30 | 2017-03-30 | International Business Machines Corporation | Modification of Personalized Health Care Plans Based on Patient Adherence to Patient Actions |
| CN105761187A (en) * | 2016-02-15 | 2016-07-13 | 苏州慈乐圆投资管理有限公司 | Intelligent nursing management alarm system and method |
| CN106897561B (en) * | 2017-02-27 | 2020-06-05 | 鄂东医疗集团市中心医院 | JCI-CCPC team care and disease information management system |
| US20190206566A1 (en) * | 2017-12-28 | 2019-07-04 | Vocational Training Council | Movement disorders monitoring and treatment support system for elderly care |
| TWM580787U (en) * | 2019-03-12 | 2019-07-11 | 長庚學校財團法人長庚科技大學 | Nursing service reminder system |
| CN109978512A (en) * | 2019-04-10 | 2019-07-05 | 上海外高桥造船有限公司 | The control method of project management system, electronic equipment, storage medium |
-
2019
- 2019-11-22 CN CN201911159422.2A patent/CN111126941B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH0619916A (en) * | 1992-06-30 | 1994-01-28 | Fuji Xerox Co Ltd | Plan notifying device |
| JP2005250627A (en) * | 2004-03-02 | 2005-09-15 | Hu-Tech Co Ltd | Memory auxiliary system |
| JP2006139625A (en) * | 2004-11-12 | 2006-06-01 | Update:Kk | Care service support system |
| CN104956391A (en) * | 2012-09-13 | 2015-09-30 | 帕克兰临床创新中心 | Clinical dashboard user interface system and method |
| KR20140069603A (en) * | 2012-11-29 | 2014-06-10 | 박원일 | Control apparatus and method for displaying user's plan for providing task display in time domain |
| CN104575215A (en) * | 2013-10-09 | 2015-04-29 | 郑夙芬 | 3D nursing situational simulation digital learning system |
| CN109615317A (en) * | 2018-11-20 | 2019-04-12 | 泰康保险集团股份有限公司 | The generation method and device of work plan |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111126941A (en) | 2020-05-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111126941B (en) | Careplan processing method and device, electronic equipment and storage medium | |
| US10665334B2 (en) | Method and system for automated healthcare care coordination and care transitions | |
| JP6796071B2 (en) | Simulation-based systems and methods to help healthcare consultants and hospital managers determine the optimal human resource plan for the hospital | |
| US9953385B2 (en) | System and method for measuring healthcare quality | |
| US8781855B2 (en) | Integrated point of care medication administration information system | |
| US20150100333A1 (en) | Systems and methods for verifying protocol compliance | |
| US20040260593A1 (en) | System and user interface supporting workflow operation improvement | |
| US20060282302A1 (en) | System and method for managing healthcare work flow | |
| US20220310214A1 (en) | Methods and apparatus for data-driven monitoring | |
| CA2782272C (en) | Systems and methods for a destination-based care services model | |
| CA2856966A1 (en) | Electronic health record system and method for patient encounter transcription and documentation | |
| Bell et al. | From promise to reality: achieving the value of an EHR: realizing the benefits of an EHR requires specific steps to establish goals, involve physicians and other key stakeholders, improve processes, and manage organizational change | |
| US20170024523A1 (en) | Requirement Forecast for Health Care Services | |
| US20180240547A1 (en) | Healthcare Visit Value Calculator | |
| Sahni et al. | The IT transformation health care needs | |
| JP2017111776A (en) | Notification system, notification method, and notification program | |
| WO2013103359A1 (en) | Systems and methods for providing enterprise visual communications services | |
| Dolan et al. | Integration of a Digital Health Intervention Into Immunization Clinic Workflows in Kenya: Qualitative, Realist Evaluation of Technology Usability | |
| EP2518617A1 (en) | Dynamic user and device specific user interface generation based on process descriptions | |
| US11854673B2 (en) | Systems and methods for managing caregiver responsibility | |
| US10128000B1 (en) | Computer system and method for delivering operational intelligence for ambulatory team based care and virtual medicine | |
| WO2023091589A1 (en) | Systems and methods for workload management | |
| CN109545304A (en) | Medical care method, apparatus, equipment and storage medium based on Intelligent bracelet | |
| US12027269B2 (en) | Intelligent system and methods for automatically recommending patient-customized instructions | |
| Dachyar et al. | Collaborating Internet of Things (IoT) and Electronic Medical Record (EMR) to Reduce Healthcare Waiting time. Outpatient Cardiology Service Case: A BPR Approach |
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 |