JP2015028773A - Care support system cooperating with medical system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enable a medical system and a care system to cooperate with each other while securing information security.SOLUTION: A care support system comprises: a terminal device; and a care support information management server which provides the terminal device with medical information and care support information via a network. The care support information management server comprises: an interface unit which exchanges information with a medical information providing server; and a storage unit which stores a care ID which is an identification ID of a user of the care support system, care support information which is associated with the care ID, a medical information access right table which defines an access right of the user of the care support system for accessing medical information managed by the medical system, and an ID correspondence table associating a medical ID which is an identification ID of a user of the medical system with the care ID of the same user.

Description

  The present invention relates to a care support system in cooperation with a medical system.

  In recent years, a regional medical cooperation system has been attracting attention for the purpose of a consistent medical system in the region. In this regional medical cooperation system, medical information such as electronic medical record information of each hospital is shared by linking hospital systems in a predetermined area. According to this cooperation, for example, the local doctor refers to the patient's past medical treatment information from the electronic medical record information of the general hospital in the area, or the local general doctor introduced the patient to the general hospital In this case, it is possible to continuously follow and follow the subsequent progress from the electronic medical record information.

  Here, since medical information is highly confidential information related to human life, when information is shared by information technology, the security of the information becomes a problem. In this regard, in the regional medical cooperation system, the mediation server that controls the transmission of the electronic medical record information performs only the information transmission management based on the user ID information managed in each hospital system, and from each hospital system. The transmitted medical chart information is not stored in the mediation server itself. Therefore, in this system, medical information such as electronic medical record information is stored in each hospital, so that the safety of the information is ensured.

  In recent years, there is a nursing support system that links nursing care providers with information technology to share nursing support information. In this type of system, care support information or the like is generally stored on a shared server, and each business operator tries to share care support information by accessing the shared server through their own terminal.

  On the other hand, a medical / nursing care cooperation system for sharing information on medical care and nursing care has recently been attracting attention (for example, Non-Patent Document 1). This is because medical information held by medical institutions and care-related information held by nursing care establishments, etc., which have not been shared in the past, are shared with each other using information technology. It aims at grasping the state of a patient or a cared person consistently from the diseased stage to after discharge, thereby enabling high-quality medical practice and care.

Information sharing and ICT utilization for promoting home medical care cooperation, "Information sharing and ICT utilization for promoting home medical care cooperation", [online], Ministry of Health, Labor and Welfare, [June 12, 2013], Internet <URL : http: //www.mhlw.go.jp/seisakunitsuite/bunya/kenkou_iryou/iryou/zaitaku/dl/h25_0509-01.pdf>

  However, there are the following problems when trying to link the medical system and the care system. In other words, as already mentioned, in the regional medical system, medical information such as electronic medical record information is basically stored in each hospital's system, etc. The support system is configured to concentrate information on a central shared server. Therefore, if information is simply shared between both systems, unfavorable situations may occur from the viewpoint of information safety management, for example, medical information that is highly confidential is stored in the shared server.

  From the above, the issue is how to link both the medical and nursing care systems while utilizing the existing medical system in which the safety of information is ensured.

  The present invention has been made in view of the above problems, and the object of the present invention is to appropriately link a conventional medical system in which safety of information is ensured with a care support system, and To provide users with medical information managed by a medical system.

  In order to achieve the above object, a first feature of a care support system according to the present invention is a terminal device, and a care support information management server that provides medical information and care support information to the terminal device via a network; The care support information management server comprising: an interface unit that exchanges information with a medical information providing server that constitutes a medical system in which a predetermined electronic medical record information system is linked; The care access ID of the user of the care support system, the care support information associated with the care ID, and the access authority of the user of the care support system to the medical information managed by the medical system The medical information access authority table that defines the medical ID, the medical ID that is the identification ID of the user of the medical system, and the When a medical information provision request regarding a predetermined browsing target person is received from the terminal device, a care ID of the user of the terminal device is stored. And a determination unit that determines whether or not to access medical information based on the medical information access authority table, and the browsing when the determination unit determines that access to medical information is possible A request for generating a medical information request including a medical ID based on the care ID of the subject and the ID correspondence table, and transmitting the medical information request to the medical information providing server via the interface unit. A medical system provided from the medical information providing server via the interface unit based on the transmission unit and the medical information request After receiving the medical information is to and a medical information providing unit for providing the medical system side medical information to the terminal device.

  Here, the medical information providing server may be a medical server that links and mediates electronic medical record information, or may be an electronic medical record information server itself.

  According to such a configuration, it is possible to provide a care support system that can provide medical information to the user of the care support system while ensuring the safety of the information.

  In order to achieve the above object, according to a second feature of the care support system of the present invention, the storage unit further includes care support system side medical information associated with the care ID, and the medical information access authority The access authority of the table is consistent with the access authority to the care support system side medical information of the user of the care support system.

  According to such a configuration, the access authority to the medical information on the medical system side can be set at the same time by setting the access authority to the medical information on the care support system side. Setting access rights is easy.

  In order to achieve the above object, a third feature of the care support system according to the present invention is that the medical information providing unit further provides the care support system side medical information together with the medical system side medical information. is there.

  According to such a configuration, while ensuring the safety of the information, the care support system user can seamlessly and simultaneously receive the medical information derived from the care support system and the medical information derived from the medical system for the user of the care support system. It is possible to provide a care support system that can be provided to the user.

  In order to achieve the above object, according to a fourth feature of the care support system according to the present invention, the storage unit further includes cooperation availability designation information for designating availability of cooperation with a medical system for each care establishment, When the care establishment is designated to be able to cooperate with the medical system, a care-side medical information providing unit is provided that transmits the care support system-side medical information to the medical system that is the cooperation destination. It is in.

  According to such a configuration, the care support system side medical information can be referred to on the care side even on the care side, and more detailed information of the user can be referred to on the medical system side.

  In order to achieve the above object, the fifth feature of the care support system according to the present invention is that medical information provided to the terminal device is provided in a manner that cannot be stored in the terminal device. is there.

  According to such a configuration, it is possible to provide a care support system that can provide medical information to the user of the care support system while ensuring the safety of the information.

  In order to achieve the above object, a first feature of a care support information management server according to the present invention is a terminal device and care support information management that provides medical information and care support information to the terminal device via a network. The care support information management server in a care support system comprising a server, wherein the care support information management server is a medical information providing server that constitutes a medical system in which a predetermined electronic medical record information system is linked, An interface unit for exchanging information, a care ID that is an identification ID of a user of the care support system, care support information associated with the care ID, and the medical information managed by the medical system The medical information access authority table defining the access authority of the user of the care support system and the same user Received a medical information provision request relating to a predetermined viewing target person from the terminal device, and a storage unit for storing an ID correspondence table in which a medical ID that is an identification ID of the user and the care ID are associated with each other In this case, the access to the medical information is performed by the determination unit that determines whether to access the medical information based on the care ID of the user of the terminal device and the medical information access authority table, and the determination unit. When it is determined that it is possible, a medical information request including a medical ID is generated based on the care ID of the person to be browsed and the ID correspondence table, and the medical information is transmitted via the interface unit. A request transmission unit that transmits a medical information request to a providing server; and the medical device through the interface unit based on the medical information request. After receiving the medical system side medical information provided by the broadcast providing server is to and a medical information providing unit for providing the medical system side medical information to the terminal device.

  According to such a configuration, it is possible to provide a care support information management server that can provide medical information to a user of a care support system while ensuring the safety of information.

  In order to achieve the above object, a first feature of the medical information providing method according to the present invention is a terminal device and a care support information management server that provides medical information and care support information to the terminal device via a network. A care information providing method for providing medical information to the terminal device, wherein the care support information management server is a medical information that constitutes a medical system in which a predetermined electronic medical record information system is linked. Managed by an interface unit that exchanges information with a providing server, a care ID that is an identification ID of a user of the care support system, care support information associated with the care ID, and the medical system The medical information access authority table that defines the access authority of the user of the care support system to the medical information to be processed, and the same user A storage unit for storing an ID correspondence table in which a medical ID that is an identification ID of a user of the medical system and the care ID are associated with each other, and a predetermined browsing from the terminal device A determination step of determining whether to access medical information based on a care ID of a user of the terminal device and the medical information access authority table when receiving a medical information provision request regarding the target person; and the determination When it is determined that the medical information can be accessed, the medical information request including the medical ID is generated based on the care ID of the viewing target person and the ID correspondence table, A request transmission step of transmitting a medical information request to the medical information providing server via the interface unit, and based on the medical information request A medical information providing step of providing the medical system side medical information to the terminal device after receiving the medical system side medical information provided from the medical information providing server via the interface unit; It is to prepare.

  According to such a configuration, it is possible to provide a medical information providing method capable of providing medical information to the user of the care support system while ensuring the safety of information.

  In order to achieve the above object, a first feature of a server program according to the present invention includes: a terminal device; and a care support information management server that provides medical information and care support information to the terminal device via a network. In the care support system comprising: a server program for providing medical information to the terminal device, wherein the care support information management server is a medical information providing server constituting a medical system in which a predetermined electronic medical record information system is linked. An interface unit for exchanging information, a care ID that is an identification ID of a user of the care support system, care support information associated with the care ID, and medical information managed by the medical system The medical information access authority table that defines the access authority of the user of the care support system to the same user A storage unit that stores an ID correspondence table in which a medical ID that is an identification ID of a user of the medical system and the care ID are associated with each other, and the care support information management server includes: When a medical information provision request regarding a predetermined person to be browsed is received from the terminal device, whether access to medical information is determined based on the care ID of the user of the terminal device and the medical information access authority table When the determination unit determines that access to medical information is possible, the medical ID is determined based on the care ID of the person to be browsed and the ID correspondence table. A request transmission step of generating a medical information request including, and transmitting a medical information request to the medical information providing server via the interface unit; Based on the medical information request, after receiving the medical system side medical information provided from the medical information providing server via the interface unit, the medical system providing the medical system side medical information to the terminal device And an information providing step.

  According to such a configuration, it is possible to provide a server program that can provide medical information to the user of the care support system while ensuring the safety of the information.

  According to the care support system, the care support information management server, the medical information providing method, and the server program according to the present invention, it is possible to provide medical information to the user of the care support system while ensuring the safety of information. it can.

