Patient information sharing system

Abstract

In one aspect, one objective of the present invention is to provide a new patient information sharing system that enables patient information to be shared in a highly convenient manner in the current situation where mobile devices such as smartphones and tablet devices are widespread. [Solution] The above-mentioned problem is solved by providing a patient information sharing system including an electronic tag and a server device capable of communicating with the electronic tag. In one preferred aspect, the server device includes an acquisition unit that acquires patient information from a memory unit that stores patients and patient information in association with each other, a code generation unit that generates a machine-readable code that can acquire part or all of the acquired patient information, and a transmission unit that transmits the generated machine-readable code to a corresponding electronic tag based on a correspondence table that associates patients with electronic tags, and the electronic tag may include a display unit that displays the machine-readable code received from the server device.

Description

[Technical Field]

[0001] The present disclosure relates to a patient information sharing system. [Background technology]

[0002] A system using bedside terminals is known as a system for sharing patient information in medical institutions (for example, Patent Document 1). By displaying information about the patient's condition and schedules for treatment, examination, rehabilitation, or surgery on a bedside terminal, which can be used to watch television or movies, browse the Internet, etc., hospitalized patients and medical staff can keep track of the patient's condition and schedule at any time, which is extremely convenient. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2012-118782 Summary of the Invention [Problem to be solved by the invention]

[0004] However, despite the fact that bedside terminals are extremely convenient systems, to the inventors' knowledge, only a limited number of medical institutions have introduced them. In medical institutions that do not have bedside terminals, efforts are being made to share information such as conditions or restrictions regarding the patient's movement, posture, excretion, diet, etc., by attaching it to the patient's bedside. Such efforts require a great deal of effort, leading to longer working hours, and may sometimes result in forgetting to attach or change the information, or attaching it incorrectly.

[0005] Despite this, the inventors have conducted extensive research into why bedside terminals have not yet become widespread, and have concluded that one reason may be the widespread use of mobile devices such as smartphones and tablet devices. Compared to when bedside terminals were first developed, high-performance mobile devices have become widespread in recent years, and most hospitalized patients own such devices. Since patients can watch television and movies and browse the internet on their own mobile devices, there is no need for hospitalized patients to use bedside terminals. This means that there is no incentive to incur the costs of installing relatively expensive bedside terminals.

[0006] There is a need for a new medical information sharing system that is suitable for the current situation in which mobile devices such as smartphones and tablet devices are widespread.

[0007] The present invention has been made to solve the problems of the conventional technology described above, and in one aspect, it is an object of the present invention to provide a patient information sharing system that allows patient information to be shared conveniently in the current situation where mobile devices such as smartphones and tablet devices are widespread. [Means for solving the problem]

[0008] In one aspect, the present invention solves the above-mentioned problems by providing a patient information sharing system including an electronic tag and a server device capable of communicating with the electronic tag. The server device an acquisition unit that acquires patient information of a patient from a storage unit that stores patients and patient information in association with each other; a code generation unit that generates a machine-readable code that can acquire part or all of the acquired patient information; and a transmitting unit that transmits the generated machine-readable code to a corresponding electronic tag based on a correspondence table that associates patients with electronic tags; The electronic tag is The device may include a display unit that displays the machine-readable code received from the server device.

[0009] The patient information sharing system according to one aspect of the present invention is based on the entirely new idea of ​​sharing patient information using mobile devices such as smartphones owned by patients, their families, acquaintances, and medical staff as display systems for patient information. As described above, a machine-readable code from which patient information can be obtained is displayed on the display unit of an electronic tag, and patient information is shared by individuals who wish to view the patient information by reading this machine-readable code with their own terminal device. Patients who visit a medical institution, as well as their families, acquaintances, medical staff, etc., can view the patient information on their own familiar terminal device, making it easy to operate and enabling highly convenient patient information sharing.

[0010] Electronic tags are small display devices with a display unit made of electronic paper. For example, in the retail and logistics fields, they are used as electronic shelf labels to improve dynamic pricing and inventory management efficiency. Electronic tags are small and much cheaper than LCDs, making them easy to implement in terms of space and cost. However, due to their small size, the amount of information that can be displayed on their display unit is limited. While sufficient for use as price tags, they are not suitable for displaying patient information required in medical institutions. In contrast, a patient information sharing system according to one aspect of the present invention enables efficient sharing of patient information via electronic tags by using terminal devices owned by patients, their families, acquaintances, medical staff, etc. as the primary display system for patient information, rather than directly displaying patient information on electronic tags. This system uses electronic tags as a bridge between the terminal devices and a server device. In a patient information sharing system according to one aspect of the present invention, the electronic tag may be anything that is placed in correspondence with and / or assigned to a patient, and may be attached to or included in, for example, a name tag, a wristband, a bedside table, a bed, a wall of a hospital room, etc. The electronic tag may have appropriate attachment means for these objects.

[0011] There are no particular restrictions on the patient information to be shared, and appropriate patient information can be shared as needed. For example, the information may include, but is not limited to, the patient's medical information, such as the patient's attribute information or information about the patient's life in the hospital. Patient medical information may include, but is not limited to, the ward, room, attending nurse, attending physician, schedules for tests, treatments, rehabilitation, and surgeries; patient condition information including vital signs such as blood pressure, pulse rate, respiratory rate, blood oxygen level, and body temperature; medication information; messages from medical staff; information regarding the patient's movement, posture, excretion, and conditions or restrictions imposed on food or drink; and information regarding the patient's risk of falling. Patient attribute information may include, but is not limited to, the patient's name, patient ID, and gender. Information regarding the patient's life in the hospital may include, but is not limited to, information regarding reservations or use of hospital facilities such as a beauty salon, laundry, and convenience store; and information regarding meal menu selection. Such patient information may be part or all of an electronic medical record or nursing record, or part or all of information stored in other hospital systems.

[0012] A machine-readable code refers to code information that can be read by a terminal device such as a smartphone or tablet. The code information can be in any form as long as it is readable by a terminal device such as a smartphone or tablet, such as a two-dimensional code. The two-dimensional code can be a stacked two-dimensional code or a matrix two-dimensional code. Examples of stacked two-dimensional codes include, but are not limited to, PDF417, Micro PDF417, Code49, and Code16K. Examples of matrix two-dimensional codes include, but are not limited to, QR Code, Micro QR Code, Veri Code, Data Matrix Code, Maxi Code, Code1, and Aztec Code. These machine-readable codes can be read by a terminal device with a camera, such as a mobile phone, smartphone, or tablet.

[0013] It is not clear to humans what the machine-readable code means at a glance. In other words, if the machine-readable code is displayed on the display unit of the electronic tag and the patient information is acquired by a terminal device by reading the machine-readable code, a third party will not be able to immediately ascertain the patient information by simply glancing at the electronic tag. Therefore, it is possible to efficiently share patient information while reducing the risk that relatively private patient information, such as the patient's age, weight, and other patient condition information, or the patient's schedule, will become known to a third party.

[0014] The machine-readable code from which patient information can be obtained means a machine-readable code from which the patient information can be obtained in a terminal device that reads the machine-readable code. The machine-readable code from which patient information can be obtained may basically be any type as long as it is a machine-readable code from which the patient information can be obtained in a terminal device that reads the machine-readable code, but it may be, for example, a machine-readable code that contains encoded patient information. That is, in a preferred embodiment, the machine-readable code generated by the code generation unit may contain, in encoded form, some or all of the patient information acquired by the acquisition unit.

[0015] The machine-readable code containing encoded patient information means a machine-readable code that can obtain the patient information by decoding the machine-readable code. If the machine-readable code displayed on the display unit of the electronic tag is a machine-readable code containing encoded patient information, the patient information can be obtained on a terminal device that reads the machine-readable code without going through a server device.

