JP7173539B2 - Service provision support device and service provision support method - Google Patents

Description

The present invention relates to a service provision support device and a service provision support method.

In the field of medical care, in order to provide medical services to a single patient, multiple hospitals such as family clinics and specialized hospitals, multiple doctors such as surgery and internal medicine, nurses, pharmacists, multiple staff such as hospital clerical staff, etc. As such, it is common for multiple parties to work together. There is a system called Electric Health Record (EHR) for efficiency in collaborating with multiple parties.

On the other hand, Patent Literature 1 discloses a medical system for selecting an appropriate doctor for a patient to receive treatment.

Japanese Patent No. 5914735

Before implementing the EHR, it is necessary to confirm whether the patient subject to the EHR has consented to the EHR. However, it was necessary to check paper documents to see if they agreed or not, and it was time-consuming and cumbersome for all EHR personnel who provide services to patients to check.

Accordingly, the present invention provides a service provision support device and a service provision support method that make it possible to quickly and easily confirm whether or not a service recipient agrees to the provision of a service. With the goal.

In order to achieve the above object, the service provision support device of the present invention includes:
including a storage unit, a related person data acquisition unit, a face image data acquisition unit, an authentication unit, and a data output unit,
The concerned party data acquisition unit acquires service recipient data and service provider data,
The service beneficiary data includes service beneficiary identification data and service beneficiary attribute data linked to the service beneficiary identification data,
The service receiver attribute data includes service receiver consent data and face image data of the service receiver linked to the consent data as consent registration face image data,
The service beneficiary attribute data includes service beneficiary terminal data,
The service provider data includes service provider identification data and service provider attribute data linked to the service provider identification data,
The service provider data is linked to the service recipient data according to the role of the service provider,
The service provider attribute data includes service provider terminal data,
The face image data acquisition unit acquires the face image data of the service recipient as matching face image data,
The authentication unit compares the matching face image data with the consent registration face image data, generates authentication data for authenticating a consent service recipient when they match, and stores the authentication data in the storage unit. register and
The data output unit is a device capable of outputting the authentication data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data. .

The service provision support method of the present invention includes:
including a stakeholder data acquisition process, a face image data acquisition process, an authentication process, and a data output process,
The related party data acquisition step acquires service recipient data and service provider data,
The service beneficiary data includes service beneficiary identification data and service beneficiary attribute data linked to the service beneficiary identification data,
The service receiver attribute data includes service receiver consent data and face image data of the service receiver linked to the consent data as consent registration face image data,
The service beneficiary attribute data includes service beneficiary terminal data,
The service provider data includes service provider identification data and service provider attribute data linked to the service provider identification data,
The service provider data is linked to the service recipient data according to the role of the service provider,
The service provider attribute data includes service provider terminal data,
The face image data acquisition step acquires the face image data of the service recipient as verification face image data,
The authentication step compares the matching face image data with the consent registration face image data, generates authentication data for authenticating a consent service beneficiary when they match, and registers the authentication data in a storage unit. death,
In the method, the data output step can output the authentication data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data. .

According to the present invention, for example, it is possible to quickly and easily confirm whether or not a service recipient has consented to the provision of a service.

FIG. 1 is a block diagram showing the configuration of an example of the apparatus of Embodiment 1. FIG. FIG. 2 is a diagram showing a data structure of a service provider in the device of Embodiment 1. FIG. FIG. 3 is an explanatory diagram for explaining the concept of EHR. FIG. 4 is a block diagram showing an example of the hardware configuration of the apparatus according to the first embodiment; FIG. 5 is a flow chart showing an example of processing in the device according to the first embodiment. FIG. 6 is a block diagram showing the configuration of an example of the device according to the second embodiment. FIG. 7 is a diagram showing an example of common list data in the device of the second embodiment. FIG. 8 is a flow chart showing an example of processing in the device according to the second embodiment.

