Information providing method, information providing system, and program

Abstract

It enables the improvement of the efficiency of identity verification in the medical field as compared to the case where only the patient's account name is displayed in the area for displaying the interaction with the patient by the messaging app. 【Solution means】In the information providing method for providing the patient's medical record screen to the client terminal as a cloud service, as an instruction for the medical record screen regarding a specific patient, a process for receiving the display of the interaction on the messaging app between the specific patient and the medical institution, and a process for displaying, in the area for displaying the interaction on the messaging app on the medical record screen, the account name of the specific patient and the name of the specific patient are provided.

Description

Technical Field

[0001] The present invention relates to an information providing method, an information providing system, and a program.

Background Art

[0002] Messaging apps such as the LINE (registered trademark) app and other messaging apps are being used not only for personal communication but also in business. In messaging apps, the content of the communication between oneself and the other party is displayed, for example, in speech bubbles. In the case of the LINE app, the communication screen is called a chat screen or a talk screen (hereinafter referred to as the "chat screen"). Incidentally, when there is one communication partner, the account name of the partner is displayed at the top of the chat screen.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Currently, a service that links the communication between the official account of a medical institution and a patient on the LINE app with an electronic medical record has been put into practical use. In this type of service, for example, it is possible for a patient to make a reservation for medical treatment. Also, it is possible to display the patient's chat screen in a partial area (pain) of the display screen of the patient information recorded in the electronic medical record. However, in the current chat screen, only the patient's account name is displayed as the information of the other party, and the patient's name is not displayed. However, from the importance of patient identification in the medical field, it is desired that the patient's name can be confirmed on the chat screen.

[0005] The object of the present invention is to enable the improvement of the efficiency of identity verification in a medical field as compared with a case where only the patient's account name is displayed in a region for displaying communication with a patient by a messaging application.

Means for Solving the Problem

[0006] The invention according to claim 1 is an information providing method for providing a patient's medical record screen to a client terminal as a cloud service, the method including: a process of receiving, as an instruction for the medical record screen of a specific patient, a display of an interaction on a messaging application between the specific patient and a medical institution; and a process of displaying, in a region for displaying the interaction on the messaging application on the medical record screen, the account name of the specific patient and the name of the specific patient. The invention according to claim 2 is the information providing method according to claim 1, wherein the instruction for displaying the interaction on the messaging application is received through a selection operation of a display item provided on the medical record screen. The invention according to claim 3 is the information providing method according to claim 1, wherein each time the display of the interaction on the messaging application is received through the medical record screen, the account name of the specific patient is combined with the name of the specific patient and displayed at a display position indicating the other party of the interaction. The invention according to claim 4 is the information providing method according to claim 1, wherein each time the display of the interaction on the messaging application is received through the medical record screen, the name of the specific patient is added to the account name of the specific patient displayed at a display position indicating the other party of the interaction. The invention according to claim 5 is an information providing system having one or more processors and providing a patient's medical record screen to a client terminal as a cloud service, wherein the one or more processors receive, as an instruction for the medical record screen regarding a specific patient, a display of an interaction on a messaging app between the specific patient and a medical institution, and display the account name of the specific patient and the name of the specific patient in a region on the medical record screen for displaying the interaction on the messaging app. The invention according to claim 6 is a program for causing a computer that provides a patient's medical record screen to a client terminal as a cloud service to realize a function of receiving, as an instruction for the medical record screen regarding a specific patient, a display of an interaction on a messaging app between the specific patient and a medical institution, and a function of displaying the account name of the specific patient and the name of the specific patient in a region on the medical record screen for displaying the interaction on the messaging app.

Advantages of the Invention

[0007] According to the present invention, it is possible to improve the efficiency of identity verification in a medical field as compared with a case where only the account name of a patient is displayed in a region for displaying an interaction with the patient by a messaging app.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Mode for Carrying Out the Invention

[0009] Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiments described below are merely examples of the mode for carrying out the present invention, and the embodiments of the present invention are not limited to the mode examples described below. Therefore, the technical scope of the present invention is not limited to the scope described in the embodiments below. For example, those obtained by making various changes or improvements to the content described in the embodiments are also included in the technical scope of the present invention. Note that various functional units described later are realized through the execution of programs by, for example, a CPU (= Central Processing Unit), MPU (= Micro Processing Unit), GPU (= Graphics Processing Unit), DSP (= Digital Signal Processor), or other processors.

[0010] <Terminology> First, the terms used in the embodiments will be described. The term "program" is used as a general term for an OS (= Operating System) and application programs. "Medical institution" includes hospitals and clinics. Note that a medical institution is not limited by its name. Hereinafter, it will also be referred to as "clinic" in the sense of a medical institution. "Medical staff" means doctors and other staff of a medical institution. "Clinic terminal" refers to a terminal operated by medical staff. "Patient terminal" refers to a terminal operated by a patient who receives medical treatment or a surgical procedure at a medical institution.

[0011] "Medical record screen" refers to the screen of an electronic medical record displayed on a clinic terminal. The electronic medical record in the embodiments described later is provided as a cloud-based service (hereinafter referred to as "cloud service"). The cloud service is also called SaaS (= Software as a Service). "Message" refers to a character string or image transmitted and received between a patient terminal and a clinic terminal. Images include, for example, still images (so-called photos) and moving images. Note that pre-prepared fixed-form messages are called stickers or stamps. A message is also called a "comment" or "chat".

[0012] "Messaging app" refers to an application program specialized for sending and viewing messages. The messaging app is executed on a patient terminal and a clinic terminal. A "message server" is a server operated by an operator that provides message sending and receiving services through a messaging app. On the screen of the messaging app, messages are displayed in the order in which they were posted. The messaging app displays self and other messages in different positions. For example, the other party's messages are displayed on the left side of the viewing screen. On the other hand, one's own messages are displayed on the right side of the viewing screen.

