Working status aggregation system, working status aggregation method and program

Abstract

To provide a working status aggregation system capable of easily aggregating the number of visits and a moving time of each staff member when aggregating the working status of staff visiting object persons and providing services.SOLUTION: A working status aggregation system 100 comprises: a working status aggregation part 111 for acquiring, as schedule information of each staff member as an aggregation object, schedule information 323 including visit time zone information representing a time zone for visiting a target person in response to a request from a user terminal 300 and travel time information representing a travel time between visits, the travel time to a next visit location after termination of each visit, and generating aggregation information representing a total visit time and a total travel time of each staff member in a prescribed aggregation period based on the visit time zone information and the travel time information of each aggregation object staff member included in the acquired schedule information 323; and an aggregation result transmission part 113 for outputting the aggregation information to the user terminal 300 of the request source.SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to an operation status compilation system, an operation status compilation method, and a program. [Background technology]

[0002] 2. Description of the Related Art Home visit services, such as home visits for medical examinations, nursing care, and care services, have traditionally been widely provided, in which staff visit the homes of patients, users, etc. receiving the services. In businesses that provide these services, the number of visits and visiting time per staff member are managed as important KPIs (Key Performance Indicators). In particular, in the fields of home visits, visiting nursing, and home care, the unit price for visiting time is stipulated in the insurance points, so visiting time is a major variable.

[0003] As a technique for creating a visiting schedule for each staff member that can be applied to such visiting services, for example, the technique described in Patent Document 1 is known. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 5847986 Summary of the Invention [Problem to be solved by the invention]

[0005] In the past, when trying to tally up the number of visits and visiting time per staff member mentioned above, the method used was to download service provision performance information from systems such as electronic medical records in CSV format, and then have the manager or administrator use that information to manage the data using spreadsheet software.

[0006] However, although this method can tally up the number of visits and visiting time, it is difficult to take travel time into account. On the other hand, in reality, in a visiting service, the time it takes to travel between visits has a large impact on the number of visits that can be made, so it is preferable to be able to tally up travel time along with the number of visits and visiting time. If travel time can be tallyed up, it will be possible to use that information to tally up various other KPIs.

[0007] This invention has been made in consideration of the above circumstances, and aims to make it possible to easily tally up the visiting time and travel time of each staff member when tallying up the operating status of staff who visit targets and provide services. The present invention is not limited to application to home visit medical treatment, home nursing, and home care, but is applicable to any business that provides services by visiting a target person. [Means for solving the problem]

[0008] In order to achieve the above-mentioned objectives, the first operation status collection system of the present invention is an operation status collection system that is composed of one computer or multiple computers working in cooperation with each other and collects the operation status of staff who visit subjects and provide services, and is equipped with an acquisition unit that acquires schedule information for each staff member to be collected, the schedule information including visiting time zone information indicating the time zone for visiting the subject and travel time information indicating inter-visit travel time which is the travel time to the next visit location after each visit is completed, and an acquisition unit that creates collection information for each staff member indicating the total visiting time and total travel time of each staff member within a specified collection period based on the visiting time zone information and travel time information of each staff member to be collected, which are included in the schedule information acquired by the acquisition unit, and outputs the collection information to a specified output destination.

[0009] In such an operational status aggregation system, it is preferable to have a schedule creation unit that accepts input of the visit location, desired visit time, and desired service for each target person to be provided with a service, and accepts input of working hours and transportation method for each staff member, and based on this, creates the above-mentioned schedule information that specifies a schedule for each staff member to visit each target person and provide the above-mentioned service. Furthermore, the service may be a medical, nursing or care service.

[0010] In addition, the schedule information includes working time period information indicating the working time periods of each staff member, and the travel time information includes information on departure travel time, which is the travel time from the work start location to the first visit location within the working time, and / or return travel time, which is the travel time to the work end location after the last visit within the working time, and when determining the total travel time corresponding to one working time period within the specified aggregation period, the aggregation unit may add the departure travel time and / or the return travel time to the inter-visit travel time corresponding to each visit within the working time.

[0011] In addition, the schedule information may include provided service information indicating the type and time of service to be provided during each visit, and travel method information indicating the travel method used by the staff for each travel, and the system may include a load information acquisition unit that acquires service load information indicating the load per unit time for each type of service and travel load information indicating the load per unit time for each of the travel methods, and a load value calculation unit that calculates a load value related to service provision for each staff member by referring to the service load information based on the provided service information related to each visit within the specified collection period, among the information regarding each staff member to be counted included in the schedule information acquired by the acquisition unit, and calculates a load value related to travel for each staff member by referring to the travel load information based on the travel time information and the travel method information related to each visit within the specified collection period, and outputs the load value to the specified output destination.

[0012] In addition, when creating the schedule information, the schedule creation unit may set a schedule of one visit and the next visit for a certain staff member as candidates, and in response to transmitting the visiting location of the first visit, the visiting location of the next visit, and the travel method of the certain staff member to a predetermined route search system, obtain from the route search system the travel time from the visiting location of the first visit to the visiting location of the next visit, and while securing the obtained travel time between the first visit and the next visit as the inter-visit travel time, if the time zone of the first visit and the time zone of the next visit satisfy the desired visiting time for each visit and can be set within the working hours of the certain staff member, register visiting time zone information indicating the time zone of the visit and the inter-visit travel time as schedule information of the certain staff member.

[0013] A second operating status tabulation system of the present invention is configured with one computer or multiple computers working together, and tabulates the operating status of staff who visit targets and provide services, the system comprising: a first acquisition unit that acquires, from a predetermined acquisition source, information on visited locations, visiting time periods, and visiting staff members as information on services provided within a predetermined tabulation period; a second acquisition unit that acquires, for each staff member, a staff member's working time period and a travel method; and a second acquisition unit that extracts, from the information acquired by the first acquisition unit, visited locations and visiting time periods visited by the staff members for each working time period of the staff members to be tabulated, in chronological order, and stores the acquired information. The system further includes a travel time acquisition unit that acquires travel time information indicating inter-visit travel time, which is the travel time from each visited location to the next visited location, from the route search system in response to transmitting, for each visited location, the location of the visited location, the location of the next visited location, and information on the staff member's travel method acquired by the second acquisition unit to a predetermined route search system, and a counting unit that creates, for each staff member, summary information indicating the total visiting time and total travel time of each staff member to be counted during the specified counting period based on the information acquired by the first acquisition unit and the travel time information acquired by the travel time acquisition unit, and outputs the information to a specified output destination.

[0014] In such an operational status aggregation system, the service may be a medical, nursing or care service, and the source of the information may be an electronic medical record system, a prescription management system, a daily report system or an attendance management system. In addition, the same modifications as those described for the first operational status compilation system can be applied to the second operational status compilation system.

[0015] The present invention as described above can be embodied in any form, such as an apparatus, a method, a program, or a recording medium having a program recorded thereon, in addition to being embodied as the above-mentioned system invention. Effect of the Invention

[0016] According to the operation status compilation system of the present invention as described above, when compiling the operation status of staff who visit targets and provide services, it is possible to easily compile the visit time and travel time of each staff member. [Brief description of the drawings]

[0017] [Figure 1] FIG. 1 is a diagram for explaining an operational status aggregation system according to a first embodiment of the present invention and an arrangement of devices related to the operation of the system. [Diagram 2] FIG. 2 is a diagram illustrating a hardware configuration of the operational status aggregation system 100 illustrated in FIG. [Diagram 3] 2 is a functional block diagram showing a configuration of functions related to schedule creation and operation status aggregation that each system shown in FIG. 1 has. [Figure 4] FIG. 4 is a diagram showing a configuration of staff information 321 shown in FIG. [Diagram 5] FIG. 13 is a diagram showing a specific example of staff information 321. [Figure 6] 4 is a diagram showing a configuration of visited destination information 322 shown in FIG. [Figure 7] 13 is a diagram showing a specific example of visited destination information 322. FIG. [Figure 8] FIG. 4 is a diagram showing a configuration of schedule information 323 shown in FIG. [Figure 9] FIG. 2 is a diagram showing an example of a one-day schedule for one staff member represented by schedule information 323. [Figure 10] 4 is a diagram showing an example of unit load information 324a relating to services among the unit load information 324 shown in FIG. 3. FIG. [Figure 11] FIG. 4 is a diagram showing an example of unit load information 324b relating to movement among the unit load information 324 shown in FIG. [Figure 12] FIG. 4 is a sequence diagram showing an operation procedure when schedule creation system 200 shown in FIG. 3 creates schedule information in response to a user instruction. [Figure 13] 13 is a flowchart showing a specific procedure of the schedule creation process shown in FIG. 12. [Figure 14] This is a continuation of the flowchart in Figure 13. [Figure 15] FIG. 4 is a sequence diagram showing an operation procedure when the operational status totalization system 100 shown in FIG. 3 creates operational status information in response to a user instruction. [Figure 16] 16 is a flowchart showing a specific procedure of the operational status aggregating process shown in FIG. 15. [Figure 17] 17 is a diagram showing an example of an operating status screen showing the operating status of each staff member, which is displayed based on the operating status information created in the operating status compilation process shown in FIG. 16. [Figure 18] 16 is a flowchart showing a specific procedure of the load calculation process shown in FIG. 15. [Figure 19] 19A to 19C are diagrams showing examples of load information created in the load calculation process shown in FIG. [Figure 20] 19 is a diagram showing an example of a load status screen showing the work load of each staff member, which is displayed based on the operating status information created in the load calculation process shown in FIG. 18. FIG. [Figure 21] 5 is a functional block diagram corresponding to FIG. 3 and showing a configuration of functions related to operation status aggregation provided in each system related to operation status aggregation by an operation status aggregation system according to a second embodiment of the present invention. FIG. [Figure 22] FIG. 22 is a diagram showing the configuration of medical record information 252 shown in FIG. 21. [Diagram 23] FIG. 22 is a sequence diagram showing an operation procedure when each system shown in FIG. 21 creates operational status information in response to a user instruction. [Figure 24] 24 is a flowchart showing a specific procedure of the operational status tabulation process shown in FIG. 23. [Diagram 25] This is a continuation of the flowchart in Figure 24. [Figure 26] FIG. 13 is a functional block diagram showing a configuration of functions related to operational status aggregation provided in each system constituting an operational status aggregation system according to a third embodiment of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] [First embodiment: Figs. 1 to 20] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. 1 shows an operational status collecting system according to a first embodiment of the present invention and the layout of devices related to the operation of the system. FIG. 2 shows a hardware configuration of the operational status collecting system 100 shown in FIG.