In the apparatus of the present invention, the service receiver attribute data may further include vital information, and the vital information may be associated with the consent registration face image data. According to this aspect, vital information such as height, weight, body temperature, blood pressure, and pulse can be linked to the consent registration face image data. The consent registration face image data linked with the vital information may be acquired by using, for example, a sensor such as an IoT sensor as the concerned party data acquisition unit.

In the device of the present invention, the service recipient attribute data may further include a moving image, and the moving image may be associated with the consent registration face image data. According to this aspect, the consent registration face image data can be associated with a moving image of the service recipient's activity status, safety, and the like. The consent registration face image data associated with the moving image may be acquired by using, for example, a camera such as an IoT camera as the concerned party data acquisition unit.

The apparatus of the present invention further includes a common list data generation unit, and the common list data generation unit lists service providers linked to the service beneficiary data, and provides services common to each service beneficiary. and registers the common list data in the storage unit, and the data output unit outputs the common list data based on the service recipient terminal data and the service provider terminal data, It may be possible to output to at least one terminal of the service recipient terminal and the service provider terminal.

In the apparatus of the present invention, the service provider data may be linked to the service recipient data by attaching linking attribute information.

In the device of the present invention, the service provider data is data of two or more service providers, and the two or more service provider data are mutually linked by attaching linking information. , may be a mode.

In the device of the present invention, the service provider data includes facility data, team data, and staff data, and the facility data includes facility identification data and facility attribute data linked to the facility identification data. , the team data includes team identification data and team attribute data linked to the team identification data; and the staff data includes staff identification data and staff attribute data linked to the staff identification data. , at least two of the facility data, the team data, and the staff data may be mutually linked by attaching linking information.

A medical care service provision support device of the present invention includes the service provision support device of the present invention, wherein the service recipient is at least one of a patient and a care receiver, and the service provider is a medical worker and a care worker. at least one of

In the method of the present invention, the service recipient attribute data may further include vital information, and the vital information may be linked to the consent registration face image data.

In the method of the present invention, the service recipient attribute data may further include moving images, and the moving images may be linked to the consent registration face image data.

The method of the present invention further includes a common list data generating step, wherein the common list data generating step lists service providers linked to the service beneficiary data to provide services common to each service beneficiary. and registering the common list data in the storage unit, and the data output step outputs the common list data based on the service recipient terminal data and the service provider terminal data, It may be possible to output to at least one terminal of the service recipient terminal and the service provider terminal.

In the method of the present invention, the service provider data may be linked to the service recipient data by attaching linking attribute information.

In the method of the present invention, the service provider data is data of two or more service providers, and the two or more service provider data are mutually linked by attaching linking information. , may be a mode.

In the method of the present invention, the service provider data includes facility data, team data, and staff data, and the facility data includes facility identification data and facility attribute data linked to the facility identification data. , the team data includes team identification data and team attribute data linked to the team identification data; and the staff data includes staff identification data and staff attribute data linked to the staff identification data. , at least two of the facility data, the team data, and the staff data may be mutually linked by attaching linking information.

The method for supporting medical and nursing care service provision of the present invention includes the method for supporting service provision of the present invention, wherein the service recipient is at least one of a patient and a care recipient, and the service provider is a medical worker and a care worker. at least one of

The program of the present invention is a program capable of executing the method of the present invention on a computer.

A recording medium of the present invention is a computer-readable recording medium recording the program of the present invention.

The application target of the present invention is not particularly limited. For example, as described above, it is EHR for medical and nursing care, but it can also be applied to critical care. In critical care, for example, paramedics and hospitals capable of receiving emergency services are service providers, and unconscious patients are service recipients.

In the present invention, the acquired service recipient data and service provider data may be acquired from a database outside the device of the present invention, or may be stored in a database (storage unit) within the device of the present invention. It may be obtained from another source.

Next, an embodiment of the present invention will be described with reference to FIGS. 1 to 8. FIG. The present invention is not limited or restricted by the following embodiments. In addition, in FIGS. 1-8, the same code|symbol is attached|subjected to the same part. The descriptions in each embodiment can be used with each other.

