JP7501586B2 - Medical interview reception system, medical interview reception method, and program - Google Patents

Description

The present invention relates to a medical interview reception system, a medical interview reception method, and a program, and in particular to a medical interview reception system, a medical interview reception method, and a program that utilize a network.

When a patient visits a medical institution, the patient can fill out a medical questionnaire prepared by the medical institution in advance with their symptoms and temperature, allowing the doctor to examine the patient more efficiently. For example, when a patient visits a medical institution, the medical questionnaire information can be provided to the medical institution via the network in advance, allowing the doctor to examine the patient more efficiently.

Patent Document 1 discloses technology related to a hospital reservation support system that can grasp a patient's condition to some extent before the patient visits a hospital and can make an appointment for a medical examination according to the patient's condition.

JP 2002-099615 A

As with the technology disclosed in Patent Document 1, when registering medical interview information, it is necessary to store the medical interview information in association with information on the patient who is the subject of the medical interview information. For example, when registering medical interview information using a user terminal, a patient ID can be issued using information for identifying a user such as an email address (hereinafter, user identification information), and this patient ID can be stored in association with the medical interview information.

However, the user identification information is used to identify the user himself/herself, and this user identification information cannot be used to register medical interview information of other users. For example, when the "person who operates the user terminal and inputs medical interview information" identified by the user identification information is different from the "patient" who is the subject of the interview, such as when a parent registers medical interview information for their infant, the patient ID cannot be generated using the parent's user identification information, and therefore the medical interview information cannot be registered. This poses the problem of reduced convenience for users when registering medical interview information in the medical interview reception system.

The medical interview reception system according to the present invention includes an access processing unit that receives user identification information transmitted from a user terminal and transmits access information to a medical interview registration site to the user terminal, and a medical interview reception processing unit that receives the medical interview information transmitted by the user terminal by accessing the medical interview registration site and a patient category indicating the subject of the medical interview information, and stores the medical interview information in a first storage in association with a patient ID constituted by the user identification information and the patient category.

The medical interview reception method according to the present invention receives user identification information transmitted from a user terminal, transmits access information to a medical interview information registration site to the user terminal, receives the medical interview information transmitted by the user terminal by accessing the medical interview information registration site and a patient category indicating the subject of the medical interview information, and stores the medical interview information in a storage in association with a patient ID constituted by the user identification information and the patient category.

The program of the present invention is a program for causing a computer to execute a process of receiving user identification information transmitted from a user terminal, transmitting access information to a medical interview information registration site to the user terminal, accepting medical interview information transmitted by the user terminal by accessing the medical interview information registration site and a patient classification indicating the subject of the medical interview information, and storing the medical interview information in a storage in association with a patient ID constituted by the user identification information and the patient classification.

The present invention provides a medical interview reception system, a medical interview reception method, and a program that can improve the convenience of users when registering medical interview information.

1 is a block diagram for explaining a medical inquiry reception system according to a first embodiment. 4 is a diagram for explaining an operation flow of the medical inquiry reception system according to the first embodiment. FIG. 11 is a table showing an example of user identification information, patient classification, and patient ID. 13 is a table showing an example of patient classification. FIG. 11 is a block diagram for explaining a medical interview reception system according to a second embodiment. FIG. 11 is a diagram for explaining an operation flow of the medical inquiry reception system according to the second embodiment. FIG. 11 is a diagram for explaining the operation of the medical inquiry reception system according to the second embodiment. FIG. 11 is a diagram for explaining the operation of the medical inquiry reception system according to the second embodiment. FIG. 11 is a diagram showing an example of ticket information used in the medical inquiry reception system according to the second embodiment. FIG. 13 is a diagram showing an example of a medical interview form of the medical interview reception system according to the second embodiment (basic information input screen). FIG. 13 is a diagram showing an example of a medical interview form of the medical interview reception system according to the second embodiment (detailed information input screen). FIG. 13 is a diagram showing an example of a medical interview form of the medical interview reception system according to the second embodiment (detailed information input screen). FIG. 13 is a diagram showing an example of an input content confirmation screen of the medical interview reception system according to the second embodiment. FIG. 13 is a diagram showing an example of a reservation confirmation screen of the medical interview reception system according to the second embodiment. FIG. 11 is a diagram showing an example of ticket information used in the medical inquiry reception system according to the second embodiment. FIG. 11 is a diagram showing an example of ticket information used in the medical inquiry reception system according to the second embodiment. FIG. 11 is a diagram showing an example of ticket information used in the medical inquiry reception system according to the second embodiment. FIG. 11 is a diagram showing an example of ticket information used in the medical inquiry reception system according to the second embodiment. A diagram showing the data structures of a PHR storage and a medical institution storage in the medical interview reception system according to the second embodiment. FIG. 11 is a block diagram showing a configuration example of a PHR storage and a medical institution storage of the medical inquiry reception system according to the second embodiment. FIG. 11 is a block diagram showing an example of a hardware configuration of the medical inquiry reception system according to the second embodiment.

<First embodiment>
Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
Fig. 1 is a block diagram for explaining a medical interview reception system according to a first embodiment. As shown in Fig. 1, the medical interview reception system 1 includes an access processing unit 11, a medical interview reception processing unit 12, and a storage 13. A user terminal 15 and a medical institution terminal 16 are each configured to be able to access the medical interview reception system 1. Specifically, the user terminal 15 accesses the medical interview reception system 1 to register patient interview information. Also, the medical institution terminal 16 accesses the medical interview reception system 1 to refer to the patient interview information.

The medical interview reception system 1 can be configured using, for example, a server system, a cloud system, etc. The user terminal 15 and the medical institution terminal 16 can be configured using a mobile terminal device such as a smartphone or a tablet terminal, a personal computer, etc.

