JP2009265866A - Service management server, service management method, and service management system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To instantaneously confirm whether or not a service provider provides a service as scheduled. <P>SOLUTION: A service management server 100 is configured to be communicable with a service provider mobile terminal carried by a service provider who provides a prescribed service. The service management server includes: a storage part 160 for storing plan information 161 showing a prescribed service to be provided by the service provider; a recording image information receiving part 120 for receiving recording image information 162 as image information acquired by photographing the content of the service provided by the service provider from the service provider mobile terminal; a format conversion part 130 for generating recording information 164 by converting the recording image information 162 into a text data format; and a service content collation part 140 for collating the recording information 164 with the plan information 161. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a service management server, a service management method, and a service management system.

  In general, in a conventional technique, a service provider who provides a predetermined service at a business trip destination such as a service user's home records a service provided after the service provider provides the service (hereinafter referred to as service provision implementation). Record). Thereafter, the service provider confirms the contents entered by the service user, receives a signature from the service user, and takes the service provision execution record from the business trip destination to the office or the like.

  The service provider submits several days of the service provision implementation records brought back together on a date designated by the manager of the service provider. The administrator confirms the service provision execution record submitted by the service provider, and pays the salary corresponding to the service provision execution record to the service provider. Further, when the service provider is a helper or the like, the local government or the like is charged a reward corresponding to the contents of the service provision execution record.

  Further, when the service provider finishes providing the service, the service provider inputs information indicating the service actually performed to the terminal carried by the service provider, and transmits the input information to the information management center side device via the terminal. Is disclosed (for example, see Patent Document 1). According to this technology, the difference between the service actually provided and the information recorded in advance in the storage device of the information management center side device as the service to be provided is determined by the display device of the information management center side device. This can be confirmed by referring to the figures and tables output in.