[Embodiment 1]
FIG. 1 is a block diagram showing an example configuration of a service provision support device 1 of this embodiment. As shown in FIG. 1 , the service provision support device 1 includes a storage unit 11 , a related person data acquisition unit 12 , a face image data acquisition unit 13 , an authentication unit 14 and a data output unit 15 . Although not shown, the device 1 can be connected to a service recipient terminal and a service provider terminal via a communication network such as the Internet, and can also be connected to an external database. The device 1 may be incorporated in a server as a system, for example. Also, the device 1 may be, for example, a personal computer (PC) in which the program of the present invention is installed. The device 1 can also be connected to a terminal of a system administrator via a communication network, and the system manager may manage the device 1 from the terminal.

As shown in FIG. 1 , the concerned party data acquisition unit 12 acquires service recipient data 111 and service provider data 112 . The acquired service recipient data 111 and service provider data 112 are stored (stored) in the storage unit 11 . The service beneficiary data 111 includes service beneficiary identification data 1111 and service beneficiary attribute data 1112 linked to the service beneficiary identification data 1111 .

The service receiver identification data 1111 includes, for example, identification number data (ID data).

The service receiver attribute data 1112 includes service receiver consent data 1112a and face image data of the service receiver linked to the consent data 1112a as consent registration face image data 1112b. The service beneficiary attribute data 1112 also includes service beneficiary terminal data 1112c. Service receiver attribute data 1112 other than service receiver consent data 1112a, consent registration face image data 1112b, and service receiver terminal data 1112c includes, for example, name, date of birth, gender, address, vital information (height, weight, body temperature, , blood pressure, pulse, etc.), activity status, safety videos, etc., medical history, hospital information (family clinic, specialty clinic), guardian information (guardian name, relationship, contact information), etc. The vital information may be, for example, linked to the consent registration face image data 1112b and acquired by using a sensor such as an IoT sensor as the concerned person data acquisition unit 12. Further, the moving image may be linked to the consent registration face image data 1112b, for example, and may be acquired by using a camera such as an IoT camera as the concerned person data acquiring unit 12, for example.

The service provider data 112 includes service provider identification data 1121 and service provider attribute data 1122 linked to the service provider identification data 1121 . FIG. 2 shows interrelationships among facility data 1123, team data 1124, and staff data 1125 in service provider data 112. As shown in FIG. As shown in the figure, the facility data 1123 includes facility identification data 1123a and facility attribute data 1123b linked to the facility identification data 1123a. Similarly, team data 1124 includes team identification data 1124a and team attribute data 1124b linked to team identification data 1124a, and staff data 1125 includes staff identification data 1125a and data linked to staff identification data 1125a. and staff identification data 1125b attached to it. Facility data 1123, team data 1124, and staff data 1125 are linked to each other.

The service provider identification data 1121 includes, for example, identification number data (ID data).

Service provider attribute data 1122 includes service provider terminal data 1122a. The service provider attribute data 1122 other than the service provider terminal data 1122a varies, for example, depending on whether the service provider is a facility, team, or staff.

When the facility is a hospital, its attribute data includes, for example, the hospital name, address, representative telephone number, representative email address, type of clinical department to which it belongs, staff information to which it belongs (doctor, nurse, pharmacist, clerk etc.). When the service provider is a team, the attribute data includes, for example, the name of the team, the name of the organization to which it belongs, members, the role or purpose of the team, the expiration date of the team, and the like. When the service provider is a staff, the attribute data includes, for example, occupation (doctor, nurse, pharmacist, caregiver, nutritionist, care manager, office staff, etc.), name, department, contact information, and the like.

Moreover, specific linking information is attached to the linking between the service recipient and the service provider, and the linking between the service providers. Linking information includes, for example, information flow (one-way or two-way), a linking expiration date, and the like.