Note that while FIG. 1 shows an example in which one user terminal 15 and one medical institution terminal 16 are each connected to the medical inquiry reception system 1, there may be multiple user terminals 15 and multiple medical institution terminals 16 connected to the medical inquiry reception system 1. In addition, the user terminals 15 and the medical institution terminals 16 are each connected to the medical inquiry reception system 1 via a wireless or wired network line.

The access processing unit 11 receives user identification information sent from the user terminal 15, and sends access information to the medical interview information registration site to the user terminal 15. Here, the access information to the medical interview information registration site is information about a site for inputting the patient's medical interview information using the user terminal 15. The medical interview information registration site is configured to be provided by the medical interview reception system 1 (e.g., the medical interview reception processing unit 12). The access processing unit 11 supplies the URL (Uniform Resource Locator) of the medical interview information registration site to the user terminal 15 as access information.

The medical interview reception processing unit 12 receives the medical interview information and the patient category indicating the subject of the medical interview information transmitted by the user terminal 15 by accessing the medical interview information registration site, and stores the medical interview information in the storage 13 in association with the patient ID consisting of the user identification information and the patient category. The storage 13 is configured using, for example, a hard disk drive.

Here, the user identification information is information for identifying a person who operates the user terminal 15 to input the medical interview information, and for example, an email address can be used as shown in FIG. 3. The patient category is a code indicating the patient who is the subject of the medical interview, and is a category assigned to each of multiple users (a first user and a second user). For example, as shown in FIG. 4, the patient category is selected from the categories assigned to the user himself and the user's children. The patient ID is ID information generated using the user identification information and the patient category. For example, as shown in FIG. 3, a patient ID "aaa@xxx.yyy:1" can be generated by adding the patient category "1" after the email address "aaa@xxx.yyy", which is the user identification information.

In this way, in the medical interview reception system 1 according to this embodiment, a patient ID is constructed using user identification information and patient classification. Therefore, even if the "person who operates the user terminal 15 to input medical interview information" identified by the user identification information is different from the "patient" who is the subject of the medical interview, a patient ID can be generated appropriately. For example, when an infant is examined, the mother needs to input the medical interview information. In such a case, by setting the mother's email address "aaa@xxx.yyy" as the user identification information and the patient classification to "1" (first child), a patient ID "aaa@xxx.yyy:1" indicating the patient (infant) who is the subject of the medical interview can be generated.

For example, if the mother herself visits the clinic, the mother's email address "aaa@xxx.yyy" can be used as the user identification information and the patient category can be set to "0" (herself), generating the mother's patient ID "aaa@xxx.yyy:0". In other words, a patient ID according to the patient category can be generated based on the email address, which is the user identification information.

In FIG. 3, an example is shown in which an email address is used as user identification information, but in this embodiment, the user may set any ID as user identification information. Considering the need to improve the accuracy of identity verification, it is preferable to use an email address, IC card number, credit card number, etc.

In particular, when an email address is used as the user identification information, a blank email is sent from the user terminal 15 to the access processing unit 11, and the URL of the medical interview information registration site is received from the access processing unit 11 as a reply, and the medical interview information registration site indicated by this URL is accessed. This can improve the accuracy of identity verification.

In addition, FIG. 4 shows an example in which the patient categories include the patient himself/herself, first child, second child, and third child. However, in this embodiment, the patient categories may be configured in other ways. For example, other family members, specifically spouses, grandparents, etc., may be added to the patient categories. Patient categories may also be configured with members other than family members. In this embodiment, multiple patient categories may be configured to be selectable. In this case, a patient ID is generated for each of the multiple selected patient categories. For example, if the first child and second child are selected as patient categories, two patient IDs "aaa@xxx.yyy:1" and "aaa@xxx.yyy:2" are generated, and the interview information of each patient can be registered in association with the patient ID.

Next, the operation of the medical interview reception system (medical interview reception method) according to this embodiment will be described. FIG. 2 is a diagram for explaining the operation flow of the medical interview reception system according to this embodiment. Note that the following description will be given using the user's email address as an example of user identification information.

As shown in FIG. 2, the user terminal 15 sends a blank email to the access processing unit 11 (step S1). When the access processing unit 11 receives the blank email sent from the user terminal 15, it sends the URL of the medical interview information registration site to the user terminal 15 (step S2).

Then, the user uses the user terminal 15 to access the URL of the medical history registration site and input the patient category and medical history information. The input patient category and medical history information are sent to the medical history reception processing unit 12 (step S3). The medical history reception processing unit 12 accepts the sent patient category and medical history information, associates the patient ID with the medical history information, and stores them in storage 13 (step S4). The medical institution uses the medical institution terminal 16 to check the patient ID and medical history information stored in storage 13 (step S5).

By using this flow, the user terminal 15 can access the medical interview reception system 1 to register the patient's medical interview information. Also, the medical institution terminal 16 can access the medical interview reception system 1 to refer to the patient's medical interview information.

As with the technology disclosed in Patent Document 1, when registering medical interview information, it is necessary to store the medical interview information in association with information on the patient who is the subject of the medical interview information. For example, when registering medical interview information using a user terminal, a patient ID can be generated using information for identifying a user (user identification information), such as an email address, and this patient ID can be stored in association with the medical interview information.

However, the user identification information is used to identify the user himself/herself, and this user identification information cannot be used to register medical interview information for other users. For example, when the "person who operates the user terminal and inputs the medical interview information" identified by the user identification information is different from the "patient" who is the subject of the interview, such as when a parent is registering medical interview information for their infant, the patient ID cannot be generated using the parent's user identification information, and therefore the medical interview information cannot be registered. This causes a problem in that it is less convenient for users to register medical interview information in the medical interview reception system.