[0016] The above-described embodiment, in which patient information is encoded and included in the machine-readable code, is particularly advantageous in emergencies such as accidents and disasters, when access to a server device may be restricted. In emergencies such as accidents and disasters, nurses, doctors, or rescue workers who are not usually responsible for caring for a patient may be required to provide care. However, it is difficult to confirm the patient's information, condition, and care instructions with the patient's caregiver, or to review the patient's nursing records. In such cases, care must be provided blindly while appropriately interviewing the patient. In contrast, when patient information is encoded and included in the machine-readable code information displayed on the display unit of an electronic tag, the patient information can be viewed on a terminal device by reading the machine-readable code. This allows nurses, doctors, rescue workers, and others who rush to the scene of an accident or disaster to access the necessary information and provide care to the patient. Electronic tags are typically powered by a built-in battery, allowing them to continue displaying predetermined information even when power supply is limited, such as during an accident or disaster.

[0017] When patient information is encoded and included in the machine-readable code, there are no particular limitations on the type of patient information encoded and included in the machine-readable code and it can be all or part of an electronic medical record or nursing record. Preferably, the information includes, for example, information regarding conditions or restrictions imposed on the patient's movement, posture, excretion, diet, or beverages, and medical information regarding the patient's risk of falling. These conditions or restrictions are important information that, if not observed, could have a serious impact on the patient. This information should be shared with everyone involved in the patient's care, including the patient themselves, medical staff such as doctors and nurses, family members, and acquaintances, including in emergencies. The information may also include, for example, precautions for medical staff, such as "Do not treat the right upper limb," the presence and type of allergies or infections, whether or not a carbohydrate restriction is in place, the presence and type of medications being taken, and information regarding the individual patient's risk of falling, expressed numerically or symbolically, which can be obtained by conducting a survey known as a fall assessment for each patient.

[0018] On the other hand, in a preferred embodiment, the machine-readable code may include information for transitioning a display screen of a terminal device that has read the machine-readable code to a patient information viewing screen for confirming the patient information. That is, in a preferred embodiment, the server device constituting the patient information sharing system according to one aspect of the present invention comprises: a patient information viewing screen generating unit that generates a patient information viewing screen for confirming a part or all of the patient information acquired by the acquiring unit, The machine-readable code may include information for transitioning the display screen of the terminal device that reads the machine-readable code to the patient information viewing screen.

[0019] The information for transitioning the display screen of the terminal device that reads the machine-readable code to the patient information viewing screen is not particularly limited as long as it can transition the display screen of the terminal device that reads the machine-readable code to the patient information viewing screen, but may be, for example, information for causing the terminal device that reads the machine-readable code to send a delivery request for the patient information viewing screen to the server device. Such information may be, for example, link information for transitioning to the patient information viewing screen.

[0020] The server device, which receives a request for delivery of a patient information viewing screen from a terminal device that reads the machine-readable code, transmits the patient information viewing screen generated by the patient information viewing screen generation unit to the terminal device that sent the delivery request. That is, in a preferred embodiment, a server device constituting a patient information sharing system according to an aspect of the present invention may include a receiving unit that receives a request for delivery of a patient information viewing screen from a terminal device, and a transmitting unit that transmits the patient information viewing screen generated by the patient information viewing screen generation unit to the terminal device that sent the received delivery request.

[0021] When a patient information sharing system according to one aspect of the present invention is equipped with the above-described configuration for displaying a patient information viewing screen via a server, it becomes possible to share and check more detailed and diverse patient information without being limited by the amount of information that can be incorporated into machine-readable code.

[0022] In a preferred embodiment, the patient information sharing system according to an aspect of the present invention may be configured to output a patient screen for the patient to check and / or input patient information. That is, in a preferred embodiment, the server device constituting the patient information sharing system according to an aspect of the present invention comprises: a patient screen generation unit that generates a patient screen for a patient to confirm a part or all of the patient information acquired by the acquisition unit and / or for a patient to input patient information; The machine-readable code may include information for transitioning the display screen of the terminal device that reads the machine-readable code to the patient screen.

[0023] The information for transitioning the display screen of the terminal device that read the machine-readable code to the patient screen is not particularly limited as long as it can transition the display screen of the terminal device that read the machine-readable code to the patient screen, but may be, for example, information for causing the terminal device that read the machine-readable code to send a request for delivery of the patient information screen to the server device. Such information may include, for example, link information for transitioning to the patient screen.

[0024] The server device, which receives a patient screen delivery request from the terminal device that read the machine-readable code, transmits the patient screen generated by the patient screen generation unit to the terminal device that sent the delivery request. That is, in a preferred embodiment, a server device constituting a patient information sharing system according to an aspect of the present invention may include a receiving unit that receives a patient screen delivery request from a terminal device, and a transmitting unit that transmits the patient screen generated by the patient screen generation unit to the terminal device that sent the received delivery request.

[0025] The patient information input on the patient screen may be stored in the storage unit that stores the patient and the patient information in association with each other by an appropriate means. For example, the server device may include an acquisition unit that acquires the patient information input on the patient screen from a terminal device, and a means for recording the acquired patient information in the storage unit.

[0026] There are no particular limitations on the type of patient information displayed on the patient screen. For example, appropriate patient information may be displayed as needed by referring to the patient information item information displayed on the patient screen. Specific examples of patient information have been described above. Patient information that may be input on the patient screen may include, but is not limited to, contact information for doctors and nurses, information regarding reservations and / or use of hospital facilities, and information regarding meal selection. Information regarding reservations and / or use of hospital facilities may include, but is not limited to, information regarding reservations and payments for beauty salons, barber shops, laundry facilities, etc., and information regarding orders and payments to shops and vendors. Information regarding meal selection may include, for example, information regarding menu selection. If hospitalized patients could input this information using their own terminal devices, the convenience of their hospital stay could be significantly improved.

[0027] In a preferred embodiment, the server device constituting the patient information sharing system according to one aspect of the present invention comprises: an acquisition unit that acquires patient authentication information for authenticating a patient from a terminal device when a request for delivery of the patient screen is received from the terminal device; The device may include a determination unit that determines whether the acquired patient authentication information matches pre-stored patient authentication information, and a transmission unit that transmits the patient screen to the terminal device when the determination unit determines that the patient authentication information matches the pre-stored patient authentication information.

[0028] The patient authentication information for authenticating a patient is stored in association with the patient identification information and may be essentially any information that can verify that access from a terminal device is from a legitimate user (i.e., a patient), such as a patient ID, a patient name, a patient name and date of birth, a password, biometric information, or a combination of these. The biometric information may be, for example, biometric information obtained from the patient's fingerprint, iris, voiceprint, face, etc., but is not limited to these. The patient authentication information may be transmitted from the terminal device to the server device together with a request for delivery of a patient screen. Alternatively, the server device may be configured to transmit a request for inputting patient authentication information (e.g., an input screen for patient authentication information) to the terminal device after receiving the request for delivery of a patient screen, and then receive impression information (e.g., a password entered via the input screen for patient authentication information) from the terminal device.

[0029] When the server device acquires patient authentication information for authenticating a patient from a terminal device, it determines whether the acquired patient authentication information matches pre-stored patient authentication information, thereby determining whether access from the terminal device is legitimate. This reduces the risk of a third party entering patient information via the patient screen or disclosing highly private patient information, thereby improving security. The pre-stored patient authentication information may be stored in a storage unit possessed by the server device, or may be stored in another storage device accessible by the server device.

[0030] In a preferred embodiment, the patient information sharing system according to one aspect of the present invention may be configured to output a screen for medical staff, such as nurses, licensed practical nurses, and doctors, to check and / or input patient information. That is, in a preferred embodiment, the server device constituting the patient information sharing system according to one aspect of the present invention may: a medical staff screen generation unit that generates a medical staff screen for a medical staff member to confirm a part or all of the patient information acquired by the acquisition unit and / or for a medical staff member to input patient information; The machine-readable code may include information for transitioning the display screen of the terminal device that reads the machine-readable code to the medical staff screen.