In this embodiment, the service receiver data 111 and the service provider data 112 are stored in the recording unit 11, but the present invention is not limited to this. The user data 112 may not be stored in the storage unit 11, and the authentication data 113 may be generated by directly using the service recipient data 111 and the service provider data 112 obtained from an external database.

Figure 3 shows an overview of the EHR. As shown in FIG. 3, a patient or care recipient who is a service recipient receives medical or nursing care services from a plurality of service providers. As shown in FIG. 3, service providers include primary physicians, specialists, family doctors, visiting doctors, family dentists, family pharmacists, visiting nursing staff, care staff, and care managers. In FIG. 3, the specialist is partnering with the primary care physician for telemedicine, and the visiting doctor is partnering with the primary care physician for home visits. The family pharmacist cooperates with the attending physician in home-visit dispensing, and the care staff also cooperates with the attending physician. Also, these service providers are mutually related (linked). Parents are in the position of service recipients who are patients or care recipients, as well as the position of service providers. Guardians are, for example, parents in the case of minors, and their children in the case of elderly people.

The communication line network is not particularly limited, and a known network can be used, and may be wired or wireless, for example. The communication network includes, for example, the Internet line, WWW (World Wide Web), telephone line, LAN (Local Area Network), WiFi (Wireless Fidelity), and the like.

Examples of the terminals include PCs, smart phones, tablets, mobile phones, and the like.

FIG. 4 illustrates a block diagram of the hardware configuration of the device 1. As shown in FIG. The device 1 has, for example, a CPU (Central Processing Unit) 101, a memory 102, a bus 103, a storage device 104, an input device 105, a display 106, a communication device 107, and the like. Each unit of the device 1 is connected to each other via a bus 103 .

The CPU 101 is responsible for overall control of the device 1 . In the device 1, the CPU 101 executes, for example, the program of the present invention and other programs, and reads and writes various information. Specifically, for example, the CPU 101 functions as a related person data acquisition unit 12 , a face image data acquisition unit 13 , an authentication unit 14 , and a data output unit 15 .

The face image data acquisition unit 13 acquires the face image data of the service recipient as the verification face image data 131 . The face image data acquisition unit 13 may acquire the matching face image data 131 by using a camera mounted on at least one of the service recipient terminal and the service provider terminal, for example.

Authentication unit 14 compares matching face image data 131 with consent registration face image data 1112b, and if they match, generates authentication data 113 for authenticating the consent service recipient. to register. A known face authentication technique can be used for matching the matching face image data 131 and the consent registration face image data 1112b. Examples of known face recognition technologies include the face recognition system "NeoFace (registered trademark)" manufactured by NEC Corporation, and the face recognition package software "NeoFace (registered trademark) KAOATO (registered trademark)" manufactured by NEC Solution Innovators. )” and the like.

The data output unit 15 can output the authentication data 113 to at least one of the service beneficiary terminal and the service provider terminal based on the service beneficiary terminal data 1112c and the service provider terminal data 1122a.

The bus 103 can also be connected to external devices, for example. Examples of the external device include an external storage device (external database, etc.), a printer, and the like. For example, the apparatus 1 can be connected to a communication network (not shown) by a communication device 107 connected to the bus 103, and can be connected to the external device via the communication network. You can also connect to your terminal.

The memory 102 includes, for example, a main memory, which is also referred to as main memory. When the CPU 101 performs processing, the memory 102 reads various operation programs such as the program of the present invention stored in a storage device 104 described later, and the CPU 101 receives data from the memory 102 and processes the programs. to run. The main memory is, for example, RAM (random access memory). Memory 102, for example, further includes a ROM (Read Only Memory).