[0013] <Embodiment> <Overall configuration of the system> FIG. 1 is a diagram for explaining the schematic configuration of an information providing system 1 assumed in the embodiment. The information providing system 1 shown in FIG. 1 is composed of a patient terminal 10, a clinic terminal 20, a message server 30, an electronic medical record server 40, and a cloud network N. The patient terminal 10 in FIG. 1 can exchange messages with the clinic terminal 20 through the message server 30.

[0014] The clinic terminal 20 in FIG. 1 can access the electronic medical records of patients managed by the electronic medical record server 40. By operating the clinic terminal 20, it is possible to create, edit, view, etc. the electronic medical records. Here, the clinic terminal 20 operates as a client terminal with respect to the electronic medical record server 40. The electronic medical record server 40 is a server that manages the electronic medical records of patients in each medical institution. The electronic medical record server 40 in the present embodiment is also provided with a function of associating and managing the messages exchanged between patients and medical staff through the messaging app with the electronic medical records of patients.

[0015] <Configuration of each terminal> The patient terminal 10 in the present embodiment is, for example, a smartphone. However, the patient terminal 10 may also be a tablet-type computer. Depending on the type of messaging app, as the patient terminal 10, a notebook computer, a desktop computer, a wearable terminal, or smart glasses can also be used. Incidentally, smart glasses refer to a glasses-type terminal including a small display and a light guide component that forms an image of the image displayed on the display on the retina.

[0016] The patient terminal 10 as a computer has, for example, a processor, a semiconductor memory, an auxiliary storage device, a display, an input reception device, a speaker, and a communication interface. In the semiconductor memory, UEFI (= Unified Extensible Firmware Interface) or the like is stored. The semiconductor memory is also used as an execution area for programs. When the patient terminal 10 is a smartphone, a semiconductor storage is used as the auxiliary storage device. In the auxiliary storage device, firmware and other programs are stored.

[0017] For the display, a liquid crystal display or an organic EL (= Electro Luminescence) display is used. As the input reception device, a capacitive touch sensor having transparency that does not obstruct visual recognition of the information displayed on the display, a power button, or other physical buttons are used. As the communication interface, for example, a wireless LAN (= Local Area Network), 5G, or other mobile communication systems are used.

[0018] In FIG. 1, for reasons of explanation, only one patient terminal 10 is drawn, but in the actual information providing system 1, a plurality of patient terminals 10 are connected to the cloud network N. In the present embodiment, the LINE app is assumed as the messaging app used by the patient terminal 10 for message exchange. In the case of FIG. 1, the patient terminal 10 is operated by the patient, Mr. "Taro Tokyo". In the case of FIG. 1, Mr. Taro Tokyo's account name is "Taro Gotanda". The account name can be freely set by the user (here, the patient) who uses the messaging app. In the case of FIG. 1, Mr. Taro Tokyo's account name is different from his name.

[0019] The account name is the display name on the messaging service. The account name is displayed in the messaging app. The account name is linked to the account. The account is information (hereinafter referred to as "authentication information") used by the message server 30 for user authentication. For example, username, address, phone number, email address, and other registration information are used as the authentication information. The authentication information is managed by an ID (= identifier) and a password. The account is also used by the message server 30 to identify the sender and recipient of a message. As will be described later, the account ID can also be linked to the account. In the case of FIG. 1, the account ID is "SSSS".

[0020] The clinic terminal 20 is a terminal operated by medical staff of a medical institution. The clinic terminal 20 shown in FIG. 1 is a terminal operated at "Clinic X". In the case of this embodiment, a desktop computer is assumed as the clinic terminal 20. However, the clinic terminal 20 may be a notebook computer, a smartphone, or a tablet computer. Technically, a wearable terminal or smart glasses can also be adopted as the clinic terminal 20.

[0021] The clinic terminal 20 as a computer has, for example, a processor, a semiconductor memory, an auxiliary storage device, a display, an input receiving device, a speaker, and a communication interface. The semiconductor memory stores UEFI and the like. When the clinic terminal 20 is a desktop computer, a hard disk drive or a semiconductor storage is used as the auxiliary storage device. The auxiliary storage device stores an OS (= Operating System) and programs.

[0022] When the clinic terminal 20 is a desktop computer, the display is a monitor connected to the terminal main body. For the monitor, for example, a liquid crystal display or an organic EL display is used. When the clinic terminal 20 is a desktop computer, a keyboard and a mouse are used as the input reception device.

[0023] Note that, as the input reception device, a capacitive touch sensor integrally attached to the display surface of the display may be used. A device in which the display and the electrostatic touch sensor are integrated is called a touch panel. In addition, as the input reception device, a tablet that detects operations such as a stylus pen may be used. When the clinic terminal 20 is a smartphone or a tablet computer, a touch panel is used as the display and the input reception device. For the communication interface, for example, a wireless LAN (= Local Area Network), 5G, or other mobile communication systems are used. In FIG. 1, for the sake of explanation, only one clinic terminal 20 is drawn, but in the actual information providing system 1, a plurality of clinic terminals 20 are connected to the cloud network N.

[0024] The clinic terminal 20 shown in FIG. 1 can also exchange messages with the patient terminal 10 through the LINE application according to prior settings. In the case of FIG. 1, the medical staff exchanges messages with the patient using the account name of "Clinic X". This account name is the same as the name of "Clinic X". Note that the account name "Clinic X" is linked to the account of Clinic X. In the case of FIG. 1, the account of Clinic X is linked to the account ID "XXXX".

[0025] The message server 30 is one or more servers operated by the operator providing the messaging application. However, for the message exchange between the patient terminal 10 and the clinic terminal 20, in addition to the message server 30, one or more servers (not shown) operated by the operator developing the patient terminal 10 are also involved. Further, when the clinic terminal 20 is a smartphone or a tablet computer, one or more servers operated by the operator developing the clinic terminal 20 are also involved.