[0031] The information for transitioning the display screen of the terminal device that reads the machine-readable code to the medical staff screen is not particularly limited as long as it can transition the display screen of the terminal device that reads the machine-readable code to the medical staff screen, but may be, for example, information for causing the terminal device that reads the machine-readable code to send a delivery request for the medical staff screen to the server device. Such information may include, for example, link information for transitioning to the medical staff screen.

[0032] The server device, upon receiving a request for distribution of a medical staff screen from a terminal device that reads the machine-readable code, transmits the medical staff screen generated by the medical staff screen generation unit to the terminal device that transmitted the distribution request. That is, in a preferred embodiment, a server device constituting a patient information sharing system according to an aspect of the present invention may include a receiving unit that receives a request for distribution of a medical staff screen from a terminal device, and a transmitting unit that transmits the medical staff screen generated by the medical staff screen generation unit to the terminal device that transmitted the received distribution request.

[0033] The patient information input on the medical staff screen may be stored in the storage unit that stores the patient and the patient information in association with each other by appropriate means. For example, the server device may include an acquisition unit that acquires the patient information input on the medical staff screen from a terminal device, and a means for recording the acquired patient information in the storage unit.

[0034] There are no particular limitations on the type of patient information displayed on the medical staff screen. For example, appropriate patient information may be displayed as needed by referencing the patient information items displayed on the medical staff screen. Specific examples of patient information are as described above. Patient information that can be viewed or entered on the medical staff screen may include, but is not limited to, information about examinations, surgeries, procedures, contact information for other nurses or doctors, rehabilitation, medication, and nutritional guidance. Examination information may include, but is not limited to, the history, results, or schedule of examinations such as blood tests, CT scans, X-rays, and MRI scans. Surgery information may include, but is not limited to, the history, results, or schedule of surgeries such as laparotomy and thoracotomy. Treatment information may include, but is not limited to, the history, results, or schedule of treatments such as hemostasis, wound treatment, and burn treatment. Rehabilitation information may include, but is not limited to, information about rehabilitation history, status, and schedule. Medication information may include, but is not limited to, prescriptions, medication, and medication history, status, or schedule. Conventionally, medical staff such as nurses and doctors make rounds with a dedicated computer on a cart to check or input patient information, or they only take notes during their rounds and input the necessary information into electronic medical records or nursing records when they return to the nurse's station, etc. In contrast, with the patient information sharing system according to one aspect of the present invention, medical staff can view and input patient information using a terminal device they carry with them, which can significantly improve the convenience of daily medical examinations and nursing work.

[0035] In a preferred embodiment, the server device constituting the patient information sharing system according to one aspect of the present invention comprises: an acquisition unit that acquires, when receiving a request for delivery of the medical staff screen from a terminal device, medical staff authentication information for authenticating the medical staff from the terminal device; The medical staff authentication information acquisition unit may include a determination unit that determines whether the acquired medical staff authentication information matches pre-stored medical staff authentication information, and a transmission unit that transmits the medical staff screen to the terminal device when the determination unit determines that the medical staff authentication information matches the pre-stored medical staff authentication information.

[0036] The medical staff authentication information for authenticating medical staff may be basically any information that can identify individual medical staff and can confirm that access from a terminal device is from a legitimate user (i.e., medical staff), and may be, for example, a staff ID, a name, a name and date of birth, a password, biometric information, or a combination of these. The biometric information may be, for example, biometric information obtained from the medical staff's fingerprint, iris, voiceprint, face, etc. The medical staff authentication information may be transmitted from the terminal device to the server device together with a request for delivery of a medical staff screen. Alternatively, when the server device receives a request for delivery of a medical staff screen, the server device may transmit a request for inputting medical staff authentication information (e.g., an input screen for medical staff authentication information) to the terminal device and receive medical staff authentication information (e.g., a combination of medical staff identification information and a password entered via the input screen for medical staff authentication information) from the terminal device.

[0037] When the server device acquires medical staff authentication information for authenticating a medical staff from a terminal device, the server device determines whether the acquired medical staff authentication information matches pre-stored medical staff authentication information, and determines whether the access from the terminal device is legitimate. This reduces the risk of a third party entering patient information or exposing highly private patient information, thereby improving security. The pre-stored medical staff authentication information may be stored in a storage unit of the server device, or may be stored in another storage device accessible to the server device.

[0038] In a preferred embodiment, the patient information sharing system according to the present invention may be configured such that the correspondence between the electronic tag and the patient can be edited via a terminal device, preferably a terminal device of a medical staff member. a correspondence table editing screen generating unit that generates a correspondence table editing screen for editing the correspondence table that associates patients with electronic tags; The machine-readable code may include information for transitioning the display screen of the terminal device that reads the machine-readable code to the correspondence table editing screen.

[0039] The information for transitioning the display screen of the terminal device that reads the machine-readable code to the correspondence table editing screen is not particularly limited as long as it can transition the display screen of the terminal device that reads the machine-readable code to the correspondence table editing screen, but may be, for example, information for causing the terminal device that reads the machine-readable code to send a distribution request for the correspondence table editing screen to the server device. Such information may include, for example, link information for transitioning to the correspondence table editing screen.

[0040] The server device, which receives a correspondence table editing screen distribution request from the terminal device that read the machine-readable code, transmits the correspondence table editing screen generated by the correspondence table editing screen generation unit to the terminal device that sent the distribution request. That is, in a preferred embodiment, a server device constituting a patient information sharing system according to an aspect of the present invention may include a receiving unit that receives a correspondence table editing screen distribution request from a terminal device, and a transmitting unit that transmits the correspondence table editing screen generated by the correspondence table editing screen generation unit to the terminal device that sent the received distribution request.

[0041] The correspondence table associating patients with electronic tags can be changed by appropriate means based on the correspondence between patients and electronic tags entered on the correspondence table editing screen. For example, the server device may include an acquisition unit that acquires the correspondence between patients and electronic tags entered on the correspondence table editing screen from a terminal device, and a modification unit that changes the correspondence table based on the acquired correspondence. The correspondence between patients and electronic tags can be, for example, a combination of patient identification information that identifies the patient and electronic tag identification information that identifies the electronic tag, but is not limited to this as long as it is possible to associate patients with electronic tags.

[0042] According to the above configuration, which allows editing of a correspondence table that associates electronic tags with patients from a terminal device, for example, when an electronic tag is distributed to a patient, when the patient uses a bedside table, bed, etc. equipped with an electronic tag for the first time, the patient and electronic tag can be associated using the terminal device and the electronic tag, for example, in front of the patient, which is extremely convenient.

[0043] In a preferred embodiment, the server device constituting the patient information sharing system according to an aspect of the present invention comprises: an acquisition unit that acquires medical staff authentication information for authenticating a medical staff member from the terminal device when receiving a request to distribute the correspondence table editing screen; The system may include a determination unit that determines whether the acquired medical staff authentication information matches pre-stored medical staff authentication information, and a transmission unit that transmits the correspondence table editing screen to the terminal device when the determination unit determines that the medical staff authentication information matches the pre-stored medical staff authentication information. This reduces the risk that a third party other than legitimate medical staff will edit the correspondence table, thereby improving security. The pre-stored medical staff authentication information may be stored in a storage unit included in the server device, or may be stored in another storage device accessible to the server device.

[0044] In a preferred embodiment, the electronic tag may display patient information in addition to the machine-readable code. That is, in a preferred embodiment, the transmission unit of the server device constituting the patient information sharing system according to one aspect of the present invention may be a transmission unit that transmits to the electronic tag, in addition to the generated machine-readable code, some or all of the patient information acquired by the acquisition unit, and the display unit of the electronic tag may be a display unit that includes a first display area that visually displays the patient information received from the server device and a second display area that displays the machine-readable code received from the server device. That is, in the patient information sharing system according to one aspect of the present invention, the display unit of the electronic tag includes a first display area and a second display area, and the first display area visually displays patient information and the second display area displays a machine-readable code from which patient information can be acquired.