[0019] An operational status aggregation system 100 shown in FIG. 1 is an embodiment of the operational status aggregation system of the present invention. In addition, a system including a schedule creation system 200, or a system including a user terminal 300, or a system including both of these, are also embodiments of the operational status aggregation system of the present invention.

[0020] The performance status aggregation system 100 is a system for providing an online aggregation service that aggregates the performance status of staff of businesses that provide services by visiting targets. The system is operated by a business that provides such an online aggregation service. The schedule creation system 200 is a system for providing a schedule creation service operated by a business that provides an online schedule creation service that creates visiting schedules for the staff of businesses that provide services by visiting targets.

[0021] The operating status aggregation system 100 and the schedule creation system 200 may be operated by the same business operator, and the hardware of these systems may be in the same local environment. In both systems, business operators, who are users, access these systems from their own user terminals 300 via the Internet N to use the services. Although multiple user terminals 300-1 to y are shown in Fig. 1, this indicates that multiple business operators can independently use the operation status aggregation system 100 and the schedule creation system 200, and in the following explanation, the symbol 300 will be used for the user terminal when there is no need to distinguish between the individual terminals.

[0022] 2, the operating status tabulation system 100 can be configured by a computer (information processing device) in which a processor 101, a memory 102, a storage 103, a communication I / F 104 for communication via the Internet N or the like, an operation unit 105 for receiving operations from an operator, and a display unit 106 for displaying information to the operator are connected by a communication path 107 such as a system bus. The necessary functions may be distributed and provided in multiple computers that can communicate with each other. This basic configuration is also applicable to the schedule creation system 200 and the user terminal 300.

[0023] The user terminal 300 is a computer operated by an individual, such as a personal computer (PC), a tablet computer, or a smartphone. However, it is also possible for one business entity to have multiple terminals, and for these terminals to refer to common data (such as staff information 321 to operating status information 325 shown in FIG. 3) and use the operating status compilation system 100 and / or the schedule creation system 200. In this case, the data storage location can be determined arbitrarily, such as a server in the user environment, a storage in a cloud environment, or a storage provided inside the operating status compilation system 100 or the schedule creation system 200.

[0024] The route search system 400 is a system that operates independently of the operation status aggregation system 100 and the schedule creation system 200, and provides a service that provides at least information on travel routes and the travel times between two specified points when traveling using various travel methods.

[0025] For example, a system for providing map information services, transfer guide services, navigation services, etc. in response to access via the Internet N corresponds to the route search system 400. In the case of a transfer guide service, a system capable of outputting not only the route using public transport but also the travel route and required time to a specific address or coordinate is used. The route search system 400 has a function of returning information on the travel route and required time between two points in response to an external request such as an API (Application Programming Interface).

[0026] Below, with reference to Figure 3 onwards, we will explain the functional configuration of each system in order to provide the above-mentioned services, as well as examples of data, algorithms, screens, etc. used to realize these functions.

[0027] FIG. 3 is a functional block diagram showing the functional configuration of the operation status aggregation system 100, schedule creation system 200, user terminal 300, and route search system 400 shown in FIG. 1, focusing on those necessary for providing and using the above-mentioned services. 4 to 11 are diagrams showing examples of data used by each unit shown in FIG. 3 or schedules represented by the data. The functions of the units shown in Fig. 3 can be realized by a processor of each system or device executing a required program to control the required hardware. This program may be installable and uninstallable as desired.

[0028] It is also possible to provide a web server function on the operation status collection system 100 and / or the schedule creation system 200 side, and to provide all or part of the functions on the user terminal 300 side through a web page displayed in response to accessing the operation status collection system 100 and / or the schedule creation system 200 from the user terminal 300 using a web browser or the like. Also, it is not prevented from realizing all or part of the functions shown in Fig. 3 by dedicated hardware. Also, it is not prevented from realizing all or part of the functions of each device by using resources of an external device such as a cloud environment.

[0029] As shown in FIG. 3, the performance aggregation system 100 includes an performance aggregation unit 111, a load information calculation unit 112, and an aggregation result transmission unit 113 as functions for providing an aggregation service that aggregates the performance status of staff members. The operation status aggregation unit 111 has a function of acquiring, in response to a request from the user terminal 300, schedule information for each staff member to be aggregated, including visit time period information indicating the time period for visiting the target person and travel time information indicating inter-visit travel time, which is the travel time to the next visit location after each visit, as schedule information for each staff member to be aggregated, and a function of creating aggregation information for each staff member indicating the total visit time and total travel time for each staff member within a specified aggregation period, based on the visit time period information and travel time information of each staff member to be aggregated, which are included in the acquired schedule information.

[0030] In this example, the visiting time period information uses the start time and end time of the service provision at the visited location (see FIG. 8). The compilation information can be created, for example, by the process of FIG. 16. The schedule information may be created by the schedule creation system 200 or may be edited by the user. As long as the schedule information contains necessary information, it may be created by a system other than the schedule creation system 200 of FIG. 3 (the operation status compilation system 100 and the schedule creation system 200 may be systems that are operated completely independently of each other). The operational status aggregating unit 111 corresponds to an acquisition unit, and also corresponds to an aggregating unit together with the aggregating result transmitting unit 113.

[0031] The load information calculation unit 112 has a function of acquiring, in response to a request from the user terminal 300, service load information indicating the load per unit time for each type of service provided by the staff and travel load information indicating the load per unit time for each staff travel method from the user terminal 300, and a function of calculating a load value related to service provision during work and a load value related to travel for each staff member while referring to the unit load information as well as the schedule information acquired by the operation status aggregation unit 111 and the aggregation information created by the operation status aggregation unit 111. When the load information calculation unit 112 is operated, the schedule information includes provided service information indicating the type and time of service provided by the staff member at each visit, travel method information indicating the travel method used by the staff member for each travel, and travel time information indicating the time required for each travel by the staff member. The load value can be calculated, for example, by the process of FIG. 18. The load information calculation unit 112 corresponds to a load information acquisition unit, and also corresponds to a load value calculation unit together with the tally result transmission unit 113 .

[0032] The tally result transmission unit 113 has a function of transmitting the tally information created by the operational status tallying unit 111 and the load value calculated by the load information calculation unit 112 to the user terminal 300 that has made the request.

[0033] Next, the schedule creation system 200 includes a schedule creation unit 211 and a travel time acquisition unit 212 as functions for providing a schedule creation service that creates a staff visit schedule. The schedule creation unit 211, in response to a request from the user terminal 300, acquires from the user terminal 300 information on the place to be visited, desired time of visit, and desired service for each person to be provided with a service, and acquires from the user terminal 300 information on working hours and transportation method for each staff member, and based on this, creates schedule information that specifies the schedule for each staff member to visit each person and provide the service, and transmits the schedule information to the user terminal 300 that made the request.

[0034] The travel time acquisition unit 212 has a function of accessing the route search unit 411 of the route search system 400 to acquire information on the time that should be secured as staff travel time when creating this schedule information. For example, by sending information on the departure and arrival locations and the method of transportation to be used (bicycle, car, etc.) along with a specified command to the API provided by the route search system 400, information on the travel route and required time (travel time) can be obtained in response.

[0035] Location information may be transmitted in a format such as an address, coordinates, or landmark that meets the specifications required by the route search system 400. The same applies to the designation of the travel method. If the information transmitted from the user terminal 300 does not meet these specifications, a converter that can convert addresses and coordinates, etc., that can be used by the travel time acquisition unit 212 to convert the description format may be provided.

[0036] The allocation condition information 221 predefines conditions that should be fixedly considered when allocating each visit to a staff member. For example, a visit providing medical services is allocated to a staff member with a medical license, a visit providing nursing services is allocated to a staff member with a nursing license, etc. Conditions related to attributes as well as qualifications may be defined. The schedule creation unit 211 creates schedule information so as to satisfy the conditions stipulated by the allocation condition information 221. The creation of schedule information by the above-mentioned units can be performed by the processes shown in FIGS.

[0037] Next, the user terminal 300 has the functions of an information input receiving unit 311 and an information display unit 312 as functions related to handling of data related to schedule creation and / or compilation of operating status. The user terminal 300 also includes a schedule creation instruction receiving unit 331, a condition information transmitting unit 332, and a schedule receiving unit 323 as functions for using the schedule creation system 200. The user terminal 300 also stores staff information 321 and visit information 322. The schedule information 323 is schedule information transmitted from the schedule creation system 200, and can also be edited on the user terminal 300 side.

[0038] The user terminal 300 also includes an operation status aggregation instruction receiving unit 341, an aggregation request unit 342, a unit load information transmitting unit 343, and an operation status receiving unit 344 as functions for using the operation status aggregation system 100. The user terminal 300 also stores unit load information 324. Operation status information 325 is the aggregation result (aggregation information and load value) of the staff operation status transmitted from the operation status aggregation system 100.

[0039] Of these, the information input reception unit 311 has a function of receiving input and editing operations of the staff information 321 to the unit load information 324 from an operator, and editing each piece of information accordingly. The information display unit 312 has a function of displaying staff information 321 to operating status information 325 on a screen such as that shown in FIG. 20, for example, in accordance with an operation by an operator. The schedule creation instruction receiving unit 331 has a function of receiving an instruction from the user to create a schedule by the schedule creation system 200 and a designation of the date range for creating the schedule.

[0040] The condition information sending unit 332 has a function of extracting information necessary for schedule creation from the staff information 321 and the visit destination information 322 in response to an instruction received by the schedule creation instruction receiving unit 331, and passing it to the schedule creation unit 211 to request the creation of a schedule. The staff information 321 is information about the staff in charge of the visit, and the visit destination information 322 is information about the customer who uses the visiting service. This customer is called a patient if the service is medical care, or a user if the service is nursing or care. The staff information 321 and the visit destination information 322 are created in advance by the user before creating a schedule.

[0041] The schedule receiving unit 333 has a function of receiving created schedule information transmitted from the schedule creation unit 211 and saving it as schedule information 323. This schedule information 323 can be edited by a user operation. In other words, once the schedule information created by the schedule creation system 200 is created, the user can modify it as desired.