[0026] The message server 30 is composed of, for example, a processor, a semiconductor memory, an auxiliary storage device, and a communication interface. UEFI etc. are stored in the semiconductor memory. For example, a hard disk device or a semiconductor storage is used for the auxiliary storage device of the message server 30. The auxiliary storage device stores an OS (=Operating System) and programs. For example, a wireless LAN (=Local Area Network), 5G or other mobile communication systems are used for the communication interface.

[0027] The electronic medical record server 40 is one or more servers that provide a service of providing the electronic medical record of a patient to the clinic terminal 20 of Clinic X. FIG. 2 is a diagram for explaining an example of the hardware configuration of the electronic medical record server 40. The electronic medical record server 40 shown in FIG. 2 is composed of a processor 401 that controls the operation of the entire terminal, a semiconductor memory 402, an auxiliary storage device 403, and a communication interface 404.

[0028] The processor 401 is, for example, a CPU. The semiconductor memory 402 stores, for example, UEFI. The semiconductor memory 402 is also used as an execution area for the electronic medical record application 411 and other programs. The auxiliary storage device 403 is, for example, a hard disk drive or a semiconductor storage. The auxiliary storage device 403 stores an OS and programs. The communication interface 404 is a device that enables communication with the patient terminal 10, the clinic terminal 20, the message server 30, and other terminals. The communication interface 404 is required to have a communication function compatible with the cloud network N used for communication.

[0029] Stored in the auxiliary storage device 403 shown in FIG. 2 are an electronic medical record application 411, clinic information 412, brand-specific electronic medical record information 413, brand-specific patient information 414, brand-specific reservation information 415, and brand-specific message logs 416. Hereinafter, the clinic information 412, the brand-specific electronic medical record information 413, the brand-specific patient information 414, the brand-specific reservation information 415, and the brand-specific message logs 416 are also referred to as management data.

[0030] The electronic medical record application 411 is an application program that realizes a service for providing a service for managing a patient's electronic medical record for each clinic. The electronic medical record application 411 in the present embodiment has a function of receiving an operation input from the clinic terminal 20 and a function of displaying information corresponding to the content of the received operation input on the clinic terminal 20. The electronic medical record application 411 also has a function of registering a new patient's electronic medical record according to the operation of medical staff.

[0031] The electronic medical record application 411 has a function of displaying, on the display of the clinic terminal 20, the medical record screen of a specific patient designated by medical staff. The electronic medical record application 411 has a function of recording medical records and the like through the operation input of medical staff on the medical record screen. The electronic medical record application 411 has a function of switching display items on the medical record screen through the operation input of medical staff on the medical record screen. Needless to say, these functions are just examples and not all of the functions that the electronic medical record application 411 has.

[0032] The clinic information 412 is information used for the management of clinics that use cloud services. The electronic medical record information 413 is the medical record of a patient. In the case of this embodiment, the electronic medical record information 413 is managed by brand. The patient information 414 is the personal information of the patient linked to the electronic medical record. In the case of this embodiment, the patient information 414 is managed by brand.

[0033] The reservation information 415 is information related to the reservation of medical treatment at the clinic. In the case of this embodiment, the reservation information 415 is managed by brand. The message log 416 is a log of messages exchanged between the clinic and the patient. That is, the message log 416 records messages exchanged between the clinic's account (or account ID) and the patient's account (or account ID) via the message server 30. In the case of this embodiment, the message log 416 is managed by brand.

[0034] <Structure of management data> FIG. 3 is a diagram for explaining the data structure of the clinic information 412, the data structure of the electronic medical record information 413, and the data structure of the patient information 414. The clinic information 412 shown in FIG. 3 includes a "clinic ID" 412A, a "clinic name" 412B, a "brand ID" 412C, an "account ID" 412D, and an "API (= Application Programming Interface) key" 412E. The "clinic ID" 412A is an administrative identifier assigned to each clinic. "Clinic Name" 412B is the name of a clinic that uses cloud services. In fact, not only "Clinic Name" 412B, but also information such as the clinic's address and contact details is managed.

[0035] "Brand ID" 412C is the identification ID of the clinic. "Account ID" 412D is an identifier that identifies an individual associated with an account. "Account ID" 412D is uniquely assigned within the messaging service. When the messaging app is the LINE app, the LINE ID is stored in "Account ID" 412D. "API Key" 412E is an identifier for the electronic medical record server 40 to access the messaging service provided by the message server 30 (see Figure 1) for a specific account (e.g., Clinic X). As will be described later, "API Key" 412E is registered from the clinic terminal 20, for example, at the start of using the cloud service.

[0036] The electronic medical record information 413 shown in Figure 3 includes "Medical Record ID" 413A, "Patient ID" 413B, "Medical Record 1" 413C, "Medical Record 2" 413D, and "Medical Record 3" 413E. "Medical Record ID" 413A is an identifier for the electronic medical record associated with a patient. "Patient ID" 413B is an identifier for the patient. "Medical Record 1" 413C, "Medical Record 2" 413D, and "Medical Record 3" 413E are records of medical treatment. In the case of Figure 3, each medical record stores the medical treatment date, the attending physician, the attending staff, the consultation content, images, test results, treatment content, surgical content, accounting information, etc.

[0037] The patient information 414 shown in Figure 3 includes "Patient ID" 414A, "Name" 414B, "Gender" 414C, "Date of Birth" 414D, "Account Name" 414E, "Account ID" 414F, and "Email Address" 414G. "Patient ID" 414A is an identifier for the patient. "Name" 414B is the patient's name. In the case of Figure 3, examples include Mr. "Taro Tokyo", Ms. "Hanako Yokohama", and Mr. "Jiro Osaka".