[0045] "Readable" means that the content can be understood by looking at the display. In other words, "readably displayed" patient information means that the patient information is displayed in a manner that allows the patient to understand the content by looking at the display. For example, displays that are incomprehensible to humans, such as two-dimensional codes, are not included in readable displays. The specific display method is not particularly limited as long as the content can be understood by looking at the display. Readable displays do not necessarily have to be text but can be text, symbols, figures, colors, or combinations thereof, such as pictograms. Displaying patient information as pictograms makes it possible to share necessary patient information with high visibility even when using a display device with a relatively small display area, such as an electronic tag. Information that can be displayed as pictograms in the first display area can include, but is not limited to, information on conditions or restrictions regarding the patient's movement, posture, excretion, diet, etc.

[0046] In a preferred embodiment, the server device constituting the patient information sharing system according to an aspect of the present invention may include a determination unit that determines whether or not the patient information needs to be displayed in a visible manner, and the transmission unit included in the server device may be a transmission unit that transmits, as patient information, the patient information that the determination unit determines needs to be displayed in a visible manner to an electronic tag. There are no particular limitations on the specific means for determining whether or not the patient information needs to be displayed in a visible manner, and for example, the determination may be made based on a correspondence table that associates each item of patient information with whether or not the patient information needs to be displayed in a visible manner.

[0047] Furthermore, there are no particular limitations on the specific information processing method in the server device, as long as the transmitting unit transmits the patient information that the determining unit has determined to require a visible display. For example, the acquiring unit may select, from the patient information acquired, the patient information that the determining unit has determined to require a visible display, and transmit the selected patient information to an electronic tag, or the acquiring unit may selectively acquire, from the storage unit, the patient information that the determining unit has determined to require a visible display, and transmit the acquired patient information to an electronic tag.

[0048] Meanwhile, in a preferred embodiment, the server device constituting the patient information sharing system according to one aspect of the present invention may include a determination unit that determines whether or not patient information needs to be coded, and the code generation unit included in the server device may be a code generation unit that generates a machine-readable code capable of acquiring the patient information determined by the determination unit to need coding. There are no particular limitations on the specific means for determining whether or not patient information needs to be coded. For example, the determination may be based on a correspondence table that associates each patient information item with whether or not coding is required. Note that the correspondence table that associates each patient information item with whether or not coding is required and the correspondence table that associates each patient information item with whether or not a visible display is required may be a single correspondence table. That is, the correspondence table may associate each patient information item with whether or not coding is required and whether or not a visible display is required.

[0049] Furthermore, there are no particular limitations on the specific information processing method in the server device, as long as the code generation unit can generate a machine-readable code that can acquire the patient information that the determination unit has determined to require coding. For example, the acquisition unit may be configured to acquire the patient information that the determination unit has determined to require coding from the storage unit and generate a machine-readable code based on the acquired patient information, or may be configured to select the patient information that the determination unit has determined to require coding from the patient information acquired by the acquisition unit and generate a machine-readable code based on the selected patient information.

[0050] In yet another aspect, the present invention solves the above problem by providing a server device included in the above-mentioned patient information sharing system, and a computer program for causing a computer to function as the server device. [Effects of the Invention]

[0051] According to the present invention, patient information can be shared more conveniently using a method suited to the current situation in which mobile devices such as smartphones and tablet devices are widespread. [Brief explanation of the drawings]

[0052] [Figure 1] 1 is a conceptual diagram showing the overall configuration of a patient information sharing system 100. FIG. [Figure 2] 10 is a diagram showing an example of a correspondence table that associates each item of patient information with whether coding is required and whether a visible display is required. FIG. [Figure 3] FIG. 10 is a diagram showing an example of a correspondence table that associates patients with electronic tags. [Figure 4] 10A and 10B are diagrams showing examples of information displayed on the display unit of an electronic tag and a display method thereof; [Figure 5] FIG. 10 is a diagram showing an example of a start screen and information displayed thereon. [Figure 6] FIG. 10 is a diagram showing an example of a code reading screen and information displayed thereon. [Figure 7] FIG. 10 is a diagram showing an example of a patient information viewing screen and information displayed thereon. [Figure 8] FIG. 10 is a diagram showing an example of a patient information viewing screen and information displayed thereon. [Figure 9] FIG. 10 is a diagram showing an example of a patient authentication information input screen and information displayed thereon. [Figure 10] FIG. 10 is a diagram showing an example of a patient screen and information displayed thereon. [Figure 11] FIG. 10 is a diagram showing an example of a medical staff authentication information input screen and information displayed thereon. [Figure 12] FIG. 10 is a diagram showing an example of a screen for medical staff and information displayed thereon. [Figure 13] FIG. 10 is a diagram illustrating an example of a correspondence table that associates patients with vital data. [Figure 14] FIG. 10 is a diagram showing an example of a vital signs screen and information displayed thereon. [Figure 15] FIG. 10 is a diagram showing an example of a vital sign input screen and information displayed thereon. [Figure 16] 10A and 10B are diagrams showing an example of a correspondence table editing screen and information displayed thereon. DETAILED DESCRIPTION OF THE INVENTION

[0053] Hereinafter, a medical information sharing system according to one aspect of the present invention will be described in more detail based on an embodiment, but it goes without saying that the present invention is not limited to the embodiment.

[0054] Fig. 1 is a conceptual diagram showing the overall configuration of a patient information sharing system 100 according to one embodiment of the present invention. As shown in Fig. 1, the patient information sharing system 100 according to one embodiment of the present invention includes a server device S1 and electronic tags E1, E2, and E3. The electronic tags E1, E2, and E3 are electronic tags that are arranged corresponding to or assigned to patients P1, P2, and P3, and are connected to the server device S1 via a network N. The network N may be, for example, the Internet, a LAN (Local Area Network), a telephone line, or a dedicated line, but is not limited to these.

[0055] <Electronic tags> The electronic card E1 is a card-shaped display device with a display unit made of electronic paper. Functionally, the electronic card E1 includes a display unit E11, a memory unit E12, a communication unit E13, a control unit E14, and a battery E15.

[0056] The display unit E11 is a means for displaying various information received by the electronic tag E1 from the server device. Functionally, the display unit E11 has a first display area E111 and a second display area E112. Patient information is displayed in a viewable manner in the first display area E111, and machine-readable code from which the patient information can be obtained is displayed in the second display area E112. The display unit E11 is typically made up of electronic paper.

[0057] The memory unit E12 is primarily a means for storing patient information and machine-readable codes displayed on the display unit E11, and conceptually includes a patient information memory unit that stores patient information displayed in the first display area E111, and a machine-readable code memory unit that stores machine-readable codes displayed in the second display area E112. The memory unit E12 is a storage medium that the electronic tag E1 has as hardware, and may be, for example, but is not limited to, a flash memory, a RAM (Random Access Memory), a ROM (Read-Only Memory), an EEPROM (Electrically Erasable Programmable Read-Only Memory), or a combination of these.

[0058] The communication unit E13 is primarily a means for communicating with the server device, and is a means for receiving, for example, patient information and machine-readable codes. The patient information and machine-readable codes received from the server device via the communication unit E13 are stored in a patient information storage unit and a machine-readable code storage unit, respectively, included in the storage unit E12.

[0059] The control unit E14 is a means for controlling the operation of the electronic tag and includes, for example, a CPU. The control unit E14 executes the program stored in the storage unit E12 and displays the information stored in the patient information storage unit and the machine-readable code in the first display area and the second display area of ​​the display unit E11, respectively.

[0060] The configuration of electronic tags E2 and E3 is the same as that of electronic tag E1, so a detailed description will be omitted. Furthermore, electronic tags E1 to E3 may have configurations other than those described above. There are no particular restrictions on the size of electronic tags, and they may be, for example, 1.5 inches to 10.2 inches, but typically 1.5 inches to 6.0 inches.