[0042] The operating status aggregation instruction receiving unit 341 has a function of receiving an instruction from a user to aggregate staff operating status by the operating status aggregation system 100, and a designation of a date range for aggregation and staff members to be aggregated. The tally request unit 342 has a function of extracting information required for tallying from the schedule information 323 in response to an instruction received by the operating status tally instruction receiving unit 341, and passing it to the operating status tallying unit 111 to request tallying of the operating status.

[0043] The unit load information sending unit 343 has a function of sending unit load information 324 related to service provision and movement used for calculating a load value to the load information calculation unit 112 in response to a request from the tally requesting unit 342 for tallying up the operation status. The unit load information 324 is created in advance by the user before tallying up the operation status. The schedule information 323 and the unit load information 324 may be transmitted together. In this case, it is not necessary to distinguish between the tally request unit 342 and the unit load information transmission unit 343. The operational status receiving unit 344 has a function of receiving the created tally information and the load value transmitted from the tally result transmitting unit 113 and saving them as the operational status information 325 .

[0044] Next, Fig. 4 shows the structure of the staff information 321 shown in Fig. 3. Fig. 5 shows an example of information registered as staff data. As shown in Fig. 4, the staff information 321 includes staff data, which is information about each registered staff member, for each staff member. In the example of Fig. 4, staff data E1 to En1 for n1 people are included.

[0045] Each staff member's data includes information such as staff member ID, name, qualifications, attributes, skills, working hours, holiday information, transportation method, starting location of work, and ending location of work. The staff ID is identification information for uniquely identifying a staff member. The names are the names of staff members. Qualifications are the qualifications held by staff members, such as doctor, nurse, care worker, physiotherapist, etc. It is also possible to stipulate multiple qualifications for one staff member.

[0046] Attributes are the characteristics of staff members other than qualifications that are used to determine which tasks a staff member will be assigned to or what kind of tasks at which clients they will be assigned to. Examples include gender, physique, compatibility with clients, etc. In cases where a client specifies the gender of a staff member, where caring for a large client is difficult only for a large and strong staff member, or where a particular staff member has been refused a task due to past circumstances, the information required to create a schedule that takes these factors into consideration is registered as an attribute. Skills is also information with a similar purpose to attributes, but it is information used to preferentially assign each staff member to customers in their area of ​​expertise, such as being good at caring for children, good at terminal care, good at dealing with customers with mental disabilities, or good at a specific procedure.

[0047] The working time period indicates the regular working time period of each staff member on each day of the week by the working start time and the working end time. In principle, each staff member is assigned a visit destination and the visiting time is determined so that the service provision can be completed within the working time period, including travel time. However, when creating the schedule information 323, working start times and working end times different from the working time period specified in the staff information 321 can be used, taking into consideration early start times, overtime, etc. In addition, the working time period can be determined based on other criteria, such as by date of the month, rather than by day of the week. Holiday information is information about holidays, such as staff vacations and whether or not the staff has holidays.

[0048] The method of transportation is information about the method of transportation used by staff when visiting customers, and it is possible to set car, bicycle, etc. It is also possible to register different methods of transportation depending on the day of the week, or different methods of transportation depending on the distance or the area to be visited. In either case, the travel method is described so that the correspondence with the travel method in the unit load information 324b relating to travel shown in Fig. 11 can be understood. For this purpose, it is preferable to describe the travel method using a common ID or service name in the staff information 321 and the unit load information 324, and to do the same in the schedule information 323.

[0049] The work start location and work end location are information about the location where a staff member starts and ends their work. If the staff member goes to a business office once and then starts work, or if the staff member returns to the business office at the end of their work, the location will be the location of the business office. If the staff member goes directly to or returns directly from the business office, the location will be the home address, or depending on the management format, the location may refer to the first or last visit. It is also possible to register different locations depending on the day of the week or the area of ​​the first or last visit of the day. For example, if the distance from the home to the first or last visit is short, the location will be the direct go or direct return. The location can be specified in any format, such as an address or coordinates.

[0050] This information is for reference when creating a schedule, and if any of the information is not to be taken into consideration when creating a schedule, that information may be omitted. Conversely, if other information is to be taken into consideration, that information is also included in the staff data. The representation format of staff data is not limited to that shown in Figure 5. For example, qualifications and attributes may be registered as IDs for referencing other tables, and working hours may be expressed by the start time of work and the number of hours worked. Break times may also be registered.

[0051] Next, Fig. 6 shows the configuration of the visited destination information 322 shown in Fig. 3. Fig. 7 shows an example of information registered as visited destination data. The visited destination information 322 includes visited destination data, which is information regarding visits to each registered customer, as shown in Fig. 6. In the example of Fig. 6, visited destination data V1 to Vn2 for n2 people are included.

[0052] Each visit data includes information such as a visit ID, a name, a location, a type of service, a service time, a standard visit date, an irregular visit date, a possible visit time period, and special constraint conditions. The visited destination ID is identification information for uniquely identifying visited destination data. When one customer has multiple contracts, or when one visited destination provides services to multiple customers, it is possible to create visited destination data by appropriate classification for each contract or customer, making it easier for the business to organize. Therefore, in this example, the visited destination ID is not used as an ID for uniquely identifying a customer or visited destination. Separate identification information for identifying a customer or visited destination may be prepared.

[0053] The name is the name of the customer to whom the service is to be provided. The location is information about the location of the visit. It can be expressed in any format, such as an address or coordinates. The service type and service time are the type and time of the service provided to the customer at the visit destination.

[0054] The service type is described so that the correspondence with the service type in the unit load information 324a for services shown in Fig. 10 can be understood. Also, the allocation condition information 221 of the schedule creation system 200 defines constraints on the allocation to staff according to the service type, and the service type is described so that the correspondence with this definition can be understood. For this purpose, it is preferable to describe the service type using a common ID or name in all of the visited destination information 322, unit load information 324, and allocation condition information 221, and to do the same in the schedule information 323.

[0055] The service time may be a fixed time, or, for example, if the time required to provide a service varies depending on the skill of the staff member in charge, it may be a basic time that is subject to variation. The basic visit date is data that specifies the planned visit date in principle by the day of the week of the week or the date of the month. It may be possible to specify a certain number of times per week without specifying a date. The irregular visit date is data that specifies any temporary changes to the basic visit date.

[0056] The visitable time period is data on the time period during which a visit to a destination can be made. For example, it may be possible to specify a time range for each day of the week, or to specify the time period in association with each basic visit date. As with irregular visit dates, temporary changes may be registered. The special constraints are data that specify constraints that should be considered when selecting staff to visit, other than the allocation condition information 221. They are specified so as to correspond to attributes and skills in the staff data. For example, it is possible to limit the staff to those with terminal care skills, or to those with a large build attribute. As with the staff data, the representation format of the visited data is not limited to that shown in FIG.

[0057] Next, Fig. 8 shows the configuration of the schedule information 323 shown in Fig. 3. Fig. 9 shows an example of a schedule represented by one day's schedule data for one staff member. 8, the schedule information 323 includes schedule data C1 to Cn1 related to each staff member registered in the staff information 321. It also includes date range data indicating which date range the schedule data applies to. When some of the staff members included in the staff information 321 are not to be allocated to a schedule (visit), the number of staff members in the staff information 321 and the schedule information 323 may differ.

[0058] The schedule data for each staff member includes a staff ID for identifying the staff member and schedule data for each day indicated by the date range. For staff members' holidays, it is recommended to prepare schedule data indicating that the holiday is on, but it is also possible to indicate that the holiday is on by not having schedule data for that date. In this example, schedule data is created on a daily basis, but if the start and end of a shift spans multiple days or if multiple days are treated as a continuous work period, it is recommended to create schedule data for each work period.

[0059] The schedule data for each day includes information such as the date, the start time of work, departure travel information, visit data for any number of visits, travel information between visits, return travel information, and the end time of work. The date indicates the date of the schedule represented by the corresponding schedule data. The work start time and work end time are the work start time and work end time of the staff member on the relevant day. In anticipation of overtime work, the times may be different from the work hours in the staff information 321.

[0060] The departure travel information is information about travel from the work start location to the first visit location. Travel information between visit data is information about travel from the previous visit location to the next visit location. The return travel information is information about travel from the last visit location on the relevant day to the work end location. Both include information on the travel method and travel time. The travel method is described so that the correspondence with the travel method in the staff information 321 and the unit load information 324b related to travel can be understood. The travel time is described so that it can be understood how many times it is one unit in the unit load information 324b. The travel time between visits may be zero, such as when providing service to multiple customers consecutively at the same visit location.

[0061] Each visit data is information regarding one visit by a staff member, and includes information regarding the visited location ID, the start time of service provision, the type of service, the duration of service provision, and the end time of service provision. The visited destination ID is identification information that indicates which visited destination data in the visited destination information 322 the visit relates to. The service provision start time is the time when the service provision at the destination is scheduled to start. The staff member must arrive at the destination before this time.

[0062] The service type is the type of service provided to the customer at the corresponding destination, and is described so that the correspondence with the service types in the destination information 322 and the unit load information 324a regarding the service provision can be understood. The provision time is the time expected to be required to provide the service at the visit destination, and even if it is specified as variable in the visit destination information 322, a fixed time actually expected depending on the assigned staff is specified.

[0063] The service end time is the time when the service provision at the visit destination is scheduled to end. The service end time can be the time after the service provision start time by the service provision time, and the time itself can be omitted. The time when the staff leaves the visit destination will be after this service provision end time. Using the above-mentioned one-day schedule information for one staff member, the schedule shown in FIG. 9 can be expressed, for example.

[0064] In the example of Fig. 9, three visits per day are specified by the visit data VD1 to VD3. By referring to the visit information 322 based on the visit ID, the name of the visit customer can be identified, and the type of service to be provided, the expected time, and the scheduled start and end of the service provision at each visit are specified by each visit data.

[0065] The travel time indicated by the arrows in Fig. 9 is specified by each piece of travel information. Although there is no data in Fig. 8 that directly specifies the free time, the free time between visits can be calculated from the difference between the time available for travel from the end time of the service provision at the previous visit to the start time of the service provision at the next visit, and the time that is assumed to actually be required for travel, which is included in the travel information. Therefore, the length of this free time is also essentially specified by the schedule information. The same applies to the time from the start of work to the first visit, and from the last visit to the end of work.

[0066] In addition, taking into consideration the administrative tasks at the destination, the length of free time may be set to be shorter than the difference between the time available for travel and the time expected to be required for the travel. Also, a long free time may be determined to be a break such as a lunch break. Schedule information may be created so that such free time corresponding to a break can be taken consecutively once a day.