[0038] "Gender" 414C is the patient's gender. In the figure, "M" means male and "F" means female. Note that "Gender" 414C may allow for unregistered or other information recordings. "Date of Birth" 414D is the patient's date of birth. "Account Name" 414E is the display name of the message. The account name of Mr. "Taro Tokyo" shown in Figure 3 is "Taro Gotanda". "Account Name" 414E can be freely registered by the patient. Therefore, "Account Name" 414E does not necessarily match the patient's name.

[0039] "Account ID" 414F is an identifier that identifies the individual associated with the patient's account. Therefore, "Account ID" 414F is uniquely assigned within the messaging service. When the messaging app is the LINE app, the LINE ID is used for "Account ID" 414F. "Email Address" 414G is the email address registered for communication with the patient. Note that a phone number may be registered instead of or together with "Email Address" 414G.

[0040] Figure 4 is a diagram explaining the data structure of reservation information 415 and the data structure of message log 416. The reservation information 415 shown in Figure 4 includes "Reservation ID" 415A, "Patient ID" 415B, "Reservation Date and Time" 415C, "Desired Treatment / Procedure" 415D, and "Desired Doctor / Staff" 415E.

[0041] "Reservation ID" 415A is an identifier assigned at the time of reservation acceptance. "Patient ID" 415B is the patient's identifier. "Reservation Date and Time" 415C is the date and time of the reservation. "Desired Treatment / Procedure" 415D is the content of the desired treatment or procedure. This item is used when the content of the treatment or procedure can be reserved. Examples of the content of the treatment include only prescribing medicine, requesting a preventive injection, and diagnosing a physical condition with fever. Examples of the content of the procedure include treating freckles and dullness, treating mole removal, and hair removal. "Desired Doctor / Staff" 415E is the content of the desired doctor or staff. This item is used when the doctor or staff involved in the treatment or procedure can be specified.

[0042] The message log 416 shown in FIG. 4 includes a "timestamp" 416A, a "patient's account name" 416B, a "patient's account ID" 416C, a "content of the received message" 416D, and a "content of the sent message" 416E. The "timestamp" 416A is the date and time when the message server 30 (see FIG. 1) receives a message from the patient terminal 10 (see FIG. 1) or the clinic terminal 20 (see FIG. 1).

[0043] The "patient's account name" 416B is information for identifying the patient who exchanges messages with Clinic X. In the case of FIG. 4, the patient's account name is "Taro Gotanda". As described above, the account name may be different from the patient's "name" 414B (see FIG. 3). The "patient's account ID" 416C is an identifier for identifying the individual associated with the patient's account. The "patient's account ID" 416C is uniquely given within the messaging service. When the messaging app is the LINE app, the LINE ID is stored in the "patient's account ID" 416C.

[0044] The "content of the received message" 416D records the content of the message received from the patient. In the case of FIG. 4, "Reserved", "Hello, doctor", and "I will visit in the evening. Thank you" are recorded. Note that the " / " in the notation means a line break. The content of the message sent, "416E", records the content of the messages sent by medical staff to patients using the clinic's account name. In the case of Figure 4, "Hello" and "Please contact us if you have any concerns" are recorded.

[0045] <Processing sequence> Hereinafter, with reference to Figures 5 to 12, the processing sequence executed in the information providing system 1 will be described.

[0046] <Initial settings> First, the initial settings required of the clinic at the start of the cloud service will be described. Figure 5 is a diagram for explaining an example of the processing sequence at the time of initial settings. The symbol S shown in the figure means step. Also, the clinic terminal 20 shown in Figure 5 is assumed to be the terminal of Clinic X. First, the medical staff logs in to the message server 30 through the operation of the clinic terminal 20 (step 101). A login ID and a login password are sent from the clinic terminal 20 to the message server 30. The login ID and the login password are input by the medical staff.

[0047] The message server 30 executes login authentication using the received login ID and login password (step 102). That is, the message server 30 verifies the identity using the login ID and the login password. Figure 5 assumes the case of successful login. Next, the medical staff requests an API key from the message server 30 through the operation of the clinic terminal 20 (step 103).

[0048] The message server 30 that has received the API key request sends an API key dedicated to Clinic X to the clinic terminal 20 that is the request source (step 104). This API key is a character string required for Clinic X to access the services provided by the message server 30. Medical staff who have obtained the API key register the API key in the electronic medical record server 40 through the operation of the clinic terminal 20 (step 105). The electronic medical record server 40 registers the API key in association with, for example, the account ID of Clinic X (step 106). In the case of this embodiment, the API key is registered in the clinic information 412 (see FIG. 3).

[0049] Next, the electronic medical record server 40 issues webhook parameters for receiving a notification from the message server 30 that a message addressed to Clinic X has been received, and notifies the clinic terminal 20 (step 107). The webhook parameters include the account ID of Clinic X and the URL of the electronic medical record server 40. Thereafter, the medical staff sets the webhook parameters issued by the electronic medical record server 40 in association with the account ID of Clinic X in the message server 30 through the operation of the clinic terminal 20 (step 108). The message server 30 that has received the setting from the clinic terminal 20 registers the webhook parameters issued by the electronic medical record server 40 in the message server 30 in association with the account ID of Clinic X (step 109).

[0050] <Settings of the Message Application> Next, the settings required for the patient and the clinic to exchange messages via the messaging application will be described. These settings include a setting that starts when the patient accesses the official account of the medical institution (hereinafter referred to as "Setting 1") and a setting that starts with a push notification from the medical institution side to the patient (hereinafter referred to as "Setting 2").