[0061] <Server device> The server device S1 is an information processing device that operates in cooperation with the electronic tags E1, E2, and E3. The server device S1 may be a single server device, or may be multiple server devices. For example, it may be server devices distributed over a network such as a cloud server. The server device may be managed by a medical institution or a management company.

[0062] The server device S1 conceptually includes a storage unit S11, a communication unit S12, and a control unit S13. It goes without saying that the server device S1 may include other components, such as a display unit or the like, an input unit or the like, such as a keyboard, etc.

[0063] The storage unit S11 is a means for storing information necessary for various processes executed by the server device S1. The storage unit S11 may be a volatile memory or a non-volatile memory. Specifically, the storage unit S11 may be, for example, a hard disk drive (HDD), a solid state drive (SSD), a cache memory, a buffer memory, a flash memory, or the like, but is not limited to these.

[0064] In this example, the storage unit S11 is a storage unit included in the server device S1, but as long as the server device S1 can connect to it at any time and read data, the storage unit S11 does not necessarily have to be a storage unit included in the server device S1. For example, one or more storage devices, or parts thereof, that are connected to the server device S1 directly or via the network N and exist independently of the server device S1 may be used as the storage unit S1. Furthermore, if other server devices or storage devices exist within the network of the medical institution to which the server device S1 can connect, some or all of their storage units may be used as the storage unit S1. The above-mentioned server devices and / or storage devices may include both on-premise servers and storages and cloud-based servers and storages.

[0065] The communication unit S12 is a means for transmitting or receiving various types of information via an appropriate network, and is configured to include, for example, a LAN (Local Area Network) card, a network card, etc. For example, the communication unit S12 transmits various types of data such as patient information and machine-readable codes to electronic tags E1, E2, and E3 via the network N. The communication unit S12 also acquires patient information via the network N from a storage unit that stores patients and patient information in association with each other.

[0066] The control unit S13 is a means for controlling the operation of the server device S1 and is configured to include, for example, one or more central processing units (CPUs), micro processing units (MPUs), graphics processing units (GPUs), etc. The control unit S13 appropriately reads out programs stored in the storage unit S11, etc., and executes various processes. For example, the control unit S13 conceptually includes, functionally, a machine-readable code generation unit S13a, a patient information viewing screen generation unit S13b, a patient screen generation unit S13c, a medical staff screen generation unit S13d, a correspondence table editing screen generation unit S13e, etc.

[0067] The patient information sharing system 100 according to one embodiment of the present invention will be described in more detail below with reference to its operation.

[0068] <Action 1 - Displaying patient information and machine-readable code on an electronic tag and viewing it on a mobile device> In FIG. 1, P1, P2, and P3 are patients identified by patient IDs "0001," "0002," and "0003," respectively, and are assigned electronic tags E1, E2, and E3, respectively. Electronic tags E1, E2, and E3 are small, 1.6-inch electronic tags, and are attached to the bedside tables of patients P1, P2, and P3, respectively. Patients P1, P2, and P3 have mobile terminals T1, T2, and T3, respectively. Mobile terminals T1, T2, and T3 are smartphones equipped with a camera function, and have installed an application capable of reading QR codes (registered trademark).

[0069] The server device S1 is connected to a storage device M (not shown) via a network N, and patients and patient information are stored in association with each other in the storage device M. In other words, in this example, the storage device M is a storage unit that stores patients and patient information in association with each other. The storage device M may be, for example, an electronic medical record, a nursing record server, or a part of these.

[0070] The storage unit S11 of the server device S1 stores item information of patient information to be acquired from the storage device M. The server device S1 acquires the patient information from the storage device M based on the item information. That is, the server device S1 acquires the patient information specified by the item information from the storage device M. The acquired patient information is stored in the storage unit S11 of the server device S1.

[0071] In this example, the storage unit S11 of the server device S1 stores a correspondence table (correspondence table T100) that associates each item of patient information with whether or not it needs to be coded and whether or not it needs to be legibly displayed on the electronic tag. An example of such a correspondence table and the information stored therein is shown in FIG. 2. In FIG. 2, "whether or not display in the first display area" corresponds to whether or not it needs to be legibly displayed on the electronic tag, and "whether or not display in the second display area" corresponds to whether or not it needs to be coded. That is, in the correspondence table T100 shown in FIG. 2, "patient name" and "patient ID" are items that need to be legibly displayed on the electronic tag, while the other items do not need to be legibly displayed on the electronic tag. On the other hand, the items that need to be coded are "patient name," "patient ID," "schedule," and "conditions and restrictions such as posture."

[0072] The server device S1, which has acquired the patient information from the storage device M, selects the patient information that needs to be coded from the patient information acquired from the storage device M and stored in the storage unit S11 based on the correspondence table T100, which associates each item of the patient information stored in the storage unit S11 with whether or not coding is required, and generates a QR code (registered trademark) as a machine-readable code that contains the selected patient information encoded.

[0073] In addition, the server device S1, which acquires patient information from the memory device M, selects, based on the above-mentioned correspondence table T100 which associates each item of patient information stored in the memory unit S11 with whether or not a visible display is required on the electronic tag, from the patient information acquired from the memory device M and stored in the memory unit S11.

[0074] The server device S1 transmits the machine-readable code (i.e., QR code) generated in the above procedure and the selected patient information (i.e., patient information that needs to be displayed in a visible manner on the electronic tag) to the electronic tag E1.

[0075] In this example, a correspondence table (correspondence table T101) that associates patients with electronic tags is stored in the storage unit S11 of the server device S1. An example of such a correspondence table and the information stored therein is shown in FIG. 3. As shown in FIG. 3, in this example, the correspondence table stores patient IDs as patient identification information and electronic tag IDs as electronic tag identification information, in association with each other. Based on the correspondence table, the server device S1 can determine that the electronic tag corresponding to the patient ID "0001" is an electronic tag (in this example, electronic tag E1) that has the electronic tag ID "E0001." Based on the correspondence table T101 that associates patients with electronic tags, the server device S1 selects the electronic tag E1 as the electronic tag corresponding to patient P1, and transmits the generated machine-readable code and the selected patient information to the electronic tag E1. It goes without saying that the server device S1 may also refer to a correspondence table, etc., that associates electronic tag IDs with electronic tag network addresses, etc., as needed.

[0076] The electronic tag E1 receives the machine-readable code and the patient information from the server device S1. When the electronic tag E1 receives the machine-readable code and the patient information from the server device S1, the electronic tag E1 stores the received machine-readable code and the patient information in a machine-readable code storage unit and a patient information storage unit, respectively, and also reads the machine-readable code and the patient information from the machine-readable code storage unit and the patient information storage unit, and displays them in a first display area E111 and a second display area E112 of the display unit E11, respectively.

[0077] An example of the information displayed on the display unit E11 of the electronic tag E1 and the display method is shown in Fig. 4. As shown in Fig. 4, the patient name and patient ID of patient P1 are legibly displayed as text in the first display area E111 of the display unit E11. Meanwhile, the QR code generated by the server device S1 is displayed as a machine-readable code in the second display area E112 of the display unit E11.

[0078] A patient P1 can obtain the patient information encoded and contained in the machine-readable code by using the mobile terminal T1 to read the machine-readable code (in this example, a QR code) displayed in the second display area E112 of the display unit E11 shown in Fig. 4. In this example, an application capable of reading QR codes (registered trademark) is installed in the mobile terminal T1. The following describes the procedure for obtaining the patient information from the machine-readable code using the application.