JP 2001-273368 A

  However, according to the conventional technology, the administrator confirms the service provision execution record several days after the service provider provides the service at the service user's home, so the service provision content cannot be confirmed immediately. There was a problem. For this reason, when the service provider does not provide the service as scheduled, it cannot be grasped until a few days later that the service provision execution record is not provided according to the schedule. In such a case, the salary payment contents to the service provider are also inadequate because the service is not provided as contracted. In addition, when the service provider is a helper or the like, when charging the nursing care service to the local government or the like, the service provision execution record does not match the care plan, so that the billing content is incomplete.

  Further, according to the technique disclosed in Patent Document 1, it is possible to confirm whether or not the service provider provides the service as scheduled. However, the information management center side device cannot automatically determine whether the service provider provides the service as scheduled. Therefore, it is necessary to visually confirm the content output to the information management center side apparatus, and there is a problem that it cannot be immediately confirmed. Furthermore, since a long time is required for the service provider to input information indicating the service actually performed to the terminal carried by the service provider, there is a problem in that it cannot be immediately confirmed.

  Therefore, the present invention has been made in view of the above problems, and an object of the present invention is to immediately confirm whether or not the service provider provides the service as scheduled. A service management server, a service management method, and a service management system are provided.

  In order to solve the above problem, according to an aspect of the present invention, there is provided a service management server capable of communicating with a service provider mobile terminal that is a terminal carried by a service provider that provides a predetermined service, Recorded image information that is image information obtained by photographing the content of the service provided by the service provider from the storage unit that stores the plan information indicating the service scheduled to be provided by the service provider and the service provider mobile terminal A recording image information receiving unit that receives the recording image, a format conversion unit that generates recording information by converting the recording image information into a text data format, and a service content verification unit that collates the recording information and the plan information. A service management server is provided.

  As described above, according to the present invention, it is possible to provide a service management server, a service management method, and a service management system capable of immediately confirming whether a service provider provides a service as scheduled. Can do.

  Exemplary embodiments of the present invention will be described below in detail with reference to the accompanying drawings. In addition, in this specification and drawing, about the component which has the substantially same function structure, duplication description is abbreviate | omitted by attaching | subjecting the same code | symbol.

  FIG. 1 is a diagram showing a configuration of a service management system according to the present embodiment. With reference to FIG. 1, the structure of the service management system according to the present embodiment will be described.

  As shown in FIG. 1, in the service management system 10, a service management server 100 and a service provider mobile terminal 200 can communicate with each other. Here, as shown in FIG. 1, one service provider mobile terminal 200 may be connected, or a plurality of service provider mobile terminals 200 may be connected. In addition, the service management server 100 and the service provider portable terminal 200 are connected via a network 400 such as the Internet as shown in FIG. The service management system 10 may include an administrator terminal 300 that can communicate with the service management server 100. In that case, as shown in FIG. 1, the administrator terminal 300 and the service management server 100 are connected via a network 400, for example.

  The service management server 100 is provided by a service such as ASP (Application Service Provider). For example, it is always connected to the network 400. The detailed configuration of the service management server 100 will be described later with reference to FIG.

  The service provider portable terminal 200 is a terminal carried by a service provider that provides a predetermined service. The service provider portable terminal 200 can store recorded image information that is image information obtained by photographing a service provision execution record 210 (see FIG. 3) that is a content of a service provided by the service provider. Has been. Further, the service provider mobile terminal 200 can transmit the image information to the service management server 100 by a button press operation of the service provider mobile terminal 200 by the service provider. The service provider mobile terminal 200 may transmit image information and information for identifying the service provider (for example, the terminal ID of the administrator terminal 300 or the service provider name).

  The service provider mobile terminal 200 may be a mobile phone, for example. In that case, the service provider mobile terminal 200 is connected to the network 400 via a mobile phone operator or the like. The service provider portable terminal 200 can store at least image information, and may further include a built-in camera. In that case, the service provider can capture and obtain the contents of the provided service using the built-in camera. The service provider portable terminal 200 may include a display unit. In that case, the information transmitted from the service management server 100 can be output to the display unit.

  The administrator terminal 300 is a terminal used by an administrator who manages a service provider, and is, for example, a PC (Personal Computer). The administrator terminal 300 may be able to transmit plan information 161 (see FIG. 4) indicating a service scheduled to be provided by the service provider to the service management server 100. In this case, information such as the user ID 161a, the user name 161b, and the use service 161c shown in FIG. 4 is input by the administrator according to the plan created by the planner (care manager or the like). In addition, the administrator terminal 300 may include a display unit. In that case, the information transmitted from the service management server 100 can be output to the display unit.

  FIG. 2 is a diagram illustrating a configuration of the service management server according to the present embodiment. With reference to FIG. 2 (refer to FIG. 1 as appropriate), the configuration of the service management server according to the present embodiment will be described.

  As shown in FIG. 2, the service management server 100 includes at least a recorded image information receiving unit 120, a format conversion unit 130, a service content verification unit 140, and a storage unit 160. Further, the plan information receiving unit 110 may be included, and the mismatch content transmitting unit 150 may be included. Each component in the service management server 100 illustrated in FIG. 2 is controlled by, for example, a CPU (Central Processing Unit) executing a program (not illustrated) stored in the storage unit 160. The format conversion unit 130 and the service content verification unit 140 are realized by a CPU or the like.

  The storage unit 160 stores information, and is realized, for example, by a RAM (Random Access Memory).

  The plan information receiving unit 110 is a communication interface and receives plan information 161 from the administrator terminal 300. The plan information 161 will be described later with reference to FIG. The recorded image information receiving unit 120 stores the received recorded image information 162 in the storage unit 160. Here, the plan information 161 received by the plan information receiving unit 110 is stored in the storage unit 160, but may be stored in the storage unit 160 by other techniques.

  The recorded image information receiving unit 120 is a communication interface, and receives recorded image information 162 that is image information obtained by photographing the contents of the service provided by the service provider from the service provider portable terminal 200. is there. The contents of the service are described on paper in a format such as a service provision execution record 210 (see FIG. 3). The service provision execution record 210 will be described later with reference to FIG. The recorded image information receiving unit 120 stores the received recorded image information 162 in the storage unit 160.

  The format conversion unit 130 generates recording information 164 by converting the recording image information received by the recording image information receiving unit 120 into a text data format. The technique for converting the recorded image information into the text data format is not particularly limited. For example, the pattern information 163 is stored in the storage unit 160, and the format conversion unit 130 uses the pattern information 163 to record the recorded image information. This is done by recognizing characters. Conversion can also be performed using OCR (Optical Character Reader) software or the like. The recorded information 164 will be described later with reference to FIG. The format conversion unit 130 stores the recording information 164 obtained by the conversion in the storage unit 160.

  The service content collating unit 140 collates the recorded information 164 with the plan information 161. In this verification, at least the usage service 161c (see FIG. 4) included in the plan information 161 and the usage service 164c (see FIG. 5) included in the recorded information 164 are verified. Here, as will be described later with reference to FIG. 4, the usage service 161 c is a service name that is information for identifying the service, and whether the service is to be implemented or not (not implemented). One or a plurality of pieces of information (execution information) to be shown are associated with each other. Similarly, as will be described later with reference to FIG. 5, the use service 164c is a service name that is information for identifying the service, and information (implementation) indicating whether the service is implemented or not implemented (not implemented). Information) is associated with one or more information. In the verification between the usage service 161c and the usage service 164c, the service content verification unit 140 verifies whether or not the implementation information corresponding to the same service name matches between the usage service 161c and the usage service 164c. . For example, if the execution information matches for all service names, it is regarded as a match, and if the execution information does not match for at least one service name, it is regarded as a mismatch.

  When there are a plurality of users of the service, the plan information 161 includes a user ID 161a (see FIG. 4) and the recorded information 164 is used as described later with reference to FIGS. It is good also as including person ID164a (refer FIG. 5). In this case, the use service 164c searches the user ID 161a (see FIG. 4) included in the plan information 161 using the user ID 164a (see FIG. 5) as a key, and the use service 161c (see FIG. 4) obtained by the search. 4) and the use service 164c (see FIG. 5) included in the recorded information 164 are collated.

  The mismatch content transmission unit 150 is a communication interface, and when the result of verification by the service content verification unit 140 is mismatch, at least one of the service provider mobile terminal 200 and the administrator terminal 300 is verified. The information indicating that the results of these are mismatched (mismatch information) is transmitted. Here, the mismatch information may include mismatch content. The content of the mismatch is at least implementation information (whether or not the service is implemented) corresponding to the same service name (name of service available to the service user) between the usage service 161c and the usage service 164c. If there is a mismatch between the information), the service name is included as the service name in which the mismatch occurred. The mismatch information may include a user ID 164a, a user name 164b, information for identifying a service provider, a collation time, and the like.

  FIG. 3 is a diagram showing a description example of the service provision execution record according to the present embodiment. With reference to FIG. 3, a description example of the service provision execution record according to the present embodiment will be described.

  As shown in FIG. 3, the service provision execution record 210 includes at least a usage service 240. The usage service 240 includes a column describing that the service has been implemented and a column describing that the service has not been implemented (not implemented) corresponding to each of one or more service names that are information for identifying the service. And are provided. In each column, for example, a service provider can put a check mark with a writing instrument.

  When there are a plurality of service users, the service provision execution record 210 includes a user ID 220. As a result, the user ID 220 is associated with the usage service 240. The service provision execution record 210 may include the user name 230. The service provision execution record 210 may be provided with a column in which a sign indicating that the service user approves the service provided by the service provider is written. The user ID 220, the user name 230, and the use service 240 can be described by a service provider using a writing tool or the like on paper.

  FIG. 4 is a diagram illustrating a configuration example of plan information according to the present embodiment. With reference to FIG. 4, the structural example of the plan information which concerns on this embodiment is demonstrated.

  As shown in FIG. 4, the plan information 161 indicating the service scheduled to be provided by the service provider includes at least the usage service 161c. In the usage service 161c, one or a plurality of service names, which are information for identifying the service, and information (execution information) indicating whether the service is planned to be implemented or not implemented (not implemented) are associated with each other. It is configured.

  When there are a plurality of service users, the plan information 161 includes a user ID 161a. Thereby, the user ID 161a and the usage service 161c are associated with each other. The plan information 161 may include a user name 161b.

  FIG. 5 is a diagram showing a configuration example of recorded information according to the present embodiment. With reference to FIG. 5, a configuration example of recording information according to the present embodiment will be described.

  As shown in FIG. 5, the record information 164 includes at least the usage service 164c. The use service 164c is configured by associating one or a plurality of service names, which are information for identifying services, with information (implementation information) indicating whether the service is implemented or not implemented (not implemented).

  When there are a plurality of service users, the recorded information 164 includes a user ID 164a. Thus, the user ID 164a and the usage service 164c are associated with each other. The recorded information 164 may include a user name 164b.

  FIG. 6 is a flowchart showing a flow of processing executed by the service management system according to the present embodiment. With reference to FIG. 6 (refer to other figures as appropriate), processing executed by the service management system according to the present embodiment will be described.

