JP2001344344A - Individual health information retrieval system and its retrieval method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To acquire information of identity check, clinical record, record of medical treatment, etc., even when it is difficult to establish the identity of a person, without having to use the medium of card, etc. SOLUTION: Fingerprint data of a patient is detected using a terminal 11. A CPU 14 makes a fingerprint collating unit 12 collate via a network 16, the fingerprint data with databases in a database server 13 and a hospital 15, so as to acquire the objective individual health information.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a personal health information search system and a search method therefor, and more particularly to a personal health information search system and a search method for searching for personal health information via a network such as the Internet.

[0002]

2. Description of the Related Art When diagnosing a patient in a medical institution such as a hospital, it may be necessary to collect information on the patient's past medical history, treatment history, and the like. If information such as the patient's past medical history and medical treatment history exists in the medical institution such as the hospital, there is no problem because it can be referred to.

[0003]

On the other hand, when there is no information such as the patient's past medical history and medical treatment history in the medical institution such as the hospital, it is difficult to obtain such information. It is also difficult to obtain such information when a suddenly sick person occurs outside a medical institution such as a hospital or when an injured person occurs due to a traffic accident or the like. Further, when it is difficult for the suddenly ill person to know his / her identity directly to the other party, such as unconsciousness, it is difficult even to confirm the identity.

[0004] On the other hand, Japanese Patent Laid-Open No. Hei 10-1998 discloses a technology capable of confirming the identity and acquiring information such as medical history and treatment history even when the identity of the person is difficult to confirm due to unknown consciousness.
It is disclosed in JP-A-334165. This is because the rescue worker reads both the patient's citizen card and the rescue worker's card into the terminal, so that information such as the patient's medical history and treatment history can be obtained from the disaster prevention system server via the communication line. That is. However, in this case, both the paramedics and the patient need to have the specific card.

[0005] As described above, if it is not possible to immediately obtain information on the patient's past medical histories and medical treatment histories even if the patient is to be treated, the response is undesirably delayed. Also, if the patient has an infectious disease, there is a risk that the patient will be infected.

Accordingly, an object of the present invention is to provide a personal health information which can be used to confirm the identity of a person and to obtain information such as medical history and treatment history without using a medium such as a card even when the identity of the person is difficult. A search system and a search method thereof are provided.

[0007]

SUMMARY OF THE INVENTION In order to solve the above-mentioned problems, the present invention is directed to an identification data ingesting means for ingesting unique identification data from a part of a patient's body, and a personal health of a plurality of patients. The database is accessed via a network based on the database in which information is stored and the unique identification data ingested by the identification data ingesting means, and the unique database is accessed. Personal health information acquiring means for acquiring personal health information corresponding to the identification data.

Another invention according to the present invention provides an identification data ingesting step of ingesting unique identification data from a part of a patient's body, and a network based on the ingested unique identification data. Acquiring a personal health information corresponding to the unique identification data by accessing a database in which personal health information of a plurality of patients is stored via a personal computer. It is characterized by.

According to the present invention and other inventions according to the present invention, unique identification data is taken from a part of a patient's body,
Since the database is accessed based on the unique identification data to acquire personal health information, even if it is difficult to confirm the identity of the individual, the identity can be confirmed and the medical history, treatment history, etc. Can be obtained without using a medium such as a card.

[0010]

Embodiments of the present invention will be described below with reference to the accompanying drawings. First, a first embodiment will be described. FIG. 1 is a configuration diagram of the first embodiment. Referring to FIG. 1, the personal health information search system 1 includes a terminal 11, a fingerprint collation device 12, a database server 13, a CPU (central processing unit) 14, and a plurality of hospitals 15-1 to 15-N (N Is an integer of 2 or more),
Network 1 such as the Internet to which these are connected
6

Here, the CPU 14 determines the fingerprint collation device 12, the database server 13,
The hospitals 15-1 to 15-N are controlled. In the present embodiment, the terminal 11 is provided outside the hospitals 15-1 to 15-N, but may be provided inside the hospitals 15-1 to 15-N.

Next, a specific configuration of the system 1 will be described. FIG. 2 is a specific configuration diagram of the personal health information search system 1. The terminal 11 includes a fingerprint receiving terminal 20. With reference to FIG.
The digital camera 21 includes a digital camera 21 for recording a face photograph as data, and a live scanner 22 for directly taking in a fingerprint image and converting it into binary data. As described above, in the present invention, since the identity is confirmed by ingesting the fingerprint, the identity can be confirmed even when it is difficult for the person to directly communicate his / her own identity to the other party due to unconsciousness or the like.