The storage device 104 is also called a so-called auxiliary storage device, for example, in contrast to the main memory (main storage device). As described above, the storage device 104 stores operating programs including the program of the present invention. Storage device 104 includes storage unit 11 . As described above, the storage unit 11 stores (stores) the service recipient data 111 and the service provider data 112 . The service beneficiary data 111 includes service beneficiary identification data 1111 and service beneficiary attribute data 1112 linked to the service beneficiary identification data 1111 . The service provider data 112 includes service provider identification data 1121 and service provider attribute data 1122 linked to the service provider identification data 1121 . Storage device 104 includes, for example, a storage medium and a drive that reads from and writes to the storage medium. The storage medium is not particularly limited, and may be, for example, a built-in type or an external type. Examples include DVD, flash memory, memory card, etc., and the drive is not particularly limited. The storage device 104 may be, for example, a hard disk drive (HDD) in which a storage medium and drive are integrated.

The device 1 further has an input device 105 and a display 106, for example. The input device 105 is, for example, a touch panel, keyboard, mouse, or the like. Examples of the display 106 include an LED display and a liquid crystal display.

In the device 1, the memory 102 and the storage device 104 may store access information and log information from users (service recipients, service providers, etc.) and information acquired from an external database (not shown). It is possible.

Next, an example of processing in the apparatus 1 will be described with reference to the block diagram of FIG. 1 and the flow chart of FIG.

First, data is acquired by the concerned person data acquisition unit 12 (S1). Acquisition of data includes, for example, input using a keyboard, reading of data using a scanner or the like, input of file data, acquisition by accessing an external database, and the like. Further, as described above, as the concerned person data acquisition unit 12, data may be acquired using a sensor such as an IoT sensor or a camera such as an IoT camera. The data to be acquired is as described above.

Next, the face image data acquisition unit 13 acquires the face image data of the service recipient as the verification face image data 131 (S2).

Next, the authentication unit 14 compares the matching face image data 131 with the consent registered face image data 1112b, and if they match, generates authentication data 113 for authenticating the consent service recipient. Register in the storage unit 11 (S3).

Next, the data output unit 15 outputs the authentication data 113 to at least one of the service beneficiary terminal and the service provider terminal based on the service beneficiary terminal data 1112c and the service provider terminal data 1122a (S4). .

According to this embodiment, the matching face image data 131 is matched with the registered consent face image data 1112b, and if they match, the authentication data 113 for authenticating the consent service recipient is generated. By outputting to at least one terminal of the beneficiary terminal and the service provider terminal, for example, it is possible to quickly and easily check whether the service beneficiary agrees to the provision of the service. becomes.

[Embodiment 2]
FIG. 6 is a block diagram showing an example configuration of the service provision support device 1 of this embodiment. As shown in FIG. 6, the service provision support device 1 is the same as the service provision support device 1 of Embodiment 1, except that it further includes a common list data generator 16 and common list data 114 . Moreover, the hardware configuration of this device 1 is the same as that of the device 1 of the first embodiment shown in FIG.

The common list data generation unit 16 lists service providers linked to the service receiver data 111, generates common list data 114 of service providers common to each service receiver, and generates the common list data 114, Register in the storage unit 11 .

FIG. 7 shows an example of the common list data 114. As shown in FIG. As shown in the figure, each facility data (facility identification ID and facility name ), and staff (personal) data (personal identification ID) belonging to the facility are listed.

As in the first embodiment, the data output unit 15 can output the authentication data 113, and also outputs the common list data 114 to the service beneficiary based on the service beneficiary terminal data 1112c and the service provider terminal data 1122a. It can be output to at least one terminal of the terminal and the service provider terminal.

Next, an example of processing in the apparatus 1 will be described with reference to the block diagram of FIG. 6 and the flow chart of FIG.

First, as in the first embodiment, related person data acquisition (S1), face image data acquisition (S2), and authentication (S3) are performed.

Next, the common list data generating unit 16 lists service providers linked to the service receiver data 111 to generate common list data 114 of service providers common to each service receiver, and 114 is registered in the storage unit 11 (S5).

Next, the data output unit 15 outputs the authentication data 113 and the common list data 114 to at least one of the service beneficiary terminal and the service provider terminal based on the service beneficiary terminal data 1112c and the service provider terminal data 1122a. Output (S4).