(Registration of plan information 161)
The administrator terminal 300 receives input of plan information 161 indicating a service scheduled to be provided by the service provider from the administrator of the service provider (step S101). The administrator terminal 300 transmits the plan information 161 input from the service provider administrator to the service management server 100 via the network 400. The service management server 100 receives the plan information 161 from the administrator terminal 300 via the network 400 (step S102). The service management server 100 stores the received plan information 161 in the storage unit 160.

(Transmission of recorded image information 162)
After providing the service to the service user, the service provider fills in the service provision execution record 210 composed of a paper medium or the like by handwriting using a writing tool. The service user writes a sign indicating approval for the service provided by the service provider in a predetermined column of the service provision execution record 210. The signature may be a seal.

  After receiving the signature, the service provider photographs the service provision execution record 210 with the built-in camera mounted on the service provider portable terminal 200 carried by the service provider. The service provider portable terminal 200 acquires the recorded image information 162 by photographing (step S111). When the service provider mobile terminal 200 does not have a built-in camera, the service provider implementation terminal 210 is photographed by a camera separate from the service provider mobile terminal 200, and the camera is provided to the service provider mobile terminal 200 from the camera. Then, the recorded image information 162 obtained by photographing is captured.

  The service provider portable terminal 200 transmits the recorded image information 162 to the service management server 100 via the network 400. For example, the service provider portable terminal 200 transmits the recorded image information 162 attached to an electronic mail.

