JP2010079628A - Regional cooperative path system utilizing it - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system, which can provide medical treatment plan information required by a doctor or a nurse for treating a patient in an emergency or the like, provide better medical service for patients, and further improve work efficiency of the medical treatment work staff. <P>SOLUTION: A regional cooperative path system includes: a server including a medical treatment plan database for saving the medical plan data for patients and a user information database for saving biometrics authentication data for users and patients; and user terminals which are communicatively connected to the server via the Internet and arranged in a medical institution or a nursing care facility. Regional cooperative path data including the medical treatment plan data and the biometrics authentication data can be transmitted from the user terminals to the server, and the server allows the user to access the system, only when the biometrics authentication data of the users are registered on the user information database beforehand. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a regional cooperation path system using IT.

  The clinical path is a medical application of a manufacturing process chart called the critical path. The Clinical Path is a summary of the essential work that must be performed by the medical team and the most desirable order of execution and timing to obtain specific results for patients with certain diseases. It is.

  On the other hand, the regional alliance pass is an attempt to link the health and welfare services by extending the clinical pass in the hospital to regional medicine. For example, patients with acute illnesses such as stroke, myocardial infarction, and femoral neck fractures are initially transported to and admitted to an acute care hospital, but depending on the subsequent medical condition, Rehabilitation hospital). If the situation does not recover, we will move from one health care facility to another for home medical treatment. In the regional cooperation pass, each of these facility personnel will cooperate to share information (medical care plan) on the current situation and future response of patients, thereby eliminating the waste of work and providing better services to patients. It is for.

  Currently, this regional alliance pass is generally operated on a paper basis, and the patient receives the regional alliance pass when the patient leaves the acute care hospital, and the patient passes it to the next medical institution (eg, near the patient's location). The doctors of the next medical institution conduct a medical examination based on the regional cooperation pass brought by the patient.

  However, in a traditional system where the information to be shared cannot be obtained without referring to the paper-based path that the patient brings, the patient loses the path or the patient does not carry the path as in an emergency. In some cases, doctors and nurses cannot access the information they need.

  Under the above circumstances, doctors and nurses can easily obtain medical plan information necessary for patient treatment even in an emergency, etc., and can provide better medical services for patients, and medical services There is a need for a system that can increase the operational efficiency of workers.

  In view of such circumstances, the present invention provides a new regional cooperation path system utilizing the following IT.

(1) A medical plan database for storing patient medical plan data and a server having a user information database for storing user and patient biometrics authentication data, and the server can communicate with each other via the Internet. A regional cooperation path system including a connected user terminal installed in a medical institution and / or care facility,
The regional cooperation path data including the medical plan data and the biometric authentication data can be transmitted from the user terminal to the server,
The server
Permit access to the system only for users whose biometrics authentication data is registered in advance in the user information database,
In response to the registration request for regional cooperation path data from the user terminal, only when both the requester's biometric authentication data and the patient's biometric authentication data are received together with the patient's medical plan data, the medical plan A regional cooperation path system that permits registration of the patient's medical plan data and biometric authentication data in the database and the user information database.
(2) The system according to (1), wherein the biometric authentication is vein authentication, fingerprint authentication, eyeball iris authentication, or voiceprint authentication.
(3) The server
The medical plan data of the patient, the biometric authentication data of the patient and the biometric authentication data of the requester are associated with each other and stored in the medical plan database and the user information database.
The regional cooperation system according to (1) or (2) above.
(4) The server
In response to the medical plan data reference request from the user terminal, only when the biometric authentication data of the requester is received and the medical plan data is associated with the biometric authentication data of the requester , Sending the medical plan data to the user terminal,
The regional cooperation path system according to any one of (1) to (3) above.
(5) The server
The regional cooperation path system according to (4), wherein editing of the medical care plan data from the user terminal with respect to the referred medical care plan data is permitted.
(6) The regional cooperation path data registration request includes a request for adding biometrics authentication data of a registered user other than the requester,
The server only requests the requester's biometrics authentication data when it is associated with the medical plan data and the requester has authority to add biometrics authentication data of other registered users. The regional cooperation path system according to the above (1), which permits a request to add biometric authentication data of a registered user other than the above.

  The regional cooperation path system of the present invention allows doctors and nurses to easily obtain medical plan information necessary for patient treatment even in an emergency, etc., providing better medical services for patients, and further providing medical services. The work efficiency of workers can be further increased.

  The regional cooperation path system of the present invention is useful as a new regional cooperation path system with improved security, business efficiency, convenience, and the like. In particular, it is useful as a regional cooperative path system utilizing IT for patients with five major diseases (stroke, myocardial infarction, femoral neck fracture, diabetes, and cancer) and patients with gastrostomy.

  FIG. 1 is a schematic diagram showing an exemplary configuration of an embodiment of a regional cooperation path system 1 according to the present invention.

  The regional cooperation path system 1 of the present invention typically includes a server 11 managed by a system management organization 16 that is a system administrator, a basic hospital 17 equipped with advanced medical equipment, a regional clinic that performs rehabilitation, and the like. 18. It is comprised from the terminal (12, 13, 14) arrange | positioned in the nursing care facility 19 grade | etc.,. The server 11 and the terminals (12, 13, 14) are connected to each other via the Internet 15 so that they can communicate with each other.

  The server 11 includes a medical care plan database 112 that stores data including patient medical plan information and the like, and a user information database 111 that stores user and patient authentication information.

  Although not shown, the server 11 is a component generally provided in a personal computer, such as a CPU, memory, communication device (communication port, ADSL modem, LAN port, PC card, etc.), input device ( Example: keyboard, mouse, touch screen, finger vein authentication device, etc.), output device (display, printer, etc.), etc. The terminal (12, 13, 14) also includes these components.

  FIG. 2 shows data 21 (referred to herein as a “tag”) obtained by digitizing medical care plan information used in the regional cooperation path system 1 of the present invention and user authentication information 22 (referred to as “ FIG. 3 is a schematic diagram conceptually showing a regional cooperation path 2 including a “ticket”. In the figure, a ticket is attached to the tag with a ring, which conceptually shows that the data of the ticket 22 is associated with the data of the tag 21 on the database.

  As shown in FIG. 2, the tag 21 included in the regional alliance path 2 used in the present invention typically has care content for the patient on the vertical axis (eg, medical goals, examination types, dietary restrictions, observation records). ), A medical plan table with the passage of time (date) on the horizontal axis.

  A ticket 22 attached to the tag 21 with a ring includes authentication information of users such as a patient P, a doctor (A, B, etc.), and a nurse C. Note that FIG. 2 is a conceptual diagram only, and shows that data of a patient's medical plan and data of user authentication information that can access the data are associated in the database.

  The user authentication information used in the present invention is obtained using biometric authentication. Biometrics authentication is an authentication method that performs identity verification based on physical features such as finger veins, palm veins, fingerprints, eyeball irises, and voiceprints. In the authentication using a password or an object, there is a risk that the person himself cannot be authenticated due to forgetting or losing, or other persons may be authenticated due to leakage or theft. However, in the case of biometric information, the risk is considered low. In addition, there is an advantage that key input or carrying of an object is unnecessary, and that a third party other than the person can be prevented from being authenticated. As the biometric authentication used in the present invention, any biometric authentication method can be used, but finger finger and palm vein authentication, fingerprint authentication and the like are particularly preferable.

  Next, a method for using the regional cooperation path system of the present invention will be specifically described.

  The users (users) of the regional cooperation path system of the present invention are typically doctors, nurses, caregivers, and the like who work at basic hospitals, rehabilitation hospitals or clinics, care facilities, and the like. If necessary, the patient itself may be included as a user.

  In order to use the regional cooperation path system of the present invention, the user must first perform user registration. User registration can be performed using each terminal (12, 13, 14) of a user equipped with a biometric authentication device (typically a vein authentication device). The user sends a user registration request from each terminal to the server 11 of the system management organization 16 via the Internet. The user registration request includes user authentication information (for example, a user finger or palm vein pattern input by a vein authentication device). Upon receiving the authentication information and registration request from the user, the server 11 stores the user authentication information in the user information database 111 and registers it. The regional cooperation path system 1 of the present invention can be configured to require user registration confirmation by biometric authentication when a user logs in to the system.

  Patients who are expected to use the regional alliance path system 1 of the present invention are mainly patients with five major diseases (stroke, myocardial infarction, femoral neck fracture, diabetes, and cancer) and patients with gastrostomy. Is included. Usually, these patients are transported to a basic hospital equipped with highly-equipped medical facilities in the acute phase, and receive treatment such as necessary surgery. For a patient who has received treatment at the core hospital, a doctor at the core hospital registers the regional cooperation path 2 including the tag 21 and the ticket 22 with respect to the server 11 via the terminal 12. In the regional cooperation path system 1 of the present invention, registration of the regional cooperation path 2 always requires both doctor authentication information (ticket) and patient authentication information (ticket). By doing so, it is possible to maintain the reliability and security of information in the regional cooperation path 2.

  FIG. 3 is a flowchart showing processing performed by the server 11 (CPU) that receives a regional cooperation path registration request including information on the tag 21 and the ticket 22 from the user. Here, in the registration request, when newly registering the patient's regional cooperation path (tag and ticket) and editing the contents of the patient's regional cooperation path (tag and ticket contents) (eg, deleting the ticket and / or To be added). In addition, considering the flow of work of regional cooperation medical care, when registering a new regional cooperation path, it is basically assumed that the server 11 is accessed from the terminal 12 of the basic hospital 17. When editing the contents of the pass (for example, adding a ticket), the server 11 may be accessed not only from the terminal 12 of the basic hospital 17 but also from the terminal 13 of the clinic 18 and the terminal 14 of the care facility 19. Assumed.

  The process shown in FIG. 3 starts when the server 11 receives a regional cooperation path registration request from the user terminal via the Internet 15. First, in step S31, it is determined whether the registration request includes a requester (typically a doctor) ticket and a patient ticket. If both the requester and patient tickets have been received (S31: Yes), the user information database 111 is connected in step S32, and then in step S33, it is determined whether or not the requester is a registered user. If the requester is registered as a user (S33: Yes), the process proceeds to step S34, where the received tag data is registered in the medical care plan database 112 in association with the requester and patient tickets, and the process ends. Note that patient authentication information (ticket information) or additional user authentication information newly added at the time of registration is stored in the user information database 111.

  If both the requester and patient tickets are not received in step S31 (S31: No), the process proceeds to step S35, a registration impossible message is transmitted to the requester's terminal, and the process ends. In step S33, if the requester is not registered as a user (S33: No), the process proceeds to step S35 and a registration impossible message is transmitted to the requester's terminal, and the process is terminated.

  In the flowchart shown in FIG. 3, there is a step of connecting to the user database and determining whether the requester is registered (step S32 and step S33), but when the requester (or user) logs in to the system. Steps S32 and S33 may be omitted if the user registration has already been determined.

  In the regional cooperation path system 1 according to the present invention, a user once given a ticket to a tag can freely refer to the tag thereafter.

  In community-linked medical care, patients who have completed acute treatment at a core hospital usually go to a rehabilitation hospital or a clinic near the patient's residence as the next step, and continue diagnosis, rehabilitation, and / or Receive medical services such as testing. In addition, after that, a service in a nursing facility or the like is used as necessary.

  In the regional cooperation path system 1 according to the present invention, when a patient visits a doctor's clinic 18 registered in the system, for example, the doctor of the clinic 18 uses a biometric authentication device (typically, A tag reference request is sent to the server 11 together with the doctor's own authentication information (ticket) and the patient's authentication information (ticket) from the terminal 13 equipped with a vein authentication device) as an input means, and is created in the basic hospital A tag (medical treatment plan table) can be referred to.

  FIG. 4 is a flowchart showing processing performed by the CPU of the server 11 that has received the tag reference request from the user terminal 13. The same processing is performed when a tag reference request is received from another user terminal (14).

  The process shown in FIG. 4 starts when the server 11 receives a tag reference request from the user terminal (13, 14). First, in step S41, it is determined whether or not the requester (eg, doctor, nurse, caregiver) ticket and patient ticket are included in the tag reference request. If both the requester and patient tickets have been received (S41: Yes), the user information database 111 is connected in step S42, and then in step S43, it is determined whether or not the requester is a registered user. . If the requester is registered as a user (S43: Yes), the process proceeds to step S44 to connect to the tag database. Next, in step S45, the tag database is referenced to determine whether or not the requester's ticket is associated with the tag. When the requester's ticket is already associated with the tag (S45: Yes), the process proceeds to step S47, where the tag is transmitted to the requester's terminal, and the process ends. On the other hand, if the requester's ticket is not associated with the tag in step S45 (S45: No), the requester's ticket is assigned to the tag in step S46, and then the process proceeds to step S47 to request the requested tag. Is sent to the user's terminal and the process is terminated.

  In step S41, if both the requester and patient tickets are not included (S41: No), the process proceeds to step S48, a reference impossible message is transmitted to the requester's terminal, and the process ends. In this way, the security of the system can be ensured by making it impossible to refer to the tag without the authentication information (ticket). Further, by referring to the requester's ticket as well as the patient's ticket in order to refer to the tag, it is possible to prevent the tag from being viewed by a user unrelated to the patient. Further, by making the authentication information based on biometric authentication, it is possible to prevent the risk that the person himself cannot be authenticated due to forgetting or loss, or the risk that another person will be authenticated due to leakage or theft. In addition, there is an advantage that key input or carrying of an object is unnecessary, and that a third party other than the person can be prevented from being authenticated.

  In step S43, even when the requester is not registered as a user (S43: No), the process proceeds to step S48, a reference impossible message is transmitted to the requester's terminal, and the process ends. Thus, by limiting the persons who can use the system to those who are registered as users in the system, the security of the system can be maintained. As described in the description of FIG. 3, the user registration determination step such as step S42 and step S43 is configured to determine whether or not the requester (or user) has registered the user when logging in to the system. If it is, it may be omitted.

  On the other hand, in another embodiment of the present invention, for example, when the patient is discharged from the main hospital 17 and the patient is to go to the clinic 18 near the patient's residence, the doctor of the main hospital 17 In order to facilitate the transfer of the patient's treatment to the doctor at the clinic 18, the doctor at the basic hospital 17 pre-defines the contents of the patient's medical plan table before the patient visits the clinic 18. Sometimes you want to let me know. In the regional cooperation path system 1 of the present invention, in such a case, on the assumption that the doctor of the clinic is registered as a user in the system, the doctor of the basic hospital obtains the authentication information of the doctor of the clinic in advance for the patient. Can be attached to the tag. This can be realized by, for example, a configuration in which a doctor at a basic hospital can designate a doctor's ticket at a clinic by a registration number and attach it to a patient tag in step S34 of the flowchart of FIG. It is. In the regional cooperation path system 1 according to the present invention, once a ticket is assigned to a tag, a user specified by the ticket can freely refer to the tag. By giving the ticket to the patient's tag in advance, the doctor of the clinic 18 can refer to the medical plan table data using the system of the present invention before the patient visits the clinic 18. . It should be noted that the system administrator can appropriately set whether or not anyone can have the authority to add another user's ticket, or whether the user can be limited to doctors at the core hospital.

  FIG. 5 shows that a user having a ticket associated with a patient tag (for example, a doctor at a basic hospital, a doctor at a clinic, a nurse at a care facility, etc.) from the user terminal (12, 13, 14) to the server 11 5 is a flowchart showing processing performed by the server 11 when making a reference request to the tag and making a reference.

  The process shown in FIG. 5 starts when the server 11 receives a tag reference request from the user terminal (12, 13, 14). Upon receiving the tag reference request, the server 11 determines whether or not the requester's ticket has been received in step S51. If the ticket has been received (S51: Yes), it is connected to the user information database 111 in step S52, and it is determined whether or not the requester is a user registered in step S53. If the user is registered (S53: Yes), the process proceeds to step S54 to connect to the tag database 112, and whether the requester's ticket is given to the tag requested in step S55 (the tag and the ticket are stored on the database). If the requester's ticket is given (S55: Yes), the requested tag is requested in step S56. To the user's terminal, and the process ends.

  If the requester's ticket has not been received in step S51 (S51: No), the process proceeds to step S57, a reference impossible message is transmitted to the requester's terminal, and the process ends. Further, even when the requester is not registered as a user in step S53 (S53: No), the process proceeds to step S57, a reference impossible message is transmitted to the requester's terminal, and the process ends. Further, even when the requester's ticket is not given to the tag in step S55 (S55: No), the process proceeds to step S57, a reference impossible message is transmitted to the requester's terminal, and the process is terminated. Note that the user registration determination step such as step S52 and step S53 is omitted if the requester (or user) is configured to determine the presence or absence of user registration when logging into the system. May be.

  In addition, in response to the tag reference request, the user can be permitted to edit not only the tag reference but also the referenced tag data. The edited tag data can be overwritten in the medical plan database 112 of the server 11.

  The embodiments of the present invention have been described above with reference to the drawings. However, the scope of the present invention is not limited to these embodiments, and does not exceed the scope of the present invention described in the claims. In the limit, various modifications are possible and are within the scope of the present invention.

  The regional cooperation path system of the present invention is useful as a new regional cooperation path system with improved security, business efficiency, convenience, and the like. In particular, it is useful as a regional cooperative path system utilizing IT for patients with five major diseases (stroke, myocardial infarction, femoral neck fracture, diabetes, and cancer) and patients with gastrostomy.

It is a mimetic diagram showing an exemplary composition of one embodiment of regional cooperation path system 1 of the present invention. It is the schematic diagram which represented not only the data 21 which digitized the medical plan information used in the regional cooperation path system 1 of this invention, but the regional cooperation path 2 containing the user authentication information 22 linked | related with the tag 21 on a database. . It is the flowchart showing the process which the server 11 (CPU of) received the regional cooperation path | pass registration request containing the information of the tag 21 and the ticket 22 from the user. It is a flowchart showing the process which CPU of the server 11 which received the tag reference request from the user terminal 13 performs. The same processing is performed when a tag reference request is received from the user terminal 14. The flowchart which shows the process which the server 11 performs when the user who has the ticket linked | related with the patient's tag makes a reference request of the tag with respect to the server 11 from a user's terminal (12, 13, 14) and refers. It is.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Regional cooperation path system 11 of this invention Server 111 User information database 112 Medical plan database 12, 13, 14 User terminal 15 Internet 16 System management organization 17 Core hospital 18 Clinic 19 Care facility 2 Local cooperation path used by this invention 21 tags 22 tickets

Claims (6)

A server including a medical plan database for storing patient medical plan data and a user information database for storing biometric authentication data of users and patients; and the server connected to be communicable via the Internet A regional alliance pass system including a user terminal installed in a medical institution and / or a care facility,
Regional cooperation path data including the medical plan data and the biometric authentication data can be transmitted from the user terminal to the server,
The server
Permit access to the system only for users whose biometrics authentication data is registered in advance in the user information database,
Only when both the requester's biometrics authentication data and the patient's biometrics authentication data are received together with the patient's medical plan data in response to the registration request for regional cooperation path data from the user terminal, the medical plan Permit registration of the patient's medical plan data and biometric authentication data in the database and the user information database;
Regional cooperation path system.   The system of claim 1, wherein the biometric authentication is vein authentication, fingerprint authentication, eyeball iris authentication, or voiceprint authentication. The server
The medical plan data of the patient, the biometric authentication data of the patient and the biometric authentication data of the requester are associated with each other and stored in the medical plan database and the user information database.
The regional cooperation system according to claim 1 or 2. The server
In response to a medical plan data reference request from the user terminal, only when the requester's biometrics authentication data is received and the medical plan data is associated with the requester's biometrics authentication data Sending the medical plan data to the user terminal;
The regional cooperation path | pass system in any one of Claims 1-3. The server
The regional cooperation path system according to claim 4 which permits edit of the medical treatment plan data from said user terminal to said referred medical treatment plan data. The registration request for the regional cooperation path data includes a request for adding biometric authentication data of a registered user other than the requester,
The server only requests the requester's biometric authentication data when it is associated with the medical plan data and the requester has authority to add biometric authentication data of other registered users. The regional cooperation path | pass system of Claim 1 which permits the addition request | requirement of biometrics authentication data of registered users other than.

Images