In contrast, in the medical interview reception system according to this embodiment, a patient ID is generated using the user identification information and patient classification sent from the user terminal 15, and the medical interview information is stored in storage 13 in association with this patient ID. Therefore, even if the "person who operates the user terminal 15 to input the medical interview information" identified by the user identification information is different from the "patient" who is the subject of the medical interview, an appropriate patient ID can be generated, and the medical interview information can be stored in storage in association with this patient ID.

Therefore, the invention according to this embodiment can provide a medical interview reception system, a medical interview reception method, and a program that can improve the convenience of users when registering medical interview information.

<Embodiment 2>
Next, a second embodiment of the present invention will be described. In the second embodiment, a more detailed configuration of the medical interview reception system described in the first embodiment will be described. Note that in the present embodiment, the description of the parts that overlap with the first embodiment will be omitted as appropriate.

Figure 5 is a block diagram for explaining the medical interview reception system according to the second embodiment. As shown in Figure 5, the medical interview reception system 2 includes a medical interview system 20 and a reservation system 30. The medical interview system 20 includes an access processing unit 21, a medical interview reception processing unit 22, a PHR (Personal Health Records) storage 23, a medical interview submission processing unit 24, a medical institution storage 25, a medical interview reference processing unit 26, and an update processing unit 27. Here, the access processing unit 21 shown in Figure 5 corresponds to the access processing unit 11 shown in Figure 1, the medical interview reception processing unit 22 shown in Figure 5 corresponds to the medical interview reception processing unit 12 shown in Figure 1, and the PHR storage 23 and the medical institution storage 25 shown in Figure 5 correspond to the storage 13 shown in Figure 1. The reservation system 30 includes a reservation processing unit 31 and a reservation reference processing unit 32.

The user terminal 15 and the medical institution terminal 16 are each configured to be able to access the medical interview reception system 2. Specifically, the user terminal 15 accesses the medical interview reception system 2 to register the patient's medical interview information. The medical institution terminal 16 also accesses the medical interview reception system 2 to refer to the patient's medical interview information and reservation status.

The medical interview reception system 2 can be configured using, for example, a server system, a cloud system, etc. The user terminal 15 and the medical institution terminal 16 can be configured using a mobile terminal device such as a smartphone or a tablet terminal, a personal computer, etc.

Note that, although FIG. 5 shows an example in which one user terminal 15 and one medical institution terminal 16 are each connected to the medical inquiry reception system 2, there may be multiple user terminals 15 and multiple medical institution terminals 16 connected to the medical inquiry reception system 2. In addition, the user terminals 15 and the medical institution terminals 16 are each connected to the medical inquiry reception system 2 via a wireless or wired network line.

When the access processing unit 21 provided in the medical interview system 20 receives the user identification information transmitted from the user terminal 15, it transmits access information to the medical interview information registration site to the user terminal 15. Here, the access information to the medical interview information registration site is information about a site for inputting the patient's medical interview information using the user terminal 15. The medical interview information registration site is configured to be provided by the medical interview system 20 (e.g., the medical interview reception processing unit 22). The access processing unit 21 supplies the URL of the medical interview information registration site to the user terminal 15 as access information.

The medical interview reception processing unit 22 receives the medical interview information and the patient category indicating the subject of the medical interview information transmitted by the user terminal 15 by accessing the medical interview information registration site, and stores the patient ID consisting of the user identification information and the patient category in association with the medical interview information in the PHR storage 23. The medical interview reception processing unit 22 also generates ticket information. The ticket information will be described in detail later. Note that the user identification information, patient category, and patient ID are the same as those described in the first embodiment (see Figures 3 and 4), so a duplicated description will be omitted.

The PHR storage 23 stores the patient interview information in association with the patient ID. For example, the PHR storage 23 stores the interview information of a specific patient at multiple medical institutions in association with the patient ID. This allows the interview information of a specific patient to be accumulated throughout his or her life, and allows the health condition to be managed throughout his or her life. The patient can check the history of his or her interview information using the user terminal 15.

The PHR storage 23 may also store medical interview information of multiple patients in association with the patient ID of each patient. In this way, by storing medical interview information of multiple patients, a large amount of medical interview information can be stored, and the stored medical interview information data can be statistically analyzed and utilized. In this case, from the viewpoint of protecting privacy, it is preferable that each patient can only refer to information associated with their own patient ID. The PHR storage 23 is configured, for example, using a hard disk drive.

The medical interview submission processing unit 24 copies the patient ID and medical interview information stored in the PHR storage 23 to the medical institution storage 25 that can be accessed by the medical institution. At this time, the medical interview submission processing unit 24 copies the patient ID and medical interview information from the PHR storage 23 to the medical institution storage 25 using the ticket information. Note that the PHR storage 23 is configured so that it cannot be accessed by the medical institution.

The medical institution storage 25 stores the medical interview information supplied from the medical interview submission processing unit 24 in association with the patient ID. The medical institution storage 25 can store medical interview information from multiple medical institutions. The medical interview information stored in the medical institution storage 25 is assigned a medical institution code corresponding to the medical institution the patient visits. Therefore, a medical institution can retrieve from the medical institution storage 25 only the medical interview information assigned with its own medical institution code among the medical interview information from multiple medical institutions. The medical institution storage 25 is configured using, for example, a hard disk drive.