The fingerprint ingesting device 20 is well known, and is disclosed in, for example, Japanese Patent No. 1289457 "pattern feature extracting device" and Japanese Patent No. 1472346 "feature point extracting device".

Next, the fingerprint collation device 12 collates the collation application 31 with an FMP (Fingerprint Ma
and a FMP database 33. The collation application 31 receives an instruction from the application program 71 described separately, transfers the instruction to the FMP 32, and converts the instruction stored in the FMP database into the instruction of the application 71 from the database stored in the FMP database. This is software for extracting relevant items and outputting the results to the terminal 11. The FMP 32 is hardware for performing fingerprint collation. The FMP database 33 is a database described later. This FMP32 is known,
For example, Applicant's Patent No. 1468842 “Fingerprint collation device”, Patent No. 1476134 “Fingerprint collation device” and US Pat. No. 4,646,352 “Method and and”.
device for matching fing
erprint with precision mini
tia pairs selected from c
oors pairs ".

Next, the FMP database 33 will be described. FIG. 3 is a configuration diagram of the FMP database 33. Referring to the figure, in the FMP database 33, fingerprint data (binary data) A, B,..., X, names and face pictures, gender, date of birth, Stored in association with personal attributes.

Next, the database server 13 will be described. Referring back to FIG. 2, the database server 13 includes a database 41 and a database module 42. The database 41 includes fingerprint data 43 and hospital name data 44, details of which will be described later. The database module 42 receives an instruction from an application program described later and extracts a database corresponding to the instruction of the application program 71 from the database stored in the database 41.

Next, the database 41 will be described. FIG. 4 is a configuration diagram of the database 41. Referring to the figure, the database 41 stores information indicating which hospital stores personal data of a registrant. That is, fingerprint data (binary data) A, B,..., X and hospital names a, b,.
By using this database 41, it is possible to know in which hospital the personal data of the owner of the fingerprint that has been taken exists. This takes into account the case where personal data cannot be directly transferred between hospitals.

Next, the hospitals 15-1 to 15-N will be described. Referring to FIG. 2, each of the hospitals 15-1 to 15-1
-N is personal data 51a, 51b,.
Is stored. FIG. 5 shows the configuration of personal data stored for each hospital. The figure shows an example of a hospital 15-
1 (hospital name a) is shown.
That is, the personal data is the same as the data stored in the FMP database such as fingerprint data (binary data), face photograph data, name data, gender data, and date of birth. In addition to important information, it is composed of hospital-specific data such as medical history.

Next, an application database 61 is shown.
Will be described. This stores a database for selecting and taking out necessary items from personal data. For example, if data for the purpose of nursing care is required, gender and medical history are selected as items to be taken out when "care" is selected in this database, and data that must be known in advance when nursing care is taken. Can be taken out. On the other hand, when the data for the purpose of emergency is required, selecting "Emergency" in this database selects the name and blood type (included in "Others" in FIG. 5) as items to be taken out. When treating, it is possible to extract data that needs to be known in advance. The same applies to other than "care" and "emergency".

Next, the application program 71 will be described. This is a program which the CPU 14 has. The CPU 14 according to the program 71, the fingerprint collating device 12, the database server 13, the hospitals 15-1 to 15-15.
-N is controlled. Hereinafter, the operation of the CPU 14 will be described. FIG. 6 is a flowchart showing the operation of the CPU 14.

First, a fingerprint of a patient is taken by the terminal 11 using the fingerprint taking device 20 (S1). Next, the fingerprint data is sent from the terminal 11 via the network 16 to the CPU.
14 is transmitted. When the CPU 14 receives the transmitted fingerprint data, the fingerprint data is collated by the fingerprint collation device 12 via the network 16. Fingerprint collation device 1
2 compares the fingerprint data with the fingerprint data in the FMP database 33 (S2). If there is fingerprint data matching the FMP database 33, the fingerprint data is registered (Y in S2). When the CPU 14 receives the notification of "registered" from the fingerprint collation device 12, the CPU 14 searches the database server 13 via the network 16 (S3). That is, the terminal 11
The personal data storage location (hospital name) is searched based on the fingerprint data received from. If the name of the hospital at the storage location is found (Y at S4), the CPU 14 searches for personal data of the hospital based on the fingerprint data received from the terminal 11 via the network 16 (S5). . Then, the personal data of the patient having the fingerprint is obtained (S6). At this time, the CPU 14 operates as an application data base 61.
To select a necessary item from the personal data, and acquire only the data of the necessary item. Of course, when the data of all the items of the personal data is required, it is not necessary to search the application database 61, and the data of all the items may be obtained.

On the other hand, if no registration has been made in step 2 or if there is no corresponding hospital in step 4, the CPU 1
4 ends the process.

Next, a second embodiment will be described. FIG. 7 is a configuration diagram of the second embodiment. In the figure, components that are the same as the components of the first embodiment (see FIG. 1) are assigned the same reference numerals, and descriptions thereof are omitted. The configuration of the personal health information search system 2 in the second embodiment is different from that of the first embodiment in that the database server 13 and the hospitals 15-1 to 15-N are replaced with a database. The point where the server 18 is connected to the network 16; Others are the same as in the first embodiment. Here, the CPU 14 controls the fingerprint collation device 12 and the database server 18 based on information from the terminal 11.

Next, a specific configuration of the system 2 will be described. FIG. 8 is a specific configuration diagram of the personal health information search system 2. In the figure, the same components as those in the specific configuration of the first embodiment (see FIG. 2) are denoted by the same reference numerals, and description thereof is omitted. The specific configuration of the personal health information search system 2 according to the second embodiment is different from that of the first embodiment in that it is a database server.
The contents of the database of the server 18 are stored in the database server 13.
And that the personal data for each hospital was deleted, and that the application program 72
Is different from the contents of the application program 71. Others are the same as the specific configuration of the first embodiment.

Next, the database 49 stored in the database server 18 will be described. Database 4
Reference numeral 9 includes photograph data 46, fingerprint data 43, and feature point data 47. FIG. 9 is a configuration diagram of the database 49. Referring to FIG. 11, the database 49 stores personal data of registrants at each hospital in a state where the personal data can be viewed. That is, fingerprint data (binary data) A, B,..., X and photograph data (for example, face photograph data) 46 of a person having the fingerprint, name, gender, date of birth, FMP data In addition to the same information as the data stored in the database, hospital-specific data such as medical history, hospital name, and other data are stored as personal data. This database 4
By using the terminal 9, the personal data of the owner of the ingested fingerprint can be obtained at the terminal 11 without asking which hospital the personal data exists. However, this is based on the premise that personal data can be exchanged directly between hospitals.

Next, the application program 72 will be described. This is a program of the CPU 14, which controls the fingerprint collation device 12 and the database server 18 according to the program 72. Hereinafter, C
The operation of the PU 14 will be described. FIG. 10 is a flowchart showing the operation of the CPU 14 in the second embodiment.

First, a fingerprint of a patient is taken by the terminal 11 using the fingerprint taking device 20 (S11). Next, the fingerprint data is transmitted from the terminal 11 via the network 16 to the CP.
Sent to U14. Upon receiving the transmitted fingerprint data, the CPU 14 transmits the fingerprint data to the network 16.
Through the fingerprint collation device 12. The fingerprint collation device 12 collates the fingerprint data with the fingerprint data in the FMP database 33 (S12). If there is fingerprint data that matches the FMP database 33, the fingerprint data is registered (Y in S12). CPU 14 informs fingerprint registration device 12 that "registered"
Is received, the CPU 14 searches the database server 18 via the network 16 (S13). That is,
The database 49 is searched based on the fingerprint data received from the terminal 11. Then, the personal data of the patient having the fingerprint is obtained (S14). At that time, the CPU 14 searches the application database 61 to select a necessary item from the personal data, and acquires only the data of the necessary item. However, the data of all items of personal data
When data is required, there is no need to search the application database 61, and data of all items may be obtained. On the other hand, if it is not registered in step 12,
The PU 14 ends the processing.

In the above description of the first and second embodiments, the fingerprint collation device 12 and the CPU 14 are provided separately.
May be included. Also, in the operation of the CPU 14, after ingesting the fingerprint of the patient, it is determined whether or not the fingerprint has been registered (step 2 in FIG. 6 and FIG. 10).
Step 12), these steps may be omitted to search the database.

