JP2023053936A - server and program - Google Patents

Abstract

To provide a server and a program that reduce working time which is required to settle residence of a required residential patient into a facility.SOLUTION: An information processing system comprises: a first client device 10 used by a care user who cares for a patient; a second client device 20 used by a facility user of a facility receiving residence of the patient; and a server 30. The server acquires patient identification information identifying the patient and patient information associated with the patient from the first client device according to an instruction of the care user, acquires an offer for receiving a specified patient who is specified by the facility user in the facility from the second client device, associates among offer patient identification information associated with the specified patient, facility identification information, and care institution identification information identifying a care institution, and presents first message information depending on an instruction of the facility user corresponding to the offer and second message information depending on an instruction of a care user to the first client device and the second client device.SELECTED DRAWING: Figure 3

Description

Patent Law Article 30, Paragraph 2 application filed April 5, 2021 Sales materials created by MedPeer, Inc. August 12, 2021 https://medpeer. co. jp/press/9461. html May 7, 2021 Sales materials created by Credit Saison Co., Ltd. August 12, 2021 https://corporate. saison card. co. jp/wr_html/news_data/avmqks000000bm8h-att/20210812_Release. pdf August 27, 2021 Elderly Housing Newspaper Seminar

The present invention relates to servers and programs.

Patients hospitalized in medical institutions include patients who need to move into facilities (for example, nursing homes) that can provide medical care even after discharge (hereinafter referred to as “hospitalized patients”).
In order to move a patient requiring admission to a facility, it is necessary for the staff of the medical institution to make adjustments between the patient requiring admission and the facility (hereinafter referred to as "discharge adjustment").

For example, Patent Literature 1 discloses a discharge adjustment support system that supports discharge adjustment. According to the hospital discharge adjustment system, the facility is easily provided with the information of the patient requiring admission.

Japanese Patent Application Laid-Open No. 2006-318174

With the aging society, the number of patients requiring admission tends to increase, and facilities that can accept such patients tend to run short.
In addition to medical institutions, cases where care managers make arrangements for facilities for patients requiring admission are also on the rise.
Therefore, coordinating acceptance takes a lot of time.

In the technique of Patent Document 1, the work time of the staff of the medical institution required for providing the information of the patient requiring admission to the facility is shortened, but the staff of the medical institution required until the admission of the patient requiring admission to the facility is confirmed. work time is not shortened. In particular, it takes time to exchange information between the staff of the medical institution and the staff of the facility. However, if the facility is in a situation where it is not possible to accept patients requiring occupancy (for example, if the rooms in the facility are fully occupied, or if the system or equipment that can provide the medical care desired by the patient requiring occupancy is not available at the facility) ), the offer may be rejected.

The purpose of the present invention is to reduce the work time required to confirm the admission of a patient who needs admission to a facility, by establishing a care institution that takes care of the patient before entering the institution and a facility that accepts the patient. It is to provide an environment that facilitates information exchange.

One aspect of the present invention is
A server connectable to a first client device used by a care user who cares for a patient and a second client device used by a facility user of a facility that accepts the patient,
means for obtaining patient identification information identifying the patient and patient information about the patient from the first client device in response to instructions from the care user;
means for storing the patient identification information and the patient information in association with each other;
comprising means for presenting the patient information to the second client device in response to an instruction from the facility user;
Means for obtaining an offer for accepting a specified patient specified by the facility user from the second client device in the facility in response to an instruction from the facility user;
The offer includes facility identification information that identifies the facility and patient information of the designated patient,
means for associating and storing offer patient identification information associated with the designated patient, facility identification information, and care institution identification information identifying a care institution;
means for updating status information associated with the offer patient identification information to indicate that the offer has been obtained;
After obtaining the offer, the first client device and the second client device are provided with first message information according to instructions from the facility user corresponding to the offer and second messages according to instructions from the care user. comprising means for presenting information;
is the server.

1 is a block diagram showing the configuration of an information processing system according to an embodiment; FIG. 2 is a functional block diagram of the information processing system of FIG. 1; FIG. BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an explanatory diagram of the outline of this embodiment; It is a figure which shows the data structure of the care institution information database of this embodiment. It is a figure which shows the data structure of the facility information database of this embodiment. It is a figure which shows the data structure of the patient information database of this embodiment. It is a figure which shows the data structure of the offer information database of this embodiment. FIG. 4 is a sequence diagram of patient information registration processing according to the present embodiment. 9 is a diagram showing an example of a screen displayed in the information processing of FIG. 8; FIG. FIG. 10 is a sequence diagram of offer processing according to the present embodiment; 11 is a diagram showing an example of a screen displayed in the information processing of FIG. 10; FIG. FIG. 10 is a sequence diagram of offer sharing processing according to the present embodiment; 13 is a diagram showing an example of a screen displayed in the information processing of FIG. 12; FIG. It is a sequence diagram of moving-in determination processing of this embodiment. 15 is a diagram showing an example of a screen displayed in the information processing of FIG. 14; FIG. FIG. 12 is a sequence diagram of registration processing of patient information according to modification 2; 17 is a diagram showing an example of a screen displayed in the information processing of FIG. 16; FIG. FIG. 21 is a sequence diagram of a follow candidate presentation process according to Modification 3; 19 is a diagram showing an example of a screen displayed in the information processing of FIG. 18; FIG.

An embodiment of the present invention will be described in detail below with reference to the drawings. In the drawings for describing the embodiments, in principle, the same constituent elements are denoted by the same reference numerals, and repeated description thereof will be omitted.

(1) Configuration of information processing system The configuration of the information processing system will be described. FIG. 1 is a block diagram showing the configuration of the information processing system of this embodiment. FIG. 2 is a functional block diagram of the information processing system of FIG.