The medical history reference processing unit 26 transmits the patient ID and medical history information stored in the medical institution storage 25 to the medical institution terminal 16. This allows the medical institution to refer to the patient ID and medical history information stored in the medical institution storage 25 using the medical institution terminal 16. At this time, the medical history reference processing unit 26 transmits to the medical institution terminal 16 only the medical history information that corresponds to the medical institution code of the medical institution using the medical institution terminal 16.

The update processing unit 27 updates the patient ID stored in the PHR storage 23 and the medical institution storage 25. Specifically, when a patient visits a medical institution for the first time, the patient interview information is registered for the first time for this medical institution. In this case, since the patient number does not exist for this patient, the patient ID is generated using the user identification information and patient classification described above. The patient ID generated using the user identification information and patient classification is used to store the patient interview information in the PHR storage 23 and the medical institution storage 25. After that, after the patient's identity is confirmed at the medical institution, the medical institution inputs the patient number to the medical institution terminal 16. This input patient number is supplied to the update processing unit 27. The update processing unit 27 updates the patient ID stored in the PHR storage 23 and the medical institution storage 25, that is, the patient ID composed of the user identification information and the patient classification, to the patient number assigned by the medical institution. Thereafter, when this patient registers interview information for this medical institution, this patient number is used as the patient ID. Note that in this embodiment, when updating the patient ID, the patient ID may be linked to the patient number without deleting the patient ID.

The reservation processing unit 31 of the reservation system 30 presents reservation slot candidates to the user based on the medical interview information acquired from the medical interview reception processing unit 22, and processes the reservation slot selected by the user from the presented reservation slot candidates as a confirmed reservation slot. At this time, the reservation processing unit 31 may determine the reservation slot candidate according to the urgency determined based on the medical interview information. For example, the reservation processing unit 31 may set the urgency according to the patient's body temperature. For example, if the body temperature is 39.0°C or higher, the urgency may be set to "high", if the body temperature is 38.0°C or higher but less than 38.9°C, the urgency may be set to "medium", and if the body temperature is lower than 38.0°C, the urgency may be set to "low". In addition, if the symptoms are high urgency, such as accidental ingestion or convulsions, the urgency may be set to "high".

The reservation reference processing unit 32 transmits information about the reservation slots confirmed by the reservation processing unit 31 to the medical institution terminal 16. This allows the medical institution to use the medical institution terminal 16 to refer to the reservation slots of patients who are scheduled to be examined.

Next, the operation of the medical interview reception system (medical interview reception method) according to this embodiment will be described. FIG. 6 is a diagram for explaining the operation flow of the medical interview reception system according to this embodiment. Note that the following description will be given using the user's email address as an example of user identification information.

As shown in FIG. 6, the user terminal 15 sends a blank email to the access processing unit 21 (step S11). When the access processing unit 21 receives the blank email sent from the user terminal 15, it sends the URL of the medical interview information registration site to the user terminal 15 (step S12).

To explain this in more detail using Figure 7, for example, the user terminal 15 reads a QR code (registered trademark) 41 posted on the homepage of a medical institution, and sends a blank email to the medical institution's email address recorded in this QR code 41 (step S11). The access processing unit 21 sends the URL (42) of the medical interview information registration site to the user terminal 15 (step S12). Since the destination of the blank email is set for each medical institution, the access processing unit 21 can use the destination of the blank email, i.e., the email address of the medical institution, to identify the medical institution that the user will visit.

As shown in FIG. 6, the user then uses the user terminal 15 to access the URL of the medical interview information registration site and inputs patient information including the patient classification. The input patient information is sent to the medical interview reception processing unit 22 (step S13). When the patient information is provided, the medical interview reception processing unit 22 generates ticket information (step S14).

To explain this in more detail using FIG. 8, for example, when the URL of the medical interview information registration site is accessed using the user terminal 15, a patient information input screen 45 is displayed on the user terminal 15. The user enters the patient's relationship to the patient, date of birth, and gender, and transmits this patient information to the medical interview reception processing unit 22 (step S13). If this is the patient's first visit to a medical institution, the patient card number is left blank.

When the patient information is provided, the medical interview reception processing unit 22 generates ticket information (step S14). Here, the ticket information is information used when the medical interview submission processing unit 24 copies the patient ID and medical interview information from the PHR storage 23 to the medical institution storage 25, and includes the patient ID, which is source information, and medical institution information, which is destination information.

Figure 9 is a diagram showing an example of ticket information. As shown in Figure 9, the ticket information has the following fields: ticket issue number, issuer code, issuer patient number, issuer response number, destination code, destination patient number, and destination response number.

The ticket issue number is a serial number assigned when the medical interview reception processing unit 22 generates ticket information. The issuer code is a code indicating the issuer of the medical interview information, and "9999" indicates that the issuer is the PHR storage 23. The issuer patient number is a patient ID consisting of user identification information and patient classification, and if the user identification information is an email address, it will be the character string "aaa@xxx.yyy:1" in which the patient classification is added to the email address as shown in Figure 9. The issuer response number is a number assigned when the medical interview information is input.

The destination code is the identification code of the selected medical institution, in other words, the identification code of the medical institution where the patient will be treated. This medical institution identification code is the identification code of the medical institution that corresponds to the destination email address when the user sends a blank email. The destination patient number is a patient ID consisting of user identification information and patient classification, and if the user identification information is an email address, it will be the character string "aaa@xxx.yyy:1" in which the patient classification is added to the email address as shown in Figure 9. The destination response number is a number that is assigned when the medical interview information is copied from the PHR storage 23 to the medical institution storage 25. The ticket information is used during the medical interview submission process in step S25 shown in Figure 6. This process will be described later.

As shown in FIG. 6, the medical interview reception processing unit 22 transmits the medical interview form to the user terminal 15 (step S15). After that, the user inputs the patient's medical interview information into the medical interview form using the user terminal 15 (step S16).