[0051] <In the Case of Setting 1> FIG. 6 is a diagram for explaining an example of a processing sequence of settings that starts when a patient accesses the official account of a medical institution. In the case of FIG. 6, it is assumed that the patient terminal 10 is the terminal operated by Mr. Taro Tokyo. Also, the clinic terminal 20 is assumed to be the terminal of Clinic X. In the case of FIG. 6, the patient applies for registration with the account ID of Clinic X through the operation of the patient terminal 10 (step 201). When the messaging app is the LINE app, this application corresponds to a "friend application".

[0052] The message server 30 that has received the application notifies the electronic medical record server 40 of Mr. Taro Tokyo's registration application addressed to the account ID of Clinic X (step 202). This notification includes Mr. Taro Tokyo's account ID and the account ID of Clinic X. This notification is executed through the function of the webhook parameters registered in step 109 (see FIG. 5). Note that this notification is not recorded in the message log 416 (see FIG. 4).

[0053] Next, the message server 30 notifies the patient terminal 10 operated by Mr. Taro Tokyo of the menu screen for Mr. Taro Tokyo registered as a friend of Clinic X (step 203). The menu screen here is, for example, called a my page. Through the menu screen, the patient can set reservations, input questionnaires, send messages, etc. Incidentally, the reservation button on the menu screen embeds the URL (= Uniform Resource Locator) of the reservation site.

[0054] In the case of FIG. 6, Mr. Taro Tokyo sends reservation information for Clinic X from the menu screen (step 204). The destination for sending the reservation information is the reservation site of the electronic medical record server 40. The reservation information includes, for example, the URL of the reservation site, Mr. Taro Tokyo's account ID, the content of the desired treatment or procedure, the date and time for which the reservation is desired, the name (Taro Tokyo), gender, email address, date of birth, and information on the desired doctor or staff. If the patient who sent the reservation information is a new patient, the electronic medical record server 40 registers the information of Mr. Taro Tokyo in the electronic medical record information 413 (see Fig. 3) and the patient information 414 (see Fig. 3) of Clinic X (step 205). In addition, the electronic medical record server 40 adds the reservation of Mr. Taro Tokyo to the reservation information 415 (see Fig. 4) of Clinic X (step 206).

[0055] <In the case of setting 2> Fig. 7 is a diagram for explaining an example of a processing sequence of a setting started by a push notification from a medical institution to a patient. Also in the case of Fig. 7, it is assumed that the patient terminal 10 is the terminal operated by Mr. Taro Tokyo. Also, the clinic terminal 20 is assumed to be the terminal of Clinic X. In the case of Fig. 7, the electronic medical record server 40 refers to the patient information 414 (see Fig. 3) and presents a QR code (registered trademark) to Mr. Taro Tokyo (a patient who has a patient ID but no registered account ID or account name and no registered friends). (step 301). For sending an email, the "email address" 414G (see Fig. 3) registered in the patient information 414 is used, etc.

[0056] In the case of Fig. 7, the QR code includes the patient ID, the account ID of Clinic X, the URL of the message server 30, and the URL of the redirect destination. Mr. Taro Tokyo reads the QR code etc. and applies for registration to Clinic X via the message server 30 (step 302). After the message server 30 links the account ID of Mr. Taro Tokyo to the account ID of Clinic X, it notifies the clinic terminal 20 of Clinic X of the addition of Mr. Taro Tokyo as a friend (step 303).

[0057] Note that the message server 30 that has received the application for registration to the friend addition site sends Mr. Taro Tokyo's application to the URL of the redirect destination (here, the URL of the electronic medical record server 40). This application includes the account ID of Clinic X, the account ID of Mr. Taro Tokyo, and the patient ID of Mr. Taro Tokyo. The electronic medical record server 40 uses the notified patient ID to add the account ID of Mr. Taro Tokyo to the patient information 414 of Clinic X (see Fig. 3) (step 304).

[0058] <Recording of message log> Fig. 8 is a diagram for explaining the registration operation of a message log when a message is sent from a patient during a period when the patient's medical record screen is not displayed on the clinic terminal 20. In the case of Fig. 8, the patient terminal 10 is also assumed to be the terminal operated by Mr. Taro Tokyo. Also, the clinic terminal 20 is assumed to be the terminal of Clinic X. Mr. Taro Tokyo sends message A addressed to Clinic X through the messaging app on the patient terminal 10 (step 401). Message A includes the account ID of Mr. Taro Tokyo, the account ID of Clinic X, and the content of message A. The message server 30 notifies the clinic terminal 20 of the reception of message A addressed to Clinic X (step 402).

[0059] Also, the message server 30 notifies the electronic medical record server 40 of the reception of message A from Mr. Taro Tokyo addressed to Clinic X and the content of message A through the function of the webhook parameter registered for Clinic X (step 403). The electronic medical record server 40 registers message A in the message log 416 of Clinic X (see Fig. 4) (step 404). Furthermore, the electronic medical record server 40 notifies the clinic terminal 20 of the reception of message A addressed to Clinic X (step 405).

[0060] <Viewing chats on the medical record screen> Hereinafter, the processing operations when checking the chat between Clinic X and Mr. Taro Tokyo on the medical record screen will be described.

[0061] <Display of Chat Screen> FIG. 9 is a diagram for explaining an example of a processing sequence executed when a chat screen of a messaging application is embedded and displayed on an electronic medical record screen. The chat screen here is an example of an area for displaying exchanges on the messaging application.

[0062] The processing sequence shown in FIG. 9 starts with the electronic medical record screen of "Taro Tokyo" being displayed on the display of the clinic terminal 20. First, the medical staff operates the clinic terminal 20 and instructs the display of the chat screen by selecting the "Chat" button on the tab bar (step 501). The selection of the "Chat" button is an example of a selection operation of a display item provided on the electronic medical record screen. The operation input to the electronic medical record screen is notified from the clinic terminal 20 to the electronic medical record server 40.