As shown in FIG. 1, the information processing system 1 includes a first client device 10, a second client device 20, a server 30, and a third client device 40. FIG.
The first client device 10, the second client device 20, the server 30, and the third client device 40 are connected via a network (for example, the Internet or an intranet) NW.

The first client device 10 , the second client device 20 , and the third client device 40 are computers (an example of an “information processing device”) that transmit requests to the server 30 . The first client device 10, the second client device 20, and the third client device 40 are, for example, smart phones, tablet terminals, or personal computers.

The server 30 sends responses to the requests transmitted from the first client device 10, the second client device 20, and the third client device 40 to the first client device 10, the second client device 20, and the third client device 40. It is a computer (an example of an “information processing device”) provided to the device 40 . Server 30 is, for example, a web server.

(1-1) Configuration of First Client Device The configuration of the first client device 10 will be described.

As shown in FIG. 2, the first client device 10 includes a storage device 11, a processor 12, an input/output interface 13, and a communication interface .

Storage device 11 is configured to store programs and data. The storage device 11 is, for example, a combination of ROM (Read Only Memory), RAM (Random Access Memory), and storage (eg, flash memory or hard disk).

Programs include, for example, the following programs.
・OS (Operating System) program ・Application (for example, web browser) program that executes information processing

The data includes, for example, the following data.
・Databases referenced in information processing ・Data obtained by executing information processing (that is, execution results of information processing)

The processor 12 is configured to implement the functions of the first client device 10 by running programs stored in the storage device 11 . The processor 12 is, for example, a CPU (Central Processing Unit), an ASIC (Application Specific Integrated Circuit), an FPGA (Field Programmable Gate Array), or a combination thereof.

The input/output interface 13 is configured to acquire user instructions from an input device connected to the first client device 10 and to output information to an output device connected to the first client device 10 .
Input devices are, for example, keyboards, pointing devices, touch panels, or combinations thereof.
An output device is, for example, a display.

Communication interface 14 is configured to control communication between first client device 10 and server 30 .

(1-2) Configuration of Second Client Device The configuration of the second client device 20 will be described.

As shown in FIG. 2, the second client device 20 comprises a storage device 21, a processor 22, an input/output interface 23, and a communication interface 24. FIG.

Storage device 21 is configured to store programs and data. Storage device 21 is, for example, a combination of ROM, RAM, and storage (eg, flash memory or hard disk).

Programs include, for example, the following programs.
- OS program - Application (for example, web browser) program that executes information processing

The data includes, for example, the following data.
・Databases referenced in information processing ・Data obtained by executing information processing (that is, execution results of information processing)

The processor 22 is configured to implement the functions of the second client device 20 by running programs stored in the storage device 21 . Processor 22 is, for example, a CPU, ASIC, FPGA, or a combination thereof.

The input/output interface 23 is configured to acquire user instructions from an input device connected to the second client device 20 and to output information to an output device connected to the second client device 20 .
Input devices are, for example, keyboards, pointing devices, touch panels, or combinations thereof.
An output device is, for example, a display.

Communication interface 24 is configured to control communication between second client device 20 and server 30 .

(1-3) Configuration of Third Client Device The configuration of the third client device 40 will be described.

As shown in FIG. 2, the third client device 40 comprises a storage device 41, a processor 42, an input/output interface 43, and a communication interface 44. FIG.

Storage device 41 is configured to store programs and data. Storage device 41 is, for example, a combination of ROM, RAM, and storage (eg, flash memory or hard disk).

Programs include, for example, the following programs.
- OS program - Application (for example, web browser) program that executes information processing

The data includes, for example, the following data.
・Databases referenced in information processing ・Data obtained by executing information processing (that is, execution results of information processing)

The processor 42 is configured to implement the functions of the third client device 40 by running programs stored in the storage device 41 . Processor 42 is, for example, a CPU, ASIC, FPGA, or a combination thereof.

The input/output interface 43 is configured to acquire user instructions from an input device connected to the third client device 40 and output information to an output device connected to the third client device 40 .
Input devices are, for example, keyboards, pointing devices, touch panels, or combinations thereof.
An output device is, for example, a display.

Communication interface 44 is configured to control communication between third client device 40 and server 30 .

(1-4) Server Configuration The configuration of the server 30 will be described.

As shown in FIG. 2, the server 30 includes a storage device 31, a processor 32, an input/output interface 33, and a communication interface .

Storage device 31 is configured to store programs and data. Storage device 31 is, for example, a combination of ROM, RAM, and storage (eg, flash memory or hard disk).

Programs include, for example, the following programs.
- OS program - Application program that executes information processing

The data includes, for example, the following data.
・Databases referenced in information processing ・Execution results of information processing

The processor 32 is configured to implement the functions of the server 30 by activating programs stored in the storage device 31 . Processor 32 is, for example, a CPU, ASIC, FPGA, or a combination thereof.

The input/output interface 33 is configured to acquire user instructions from input devices connected to the server 30 and to output information to output devices connected to the server 30 .
Input devices are, for example, keyboards, pointing devices, touch panels, or combinations thereof.
An output device is, for example, a display.

Communication interface 34 is configured to control communication between server 30 and first client device 10 , second client device 20 , and third client device 40 .

(2) Outline of Embodiment An outline of this embodiment will be described. FIG. 3 is an explanatory diagram of the outline of this embodiment.

As shown in FIG. 3 , a user of a care institution (hereinafter referred to as “care user”) who takes care of patients before moving into the facility uses the first client device 10 . A care institution has a role of adjusting a medical treatment destination for a patient requiring medical treatment according to a patient's factors (for example, a change in condition or environment). Care institutions include, for example, medical institutions, long-term care health facilities, and in-home care support offices. Care users include, for example:
・Medical institution staff (eg, doctors, pharmacists, nurses, and medical office staff)
・Staff at long-term care facilities ・Care managers