[0067] Next, FIG. 10 shows an example of unit load information 324a related to the service provision in the unit load information 324. This information specifies the load per unit time that the provision of each service is expected to place on the staff in charge of the service. I2 to I5 specify the type of service according to the service code established by the Ministry of Health, Labor and Welfare. The load is a numerical value that abstractly expresses the combined mental and physical load. The value that corresponds to each service can be determined appropriately by the business operator who operates the user terminal 300. The operator of the operational status aggregation system 100 may prepare an appropriate template and use this as a general rule. The business operator who operates the user terminal 300 can determine the granularity at which the service types are classified appropriately. However, it is preferable to define at least services that provide significantly different loads as different services.

[0068] Next, FIG. 11 shows an example of unit load information 324b relating to movement in the unit load information 324. This information specifies the load per unit time that is expected to be imposed on the staff member in charge of travel by each travel method. This load is also a numerical value that abstractly expresses the combined mental and physical load. The business operator can decide the numerical value as appropriate, an appropriate template may be used, and the concept of classification of travel methods is the same as that of the unit load information 324a related to service provision.

[0069] Next, examples of processes and operations executed by the operation status tabulation system 100, the schedule creation system 200, and the user terminal 300 to realize the above-described functions will be described with reference to Figures 12 to 17. Unless otherwise specified, it is assumed that the user terminal 300 or its operator has been authenticated by some means as a legitimate user of the system by the operation status tabulation system 100 or the schedule creation system 200 that is being accessed, when performing the operations shown in the sequence diagrams of Figures 12 and 15.

[0070] First, Fig. 12 shows the procedure of operation of each device when schedule creation system 200 shown in Fig. 3 creates schedule information in response to a user's instruction. The operation of each device shown in Fig. 12, particularly the operation executed by schedule creation system 200, is an example of a schedule creation procedure in the operation status tabulation method of this invention. In the procedure of FIG. 12, the user terminal 300 accepts input of staff information 321 and visit information 322 in advance and stores them in an appropriate storage device in preparation for creating a schedule (S11).

[0071] In this state, when the date range for creating the schedule and creation instructions are received from the user (S12), the user terminal 300 transmits the staff information 321, visiting destination information 322 saved in step S11, and the received date range together with a schedule creation request to the schedule creation system 200 (S13).

[0072] When the schedule creation system 200 receives this request, it performs the schedule creation process shown in Figures 13 and 14 to create schedule information as shown in Figure 8 (S14), and transmits the created schedule information to the user terminal 300 (S15). When creating the schedule information, the schedule creation system 200 accesses the route search system 400 to automatically obtain information on travel time (S21).

[0073] The user terminal 300 that has received the schedule information stores it in an appropriate storage as schedule information 323 (S16). In response to user operations, the user terminal 300 displays a schedule such as that shown in Fig. 9 based on the stored schedule information 323 (S17), or edits the schedule information according to the user's editing operations (S18).

[0074] Schedules can be displayed for a specific staff member for a day, week, month, etc., or the schedules of multiple staff members can be displayed for a specific day or week. One example of editing a schedule could be to assign visits that could not be assigned automatically to staff members, taking overtime into consideration as necessary, or to respond to a sudden absence of a staff member by assigning that staff member's visits to another staff member.

[0075] 13 and 14 show the schedule creation process in step S14 in more detail. In this process, the schedule creation system 200 first performs a loop L1 in which each piece of destination data passed from the user terminal 300 is sequentially processed, and repeats the process of step S31 and a loop L2.

[0076] In step S31, visit data is created for each visit within the date range passed from user terminal 300, which is specified in the visited data to be processed. For example, if the visited data specifies that a visit should be made every Monday, and the date range is the month of March, visit data is created for each Monday in March. This visit data will become part of the schedule data in FIG. 8 in later processing. Thereafter, the schedule creation system 200 repeats the processes of steps S32 to S41 as a loop L2, sequentially processing each of the created visit data.

[0077] In step S32, the schedule creation system 200 extracts staff X who can make the visit, based on the service type, available visiting time period, and special constraint conditions defined in the destination data to be processed, and taking into consideration the allocation condition information 221. If there are multiple candidates, any one of them can be selected as appropriate.

[0078] If extraction is possible in step S32 (Yes in S33), in step S34, the schedule creation system 200 refers to the schedule data for staff X on the visit date related to the visit data to be processed, determines the approximate visit time taking into account the possible visiting time zone, and acquires the previous location of staff X. The previous location is the location of the previous visit destination specified by the visit data to be processed, or the work start location if there is no previous visit destination. In addition, the travel method is acquired from the staff data of staff X.

[0079] Next, in step S35, the schedule creation system 200 transmits a travel time calculation request including the acquired previous location and travel method, and the location of the current destination specified in the destination data to be processed, to the route search system 400. In response to this request, the route search system 400 acquires the travel time from the previous location to the current destination. Similarly, in steps S36 and S37, the next location of staff member X (the location of the next visit destination or the location where work ends) and the travel method are acquired, and a travel time calculation request including these and the location of the current visit destination is sent to the route search system 400. In response to this request, the route search system 400 acquires the travel time from the current visit destination to the next location.

[0080] Next, the schedule creation system 200 determines whether or not the visit schedule related to the visit data to be processed can be added between the previous and next visit schedules based on the travel time acquired in steps S35 and S37 (S38). If the visit schedule is the first visit schedule of the day, the previous visit schedule is read as the work start time, and if the visit schedule is the last visit schedule of the day, the later visit schedule is read as the work end time. Taking into account early starts and overtime work, the work start time and work end time may not match the work hours defined in the staff information 321. In either case, if the answer is Yes in step S38, the visit data to be processed is added to staff member X's schedule data (S39), the service provision start time and service provision end time are set appropriately so that the travel will be within the range of the available visiting time slot (S40), and the process proceeds to loop L2, with the next visit data to be processed.

[0081] If the answer is No in step S38, the process returns to step S32 to extract another staff member. If there is no other staff member that can be extracted (No in S33), the process records that a staff member could not be assigned to the visit data to be processed (S41), and the process proceeds to loop L2 for processing the next visit data. When the process of loop L2 is completed for all the visit data created in step S31, the process proceeds to the process of loop L1 for the next visited data.

[0082] When the process of loop L1 is completed for all visit data, the process proceeds to step S51 in Fig. 14. If the number of visit data to which staff could not be assigned is equal to or less than a predetermined number (Yes in S51), the schedule creation system 200 confirms the schedule data created up to this point and the unassigned visit data as the schedule creation results (S52), and ends the schedule creation process.

[0083] If the answer is No in step S51, the processing order of the visit data is changed and loop L1 is retried (S55) until the number of retries exceeds a predetermined upper limit (No in S53). This is because changing the processing order may allow for more dense allocation of visits to staff and reduce the amount of visit data that cannot be allocated.

[0084] On the other hand, if the number of retries exceeds the upper limit in step S53, the schedule data for the session with the fewest unallocated visit data, the unallocated visit data at that time, and a warning to the effect that there is a large amount of unallocated data are determined as the schedule creation results (S54), and the schedule creation process is terminated.

[0085] The results determined in step S52 or S54 are returned to the user terminal 300 in step S15 of Fig. 12. As a result, the operator of the user terminal 300 can automatically obtain a visiting schedule for each staff member that satisfies many conditions defined in the staff information 321 and the visit destination information 322 and also properly takes into account the time required for travel between visits.

[0086] In this case, if the location of each visit, the work start location, and the work end location are set, the schedule creation system 200 can automatically obtain the travel time, so the operator of the user terminal 300 does not need to check the travel time himself, reducing the burden on the operator. Since checking the travel time for each staff member who is a candidate for assignment to each visit and assuming an assignment is an extremely heavy workload, automating this process has a significant labor-saving effect.

[0087] If there is unassigned visit data, it is expected that the operator of the user terminal 300 will manually assign it in the editing of step S18, but the schedule creation system 200 does not need to be involved in this editing. The operator of the user terminal 300 can change the conditions, such as resetting the working hours taking into account overtime work by staff, and then have the schedule creation system 200 create a schedule again.

[0088] Next, Fig. 15 shows the procedure of operation of each device when the performance status compilation system 100 shown in Fig. 3 compilations the staff performance status in response to a user's instruction. The operation of each device shown in Fig. 15, particularly the operation executed by the performance status compilation system 100, is one example of the performance status compilation method of the present invention. In the procedure of Fig. 15, the user terminal 300 accepts the input of unit load information 324 in advance and stores it in an appropriate storage in preparation for schedule creation (S71). In addition, the schedule information 323 is also stored in an appropriate storage (S72). This schedule information may be created by the schedule creation system 200 or may be edited by the user. Also, as long as the necessary information is included, it may be created independently of the operation status compilation system 100 and the schedule creation system 200.

[0089] In any case, after steps S71 and S72 have been executed, when the target period for which staff operating status is to be aggregated, the staff to be aggregated, and aggregation instructions are received from the user (S73), the user terminal 300 sends to the operating status aggregation system 100 a request for aggregation of operating status, along with the schedule information 323 saved in step S72, information on the target staff and target period, and the unit load information 324 saved in step S71 (S74).

[0090] When the operation status compilation system 100 receives this request, it performs the operation status compilation process shown in Fig. 16 to create operation status compilation information for each staff member including the total visit time and total travel time of each staff member within a specified compilation period (S75). It also performs the load calculation process shown in Fig. 18 to calculate load compilation information including the load value related to the service provision and the load value related to travel within the compilation period for each staff member (S76).

[0091] The operation status compilation system 100 transmits the operation status compilation information and the load compilation information to the user terminal 300 (S77). The user terminal 300 that has received the information in step S77 stores it in an appropriate storage as operational status information 325 (S78). In addition, in response to an operator's operation, the stored operational status information 325 can be displayed, for example, as shown in Figs. 17 and 20 (S79). In the above operations, step S74 is an example of an operation of an acquisition procedure, steps S75 and S77 are an example of an operation of a counting procedure, and steps S76 and S77 are an example of an operation of a load value calculation procedure.

[0092] FIG. 16 shows the operation status aggregation process in step S75 in more detail. In this process, the operating status totalization system 100 first performs a loop L11, sequentially processing the staff members to be totaled that have been sent from the user terminal 300, and repeats the process of a loop L12 and step S95. In addition, in loop L12, the processes of steps S91 to S94 are repeated for the schedule data of the staff member to be processed and the dates in the collection range.