[0079] FIG. 5 shows an example of a start screen S100 displayed on the display unit of the mobile terminal T1 when the above application is launched on the mobile terminal T1. As shown in FIG. 5, a "Launch Camera (Read Code)" button is displayed on the start screen S100 displayed on the mobile terminal T1 of the patient P1. When the patient P1 presses the "Launch Camera (Read Code)" button, the camera of the mobile terminal T1 is launched, and a code reading screen S101 is displayed (FIG. 6). When the machine-readable code displayed in the second display area E112 of the display unit E11 shown in FIG. 4 is read using the camera of the mobile terminal T1 (FIG. 6), the read machine-readable code is decoded, and patient information is generated. The mobile terminal T1 displays a patient information viewing screen S101 including patient information generated based on the machine-readable code. FIG. 7 shows an example of the patient information viewing screen S101 displayed on the display unit of the mobile terminal T1 and the information contained therein.

[0080] As shown in FIG. 7, the patient information viewing screen S101 displayed on the display unit of the mobile terminal T1 displays the patient information acquisition date "January 8, 2025" as well as the patient information about the patient P1, including the patient name ("Patient Taro"), patient ID ("0001"), schedule ("10:00~blood test", "11:00~rehabilitation"), and conditions or restrictions regarding the patient's movement, posture, excretion, diet, etc. ("Mobility restrictions (cane)", "Posture restrictions (bed up restrictions 60")). о ) and "No alcohol allowed") are displayed on the patient information viewing screen S101 shown in FIG. 7. By checking the patient information viewing screen S101 shown in FIG. 7, the patient P1 can check, for example, the schedule for examinations and rehabilitation for that day. Furthermore, if a family member or acquaintance visiting the patient P1 arrives at 11:30, for example, and the patient P1 is not at home, the family member or acquaintance can use their own mobile terminal to display the patient information viewing screen S101 and check the schedule information displayed on the patient information viewing screen S101 to confirm that the patient P1 is undergoing rehabilitation.

[0081] Furthermore, although the above example describes a case in which patient information is confirmed by patient P1 and / or his / her family and / or acquaintances, other parties may also obtain patient information using a similar procedure. For example, in an emergency such as a disaster, medical staff or rescue workers rushing to the scene to provide support may obtain patient information using a similar procedure. Since the patient information is encoded and included in the machine-readable code displayed in the second display area of ​​the display unit of electronic tag P1, any mobile terminal equipped with a corresponding decoding means can obtain the patient information.

[0082] <Action 2 - Displaying patient information and machine-readable code on the electronic tag and viewing it on a mobile device> Next, the operation and procedure when the server device S1 generates a machine-readable code including information for transitioning the display screen of the mobile terminal T1 that reads the machine-readable code to a patient information viewing screen will be described.

[0083] In this example, the server device S1 generates a QR code including link information for transitioning the display screen of the mobile terminal T1 that reads the machine-readable code to a patient information viewing screen. The generated QR code is transmitted to the electronic tag E1 in the same manner as described in operation 1, and is displayed in the second display area E112 of the display unit E11 of the electronic tag E1.

[0084] When the patient P1 uses the mobile terminal T1 to read the machine-readable code (QR code) displayed in the second display area E112 of the display unit E11, the mobile terminal T1 acquires link information for transitioning the display screen of the mobile terminal T1 to a patient information viewing screen. Based on the acquired link information, the mobile terminal T1 transmits a delivery request for the patient information viewing screen to the server device S1. In this way, the link information for transitioning the display screen of the mobile terminal T1 to the patient information viewing screen functions as information for causing the mobile terminal T1 to transmit a delivery request for the patient information viewing screen to the server device S1. It goes without saying that the delivery request for the patient information viewing screen is a delivery request for a patient information viewing screen that identifies a specific patient.

[0085] When the server device S1 receives a request to distribute a patient information viewing screen from the mobile terminal T1, it retrieves patient information from the memory device M, selects the patient information that needs to be coded, generates a patient information viewing screen based on the selected patient information, and transmits the generated patient information viewing screen to the mobile terminal T1, in the same manner as described in operation 1.

[0086] The mobile terminal T1 receives the patient information viewing screen from the server device S1. When the mobile terminal T1 receives the patient information viewing screen, the patient information viewing screen is displayed on the display unit of the mobile terminal T1. An example of the patient information viewing screen and the information displayed thereon is as shown in FIG. 7, and is the same as that described in operation 1.

[0087] <Action 3 - Displaying the patient screen> Next, the operation and procedure for displaying the patient screen will be described, taking as an example the case where the patient information viewing screen S102 is transitioned to the patient screen.

[0088] On the patient information viewing screen S102 shown in Fig. 7, when the "···" button on the upper right of the screen is pressed, a pull-down list including a "Patient Screen" button is displayed (Fig. 8). When the "Patient Screen" button included in the pull-down list is selected, the mobile terminal T1 transmits a request to the server device S1 to deliver the patient screen.

[0089] Note that information for causing the mobile terminal T1 to transmit a delivery request for the patient screen to the server device S1 may basically be acquired or generated in any manner. For example, when the patient information viewing screen S102 is generated and displayed in the procedure of operation 1, link information for transitioning the display screen of the mobile terminal T1 to the patient screen may be included in the machine-readable code displayed on the display unit of the electronic tag E1. On the other hand, when the patient information viewing screen S102 is generated and displayed in the procedure of operation 2, for example, the server device may generate link information, and the generated patient information viewing screen S102 may include link information for transitioning the display screen of the mobile terminal T1 to the patient screen. Note that when the patient information viewing screen S102 generated by the server device S1 includes link information for transitioning the display screen of the mobile terminal T1 to the patient screen, the link information for transitioning the display screen of the mobile terminal T1 to the patient information viewing screen, which is included in the machine-readable code, also functions as information for causing the mobile terminal T1 to transmit a delivery request for the patient screen to the server device S1 via the patient information viewing screen that includes a button for transmitting a delivery request for the patient screen.

[0090] When the server device S1 receives a request to distribute a patient screen from the mobile terminal T1, it generates a patient authentication information input screen S103 that accepts input of patient authentication information for authenticating the patient, and transmits the generated patient authentication information input screen S103 to the mobile terminal T1. When the mobile terminal T1 receives the patient authentication information input screen S103 from the server device S1, the patient authentication information input screen S103 is displayed on the display unit of the mobile terminal T1. An example of the patient authentication information input screen S103 is shown in FIG. 9. As shown in FIG. 9, the patient authentication information input screen S103 displays the patient ID "0001" of the patient P1 as patient identification information, a message asking the user to enter a password, and an input field for accepting input of the password. The patient P1 simply enters a preset password in the input field. When the "Send" button is pressed with the password entered in the input field, the entered password is transmitted to the server device S1 as patient authentication information.

[0091] When the server device S1 receives the password as patient authentication information, it determines whether the patient authentication information matches the patient authentication information stored in advance. In this example, the storage unit S11 of the server device S1 stores patient identification information that identifies a patient and patient authentication information in association with each other, and the server device S1 refers to the association to determine whether the received patient authentication information matches the patient authentication information stored in advance as the patient authentication information of patient P1.

[0092] If it is determined that the received patient authentication information matches the pre-stored patient authentication information, the server device S1 acquires the patient information from the memory device M, generates a patient screen including some or all of the acquired patient information, and transmits the generated patient screen to the mobile terminal T1.

[0093] The mobile terminal T1 receives the patient screen from the server device S1. The display unit of the mobile terminal T1 that has received the patient screen displays the patient screen S104 received from the server device S1. An example of the patient screen S104 displayed in this manner and the information displayed thereon is shown in FIG.

[0094] As shown in Figure 10, the patient screen S104 displays "Schedule," "Restrictions / Conditions," "Meal Selection," and "Facility Reservation" buttons, as well as a "Notice" column. The "Schedule" button is for checking schedules for surgery, examinations, medical treatment, rehabilitation, etc., the "Restrictions / Conditions" button is for checking information such as conditions or restrictions regarding movement, posture, excretion, diet, etc., the "Meal Selection" button is for selecting a menu of in-hospital meals, and the "Facility Reservation" button is for reserving facilities within the medical institution. The "Notice" column displays messages from nurses and doctors, and further "Notice" information can be viewed by clicking the "View More" button.