FIG. 1 is an explanatory diagram of the overall configuration of the system. FIG. 2 is a block diagram showing an example of the internal configuration of the computer. FIG. 3 is an explanatory diagram of a memory map of the storage unit of the electronic medical record information server. FIG. 4 is an explanatory diagram of a memory map of the storage unit of the regional medical server. FIG. 5 is an explanatory diagram of a memory map of the storage unit of the care support information management server. FIG. 6 is an explanatory diagram showing an example of the operating state of the staff information access authority table. FIG. 7 is an explanatory diagram showing an example of the operating state of the state of the user information access authority table. FIG. 8 is an explanatory diagram of a registration processing flow to the staff information table. FIG. 9 is a screen diagram at the time of registration processing of an office. FIG. 10 is a screen diagram (part 1) during the staff registration process. FIG. 11 is a screen diagram (part 2) during the staff registration process. FIG. 12 is a screen view during user registration processing. FIG. 13 is a screen diagram during the family registration process. FIG. 14 is a screen diagram during registration processing of a person in charge. FIG. 15 is a screen diagram during the registration process of the contact slip. FIG. 16 is a screen diagram at the time of registration processing of history information and the like. FIG. 17 is a screen view during the emergency contact registration process. FIG. 18 is a screen diagram during prescription registration processing. FIG. 19 is a screen view during the allergy / inhibitory registration process. FIG. 20 is a screen diagram during a disease name registration process. FIG. 21 is a screen view during registration processing of a family doctor. FIG. 22 is a screen view during ADL registration processing. FIG. 23 is an explanatory diagram of a registration process flow in the user information table. FIG. 24 is a screen view during today's physical condition registration process. FIG. 25 is a screen diagram during the registration process of the contact slip. FIG. 26 is a screen diagram during registration processing such as upbringing. FIG. 27 is a screen diagram during the registration process of what is desired in the future. FIG. 28 is a screen view during emergency contact registration processing. FIG. 29 is a screen diagram during registration processing of blood pressure, pulse, and the like. FIG. 30 is a screen view during the allergy / contraindication registration process. FIG. 31 is a screen diagram during the registration process of a family doctor. FIG. 32 is a screen diagram during the registration process of the activity ability (A3). FIG. 33 is a screen view during disease name registration processing. FIG. 34 is an explanatory diagram of the information reference processing flow. FIG. 35 is a screen view when referring to the basic user information. FIG. 36 is an explanatory diagram of the information browsing flow of the regional medical system. FIG. 37 is an explanatory diagram of a matching process between a care etc. ID and an integrated medical ID. FIG. 38 is an explanatory diagram of a medical information acquisition flow. FIG. 39 is a flowchart for explaining the introduction part to the medical information acquisition flow. FIG. 40 is a screen diagram of the introduction part to the medical information acquisition flow. FIG. 41 shows a medical information storage flow. FIG. 42 is an explanatory diagram of the overall system configuration (another embodiment). FIG. 43 is an explanatory diagram of a matching process between a care etc. ID and a local medical ID. FIG. 44 is an explanatory diagram for explaining a medical information acquisition flow. FIG. 45 is a view (part 1) of the user-side reference authority setting screen. FIG. 46 is a view (part 2) of the user-side reference authority setting screen. FIG. 47 is a diagram (part 1) illustrating an example of a reference authority setting screen on the administrator side. FIG. 48 is a diagram (part 2) illustrating an example of the reference authority setting screen on the administrator side. FIG. 49 is a diagram showing an example of the configuration of a management server for care support information and the like. FIG. 50 is a diagram illustrating an example of the configuration of the regional medical server. FIG. 51 is a diagram showing an example of the configuration of the electronic medical record information server. FIG. 52 is an explanatory diagram of an initial state of the staff information table. FIG. 53 is an explanatory diagram of an initial state of the user information table. FIG. 54 is a view of a reference authority setting screen by the user family. FIG. 55 is a flowchart showing an outline of shared data transmission processing. FIG. 56 is a flowchart showing details of the shared data transmission process. FIG. 57 is a flowchart showing details of the initial transmission data determination process. FIG. 58 is a flowchart showing an example of browsing processing on the medical side of shared data. FIG. 59 is a flowchart showing another form of browsing processing on the medical side of shared data. FIG. 60 is a screen diagram at the time of external cooperation setting registration. FIG. 61 is a screen view at the time of disease name registration. FIG. 62 is a screen view at the time of emergency contact information setting registration. FIG. 63 is a screen view at the time of therapeutic attention setting registration.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  In one embodiment of the present invention, a care support information management server, which will be described later, acquires medical information through a regional medical server, which will be described later, connected to each electronic medical record information server. The system according to this embodiment will be described in detail below.

<1. System configuration>
First, the configuration of the system according to the present embodiment will be described.

<1.1 Overall system configuration>
First, the overall configuration of the system according to the present embodiment will be described with reference to FIGS. 1 and 49 to 51.

  The system according to this embodiment includes a care support information management server 3, a network 6, a care support system 1 including a staff 7 such as a care establishment or a user terminal 7, a regional medical server 8, and a network 9 And a regional medical system 2 composed of the electronic medical record information server 10.

  An example of the configuration of a management server for care support information and the like is shown in FIG. The care support information management server 3 includes a server device 4 and a large-capacity storage unit 5. The care support information management server is connected to the network 6, and the network 6 is a care provider (for example, home care provider, home care provider, entrance care provider, etc.), Regional Comprehensive Support Center, civilian Homes, NPOs, homes of family members of nursing care support systems, elderly homes with care, medical establishments (eg hospitals, establishments of home-visit nursing and home-visit nutrition), etc. The terminal 7 (for example, a tablet terminal, a smart phone, a personal computer, etc.) is connected.

  In addition, when connecting between the care support information etc. management server 3 and the various terminals 7 via the network 6, it is preferable to use various encryption technologies such as SSL and SSL-VPN.

  An example of the configuration of the regional medical server is shown in FIG. 50, and an example of the configuration of the electronic medical record server is shown in FIG. In this example, the regional medical server 8 includes a VPN device 801, a gateway server 802, and a storage 803. The regional medical server 8 is connected to a network 9, and the network 9 is provided in various medical institutions (acute phase hospital, subacute phase / recovery rehabilitation hospital, clinic, etc.) within a predetermined area (for example, daily life area of a patient). Connected to various terminals (for example, tablet terminals, smartphones, personal computers, etc.) or the electronic medical record information server 10. The electronic medical record information server 10 includes a server 105 and a storage 106, and information stored in the electronic medical record information server 10 can be viewed on the electronic medical record terminal 107.

  In addition, when connecting between the regional medical server 8 and each electronic medical record information server 10 via the network 9, it is preferable to use various encryption technologies such as SSL, SSL-VPN, and IPsec-VPN. .

  The care support information management server 3 is connected to the regional medical server 8 via the VPN device 301 and the gateway server 302. As a result, information can be linked between the care support network and the regional medical network.

<1.2 Hardware configuration>
Next, the hardware configuration of each server (electronic medical record information server, regional medical server, care support information management server, etc.) shown in FIG. 1 will be described with reference to FIG.

  The hardware configuration of the server is as follows. That is, the server computer 1000 includes a control unit 1001, a display unit 1002, a storage unit 1003, an input / output interface unit 1004, and an input operation unit 1005 therein. The control unit 1001 executes various programs. The display unit 1002 may be a graphic processing unit, a display, or the like, but is not necessarily provided in the computer 1000. The storage unit 1003 may be a memory, a hard disk, a storage, or the like, and may be used in combination with or replaced with a large-capacity storage provided outside the computer 1000. The input / output interface 1004 may be provided with a communication interface or the like, and may communicate information with an external device via the interface. The input operation unit 1005 is configured to receive an operation by the operator.