[0063] Upon receiving the notification, the electronic medical record server 40 reads out the message log 416 of Mr. Taro Tokyo (see FIG. 4) and switches the display of the main pane of the electronic medical record screen to the chat screen (step 502). However, the account name and name of Mr. Taro Tokyo are displayed in the title section of the chat screen. The title section displays the counterpart of the message displayed on the chat screen. That is, the title section is an example of a display position indicating the counterpart of the exchange. In the case of this embodiment, the account name of Mr. Taro Tokyo is "Taro Gotanda". In the case of this embodiment, the account name is linked to the account ID of the message sent from Mr. Taro Tokyo to the clinic and stored in the patient information 414 (see FIG. 3) and the message log 416.

[0064] The electronic medical record server 40 displays the title section of the chat screen to be displayed in the main pane of the electronic medical record screen by any of the following processing operations. (1) Operation 1: The electronic medical record server 40 reads out the "name" 414B of the patient (see FIG. 3) associated with the account name and account ID from the patient information 414, and generates a title section by combining the patient's name with the account name. That is, when the electronic medical record server 40 receives an instruction to display a chat screen with a specific patient from the clinic terminal 20, it generates a title section each time. For example, it is displayed in the title section in the form of "account name / patient's name". For example, a title section of "Gotanda Taro / Tokyo Taro" is generated.

[0065] In the case of this embodiment, the electronic medical record server 40 may replace the original title section with the generated title section. Note that the electronic medical record server 40 may place the generated title section in the upper layer of the title section of the chat screen so that the original title section is not recognized. However, the order of the names in the title section is arbitrary, and it may be in the form of "patient's name / account name". In this case, a title section of "Tokyo Taro / Gotanda Taro" is displayed.

[0066] (2) Operation 2: The electronic medical record server 40 reads out the name of the patient associated with the account name and account ID from the patient information 414 and adds it to the account name in the title section. That is, when the electronic medical record server 40 receives an instruction to display a chat screen with a specific patient from the clinic terminal 20, it adds the patient's name to the title section each time. The patient's name may be added after the account name or added (i.e., inserted) before the account name. For example, when adding the "patient's name" after the display position of the "account name", the display of the title section is changed from "Gotanda Taro" to "Gotanda Taro / Tokyo Taro". Also, when adding the "patient's name" before the display position of the "account name", the display of the title section is changed from "Gotanda Taro" to "Tokyo Taro / Gotanda Taro".

[0067] (3) Operation 3: The electronic medical record server 40 stores in the auxiliary storage device 403 (see FIG. 2) a title section including the account name generated for the chat screen on the medical record screen and the patient's name, and reads and uses it when displaying the chat screen for the second and subsequent times. The title section may be stored, for example, as one of the items of the patient information 414 (see FIG. 2) or the message log 416 (see FIG. 2), or may be stored as independent information associated with the account ID, patient ID, etc. In this operation, the generation of the title section is executed only once. However, the replacement of the title section is executed each time an instruction to display the chat screen with a specific patient is received from the clinic terminal 20.

[0068] After the process of step 502 described above, the clinic terminal 20 displays a chat screen with Mr. Taro Tokyo in the main pane of the electronic medical record (step 503). FIG. 10 is a diagram for explaining a display example of the medical record screen 200 displayed on the clinic terminal 20. The medical record screen 200 is displayed on the display of the clinic terminal 20.

[0069] The medical record screen 200 shown in FIG. 10 is divided into three panes. In the case of FIG. 10, patient information is displayed in the left pane 210 of the screen. Also, a tab bar is displayed in the upper pane 220 of the screen. Also, a chat screen is displayed in the central pane 230 of the screen. In the case of this embodiment, the display size of each pane can be changed by the medical staff while browsing the medical record screen.

[0070] In the case of FIG. 10, the name of the patient registered in the electronic medical record, the patient ID, and the date of birth are displayed in the pane 210 where the patient information is displayed. Note that the display of the pane 210 shown in FIG. 10 is an example, and in addition, gender, allergy information, special notes, medical examination history, and accounting information are also displayed. The pane 210 is also referred to as a side pane. Also, in relation to the main pane, the pane 210 is also referred to as a sub-pane.

[0071] In the case of FIG. 10, on the pane 220 where the tab bar is displayed, selection buttons for items to be displayed on the pane 230 are shown. In the case of FIG. 10, "Medical Record", "Accounting", "Chat", "Inquiry", "Photo", "Document", "Note" are listed. Other items can also be displayed on the selection buttons. In FIG. 10, the state where "Chat" is selected by shading is shown. The pane 220 is also referred to as the top pane. Also, in relation to the main pane, the pane 220 is also referred to as a sub-pane.

[0072] In the case of FIG. 10, on the pane 230, as described above, a chat screen is displayed. In relation to the sub-pane, the chat screen is also referred to as the main pane. As described above, the display size of the pane 230 can be changed by the medical staff while viewing the medical record screen. That is, the display size of the pane 230 has a high degree of freedom. The chat screen shown in FIG. 10 is composed of three regions 231, 232, and 233.

[0073] The region 231 is a title section representing the chat partner. In the case of FIG. 10, in the title section, "Taro Gotanda / Taro Tokyo", which combines the account name "Taro Gotanda" and the patient's name "Taro Tokyo", is displayed. By including the patient's name in the title section of the chat screen, the medical staff can confirm the chat partner without moving their line of sight to the area where patient information is displayed (i.e., the pane 210).

[0074] Also, the pane 230 is a display area that is long in the horizontal direction. For this reason, in the title section of the chat screen, the patient's name can be displayed larger compared to the font size of the pane 210 where the horizontal display size is limited. For this reason, the discriminability of the chat partner by the medical staff is increased. That is, the discriminability of the patient's name is increased.