A facility user of a facility that accepts patients after the care user completes care uses the second client device 20 .

A patient-user (patient or patient's associate) uses the third client device 40 .

The care user uses the first client device 10 to register patient information in the server 30 .

By accessing the server 30 using the second client device 20, the facility user browses the patient information and presents an offer of residence to the patient who can accept the residence after discharge.

By accessing the server 30 using the first client device 10, the care user confirms the offer to move in to the patient and designates the facility where the patient wishes to move in (hereinafter referred to as the "requested facility"). do.

(3) Database The database of this embodiment will be described. The following databases are stored in the storage device 31.

(3-1) Care Institution Information Database The care institution information database of this embodiment will be described. FIG. 4 is a diagram showing the data structure of the care institution information database of this embodiment.

The care institution information database of FIG. 4 stores care institution information. Care institution information is information about a care institution.
The care agency information database includes a "care agency ID" field, a "care agency name" field, and a "care agency contact" field. Each field is associated with one another.

The “care institution ID” field stores care institution identification information. Care institution identification information is information for identifying a care institution. If the care institution is a medical institution, the care institution identification information is information that identifies the medical institution. When the care institution is a nursing care insurance facility for the elderly, the care institution identification information is information identifying the nursing care insurance facility for the elderly. If the care institution is an in-home care support office, the care institution identification information is information that identifies the care manager.

The "care institution name" field stores care institution name information. The care institution name information is information relating to the name of the care institution.

The "care institution contact" field stores care institution contact information. The care institution contact information is information (eg, at least one of a phone number and an e-mail address) regarding the contact information of the care institution.

(3-2) Facility Information Database The facility information database of this embodiment will be described. FIG. 5 is a diagram showing the data structure of the facility information database of this embodiment.

Facility information is stored in the facility information database of FIG. The facility information is information about facilities.
The facility information database includes a "facility ID" field, a "facility name" field, a "facility attribute" field, and a "facility contact" field. Each field is associated with one another.

The “facility ID” field stores facility identification information. The facility identification information is information that identifies the facility.

The "facility name" field stores facility name information. The facility name information is information regarding the name of the facility.

The "facility attribute" field stores facility attribute information. The facility attribute information includes a "type" field, an "area" field, a "usage amount" field, and a "public assistance" field.

The “type” field stores facility type information. The facility type information is information about the type of facility. The facility type is, for example, at least one of the following.
・Nursing care business operators (for example, nursing homes with nursing care, or nursing care facilities such as housing for the elderly with services)
・Welfare facilities ・Home care support clinics ・Convalescent/chronic hospitals (for example, convalescent hospitals)
・Visiting Nursing Station

Facility area information is stored in the "area" field. The facility area information is information regarding the location of the facility.

Charge information is stored in the "charge" field. The fee information is information on fees for each facility. The fee information includes, for example, at least one of the following.
・Monthly usage fee ・Lump-sum move-in fee

Information on acceptance or non-acceptance of public assistance recipients is possible in the "public assistance" field.

The facility contact information is stored in the "facility contact" field. The facility contact information is information (for example, at least one of a telephone number and an e-mail address) regarding the contact information of the facility.

(3-3) Patient Information Database The patient information database of this embodiment will be described. FIG. 6 is a diagram showing the data structure of the patient information database of this embodiment.

Patient information is stored in the patient information database of FIG. Patient information is information about a patient.
The patient information database includes a 'patient ID' field and a 'occupancy judgment' field. Each field is associated with one another.
A patient information database is associated with the care organization identification information.

The “patient ID” field stores patient identification information. The patient identification information is information that identifies the patient and is information that does not correspond to the patient's personal information (for example, the patient's name). Patient identification information is, for example, any of the following.
・Patient's ID card number ・Patient's chart number ・Initials of patient's name

In the "occupancy judgment" field, information on determination of occupancy is stored. The occupancy determination information is information that the facility refers to when determining whether or not to accept the patient's occupancy. The move-in availability determination information includes, for example, the following information.
・Gender ・Age ・Presence or absence of long-term care insurance ・Level of care of the patient ・Postal code of the patient's home ・Presence or absence of a guarantor )
・Scheduled date of discharge ・Type of facility desired ・Medical classification ・Preferred area of facility ・Conditions for lump-sum payment required for moving in ・Conditions for monthly fee required for moving in ・Presence or absence of public assistance ・Details of necessary medical care during residence・Disease ・Level of independence in daily life (for example, if the disease is dementia, registration of the level of independence in daily life is required)
- Presence or absence of a care manager - Message to facility considering offer - Name of responsible care agency staff - Information about key persons (e.g., family, relatives, or guardians)

(3-4) Offer Information Database The offer information database of this embodiment will be described. FIG. 7 is a diagram showing the data structure of the offer information database of this embodiment.

Offer information is stored in the offer information database of FIG. Offer information is information about patient and facility offers.
The offer information database includes an "offer ID" field, a "patient ID" field, a "facility ID" field, a "status" field, an "offer content" field, a "message" field, and a "coordinator ID ” fields. Each field is associated with one another.
The offer information database is associated with the care organization identification information.

The "offer ID" field stores offer identification information. Offer identification information is information that identifies an offer.

The "patient ID" field stores patient identification information (hereinafter referred to as "offered patient identification information") of a patient (hereinafter referred to as "designated patient") to whom the facility has offered an offer of acceptance.

The "facility ID" field stores facility identification information of a facility that has presented an offer to accept a residence (hereinafter referred to as "offer facility").