[0093] In this loop, the operating status tabulation system 100 first counts the number of visit data in the schedule data to be processed, that is, the number of visits by the staff to be processed (S91). Next, the service provision time related to each visit data in the schedule data to be processed is totaled for each service type (S92). In addition, the travel time in each travel information (including departure travel information and return travel information) in the schedule data to be processed is totaled for each travel method (S93). In addition, the difference between the time from the end of service provision at each visit destination to the start of service provision at the next visit destination and the travel time therebetween is totaled as the idling time of the staff to be processed (S94).

[0094] Here, ad-listing time is the time that staff are considered to be in an inefficient environment, such as the time spent waiting in a car while traveling by car and working. Ad-listing time roughly corresponds to the free time in Figure 9, but does not include the time before the first visit and the time after the final visit. This is because free time here can be used for meetings at the office, clerical work, etc.

[0095] When the processing of loop L12 for the schedule data for all dates in the aggregation range is completed, the operating status aggregation system 100 counts the number of working days for the target staff member, totals the number of visits, service provision time, travel time, and idling time for each day, and creates an aggregation result for the target staff member (S95). The reason why the totals are calculated for each service type and travel method in steps S92 and S93 is because the totals are used in the load calculation process in Fig. 18, but if the purpose is to aggregate operating status, it is not essential to total each service type and travel method.

[0096] When processing of loop L11 has been completed for all staff members to be tallied, the performance aggregation system 100 totals the number of visits, service provision period, travel time, and idling time for each staff member, creates aggregation results for all staff members, and terminates the performance aggregation process.

[0097] The counting results of steps S95 and S96 are returned to the user terminal 300 in step S77 of FIG. The user terminal 300 can display the tabulated results on an operation status screen 500 as shown in Fig. 17. The operation status screen 500 includes a table display section 510.

[0098] In the table display section 510, in addition to displaying the raw data of the tally results transmitted in step S77 in table form, it is also possible to display information obtained by calculations between items of the tally results, such as the number of visits per day, travel time per day, etc. It is preferable that the operator of the user terminal 300 be able to appropriately specify which items to display.

[0099] The operator of the user terminal 300 can refer to this display and understand the KPIs for business management. In particular, one of the features of this embodiment is that by tabulating the staff's operating status based on the schedule information 323 including information on the travel time between staff visits, it is possible to easily tabulate not only the number of visits and visit time but also the total travel time. As mentioned in the problem section, although travel time in a visiting service is essentially an important KPI, it has been difficult to tabulate travel time in the past. Therefore, the system of this embodiment, which can improve this point, can have a large impact on the management of visiting services.

[0100] By linking the operation status aggregation system 100 and the schedule creation system 200 to facilitate the exchange of schedule information, or by allowing schedule information to be provided to the operation status aggregation system 100 via the user terminal 300 even if they are not directly linked, the effect of easily performing aggregation including total travel time can be more effectively demonstrated. When tabulating travel times, travel times during working hours can be grasped more accurately by adding the travel times indicated by the departure travel information and return travel information in Fig. 8 to the tabulation. However, adding these travel times is not essential, and one or both may be excluded from the tabulation. For example, in the case of direct travel or direct return, these travel times may need to be considered as commuting time outside of working hours.

[0101] FIG. 18 shows the load calculation process in step S76 in more detail. In this process, the operating status totalization system 100 first repeats the processes of steps S101 to S107 as a loop L21, sequentially processing the staff members to be totaled that have been sent from the user terminal 300.

[0102] In this loop, the operating status aggregation system 100 first acquires the total service provision time of the staff member to be processed within the aggregation period for each service type (S101). This data can be acquired from the aggregation result in step S95 of FIG. Using this data, the operation status aggregation system 100 multiplies the service provision time corresponding to each service by the unit load according to the service type to calculate, for each service type, the load value of the service provision load that the staff is assumed to bear by providing the service (S102). The unit load is included in the information transmitted from the user terminal 300 in step S74 of FIG. 15.

[0103] Furthermore, the operating status aggregation system 100 sums up the service provision loads of each service type calculated in step S102, and calculates the total service provision load that is assumed to have been borne by the target staff member during their work in the aggregation period (S103). Next, the operating status aggregation system 100 acquires the total travel time of the target staff member for the aggregation period for each travel method (S104). This data can be acquired from the aggregation results in step S95 of FIG.

[0104] Using this data, the operation status aggregation system 100 multiplies the travel time corresponding to each travel method by the unit load according to the travel method to calculate, for each travel method, the travel load value of the travel load assumed to be incurred by the staff by the travel method (S105). The unit load is included in the information transmitted from the user terminal 300 in step S74 of FIG. 15.

[0105] Furthermore, the operating status aggregation system 100 sums up the travel loads of the respective travel methods calculated in step S105, and calculates the total travel load assumed to have been imposed on the target staff member during work in the aggregation period (S106). In addition, the operation status aggregation system 100 sums the total service provision load calculated in step S103 and the total travel load calculated in step S106 to calculate the total load that is assumed to have been incurred by the staff being processed during their work during the aggregation period (S107).

[0106] When processing of loop L21 is completed for all staff to be aggregated, the operation status aggregation system 100 calculates the sum of the load values ​​of each staff for the total service provision load, total travel load, and total load as the sum of the load values ​​of all staff (S108), and terminates the load calculation process. The load values ​​calculated in steps S103, S106, S107, and S108 are returned to the user terminal 300 in step S77 of FIG.

[0107] 19A to 19C show examples of calculation of the load value for one staff member. Fig. 19A shows the service provision load for each service type, Fig. 19B shows the travel load for each travel method, and Fig. 19C shows an example of calculation of the total load. In this embodiment, the service type in the visited information 322 in Fig. 6 can be specified as a combination of multiple service types in the unit load information 324a in Fig. 10. For example, "I2+child" in Fig. 19A indicates that I2 service was provided to a child user. "Medical care+terminal care" indicates that medical care was provided to a patient who requires terminal care.

[0108] In the example of Figure 19A, when a service defined by a combination of multiple service types is provided, the unit load is the product of the unit loads defined for each of the combined service types. For example, the unit load corresponding to the service type "I2 + Pediatric" is "2", which is the product of the unit load "1" for "I2" and the unit load "2" for "Pediatric". Similarly, the unit load for "Medical + Terminal Care" is 1 x 5 = 5.

[0109] In Figure 19A, if the service type in the table corresponds to one of the service types in Figure 10, the unit load of that service type is entered in the first unit load column, and if it corresponds to a combination of two service types in Figure 10, the unit loads of those two service types are entered in the first unit load and second unit load columns. Similarly, it may be possible to define the service actually provided by combining three or more service types. It is also possible to define the unit load as the sum of the unit loads defined for each of the combined service types.

[0110] The user terminal 300 can display the tabulated results on a load status screen 600 as shown in, for example, Fig. 20. The load status screen 600 includes a table display section 610. The raw data of the counting result transmitted in step S77 is displayed in a table format in the table display section 610. As in the case of the operation status screen 500, the numerical values ​​per day, etc. may be displayed.

[0111] The operator of the user terminal 300 can refer to this display and quantitatively grasp the load of each staff member due to the current work. Each load value can be used as reference information when allowing staff members to take vacations, balancing work loads, and determining fair treatment. One of the features of this embodiment is that the load value can be calculated by taking into account not only the service provision load but also the travel load. As in the case of tabulating the operating status, the load value can be calculated based on the schedule information 323 including information on the travel time between staff visits, making it easy to calculate the load value including the travel load. It is not essential that the operational status totalization system 100 transmits the service provision load and the movement load separately to the user terminal 300, and it is also possible to transmit only the total load calculated by taking these into consideration.

[0112] [Second embodiment: Figs. 21 to 25] Next, a second embodiment of the operation status totalizing system according to the present invention will be described with reference to FIGS. 21 shows the configuration of functions related to the operation status aggregation provided in each system related to the operation status aggregation by the operation status aggregation system 100 of the second embodiment. The same reference numerals are used to designate parts common to or corresponding to the configuration of the first embodiment, and description of parts common to the first embodiment will be omitted.

[0113] The second embodiment differs from the first embodiment in that the operating status tabulation system 100 tabulates the operating status of staff using chart information managed by the electronic medical record system, rather than schedule information. Accordingly, the schedule creation system 200 is not necessary in the second embodiment, and instead, the electronic medical record system 250 can be accessed and used from the user terminal 300. However, the operating status tabulation system 100 does not need to operate in conjunction with the electronic medical record system 250.

[0114] The operating status aggregation system 100 of the second embodiment includes a function of a travel time acquisition unit 114 in addition to the functions shown in FIG. The travel time acquisition unit 114 has a function of acquiring information on staff travel time by accessing the route search unit 411 of the route search system 400, in the same manner as the travel time acquisition unit 212 of the first embodiment, when the operation status aggregation unit 111 aggregates the operation status. Since the medical record information used by the operating status aggregation unit 111 to aggregate the operating status does not include information on travel time, when aggregating the operating status, the operating status aggregation unit 111 provides the necessary information included in the medical record information to the travel time acquisition unit 114 to acquire information on staff travel time.

[0115] The electronic medical record system 250 is a known system having a function of electronically managing medical records in a medical institution or the like, and has an information input receiving unit 251 and an information transmitting unit 253, and manages medical record information 252 of multiple patients or users. The information input receiving unit 251 has a function of editing the medical record information 252 in response to a request from a user terminal 300 which is a terminal of a user of the electronic medical record system 250 . The information transmission unit 253 also has a function of transmitting all or a part of the medical record information 252 to the user terminal 300 that has made the request, in response to a request from the user terminal 300 .

[0116] The user terminal 300 includes an information input receiving unit 311, an information display unit 312, an operation status compilation instruction receiving unit 341, a compilation request unit 342, a unit load information transmitting unit 343, and an operation status receiving unit 344, which correspond to the functions of the same names in Figure 3, as well as a medical chart entry receiving unit 351 and a medical chart information acquisition unit 352. The staff information 321, unit load information 324, and operating status information 325 used by these divisions are the same as those in FIG. 3, and the visit destination information 322 and schedule information 323 in FIG. 3 are not necessary.

[0117] Of the above, the medical record entry reception unit 351 has a function of receiving an editing operation of the medical record information 252 managed by the electronic medical record system 250, and obtains the medical record information 252 to be edited from the electronic medical record system 250 according to an operator's operation, and transmits an editing instruction to the information input reception unit 251. Information on the staff in charge of providing services such as medical examinations and nursing can be input by referring to the staff information 321.

