JP2012185644A - Nursing support system, terminal device and server device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a nursing support system, a terminal device and a server device capable of automatically recording a nursing plan executed by a nurse.SOLUTION: The nursing support system includes a terminal device carried by a nurse and a sever device communicable with the terminal device. When patient information identifying a nursed patient, as well as tag information indicating a content of an operation with an apparatus which is read from an RFID tag attached to each apparatus in a hospital, is input, the terminal device transmits these pieces of information and terminal location information showing current location of its own device as action history to the server device. The server device compares each item of a performed nursing plan which comprises a set of the action history received from the terminal device, showing a nursing operation plan performed by the nurse, location information identifying a place of the nursing operation, the patient information identifying the nursed patient and operation content information showing a content of the nursing operation, and adds confirmation information showing that the plan has been completed to the matched plan.

Description

  Embodiments described herein relate generally to a nursing support system, a terminal device, and a server device.

  2. Description of the Related Art Conventionally, data is browsed and data is input by using a portable terminal device such as a PDA in order to advance a nursing action efficiently in a hospital. Conventionally, a technique has been proposed in which a portable wireless terminal is carried so that the flow and position of a nurse in a hospital can be confirmed.

  However, although the conventional technique can confirm the position and flow line of the nurse, no consideration is given to the relationship with the nursing work (nursing plan) performed by the nurse at each position in the hospital. Therefore, the nurse has to manually record the fact that it has been performed each time the nursing operation is performed at each position in the hospital.

  The nursing support system of an embodiment includes a terminal device carried by a nurse and a server device that can communicate with the terminal device. The terminal device includes an input unit, a reading unit, a position acquisition unit, and a transmission unit. The input means receives input of patient information for identifying a patient who is a subject of nursing work. The reading unit reads tag information representing the work content using the device from the RFID tag attached to each device in the hospital. The position acquisition unit acquires terminal position information representing the current position of the terminal device. When the patient information is input and the tag information is read, the transmission unit transmits the terminal position information acquired by the position acquisition unit together with the information as an action history to the server device. The server device includes nursing plan storage means, reception means, and execution determination means. The nursing plan storage means includes the nursing information in which the position information for specifying the position where the nursing work is performed, the patient information for identifying the patient who is the subject of the nursing work, and the work content information representing the content of the nursing work. Memorize the nurse's nursing plan. The receiving means receives the action history transmitted from the terminal device. The execution determination means includes a set of terminal position information, patient information, and tag information included in the action history, and a set of position information, patient information, and work content information included in each nursing plan stored in the nursing plan storage means. In comparison, check information indicating that the two plans have been executed is added to the nursing plan in which the contents of both sets match.