(Processing executed by the service management server 100)
The recorded image information receiving unit 120 of the service management server 100 receives the recorded image information 162 transmitted from the service provider portable terminal 200 (step S112). The recorded image information receiving unit 120 stores the received recorded image information 162 in the storage unit 160.

  The format conversion unit 130 generates the recording information 164 by converting the recording image information 162 stored in the storage unit 160 into a text data format (step S113). The recording information 164 generated by converting to the text data format has the same format as the plan information 161.

  The service content collation unit 140 collates the recorded information 164 with the plan information 161 (step S114). As described above, the plan information 161 includes at least the usage service 161c, and the record information 164 includes at least the usage service 164c.

  If the result of verification by the service content verification unit 140 does not match (“No match” in step S114), the mismatch content transmission unit 150 indicates that the service provider did not provide the service as scheduled. Information indicating that the collation result is inconsistent is transmitted to at least one of the service provider portable terminal 200 and the administrator terminal 300 (steps S115 and S116).

  If the result of collation by the service content collation unit 140 is coincident (“match” in step S114), the mismatch content transmission unit 150 indicates that the service provider has provided the service as scheduled. finish.

  When the administrator terminal 300 receives information indicating that the collation result is mismatched, the administrator terminal 300 outputs information indicating that the collation result is mismatched (mismatch information) to the display unit as an alert (step S117). The mismatch information output to the display unit of the administrator terminal 300 will be described later with reference to FIG.

  When the service provider portable terminal 200 receives the information indicating that the collation result is mismatched, the service provider portable terminal 200 outputs information indicating that the collation result is mismatched (mismatch information) to the display unit as an alert (step S118). . The mismatch information output to the display unit of the service provider portable terminal 200 will be described later with reference to FIG.

  FIG. 7 is a diagram illustrating an example of mismatch information output to the display unit of the administrator terminal according to the present embodiment. With reference to FIG. 7, an example of the mismatch information output to the display unit of the administrator terminal according to the present embodiment will be described.

  As shown in FIG. 7, the mismatch information is automatically output to the display unit of the administrator terminal 300. For example, a window displaying disagreement information may be popped up with a buzzer sounding to notify the administrator that the collation disagreement has occurred.

  FIG. 8 is a diagram illustrating an example of mismatch information output to the display unit of the service provider portable terminal according to the present embodiment. With reference to FIG. 8, an example of the mismatch information output to the display unit of the service provider portable terminal according to the present embodiment will be described.

  As shown in FIG. 8, the mismatch information is automatically output on the display unit of the service provider portable terminal 200. The service provider can confirm that a verification mismatch has occurred by referring to the mismatch information.

  According to the present embodiment, it is possible to immediately confirm whether or not the service provider provides the service as scheduled. Since the administrator can confirm the service provision execution record 210 immediately after the service provider performs the service at the service user's home, the service contents can be managed in real time. Therefore, when the service provider does not provide the service as planned, it can be immediately grasped that the service provision execution record 210 is not the implementation content as planned. In addition, since the service provider can immediately notice the service omission and the like, if it can be confirmed that the service has been performed as planned, it can be withdrawn immediately. Furthermore, since the service is executed as contracted, the salary payment to the service provider can be performed properly. In addition, when the service provider is a helper or the like, when the nursing care service fee is charged to the local government or the like, the service provision execution record 210 matches the plan, so the billing contents are accurate.

  In addition, by confirming approval by signing from a service user or a seal, it is possible to suppress fraudulent reporting of service results and unfair compensation claims.

  The preferred embodiments of the present invention have been described in detail above with reference to the accompanying drawings, but the present invention is not limited to such examples. It is obvious that a person having ordinary knowledge in the technical field to which the present invention pertains can come up with various changes or modifications within the scope of the technical idea described in the claims. Of course, it is understood that these also belong to the technical scope of the present invention.

  For example, in the present embodiment, what service the service provider provides is not particularly limited. For example, the service provider may be a care service provider or a person who provides irregular or one-time visit services such as a piano tuner or a babysitter.