[0075] In addition, the account name is displayed on the chat screens of all accounts that use the messaging app, except when there are individual display settings. Therefore, the patient's name is not always used for the account name, and unlike the account ID, it may overlap with other accounts. However, as in this embodiment, by displaying the patient's name in the title section of the chat screen on the medical record screen where identity verification is important, medical staff can confirm the patient's name without taking their eyes off the chat screen.

[0076] In area 232, the contents of the messages recorded in the message log 416 (see FIG. 4) are displayed in chronological order. In area 233, an input field 233A for messages and a "send" button 233B are displayed. In the case of FIG. 10, the input field 233A displays the message "Don't forget your insurance card" before sending. This message is sent to the account named "Taro Gotanda" by operating the "send" button 233B.

[0077] FIG. 11 is a diagram showing a display example when a chat screen is displayed using the account of Clinic X from a terminal not logged in to the electronic medical record server 40 (see FIG. 1). In FIG. 11, the corresponding parts to those in FIG. 10 are indicated by corresponding reference numerals. Note that the chat screen shown in FIG. 11 assumes a smartphone 20A used for the account of Clinic X. The chat screen shown in FIG. 11 is displayed simultaneously with the medical record screen shown in FIG. 10. Therefore, the display content of the chat screen shown in FIG. 11 is the same as the display content of the chat screen shown in FIG. 10.

[0078] By the way, the chat screen shown in FIG. 11 is displayed as a screen of the messaging app, not as a medical record screen. Therefore, in area 231 of FIG. 11, only the account name is displayed in the title section representing the chat partner. That is, only "Taro Gotanda" is displayed. This is because only the message server 30 is involved in the display of the chat screen shown in FIG. 11. In other words, this is because the electronic medical record server 40 does not intervene in the process of notifying messages in the display of the chat screen shown in FIG. 11. In the case of a medical record screen that does not use the technology described in this embodiment, the same screen as the chat screen shown in FIG. 11 is displayed on the medical record screen. That is, only the account name is displayed in the title section of the chat screen.

[0079] FIG. 12 is a diagram for explaining a processing sequence when message transmission and reception are executed while the patient's medical record screen is displayed on the clinic terminal 20. In FIG. 12, the corresponding parts to those in FIG. 9 are marked with corresponding reference numerals. Incidentally, steps 601 to 605 are a processing sequence when a message addressed to Clinic X is transmitted from the patient terminal 10. On the other hand, steps 701 to 705 are a processing sequence when a message addressed to Mr. Taro Tokyo is transmitted from the clinic terminal 20.

[0080] First, steps 601 to 605 will be described. Mr. Taro Tokyo operates the messaging app on the patient terminal 10 and transmits message A addressed to Clinic X (step 601). This message A is transmitted to the message server 30. Message A includes Mr. Taro Tokyo's account ID, Clinic X's account ID, and the content of message A. The message server 30 that has received message A notifies the clinic terminal 20 of Clinic X of the reception of message A from Mr. Taro Tokyo according to the account ID indicating the destination (step 602). When this notification is opened in the messaging app of the smartphone 20A (see FIG. 11), the chat screen shown in FIG. 11 is displayed.

[0081] In the case of FIG. 12, the message server 30 notifies the electronic medical record server 40 of the reception of message A from Mr. Taro Tokyo addressed to Clinic X and the content of message A (step 603). This notification is executed as a function of webhook parameters. Upon receiving the notification from the message server 30, the electronic medical record server 40 registers message A in the message log 416 of Clinic X (see FIG. 4) (step 604). Subsequently, the electronic medical record server 40 reflects message A on the chat screen with Mr. Taro Tokyo (step 605).

[0082] Next, steps 701 to 705 will be described. Here, it is assumed that the medical staff of Clinic X is displaying the chat screen on pain 230 of Mr. Taro Tokyo's medical record screen. In this state, the clinic terminal 20 sends message B addressed to Mr. Taro Tokyo from the chat screen on the medical record screen (step 701). This transmission corresponds to the case where, for example, the operation of the "send" button 233B (see FIG. 10) is received with the input "Don't forget your insurance card" entered in the message input field 233A (see FIG. 10).

[0083] Since the medical record screen is displayed as a cloud service, message B addressed to Mr. Taro Tokyo is sent to the electronic medical record server 40. Message B includes the account ID of Clinic X, the account ID of Mr. Taro Tokyo, and the content of message B. Upon receiving the message transmission from Clinic X, the electronic medical record server 40 uses the API key of Clinic X to send message B to the message server 30 (step 702). Upon receiving message B, the message server 30 notifies Mr. Taro Tokyo's patient terminal 10 of the reception of message B from Clinic X according to the account ID indicating the destination (step 703). When Mr. Taro Tokyo opens this notification with the messaging app on his smartphone, message B is displayed on the chat screen.

[0084] In addition, the electronic medical record server 40 transmits message B to the message server 30 and registers message B in the message log 416 (see FIG. 4) of Clinic X (step 704). Further, the electronic medical record server 40 reflects message B on the chat screen with Mr. Tokyo Taro (step 705). Specifically, a message "Don't forget your insurance card" is added to the last line of the area 232 shown in FIG. 10.

[0085] <Small parentheses> As described above, the electronic medical record server 40 in the present embodiment is a server that provides the medical record screen of a patient to the clinic terminal 20 as a cloud service. When this electronic medical record server 40 receives a request to display a chat screen with a specific patient as part of the medical record screen, it displays the account name of the specific patient and the name of the patient in the title section of the chat screen.

[0086] Therefore, the medical staff viewing the medical record screen can easily confirm the name of the patient while keeping an eye on the chat screen. In addition, the display size of the title section of the chat screen displayed in the main pane of the medical record screen is larger than the display size of the patient information displayed in the side pane. Therefore, the medical staff can confirm the name of the patient in a font larger than that in the side pane. As a result, the distinguishability of the name of the patient is increased. Note that the display of the title section including the account name of the patient and the name of the patient described in the present embodiment is provided only on the medical record screen provided as a cloud service.