The "status" field stores status information. The status information is information about the status of the offer of the offer facility. The status information includes facility status information and care agency status information. The facility status information is information regarding the status of the facility. Care agency status information is information about the status for a care agency.

The facility status information is, for example, any of the following.
• "Offered": means that the facility has sent an offer to the patient and is awaiting a reply from the care institution.
• "Adjusting admission": means that there is a reply from the care institution to the facility's offer and that the patient's admission is being adjusted.
- "Adjustment completed": It means that the patient has decided to move into another facility, or that the patient has refused to move into the facility.
- "Decision to move in": It means that the patient has decided to move into the facility.
- "Offer withdrawn": means that the facility has withdrawn the offer.

Care institution status information is, for example, any of the following.
• "Editing": Means that the patient information is private (ie not open to the facility).
- "Offer accepted": means that the patient information is open to the facility (that is, the patient is waiting for an offer).
• "Acceptance pending": Means that at least one offer has been received from the facility (ie, patient admission is being coordinated).
- "Decision to move in": It means that the patient has decided to move into the facility.
・“Adjustment end”: Same as “Adjustment end” in the facility status information.

The "offer content" field stores offer content information. The offer content information is information (information arbitrarily input by the facility user) regarding the content of the offer from the facility to the patient.

The "message" field stores message information. Chat message information is information relating to messages exchanged between at least two parties, a care agency, a facility, and a patient.

The “person in charge of adjustment ID” field stores the identification information of the person in charge of adjustment. The coordinator identification information is information that identifies the coordinator.

(4) Information processing Information processing according to this embodiment will be described.

(4-1) Patient Information Registration Processing The patient information registration processing of this embodiment will be described. FIG. 8 is a sequence diagram of patient information registration processing according to the present embodiment. 9 is a diagram showing an example of a screen displayed in the information processing of FIG. 8. FIG.

The processing in FIG. 8 is triggered by a care user's instruction (for example, input of care institution identification information) given to the first client device 10 .

As shown in FIG. 8, the first client device 10 receives patient information (S1110).
Specifically, processor 12 displays screen P1110 (FIG. 9) on the display.

A screen P1110 includes an operation object B1110 and a field object F1110.