FIG. 1 is a diagram schematically illustrating the overall configuration of a nursing support system according to an embodiment. FIG. 2 is a diagram illustrating an example of a configuration of the terminal device. FIG. 3 is a diagram illustrating an example of the configuration of a hospital server. FIG. 4 is a diagram schematically illustrating an example of the data configuration of the authentication repository. FIG. 5 is a diagram schematically illustrating an example of the data configuration of the electronic medical record repository. FIG. 6 is a diagram schematically illustrating an example of the data configuration of the nursing plan repository. FIG. 7 is a diagram schematically illustrating an example of the data configuration of the action history repository. FIG. 8 is a flowchart showing a procedure of authentication processing performed between the terminal device and the hospital server. FIG. 9 is a flowchart illustrating a procedure of nursing plan providing processing performed between the terminal device and the hospital server. FIG. 10 is a flowchart showing a procedure of electronic medical record provision processing performed between the terminal device and the hospital server. FIG. 11 is a flowchart illustrating the procedure of the action history registration process performed between the terminal device and the hospital server. FIG. 12 is a flowchart illustrating a procedure of the execution determination process illustrated in FIG. FIG. 13 is a flowchart showing the procedure of the unprocessed work notification process performed between the terminal device and the hospital server. FIG. 14 is a diagram illustrating an example of a display screen for unprocessed work information.

  Hereinafter, embodiments of a nursing support system, a terminal device, and a server device will be described in detail with reference to the accompanying drawings. In addition, this invention is not limited by embodiment described below.

  FIG. 1 is a diagram schematically showing an overall configuration of a nursing support system 100 according to the present embodiment. As shown in the figure, the nursing support system 100 includes a terminal device 10, a hospital server 20, and hospital equipment 30. Here, the terminal device 10, the hospital server 20, and the hospital equipment 30 are provided in the same hospital H. The terminal device 10 and the hospital server 20 are communicably connected via a wired or wireless LAN 41 (Local Area Network).

  The terminal device 10 is a portable information communication terminal carried by each nurse (including an associate nurse) in the hospital H. The nurse can refer to the electronic medical records, nursing plans, etc. of each patient by accessing the in-hospital server 20 using the terminal device 10. Here, the “nursing plan” is a schedule for nursing work such as temperature measurement and blood sampling performed by each nurse.

  The hospital server 20 is one or a plurality of server devices having functions such as a Web server, an application server, and a database server. The in-hospital server 20 stores and manages various data necessary for nursing work in the hospital H, and provides these data so that the terminal device 10 can refer to them.

  The in-hospital device 30 is various devices used by the nurse for various operations, and is provided at a predetermined location in the hospital H. The in-hospital device 30 is provided with an RFID tag 31 that stores information indicating work content using the in-hospital device 30 (hereinafter referred to as work content information) as tag information. For example, when the in-hospital device 30 is a thermometer, “temperature measurement” or the like is stored in the RFID tag 31 as work content information as work content using the thermometer. The in-hospital apparatus 30 includes medical equipment such as a thermometer as described above, and medicines such as injections and infusions, treatment equipment such as bandages and poultices, and the like. The in-hospital device 30 has a concept including a specific facility (for example, a bathroom or an X-ray room) in the hospital H. In this case, the RFID tag 31 is attached to a specific part or article in the facility. It shall be.

  Each nurse in the hospital H causes the RFID tag 31 to be read by the reader unit 17 to be described later by bringing the portable terminal device 10 close to the in-hospital device 30 used for the nursing work when performing the nursing work. In addition, a patient ID for identifying a patient to be subjected to nursing work is input using an input unit 14 and a reader unit 17 described later provided in the terminal device 10.

  Hereinafter, the configuration of the terminal device 10 and the hospital server 20 will be described. FIG. 2 is a diagram illustrating an example of the configuration of the terminal device 10. As shown in the figure, a terminal device 10 is a microcomputer that executes information processing, a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, an input unit 14, a display. Unit 15, storage unit 16, reader unit 17, communication I / F 18, and the like.

  The CPU 11 comprehensively controls the terminal device 10 by executing various programs stored in the ROM 12 or the storage unit 16 described later. The ROM 12 stores a program for performing basic operations. The RAM 13 is a main storage device of the terminal device 10 and functions as a work area for the CPU 11.

  The CPU 11 is connected to an input unit 14 and a display unit 15 via various input / output circuits (not shown). The input unit 14 is an input device such as a keyboard or a pointing device, and notifies the CPU 11 of the operation content operated by the nurse. The display unit 15 is a display device such as an LCD (Liquid Crystal Display), and displays various types of information in accordance with instructions from the CPU 11. In addition, it is good also as a form which receives operation content in cooperation with the display part 15 by making the input part 14 into a touchscreen structure.

  The CPU 11 is connected to a storage unit 16, a reader unit 17, and a communication I / F 18 through various input / output circuits (not shown). The storage unit 16 is a storage medium such as an HDD (Hard Disk Drive) or a flash memory, and stores various programs executed by the CPU 11 and various setting files.

  The reader unit 17 is a reader device that reads information from an RFID tag (IC tag) or an IC card. Specifically, the reader unit 17 reads work content information from an RFID tag 31 attached to the in-hospital device 30. Further, when an IC card storing information identifying the nurse (for example, a nurse ID or a set of nurse ID and password) is distributed to each nurse at the hospital H, the IC card Read information. Also. When an IC card storing information for identifying the patient (for example, a patient ID or name to be described later) is distributed to each patient in the hospital H, the information is read from the IC card.

  The communication I / F 18 is an interface for performing data communication with the hospital server 20. The CPU 11 controls the communication I / F 18 and transmits / receives various data to / from the hospital server 20. Although not shown, the terminal device 10 includes a time measuring device such as an RTC (Real Time Clock), and the CPU 11 can acquire date and time information representing the current date and time from the time measuring device.

  Next, the functional configuration of the terminal device 10 will be described. As shown in FIG. 2, the CPU 11 of the terminal device 10 cooperates with a program stored in the ROM 12 or the storage unit 16 to communicate with the communication control unit 111, the nursing plan reference unit 112, the electronic medical record reference unit 113, and obtain position information. Unit 114 and action history registration unit 115 are realized.

  The communication control unit 111 is a functional unit that controls the communication I / F 18 and transmits / receives data to / from the hospital server 20. When the communication control unit 111 accesses the in-hospital server 20, the communication control unit 111 sets the combination of the nurse ID and the password input from the operator (nurse) of the device through the input unit 14 and the reader unit 17 as connection information. As shown in FIG. When the communication control unit 111 receives unprocessed work information described later from the in-hospital server 20, the communication control unit 111 displays various types of information included in the unprocessed work information on the display unit 15.

  The nursing plan reference unit 112 generates instruction information for requesting reference to the nursing plan (hereinafter referred to as nursing plan reference request) according to the operation content input via the input unit 14, and the hospital plans through the communication control unit 111. To the internal server 20. In addition, when a nursing plan is provided from the in-hospital server 20, the nursing plan reference unit 112 displays each work item included in the nursing plan on the display unit 15.

  The electronic medical chart reference unit 113 transmits an electronic medical chart reference request for requesting reference to the electronic medical chart to the hospital server 20 through the communication control unit 111 according to the operation content input through the input unit 14. In addition, when the electronic medical record is provided from the hospital server 20, the electronic medical record reference unit 113 displays each item included in the electronic medical record on the display unit 15 in a selectable state. In addition, when the electronic medical record reference unit 113 receives an editing operation (for example, recording of the progress of a medical condition) for a specific item via the input unit 14, the electronic medical record reference unit 113 notifies the hospital server 20 of the editing content via the communication control unit 111. By instructing to update the electronic medical record. The electronic medical record reference request includes the patient ID of a specific patient.

  The position information acquisition unit 114 acquires position information representing the position of the terminal device 10 in the hospital H, that is, the position of the nurse who operates the terminal device 10. Here, the acquisition method of the position information in the hospital H is not particularly limited, and a publicly known / public technique related to indoor positioning can be used. For example, when a PHS or a wireless LAN is used for connection to the LAN 41, a known technique for specifying the position from the radio wave intensity with each access point provided in the hospital H may be used. Further, an RFID tag is attached to the terminal device 10, a receiver connected to the LAN 41 detects the RFID tag of the terminal device 10, and the position of the receiver that detects the RFID tag is used as position information of the terminal device 10. It is good also as a form acquired from this receiver. In addition, when another device is required for acquisition of position information, the terminal device 10 may include the device.

  The action history registration unit 115 includes an action history registration request including position information indicating the current position acquired by the position information acquisition unit 114 and date / time information indicating the current date and time, every predetermined time (for example, 5 minutes). Is transmitted to the in-hospital server 20 through the communication control unit 111.

  In addition, when the patient history information indicating the patient ID is input from the input unit 14 or the reader unit 17 and the work content information is continuously input from the reader unit 17, the behavior history registration unit 115 stores the patient information and the work content information. And the action history registration request including the position information indicating the current position acquired by the position information acquisition unit 114 and the date information indicating the current date and time as elements, and transmitting the request to the in-hospital server 20 through the communication control unit 111. .

  Specifically, the action history registration unit 115 receives the other information within a predetermined time (for example, within 5 minutes) after the patient information (patient ID) or the work content information is input. If it is determined that both pieces of information have been input continuously, the action history registration request including these pieces of information is generated and transmitted to the in-hospital server 20. In addition, although the input order of patient information and work content information is not particularly limited, the input order may be defined. In addition, when the patient information and the work content information are input after a predetermined operation (for example, input of a work start command) is performed via the input unit 14, it is determined that both pieces of information are continuously input. It is good also as a form.

  FIG. 3 is a diagram illustrating an example of the configuration of the hospital server 20. As shown in the figure, the hospital server 20 includes a CPU 21, a ROM 22, a RAM 23, an input unit 24, a display unit 25, a storage unit 26, a communication I / F 27, and the like as microcomputers for executing information processing.

  The CPU 21 comprehensively controls the hospital server 20 by executing various programs stored in the ROM 22 or a storage unit 26 described later. The ROM 22 stores a program for performing basic operations. The RAM 23 is a main storage device of the hospital server 20 and functions as a work area for the CPU 21.

  The CPU 21 is connected to an input unit 24 and a display unit 25 via various input / output circuits (not shown). The input unit 24 is an input device such as a keyboard or a pointing device, and notifies the CPU 21 of the operation content operated by the operator. The display unit 25 is a display device such as an LCD, and displays various types of information in accordance with instructions from the CPU 21.

  The CPU 21 is connected to a storage unit 26 and a communication I / F 27 via various input / output circuits (not shown).

  The storage unit 26 is a storage medium such as an HDD or a flash memory, and stores various programs executed by the CPU 21 and various setting files. The files stored in the storage unit 26 include, for example, an authentication repository 261 that stores and manages a pair of each nurse's nurse ID and password, an electronic medical record repository 262 that stores and manages each patient's electronic medical record, Examples include a nursing plan repository 263 that stores and manages each nurse's nursing plan, and an action history repository 264 that stores and manages each nurse's action history.

  FIG. 4 is a diagram schematically illustrating an example of the data configuration of the authentication repository 261. As shown in the figure, the authentication repository 261 stores a nurse ID as identification information for identifying each nurse and a password in association with each other. Here, the combination of the nurse ID and the password is authentication information required when accessing the hospital server 20. The in-hospital server 20 permits access to various repositories when the combination of the nurse ID and password transmitted from the terminal device 10 matches any authentication information registered in the authentication repository 261. . Note that the nurse ID and password are assigned in advance to each nurse.

  FIG. 5 is a diagram schematically illustrating an example of the data configuration of the electronic medical record repository 262. As shown in the figure, the electronic medical record repository 262 stores a patient ID for identifying each patient in the hospital H and the electronic medical record of the patient with this patient ID in association with each other.

  FIG. 6 is a diagram schematically illustrating an example of the data configuration of the nursing plan repository 263. As shown in the figure, the nursing plan repository 263 associates with the nurse ID for identifying the nurse, the contents (work contents) of the nursing work to be performed by the nurse of the nurse ID and the work contents. The nursing plan including the execution deadline is stored. Each work content is associated with a column (execution column) for checking whether or not the nursing work has been executed. Here, in addition to the date and time being registered, only the date may be registered as the execution deadline. In addition, the work content includes, as elements for identifying the content of the nursing work, work position information for identifying the place where the nursing work is performed, patient information (patient ID) of the patient who is the subject of the nursing work, Work content information representing the content. For example, in the case of FIG. 6, “Room 101” is work position information, “Patient 01” is patient information, and “Temperature” is work content information.

  FIG. 7 is a diagram schematically illustrating an example of the data configuration of the action history repository 264. As shown in the figure, for each nurse ID of each nurse, the action history repository 264 includes a history of actions performed by the nurse of the nurse ID (action history) and the date and time when the action was performed ( Action date and time). The action history recording unit 214 described later registers the contents of the action history registration request transmitted from the terminal device 10 in the action history repository 264. In the example of FIG. 7, the action history of the nurse with the nurse ID “nurse 01” is present at the nurse center at 10:15 on November 9, 2010, and at 10:20 on the same day. It is recorded that “temperature measurement” work of “patient 01” was performed in “room 101”.

  Returning to FIG. 3, the communication I / F 27 is an interface for performing data communication with the terminal device 10. CPU21 transmits / receives various data between the terminal devices 10 using communication I / F27.

  Next, the functional configuration of the hospital server 20 will be described. As shown in FIG. 3, the CPU 21 of the hospital server 20 cooperates with a program stored in the ROM 22 or the storage unit 26 to communicate with the communication control unit 211, the nursing plan providing unit 212, the electronic medical record providing unit 213, and the action history. The recording unit 214, the execution determination unit 215, and the nursing plan monitoring unit 216 are realized.

  The communication control unit 211 controls the communication I / F 27 and transmits / receives data to / from the terminal device 10. Specifically, the communication control unit 211 sets the nurse ID and password set included in the connection information transmitted from the terminal device 10 and each authentication information registered in the authentication repository 261 (a set of nurse ID and password). ) To determine whether there is a match. If they match, the communication control unit 211 determines that the nurse with the nurse ID is an operator of the terminal device 10 and uses a known technique such as a cookie, so that the terminal device 10 that has transmitted the nurse ID Establish a session for. If the connection information does not match any authentication information in the authentication repository 261, the communication control unit 211 determines that the access is unauthorized and rejects the access.

  The nursing plan providing unit 212 provides a nursing plan to the terminal device 10 in response to a nursing plan reference request transmitted from the terminal device 10. Specifically, the nursing plan providing unit 212 reads the nursing plan associated with this nurse ID from the nursing plan repository 263 based on the nurse ID of the terminal device 10 that transmitted the nursing plan reference request, and the communication control unit It transmits to the terminal device 10 via 211. In addition, when a specific date (year / month / day) is specified together with the nursing plan reference request from the terminal device 10, the nursing plan associated with the specified date is read, but the date is not specified. To read the nursing plan associated with today's date.

  The electronic medical record providing unit 213 provides the electronic medical record to the terminal device 10 in response to the electronic medical record reference request transmitted from the terminal device 10. Specifically, the electronic medical record providing unit 213 reads the electronic medical record associated with the patient ID from the electronic medical record repository 262 based on the patient ID included in the electronic medical record reference request, and the terminal via the communication control unit 211 Transmit to device 10. When receiving an electronic medical record update instruction (edit contents) from the terminal device 10, the electronic medical record providing unit 213 updates the electronic medical record by reflecting the edited contents on the electronic medical record being provided to the terminal device 10. .

  The behavior history recording unit 214 registers various information included in the behavior history registration request in the behavior history repository 264 in response to the behavior history registration request transmitted from the terminal device 10. Specifically, the action history recording unit 214 associates the date and time information included in the action history registration request in the action date and time column in association with the nurse ID of the nurse who operates the terminal device 10 that has transmitted the action history registration request. sign up. The action history recording unit 214 registers the position information, patient information, and work content information included in the action history registration request in the action history column.

  Each time the behavior history repository 264 is updated by the behavior history registration by the behavior history recording unit 214, the execution determination unit 215 updates the nurse ID, behavior date and behavior history newly registered in the behavior history repository 264. Then, by comparing with the nursing plan (execution deadline and work content) of each nurse ID registered in the nursing plan repository 263, it is determined whether any nursing plan (work content) has been executed. Then, the execution determination unit 215 determines that it has been executed, and updates the nursing plan repository 263 by registering a check flag in the execution column of the nursing plan.

  More specifically, the execution determination unit 215 corresponds to the nurse ID newly registered in the action history repository 264 among the nursing plans registered in the nursing plan repository 263 and the execution column is not checked. And, the execution deadline of today is extracted. When the execution determination unit 215 sets each element included in the action history newly registered in the action history repository 264 as a search condition, the execution determination unit 215 adds the search condition to the work content of each nursing plan extracted from the nursing plan repository 263. It is determined whether or not there is a thing corresponding to. Then, the execution determination unit 215 determines that the nursing plan corresponding to the search condition has been executed, and registers a check flag in the execution column.

  The nursing plan monitoring unit 216 includes a nursing plan registered in the nursing plan repository 263. In the nursing plan, the execution column is unchecked, and the time difference from the current date and time of the execution deadline included in the nursing plan is within a predetermined time. Extract the plan. Further, when the nursing plan monitoring unit 216 classifies the extracted nursing plans according to the nurse IDs of the nurses in charge, the nursing plan monitoring unit 216 communicates as unprocessed work to the terminal device 10 operated by the nurse with the corresponding nurse ID. It transmits through the control unit 211. When only the date is registered as the execution deadline, the nursing plan is extracted by determining the time difference from a predetermined time (for example, 18:00).

  Hereinafter, the operation of the nursing support system 100 will be described with reference to FIGS. First, the authentication process performed between the terminal device 10 and the hospital server 20 will be described with reference to FIG. Here, FIG. 8 is a flowchart showing a procedure of authentication processing performed between the terminal device 10 and the hospital server 20.

  First, in the terminal device 10, when accessing the hospital server 20, the nurse inputs the connection information (nurse ID and password) assigned to him / her through the input unit 14 and the reader unit 17. Accordingly, when receiving the connection information input from the input unit 14 (step S11), the communication control unit 111 of the terminal device 10 transmits the connection information to the hospital server 20 (step S12).

  In the hospital server 20, when the communication control unit 211 receives the connection information transmitted from the terminal device 10 (step S21), the communication control unit 211 reads the connection information and each authentication information registered in the authentication repository 261. Are checked (step S22), and it is determined whether or not there is a match (step S23). Here, when it is determined that the authentication information does not match any authentication information registered in the authentication repository 261 (step S23; No), the communication control unit 211 determines that the access is unauthorized and responds that the access is denied. Is transmitted to the terminal device 10 (step S24), and the process is terminated.

  If it is determined in step S23 that there is authentication information that matches the connection information (step S23; Yes), the communication control unit 211 determines that the nurse corresponding to the nurse ID of the authentication information is the terminal device that is the access source. 10 is determined, and response information indicating that access is permitted is transmitted to the terminal device 10 (step S25). In this case, the communication control unit 211 maintains a session with the terminal device 10 and continues the nursing plan providing process (FIG. 9), the electronic medical record providing process (FIG. 10), or the action history registration process (FIG. 11). Continue to one of the following.

  On the other hand, in the terminal device 10, when the communication control unit 111 receives the response information from the hospital server 20 (step S13), it is determined whether or not this response information permits access (step S14). Here, when it is determined that the response information indicates that access is denied (step S14; No), the communication control unit 111 displays a screen informing that the access is denied on the display unit 15 (step S15). ), The process is terminated.

  If it is determined in step S14 that the response information indicates that access is permitted (step S14; Yes), the communication control unit 111 maintains a session with the in-hospital server 20 and provides a subsequent nursing plan. It continues to any one of the process (FIG. 9), the electronic chart providing process (FIG. 10), or the action history registration process (FIG. 11).

  As described above, since the hospital server 20 permits access only to a regular nurse registered in the authentication repository 261, security of various repositories such as an electronic medical record can be secured.

  Next, with reference to FIG. 9, the operation | movement at the time of referring a nursing plan from the terminal device 10 is demonstrated. Here, FIG. 9 is a flowchart showing the procedure of the nursing plan providing process performed between the terminal device 10 and the hospital server 20. This process can be executed after access is permitted in the authentication process of FIG.

  First, when the nursing plan reference unit 112 of the terminal device 10 receives an operation content instructing reference of a nursing plan from the input unit 14 (step S31), the nursing plan reference request is generated and transmitted to the hospital server 20 (step S31). Step S32).

  In the hospital server 20, when the communication control unit 211 receives a nursing plan reference request from the terminal device 10 (step S41), the nursing plan providing unit 212 sets the nurse ID of the terminal device 10 that has transmitted the nursing plan reference request. Based on this, the record associated with the nurse ID, that is, the nursing plan is read from the nursing plan repository 263 (step S42). Subsequently, the nursing plan providing unit 212 transmits the nursing plan read in step S42 to the terminal device 10 (step S43).

  In the terminal device 10, when the communication control unit 111 receives the nursing plan (step S33), the nursing plan reference unit 112 displays the nursing plan on the display unit 15 (step S34). In the subsequent step S35, the nursing plan reference unit 112 determines whether or not an operation content for ending reference to the nursing plan has been input to the input unit 14, and if it is determined that the operation content has not been input (step S35; No) ), The process returns to step S34 again. In addition, when an operation to end the nursing plan reference is input via the input unit 14 (step S35; Yes), the nursing plan reference unit 112 notifies the hospital server 20 of the reference end of the nursing plan. (Step S36). Then, the nursing plan reference unit 112 deletes the nursing plan displayed on the display unit 15 (step S37), and ends the process.

  On the other hand, in the in-hospital server 20, the nursing plan providing unit 212 determines whether an execution column of any nursing plan being provided to the terminal device 10 has been updated by an action history registration process described later. Here, when an update is detected (step S44; Yes), the nursing plan providing unit 212 returns to step S42 again, and transmits the read nursing plan to the terminal device 10 (step S43), whereby the execution column is updated. The nursing care plan after being done is displayed on the terminal device 10.

  In step S44, when the update of the nursing plan is not confirmed (step S44; No), the nursing plan providing unit 212 determines whether or not the terminal device 10 is notified of the end of the nursing plan reference (step S45). If it is determined not to be notified (step S45; No), the process returns to step S44 again. If the end of nursing plan reference is notified (step S45; Yes), the process ends.

  As described above, the hospital server 20 provides a nursing plan for the nurse who operates the terminal device 10 in response to a request from the terminal device 10. When the nursing plan execution column is updated, the updated nursing plan is transmitted to the terminal device 10, and the updated nursing plan is displayed on the display unit 15 of the terminal device 10. Thereby, since the nurse who operates the terminal device 10 can confirm an own nursing plan and its execution state easily, it can improve the convenience.

  Next, with reference to FIG. 10, the operation | movement at the time of referring an electronic medical record from the terminal device 10 is demonstrated. Here, FIG. 10 is a flowchart showing the procedure of the electronic medical record providing process performed between the terminal device 10 and the hospital server 20. This process can be executed after access is permitted in the authentication process of FIG.

  First, when the electronic medical chart reference unit 113 of the terminal device 10 receives an operation content instructing to refer to the electronic medical record for a specific patient ID from the input unit 14 (step S51), the electronic medical chart reference request including the patient ID is received. Is transmitted to the in-hospital server 20 (step S52).

  In the hospital server 20, when the communication control unit 211 receives the electronic medical record reference request from the terminal device 10 (step S61), the electronic medical record providing unit 213 determines the patient based on the patient ID included in the electronic medical record reference request. The electronic medical record associated with the ID is read from the electronic medical record repository 262 (step S62). Subsequently, the electronic medical record providing unit 213 transmits the electronic medical record read in step S62 to the terminal device 10 (step S63).

  In the terminal device 10, when the communication control unit 111 receives the electronic medical record (step S53), the electronic medical record reference unit 113 displays the electronic medical record on the display unit 15 (step S54). Subsequently, the electronic medical record reference unit 113 determines whether an editing operation for any item included in the electronic medical record has been input via the input unit 14 (step S55). If it is determined that no editing operation is input (step S55; No), the process proceeds to step S57.

  If it is determined in step S55 that an editing operation has been input for a specific item (step S55; Yes), the electronic medical record reference unit 113 displays the name of the item to be edited and the edited content in the hospital. The server 20 is notified (step S56), and the process proceeds to step S57.

  In subsequent step S57, the electronic medical chart reference unit 113 determines whether or not an operation content for ending reference to the electronic medical record has been input to the input unit 14, and if it is determined that it has not been input (step S57; No) ), The process returns to step S55. In addition, when an operation for ending reference to the electronic medical record is input via the input unit 14 (step S57; Yes), the electronic medical record reference unit 113 notifies the hospital server 20 of the reference end of the electronic medical record. (Step S58). Then, the electronic medical chart reference unit 113 deletes the electronic medical chart displayed on the display unit 15 (step S59), and ends the process.

  On the other hand, in the hospital server 20, the electronic medical record providing unit 213 determines whether or not the item name to be edited and the editing content are notified from the terminal device 10 (step S 64). Here, when it determines with not being notified (step S64; No), it transfers to step S66. In step S64, when the notification of the item name to be edited and the editing content is received (step S64; Yes), the electronic medical record providing unit 213 identifies the item to be edited from the electronic medical record being provided to the terminal device 10. Then, editing according to the editing content is performed (step S65).

  Subsequently, the electronic medical record providing unit 213 determines whether or not the terminal device 10 has been notified of the end of reference to the electronic medical record. If it is determined that the electronic medical record is not notified (step S66; No), the process returns to step S64 again. In addition, when the end of the reference of the electronic chart is notified (step S66; Yes), the process is ended.

  As described above, the hospital server 20 provides the terminal device 10 with the electronic medical record of the patient designated by the patient ID in response to a request from the terminal device 10. In addition, the contents edited in the electronic medical record in the terminal device 10 are reflected in the electronic medical record stored in the electronic medical record repository 262. Thereby, since the nurse who operates the terminal device 10 can browse and edit each patient's electronic medical record easily, the convenience can be improved.

  Next, with reference to FIG. 11, an operation when registering each nurse's action history in the action history repository 264 will be described. Here, FIG. 11 is a flowchart showing the procedure of the action history registration process performed between the terminal device 10 and the hospital server 20. This process can be executed after access is permitted in the authentication process of FIG.

  First, the action history registration unit 115 of the terminal device 10 determines whether or not a predetermined time (for example, 5 minutes) has elapsed since the previous action history registration request was transmitted (step S71). Here, when it determines with predetermined time not having passed (step S71; No), the action history registration part 115 transfers to step S73.

  If it is determined in step S71 that the predetermined time has elapsed (step S71; Yes), the behavior history registration unit 115 acquires position information indicating the current position acquired by the position information acquisition unit 114 and date / time information indicating the current date and time. The action history registration request including the above is transmitted to the hospital server 20 through the communication control unit 111 (step S72), and the process proceeds to step S73.

  In step S73, the action history registration unit 115 determines whether both the work content information and the patient information are continuously input (step S73). Here, when input cannot be confirmed (step S73; No), it returns to step S71 again. If it is determined in step S73 that the input has been made (step S73; Yes), the action history registration unit 115 represents the input work content information and patient information and the current position acquired by the position information acquisition unit 114. The action history registration request including the position information and the date / time information indicating the current date / time is transmitted to the hospital server 20 through the communication control unit 111 (step S74), and the process returns to step S71 again.

  Here, the predetermined time which becomes an index of determination in step S71 and step S73 may be the same value or different values. Further, in this process, the determination of step S71 and step S73 is performed sequentially. However, the present invention is not limited to this, and the processes of step S71 (and step S72) and step S73 (and step S74) are performed in parallel. It is good also as a form. In step S73, the input of patient information in step S51 of the electronic medical chart provision process described above is also included in the determination target.

  On the other hand, in the hospital server 20, when the communication control unit 211 receives an action history registration request from the terminal device 10 (step S81), the action history recording unit 214 transmits the action history registration request to the nurse of the terminal device 10. Various information included in the action history registration request is registered in the action history repository 264 in association with the ID (step S82).

  In addition, when the execution determination unit 215 detects the update of the action history repository 264 in accordance with the process of step S82, the execution determination process is executed (step S83), and this process ends. Hereinafter, the operation of the execution determination process in step S83 will be described with reference to FIG.

  FIG. 12 is a flowchart illustrating the procedure of the execution determination process. First, the execution determination unit 215 selects a nursing plan corresponding to the nurse ID newly registered in the action history repository 264 and the action date and time among the unchecked nursing plans registered in the nursing plan repository 263. Is extracted (step S91).

  Subsequently, when the execution determination unit 215 sets a search condition using elements included in the action history newly registered in the action history repository 264 (step S92), the nursing plan (work content) corresponding to the search condition is set. Is present in each nursing plan extracted in step S91 (step S93). If it is determined that there is no nursing plan corresponding to the search condition (step S93; No), the process returns to the action history registration process of FIG. 11 and the process ends.

  In Step S93, when it is determined that there is a nursing plan corresponding to the search condition (Step S93; Yes), the execution determination unit 215 registers a check flag in the execution column of the nursing plan determined to be applicable (Step S93). S94), the process returns to the action history registration process of FIG.

  As described above, in the action history registration process, each time an action history registration request is transmitted from the terminal device 10, the nurse ID of the nurse who operates the terminal device 10 is used for various information included in the action history registration request. And registered in the action history repository 264. If the action history registered in the action history repository 264 corresponds to a nursing plan (work content) in the nursing plan repository 263, a check flag is registered in the execution column of the nursing plan. Thereby, since the nursing plan executed by the nurse can be automatically checked (recorded), it is possible to save the trouble of manually checking and to improve convenience when performing the nursing work.

  In this process, the execution determination process is executed immediately after the action history repository 264 is updated. However, the present invention is not limited to this. For example, the execution determination process may be executed independently. In this case, for example, by executing the execution determination process at predetermined time intervals, it is possible to determine the execution of the nursing plan for each of one or more records newly registered in the behavior history repository 264. In addition, when it is determined that there are a plurality of nursing plans corresponding to the search condition, a check flag is registered in a nursing plan whose execution deadline (time) is earlier.

  Next, with reference to FIG. 13, the operation | movement at the time of alerting | reporting the unprocessed work content from the hospital server 20 to the terminal device 10 is demonstrated. Here, FIG. 13 is a flowchart showing a procedure of an unprocessed work notification process performed between the terminal device 10 and the hospital server 20.

  First, the nursing plan monitoring unit 216 of the in-hospital server 20 waits until a predetermined time (for example, 30 minutes) elapses after referring to the previous nursing plan repository 263 (step S101; No). When the predetermined time has elapsed (step S101; Yes), the nursing plan monitoring unit 216 refers to the nursing plan repository 263, and extracts the nursing plan associated with the current date that has not been checked in the execution column. (Step S102).

  Subsequently, the nursing plan monitoring unit 216 compares the current time with the time indicated by the execution deadline included in each nursing plan extracted in step S102 (step S103), and the time difference is a predetermined threshold value (for example, Nursing plans within one hour) are further extracted (step S104). If there is no nursing plan that falls within the threshold, the processing of steps S104 to S106 is skipped, and the process returns to step S101 again.

  The nursing plan monitoring unit 216 classifies the nursing plan extracted in step S104 for each nurse ID associated with the nursing plan (step S105). When the nursing plan monitoring unit 216 generates unprocessed work information for each classified nursing plan, the nursing plan monitoring unit 216 transmits the information to the terminal device 10 corresponding to the nurse ID through the communication control unit 211 (step S106). Return to again.

  On the other hand, when the terminal device 10 receives the unprocessed work information transmitted from the in-hospital server 20 (step S111), the communication control unit 111 converts the nursing plan included in the unprocessed work information into the nursing plan. By displaying on the display unit 15 together with a message confirming the execution, the nurse is notified of the existence of unprocessed work content (step S112).

  Here, FIG. 14 is a diagram illustrating an example of a display screen of unprocessed work information. In the figure, as the nursing plan included in the unprocessed work information, the execution deadline (November 9, 2010, 15:00) and the work content ("blood pressure measurement" of "patient 04" in "Room 303") are shown. In addition to the display, an example is shown in which a message indicating that this nursing plan is unprocessed is displayed.

  In this way, in the unprocessed work notification process, it is possible to notify each nurse of the nursing plans registered in the nursing plan repository 263 and whose execution deadline is approaching. You can prevent forgetting.

  In the present embodiment, the nursing plan included in the unprocessed work information is immediately displayed as the unprocessed work information is received. However, the present invention is not limited to this. For example, it is possible to notify that the unprocessed work information has been received with a message, an icon, etc., and display a nursing plan included in the unprocessed work information when a display is instructed via the input unit 14. Good. Moreover, when the terminal device 10 is provided with a speaker, an indicator lamp, etc., it is good also as a form which alert | reports reception of unprocessed work information using these.

  As mentioned above, although embodiment of this invention was described, the said embodiment was shown as an example and is not intending limiting the range of invention. The above embodiment can be implemented in various other forms, and various omissions, replacements, changes, additions, and the like can be made without departing from the scope of the invention. Moreover, the said embodiment and its deformation | transformation are included in the range of the invention, the summary, and the invention described in the claim, and its equal range.

  For example, in the above embodiment, the work content information representing the work content using the in-hospital device 30 is directly stored in the RFID tag 31 of the in-hospital device 30 as tag information. It is good also as a form which memorize | stores the information which indirectly represents as tag information. For example, the RFID tag 31 of the in-hospital device 30 stores identification information unique to the in-hospital device 30 (for example, a serial number, a management number, etc.) as tag information, and further, the in-hospital device 30 corresponding to the identification information. The action history recording unit of the in-hospital server 20 that has received the action history registration request from the terminal device 10 stores the table (conversion table) associated with the work content information in the in-hospital server 20 or the like. The conversion table may be referred to, and the identification information included in the action history registration request may be converted into work content information and then registered in the action history repository 264.

  In addition, the program executed by each device of the above embodiment is provided by being incorporated in advance in a storage medium (ROM or storage unit) included in each device, but is not limited thereto, and can be installed in a form or executable. Various types of files may be recorded and provided on a computer-readable recording medium such as a CD-ROM, a flexible disk (FD), a CD-R, or a DVD (Digital Versatile Disk). Furthermore, the storage medium is not limited to a medium independent of a computer or an embedded system, but also includes a storage medium in which a program transmitted via a LAN, the Internet, or the like is downloaded and stored or temporarily stored.

  Further, the program executed by each device of the above embodiment may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network, or via a network such as the Internet. It may be configured to be provided or distributed.