For example, medical interview information includes (1) basic information, (2) profile information, and (3) current information. Basic information is basic information such as the patient's date of birth and gender. Profile information is past facts such as the patient's allergies and vaccination history. Current information is information such as weight, current body temperature, reason for visit, etc.

Figure 10 is a diagram showing an example of a medical interview form, and shows an example of a basic information input screen. As shown in Figure 10, the basic information input screen has columns for the medical interview items: date of birth, gender, weight, respondent, current body temperature, highest body temperature, and time when fever started, and the user enters the details of the medical interview in these columns. Here, date of birth and gender correspond to basic information, and weight, current body temperature, highest body temperature, and time when fever started correspond to current information.

Figures 11 and 12 are diagrams showing an example of a medical interview form and an example of a detailed information input screen. The detailed information input screen shown in Figure 11 is configured so that medical interview content (current information) can be entered for each symptom, such as drowning, burns, bruises, sprains, etc. Also, the detailed information input screen shown in Figure 12 is configured so that medical interview content can be entered for each body part shown on the screen. Note that these medical interview forms are only examples, and other medical interview forms may be used in the medical interview reception system according to this embodiment.

In addition, when the medical interview reception processing unit 22 sends the medical interview form to the user terminal 15 in step S15 of FIG. 6, if this is the second or subsequent time that the patient's medical interview information is being registered, the input of the basic information and profile information, which are common items, can be omitted.

In other words, when patient information is sent from the user terminal 15 (step S13), the medical interview reception processing unit 22 can identify whether this is the patient's first visit or the second or subsequent visit. If the patient is visiting for the first time, the medical interview reception processing unit 22 sends to the user terminal 15 a medical interview form into which medical interview information including basic information, profile information, and current information can be entered (step S15). On the other hand, if the patient is visiting for the second or subsequent visit, the medical interview reception processing unit 22 sends to the user terminal 15 a medical interview form that reflects the previous input values of the basic information and profile information, which are common items (step S15).

After the user inputs the patient's medical history information into the medical history form, the user terminal 15 requests a reservation slot from the reservation system 30 (step S17). Specifically, the user terminal 15 shown in FIG. 5 transmits the medical history information to the medical history reception processing unit 22. The medical history reception processing unit 22 transmits the medical history information transmitted from the user terminal 15 to the reservation processing unit 31. The reservation processing unit 31 then determines a candidate reservation slot based on the availability of the medical institution where the patient is scheduled to be examined and the medical history information acquired from the medical history reception processing unit 22. At this time, the reservation processing unit 31 may determine the candidate reservation slot according to the urgency determined based on the medical history information. For example, the reservation processing unit 31 may set the urgency according to the patient's body temperature.

Then, the appointment processing unit 31 presents the appointment slot candidates to the user terminal 15 via the medical interview reception processing unit 22 (step S18). Figure 13 is a diagram showing an example of an input content confirmation screen of the medical interview reception system. A number of appointment slot candidates 46 are displayed on the input content confirmation screen shown in Figure 13, and the user selects an appointment slot from the appointment slot candidates and confirms the appointment slot (step S19).

Then, the user terminal 15 transmits the medical inquiry information input by the user to the medical inquiry reception processing unit 22 (step S20). The user terminal 15 also transmits the confirmed reservation slot to the reservation processing unit 31 via the medical inquiry reception processing unit 22 (step S21). Specifically, the user terminal 15 transmits the confirmed reservation slot to the medical inquiry reception processing unit 22. The medical inquiry reception processing unit 22 then transmits the confirmed reservation slot to the reservation processing unit 31.

When the medical interview reception processing unit 22 receives the medical interview information and the reservation slot from the user terminal 15, it transmits a registration confirmation notification to the user terminal 15 (step S22). As a result, a confirmation screen is displayed on the user terminal 15, showing the reservation date and time 48 and the medical interview content 49 as shown in FIG. 14.

The medical interview reception processing unit 22 also stores the patient ID and medical interview information in the PHR storage 23 (step S23). As a result, the patient ID and medical interview information are stored in the PHR storage 23 (step S24). When storing the patient ID and medical interview information in the PHR storage 23, the medical interview reception processing unit 22 assigns a new issuer response number of the ticket information as shown in FIG. 15. In FIG. 15, the issuer response number is "100". Here, the issuer response number of the ticket information is a number for identifying the medical interview information stored in the PHR storage 23.

Then, the medical interview submission processing unit 24 copies the patient ID and medical interview information stored in the PHR storage 23 to the medical institution storage 25 (step S25: medical interview submission processing). As a result, the patient ID and medical interview information are stored in the medical institution storage 25 (step S26). At this time, the medical interview submission processing unit 24 copies the patient ID and medical interview information from the PHR storage 23 to the medical institution storage 25 using the ticket information. In other words, the medical institution storage 25 corresponding to the medical institution where the patient will be examined is identified by the "issuance destination code" of the ticket information (see the issue destination code "0001" in FIG. 15), and the medical interview submission processing unit 24 copies the patient ID and medical interview information to the medical institution storage 25 corresponding to this issue destination code. The "issue destination code" of this ticket information is assigned by the user sending a blank email to the address of the blank email destination set for each medical institution. The ticket information is supplied from the medical interview reception processing unit 22 to the medical interview submission processing unit 24.

When storing the patient ID and medical interview information in the medical institution storage 25, the medical interview submission processing unit 24 assigns a new ticket information issuer response number as shown in FIG. 16. In FIG. 16, the issuer response number is "101." Here, the ticket information issuer response number is a number for identifying the medical interview information stored in the medical institution storage 25.