[0118] When the operation status compilation instruction receiving unit 341 receives an instruction to compile operation status, the medical record information acquisition unit 352 has a function of making a request to the information transmission unit 253 of the electronic medical record system 250 to acquire visit records and addresses of visited destinations that satisfy the conditions of the compilation period and the compilation target staff from the medical record information 252, and passing them to the compilation request unit 342.

[0119] The tally request unit 342 has a function of extracting information required for tallying from the visit records acquired by the medical record information acquisition unit 352 in response to instructions received by the operation status tally instruction receiving unit 341, and also extracting information on the transportation method of each staff member from the staff information 321, and passing it to the operation status tallying unit 111 to request the tallying of the operation status. The functions of the other units are the same as those in the example of Fig. 3. Note that the operational status tallying unit 111 in the second embodiment corresponds to the first acquisition unit and the second acquisition unit, and also corresponds to the tallying unit together with the tallying result sending unit 113.

[0120] Next, Fig. 22 shows an example of the configuration of the medical chart information 252 shown in Fig. 21. The configuration and format of the medical chart information 252 are determined by the electronic medical chart system 250. Although the specific description format and data hierarchical structure may differ depending on the electronic medical chart system 250, information that is considered to be included in the medical chart information 252 in many electronic medical chart systems 250 will be described here.

[0121] As shown in Fig. 22, the medical record information 252 includes medical record data for each patient (which may include non-medical service users. The same applies to the following embodiment) for whom a medical record is to be created. In the example of Fig. 22, medical record data K1 to Kn3 for n3 people are included. Each medical record data includes information such as patient ID, name, address (visited location), other personal information, and visit records for each visit. The patient ID is identification information for uniquely identifying a patient. The name is the name of the patient whose information is to be entered in the medical record.

[0122] The address is the address of the patient, and can be used as location information of the destination when visiting to provide services. Other personal information is information that can identify a patient, such as age, gender, and telephone number, but is not used to compile operating status data.

[0123] A visit record is a record of services provided, such as medical examinations and nursing care, during a visit. Records of services provided other than visits may be mixed in, but it is necessary to distinguish them from records other than visits using some criteria so that only records related to visits can be extracted. In the example of FIG. 22, visit data is created for each visit as a record related to that visit, and n4 visit data KV1 to KVn4 are included.

[0124] Each visit data includes the visiting staff ID, visiting staff name, start date and time of the visit, end date and time of the visit, details of the examination / nursing, and prescription linkage information. The visiting staff ID and visiting staff name are the ID and name of the staff member in charge of the relevant visit, and are described using the staff ID and name registered in the staff information 321. Information on multiple people may be included. The service provision start date and time and the service provision end date and time are the date and time when the service provision at the corresponding visited destination starts and ends.

[0125] The medical examination / nursing details are information indicating the details of the service provided during the visit. It is preferable that this information includes at least information indicating one or more types of services provided. The service types in the unit load information 324a in FIG. 10 are created so that the correspondence with the service types described in the medical examination / nursing details can be understood. When the details of the provided services are described in natural language and mechanical correspondence is difficult, it is possible to estimate the correspondence using a trained model in which the correspondence is trained in a neural network.

[0126] In addition, it is preferable that the consultation / nursing content includes information on the time that the relevant service was provided for each type of service. However, if there is no direct description of the time, it is also possible to treat the stay time understood from the visit start date and time and the visit end date and time as the time of providing each service by appropriately allocating it to the services provided. The medical receipt linkage information is reference information for linking with a medical receipt management system for billing for the corresponding visit.

[0127] When an instruction to tally up the operating status is given, the medical record information acquisition unit 352 can identify the visit data to be tallied using the visiting staff ID, the visit start date and time, etc. as keys, and can acquire the visit data and the corresponding addresses of the visited destinations. With this information, the travel method, work start location, and work end location of each staff member in the staff information 321, and the unit load information 324, the operating status tabulation system 100 can tally up the operating status and calculate the load value in the same way as in the first embodiment.

[0128] Next, Fig. 23 shows the procedure of operation of each device when the performance status compilation system 100 shown in Fig. 21 collects the staff performance status in response to a user's instruction. The operation of each device shown in Fig. 23, particularly the operation executed by the performance status compilation system 100, is one example of the performance status compilation method of the present invention. In this case, it is assumed that the user of the user terminal 300 has used the electronic medical record system 250 by performing the operations up to step S124, and has registered in the electronic medical record system 250 information regarding the provision of services by visiting the customer.

[0129] That is, as a preparatory work, the user terminal 300 accepts input of staff information 321 and unit load information 324 in advance and stores them in an appropriate storage (S121). In addition, the user terminal 300 accepts instructions to fill in the electronic medical chart (S122), transmits a request to fill in the medical chart according to the instructions to the electronic medical chart system 250 (S123), and the electronic medical chart system 250 updates the medical chart information according to the request (S124).

[0130] Assuming that the above has been executed, when the user terminal 300 receives from the user the target period for tallying up staff operating status, the staff to be tallyed up, and tallying instructions (S131), it transmits a chart information acquisition request that specifies the specified target period and target staff to the electronic medical record system 250 (S132). Upon receiving this request, the electronic medical record system 250 acquires visit data that satisfies the target period and target staff sent from the medical record information 252 and data on the visit destinations of the visits indicated by the visit data (S133), and returns the acquired information to the user terminal 300 (S134). The user terminal 300 that receives this transmits the acquired chart information, the staff information 321 of the staff to be tabulated and the unit load information 324 saved in step S121, together with the operating status tabulation request to the operating status tabulation system 100 (S135).

[0131] When the operation status compilation system 100 receives this request, it performs the operation status compilation process shown in Figures 24 and 25 to create operation status compilation information for each staff member including the total visit time and total travel time of each staff member during the specified compilation period (S136). When compiling the operation status, the operation status compilation system 100 accesses the route search system 400 to automatically obtain travel time information (S141). Furthermore, the load calculation process shown in FIG. 18 in the first embodiment is performed to calculate load summary information including load values ​​related to service provision and load values ​​related to movement during the summary period for each staff member (S137).

[0132] The operation status compilation system 100 transmits the operation status compilation information and the load compilation information to the user terminal 300 (S138), and the user terminal 300 stores this in an appropriate storage as operation status information 325 (S139). In addition, in response to an operator's operation, the stored operation status information 325 can be displayed in the same manner as in the first embodiment (S140). In the above operations, step S135 is an example of the operations of the first acquisition procedure and the second acquisition procedure. Steps S136 and S138 are an example of the operations of the tallying procedure. Steps S137 and S138 are an example of the operations of the load value calculation procedure.

[0133] 24 and 25 show the operational status aggregation process in step S136 in more detail. In this process, the operating status totalization system 100 first performs a loop L31, sequentially treating the staff members to be totaled sent from the user terminal 300 as processing targets (staff member X) and repeats the process of a loop L32 and step S160.

[0134] In addition, in loop L32, the dates in the aggregation range are sequentially processed (date Y), and loop L33 and steps S157 to S159 are repeated. If the staff member's working hours span multiple dates, the period to be processed can be determined by using one working time slot as a unit. In addition, in loop L33, the process of steps S151 to S156 is repeated for the visit data of staff member X on date Y, for example, in order of visit time based on the data of the visit start time. The visit time order is used here to identify the order in which the staff member moved between the visit destinations.

[0135] In loop L33, the operating status aggregation system 100 first counts up the number of visits by staff X on date Y (S151). In addition, according to the medical examination / care details in the visit data to be processed, the operating status aggregation system 100 calculates the service provision time for each service type and counts it as the service provision time of staff X (S152).

[0136] Next, the operating status aggregation system 100 acquires the previous location and travel method for staff member X (S153), and transmits a travel time calculation request including the location of the destination related to the visit data to be processed to the route search system 400. In response to this request, the route search system 400 acquires the travel time from the previous location to the current destination (S154). This is a process for acquiring travel time information not included in the medical record information by the same process as steps S34 and S35 in FIG. 13, based on the location of the destination included in the medical record information.

[0137] The operation status aggregation system 100 counts the travel time acquired in step S154 as the travel time of staff X for each travel method (S155). In addition, based on the acquired travel time, the idling time is counted in the same manner as in step S94 of FIG. 16 (S156).

[0138] When processing of loop L33 is completed for all visit data to be processed, the operation status aggregation system 100 acquires the work end location and travel method for staff member X (S157), and, as in steps S154 and S155, acquires and counts the travel time from the last visit to the work end location from the route search system 400 (S158, S159).

[0139] This is the processing of loop L32. When processing of loop L32 is completed for all dates in the target period, the operation status aggregation system 100 calculates the total number of working days, number of visits, service provision time, travel time, and idling time for staff X in the target period based on the aggregation results up to this point, and creates the aggregation results for staff X (S160).

[0140] This is the processing of loop L31, and when the processing of loop L31 is completed for all staff members to be counted, the performance tabulation system 100 totals the number of visits, service provision time, travel time, and idling time for each staff member, and creates a counting result for all staff members (S161). This ends the performance tabulation process.

[0141] The counting results of steps S161 and S162 are returned to the user terminal 300 in step S138 of Fig. 23. As the counting results, information similar to that in the first embodiment can be created. Furthermore, the user terminal 300 can display the counting results in the same manner as in the first embodiment. Furthermore, by the above process, information on the service provision time for each service type and the travel time for each travel method for each staff member can be obtained. Therefore, the load value of each staff member can be calculated by the same process as in the first embodiment.

[0142] As described above, according to the operation status tabulation system 100 of the second embodiment, it is possible to tabulate the operation status of staff and calculate the load value while taking into account travel time, similarly to the first embodiment, based on the medical record information 252 of the electronic medical record system 250 that does not include information on travel time. This is because the route search system 400 is accessed to acquire travel time information based on the location information of each visit destination included in the medical record information 252 and the travel time information for each staff member that is separately prepared. Even if the medical record information 252 does not include information on the order of staff movement, by extracting information on visits made by a specific staff member in chronological order, it is possible to know that the staff moved in that order.

[0143] Businesses that provide medical, nursing, or care services usually create medical records, and in recent years, the number of businesses that adopt electronic medical record systems has been increasing. Therefore, if data can be tabulated using the data from the electronic medical record system as in the second embodiment, it is expected that the cost and effort required for tabulation can be reduced.