[0029]

According to the present invention, identification data taking means for taking in unique identification data from a part of a patient's body, and a database storing personal health information of a plurality of patients. − And
The database is accessed via a network based on the unique identification data ingested by the identification data ingesting means, and personal health information corresponding to the unique identification data is obtained. Therefore, even if it is difficult to confirm the identity of the person, it is possible to acquire the information such as the confirmation of the identity and the medical history and treatment history without using a medium such as a card.

According to another aspect of the present invention, identification data for ingesting unique identification data from a part of a patient's body is provided.
Accessing a database storing personal health information of a plurality of patients via a network based on the ingested unique identification data and accessing the unique identification data. And a personal health information acquisition step of acquiring personal health information corresponding to (i).

[Brief description of the drawings]

FIG. 1 is a configuration diagram of a first embodiment.

FIG. 2 is a specific configuration diagram of the personal health information search system 1.

FIG. 3 is a configuration diagram of an FMP database 33.

FIG. 4 is a configuration diagram of a database 41.

FIG. 5 is a diagram showing a configuration of personal data stored for each hospital.

FIG. 6 is a flowchart showing the operation of the CPU 14 in the first embodiment.

FIG. 7 is a configuration diagram of a second embodiment.

FIG. 8 is a specific configuration diagram of the personal health information search system 2.