Then, in response to a request from the medical institution terminal 16, the medical history reference processing unit 26 transmits the patient ID and medical history information stored in the medical institution storage 25 to the medical institution terminal 16 (step S27: medical history reference processing). This allows the medical institution to refer to the patient ID and medical history information stored in the medical institution storage 25 using the medical institution terminal 16 (step S28).

In addition, in response to a request from the medical institution terminal 16, the reservation reference processing unit 32 transmits information regarding the reservation slots confirmed by the reservation processing unit 31 to the medical institution terminal 16 (step S29: reservation reference processing). This allows the medical institution to use the medical institution terminal 16 to refer to the reservation slots of patients who are scheduled to be examined (step S30). For example, the medical institution can use the medical institution terminal 16 to check the reservation slots for the day.

When a patient visits a medical institution for the first time, once the patient visits the medical institution and the medical institution has confirmed the patient's identity, a medical institution staff member (e.g., a doctor) confirms the patient number using the medical institution terminal 16 (step S31).

When the patient number is confirmed in step S31 of FIG. 6, the update processing unit 27 updates the patient ID stored in the PHR storage 23 and the medical institution storage 25 (step S32). That is, when the patient visits a medical institution for the first time, the patient ID stored in the PHR storage 23 and the medical institution storage 25 is a patient ID (e.g., "aaa@xxx.yyy:1") generated using the user identification information (email address) and the patient classification. The update processing unit 27 updates this patient ID stored in the PHR storage 23 and the medical institution storage 25 to a patient number (e.g., "12345") assigned by the medical institution. FIG. 17 shows an example of ticket information after the patient ID has been updated to the patient number ("12345"). Thereafter, when this patient registers interview information for this medical institution, this patient number is used as the patient ID.

Note that if the patient has visited a medical institution in the past, i.e., if a patient number already exists, steps S31 to S32 in Figure 6 are skipped.

Next, we will explain the operation flow when a patient visits a medical institution that he or she has visited before. As shown in Figure 6, the user terminal 15 sends a blank email to the access processing unit 21 (step S11). When the access processing unit 21 receives the blank email sent from the user terminal 15, it sends the URL of a medical interview information registration site to the user terminal 15 (step S12).

Then, the user uses the user terminal 15 to access the URL of the medical interview information registration site and inputs patient information including the patient classification. The input patient information is sent to the medical interview reception processing unit 22 (step S13). The medical interview reception processing unit 22 then generates a patient ID (aaa@xxx.yyy:1) consisting of the user identification information and the patient classification. Here, if the patient has previously visited a medical institution (issuer code "0001"), ticket information such as that shown in FIG. 18 already exists. In this case, the patient ID (aaa@xxx.yyy:1) generated by the medical interview reception processing unit 22 matches the "issuer patient number" of the already existing ticket information, so the issuer patient number "12345" is used as the patient ID.

The subsequent operational flow, i.e., steps S15 to S30 shown in FIG. 6, is the same as that described above, so duplicate explanations will be omitted.

When the update processing unit 27 updates the patient ID stored in the PHR storage 23 and medical institution storage 25 in step S32, the "recipient patient number" of the ticket information is also updated to the patient number "12345" assigned by the medical institution, as shown in FIG. 18. However, the "issuer patient number" is not updated to the patient number assigned by the medical institution, but is set to the patient ID (aaa@xxx.yyy:1) consisting of user identification information and patient classification. This is because, as explained above, the "issuer patient number" (aaa@xxx.yyy:1) is used to check whether the same patient has visited the same medical institution before, that is, whether ticket information already exists.

Next, the data structures of the PHR storage 23 and medical institution storage 25 in the medical interview reception system according to this embodiment will be described with reference to FIG. 19. As shown in FIG. 19, the PHR storage 23 and medical institution storage 25 each have a basic information table 51 and a medical interview table 52 as data tables. The basic information table 51 is a table that stores basic information about a patient. The medical interview table 52 is a table that stores medical interview information, that is, the specific contents of a patient's medical interview.

The basic information table 51 has fields for ID number, response date, medical institution code, patient ID, and medical interview response code. The medical interview table 52 has fields for medical interview response code, birthday, height, weight, gender, and medical interview response (multiple). The basic information table 51 and the medical interview table 52 have a one-to-one relationship, and each table is linked to each other using the medical interview response code as a key. The medical interview response code, birthday, and gender in the medical interview table 52 correspond to the basic information of the medical interview information.

When the medical institution code in the basic information table 51 is stored in the PHR storage 23, it is a code indicating the PHR storage 23 (e.g., "9999"), which corresponds to the issuer code of the ticket information. When the medical institution code is stored in the medical institution storage 25, it is a code indicating the medical institution where the patient will be treated (e.g., "0001"), which corresponds to the issuer code of the ticket information.

The patient ID in the basic information table 51 is a patient ID consisting of an email address and a patient category (e.g., "aaa@xxx.yyy:1") when a new patient is registered, and is a patient number (e.g., "12345") when a patient number has already been assigned by the medical institution. When the update process is performed in step S32 of FIG. 6, the patient ID in the basic information table 51 (e.g., "aaa@xxx.yyy:1") is updated to the patient number assigned by the medical institution (e.g., "12345").

Next, a configuration example of the PHR storage 23 and medical institution storage 25 of the medical interview reception system according to this embodiment will be described with reference to the block diagram shown in FIG. 20. FIG. 20 shows a case where multiple patients and multiple medical institutions access the medical interview reception system. As shown in FIG. 20, the PHR storage 23 includes a patient data area A accessible to patient A, a patient data area B accessible to patient B, and a patient data area C accessible to patient C. Here, each of the patient data areas A to C may be physically separated by using different hard disk drives, or may be separated by software by using the same hard disk drive. When each of the patient data areas A to C is separated by software, the data can be separated by using, for example, the "patient ID" in the basic information table 51 shown in FIG. 19.