[0095] For example, when the "Meal Selection" button displayed on the patient screen S104 is pressed, a meal selection screen (not shown) for accepting meal selection is displayed. Patient P1 can select a meal by selecting a desired menu from the menus displayed on the meal selection screen. Information regarding the meal selection entered via the meal selection screen is transmitted to server device S1 and stored, for example, in memory unit S11. In this case, the medical institution's meal management system can refer to memory unit S11 to obtain information regarding the meal selection entered by patient P1 via the meal selection screen. Meanwhile, server device S1 may be configured to transmit information regarding the meal selection entered via the meal selection screen to the medical institution's meal management system.

[0096] Furthermore, when the "facility reservation" button displayed on the patient screen S104 is pressed, a facility reservation screen (not shown) for accepting input such as reservations for hospital facilities is displayed. Patient P1 can make reservations for the hospital's barber shop, laundry, etc. from the facility reservation screen. Information regarding the facility reservation entered via the facility reservation screen is transmitted to the server device S1 and stored, for example, in the memory unit S11. In this case, the facility management system of the medical institution can refer to the memory unit S11 to obtain the information regarding the facility reservation entered by patient P1 via the facility reservation screen. Meanwhile, the server device S1 may be configured to transmit the information regarding the facility reservation entered via the facility reservation screen to the facility management system of the medical institution.

[0097] <Action 4 - Displaying the screen for medical staff> Next, the operation and procedure for displaying the medical staff screen will be described using an example in which the patient information viewing screen is transitioned to the medical staff screen.

[0098] The medical staff member uses his / her own mobile terminal T2 to display the patient information viewing screen S102 on the display unit of the mobile terminal T2 in the same procedure as in operation 1 or operation 2. On the patient information viewing screen S102 shown in FIG. 7, when the "···" button in the upper right corner of the screen is pressed, a pull-down list including a "medical staff screen" button is displayed (FIG. 8). When the "medical staff screen" button included in the pull-down list is selected, the mobile terminal T2 transmits a request to the server device S1 to distribute the medical staff screen.

[0099] Note that information for causing the mobile terminal T1 to transmit a delivery request for the medical staff screen to the server device S1 may basically be acquired or generated in any manner. For example, when the patient information viewing screen S102 is generated and displayed in the procedure of operation 1, link information for transitioning the display screen of the mobile terminal T2 to the medical staff screen may be included in the machine-readable code. On the other hand, when the patient information viewing screen S102 is generated and displayed in the procedure of operation 2, for example, the server device may generate link information, and the generated patient information viewing screen S102 may include link information for transitioning the display screen of the mobile terminal T2 to the medical staff screen. Note that when the patient information viewing screen S102 generated by the server device S1 includes link information for transitioning the display screen of the mobile terminal T2 to the medical staff screen, the link information for transitioning the display screen of the mobile terminal T2 to the patient information viewing screen, which is included in the machine-readable code, also functions as information for causing the mobile terminal T2 to transmit a delivery request for the medical staff screen to the server device S1 via the patient information viewing screen that includes a button for transmitting a delivery request for the medical staff screen.

[0100] When the server device S1 receives a request to distribute a screen for medical staff from the mobile terminal T2, it generates a medical staff authentication information input screen S105 that accepts input of medical staff authentication information for authenticating the medical staff, and transmits the generated medical staff authentication information input screen S105 to the mobile terminal T2. When the mobile terminal T2 receives the medical staff authentication information input screen S105 from the server device S1, the medical staff authentication information input screen S105 is displayed on the display unit of the mobile terminal T2. An example of the medical staff authentication information input screen S105 is shown in FIG. 11. As shown in FIG. 11, the medical staff authentication information input screen S105 displays a message requesting that the medical staff ID and password be entered, as well as input fields for accepting the entry of the medical staff ID and password. The medical staff simply enters the staff ID and password in the input fields. When the "send" button is pressed with the staff ID and password entered in the input fields, the entered staff ID and password are transmitted to the server device S1 as medical staff authentication information.

[0101] When the server device S1 receives the staff ID and password as medical staff authentication information, it determines whether the medical staff authentication information matches pre-stored medical staff authentication information. In this example, the storage unit S11 of the server device S1 stores medical staff identification information (staff ID) that identifies a medical staff member in association with a password, and the server device S1 refers to the association to determine whether the combination of the received staff ID and password matches the combination of the staff ID and password pre-stored as medical staff authentication information.

[0102] If it is determined that the received staff ID and password combination matches a pre-stored staff ID and password combination (i.e., medical staff authentication information), the server device S1 acquires patient information from the memory device M, generates a screen S106 for medical staff that includes some or all of the acquired patient information, and transmits the generated screen S106 for medical staff to the mobile terminal T2.

[0103] When the mobile terminal T2 receives the medical staff screen S106 from the server device S1, the medical staff screen S106 received from the server device S1 is displayed on the display unit of the mobile terminal T2. An example of the medical staff screen S106 displayed in this manner and the information displayed thereon is shown in FIG.

[0104] As shown in FIG. 12 , the name of the nurse ("Nurse Taro") who is the user of the mobile terminal T2 and currently logged in to the medical staff screen is displayed in the upper right corner of the medical staff screen S106. The medical staff screen also displays the patient's name ("Patient Taro") and patient ID ("0001") as information identifying the patient being displayed. Information regarding conditions or restrictions, such as the patient's posture, that must be observed when caring for the patient is also displayed as pictograms. Buttons for viewing detailed patient information include a "Schedule" button for viewing and / or entering the patient's schedule for surgeries, examinations, medical examinations, etc.; a "Nursing Record" button for viewing and / or entering the patient's nursing record; a "Medication Information" button for viewing and / or entering medication information; and a "Vital Signs" button for viewing and / or entering vital signs information. By pressing these buttons, nurse N1 can display a display screen for viewing and / or entering detailed patient information. The following describes the vital signs screen for viewing and / or entering medical information related to "vital signs" as patient information.

[0105] The storage device M stores a correspondence table T102 that associates patients with their vital data and the measurement dates and times. An example of the correspondence table T102 and the information stored therein is shown in Fig. 13. As shown in Fig. 13, the correspondence table T102 stores patient IDs, measurement dates and times, and vital data such as systolic blood pressure, diastolic blood pressure, pulse rate, body temperature, respiratory rate, and oxygen concentration in association with each other.

[0106] When the "Vital Signs" button is pressed on the medical staff screen S106, the mobile terminal T2 transmits a request to the server device S1 to distribute a vital signs screen. When the server device S1 receives the request to distribute a vital signs screen from the mobile terminal T2, it acquires the necessary patient information from the storage device M (more specifically, the correspondence table T102), generates a vital signs screen, and transmits it to the mobile terminal T2. When the mobile terminal T2 receives the vital signs screen, it displays the vital signs screen on its display unit.

[0107] An example of the vital signs screen S107 and the information displayed thereon is shown in Fig. 14. As shown in Fig. 14, the vital signs screen has a blood pressure column where the measurement results of systolic and diastolic blood pressure are displayed over time. By sliding the vital signs screen left and right, nurse N1 can display a pulse column, body temperature column, respiratory rate column, oxygen concentration column, and other columns (not shown) that display the measurement results of each vital sign over time.

[0108] Meanwhile, a "vital input" button is provided at the bottom of the vital sign screen S107, and when the "vital input" button is pressed, the display screen of the mobile terminal T2 transitions to a vital sign input screen S108.

[0109] An example of the vital sign input screen S108 and the information displayed thereon is shown in Fig. 15. As shown in Fig. 15, the vital sign input screen S108 has input fields for accepting input of measurement results for systolic blood pressure, diastolic blood pressure, pulse rate, body temperature, respiratory rate, and oxygen concentration. Nurse N1 measures vital signs using appropriate medical equipment and measuring devices, and inputs the measured vital signs into the respective input fields.