<1.3 Contents stored in each storage unit>
The contents stored in the storage unit of each server will be described with reference to FIGS.

  The contents stored in the storage unit of the electronic medical record information server 10 will be described with reference to FIG. The storage unit includes a program storage unit 2001 and a data storage unit 2002. The program storage unit 2001 stores a program for performing information transmission / reception processing and the like. On the other hand, in the data storage unit 2002, local medical ID data of the patient (user) who visited the medical institution or the like provided with the electronic medical record information server and the electronic medical record information data of the patient are stored. Stored in a linked state.

  The contents stored in the storage unit of the regional medical server 8 will be described with reference to FIG. The storage unit includes a program storage unit 2003 and a data storage unit 2004. The program storage unit 2003 stores a program for performing information transmission / reception processing and the like. On the other hand, in the data storage unit 2004, the local medical ID data individually managed by the medical institution connected to the regional medical server and the plurality of local medical IDs are collected for each user. The associated integrated medical ID data is stored.

  The electronic medical record information data is not stored in the storage unit of the regional medical server 8 except for temporary storage when information is bridged. That is, the regional medical server merely mediates information of each electronic medical record information server based on the electronic medical record information request from each medical institution and the integrated medical ID.

  The contents of the storage unit of the care support information etc. management server 3 will be described with reference to FIG. The storage unit includes a program storage unit 2005 and a data storage unit 2006. The program storage unit 2005 stores a program for performing transmission / reception processing of information, a program for registering information transmitted from each terminal, and the like. On the other hand, in the data storage unit 2006, a login ID management table used for login management to the care support system, and for the same user, a care ID that is an identification ID in the care support system and a medical ID that is an identification ID in the community medical system. Each of the correspondence table of care / medical ID linked with the ID, the staff information database mainly registered by the staff of the care establishment, the user information database mainly registered by the user, and the staff information database Staff information access authority table that associates data types with their access authority (reference authority, registration authority), and usage that associates each data type of the user information database with its access authority (reference authority, registration authority) Person information access authority table and the like. The care ID is a unique identification ID assigned to a business operator, the person, or a family who uses the care support system. The medical ID is a unique identification ID given to the user of the medical system.

  The contents of the staff information access authority table will be described with reference to FIGS. As is clear from these figures, the staff information access authority table includes a reference authority field for registering a person with reference authority and a registration authority field for registering a person with registration authority. It is provided for each type. The authority to register an arbitrary person in the reference authority field and the registration authority field is given only to an administrator of the system (who has an ID as an administrator) in the default state of the system. For this reason, in the default state of the system, any request for registration by a person other than the administrator (for example, one of the care staff, the person being cared for, the family, etc.) of the reference authority or the registration authority is not made by the system. Not accepted. The registration operation of the reference authority or the registration authority is usually performed by a terminal (personal computer or the like) 7 possessed by the administrator.

  FIG. 52 shows a state in which the administrator registers himself / herself as a person having reference authority (reference authority) and a person having registration authority (registration authority) in the default state. In this state, the administrator can refer to and register the corresponding data type in the staff information database only by the administrator himself / herself (for example, any one of the nursing staff, the person being cared for, or their family). Requests for reference or registration are rejected.

  The administrator can also register other persons (for example, any one of the care staff, the person being cared for, the family thereof, etc.) as a person having a reference authority and / or a person having a registration authority. FIG. 6 shows a state in which a person other than the administrator is registered as a person having reference authority and / or a person having registration authority in this manner. As shown in the figure, in the staff information access authority table, the reference authority / registration authority is stored in association with the care ID of the user or the like for each data type.

  In this example, regarding the data type of “care guidance”, the specific staff A, the care recipient himself, and his / her family can both refer to and register. For master information, it is the registration of basic information and the authority to access the specified information (access prohibition, reference or registration) is established, so the authority is the administrator (such as a nursing care establishment or corporation) Is concentrated on. For specific data types, “communication slips”, “prescriptions”, “disease names”, and “precautions for treatment”, both for reference and registration, due to the convenience of communication between staff, the necessity of concealing medical information, etc. It is set so that only specific staff A can perform. In the figure, the data content column is information for convenience of explaining the content of the data type, not the actual stored content.

  Each data type further includes individual detailed data items. That is, if it is an office master, the office name, office number or address, etc., if it is an employee master, staff number, staff ID, password or name, etc. If it is a user master, the user name, kana, gender or If it is a family master, such as date of birth, name, kana or relationship, if it is a master in charge, relationship with the user, etc., if it is a contact card, address, contents, etc. If there is, place of birth, student, work history or personality, if it is an emergency contact, name, relationship, phone number, etc., if it is vital, date, body temperature, systolic blood pressure or pulse, etc. If you are allergic or contraindicated, such as hospital name or prescription doctor, item name, comment or writer, if it is a disease name, writer, illness name or treatment status, etc. Whether it is medical attention such as department or doctor name If it is nursing guidance, such as the entry person, care precautions or start date, etc., the entry name, nursing guidance content, start date or end date, etc. If so, it is the evaluation date, the entry person, or the type.

  The administrator can also delegate the right to appoint a reference authority and / or a registration authority to a specific staff member. For example, when the staff ID of a specific staff is temporarily changed as an administrator, or when a special appointment right delegation code is separately added to the staff ID and this is detected on the system side, the reference authority This can be realized by permitting the registration request of the administrator and / or the registration authority.

  As described above, in the staff information access authority table, it is possible to register an access authority (reference authority and / or registration authority) by a system administrator and / or a care staff who is delegated the appointment authority. Yes.

  Next, the contents of the user information access right table will be described with reference to FIGS. As is clear from these figures, in the user information access authority table, a reference authority column for registering a person with reference authority (reference authority) and a person with registration authority (registration authority) are registered. A registration authority column for this is provided for each data type. The authority to register an arbitrary person in the reference authority field and the registration authority field is given only to the cared person (who has the ID as the cared person) in the default state of the system. Therefore, in the default state of the system, a request for registration of a reference authorized person or a registered authorized person by a person other than the care recipient (for example, the system administrator, any care staff, the family of the care recipient, etc.) Not accepted at all by the system side. In addition, registration operation of this reference authority person or registration authority person is normally performed by the terminal (mobile terminal etc.) 7 which a care receiver has.

  FIG. 53 shows a state where the cared person himself / herself has registered himself / herself as a person having reference authority (reference authority) and a person having registration authority (registration authority). In this state, the corresponding data type in the user information database can be referred to and registered only by the care recipient himself / herself (for example, an administrator, any care staff, the family of the care recipient). Etc.) and requests for registration are rejected.

  The care recipient himself / herself can also register other persons (for example, an administrator, any care staff, the family of the care recipient, etc.) as a person with reference authority and / or a person with registration authority. FIG. 7 shows a state in which a person other than the care recipient is registered as a person having reference authority and / or a person having registration authority. As shown in the figure, in the user information access authority table, for each data type, the reference authority / registration authority is stored in a state associated with the care ID of the user or the like.

  In this example, the data type of “family doctor” is set so that a specific staff A, the user himself / herself, and the user's family can both refer to and register. On the other hand, since there are cases where the user himself / herself does not know about the specific data type, “Birthday”, or “What to expect in the future”, only the user himself / herself can refer to and register. It is set to be able to do. In the figure, the data content column is information for convenience of explaining the content of the data type, not the actual stored content.

  Each data type further includes individual detailed data items. In other words, if it is today's physical condition, it is good, bad or normal, if it is a contact card, if it is a destination, contents, etc., if it is a birth, birth, education, work history or personality, etc. If you are an emergency contact, such as a person who wants to receive care, a place where you want to receive care, the necessity of notification of serious illness, name, relationship, priority, etc. If it is blood pressure / pulse, etc., the date and time, body temperature or SPO2, etc., if it is allergic or contraindicated, items, comments, etc., if it is a family doctor, name of medical institution, department name, doctor name, etc. If it is A3), it will be an evaluation date, an entry person, or a classification.

  The care recipient himself / herself can also delegate the right to appoint the reference authority and / or the registration authority to the family. For example, when the personal ID of the family is temporarily changed as the principal, or when a special appointing authority delegation code is added to the personal ID of the family and the system detects this, the reference authority This can be realized by permitting the registration request of the administrator and / or the registration authority.

  In this way, in the user information access authority table, it is possible to register the access authority (reference authority and / or registration authority) by the care recipient and / or the family to whom the appointment authority is delegated. ing.

<2. Operation of care support information management server>
Next, the operation of the care support information management server will be described with reference to FIGS.