The field object F1110 is an object that receives user instructions for entering patient information to be registered in the server 30 . Patient information includes, for example, the following information.
・Patient identification information (for example, the patient's patient registration number or chart number)
・Occupancy judgment information

The operation object B1110 is an object that receives a user instruction for finalizing the input to the field object F1110.

When the care user inputs patient information into the field object F1110 and operates the operation object B1110, the processor 12 displays a screen P1111 (FIG. 9) on the display.

The screen P1111 includes a display object A1111 and operation objects B1111a to B1111b.

The display object A1111 displays a message for confirming whether or not the patient's consent has been obtained for registration of the patient information.

The operation object B1111a is an object to be operated when the patient consents to registration of patient information.
The operation object B1111b is an object to be operated when the patient's consent has not been obtained for registration of patient information.

After step S1110, the first client device 10 executes a patient registration request (S1111).
Specifically, when the care user operates the operation object B1111a, the processor 12 transmits patient registration request data to the server 30 .
The patient registration request data includes the following information.
・Care institution identification information ・Patient identification information (for example, the patient's patient registration card number or chart number)
・Occupancy judgment information

After step S1111, the server 30 performs patient registration (S1130).

Specifically, processor 32 adds a new record to the patient information database (FIG. 6) associated with the care organization identification included in the patient registration request data. Each field in the new record contains the following information:
・“Patient ID” field: Patient identification information included in patient registration request data ・“Admission acceptance judgment” field: Admission acceptance judgment information included in patient registration request data

Processor 32 adds a new record to the offer information database (FIG. 7) associated with the care agency identification included in the patient registration request data. Each field in the new record contains the following information:
・“Patient ID” field: patient identification information included in patient registration request data ・“Facility ID” field: blank ・“Status” field: accepting offer ・“Offer details” field: blank

(4-2) Offer Processing The offer processing of this embodiment will be described. FIG. 10 is a sequence diagram of offer processing according to this embodiment. 11 is a diagram showing an example of a screen displayed in the information processing of FIG. 10. FIG.

The processing in FIG. 10 is triggered by an instruction (for example, input of facility identification information) given to the second client device 20 by the facility user.

As shown in FIG. 10, the second client device 20 executes a browsing request (S1220).
Specifically, processor 22 transmits viewing request data to server 30 . The viewing request data includes the following information.
・Facility identification information entered by the facility user

After step S1220, the server 30 creates a patient list (S1230).
Specifically, the processor 32 creates a list of patient information (a combination of patient identification information and occupancy determination information) by referring to the patient information database (FIG. 6).

After step S1230, the server 30 executes a browsing response (S1231).
Specifically, the processor 32 transmits the browsing response data to the second client device 20 . The browsing response data includes, for example, a list of patient information (a combination of patient identification information and move-in availability determination information) created in step S1230.

After step S1231, the second client device 20 presents patient information (S1221).
Specifically, processor 22 displays screen P1220 (FIG. 11) on the display.

On the screen P1220, at least part of the move-in availability determination information included in the browsing response data and operation objects B1220a and B1220b are displayed.
Patient identification information is assigned to each of the operation objects B1220a and B1220b. The patient identification information is not displayed on screen P1220 (that is, it is made anonymous to the facility user). Each of the operation objects B1220a-B1220b is an object that accepts user instructions for viewing details of patient information associated with assigned patient identification information.

For example, when the facility user operates the operation object B1220b, the processor 22 displays the screen P1221 (FIG. 11) on the display.

The screen P1221 includes a display object A1221, an operation object B1221, and a field object F1221.

The display object A1221 displays details of patient information associated with the patient identification information assigned to the operation object B1220b operated by the facility user.

The field object F1221 is a user input of the name of the person in charge of the facility, the name of the facility, the contact information (e.g., email address and telephone number), and the contents of the offer for the patient to whom the offer is presented (hereinafter referred to as "offer patient"). An object that accepts instructions.

The operation object B1221 is an object that receives a user instruction for confirming the input to the field object F1221.

After step S1221, the second client device 20 executes the offer request (S1222).
Specifically, when the facility user inputs a user instruction to the field object F1221 and operates the operation object B1221, the processor 22 transmits offer request data to the server 30. FIG. The offer request data includes, for example, the following information: Facility identification information Patient identification information of the offered patient (hereinafter referred to as "offered patient identification information")

After step S1222, the server 30 updates the database (S1232).
Specifically, processor 32 adds a new record to the offer information database (FIG. 7). Each field in the new record contains the following information:
・“Patient ID” field: offer patient identification information included in offer request data ・“Facility ID” field: facility identification information included in offer request data ・“Status” field: status information “offered”
・"Offer content" field: Offer content information

(4-3) Offer Sharing Processing The offer sharing processing of this embodiment will be described. FIG. 12 is a sequence diagram of offer sharing processing according to this embodiment. 13 is a diagram showing an example of a screen displayed in the information processing of FIG. 12. FIG.

The process of FIG. 12 is triggered by a care user's instruction given to the first client device 10 (for example, input of care institution identification information and patient identification information).

As shown in FIG. 12, the first client device 10 executes an offer list request (S1310).
Specifically, processor 12 transmits offer list request data to server 30 when a care user provides a user instruction to have an offer list presented. The offer list request data includes, for example, the following information.
- Care institution identification information entered by the care user - Patient identification information entered by the care user - Coordinator identification information entered by the care user

The server 30 creates an offer list (S1330).
Specifically, the processor 32 stores the coordinator ID included in the offer list request data in the "Coordinator ID" field of the offer information database (FIG. 7) associated with the care institution identification information included in the offer list request data. Stores user identification information.
Processor 32 references the offer information database to identify offer information associated with the patient identification information included in the offer list request data.

After step S1330, the server 30 executes an offer list response (S1331).
Specifically, the processor 32 transmits offer list response data to the first client device 10 . The offer response data includes the offer information identified in step S1235.

After step S1331, the first client device 10 presents the offer list (S1311).
Specifically, processor 12 displays screen P1310 (FIG. 13) on the display.

An offer list is displayed on screen P1310. The offer list includes, for example, offer information included in the offer response data.

After step S1311, the first client device 10 executes the sharing request (S1312).
Specifically, when the care user designates arbitrary facility identification information on screen P1310, processor 12 displays screen P1311 (FIG. 13) on the display.

The screen P1311 includes a display object A1311, operation objects B1311a to B1311c, and a field object F1311.

The display object A1311 displays facility information and offer content information associated with the facility identification information specified on the screen P1310.

A field object F1311 displays messages exchanged between the care user and the facility user. A field object F1311 is an object that receives input of a message.

The operation object B1311a is an object that receives a user instruction for deciding whether to move into the facility corresponding to the facility identification information specified on the screen P1310.

The operation object B1311b is an object that receives a user's instruction to deny admission to the facility corresponding to the facility identification information specified on the screen P1310.

The operation object B1311c is an object that receives user instructions for sharing with patients an offer from the facility corresponding to the facility identification information specified on the screen P1310.

When the care user operates the operation object B1311c, the processor 12 displays the screen P1312 (FIG. 13) on the display.

The screen P1312 includes field objects F1312a to F1312b and an operation object B1312.

The field object F1312a specifies the destination information of the offer (e.g., the patient's or patient's related person's email address, web service (for example, message exchange service or SNS (Social Network Service)) account, or phone number) It is an object that accepts user instructions for

The field object F1312b is an object that receives a user instruction for designating a message addressed to the patient.

The operation object B1312 is an object that receives a user instruction to share an offer to the destination indicated by the destination information specified by the user instruction input to the field object F1312a.

When the care user inputs user instructions to field objects F1312a-F1312b and operates operation object B1312, processor 12 transmits shared request data to server 30. FIG. The shared request data includes, for example, the following information.
・Patient identification information entered by the care user ・Facility identification information specified by the care user ・Addressee information specified by the care user ・Offer information from the facility corresponding to the facility identification information (facility information, offer content information, and patient message)

After step S1312, the server 30 updates the database (S1332).
Specifically, the processor 32 refers to the offer information database (FIG. 7) and stores the following information in records associated with the patient identification information and facility identification information included in the shared request data.
・"Status" field: "Adjusting acceptance"
・"Message" field: message for the patient included in the sharing request data

After step S1332, the server 30 performs offer sharing (S1333).
Specifically, the processor 32 transmits the offer information included in the shared request data to the destination indicated by the destination information included in the shared request data (for example, the third client device 40).

(4-4) Occupancy Decision Processing The occupancy decision processing of this embodiment will be described. FIG. 14 is a sequence diagram of move-in decision processing according to the present embodiment. FIG. 15 is a diagram showing an example of a screen displayed in the information processing of FIG. 14. FIG.

The process of FIG. 14 is triggered by a care user's instruction given to the first client device 10 (for example, input of care institution identification information).

As shown in FIG. 14, the first client device 10 executes an offer list request (S1310) as in FIG.
After step S1310, the server 30 executes offer list creation (S1330) to offer list response (S1331) as in FIG.
After step S1331, the first client device 10 presents the offer list (S1311) as in FIG.

After step S1311, the first client device 10 executes a message request (S1410).
Specifically, the processor 12 displays a screen P1310 (FIG. 15) similar to that of FIG. 13 on the display.

When the care user enters a message in field object F1311, processor 12 sends message request data to server 30. FIG. The message request data includes, for example, the following information.
・Care institution identification information entered by the care user ・Patient identification information entered by the care user ・Facility identification information specified by the care user ・Message information entered in the field object F1311 (an example of “first message information”)

After step S1410, the server 30 sends a message response (S1430).
Specifically, the processor 32 refers to the offer information database (FIG. 7) associated with the care institution identification information included in the message request data to associate the patient identification information and the facility identification information included in the message request data. Identifies the record that was offered (hereinafter referred to as the “offer record”).
Processor 32 stores the message information in the "chat message" field of the offer record.
Processor 32 references the patient information database (FIG. 6) to identify patient information included in the message request data.
Processor 32 references the facility information database (FIG. 5) to identify facility contact information included in the message request data.
The processor 32 transmits the message response data to the contact indicated by the facility contact information (for example, the second client device 20). The message response data includes, for example, the following information.
・Message information included in message request data (an example of “second message information”)
・Identified patient information

After step S1430, the second client device 20 performs message presentation (S1420).
Specifically, processor 22 displays screen P1420 (FIG. 15) on the display.

Screen P1420 includes display object A1420 and field object F1420.

The display object A1420 displays patient information included in the message response data.

The field object F1420 displays message information included in the message response data (that is, messages exchanged between the care user and the facility user). A field object F1420 is an object that receives an input of a message.

After step S1420, the second client device 20 executes a message request (S1421).
Specifically, when the facility user enters a message in the field object F1420, the processor 12 transmits message request data to the server 30. FIG. The message request data includes, for example, the following information.
- Message information entered in the field object F1420

After step S1410, the server 30 executes a message response (S1431).
Specifically, processor 32 stores the message information contained in the message request data in the "chat message" field of the offer record.
Processor 32 transmits the message response data to first client device 10 . The message response data includes, for example, the following information.
・Message information included in message request data

After step S1431, the first client device 10 presents the message (S1411).
Specifically, processor 12 displays screen P1410 (FIG. 15) on the display.

A screen P1410 includes a display object A1311, operation objects B1311a to B1311c, and a field object F1410.

The field object F1410 displays the message information included in the message response data transmitted in step S1431 (that is, messages exchanged between the care user and the facility user). A field object F1410 is an object that receives an input of a message.

After step S1411, the first client device 10 executes a move-in decision request (S1412).
Specifically, when the care user operates the operation object B1311c, the processor 42 transmits move-in decision request data to the server 30 .
The move-in determination request data includes, for example, the following information.
・Care user-entered care institution identification information ・Care user-entered patient identification information ・Care user-specified facility identification information

After step S1412, the server 30 updates the database (S1432).
Specifically, the processor 32 refers to the offer information database (FIG. 7) and updates the status information associated with the patient identification information and facility identification information included in the occupancy decision request data to "occupancy decision".

(5) Modification A modification of the present embodiment will be described.

(5-1) Modification 1
Modification 1 of the present embodiment will be described. Modification 1 of this embodiment is an example of exchanging messages between a care institution and a patient.

In Modified Example 1 of the present embodiment, the server 30 shares the care user's message with the patient user after "acceptance adjustment in progress" is stored in the "status" field in step S1332.
Specifically, in step S1430 or S1431, the processor 32 transmits message information according to the care user's instruction to the third client device 40. FIG.

Also, after "Adjusting acceptance" is stored in the "status" field in step S1332, server 30 shares the message of the patient user with the care user.
Specifically, the third client device 40 transmits the patient user's message information (an example of “third message information”) to the server 30 according to the patient user's instruction.
At step S1430 or S1431, processor 32 stores the patient-user message information in the "message content" field of the offer record. Processor 32 transmits the message information to first client device 10 .

According to variant 1, after the offer has been shared with the patient, it is possible to exchange messages between the care user and the patient user.
As a result, it becomes possible to easily adjust acceptance to a facility that reflects the patient's intention.

(5-2) Modification 2
Modification 2 of the present embodiment will be described. Modification 2 of the present embodiment is a modification of patient information registration processing.
FIG. 16 is a sequence diagram of patient information registration processing according to Modification 2. As shown in FIG. FIG. 17 is a diagram showing an example of a screen displayed in the information processing of FIG. 16. FIG.

The process of FIG. 16 is triggered by a care user's instruction (for example, input of care institution identification information) given to the first client device 10 .

As shown in FIG. 16, the first client device 10 receives patient information (S2110).
Specifically, processor 12 displays screen P1110 (FIG. 9) on the display.

When the care user inputs patient information into the field object F1110 and operates the operation object B1110, the processor 12 displays a screen P2110 (FIG. 17) on the display.

The screen P2110 includes an operation object B2110 and field objects F2110a to F2110b.

The field object F2110a is an object that receives input of medicine management information. The medicine management information is information relating to management of medicines currently being taken by the patient. Medication management information includes, for example, information about:
- Drug name (for example, a care user is selected from a drug master stored in advance in the storage device 31)
- Dosage (entered by the care user as an example)
Dosing frequency (entered by the care user as an example)

The field object F2110b is an object that accepts input of conditions regarding the desired area (hereinafter referred to as "area conditions").

The operation object B2110 is an object that receives a user instruction for confirming the input to the field objects F2110a-F2110b.

When the care user inputs patient information into field objects F2110a-F2110b and operates operation object B2110, processor 12 displays screen P2111 (FIG. 17) on the display.

The screen P2111 includes an operation object B2111 and field objects F2111a to F2111b.

The field object F2111a is an object that receives input of documents related to patient records by care institutions (hereinafter referred to as "patient record documents"). Patient record documents include, for example, documents containing nursing summary information on the content of nursing care performed within the care institution, medical information documents, and other hospital records containing patient information necessary for coordination of discharge destinations. At least one of the documents.

The field object F2111b is an object that receives an input of a condition for disclosure of patient information (hereinafter referred to as "disclosure destination condition").

The operation object B2111 is an object that receives a user's instruction to confirm the input to the field objects F2111a to F2111b.

When the care user inputs patient information into the field objects F2111a-F2111b and operates the operation object B2111, the processor 12 displays a screen P2112 (FIG. 17) on the display.

The screen P2112 includes an operation object B2112 and a field object F2112.

The field object F2112 is an object that receives input of offer items. The offer item is an information item requested from the facility side at the time of the offer.

The operation object B2112 is an object that receives a user instruction for confirming the input to the field object F2112.

When the care user inputs an offer item into the field object F2112 and operates the operation object B2112, the processor 12 displays the screen P1111 (FIG. 9) on the display.

After step S2110, the first client device 10 performs personal information masking (S2111).
Specifically, processor 12 deletes information corresponding to personal information among the information input by the care user in step S2110.

After step S2111, the first client device 10 executes a patient registration request (S2112).
Specifically, when the care user operates the operation object B1111a, the processor 12 transmits patient registration request data to the server 30 .
The patient registration request data includes the following information.
・Care institution identification information ・Patient identification information (for example, the patient's patient registration card number or chart number)
・Occupancy judgment information ・Medicine management information ・Preferred area information ・Patient record documents ・Information on disclosure destination conditions ・Information on offer items

After step S2111, the server 30 performs patient registration (S2130).
Specifically, processor 32 adds a new record to the patient information database (FIG. 6) associated with the care organization identification included in the patient registration request data. Each field in the new record contains the following information:
・“Patient ID” field: Patient identification information included in patient registration request data ・“Residential availability judgment” field: Residential availability determination information included in patient registration request data ・“Medicine management” field (not shown): Patient registration request Medicine management information included in the data ・"Preferred area" field (not shown): Desired area information included in patient registration request data ・"Nursing summary" field (not shown): Nursing summary information included in patient registration request data ・"Publication destination" field (not shown): Information on disclosure destination conditions included in patient registration request data ・"Offer items" field (not shown): Information on offer items included in patient registration request data

After step S2130, the server 30 executes information disclosure (S2131).
Specifically, processor 32 refers to the facility information database (FIG. 5) to refer to the facility (hereinafter referred to as the "appropriate facility") that corresponds to the information regarding the disclosure destination conditions registered in the "publication destination" field in step S2130. identify. The applicable facility is, for example, at least one of the following.
・The facility should be of the type desired by the patient. ・The facility should be included in the area desired by the patient. ・The facility should be affordable for the patient.

Processor 32 presents the patient information registered in step S2130 to the identified relevant facility.

According to Modified Example 2, patient information is not disclosed to facilities other than those corresponding to the disclosure destination conditions. As a result, it is possible to improve the probability of receiving an offer from a facility desired by the patient.

According to the modified example 2, the storage device 31 stores the medicine management information regarding the management of the medicine that the patient is taking. As a result, the facility user can determine whether or not the patient's medicine can be accepted after grasping the necessary measures for management of the patient's medicine.

According to Modification 2, when personal information is included in the information input by the care user, the happiness information is deleted. This can prevent personal information from being disclosed to the facility.

In Modified Example 2, step S2110 shows an example in which the medicine management information is received according to the care user's operation, but the scope of Modified Example 2 is not limited to this.
Modification 2 is that in step S2110, an image of a document in which medicine management information is described is received in response to an operation by the care user, and first client device 10 or server 30 recognizes characters included in the image. By doing so, it can also be applied to an example of registering medicine management information in the server 30 .

(5-3) Modification 3
Modification 3 of the present embodiment will be described. Modified Example 3 of the present embodiment is an example of notifying a care user of a patient for whom offer adjustment is to be performed (hereinafter referred to as "adjustment target patient").
FIG. 18 is a sequence diagram of a follow candidate presentation process according to Modification 3. As shown in FIG. 19 is a diagram showing an example of a screen displayed in the information processing of FIG. 18. FIG.

The process of FIG. 18 is executed each time the database of the server 30 is updated.

As shown in FIG. 18, the server 30 extracts patients to be adjusted (S3130).
Specifically, the processor 32 extracts the patient identification information of a patient who corresponds to at least one of the following (hereinafter referred to as "adjustment target patient").
・Patients whose number of offers is greater than or equal to a predetermined threshold ・Patient whose number of offers is less than or equal to a predetermined threshold ・Patient whose number of offers from the relevant facility is greater than or equal to a predetermined threshold ・Patient whose number of offers from the relevant facility is a predetermined number -Patients whose number of remaining days until the scheduled discharge date is less than or equal to a predetermined threshold -Patients who do not respond to care users and facility users for a certain period of time

After step S3130, the server 30 executes notification of the adjustment target patient (S3131).
Specifically, the processor 32 transmits patient information associated with the patient identification information of the adjustment target patient extracted in step S3130 (hereinafter referred to as “adjustment target patient information”) to the first client device 10 .

After step S3131, the first client apparatus 10 displays the adjustment target patient information (S3110).
Specifically, processor 12 displays screen P3110 (FIG. 19) on the display.
The screen P3110 displays the number of offers, the number of offers from the corresponding facility, and the number of remaining days until the scheduled date of discharge for each adjustment target patient.

According to Modified Example 3, based on at least one of the number of offers, the number of offers from the facility, and the number of remaining days until the scheduled discharge date, patients with high priority for adjustment are presented to the care user as adjustment target patients. do. As a result, the care user can preferentially adjust admission to the facility of a patient with a high adjustment priority.

Although Modification 3 shows an example in which adjustment target patient information is presented to the first client device 10 (that is, the care user), the scope of Modification 3 is not limited to this. Modification 3 can also be applied to an example in which adjustment target patient information is presented to the administrator of the server 30 (a person who has authority different from that of the care user).
In this case, in step S3131, the server 30 transmits the adjustment target patient information extracted in step S3130 to the administrator terminal device.
A predetermined management screen is displayed on the display of the administrator terminal device. The management screen displays the number of offers, the number of offers from the corresponding facility, and the number of remaining days until the scheduled date of discharge for each adjustment target patient. No adjustment target patient information is transmitted to the first client device 10 (that is, no adjustment target patient information is presented to the care user).
Based on the adjustment target patient information displayed on the management screen, the administrator can preferentially adjust admission to the facility of patients with high priority for adjustment. As a result, the burden on care users can be reduced.

(6) Summary of the present embodiment The server 30 of the present embodiment obtains an offer for the patient's move-in from the second client device 20 in accordance with the instruction of the facility user who browsed the patient information, and then receives the care user's message and the facility user's message is presented to the first client device 10 and the second client device 20 . Especially when the care institution is an in-home long-term care support office, for example, at the stage where the condition of the patient to be cared for deteriorates and it is decided to be hospitalized in a medical institution, the care manager will move in after being discharged from the medical institution. Coordination with the facility can begin prior to discharge.
This facilitates information exchange between care institutions and facilities.

The server 30 of the present embodiment may notify the third client device 40 of an offer by the facility user in accordance with an instruction from the care user.
Thereby, the care user can easily inform the patient user of the offer from the facility user.

(7) Other Modifications Other modifications will be described.

The storage device 11 may be connected to the first client device 10 via the network NW. The storage device 21 may be connected to the second client device 20 via the network NW. Storage device 31 may be connected to server 30 via network NW. The storage device 41 may be connected to the third client device 40 via the network NW.

Although the embodiments of the present invention have been described in detail above, the scope of the present invention is not limited to the above embodiments. Also, the above embodiments can be modified and modified in various ways without departing from the gist of the present invention. Also, the above embodiments and modifications can be combined.

1: information processing system 10 : first client device 11 : storage device 12 : processor 13 : input/output interface 14 : communication interface 20 : second client device 21 : storage device 22 : processor 23 : input/output interface 24 : communication interface 30 : server 31 : storage device 32 : processor 33 : input/output interface 34 : communication interface 40 : third client device 41 : storage device 42 : processor 43 : input/output interface 44 : communication interface

Claims (8)

A server connectable to a first client device used by a care user who cares for a patient and a second client device used by a facility user of a facility that accepts the patient,
means for obtaining patient identification information identifying the patient and patient information about the patient from the first client device in response to instructions from the care user;
means for storing the patient identification information and the patient information in association with each other;
comprising means for presenting the patient information to the second client device in response to an instruction from the facility user;
Means for obtaining an offer for accepting a specified patient specified by the facility user from the second client device in the facility in response to an instruction from the facility user;
The offer includes facility identification information that identifies the facility and patient information of the designated patient,
means for associating and storing offer patient identification information associated with the designated patient, facility identification information, and care institution identification information identifying a care institution;
means for updating status information associated with the offer patient identification information to indicate that the offer has been obtained;
After obtaining the offer, the first client device and the second client device are provided with first message information according to instructions from the facility user corresponding to the offer and second messages according to instructions from the care user. comprising means for presenting information;
server. means for sharing the offer with a patient user upon direction of the care user;
the means for updating updates the status information to indicate that the offer has been shared;
A server according to claim 1 . After sharing the offer to the patient-user, the means for presenting the message information includes:
presenting message information in accordance with instructions from the care user to a third client device used by the patient user;
presenting message information to the first client device in accordance with instructions from the patient user;
3. A server according to claim 2. The patient information includes drug management information related to management of drugs being taken by the patient,
The server according to any one of claims 1 to 3. The means for storing the patient identification information and the patient information in association with each other stores the patient information other than the personal information and the patient identification information when the patient information including the personal information of the patient is acquired. memorize in association with
The server according to any one of claims 1 to 3. comprising means for accepting a specification of a disclosure destination condition of the patient information;
Equipped with means for determining the applicable facility that corresponds to the disclosure destination condition,
the means for presenting the patient information presents the patient information to the facility;
The server according to any one of claims 1 to 3. Means for determining patients to be adjusted based on the number of offers for the patient, the number of offers from facilities that meet the conditions desired by the patient, and the number of days remaining until the scheduled date of discharge of the patient with
comprising means for presenting patient information of the adjustment target patient to the care user;
The server according to any one of claims 1 to 3. A program of a server connectable to a first client device used by a care user who cares for a patient and a second client device used by a facility user of a facility that accepts the patient, wherein
Functioning as a means for acquiring patient identification information for identifying the patient and patient information about the patient from the first client device in response to instructions from the care user;
functioning as means for storing the patient identification information and the patient information in association with each other;
causing the second client device to function as means for presenting the patient information in accordance with an instruction from the facility user;
Functioning as a means for acquiring an offer for accepting a designated patient designated by the facility user into the facility from the second client device in accordance with an instruction from the facility user;
The offer includes facility identification information that identifies the facility and patient information of the designated patient,
function as means for associating and storing offer patient identification information associated with the designated patient, facility identification information, and care institution identification information identifying a care institution;
serve as means for updating status information associated with the offer patient identification information to indicate that the offer has been obtained;
After obtaining the offer, the first client device and the second client device are provided with first message information according to instructions from the facility user corresponding to the offer and second messages according to instructions from the care user. serve as a means of presenting information,
program for.

Images