[0110] When the "Send" button displayed at the bottom of the vital sign input screen S108 is pressed, the mobile terminal T2 transmits the input values ​​entered in each input field to the server device S1. Upon receiving this, the server device S1 outputs the received information to the storage device M based on the received information. This updates the correspondence table T102.

[0111] <Step 5 - Correspondence table editing screen> Next, the operation and procedure for displaying the correspondence table editing screen for editing the correspondence table that associates patients with electronic tags will be described, taking as an example the case of transitioning from the patient information viewing screen to the correspondence table editing screen.

[0112] Nurse N1, who is a medical staff member, uses her own mobile terminal T2 to display a patient information viewing screen S102 on the display unit of mobile terminal T2 using the same procedure as in operation 1 or operation 2. On the patient information viewing screen S102, when the "···" button in the upper right corner of the screen is pressed, a pull-down list including an "Edit Correspondence Table" button is displayed (FIG. 8), and when nurse N1 selects the "Edit Correspondence Table" button included in the pull-down list, mobile terminal T2 sends a request to server device S1 to distribute the correspondence table editing screen.

[0113] Note that information for causing the mobile terminal T1 to transmit a correspondence table editing screen distribution request to the server device S1 may basically be acquired or generated in any manner. For example, when the patient information viewing screen S102 is generated and displayed in the procedure of Operation 1, link information for transitioning the display screen of the mobile terminal T2 to the correspondence table editing screen may be included in the machine-readable code. On the other hand, when the patient information viewing screen S102 is generated and displayed in the procedure of Operation 2, link information may be generated in the server device, and the generated patient information viewing screen S102 may include link information for transitioning the display screen of the mobile terminal T2 to the correspondence table editing screen. Note that when the patient information viewing screen S102 generated by the server device S1 includes link information for transitioning the display screen of the mobile terminal T2 to the correspondence table editing screen, the link information for transitioning the display screen of the mobile terminal T2 to the patient information viewing screen, which is included in the machine-readable code, also functions as information for causing the mobile terminal T2 to transmit a correspondence table editing screen distribution request to the server device S1 via the patient information viewing screen S102, which includes a button for transmitting a correspondence table editing screen distribution request.

[0114] When the server device S1 receives a request to distribute the correspondence table editing screen from the mobile terminal T2, it generates a medical staff authentication information input screen S105 (FIG. 11) that accepts input of medical staff authentication information for authenticating the medical staff, and transmits the generated medical staff authentication information input screen S105 to the mobile terminal T2. The subsequent authentication procedure is the same as in operation 4.

[0115] If the server device S1 determines that the combination of staff ID and password received from the mobile terminal T2 matches the pre-stored medical staff authentication information (combination of staff ID and password), it acquires the necessary information from the memory unit S11 that stores the correspondence table T101 that associates patients with electronic tags, generates a correspondence table editing screen, and transmits the generated correspondence table editing screen to the mobile terminal T2. The mobile terminal T2 receives the correspondence table editing screen from the server device S1. The correspondence table editing screen received from the server device S1 is displayed on the display unit of the mobile terminal T2. An example of the correspondence table editing screen S109 displayed in this way and the information displayed thereon is shown in FIG. 16.

[0116] As shown in FIG. 16 , the correspondence table editing screen S109 displays patient identification information for identifying a patient and electronic tag identification information for identifying an electronic tag in association with each other. Furthermore, the correspondence table editing screen S106 allows editing of the patient identification information associated with the electronic tag on which the machine-readable code for transitioning to the correspondence table editing screen S106 is displayed, i.e., the electronic tag whose QR code the medical staff has read. For example, the medical staff may input the patient identification information of the patient who will use the electronic tag to be edited on the correspondence table editing screen and press the “Apply” button at the bottom of the correspondence table editing screen S106. When the “Apply” button is pressed, the correspondence table T101 is updated based on the input patient identification information. That is, the input patient identification information is recorded in the correspondence table T101 in association with the corresponding electronic tag identification information.

[0117] By configuring the correspondence table that associates patients with electronic tags to be editable via the machine-readable code displayed on the electronic tag in this way, it is possible to obtain the advantage of easily associating patients with electronic tags. While patient identification information may be entered manually, it may also be obtained by, for example, scanning a barcode or the like printed on the patient's wristband or patient card using the camera function of the mobile terminal T2. This configuration can prevent input errors in patient identification information and misidentification of patients. [Industrial Applicability]

[0118] The patient information sharing system according to one aspect of the present invention, which allows for the sharing of patient information at a much lower cost and more efficiently than conventional bedside terminals, will promote the sharing of patient information in many medical institutions, including those that cannot introduce bedside terminals, and will contribute to improving the working environment and the quality of medical care, and has great industrial applicability.

Claims

1. A patient information sharing system including an electronic tag and a server device capable of communicating with the electronic tag, The server device an acquisition unit that acquires patient information from a storage unit that stores patient identification information that identifies a patient and the patient information in association with each other; a code generation unit that generates a machine-readable code that can acquire part or all of the acquired patient information; and a transmitting unit that transmits the generated machine-readable code to a corresponding electronic tag based on a correspondence table that associates patient identification information with electronic tag identification information that identifies the electronic tag; The electronic tag is a display unit that displays the machine-readable code received from the server device; A patient information sharing system characterized by:

2. The machine-readable code contains, in an encoded form, part or all of the patient information acquired by the acquisition unit. The patient information sharing system according to claim 1 .

3. The server device a patient information viewing screen generating unit that generates a patient information viewing screen for confirming a part or all of the patient information acquired by the acquiring unit, the machine-readable code includes information for causing a terminal device that reads the machine-readable code to transmit a delivery request for the patient information viewing screen to the server device; The patient information sharing system according to claim 1 .

4. The server device a patient screen generation unit that generates a patient screen for a patient to confirm a part or all of the patient information acquired by the acquisition unit and / or for a patient to input patient information; the machine-readable code includes information for causing a terminal device that reads the machine-readable code to transmit a delivery request for the patient screen to the server device; The patient information sharing system according to claim 2 or 3.

5. The server device a receiving unit that receives patient authentication information for authenticating a patient from a terminal device when a request for delivery of the patient screen is received from the terminal device; a determination unit that determines whether the received patient authentication information matches pre-stored patient authentication information; and a transmitting unit that transmits the patient screen to the terminal device when the determining unit determines that the patient authentication information matches pre-stored patient authentication information; The patient information sharing system according to claim 4 .

6. The server device a medical staff screen generation unit that generates a medical staff screen for a medical staff member to confirm a part or all of the patient information acquired by the acquisition unit and / or for a medical staff member to input patient information; the machine-readable code includes information for causing a terminal device that reads the machine-readable code to transmit a delivery request for the medical staff screen to the server device; The patient information sharing system according to claim 2 or 3.

7. The server device a receiving unit that, when receiving a request for delivery of the medical staff screen from a terminal device, receives medical staff authentication information for authenticating the medical staff from the terminal device; a determination unit that determines whether the received medical staff authentication information matches pre-stored medical staff authentication information; and a transmitting unit that transmits the medical staff screen to the terminal device when the determining unit determines that the medical staff authentication information matches pre-stored medical staff authentication information; The patient information sharing system according to claim 6 .

8. The server device a correspondence table editing screen generating unit that generates a correspondence table editing screen for editing the correspondence table that associates patient identification information with electronic tag identification information; the machine-readable code includes information for causing a terminal device that reads the machine-readable code to transmit a distribution request for the correspondence table editing screen to the server device; The patient information sharing system according to claim 2 or 3.

9. The server device a receiving unit that, when receiving a request for distribution of the correspondence table editing screen from a terminal device, receives medical staff authentication information for authenticating the medical staff from the terminal device; a determination unit that determines whether the received medical staff authentication information matches pre-stored medical staff authentication information; and a transmitting unit that transmits the correspondence table editing screen to the terminal device when the determining unit determines that the medical staff authentication information matches pre-stored medical staff authentication information; The patient information sharing system according to claim 8 .

Images