In this way, the security level of the medical interview reception system can be maintained by limiting the patient data area that each patient can access. In addition, since the medical interview information of multiple patients A to C is stored in PHR storage 23 in association with each patient's patient ID, the accumulated medical interview information data can be statistically analyzed and utilized. In this case, since no personal information of patients is stored in PHR storage 23, the patient's privacy can be protected while the patient's medical interview information can be utilized.

As shown in FIG. 20, the medical institution storage 25 includes a medical institution data area A accessible by medical institution A, a medical institution data area B accessible by medical institution B, and a medical institution data area C accessible by medical institution C. Here, each of the medical institution data areas A to C may be configured using different hard disk drives and be physically separated, or may be configured using the same hard disk drive and be separated by software. When each of the medical institution data areas A to C is separated by software, the data can be separated, for example, by using the "medical institution code" in the basic information table 51 shown in FIG. 19. In this way, the security level of the medical interview reception system can be maintained by limiting the medical institution data areas that each medical institution can access.

In the medical interview reception system 2 according to this embodiment, a patient ID is generated using the user identification information and patient classification sent from the user terminal 15, and the medical interview information is stored in the PHR storage 23 and the medical institution storage 25 in association with this patient ID. Therefore, even if the "person who operates the user terminal 15 to input the medical interview information" identified by the user identification information is different from the "patient" who is the subject of the medical interview, an appropriate patient ID can be generated, and the medical interview information can be stored in storage in association with this patient ID. Therefore, the invention according to this embodiment can provide a medical interview reception system that can improve the convenience for users when registering medical interview information.

In addition, medical institutions can accept medical interview information from new patients who do not have patient numbers. Furthermore, patients can register medical interview information using only user identification information (e.g., email address) without managing patient numbers. Furthermore, patients can manage their lifetime records using user identification information (e.g., email address), which is a single ID. Furthermore, if a patient ID (ticket information) has already been created, medical interview information previously registered can be displayed, thereby reducing the time required to register medical interview information. Furthermore, by using the medical interview reception system according to this embodiment at multiple medical institutions, medical interview information from multiple medical institutions can be accumulated in the medical interview reception system, and this accumulated medical interview information can be effectively utilized.

Next, an example of the hardware configuration of the medical interview reception systems 1 and 2 according to the first and second embodiments will be described with reference to the block diagram shown in FIG. 21. The medical interview reception systems 1 and 2 can be configured using, for example, a server system, a cloud system, etc.

The medical inquiry reception systems 1 and 2 include a network interface 101, a processor 102, a memory 103, and a storage 104. The network interface 101 is an interface for communicating with a user terminal 15 and a medical institution terminal 16.

The processor 102 reads out and executes software (computer programs) stored in the memory 103 to perform the processes described above in FIGS. 1 and 2 of the first embodiment and FIGS. 5 and 6 of the second embodiment. The processor 102 can be configured using, for example, a microprocessor, an MPU (Micro Processing Unit), or a CPU (Central Processing Unit). The processor 102 may include multiple processors.

The memory 103 stores software (computer programs) executed by the processor 102. The memory 103 can be configured, for example, as a volatile memory, a non-volatile memory, or a combination of these. For example, a static random access memory (SRAM) or a dynamic random access memory (DRAM) can be used as the volatile memory. For example, a flash memory can be used as the non-volatile memory.

Storage 104 corresponds to storage 13 shown in FIG. 1, PHR storage 23 shown in FIG. 5, and medical institution storage 25, and stores patient IDs and medical interview information. Storage 104 can be configured using, for example, a hard disk drive.

The present invention has been described above in accordance with the above embodiment, but the present invention is not limited to the configuration of the above embodiment, and of course includes various modifications, alterations, and combinations that a person skilled in the art could make within the scope of the invention of the claims of this patent application.

(Appendix 1)
an access processing unit that receives user identification information transmitted from a user terminal and transmits access information to the user terminal for accessing a medical interview information registration site;
a medical interview reception processing unit that receives the medical interview information and a patient category indicating a subject of the medical interview information transmitted by the user terminal through access to the medical interview information registration site, and stores the medical interview information in a first storage in association with a patient ID constituted by the user identification information and the patient category.
Medical enquiry reception system.

(Appendix 2)
The medical interview reception system described in Appendix 1, wherein the user identification information is a user's email address.

(Appendix 3)
3. The medical interview reception system according to claim 1, wherein the patient category is at least one category selected from categories assigned to a first user and a second user, respectively.

(Appendix 4)
the access processing unit has a destination address of the user identification information for each medical institution;
the medical interview reception processing unit stores the medical interview information in the first storage in association with a medical institution corresponding to an address to which the user terminal has transmitted the user identification information;
4. The medical interview reception system according to any one of claims 1 to 3.

(Appendix 5)
5. The medical interview reception system according to claim 1, wherein the first storage stores medical interview information of the patient at a plurality of medical institutions in association with the patient ID.

(Appendix 6)
a medical interview submission processing unit that copies the patient ID and the medical interview information stored in the first storage to a second storage,
the first storage is configured to be inaccessible to a medical institution, and the second storage is configured to be accessible to the medical institution;
the medical interview submission processing unit copies the patient ID and the medical interview information from the first storage to the second storage by using ticket information including a patient ID as source information and medical institution information as destination information;
An inquiry reception system according to any one of appendix 1 to 5.