[0144] A similar system can be constructed by using, instead of the electronic medical record system 250, a prescription management system that has the function of electronically managing prescriptions created by medical institutions and other organizations to claim fees for medical treatment and nursing care. For the purpose of billing for medical fees, the medical receipt management system is expected to describe the content and time of services provided to customers more clearly and precisely than the medical record information 252. For this reason, by using medical receipt information managed by the medical receipt management system instead of the medical record information 252, it may be possible to more easily create unit load information 324a regarding services.

[0145] Businesses that provide medical insurance and nursing care insurance services usually create medical receipts, and in recent years, the number of businesses that adopt medical receipt management systems has been increasing. Therefore, if the data from the medical receipt management system can be used to compile the work status of staff, it is expected that the cost and effort required for compilation can be reduced, just as in the case of using the electronic medical record system 250.

[0146] Other possible systems that are assumed to manage information such as the content, time, person in charge, and location of services provided to customers (patients) include a daily report system for electronically creating and managing daily reports for each staff member, and an attendance management system for managing the attendance of each staff member. It is assumed that the data on the above-mentioned service content, etc., managed by these systems can also be used to tabulate the staff operating status and calculate the load value in the same manner as in the second embodiment.

[0147] [Third embodiment: FIG. 26] Next, a third embodiment of the operation status totalizing system according to the present invention will be described with reference to FIG. The third embodiment differs from the first embodiment in that each piece of information, from staff information 321 to operating status information 325, is held by the operating status aggregation system 100 or the schedule creation system 200, rather than by the user terminal 300. In addition, the functional configuration of each system differs accordingly. 26 shows the configuration of functions related to the operation status aggregation provided in each system related to the operation status aggregation by the operation status aggregation system 100 of the third embodiment. The same reference numerals are used to designate parts common to or corresponding to the configurations of the first and second embodiments, and a description of the common parts will be omitted.

[0148] First, the functions related to schedule creation will be described. 26, the user terminal 300 includes a schedule information input reception unit 361. The schedule information input reception unit 361 has a function of receiving editing operations of the staff information 321 and the visit information 322, and acquires information to be edited from the schedule creation system 200 according to the operation of the operator, and transmits an editing instruction to the information editing unit 213 of the schedule creation system 200. The information editing unit 213 has a function of editing the staff information 321 and the visit destination information 322 in response to this editing instruction.

[0149] The schedule creation instruction receiving unit 331 has a function of receiving instructions from a user to create a schedule by the schedule creation system 200 and a specification of the date range for which the schedule is to be created, and upon receiving the instruction, transmits a schedule creation request together with this specification information to the schedule creation unit 211 of the schedule creation system 200.

[0150] In response to this request, the schedule creation unit 211 creates schedule information 323 in the same manner as in the first embodiment. The created schedule information 323 is stored in an appropriate storage on the schedule creation system 200 side, and is provided to the user terminal 300 by the function of the schedule providing unit 214. It is also possible to provide the schedule information 323 in advance to the operation status aggregation system 100 so that the operation status aggregation system 100 can refer to the schedule information when aggregating the operation status. The schedule display unit 362 of the user terminal 300 has a function of displaying a schedule according to the schedule information 323 provided by the schedule providing unit 214 .

[0151] Next, we will explain the functions related to the aggregation of staff operating status. The user terminal 300 includes a tabulation information input receiving unit 363. The tabulation information input receiving unit 363 has a function of receiving an editing operation of the unit load information 324, and acquires information to be edited from the operation status tabulation system 100 in accordance with an operator's operation, and transmits an editing instruction to the information editing unit 115 of the operation status tabulation system 100. The information editing unit 115 has a function of editing the unit load information 324 in response to this editing instruction.

[0152] The operation status aggregation instruction receiving unit 341 has a function of receiving instructions from a user to have the operation status aggregation system 100 aggregate staff operation status, as well as the date range for aggregation and the staff to be aggregated. Upon receiving an instruction, the operation status aggregation request is sent to the operation status aggregation unit 111 of the operation status aggregation system 100 along with the specified information.

[0153] In response to this request, the operation status tabulation unit 111 and the load information calculation unit 112 tabulate the operation status of the staff and calculate the load information in the same manner as in the first embodiment. The operation status information 325 created as a result is stored in an appropriate storage on the operation status tabulation system 100 side, and is provided to the user terminal 300 by the function of the operation status providing unit 116. The timing of the creation of the operation status information 325 and the provision (output) to the user terminal 300 do not need to be close to each other. The operation status information 325 may be provided to the user terminal in response to a request from the user terminal 300 that is asynchronous with the creation of the operation status information 325. The operational status display unit 364 of the user terminal 300 has a function of displaying the operational status and load status of staff members according to the operational status information 325 provided from the operational status providing unit 116 in the same manner as in the first embodiment.

[0154] Here, the operating status compilation unit 111 refers to the schedule information 323 when compiling the operating status. Possible methods of this reference include referring to the schedule information 323 provided in advance from the schedule creation system 200 and stored in storage on the operating status compilation system 100 side, receiving the schedule information from the schedule providing unit 214 via an interface similar to that used when the user terminal 300 displays a schedule, accessing the schedule information 323 stored in the schedule creation system 200 via another interface, etc. In any case, it can be said that the schedule information 323 is stored in a storage unit that the operating status compilation unit 111 can refer to.

[0155] It is also possible to use an ETL (Extract-Transform-Load) tool or an ELT (Extract-Load-Transform) tool, and a database called a data warehouse, to transfer schedule information 323 between the schedule creation system 200 and the operation status compilation system 100. Even in this configuration, although a tool is interposed between them, the schedule information 323 created by the schedule creation system 200 is stored in a storage unit that can be referenced by the operation status compilation unit 111 after the transfer is completed.

[0156] Even in the above aspect, it is possible to tabulate the operating status of staff and calculate load values ​​in the same manner as in the first embodiment, and it is possible to obtain the same effects as in the first embodiment. In this embodiment, the schedule information 323 is provided from the schedule creation system 200 to the operation status collection system 100 without going through the user terminal 300. However, as in the first embodiment, there is no impediment to the schedule creation system 200 transmitting the schedule information 323 to the user terminal 300, and then transmitting it from the user terminal 300 to the operation status collection system 100. Furthermore, it is not essential that all of the staff information 321 to the operating status information 325 be stored on the schedule creation system 200 or the operating status compilation system 100 side; some of the information may be stored in the user terminal 300.

[0157] [Modifications] This concludes the explanation of the embodiment, but in this invention, the specific configurations of the systems and devices, specific processing procedures, data formats, network configurations, screen displays, calculation formulas used, etc. are not limited to those described in the embodiment.

[0158] For example, in the above embodiment, the services provided are medical, nursing, and care services, but the present invention is not limited to this. The schedule information, schedule creation system, daily report system, and attendance management system can be used regardless of the type of business, and the tabulation of staff operating status and calculation of load values ​​can be performed using these systems regardless of the type of business. The items to be tallied and displayed are not limited to those in the above-described embodiment.

[0159] In the above embodiment, the visiting time is calculated by using the service provision start time and the service provision end time at the visiting destination as the visiting time period information. However, it is also possible to calculate the visiting time by focusing on the stay time at the visiting destination from the arrival at the visiting destination to the departure from the visiting destination. The time from the start to the end of the visiting time to be calculated can be determined according to the purpose of the calculation.

[0160] When tabulating travel times, it is possible to consider various factors and correct the travel times included in the schedule information before tabulating, or to correct the travel times obtained from the route search system. For example, in an apartment building, it takes longer to move from entering the building to the customer's room compared to a single-family home, so it is possible to make corrections by taking into account the type of residence. Also, in snowy regions, it takes longer to move in winter than in summer, so it is possible to make corrections by taking into account the region and season (month).

[0161] In addition, in the above-described embodiment, an example was described in which the route search system 400 is provided separately from the operation status collection system 100 and the schedule creation system 200, but the functions of the route search system 400 can also be provided on-premise as part of the operation status collection system 100 or the schedule creation system 200 (as one of the functions provided by these systems).

[0162] Furthermore, an embodiment of the program of the present invention is a program for causing a computer to control the necessary hardware to realize one or more functions of the operational status aggregation system 100, the schedule creation system 200, and the user terminal 300 in the above-described embodiments.

[0163] Such a program may be stored in a ROM or other non-volatile storage medium (flash memory, EEPROM, etc.) that is included in the computer from the beginning. However, it may also be provided by recording it on any non-volatile recording medium such as a memory card, CD, DVD, or Blu-ray disc. By installing the program recorded on such a recording medium on a computer and executing it, each of the above-mentioned functions can be realized.

[0164] Furthermore, it is also possible to download the program from an external device connected to a network and having a recording medium on which the program is recorded, or from an external device having the program stored in a storage means, and install the program on a computer for execution. Furthermore, it goes without saying that the configurations of the respective embodiments and modified examples described above can be implemented in any combination as long as they are not mutually inconsistent. [Explanation of symbols]

[0165] 100: operation status aggregation system, 200: schedule creation system, 250: electronic medical record system, 300: user terminal, 400: route search system, 500: operation status screen, 510, 610: table display unit, 600: load status screen

Claims

1. An operating status tabulation system that is configured by one computer or a plurality of computers working in cooperation with each other and tabulates the operating status of staff who visit targets and provide services, an acquisition unit that acquires schedule information including visiting time period information indicating the time period during which the staff visits the subject and travel time information indicating inter-visit travel time, which is the travel time to the next visit location after each visit, as schedule information of each staff member to be tabulated; and a calculation unit that creates calculation information for each staff member indicating the total visit time and total travel time of each staff member within a specified calculation period based on the visit time zone information and travel time information of each staff member to be calculated, which are included in the schedule information acquired by the acquisition unit, and outputs the calculation information to a specified output destination.

2. The operation status tabulation system according to claim 1, An operational status aggregation system characterized by having a schedule creation unit that accepts input of the location to be visited, desired time of visit, and desired service for each person to be provided with a service, and accepts input of working hours and transportation method for each staff member, and based on this, creates the schedule information that specifies a schedule for each staff member to visit each person and provide the service.

3. The operation status tabulation system according to claim 2, The operation status aggregation system, wherein the service is a medical, nursing or care service.