<2.1 Various information registration process>
The operation flow when registering various types of information in the care support information etc. management server 3 via the network 6 from the business operator terminal 7 such as a care business operator will be described with reference to FIG. In the same flow, login processing to the care support system is omitted.

  The staff of the nursing care establishment who has logged into the care support system selects the registration mode through the provider terminal 7 (S101). In response to the mode selection input, a mode display request and the care ID of the currently logged-in staff are transmitted to the care support information management server (S102). Subsequently, the care support information management server determines whether or not there is an information registration authority based on the care ID received in S102 and the registration authority included in the staff information access authority table (S103). If it is determined by the same determination that the staff does not have the authority to register the information (NO in S103), a process when the registration mode is hidden (for example, prohibition of transition to the registration screen) is performed. Ends (S104). On the other hand, when it is determined by the same determination that the staff has the registration authority for the information (YES in S103), the care support information management server 1 displays the registration mode display screen information and the like to display the registration mode on the terminal. Provision is made (S105). The business entity terminal that has received the registration mode display screen information performs registration mode display (S106). Next, the user of the business terminal performs information entry and registration determination processing using the mode display displayed on the business terminal as a guide (S107). When the registration determination process is performed, the information registration request and the registration content are transmitted to the care support information management server (S108). The care support information management server stores the registration content in the staff information database of the storage unit (S109), transmits information storing information to the business operator terminal, and the entered information is registered in the business operator terminal. It is displayed (S110).

  A specific example of the registration processing flow to the staff information database will be described with reference to FIGS.

  FIG. 9 is a screen diagram for explaining a display when registering establishment information such as a care establishment. The figure shows a registration mode screen displayed on the business operator terminal after the registration mode selection and registration authority confirmation (S101 to S105) have been completed (S106). In the detailed display column 20 of the business site master in the center of the screen, the business site name, business site number, business site name abbreviation, postal code, address, telephone number, password validity period, etc. are displayed together with each entry field. . A registration button 21 is displayed at the upper right of the screen. A registrant such as a business office enters appropriate information in each entry field, and then selects the registration button 21 (S107). By selecting this registration button, the registration processing already described is performed (S108 and S109), and the establishment master information is registered in the staff information table in the storage unit of the management server such as the care support information. The external cooperation setting column 23 is a column for setting presence / absence of cooperation with an external system of the care support system 1. Here, an example in the case of cooperation with the regional medical system 2 is shown, and when it is desired to receive the “disease name” and / or “prescription” information from the regional medical system 2, the corresponding check box is displayed. Put a check mark. Details of information acquisition from the regional medical system 2 will be described later.

  FIG. 47 is a diagram showing an example of a setting screen for setting reference authority for a user such as a care recipient, their family, and staff for information created by a care provider or the like. A person with reference authority, such as an administrator, gives the reference authority by operating the screen, so that the information created by the care provider can be permitted to be viewed by users and their families. . Specifically, for the user displayed in the user column 131, a check box 135 is provided for each information item created by a care provider and the registration button is displayed with the check mark 136 in the check box 135. By pressing 137, it is possible to refer to any item. When granting the reference authority to the user himself / herself, the check box 135 of the user's own disclosure information column 132 is displayed. When giving the reference authority to the user family, the check box 135 of the user / family disclosure information column 133 is displayed, When giving a reference authority to the care staff, check boxes 135 in the care staff disclosure information column 134 are selected and checked. The staff may be managed as staff information separately.

  FIG. 48 is a diagram illustrating an example of a setting screen for setting a staff member to which reference authority is set for each user with respect to information about users created by a care provider or the like. A person having a reference authority such as an administrator gives the reference authority by operating the screen, thereby permitting each staff to browse the information. Specifically, for a user displayed in the user column 131, a staff list is displayed in a disclosure target staff column 138 that can be a reference authority grant target, and a check mark 136 is displayed in a check box 135 provided next to the staff name. When the registration button 137 is pressed in the state where “” is entered, the right to refer to information is granted to the corresponding staff regarding the user displayed in the user column 131.

  FIG. 10 is a screen diagram illustrating a display when registering staff (staff) information such as a care establishment. The figure shows a registration mode screen displayed on the business operator terminal after the registration mode selection and registration authority confirmation (S101 to S105) have been completed (S106). The staff master detail display field 22 in the center of the screen includes a staff information entry field 22a and a staff authority setting field 22b. An enlarged view of the staff authority setting column 22b is shown in FIG. In the staff information entry field 22a, the staff number, staff ID, password, end of use, name, kana, contact information, occupation (doctor, nurse, etc.), staff type (general staff, corporate manager, office manager, etc.) Personal information of employees, etc. can be registered. On the other hand, in the staff authority setting field 22b, it is possible to select the authority of the staff member to be registered from among the unusable care support system, only referable (view (cannot be saved)), and registerable (edit (can be saved)) it can. The staff authority can be set when the staff type of the staff member to be registered is a general staff member.

  That is, a manager of a nursing care establishment or a corporation that registers a staff member can individually set the reference / registration authority for various data of the staff member on the setting screen. Thereby, the authority can be managed individually for each information and each staff member, thereby ensuring the safety of the information.

  A registration button 21 is displayed at the upper right of the screen. The registrant enters appropriate information in each entry field, and then selects the registration button 21 (S107). By selecting this registration button, the registration process already described is performed (S108 and S109), and the staff master information is registered together with the authority information in the staff information table of the storage unit of the management server such as the care support information.

  In addition, in this embodiment, it is set as the structure which sets the access authority to the medical information managed by a medical system together with the access authority setting to the care management information (including medical information such as medicine). Therefore, by setting the access right to the medical information on the care support system side, the access right to the medical information on the medical system side can be set at the same time, which makes it easy to set the access right to the medical information. There is an advantage that The access authority may be set separately for the access authority setting for the care support system management information and the access authority for the medical system management information.

  FIG. 12 is a screen diagram illustrating a display when registering a user of the care support network. The figure shows a registration mode screen displayed on the business operator terminal after the registration mode selection and registration authority confirmation (S101 to S105) have been completed (S106). In the detail display field 30 of the user master at the center of the screen, the login ID, password, user name, kana, gender, date of birth, postal code, address, telephone number, medical insurance number, medical insured number, Nursing care insurance number, nursing care insured person number, number of days for notification in case of poor physical condition, etc. are displayed together with each entry column. A registration button 31 is displayed at the upper right of the screen. A registrant such as a business office enters appropriate information in each entry field, and then selects the registration button 31 (S107). By selecting this registration button, the registration process described above is performed (S108 and S109), and the user master information is registered in the staff information table of the storage unit of the management server such as care support information.

  FIG. 13 is a screen diagram for explaining a display when the family of the user of the care support network is registered. The figure shows a registration mode screen displayed on the business operator terminal after the registration mode selection and registration authority confirmation (S101 to S105) have been completed (S106). The detailed display field 32 of the user family master in the center of the same screen includes a login ID, password, name, kana, gender, relationship with the user, telephone number, postal code, address, number of days to be notified in case of poor physical condition, and the like. , Displayed with each entry field. A registration button 33 is displayed on the upper right of the screen. A registrant such as a business office enters appropriate information in each entry field, and then selects the registration button 33 (S107). By selecting this registration button, the registration processing already described is performed (S108 and S109), and the user family master information is registered in the staff information table of the storage unit of the management server such as care support information.

  FIG. 14 is a screen diagram illustrating a display when registering the person in charge of the user of the care support network. The detail display column 34 of the person-in-charge selection master in the center of the screen is provided with a business name abbreviation column, a name column, a disclosure / charge setting column, and a new staff addition button column from the left of the screen. Further, a plurality of new addition buttons 35 are arranged in the new staff addition button row. A registrant such as an office manager activates a registration mode for setting a relationship between a user and a staff member by selecting the new addition button 35 (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server The person-in-charge information is registered in the staff information table of the storage section.

  FIG. 15 is a screen diagram illustrating a display when registering a contact form. The figure shows a registration mode screen displayed on the business operator terminal after the selection of the registration mode made by selecting the contact form list tab 36 and the confirmation of the presence / absence of registration authority (S101 to S105) is completed. (S106). In the registration information detail display field 37, a user selection button 38, a destination, a priority, a contact classification, and contents are displayed together with each entry field. By pressing the user selection button 38, the user (care recipient, etc.) can be set. A temporary save button 39 is displayed at the upper right of the screen. Registrants such as staff at the nursing care facility set the user, destination, priority of the contact form, classification of the content of the communication, enter appropriate information in the content entry field, and then click the registration (or send) button ( (Not shown) is selected (S107). By selecting this registration button, the registration processing described above is performed (S108 and S109), and the contact form information is registered in the staff information table of the storage unit of the management server such as care support information. Note that by selecting the temporary save 39, it is also possible to temporarily save the contact slip being created.

  FIG. 54 is a screen diagram for explaining disclosure setting of a contact form. The communication slip may be used not only between the cared person and the staff but also between the cared person's family and the staff. In such a case, there may be a case where the user's family does not want to show the communication items to the user himself / herself, so the user's family can also set the reference authority for the contact slip. The reference authority can be arbitrarily set by selecting a partner to whom browsing is permitted from the browsing disclosure destination 130, checking the check box 123 and pressing the save button 124. Further, a similar check box may be provided on the contact form creation screen shown in FIG. 15 so that a partner to whom reference authority is given can be appropriately selected for each contact item.

  FIG. 16 is a screen diagram illustrating a display when registering upbringing information or the like. This figure is a screen displayed by selecting the basic information tab 40, and the registration information details display column 41 includes a user selection button 43, place of birth, educational background, work history, history, personality, hobby. Etc. are displayed together with each entry column. When the user selection button 43 is pressed, a user (care recipient, etc.) can be set. An edit button 42 is displayed on the upper right of the screen. A registrant such as an office staff activates a registration mode for registering history information and the like by selecting the edit button 43 (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server The history information and the like are registered in the staff information table of the storage unit.

  FIG. 17 is a screen diagram for explaining a display when registering an emergency contact. In the registration information detail display field 45, a user selection button 46, a new registration button 47, and existing emergency contact information are displayed. The user selection button 46 can set a user (care recipient, etc.) by the selection. In addition, the new registration button 47 displays the entry items and entry fields for new registration of the emergency contact address according to the selection. A registrant such as an office can activate the new registration mode by pressing the new registration button 47 (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server The emergency contact information and the like are registered in the staff information table of the storage unit.

  FIG. 18 is a screen diagram illustrating a display when registering prescription information. In the detailed display column 51 displayed by selecting the medical information tab 50, a user selection button 52, a prescription addition button 53, and existing prescription information are displayed. The user selection button 52 can set a user (care recipient, etc.) by the selection. The prescription addition button 53 activates a new prescription information registration mode according to the selection (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server Prescription information is registered in the staff information table of the storage section.

  It is also possible to register image information as prescription information by selecting the QR reading button 54. According to such image registration, in addition to prescription information prescribed at the hospital, information on medicines prescribed at actual pharmacies, etc. can be recorded. For example, whether the prescribed medicine is generic Etc. can be grasped.

  FIG. 19 is a screen diagram illustrating a display when registering allergies and contraindications. This figure is a screen displayed by selecting the medical information tab 55. In the registration information detail display field 56, a user selection button 57, a new registration button 58, and existing allergy / indication information are displayed. The user selection button 57 can be used to set a user (care recipient, etc.). Further, the new registration button 58 activates a new registration mode for allergy / indication information in response to the selection (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server Allergy and contraindication information is registered in the staff information table of the storage section.

  FIG. 20 is a screen diagram for explaining a display when registering disease name information. This figure is a screen displayed by selecting the medical information tab 59. In the registration information details display field 60, a user selection button 61, a new registration button 62, and existing disease name information are displayed. The user selection button 61 can set a user (care recipient, etc.) by the selection. Also, the new registration button 62 activates a new registration mode for disease name information according to the selection (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server Disease name information is registered in the staff information table of the storage unit.

  FIG. 21 is a screen diagram illustrating a display when registering family doctor information. This figure is a screen displayed by selecting the medical information tab 63. In the detailed information display field 64, a user selection button 65, a new registration button 66, and existing family doctor information are displayed. The user selection button 65 can set a user (care recipient, etc.) by the selection. Further, the new registration button 66 activates a new registration mode of family medical information by the selection (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server Family doctor information is registered in the staff information table of the storage unit.

  FIG. 22 is a screen diagram for explaining a display when registering ADL (Activities of Daily Living) information. This figure is a screen displayed by selecting the care information tab 67. In the detail display column 68, a user selection button 69, an A3 new addition button 70, and existing A3 information are displayed. Here, A3 refers to the ADL evaluation format defined in “All-Health Health Care Management Method-R4 System” provided by the “National Health Service Facility for the Aged”. The user selection button 69 can set a user (care recipient, etc.) according to the selection. The A3 new addition button 70 activates a new registration mode of A3 information by the selection (S101 to S106). By inputting necessary information in the registration mode (not shown) and selecting a registration (setting) button (not shown) (S107), the registration processing already described is performed (S108 and S109), and the care support information management server ADL information is registered in the staff information table of the storage unit.

  With reference to FIG. 23, an operation flow when registering various types of information in the care support information etc. management server 3 from the user terminal 7 such as a care receiver via the network 6 will be described. In the same flow, the login process to the care support system 1 is omitted.

  A user such as a care recipient who logs in to the care support system selects a registration mode through the user terminal (S201). By the input of the mode selection, the mode display request and the care ID of the currently logged-in user are transmitted to the care support information management server (S202). Subsequently, the care support information etc. management server 1 collates the presence or absence of information registration authority based on the care ID received in S202 and the user information table (S203). If it is determined by the collation that the staff does not have the authority to register the information (NO in S203), a process when the registration mode is hidden is performed, and the process ends (S204). On the other hand, if it is determined by the collation that the staff has the authority to register the information (YES in S203), the care support information management server 1 displays the registration mode display screen information and the like to display the registration mode on the terminal. Provision is made (S205). The user terminal that has received the registration mode display screen information performs registration mode display (S206). Next, the user performs information entry and registration determination processing using the mode display displayed on the user terminal as a guide (S207). When the registration determination process is performed, the information registration request and the registration content are transmitted to the care support information etc. management server 1 (S208). The care support information management server 1 stores the registered contents in the user information table of the storage unit 3 (S209), transmits the information storage to the user terminal, and fills in the user terminal The fact that the information has been registered is displayed (S210).

  A specific example of the registration processing flow for the user information table will be described with reference to FIGS. 24 to 33.

  FIG. 24 is a screen diagram illustrating a display example when a user of the care support system 1 such as a care receiver performs today's (that day) physical condition registration processing. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the center of the screen, a character and a balloon are displayed as if the character is speaking, and a text asking about the physical condition of the user is displayed in the balloon. In the lower part of the screen, an option button 80 indicating the degree of physical condition of the user is displayed, and there are three options: “good”, “normal”, and “bad”. When the user selects one of the options displayed on the screen (S207), the above-described registration process can be performed (S208 to S210).

  FIG. 25 is a screen diagram illustrating a display screen when a user of the care support system 1 such as a care receiver performs registration processing of a contact form. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the same screen, an address selection field 81, a content entry field 82, a transmission button 83, and an image selection button 84 are arranged in order from the top of the screen. In the address selection column 81, the address of the contact slip can be determined. In the content entry field 82, the content to be communicated can be entered. According to the selection of the transmission button 83, transmission processing, that is, registration processing to the server such as care support information can be started. In the image selection button 84, for example, an image taken by a terminal can be attached. The user can perform the above-described registration process (S208 to S210) by filling in necessary items and selecting the send button 83 displayed on the screen (S207).

  FIG. 26 is a screen diagram illustrating a display screen when a user of the care support system 1 such as a care receiver performs registration processing of upbringing information and the like. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the display screen 85, entry fields such as birth place, educational background, work history, and background are arranged in order from the top of the screen. The user can perform the above-described registration process (S208 to S210) by filling in necessary items and selecting a registration button (not shown) (S207).

  FIG. 45 is a screen diagram illustrating a display example when the user of the care support system 1 such as a care receiver sets a partner to disclose the registered history information and the like. With respect to the registration information such as upbringing described in FIG. 26, the care giver, the user family, and the like can browse the information by giving the user the reference authority. Specifically, when it is desired to disclose upbringing information, etc. to a caregiver or family member, the disclosure target can be selected from the options “show to person in charge” and “show to family” displayed in the disclosure destination display field 122. By selecting the check box 123 of the item to be displayed and pressing the save button 124 in a state where the check mark 121 is displayed, the history information or the like can be disclosed to any disclosure target.

  FIG. 27 is a screen diagram showing a display screen when a user of the care support system 1 such as a care receiver performs a registration process of information desired in the future. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the same screen, a selection column 86 for a person who wants to receive care and an entry column 87 for a person / place to receive care for are arranged in order from the top of the screen. The user can perform the above-described registration process (S208 to S210) by filling in necessary items and selecting a registration button (not shown) (S207).

  FIG. 28 is a screen diagram illustrating a display screen when a user of the care support system 1 such as a care receiver performs registration processing of emergency contact information. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the display screen 88, columns for name, kana, phone number, mobile phone, zip code, address, and remarks are arranged in order from the top of the screen. The user can perform the above-described registration process (S208 to S210) by filling in necessary items and selecting a registration button (not shown) (S207).

  FIG. 29 is a screen diagram illustrating a display screen when a user of the care support system 1 such as a care receiver performs registration processing of information such as blood pressure and pulse. In the same screen, a list display button group 90, a blood pressure display button 91, a pulse display button 92, an SPO2 display button 93, and the like are displayed in order from the top of the screen (including a blood pressure pulse list, an SPO2 list, a body temperature list, and a weight list). Yes. The user activates a registration mode by selecting a registration processing button (not shown) such as blood pressure / pulse (S201 to S206), fills in necessary items, and selects a registration button (not shown) (S207). ), The above-described registration process can be performed (S208 to S210).

  FIG. 30 is a screen diagram showing a display screen when a user of the care support system 1 such as a care recipient performs a registration process of allergy / contraindication information. By selecting a new button 94 on the same screen, a registration processing screen is displayed (S201 to S206), and the user fills in the displayed registration processing screen and then a registration button (not shown). By selecting, registration processing of allergy / indication information can be performed (S207 to S210).

  FIG. 31 is a screen diagram illustrating a display screen when a user of the care support system 1 such as a care receiver performs registration processing of family medical information. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the display screen 95, an entry field for entering a medical institution name, a department, and a doctor name is displayed in order from the top of the screen. The user can perform the registration process described above (S208 to S210) by filling in the necessary items and selecting the save button 96 (S207).

  FIG. 46 is a screen diagram illustrating a display example when a user of the care support system 1 such as a care receiver permits the family doctor to share information created on the care support system side. When the user himself / herself gives the reference authority by the operation on the screen, the family doctor registered in FIG. 31 can browse the information created on the care support system side. Specifically, for the family doctors who are permitted to view the information created on the care support system side, “XX General Hospital”, “XX Otolaryngology”, and “XX Eye Clinic” displayed in the family doctor display field 128 are displayed. The check box 123 of the item to be disclosed is selected from the choices such as “” and the save button 124 is pressed in a state where the check mark 121 is displayed. Information can be disclosed. Here, examples of the information for giving the reference authority to the family doctor include data on medicines used on the care support system side, data on allergies, ADL data on activity ability, and the like.

  FIG. 32 is a screen diagram showing a display screen when a user of the care support system 1 such as a care receiver performs registration processing of activity ability (A3) information. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the display screen 97, the basic operation, movement method, cognitive function orientation, cognitive function communication, mental activity and their entry fields are displayed in order from the top of the screen. The user can perform the above-described registration process (S208 to S210) by filling in necessary information in each entry field and selecting the save button 98 (S207).

  FIG. 33 is a screen diagram illustrating a display screen when a user of the care support system 1 such as a care receiver performs a disease name information registration process. The screen is a screen that is displayed on the terminal after various registration mode selection processing and registration authority confirmation processing are performed (S201 to S206). In the same screen, a disease name entry field 99, a treatment status selection field 100, an onset time selection field 101, and a remarks entry field 102 are displayed in order from the top of the screen. The user can perform the above-described registration process (S208 to S210) by entering necessary items in each entry field and selecting a save button (not shown) (S207).

  As described above, the user (staff or the like) of the system according to the present embodiment can register various information in the management server for care support information or the like according to the authority given by the administrator.

<2.2 Various information reference processing>
Next, with reference to FIG. 34, a flow in which a staff such as a nursing care facility refers to information in the management server such as a care support information using a terminal such as the facility will be described.

  First, the staff selects an information reference button displayed on a terminal such as an office (S301). With this selection action, the care support information management server receives the reference mode display request and the care ID of the staff, and the user himself / herself has authority to refer to the staff regarding the information of the user that the staff wishes to refer to. It is determined whether or not it is given (S303). When the reference authority is not given to the staff (NO in S303), non-display processing in various modes is performed (S306). When the reference authority is given to the staff (S303 YES), it is subsequently determined whether or not the staff is given the reference authority by the administrator (S304). When the reference authority is not given to the staff (NO in S304), non-display processing in various modes is performed (S306). When the reference authority is given to the staff (YES in S304), the staff can receive the reference information provided from the management server such as care support information, and can display the reference information (S305, S307).

  In this example, the reference authority by the user himself and the reference authority by the administrator are shown in the two-stage confirmation. However, there are additional reference authority granters such as the user's family for the item. In this case, it is possible to refer only when confirmation of three or more levels is performed and all the reference authority is given. On the other hand, when there is only one reference authority for the item, the reference information is provided in one step of confirmation.

  With reference to FIG. 35, the case of referring to the basic information of the user will be specifically described as an example. In the figure, the staff or user who has logged into the care support network 1 first selects the basic information tab 110. By this selection, the user basic information screen 111 is displayed. Thereafter, the staff or user selects the user to be referred to by the user selection button 112 (S301). Then, the reference information is displayed on the staff or user terminal (S306) through the above-described reference authority determination process, reference information providing process, and the like (S302 to S305).

  Here, the reference of the basic information is taken as an example, but various information stored in the management server such as care support information can be referred to according to the authority in the same procedure.

<3. Operation of regional medical server>
The operation of the regional medical system, that is, the browsing flow of medical information will be described with reference to FIG. As described above, in the regional medical system, the electronic medical record information stored in the electronic medical record information server in the same region is browsed from the browsing terminal set in the local medical clinic etc. Can do.

  First, the viewer inputs the login ID and password via the viewing terminal, and transmits them to the regional medical server (S401). The transmitted login ID and password are received by the regional medical server, and an authentication process is performed based on the login ID management table (S402 and S403). If authentication fails, authentication error processing is performed (S404).

  On the other hand, if the authentication is successful, a post-authentication screen is provided and displayed (S405 and S406). Next, the browsing person specifies the browsing target user via the browsing terminal, and transmits the local medical ID of the user to the regional medical server together with the browsing request (S407). In the regional medical server, based on the integrated medical ID associated with the local medical ID between the hospitals, the electronic medical record information corresponding to the user to be browsed is received from each received local medical ID. (S408).

  Each electronic medical record information server that has received the request transmits the electronic medical record information of the browsing target user to the regional medical server (S409 and S410), and then the regional medical server provides the browsing target information to the browsing terminal ( (S411), the browsing terminal displays information on the browsing target person (S412).

  As described above, the regional medical server according to the present embodiment is based on the local medical ID managed by each electronic medical record server and the integrated medical ID corresponding to the local medical ID and set for each region. Therefore, the regional medical server itself does not hold information because it merely mediates information, and thus a regional medical system with high information security is realized.

<4. Cooperation operation between care support information management server and regional medical server>
Next, a cooperative operation between the care support system and the regional medical system will be described.

<4.1 Matching process>
In order to link the care support system and the regional medical system, it is necessary to perform a matching process between the care ID and the integrated medical ID so that the same user is recognized as the same user between the two systems. is there. Hereinafter, this matching process will be described in detail with reference to FIG.

  First, the manager or the like of the business establishment that performs the matching process transmits a candidate request for the cooperation destination system via the business operator terminal (S501). The care support information management server that has received the candidate request for the cooperation destination system provides a cooperation destination candidate (for example, regional medical network A, regional medical network B, etc.) and displays it on the operator terminal (S502 to S504). Next, the administrator selects a cooperation system for which matching processing is to be performed from one or a plurality of cooperation destination candidates displayed on the provider terminal. When the selection is made, a connection request for the cooperation destination system is made from the business operator terminal, and the request is received by the management server such as care support information (S505 and S506). Next, the care support information etc. management server makes a connection request to the selected regional medical server, and after the local medical server performs the authentication process of the care support information etc. management server, it establishes the connection and sends a connection establishment signal. It transmits to management server, such as care support information (S507 thru / or S509).

  After receiving the connection establishment signal (S510), the care support information management server, for the user information selected to be the target of the matching process among the users who have not yet performed the matching process with the regional medical server, An inquiry request by name, gender, and date of birth is transmitted (S511).

  Based on the request, the regional medical server searches the candidate medical information that matches the name, gender, and date of birth from the user information of the regional medical system stored in the regional medical server. The candidate's local medical ID is transmitted to the care support information management server (S512 and S513). After receiving the candidate information and the local medical ID, the care support information management server transmits the candidate information and the integrated medical ID to the business terminal (S514). Based on the unmatched person list transmitted from the management server for care support information, the candidate list, and the integrated medical ID of the candidate, the business entity terminal, the unmatched person, the candidate, and the candidate The medical ID of the person is displayed as a list (S515).

  Thereafter, the manager or the like of the business establishment visually checks the list displayed on the business operator terminal and performs confirmation processing after confirmation (S516). By transmitting this confirmation process to the care support information management server, the care support information management server stores the integrated medical ID of the cooperation destination (S517). Thereby, a correspondence table of care / medical ID is generated in the management server for care support information and the like. After the storage, the care support information etc. management server transmits the storage to the business operator terminal, and the business operator terminal displays the storage completion (S518 and S519).

  According to the matching processing described above, the operator terminal displays the unmatched person list and the correspondence list between the matching candidate information before final confirmation, and waits for the visual confirmation of the administrator etc. before matching. Since it is determined, matching mistakes can be avoided as much as possible. In addition, managers of business establishments that perform matching can select a cooperation destination system, select a target person at once, and a matching candidate list is displayed. The matching process between systems can be performed with a simple process.

  In this embodiment, PDQ based on name, gender, date of birth, etc. is adopted when performing matching processing. However, when common identification information possessed by each system such as My Number exists in advance. The matching process may be performed using the information.

<4.2 Reference processing of medical information on the nursing side>
Next, medical information (for example, prescription information) accumulated in the electronic medical record server on the regional medical system side from the terminal on the care support network side using the care / medical ID correspondence table generated by the matching process described above. The method of referring to the disease name information and the like will be described with reference to FIGS.

  First, the office staff or the like inputs the user to be acquired and the medical information to the company terminal (S601).

  The details of the procedure of the input process will be described with reference to the flow of FIG. 39 and the screen diagram of FIG. The staff of the business office first performs login processing to the care support system (S6011). If the authentication process fails (NO in S6012), login is performed again. If the authentication process is successful (YES in S6012), an initial screen is displayed on the business operator terminal (S6013). Next, after the predetermined operation waiting process (S6014), when the medical information tab 113 is selected (S6015), the medical information display screen 114 is displayed (S6016). When another tab is selected, another display process corresponding to the tab is performed. The medical information display screen includes a user selection button 115, a prescription addition button 116, a QR reading button 117, and the like. After waiting for a predetermined operation (NO in S6017 and S6018), when a user is selected by selecting the user selection button 115 (YES in S6018), a user selection process is performed (S6019).

  Returning to FIG. 38, when the type of medical information desired to be acquired by the input process and the user selection process are performed, a request for medical information is transmitted from the business operator terminal (S602). The care support information management server that has received the request determines whether the staff can refer to medical information (such as prescription and disease name information) based on the reference authority stored in the staff information table ( S604). If it is determined that there is no reference authority (S605), end processing is performed.

  On the other hand, when it is determined that the user has the reference authority, it is checked whether the user who wants to acquire medical information has matched with the local medical system in the past (S606). Here, if the user who wants to acquire the medical information has not performed matching processing with the local medical system in the past, only the information in the management server such as care support information is provided to the operator terminal. A display process is performed (S607). On the other hand, if the user who wants to acquire the medical information has matched with the regional medical system in the past, the user already has a correspondence table of care / medical ID, so the ID information is used. Then, the process proceeds to the subsequent medical information acquisition flow.

  When the user who wants to acquire the medical information has performed matching processing with the local medical system in the past, the management server for care support information, etc. requests the medical information to be acquired and the integrated medical ID to the local medical server. Then, it is transmitted (S608). The regional medical server that has received the transmission content transmits a transmission request for electronic medical record information to one or a plurality of electronic medical record information servers based on the integrated medical ID (S609). Each electronic medical record information server transmits medical information based on the request content transmitted from the regional medical server (S611). The medical information transmitted from each electronic medical record information server is transmitted to the care support information management server via the regional medical server (S612). Upon receiving the medical information, the care support information management server temporarily stores the medical information and performs an integration process for displaying the medical information together with the information in the care support information management server (S613 and S614).

  FIG. 41 is a processing flow of the management server for care support information and the like when performing temporary storage. The data format of the information sent from the regional medical server is a data format recommended by SS-MIX that aims to standardize medical data. Therefore, if stored as it is, the data format may be different from other care support information. Therefore, in the present embodiment, the data received in the data format recommended by SS-MIX (S6141) is first converted into the data format adopted by the care support system (S6142) and then converted. Is temporarily stored in the data format (S6143).

  According to such a configuration, as will be described later, handling of information is simplified when information from the local medical system and information from the care support system are displayed simultaneously for common or similar items. .

  Also, the medical information stored in the care support information management server is only temporarily stored, unlike the information managed by other care support information management servers. Accordingly, information is stored only at the stage where browsing or the like is completed, or until a predetermined condition (e.g., elapse of a predetermined period) is satisfied after browsing. For this reason, medical information is not continuously stored on the care support information management server, and the safety of information is further ensured. In addition, when information is temporarily stored, if the encryption process or the restriction on a part of the menu is used together, the security of information is further secured.

  Note that the configuration for restricting browsing to temporary ones is limited to the above, as is well known to those skilled in the art, as long as the configuration does not allow the management server or terminal for care support information or the like to download or save information. Not.

  Returning to FIG. 38, after the integration process, the care support information management server manages the medical information managed by the local medical system (for example, prescription information acquired from the electronic medical record system) and the care support system. Medical information (for example, prescription information input by a user or the like of the care support system) is provided to the operator terminal (S615). Upon receiving this provision, the business entity terminal simultaneously displays the medical information managed on the side of the regional medical system and the medical information managed on the side of the care support system (S616).

  That is, the staff of the nursing care establishment using the system of the present embodiment selects the medical information tab, so that the medical information provided by the regional medical system or the medical care managed by the care support system Medical information about the user can be referred to seamlessly without being conscious of whether it is information. Thereby, the staff of a nursing care establishment etc. can grasp | ascertain a user's condition more correctly.

<4.3 Care-side information reference processing on the medical side>
Next, processing on the care side when referring to the medical information to be shared generated on the care support network side (hereinafter sometimes referred to as care support system side medical information) from the terminal on the side of the regional medical system Will be described with reference to FIGS. 55 to 60. FIG. Among the information generated on the care support network side, examples of information that can be provided to the regional medical system include ADL evaluation and information on drugs used.

  FIG. 60 is an external cooperation setting registration screen view. The care business side information column 140 shows care site information to be linked, and the linkage information detail column 141 shows information such as the name of the medical system to be linked and the cooperation start date. In addition, the cooperation target item field 142 has a selection field for information items received from the cooperation-destination medical system, and is selected from the medical side by selecting an item to be linked and adding a check mark 145 to the check box 144. It is also possible to set to receive only the information. In general, there are many stricter information handling standards on the medical side than on the nursing side, so there are some nursing establishments that do not like the handling of medical side information. By having such a configuration, there is an advantage that the nursing care facility does not need to receive unnecessary information. In the shared information setting field 143, the extension of the file to be transmitted and the writing frequency can be set for the care support system side medical information shared with the medical side.

  The medical information on the care support system side such as ADL evaluation and used drugs is input by the operation of the terminal 7 such as the user or the terminal 7 such as each care provider, and is registered in the care support information management server. These care support system side medical information may be configured to be sent to the regional medical server immediately after being registered, or may be configured to be sent together at regular intervals. 55 to 57, an example will be described in which care support system side medical information is collectively sent at regular intervals for a plurality of care establishments assigned numbers in order from n = 1. In FIGS. 55 to 59, “care support system side medical information” is represented as “shared data” for convenience of space.

  When the transmission time of the care support system side medical information arrives (S901), in the care support information management server, it is determined whether or not n = 1 establishment has cooperation with the medical system (S902 to S904). ) When the cooperation is performed, a care support system side medical information transmission process described later is performed (YES in S904 and S905). When the care support system side medical information is completed (S905), or when the medical system is not linked (S904 NO), it is determined whether or not the establishment is the last establishment to process. If it is not the last establishment, 1 is added to n and the process about the next establishment is performed, and the process of S903-S906 is repeated until the process regarding all the establishments is completed.

  Next, the care support system side medical information transmission process shown in S905 will be described with reference to FIG. Prior to the transmission of care support system side medical information, the care support information management server requests confirmation that the care support system side medical information about the establishment has been stored in the local medical server that is the transmission destination. (S1001 to S1003). When the stored data does not exist (S1003 NO, S1004), it is determined that the process is the first process, and the initial transmission data determination process (S1005, details will be described later) is performed. It is transmitted to the medical server (S1006, S1010). On the other hand, if there is stored data (S1003 YES), the last update time information of the care support system side medical information on the establishment is notified from the regional medical server (S1007, S1008), and the care support information management server receives it. The difference data of the establishment is created using the last update time information and transmitted to the regional medical server (S1009, S1010). The update frequency of the care support system side medical information shown in FIGS. 55 and 56 can be set in the “write frequency” of the shared information setting field 143 of FIG.

  Next, details of the initial transmission data determination process shown in S1005 will be described with reference to FIG. The figure shows an example in which transmission processing is performed for a plurality of new transmission data numbered sequentially from m = 1 to the regional medical server. First, it is determined whether or not the initial synchronization range is set for the data item of m = 1 (S1101 to S1103, FIGS. 60 to 143), and if the initial synchronization range is set, according to the setting. Data transmission processing is performed (S1103 YES, S1105). On the other hand, if the initial synchronization range is not set for the data item, data transmission processing is performed for the range arbitrarily set by the system (NO in S1103 and S1104). If the data item is not the last processing item after performing the data transmission processing in S1104 or S1105, 1 is added to m and the same processing is performed for the next data item, and processing for all data items is performed. The processing of S1102 to S1106 is repeated until the end. Note that the above-described initial synchronization range can be set in the “initial synchronization range” in the shared information setting field 143 of FIG.

  In addition, if each business location registered in the care support information management server is linked to multiple medical systems, refer to the linked business site table for each medical system to be linked, and May be configured to transmit.

  Next, FIG. 58 shows an example of a configuration in the case where the care support system side medical information registered in the regional medical server by the above-described processing is referred to by the medical side terminal. As a method of using medical information on the care support system side on the medical side, for example, when referring to prescription / disease name data registered in an electronic medical record information server, the care support system side medical information may be displayed side by side. When a browsing request for prescription / disease name data is transmitted from the electronic medical record terminal to the electronic medical record information server (S1201, S1202), is the electronic medical record information server stored with care support system side medical information for the user to be browsed? It is inquired to the regional medical server whether or not (S1203 to S1205). If there is no medical information on the user's care support system side in the regional medical server, the regional medical server notifies the electronic medical record information server to that effect (S1205 NO, S1206), and the electronic medical record information server receives this notification. Only prescription / disease name data is displayed on the electronic medical record terminal (S1207, S1208). On the other hand, when the medical support system side medical information about the user is stored in the local medical server (YES in S1205), the local medical server transmits the user's care support system side medical information to the electronic medical record information server. Then, the electronic medical record information server displays the care support system side medical information on the electronic medical record terminal together with the prescription / disease name data stored in itself (S1211, S1212). At this time, by dividing the screen vertically and horizontally and displaying it, the prescription / disease name data created on the medical side and the ADL data and medication data created on the care side can be viewed side by side.

FIG. 59 shows an example in which the care support system side medical information is not stored in the regional medical server.
When a browsing request for prescription / disease name data is transmitted from the electronic medical record terminal to the electronic medical record information server (S1301, S3202), the electronic medical record information server stores care support system side medical information for the user to be viewed It is inquired to the management server such as care support information via the regional medical server (S1303 to S1307). When there is no medical information on the care support system side of the user in the care support information management server, the regional medical server notifies the electronic medical record information server (S1307 NO, S1308 to S1311), and the electronic medical record information server In response to this notification, only prescription / disease name data is displayed on the electronic medical chart terminal (S1312, S1313). On the other hand, when the care support system side medical information about the user is stored in the care support information management server (YES in S1307), the care support information management server stores the care support system side medical information of the user. The information is transmitted to the electronic medical record information server (S1314-1317), and the electronic medical record information server displays the care support system side medical information on the electronic medical record terminal together with the prescription / disease name data stored in the electronic medical record information server (S1318, S1319). At this time, by dividing the screen vertically and horizontally and displaying it, the prescription / disease name data created on the medical side and the ADL data and medication data created on the care side can be viewed side by side.

  Next, another embodiment of the present invention will be described.

<5. System configuration>
In the present embodiment, the care support information management server acquires medical information directly from each electronic medical record information server. The overall configuration of the system according to the present embodiment will be described in detail below with reference to FIG.

<5.1 Overall system configuration>
FIG. 42 describes the overall configuration of the system according to the present embodiment. In the figure, the same reference numerals are given to the same configurations as those of the above-described embodiment. The difference from the embodiment described above is that there is no regional medical server, and a management server such as care support information is directly connected to the electronic medical record information server of each hospital via the network.

  Note that the contents stored in each server are the same as those in the above-described embodiment, and thus description thereof is omitted here.

<6. Cooperation between the care support information management server and each electronic medical record information server>
<6.1 Matching process>
In order to link the care support system and the electronic medical record information server, it is necessary to perform a matching process between the care ID and the local medical ID so that the same user is recognized as the same user between the two systems. There is. Hereinafter, this matching process will be described in detail with reference to FIG.

  First, the manager or the like of the office that performs the matching process transmits a candidate request for the cooperation destination electronic medical record information server via the company terminal or the like (S701). The care support information management server that has received the candidate request for the cooperation destination electronic medical record information server provides a cooperation destination candidate (for example, electronic medical record information server A, electronic medical record information server B, etc.) and displays it on the operator terminal ( S702 to S704). Next, the administrator selects an electronic medical record information server on which matching processing is to be performed from one or a plurality of cooperation destination candidates displayed on the provider terminal. When the selection is made, a connection request from the business operator terminal to the cooperation destination electronic medical record information server is made, and the request is received by the care support information management server (S705 and S706). Next, the care support information management server makes a connection request to the selected electronic medical record information server, and the electronic medical record information server performs authentication processing of the care support information management server, then establishes a connection and establishes a connection. The signal is transmitted to the care support information management server (S707 to S709).

  After receiving the connection establishment signal (S710), the care support information management server transmits a PDQ request for user information that has not been matched with the electronic medical record information server (S711).

  Based on the PDQ request, the electronic medical record information server searches the user information stored in the electronic medical record information server for a candidate whose name, gender, and date of birth match, and the candidate information and candidate The local medical ID of the person is transmitted toward the care support information management server (S712 and S713). After receiving the candidate information and the local medical ID, the management server for care support information and the like transmits the candidate information and the local medical ID to the business operator terminal (S714). Based on the unmatched person list transmitted from the care support information management server, the candidate list, and the local medical ID of the candidate, the company terminal is configured to match the unmatched person, the candidate, and the candidate. The medical ID of the person is displayed as a list (S715).

  Thereafter, the manager of the business establishment visually checks the list displayed on the business operator terminal and performs confirmation processing after confirmation (S716). By transmitting this confirmation process to the care support information management server, the care support information management server stores the local medical ID of the cooperation-destination electronic medical record information server (S717). Thereby, a correspondence table of care / medical ID is generated in the management server for care support information and the like. After the storage, the care support information etc. management server transmits the information of the storage to the company terminal, and the company terminal displays the storage completion (S718 and S719).

  According to the matching processing described above, the operator terminal displays the unmatched person list and the correspondence list between the matching candidate information before final confirmation, and waits for the visual confirmation of the administrator etc. before matching. Since it is determined, matching mistakes can be avoided as much as possible. In addition, managers of business establishments that perform matching can select a cooperation destination system, select a target person at once, and a matching candidate list is displayed. ID matching between different systems can be performed with simple processing.

  In this embodiment, PDQ based on name, gender, date of birth, etc. is adopted when performing matching processing. However, when common identification information possessed by each system such as My Number exists in advance. The matching process may be performed using the information.

<6.2 Medical information reference processing>
Next, medical information (for example, prescription information and disease name information) accumulated in the electronic medical record server 10 from the terminal 7 on the care support system side using the care / medical ID correspondence table generated by the matching process described above. ) Will be described with reference to FIG.

  First, the staff of the office opens the medical information acquisition page, and inputs the user to be acquired and the medical information to be acquired to the company terminal (S801).

  When the medical information desired to be acquired by the input process and the user selection process are performed, a request for medical information is transmitted from the business terminal (S802). The care support information management server that has received the request determines whether or not the staff can refer to the medical information (such as prescription and disease name information) based on the reference authority stored in the staff information table. (S804). If it is determined that there is no reference authority (S805), end processing is performed.

  On the other hand, if it is determined that the user has the reference authority, it is checked whether the user who wants to acquire medical information has matched with the electronic medical record information server in the past (S806). Here, if the user who wants to acquire the medical information has not performed matching processing with the electronic medical record information server in the past, only the information in the management server such as care support information is displayed on the provider terminal. (S807). On the other hand, if the user who wants to acquire the medical information has matched with the electronic medical record information server in the past, the user already has the correspondence table of the care / medical ID. And proceed to the subsequent medical information acquisition flow.

  When the user who wants to acquire the medical information has performed matching processing with the electronic medical record information server in the past, the care support information management server sends the request for the medical information to be acquired and the local medical ID to the electronic medical record information. This is transmitted to the server (S808). Each electronic medical record information server transmits medical information based on the request content transmitted from the care support information management server (S809 and 810). The medical information transmitted from each electronic medical record information server is transmitted to a care support information management server and temporarily stored (S811).

  If the user who wants to acquire medical information has already been matched with multiple electronic medical record information servers, the above processing is performed until electronic medical record information is acquired from all electronic medical record information servers that have been matched. (S808 to S811) may be repeated.

  Upon receiving the medical information, the care support information management server performs an integration process for integrating the temporarily stored medical information and displaying it together with the medical information in the care support information management server (S812). After the above integration process, the care support information management server manages the medical information managed by the electronic medical record information server (for example, prescription information acquired from the electronic medical record system) and the medical care managed by the care support system. Information (for example, prescription information input by a user or the like of the care support system) is provided to the operator terminal (S813). Upon receiving this provision, the business entity terminal simultaneously displays the medical information managed on the electronic medical record information server side and the medical information managed on the care support system side (S814).

  That is, the staff of the nursing care establishment using the system of the present embodiment selects the medical information tab, and is medical information provided from the electronic medical record information system or managed by the nursing support system. Medical information about the user can be referred to seamlessly without being conscious of the medical information. Thereby, the staff of a nursing care establishment etc. can grasp | ascertain a user's condition more correctly.

  FIG. 61 is a screen diagram when a staff member of a care facility sets and registers disease name information related to a care recipient. The name of the operator who is currently logged in is automatically displayed in the entry field 157, and the operator such as the staff presses the user selection field 151 and selects the user to be edited from the displayed user list. By doing so, it becomes possible to edit the disease name information of the user. In the disease name information registration field 152, information such as a disease name, treatment status, and onset time can be entered, and the user's disease name information can be registered by pressing the registration button 156 after inputting the information. . At this time, by adding a check mark 155 to the check box 154 in the disclosure selection field 153, the registered disease name information can be made undisclosed to the user himself / herself and the family.

  FIG. 62 is a screen diagram when a staff of a care facility or the like sets and registers an emergency contact for a care recipient. The name of the operator who is currently logged in is automatically displayed in the entry field 157, and the operator such as the staff presses the user selection field 151 and selects the user to be edited from the displayed user list. By doing so, it becomes possible to edit the emergency contact information of the user. In the emergency contact information registration field 158, information such as the name of the person to be contacted, the relationship with the user, telephone number, address, priority of the contact, etc. can be entered. By pressing the registration button 156 above, emergency contact information can be registered. At this time, by adding a check mark 155 to the check box 154 of the disclosure selection field 159, the registered emergency contact information can be made non-disclosure to the user himself / herself and the family.

  FIG. 63 is a screen view when a care facility staff or the like sets and registers medical precautions for a care recipient. The name of the operator who is currently logged in is automatically displayed in the entry field 157, and the operator such as the staff presses the user selection field 151 and selects the user to be edited from the displayed user list. This makes it possible to edit the user's treatment precautions. In the treatment precautions column 160, information such as the start date of treatment and precautions for treatment can be input, and the treatment precautions are registered by pressing the registration button 156 after inputting the information. be able to. At this time, by adding a check mark 155 to the check box 154 of the disclosure selection field 159, the registered emergency contact information can be made non-disclosure to the user himself / herself and the family.

  According to the present invention, it is possible to provide a care support system in cooperation with a medical system.

DESCRIPTION OF SYMBOLS 1 Care support system 2 Community medical system 3 Care support information etc. management server 4 Server apparatus 5 Mass storage part 6 Network 7 Terminal 8 Community medical server 9 Network 10 Electronic medical record information server 20 Detailed display column 21 Registration button 22 Detailed display column 23 External link setting field 30 Detailed display field 31 Registration button 32 Detailed display field 33 Registration button 34 Detailed display field 35 New addition button 36 Contact form list tab 37 Detailed display field 38 User selection button 39 Temporary save button 40 Basic information tab 41 Details Display field 42 Edit button 43 User selection button 44 Basic information tab 45 Detailed display field 46 User selection button 47 New registration button 50 Medical information tab 51 Detailed display field 52 User selection button 53 Prescription addition button 54 QR reading button 55 Medical Information tab 5 6 Detailed display column 57 User selection button 58 New registration button 59 Medical information tab 60 Detailed display column 61 User selection button 62 New registration button 63 Medical information tab 64 Detailed display column 65 User selection button 66 New registration button 67 Care information Tab 68 Detailed display column 69 User selection button 70 A3 new addition button 80 Choice button 81 Destination selection column 82 Contents entry column 83 Send button 84 Image selection button 85 Display screen 86 Selection column of person who wants to receive care 87 Care Entry field for the person / location to be requested 88 Display screen 89 Selection button 90 List display button 91 Blood pressure display button 92 Pulse display button 93 SPO2 display button 94 New registration button 95 Display screen 96 Save button 97 Display screen 98 Save button 99 Disease name entry column 100 Treatment Status selection field 101 Disease onset time selection field 102 Remarks entry field 105 Server 106 Storage 107 Electronic medical record terminal 110 Basic information tab 111 Basic user information screen 112 User selection button 113 Medical information tab 114 Medical information display screen 115 User selection button 116 Prescription addition button 117 QR reading button 121 Check mark 122 Disclosure destination display column 123 Check box 124 Save button 128 Medical display column 130 Viewing disclosure destination 131 User column 132 User personal disclosure information column 133 User family disclosure information column 134 Nursing care staff Disclosure information column 135 Check box 136 Check mark 137 Registration button 138 Disclosure target staff column 140 Care business side information column 141 Cooperation information detail column 142 Cooperation target item column 143 Shared information setting column 1 44 Check box 145 Check mark 151 User selection column 152 Disease name information registration column 153 Disclosure selection column 154 Check box 155 Check mark 156 Registration button 157 Entry column 158 Emergency contact information registration column 159 Disclosure selection column 160 Notes column 301 Device 302 Gateway server 801 Device 802 Gateway server 803 Storage

Claims (8)

A care support system comprising a terminal device and a care support information management server for providing medical information and care support information to the terminal device via a network,
The care support information management server
An interface unit for exchanging information with a medical information providing server constituting a medical system in which a predetermined electronic medical record information system is linked;
The care access ID of the user of the care support system, the care support information associated with the care ID, and the access authority of the user of the care support system to the medical information managed by the medical system A storage unit that stores a medical information access authority table that defines a medical information, and an ID correspondence table that associates a medical ID that is an identification ID of a user of the medical system and the care ID with respect to the same user; ,
When a medical information provision request regarding a predetermined person to be browsed is received from the terminal device, whether access to medical information is determined based on the care ID of the user of the terminal device and the medical information access authority table A determination unit for performing
When the determination unit determines that access to medical information is possible, a medical information request including a medical ID is generated based on the care ID of the person to be browsed and the ID correspondence table A request transmitting unit that transmits a medical information request to the medical information providing server via the interface unit;
Based on the medical information request, after receiving the medical system side medical information provided from the medical information providing server via the interface unit, the medical system providing the medical system side medical information to the terminal device An information provider,
Nursing care support system. The storage unit further includes care support system side medical information associated with the care ID,
The care support system according to claim 1, wherein an access authority of the medical information access authority table matches an access authority of the user of the care support system to the medical information on the care support system side. The storage unit further includes care support system side medical information associated with the care ID,
The care support system according to claim 1, wherein the medical information providing unit further provides the care support system side medical information together with the medical system side medical information. The storage unit further includes cooperation availability designation information for designating availability of cooperation with a medical system for each care establishment,
When the care establishment is designated as capable of cooperating with a medical system, a care side medical information providing unit is provided that transmits the care support system side medical information to the medical system that is the cooperation destination. The care support system according to claim 1.   The care support system according to claim 1, wherein medical information provided to the terminal device is provided in a manner that cannot be stored in the terminal device. The care support information management server in a care support system comprising a terminal device and a care support information management server that provides medical information and care support information to the terminal device via a network,
The care support information management server
An interface unit for exchanging information with a medical information providing server constituting a medical system in which a predetermined electronic medical record information system is linked;
The care access ID of the user of the care support system, the care support information associated with the care ID, and the access authority of the user of the care support system to the medical information managed by the medical system A storage unit that stores a medical information access authority table that defines a medical information, and an ID correspondence table that associates a medical ID that is an identification ID of a user of the medical system and the care ID with respect to the same user; ,
When a medical information provision request regarding a predetermined person to be browsed is received from the terminal device, whether access to medical information is determined based on the care ID of the user of the terminal device and the medical information access authority table A determination unit for performing
When the determination unit determines that access to medical information is possible, a medical information request including a medical ID is generated based on the care ID of the person to be browsed and the ID correspondence table A request transmitting unit that transmits a medical information request to the medical information providing server via the interface unit;
Based on the medical information request, after receiving the medical system side medical information provided from the medical information providing server via the interface unit, the medical system providing the medical system side medical information to the terminal device An information provider,
A care support information management server comprising: In a care support system comprising a terminal device and a care support information management server for providing medical information and care support information to the terminal device via a network, a medical information providing method for providing medical information to the terminal device There,
The care support information management server
An interface unit for exchanging information with a medical information providing server constituting a medical system in which a predetermined electronic medical record information system is linked;
The care access ID of the user of the care support system, the care support information associated with the care ID, and the access authority of the user of the care support system to the medical information managed by the medical system A storage unit that stores a medical information access authority table that defines a medical information, and an ID correspondence table that associates a medical ID that is an identification ID of a user of the medical system and the care ID with respect to the same user; , And
When a medical information provision request regarding a predetermined person to be browsed is received from the terminal device, whether access to medical information is determined based on the care ID of the user of the terminal device and the medical information access authority table A determination step for performing
When the determination unit determines that access to medical information is possible, a medical information request including a medical ID is generated based on the care ID of the person to be browsed and the ID correspondence table And a request transmission step of transmitting a medical information request to the medical information providing server via the interface unit;
Based on the medical information request, after receiving the medical system side medical information provided from the medical information providing server via the interface unit, the medical system providing the medical system side medical information to the terminal device An information providing step;
A method for providing medical information. In a care support system comprising a terminal device and a care support information management server that provides medical information and care support information to the terminal device via a network, the server program provides medical information to the terminal device. ,
The care support information management server
An interface unit for exchanging information with a medical information providing server constituting a medical system in which a predetermined electronic medical record information system is linked;
The care access ID of the user of the care support system, the care support information associated with the care ID, and the access authority of the user of the care support system to the medical information managed by the medical system A storage unit that stores a medical information access authority table that defines a medical information, and an ID correspondence table that associates a medical ID that is an identification ID of a user of the medical system and the care ID with respect to the same user; , And
In the care support information management server,
When a medical information provision request regarding a predetermined person to be browsed is received from the terminal device, whether access to medical information is determined based on the care ID of the user of the terminal device and the medical information access authority table A determination step for performing
When the determination unit determines that access to medical information is possible, a medical information request including a medical ID is generated based on the care ID of the person to be browsed and the ID correspondence table And a request transmission step of transmitting a medical information request to the medical information providing server via the interface unit;
Based on the medical information request, after receiving the medical system side medical information provided from the medical information providing server via the interface unit, the medical system providing the medical system side medical information to the terminal device An information providing step;
Server program that executes

Images