[0087] <Other embodiments> (1) The electronic medical record described in the above-described embodiment may be provided to the clinic terminal as an on-premises type service. That is, as one of the functions of a program executed by a server installed in a medical institution, the above-described display of the medical record screen may be realized. In addition, the electronic medical record described in the above embodiment may be displayed as a function of a program operating on a clinic terminal. That is, the display of the medical record screen described above may be realized as one of the functions of a stand-alone type program.

[0088] <Summary> The embodiments include the following information providing method, information providing system, and program. (((1))) One of the objects of the present invention is to enable the efficiency of identity verification when displaying the communication with a patient by a messaging app on the patient's medical record screen. The information providing method according to the embodiment is an information providing method for providing a patient's medical record screen to a client terminal as a cloud service, and as an instruction for the medical record screen regarding a specific patient, a process of receiving a display of communication on a messaging app between the specific patient and a medical institution, and a process of displaying the account name of the specific patient and the name of the specific patient in a region for displaying communication on the messaging app on the medical record screen. According to this information providing method, it is possible to improve the efficiency of identity verification when displaying the communication with a patient by a messaging app on the patient's medical record screen.

[0089] (((2))) One of the objects of the present invention is to enable the display of communication with a patient by a messaging app on the medical record screen through an operation on the patient's medical record screen. The information providing method according to ((1)), wherein an instruction for displaying communication on a messaging app is received through a selection operation of a display item provided on the medical record screen. According to this information providing method, it is possible to enable the display of communication with a patient by a messaging app on the medical record screen through an operation on the patient's medical record screen.

[0090] (((3))) One of the objectives of the present invention is to enable the combined display of the patient's account name and the patient's name each time the patient's medical record screen is displayed. The information providing method according to ((1)) or ((2)), wherein each time a message exchange display on the messaging app is received through the medical record screen, the account name of a specific patient and the name of the specific patient are combined and displayed at the display position indicating the other party of the message exchange. According to this information providing method, each time the patient's medical record screen is displayed, the patient's account name and the patient's name can be combined and displayed.

[0091] (((4))) One of the objectives of the present invention is to enable the combined display of the patient's account name and the patient's name each time the patient's medical record screen is displayed. The information providing method according to ((1)) or ((2)), wherein each time a message exchange display on the messaging app is received through the medical record screen, the name of the specific patient is added to the account name of the specific patient displayed at the display position indicating the other party of the message exchange. According to this information providing method, each time the patient's medical record screen is displayed, the patient's account name and the patient's name can be combined and displayed.

[0092] (((5))) One of the objectives of the present invention is to enable the efficiency improvement of identity verification when displaying the message exchange between the patient and the patient by the messaging app on the patient's medical record screen. The information providing system in the embodiment has one or more processors and is an information providing system that provides the patient's medical record screen to the client terminal as a cloud service. The one or more processors receive the display of the message exchange on the messaging app between a specific patient and a medical institution as an instruction for the medical record screen of the specific patient, and display the account name of the specific patient and the name of the specific patient in the area for displaying the message exchange on the messaging app on the medical record screen. According to this information providing system, it is possible to improve the efficiency of identity verification when displaying the communication with the patient by the messaging app on the medical record screen of the patient.

[0093] (((6))) One of the objects of the present invention is to enable the improvement of the efficiency of identity verification when displaying the communication with the patient by the messaging app on the medical record screen of the patient. The program in the embodiment causes the computer that provides the medical record screen of the patient as a cloud service to the client terminal to receive, as an instruction for the medical record screen of a specific patient, the display of the communication on the messaging app between the specific patient and the medical institution, and to display, in the area for displaying the communication on the messaging app on the medical record screen, the account name of the specific patient and the name of the specific patient. According to this program, it is possible to improve the efficiency of identity verification when displaying the communication with the patient by the messaging app on the medical record screen of the patient.

Description of Reference Numerals

[0094] 1... Information providing system, 10... Patient terminal, 20... Clinic terminal, 20A... Smartphone, 30... Message server, 40... Electronic medical record server

Claims

1. An information providing method for providing a patient's medical record screen to a client terminal as a cloud service, comprising: receiving, as an instruction for the medical record screen relating to a particular patient, a display of an exchange on a messaging app between the particular patient and a medical institution; A process of displaying the account name and the name of the specific patient in an area on the medical record screen that displays the exchange on the messaging app; A method of providing information having the above-mentioned features.

2. The information providing method according to claim 1 , wherein the instruction to display the exchange on the messaging app is received through a selection operation of a display item provided on the medical record screen.

3. The information providing method of claim 1 , wherein each time an exchange on the messaging app is received via the medical record screen, the account name of the specific patient is combined with the name of the specific patient and displayed in a display position indicating the other party of the exchange.

4. The information providing method of claim 1 , wherein each time a display of an exchange on the messaging app is accepted via the medical record screen, the name of the specific patient is added to the account name of the specific patient displayed in a display position indicating the other party of the exchange.

5. An information providing system having one or more processors and providing a patient's medical record screen as a cloud service to a client terminal, The one or more processors: Accepting a display of an exchange on a messaging app between the specific patient and a medical institution as an instruction for the medical record screen for the specific patient; In an area on the medical record screen that displays interactions on the messaging app, the account name of the specific patient and the name of the specific patient are displayed. Information provision system.

6. A computer that provides patient chart screens to client terminals as a cloud service. A function of accepting a display of an exchange on a messaging app between the specific patient and a medical institution as an instruction for the medical record screen regarding the specific patient; A function of displaying the account name and the name of the specific patient in an area on the medical record screen that displays interactions on the messaging app; A program to achieve this.

Images