(Appendix 7)
The medical interview reception system described in Appendix 6, further comprising a medical interview reference processing unit for referring to the patient ID and the medical interview information stored in the second storage using a medical institution terminal.

(Appendix 8)
8. The medical interview reception system according to claim 6 or 7, further comprising an update processing unit that updates the patient ID stored in the first and second storages to a patient number assigned by the medical institution.

(Appendix 9)
The medical inquiry reception system further includes a reservation processing unit,
The reservation processing unit:
presenting reservation slot candidates to the user based on the medical interview information;
A reservation slot selected by the user from the presented reservation slot candidates is treated as a confirmed reservation slot.
An inquiry reception system according to any one of appendix 1 to 8.

(Appendix 10)
The medical interview reception system according to claim 9, wherein the reservation processing unit determines the reservation slot candidates according to a degree of urgency determined based on the medical interview information.

(Appendix 11)
The medical inquiry reception system according to claim 9 or 10, further comprising a reservation reference processing unit for referring to the reservation slot confirmed by the reservation processing unit using a medical institution terminal.

(Appendix 12)
receiving user identification information transmitted from a user terminal, and transmitting access information to the user terminal for accessing a medical interview information registration site;
receiving the medical interview information and a patient category indicating a subject of the medical interview information transmitted by the user terminal through access to the medical interview information registration site, and storing the medical interview information in a storage in association with a patient ID constituted by the user identification information and the patient category;
How to receive an interview.

(Appendix 13)
receiving user identification information transmitted from a user terminal, and transmitting access information to the user terminal for accessing a medical interview information registration site;
receiving the medical interview information and a patient category indicating a subject of the medical interview information transmitted by the user terminal through access to the medical interview information registration site, and storing the medical interview information in a storage in association with a patient ID constituted by the user identification information and the patient category;
A program that causes a computer to execute a process.

Reference Signs List 1, 2 Medical inquiry reception system 11 Access processing unit 12 Medical inquiry reception processing unit 13 Storage 15 User terminal 16 Medical institution terminal 20 Medical inquiry system 21 Access processing unit 22 Medical inquiry reception processing unit 23 PHR storage 24 Medical inquiry submission processing unit 25 Medical institution storage 26 Medical inquiry reference processing unit 27 Update processing unit 30 Reservation system 31 Reservation processing unit 32 Reservation reference processing unit

Claims (5)

A means for generating ticket information for storing information for identifying a patient and interview information in association with each other;
A means for acquiring the medical interview information inputted into the medical interview form from a user terminal;
a means for storing the patient identification information and the interview information in association with each other in a medical institution storage accessible from the medical institution;
A means for receiving a request from a medical institution terminal of the medical institution;
a means for transmitting the medical interview information from the medical institution storage to the medical institution terminal when a request from the medical institution terminal is received,
The ticket information includes a medical institution identification code and a patient number for identifying the medical institution,
The means for storing the information for identifying the patient and the interview information in association with each other refers to the patient number, and stores the information for identifying the patient and the interview information in association with each other;
The means for transmitting the medical interview information from the medical institution storage to the medical institution terminal is configured to refer to the medical institution identification code and transmit the medical interview information corresponding to the medical institution identification code among the medical interview information stored in the medical institution storage ,
The patient number is updated to a patient number assigned by the medical institution when the patient first visits the medical institution in response to a request from the medical institution terminal.
Medical enquiry reception system. The medical inquiry reception system according to claim 1, wherein the ticket information is generated in response to a request from the user terminal. The information for identifying the patient includes user identification information and a patient classification,
the user identification information is a user's email address,
The medical institution identification code is an identification code of a medical institution corresponding to a destination email address when the user sends a blank email from the user terminal.
The medical inquiry reception system according to claim 2. A means for generating ticket information for storing information for identifying a patient and interview information in association with each other;
A means for acquiring the medical interview information inputted into the medical interview form from a user terminal;
a means for storing the patient identification information and the interview information in association with each other in a medical institution storage accessible from the medical institution;
A means for receiving a request from a medical institution terminal of the medical institution;
a means for transmitting the medical interview information from the medical institution storage to the medical institution terminal when a request from the medical institution terminal is received,
The ticket information includes a medical institution identification code and a patient number for identifying the medical institution,
The means for storing the information for identifying the patient and the interview information in association with each other refers to the patient number, and stores the information for identifying the patient and the interview information in association with each other;
The means for transmitting the medical interview information from the medical institution storage to the medical institution terminal is configured to refer to the medical institution identification code and transmit the medical interview information corresponding to the medical institution identification code among the medical interview information stored in the medical institution storage ,
The patient number is updated to a patient number assigned by the medical institution when the patient first visits the medical institution in response to a request from the medical institution terminal.
Medical interview reception device. The computer
generating ticket information for storing information for identifying a patient and interview information in association with each other;
Acquire the medical interview information inputted into the medical interview form from a user terminal;
storing the patient identification information and the interview information in association with each other in a medical institution storage accessible from the medical institution;
Accepting a request from a medical institution terminal of the medical institution;
When a request from the medical institution terminal is received, the medical interview information is transmitted from the medical institution storage to the medical institution terminal;
The ticket information includes a medical institution identification code and a patient number for identifying the medical institution,
When storing the information for identifying the patient and the interview information in association with each other, the patient number is referenced to store the information for identifying the patient and the interview information in association with each other;
When transmitting the medical interview information from the medical institution storage to the medical institution terminal, the medical institution identification code is referenced, and the medical interview information stored in the medical institution storage that corresponds to the medical institution identification code is transmitted ;
The patient number is updated to a patient number assigned by the medical institution when the patient first visits the medical institution in response to a request from the medical institution terminal.
How to receive an interview.

Images