It is a figure which shows the structure of the service management system which concerns on this embodiment. It is a figure which shows the structure of the service management server which concerns on this embodiment. It is a figure which shows the example of a description of the service provision implementation record which concerns on this embodiment. It is a figure which shows the structural example of the plan information which concerns on this embodiment. It is a figure which shows the structural example of the recording information which concerns on this embodiment. It is a flowchart which shows the flow of the process which the service management system which concerns on this embodiment performs. It is a figure which shows an example of the discrepancy information output to the display part of the administrator terminal which concerns on this embodiment. It is a figure which shows an example of the discrepancy information output to the display part of the service provider portable terminal which concerns on this embodiment.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 Service management system 100 Service management server 110 Plan information receiving part 120 Recorded image information receiving part 130 Format conversion part 140 Service content collation part 150 Disagreement content transmission part 160 Storage part 161 Plan information 162 Recorded image information 163 Pattern information 164 Record information 200 Service provider mobile terminal 210 Service provision execution record 300 Administrator terminal 400 Network

Claims (6)

A service management server capable of communicating with a service provider mobile terminal that is a terminal carried by a service provider that provides a predetermined service;
A storage unit for storing plan information indicating a service scheduled to be provided by the service provider;
A recorded image information receiving unit that receives recorded image information that is image information obtained by photographing the content of the service provided by the service provider from the service provider mobile terminal;
A format converter for generating recording information by converting the recording image information into a text data format;
A service content collation unit for collating the record information with the plan information;
A service management server comprising: A mismatch content transmission unit that transmits information indicating that the collation result is inconsistent to the service provider portable terminal when the collation result by the service content collation unit is mismatch; The service management server according to claim 1, wherein the service management server is characterized in that: A service management server having a storage unit that stores plan information indicating a service scheduled to be provided by the service provider and capable of communicating with a service provider portable terminal that is a terminal carried by a service provider that provides a predetermined service Service management method by
A recorded image information receiving unit receiving, from the service provider portable terminal, recorded image information that is image information obtained by photographing the content of the service provided by the service provider;
A format conversion unit that generates recording information by converting the recording image information into a text data format;
A service content collation unit collating the record information with the plan information;
A service management method comprising: A terminal that is carried by a service provider that provides a predetermined service, and that includes a service provider portable terminal that transmits recorded image information that is image information obtained by photographing the content of the service provided by the service provider. With
A storage unit for storing plan information indicating a service scheduled to be provided by the service provider;
A recorded image information receiving unit for receiving the recorded image information from the service provider portable terminal;
A format converter for generating recording information by converting the recording image information into a text data format;
A service content collation unit for collating the record information with the plan information;
A service management system comprising: a service management server. It is a terminal carried by a service provider that provides a predetermined service, and includes a service provider portable terminal that transmits recorded image information that is image information obtained by photographing the content of the service provided by the service provider. With
A terminal used by an administrator who manages the service provider, and includes an administrator terminal that transmits plan information indicating a service scheduled to be provided by the service provider;
A storage unit;
A plan information receiving unit that receives the recording information from the manager terminal and stores it in the storage unit;
A recorded image information receiving unit for receiving the recorded image information from the service provider portable terminal;
A format converter for generating recording information by converting the recording image information into a text data format;
A service content collation unit for collating the record information with the plan information;
A service management system comprising: a service management server. The service management server
When the result of verification by the service content verification unit is inconsistent, at least information indicating that the result of verification is inconsistent with respect to any one of the service provider mobile terminal and the administrator terminal. The service management system according to claim 5, further comprising: a mismatch content transmission unit for transmission.

Images