FIG. 9 is a configuration diagram of a database 49.

FIG. 10 is a flowchart showing the operation of a CPU 14 according to the second embodiment.

[Explanation of symbols]

 1, 2 Personal health information retrieval system 11 Terminal 12 Fingerprint matching device 13, 18 Database server 14 CPU 15-1 to 15-N Hospital 16 Network 20 Fingerprint ingesting device 41, 49 Database 43 Fingerprint data 61 Application data -S 71,72 Application program

Continued on the front page (72) Inventor Satoshi Nishimura 5-7-1 Shiba, Minato-ku, Tokyo F-term in NEC Corporation 5B049 AA01 BB41 EE05 EE08 5B075 ND20 NK10 PQ05 UU26

Claims (18)

[Claims] 1. An identification data ingesting means for ingesting unique identification data from a part of a patient's body, a database storing personal health information of a plurality of patients, and the identification. An individual who accesses the database via a network based on the unique identification data ingested by the data ingesting means and acquires personal health information corresponding to the unique identification data. A personal health information retrieval system, comprising: health information acquisition means. 2. The personal health information search system according to claim 1, wherein the unique identification data and the personal health information are stored in the database in association with each other. 3. The database according to claim 1, wherein the database is the unique identification data.
A first database in which data and the personal health information storage location are stored in association with each other; and a second database in which the personal health information is stored for each personal health information storage location. The personal health information retrieval system according to claim 1 or 2, wherein 4. The personal health according to claim 3, wherein the unique identification data and the personal health information storage location are stored in the second database in association with each other. Information retrieval system. 5. The data base stores the unique identification data, the personal health information, and a location where the personal health information is stored in association with each other. The personal health information search system according to claim 1. 6. The data base according to claim 3, wherein said data base further includes a third data base in which said registered unique identification data is stored. Personal health information search system described in. 7. The personal health information retrieval system according to claim 3, wherein the personal health information storage destination is a medical institution such as a hospital connected to the network. 8. The personal health information retrieval system according to claim 1, wherein said identification data intake means is provided in a terminal connected to said network. 9. The personal health information retrieval system according to claim 1, wherein said unique identification data is fingerprint data. 10. A unique identification data from a part of a patient's body.
An identification data ingesting step of ingesting data, and accessing a database storing personal health information of a plurality of patients via a network based on the unique identification data ingested. Obtaining a personal health information corresponding to the unique identification data. 11. The personal health information search method according to claim 10, wherein the unique identification data and the personal health information are stored in the database in association with each other. 12. The database according to claim 1, wherein the database is a first database in which the unique identification data and the personal health information storage location are stored in association with each other, and the personal health information storage. 12. The personal health information retrieval method according to claim 10, comprising a second database in which said personal health information is stored for each destination. 13. The personal health according to claim 12, wherein said unique identification data and said personal health information storage location are stored in association with each other in said second database. Information retrieval method. 14. The database according to claim 1, wherein said unique identification data, said personal health information and a place where said personal health information is stored are stored in association with each other. The personal health information search method according to claim 10. 15. The apparatus according to claim 12, wherein said data base further includes a third data base in which said registered unique identification data is stored. Search for personal health information described in 16. The personal health information retrieval method according to claim 12, wherein said personal health information storage destination is a medical institution such as a hospital connected to said network. 17. The personal health information search method according to claim 10, wherein the identification data ingesting step is performed by a terminal connected to the network. 18. The personal health information search method according to claim 10, wherein said unique identification data is fingerprint data.