100 Nursing Support System 10 Terminal Device 11 CPU
111 Communication control unit 112 Nursing plan reference unit 113 Electronic medical record reference unit 114 Location information acquisition unit 115 Action history registration unit 12 ROM
13 RAM
14 Input unit 15 Display unit 16 Storage unit 17 Reader unit 18 Communication I / F
20 Hospital server 21 CPU
211 Communication Control Unit 212 Nursing Plan Providing Unit 213 Electronic Medical Record Providing Unit 214 Action History Recording Unit 215 Execution Determination Unit 216 Nursing Plan Monitoring Unit 22 ROM
23 RAM
24 Input Unit 25 Display Unit 26 Storage Unit 261 Authentication Repository 262 Electronic Medical Record Repository 263 Nursing Plan Repository 264 Action History Repository 27 Communication I / F
30 Hospital equipment 31 RFID tag 41 LAN

JP 2002-31471 A

Claims (6)

A nursing support system comprising a terminal device carried by a nurse and a server device capable of communicating with the terminal device,
The terminal device includes input means for accepting input of patient information for identifying a patient who is a subject of nursing work, and tag information representing work contents using the device from RFID tags attached to each device in the hospital. Reading means for reading, position acquisition means for acquiring terminal position information indicating the current position of the terminal device, and when the patient information is input and the tag information is read, the position acquisition means together with these information Transmitting means for transmitting the terminal location information acquired by the server to the server device as an action history;
With
The server device includes position information for specifying a position to perform nursing work, patient information for identifying a patient who is a subject of the nursing work, and work content information representing the content of the nursing work. A nursing plan storage means for storing the nursing plan, a receiving means for receiving the behavior history transmitted from the terminal device, a set of the terminal position information, the patient information and the tag information included in the behavior history, The position information, the patient information, and the work content information sets included in each nursing plan stored in the nursing plan storage means are compared, and the nursing plans in which the contents of the two sets are the same have been executed. Execution determination means for adding check information representing
A nursing support system characterized by having The terminal device further comprises nurse information input means for receiving input of nurse information for identifying a nurse who is an operator of the own device,
The transmission means includes the nurse information in the action history and transmits the information to the server device,
The nursing plan storage means stores the nursing plan of the nurse in association with the nurse information of each nurse,
The execution determination unit is configured to compare each nursing plan associated with the same nurse information as the nurse information included in the action history among the nursing plans stored in the nursing plan storage unit as the comparison target. The nursing support system according to claim 1, wherein: The server device further includes a nursing plan providing means for providing a nursing plan stored in the nursing plan storage means to the terminal device operated by a nurse of nurse information associated with the nursing plan,
The nursing support system according to claim 2, wherein the terminal device further includes nursing plan display means for displaying a nursing plan provided from the nursing plan providing means. The nursing plan storage means stores execution deadline information indicating an execution deadline of the nursing work included in the nursing plan,
The server device compares the execution deadline represented by the execution deadline information included in each nursing plan to which the check information is not added with the current date and time, and determines the nursing plan whose time difference is within a predetermined time. Further comprising nursing plan monitoring means for providing to the terminal device operated by the nurse of the nurse information associated with
4. The terminal device according to claim 2, further comprising an execution confirmation unit that displays the nursing plan provided from the nursing plan monitoring unit together with a message for confirming the execution of the nursing plan. Nursing support system. A terminal device carried by a nurse,
An input means for receiving input of patient information for identifying a patient who is a subject of nursing work;
Reading means for reading tag information representing the work content using the device from the RFID tag attached to each device in the hospital;
Position acquisition means for acquiring terminal position information representing the current position of the terminal device;
When the patient information is input and the tag information is read, the terminal position information acquired by the position acquisition unit together with the information is set as an action history, and the transmission means is transmitted to a server device that manages the action history. When,
A terminal device comprising: A server device capable of communicating with a terminal device carried by a nurse,
The nurse's position information that identifies the position where the nurse performs nursing work, patient information that identifies a patient who is the subject of the nursing work, and work content information that represents the content of the nursing work. Nursing plan storage means for storing nursing plans;
From the terminal device, position information indicating the current position of the terminal device, the patient information of the patient targeted by the nurse carrying the terminal device, and tag information indicating the work content of the nursing operation, Receiving means for receiving an action history including
A set of the terminal position information, the patient information, and the tag information included in the action history, and the position information, the patient information, and the work content information included in each nursing plan stored in the nursing plan storage unit. An execution determination means that compares the set and adds check information indicating that the care plan in which the contents of both sets match is already executed;
A server device comprising:

Images