[Embodiment 3]
A program of the present embodiment is a program capable of executing the service provision support method of the first embodiment or the second embodiment on a computer. Moreover, the program of this embodiment may be recorded on a computer-readable recording medium, for example. The recording medium is not particularly limited, and examples thereof include read-only memory (ROM), hard disk (HD), optical disk, floppy (registered trademark) disk (FD), and the like.

Although the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes can be made to the configuration and details of the present invention within the scope of the present invention that can be understood by those skilled in the art.

Some or all of the above embodiments may also be described in the following additional remarks, but are not limited to the following.
(Appendix 1)
including a storage unit, a related person data acquisition unit, a face image data acquisition unit, an authentication unit, and a data output unit,
The concerned party data acquisition unit acquires service recipient data and service provider data,
The service beneficiary data includes service beneficiary identification data and service beneficiary attribute data linked to the service beneficiary identification data,
The service receiver attribute data includes service receiver consent data and face image data of the service receiver linked to the consent data as consent registration face image data,
The service beneficiary attribute data includes service beneficiary terminal data,
The service provider data includes service provider identification data and service provider attribute data linked to the service provider identification data,
The service provider data is linked to the service recipient data according to the role of the service provider,
The service provider attribute data includes service provider terminal data,
The face image data acquisition unit acquires the face image data of the service recipient as matching face image data,
The authentication unit compares the matching face image data with the consent registration face image data, generates authentication data for authenticating a consent service recipient when they match, and stores the authentication data in the storage unit. register and
The data output unit is capable of outputting the authentication data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data.
Service provision support device.
(Appendix 2)
The service recipient attribute data further includes vital information,
The vital information is linked to the consent registration face image data,
The service provision support device according to appendix 1.
(Appendix 3)
The service recipient attribute data further includes moving images,
The video is linked to the consent registration face image data,
3. The service provision support device according to appendix 1 or 2.
(Appendix 4)
Furthermore, including a common list data generation unit,
The common list data generation unit lists service providers linked to the service receiver data, generates common list data of service providers common to each service receiver, and converts the common list data to the Register in memory,
The data output unit is capable of outputting the common list data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data.
4. The service provision support device according to any one of appendices 1 to 3.
(Appendix 5)
The service provider data is linked to the service beneficiary data with linking attribute information attached.
5. The service provision support device according to any one of appendices 1 to 4.
(Appendix 6)
The service provider data is data of two or more service providers,
The two or more service provider data are mutually linked by attaching linking information,
6. The service provision support device according to any one of appendices 1 to 5.
(Appendix 7)
the service provider data includes facility data, team data, and staff data;
The facility data includes facility identification data and facility attribute data linked to the facility identification data,
The team data includes team identification data and team attribute data linked to the team identification data,
The staff data includes staff identification data and staff attribute data linked to the staff identification data,
At least two of the facility data, the team data, and the staff data are mutually linked by attaching linking information.
7. The service provision support device according to any one of appendices 1 to 6.
(Appendix 8)
including the service provision support device according to any one of appendices 1 to 7,
The service recipient is at least one of a patient and a care recipient,
the service provider is at least one of a health care worker and a care worker;
Medical care service provision support device.
(Appendix 9)
including a stakeholder data acquisition process, a face image data acquisition process, an authentication process, and a data output process,
The related party data acquisition step acquires service recipient data and service provider data,
The service beneficiary data includes service beneficiary identification data and service beneficiary attribute data linked to the service beneficiary identification data,
The service receiver attribute data includes service receiver consent data and face image data of the service receiver linked to the consent data as consent registration face image data,
The service beneficiary attribute data includes service beneficiary terminal data,
The service provider data includes service provider identification data and service provider attribute data linked to the service provider identification data,
The service provider data is linked to the service recipient data according to the role of the service provider,
The service provider data includes service provider terminal data,
The face image data acquisition step acquires the face image data of the service recipient as verification face image data,
The authentication step compares the matching face image data with the consent registration face image data, generates authentication data for authenticating a consent service beneficiary when they match, and registers the authentication data in a storage unit. death,
The data output step is capable of outputting the authentication data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data.
How to support service delivery.
(Appendix 10)
The service recipient attribute data further includes vital information,
The vital information is linked to the consent registration face image data,
The service provision support method according to appendix 9.
(Appendix 11)
The service recipient attribute data further includes moving images,
The video is linked to the consent registration face image data,
The service provision support method according to appendix 9 or 10.
(Appendix 12)
Furthermore, including a common list data generation step,
The common list data generating step lists service providers linked to the service beneficiary data, generates common list data of service providers common to each service beneficiary, and converts the common list data to the Register in memory,
The data output step is capable of outputting the common list data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data.
The service provision support method according to any one of Appendices 9 to 11.
(Appendix 13)
The service provider data is linked to the service beneficiary data with linking attribute information attached.
13. The service provision support method according to any one of Appendices 9 to 12.
(Appendix 14)
The service provider data is data of two or more service providers,
The two or more service provider data are mutually linked by attaching linking information,
14. The service provision support method according to any one of Appendices 9 to 13.
(Appendix 15)
the service provider data includes facility data, team data, and staff data;
The facility data includes facility identification data and facility attribute data linked to the facility identification data,
The team data includes team identification data and team attribute data linked to the team identification data,
The staff data includes staff identification data and staff attribute data linked to the staff identification data,
15. The service provision support method according to any one of Appendices 9 to 14, wherein at least two of the facility data, the team data, and the staff data are mutually linked by attaching linking information.
(Appendix 16)
including the service provision support method according to any one of appendices 9 to 15,
The service recipient is at least one of a patient and a care recipient,
the service provider is at least one of a health care worker and a care worker;
Medical care service provision support method.
(Appendix 17)
A program capable of executing the method according to any one of appendices 9 to 16 on a computer.
(Appendix 18)
A computer-readable recording medium recording the program according to appendix 17.