4. An operating status tabulation system that is configured by one computer or a plurality of computers working in cooperation with each other and tabulates the operating status of staff who visit targets and provide services, a first acquisition unit that acquires, from a predetermined acquisition source, information on a visited location, a visited time period, and information on a visiting staff member as information on a service provided within a predetermined collection period; A second acquisition unit that acquires a working time period and a travel method of each staff member; a travel time acquisition unit that extracts, from the information acquired by the first acquisition unit, visited locations and visiting time periods visited by the staff member to be counted for each working time period of the staff member in chronological order, and acquires travel time information indicating inter-visit travel time, which is the travel time from each visited location to the next visited location, from the route search system in response to transmitting, for each visited location acquired, the location of the visited location, the location of the next visited location, and information on the travel method of the staff member acquired by the second acquisition unit to a predetermined route search system; and a calculation unit that creates calculation information indicating the total visit time and total travel time of each staff member to be calculated during the specified calculation period based on the information acquired by the first acquisition unit and the travel time information acquired by the travel time acquisition unit, and outputs the calculation information to a specified output destination.

5. The operation status tabulation system according to claim 4, The service is a medical, nursing or care service, An operation status aggregation system, characterized in that the source of data acquisition is an electronic medical record system, a prescription management system, a daily report system, or an attendance management system.

6. The operation status tabulation system according to claim 2 or 3, The schedule information includes work time information indicating the work time of each staff member, The travel time information includes information on a departure travel time, which is a travel time from a work start location to a first visit location within a work hour, and / or information on a return travel time, which is a travel time to a work end location after the end of the last visit within the work hour, The operation status aggregation system is characterized in that, when determining a total travel time corresponding to one working time slot within the specified aggregation period, the aggregation unit adds the departure travel time and / or the return travel time to the inter-visit travel time corresponding to each visit within that working time slot.

7. The operation status tabulation system according to claim 4 or 5, The second acquisition unit also acquires information on the start location and / or end location of the staff member for each staff member, the travel time acquisition unit performs a process of acquiring a departure travel time, which is the travel time from the work start location to the first visited location, from a predetermined route search system in response to transmitting information on the location of each staff member's work start location, the location of the first visited location within the work hours, and the staff member's travel method to the predetermined route search system; and / or a process of acquiring a return travel time, which is the travel time from the last visited location to the work end location, from the route search system in response to transmitting information on the location of each staff member's last visited location within the work hours, the location of the work end location, and the staff member's travel method to the predetermined route search system; The operation status aggregation system is characterized in that, when determining a total travel time corresponding to one working time slot within the specified aggregation period, the aggregation unit adds the departure travel time and / or the return travel time to the inter-visit travel time corresponding to each visit within that working time slot.

8. The operation status tabulation system according to claim 2 or 3, The schedule information includes provided service information indicating the type and time of service to be provided during each visit, and transportation method information indicating the transportation method to be used by the staff for each trip, a load information acquisition unit that acquires service load information indicating a load per unit time for each type of service and travel load information indicating a load per unit time for each travel method; an operation status aggregation system comprising: a load value calculation unit that calculates a load value related to service provision for each staff member based on the provided service information related to each visit within the specified aggregation period by referring to service load information among the information about each staff member to be aggregated that is included in the schedule information acquired by the acquisition unit; calculates a load value related to travel for each staff member based on the travel time information and the travel method information related to each visit within the specified aggregation period by referring to travel load information; and outputs the calculated load value to the specified output destination.

9. The operation status tabulation system according to claim 4 or 5, the information on the provided service acquired by the first acquisition unit includes provided service information indicating a type and a time of the provided service, a third acquisition unit that acquires service load information indicating a load per unit time for each type of service and travel load information indicating a load per unit time for each travel method; an operation status aggregation system comprising: a load value calculation unit that calculates a load value related to service provision for each staff member based on the provided service information related to each visit within the specified aggregation period, which is included in the information acquired by the first acquisition unit, by referring to the service load information; calculates a load value related to travel for each staff member based on the travel time information related to each visit within the specified aggregation period and the travel method of the staff member acquired by the second acquisition unit, by referring to the travel load information; and outputs the calculated load value to the specified output destination.

10. The operation status tabulation system according to claim 2 or 3, The schedule creation unit, when creating the schedule information, sets a schedule of one visit and the next visit for a certain staff member as candidates, and in response to sending the location of the first visit, the location of the next visit, and the travel method of the certain staff member to a predetermined route search system, obtains from the route search system the travel time from the location of the first visit to the location of the next visit, and while securing the obtained travel time between the first visit and the next visit as the inter-visit travel time, if the time zone of the first visit and the time zone of the next visit satisfy the desired visiting time for each visit and can be set within the working hours of the certain staff member, registers visiting time zone information indicating the time zone of the visit and the inter-visit travel time as schedule information for the certain staff member.

11. A method for tabulating operational status of staff who visit a target person and provide a service, the method being executed by one computer or a plurality of computers working in cooperation with each other, comprising: An acquisition step of acquiring schedule information including visiting time period information indicating the time period during which the staff visits the subject and travel time information indicating the travel time between visits, which is the travel time to the next visit location after each visit, as schedule information of each staff member to be tabulated; and a calculation step of creating calculation information for each staff member indicating the total visit time and total travel time of each staff member within a specified calculation period based on the visit time zone information and travel time information of each staff member to be calculated, which are included in the schedule information acquired in the acquisition step, and outputting the calculation information to a specified output destination.

12. The operating status tabulation method according to claim 11, The method for aggregating operational status comprises a schedule creation step of accepting input of a visit location, desired visit time, and desired service for each person to be provided with a service, and accepting input of working hours and transportation method for each staff member, and creating the schedule information based on the above, which specifies a schedule for each staff member to visit each person and provide the service.

13. The operation status tabulation method according to claim 12, The operating status aggregation method, wherein the service is a medical, nursing or care service.

14. A method for tabulating operational status of staff who visit a target person and provide a service, the method being executed by one computer or a plurality of computers working in cooperation with each other, comprising: a first acquisition step of acquiring information on a visited location, a visited time period, and a visiting staff member as information on a service provided within a predetermined collection period from a predetermined acquisition source; A second acquisition step of acquiring a working time period and a travel method of each staff member; a travel time acquisition step of extracting, from the information acquired in the first acquisition step, visited locations and visiting time periods visited by the staff member to be counted for each working time period of the staff member in chronological order, and, in response to transmitting, for each of the acquired visited locations, the location of the visited location, the location of the next visited location, and information on the travel method of the staff member acquired in the second acquisition step to a predetermined route search system, acquiring travel time information from the route search system indicating inter-visit travel time, which is the travel time from each visited location to the next visited location; and a calculation step of creating calculation information indicating the total number of visiting hours and the total travel time of each staff member to be calculated during the specified calculation period based on the information acquired in the first acquisition step and the travel time information acquired in the travel time acquisition step, and outputting the calculation information to a specified output destination.

15. The operating status tabulation method according to claim 14, The service is a medical, nursing or care service, An operating status aggregation method, characterized in that the source of data acquisition is an electronic medical record system, a prescription management system, a daily report system, or an attendance management system.

16. The operation status tabulation method according to claim 12, The schedule information includes work time information indicating the work time of each staff member, The travel time information includes information on a departure travel time, which is a travel time from a work start location to a first visit location within a work hour, and / or information on a return travel time, which is a travel time to a work end location after the end of the last visit within the work hour, a calculation step of calculating a total travel time corresponding to one working time slot within the specified calculation period by adding the departure travel time and / or the return travel time to an inter-visit travel time corresponding to each visit within the working time slot.

17. The operating status tabulation method according to claim 14, In the second acquisition step, information on the start and / or end location of the staff member is also acquired for each staff member; In the travel time acquisition step, in response to transmitting information on the location of each staff member's work start location, the location of the first location visited during work hours, and the travel method of the staff member to a predetermined route search system, a process of acquiring a departure travel time, which is the travel time from the work start location to the first location visited, from the route search system; and / or in response to transmitting information on the location of each staff member's last location visited during work hours, the location of the work end location, and the travel method of the staff member to the predetermined route search system, a process of acquiring a return travel time, which is the travel time from the last location visited to the work end location, from the route search system; a calculation step of calculating a total travel time corresponding to one working time slot within the specified calculation period by adding the departure travel time and / or the return travel time to an inter-visit travel time corresponding to each visit within the working time slot.

18. The operation status tabulation method according to claim 12, The schedule information includes provided service information indicating the type and time of service to be provided during each visit, and transportation method information indicating the transportation method to be used by the staff for each trip, a load information acquisition step of acquiring service load information indicating a load per unit time for each type of service and travel load information indicating a load per unit time for each travel method; a load value calculation step of calculating a load value related to service provision for each staff member based on the provided service information related to each visit within the specified collection period by referring to service load information among the information related to each staff member to be collected that is included in the schedule information acquired in the acquisition step, calculating a load value related to travel for each staff member based on the travel time information and the travel method information related to each visit within the specified collection period by referring to travel load information, and outputting the calculated load value to the specified output destination.

19. The operating status tabulation method according to claim 14, The information on the provided service acquired in the first acquisition step includes provided service information indicating a type and a time of the provided service, a third acquisition step of acquiring service load information indicating a load per unit time for each type of service and travel load information indicating a load per unit time for each travel method; a load value calculation step of calculating a load value related to service provision for each staff member based on the provided service information for each visit within the specified aggregation period, including information regarding visits by each staff member to be aggregated, which is included in the information acquired in the first acquisition step, by referring to the service load information; calculating a load value related to travel for each staff member based on the travel time information for each visit within the specified aggregation period and the travel method of the staff member acquired in the second acquisition step, by referring to the travel load information; and outputting the calculated load value to the specified output destination.

20. The operation status tabulation method according to claim 12, The schedule creation procedure is a procedure for creating the schedule information by setting a schedule of one visit and the next visit for a certain staff member as candidates, transmitting the location of the first visit, the location of the next visit, and the travel method of the certain staff member to a predetermined route search system, obtaining from the route search system the travel time from the location of the first visit to the location of the next visit, and, while reserving the obtained travel time between the first visit and the next visit as the inter-visit travel time, if the time zone of the first visit and the time zone of the next visit satisfy the desired visiting time for each visit and can be set within the working hours of the certain staff member, registering visiting time zone information indicating the time zone of the visit and the inter-visit travel time as schedule information for the certain staff member.

21. A program for causing one computer or a plurality of computers to cooperate with each other to execute each step of the operation status compilation method according to any one of claims 11 to 20.

Images