According to the present invention, for example, it is possible to quickly and easily confirm whether or not a service recipient has consented to the provision of a service. can be made more efficient.

1 Service provision support device 11 Storage unit 12 Participant data acquisition unit 13 Face image data acquisition unit 14 Authentication unit 15 Data output unit 16 Common list data generation unit 101 CPU (central processing unit)
102 memory 103 bus 104 storage device 105 input device 106 display 107 communication device 111 service recipient data 112 service provider data 113 authentication data 114 common list data 131 matching face image data 1111 service recipient identification data 1112 service recipient attribute data 1112a Service enjoyment consent data 1112b Consent registration face image data 1112c Service recipient terminal data 1121 Service provider identification data 1122 Service provider attribute data 1122a Service provider terminal data 1123 Facility data 1123a Facility identification data 1123b Facility attribute data 1124 Team data 1124a Team Identification data 1124b Team attribute data 1125 Staff data 1125a Staff identification data 1125b Staff attribute data

Claims (16)

including a storage unit, a related person data acquisition unit, a face image data acquisition unit, an authentication unit, and a data output unit,
The concerned party data acquisition unit acquires service recipient data and service provider data,
The service beneficiary data includes service beneficiary identification data and service beneficiary attribute data linked to the service beneficiary identification data,
The service receiver attribute data includes service receiver consent data and face image data of the service receiver linked to the consent data as consent registration face image data,
The service beneficiary attribute data includes service beneficiary terminal data,
The service provider data includes service provider identification data and service provider attribute data linked to the service provider identification data,
The service provider data is linked to the service recipient data according to the role of the service provider,
The service provider attribute data includes service provider terminal data,
The face image data acquisition unit acquires the face image data of the service recipient as matching face image data,
The authentication unit compares the matching face image data with the consent registration face image data, generates authentication data for authenticating a consent service recipient when they match, and stores the authentication data in the storage unit. register and
The data output unit is capable of outputting the authentication data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data.
Service provision support device. The service recipient attribute data further includes vital information,
The vital information is linked to the consent registration face image data,
The service provision support device according to claim 1. The service recipient attribute data further includes moving images,
The video is linked to the consent registration face image data,
3. The service provision support device according to claim 1 or 2. Furthermore, including a common list data generation unit,
The common list data generation unit lists service providers linked to the service receiver data, generates common list data of service providers common to each service receiver, and converts the common list data to the Register in memory,
The data output unit is capable of outputting the common list data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data.
The service provision support device according to any one of claims 1 to 3. The service provider data is linked to the service beneficiary data with linking attribute information attached.
The service provision support device according to any one of claims 1 to 4. The service provider data is data of two or more service providers,
The two or more service provider data are mutually linked by attaching linking information,
The service provision support device according to any one of claims 1 to 5. the service provider data includes facility data, team data, and staff data;
The facility data includes facility identification data and facility attribute data linked to the facility identification data,
The team data includes team identification data and team attribute data linked to the team identification data,
The staff data includes staff identification data and staff attribute data linked to the staff identification data,
At least two of the facility data, the team data, and the staff data are mutually linked by attaching linking information.
The service provision support device according to any one of claims 1 to 6. Including the service provision support device according to any one of claims 1 to 7,
The service recipient is at least one of a patient and a care recipient,
the service provider is at least one of a health care worker and a care worker;
Medical care service provision support device. including a stakeholder data acquisition process, a face image data acquisition process, an authentication process, and a data output process,
The related party data acquisition step acquires service recipient data and service provider data,
The service beneficiary data includes service beneficiary identification data and service beneficiary attribute data linked to the service beneficiary identification data,
The service receiver attribute data includes service receiver consent data and face image data of the service receiver linked to the consent data as consent registration face image data,
The service beneficiary attribute data includes service beneficiary terminal data,
The service provider data includes service provider identification data and service provider attribute data linked to the service provider identification data,
The service provider data is linked to the service recipient data according to the role of the service provider,
The service provider data includes service provider terminal data,
The face image data acquisition step acquires the face image data of the service recipient as verification face image data,
The authentication step compares the matching face image data with the consent registration face image data, generates authentication data for authenticating a consent service beneficiary when they match, and registers the authentication data in a storage unit. death,
The data output step is capable of outputting the authentication data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data ,
each of the steps is executed by a computer,
How to support service delivery. The service recipient attribute data further includes vital information,
The vital information is linked to the consent registration face image data,
The service provision support method according to claim 9. The service recipient attribute data further includes moving images,
The video is linked to the consent registration face image data,
The service provision support method according to claim 9 or 10. Furthermore, including a common list data generation step,
The common list data generating step lists service providers linked to the service beneficiary data, generates common list data of service providers common to each service beneficiary, and converts the common list data to the Register in memory,
The data output step is capable of outputting the common list data to at least one of a service beneficiary terminal and a service provider terminal based on the service beneficiary terminal data and the service provider terminal data.
The service provision support method according to any one of claims 9 to 11. The service provider data is linked to the service beneficiary data with linking attribute information attached.
The service provision support method according to any one of claims 9 to 12. The service provider data is data of two or more service providers,
The two or more service provider data are mutually linked by attaching linking information,
The service provision support method according to any one of claims 9 to 13. the service provider data includes facility data, team data, and staff data;
The facility data includes facility identification data and facility attribute data linked to the facility identification data,
The team data includes team identification data and team attribute data linked to the team identification data,
The staff data includes staff identification data and staff attribute data linked to the staff identification data,
15. The service provision support method according to any one of claims 9 to 14, wherein at least two of said facility data, said team data, and said staff data are mutually linked by attaching linking information. Including the service provision support method according to any one of claims 9 to 15,
The service recipient is at least one of a patient and a care recipient,
the service provider is at least one of a health care worker and a care worker;
Medical care service provision support method.

Images