JP6545871B2 - Terminal device, control method for terminal device, and control program for terminal device - Google Patents

Description

  The present invention relates to a display technique of medical information on medical care.

  Conventionally, when a patient in a hospital wants to know medical information such as a treatment, an examination, or an operation performed on itself, the medical information may be confirmed by a terminal device displayed as a pictogram or the like. This type of terminal device can be easily changed in display contents by updating data, and is therefore used in recent years because it is more convenient than paper or the like.

  For example, Patent Document 1 describes a terminal device that acquires medical information from a medical server and displays a pictogram based on the acquired medical information.

JP, 2015-18461, A

  However, the terminal device disclosed in Patent Document 1 has a problem that it is difficult to ensure security.

  One aspect of the present invention is to provide a program and the like that can improve security compared to the prior art.

In order to achieve the above object, a terminal device according to the present invention is:
A patient identification information acquisition unit that acquires patient identification information for identifying a patient;
The obtained the patient identification information after sending to the information processing apparatus, based on the acquired patient medical information from the information processing apparatus using the patient identification information, the displaying the patient screen in which the patient can be confirmed 1 Medical information display section,
A medical worker identification information acquisition unit for acquiring medical worker identification information for identifying a medical worker after display by the first medical information display unit;
The obtained the medical person identification information after transmitting to the information processing apparatus, based on the acquired patient medical information from the information processing apparatus using the patient identification information, the medical practitioner medical information of the patient A second medical information display unit for displaying a screen for a medical worker for confirming
Equipped.

In order to achieve the above object, another terminal device according to the present invention is:
A patient identification information acquisition unit that acquires patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display section,
A medical worker identification information acquisition unit for acquiring medical worker identification information for identifying a medical worker after display by the first medical information display unit;
After transmitting the acquired medical worker identification information to the information processing apparatus, the input screen acquired from the information processing apparatus is displayed to receive the input of the state information on the state of the patient An input screen display unit,
Equipped.

In order to achieve the above object, a control method of a terminal device according to the present invention is:
A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A medical worker identification information acquisition step of acquiring medical worker identification information for identifying a medical worker after display in the first medical information display step;
After transmitting the acquired medical worker identification information to the information processing apparatus, the medical worker performs medical information on the patient based on patient medical information acquired from the information processing apparatus using the patient identification information. A second medical information display step of displaying a screen for medical staff for confirming
including.
Further, in order to achieve the above object, another control method of a terminal apparatus according to the present invention is:
A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A doctor identification information acquisition step for acquiring, for example, a doctor identification information for identifying a medical worker after display in the first medical information display step;
An input screen which is an input screen acquired from the information processing apparatus after transmitting the acquired identification information for the doctor etc. to the information processing apparatus, the input screen for receiving the input of the state information related to the state of the patient Screen display step,
including.

In order to achieve the above object, a control program of a terminal device according to the present invention is:
A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A medical worker identification information acquisition step of acquiring medical worker identification information for identifying a medical worker after display in the first medical information display step;
After transmitting the acquired medical worker identification information to the information processing apparatus, the medical worker performs medical information on the patient based on patient medical information acquired from the information processing apparatus using the patient identification information. A second medical information display step of displaying a screen for medical staff for confirming
On a computer.
In order to achieve the above object, a control program of a terminal device according to the present invention is:
A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A doctor identification information acquisition step for acquiring, for example, a doctor identification information for identifying a medical worker after display in the first medical information display step;
An input screen which is an input screen acquired from the information processing apparatus after transmitting the acquired identification information for the doctor etc. to the information processing apparatus, the input screen for receiving the input of the state information related to the state of the patient Screen display step,
On a computer.

  Security in patient's medical information can be improved more than before.

It is a schematic diagram which shows the outline | summary of an information processing system. It is a block diagram which shows the hardware group of an information processing apparatus, a medical server, a terminal device, and an electronic medical chart server. It is a figure which shows an example of the data stored in medical information DB. It is a figure which shows an example of the data stored in plan information DB. It is a figure which shows an example of the data stored in test | inspection information DB. It is a figure which shows an example of the data stored in surgery information DB. It is an explanatory view explaining a screen for patients for displaying medical information on a patient. It is an explanatory view explaining an inspection display screen. It is an explanatory view explaining a surgery display screen. It is an explanatory view explaining an agreement screen. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the display process of the inspection display screen in this embodiment. It is the flowchart which showed the display process of a surgery display screen etc. in this embodiment. It is the flowchart which showed the display process of a surgery display screen etc. in this embodiment. It is the flowchart which showed the display process of a surgery display screen etc. in this embodiment. It is a block diagram which shows the hardware group of an information processing apparatus, a medical server, a terminal device, and an electronic medical chart server. It is a figure which shows an example of the data stored in ID type DB. It is a figure which shows an example of the data stored in vital DB. It is an explanatory view explaining a screen only for nurses. It is an explanatory view explaining a vital screen. It is an explanatory view explaining a nursing support record screen. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is a block diagram which shows the hardware group of an information processing apparatus, a medical server, a terminal device, and an electronic medical chart server. It is a figure which shows an example of the data stored in pictogram DB. It is explanatory drawing which shows the clinical path screen which displays a clinical path. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is a block diagram which shows the hardware group of an information processing apparatus, a medical server, a terminal device, and an electronic medical chart server. It is a figure which shows an example of the data stored in image data DB. It is an explanatory view explaining a doctor only screen. It is an explanatory view explaining an image selection screen. It is the flowchart which showed the processing procedure of the information processing system in this embodiment. It is the flowchart which showed the processing procedure of the information processing system in this embodiment.

Embodiment 1
Hereinafter, the present embodiment will be described with reference to the drawings. FIG. 1 is a schematic view showing an outline of an information processing system. The information processing system shown in FIG. 1 includes an information processing device 1, a medical server 2, a terminal device 3 and an electronic medical chart server 4. The information processing device 1, the medical server 2 and the terminal device 3 are mutually connected by a communication network N1 such as the Internet, a LAN (Local Area Network) or a mobile telephone network. The medical server 2 and the electronic medical record server 4 are mutually connected by a communication network N2 such as the Internet, a LAN or a mobile telephone network. The information processing device 1 transmits and receives information to and from the medical server 2 and the terminal device 3 via the communication network N1. The medical server 2 transmits / receives information to / from the electronic medical record server 4 via the communication network N2. Note that the electronic medical record server 4 is not connected to the information processing device 1 and the terminal device 3 via the communication network N1 from the viewpoint of security. Information in the electronic medical chart 421 in the present embodiment is transmitted and received using a system such as SS-MIX (Standardized Structured Medical Information eXchange), for example.

  The outline of the information processing system will be described below. The electronic medical record server 4 is a device for storing an electronic medical record 421 described later, and is, for example, a server computer. The electronic medical chart server 4 outputs the medical information and the like stored in the electronic medical chart 421 to the medical server 2.

  The medical server 2 is a device for storing an ID (identification information) for identifying a patient, a nurse or a doctor (user) or the like, medical information about medical treatment, and the like, and is, for example, a server computer or the like. The medical server 2 acquires medical information and the like from the electronic medical chart server 4. The medical server 2 stores the acquired medical information and the like in association with the ID. The medical server 2 outputs medical information and the like stored in association with the ID to the information processing apparatus 1.

  The information processing device 1 is a device that generates a screen or the like to be displayed on the terminal device 3 and is, for example, a personal computer or the like. The information processing apparatus 1 acquires an ID, medical information, and the like from the medical server 2. The information processing apparatus 1 generates a medical screen for displaying medical information based on the ID, the medical information, and the like. The information processing device 1 outputs the generated medical screen to the terminal device 3.

  The terminal device 3 is a device that displays a medical screen or the like, and is, for example, a tablet computer, a smartphone, a PDA (Personal Digital Assistant), a mobile phone, a personal computer, or the like. The terminal device 3 in the present embodiment will be described as a tablet computer. The terminal device 3 performs an authentication process from the barcode described in the wristband wound around the patient's hand (the detailed description will be described later). The terminal device 3 acquires the medical screen from the information processing device 1 after performing the authentication process. The terminal device 3 displays the acquired medical screen. The patient can know the medical practice and the like to be performed on the patient by confirming the medical screen.

  The details of the information processing system will be described below. FIG. 2 is a block diagram showing a hardware group of the information processing device 1, the medical server 2, the terminal device 3 and the electronic medical record server 4. The information processing apparatus 1 illustrated in FIG. 2 includes a central processing unit (CPU) 11, a storage unit 12, a RAM (storage unit) 13, an input unit 14, a display unit 15, a communication unit 16, and a clock unit 17.

  The CPU 11 is connected to hardware units via a bus. The CPU 11 includes, for example, one or more CPUs or multi-core CPUs. The CPU 11 controls each part of the hardware in accordance with the program 12P stored in the storage unit 12.

  The storage unit 12 is, for example, a hard disk or a large capacity memory. The storage unit 12 stores various data and programs 12P required when the CPU 11 performs processing. The RAM 13 is, for example, a static random access memory (SRAM) or the like. The RAM 13 also functions as a storage unit, and temporarily stores various data generated when the CPU 11 executes various programs.

  The input unit 14 is an input device such as a mouse or a keyboard, and transmits the received operation information to the CPU 11. The display unit 15 displays the image data transmitted from the CPU 11. The display unit 15 is, for example, a liquid crystal screen. The communication unit 16 is, for example, a wireless LAN card or a communication module for a mobile phone, and transmits and receives various types of information between the medical server 2 and the terminal device 3 via the communication network N1. The clock unit 17 counts, for example, the time and date at the present time, and outputs the clocking result to the CPU 11 according to the request of the CPU 11.

  The medical server 2 illustrated in FIG. 2 includes a CPU 21, a storage unit 22, a RAM 23, an input unit 24, a display unit 25, and a communication unit 26. The configuration of the medical server 2 is the same as the configurations of the CPU 11, the RAM 13, the input unit 14 and the display unit 15 of the information processing apparatus 1, and the description thereof will be briefly described. I omit it.

  The storage unit 22 is, for example, a hard disk or a large capacity memory. The storage unit 22 stores various data required when the CPU 21 performs processing, a medical information DB 221, a schedule information DB 222, an examination information DB 223, a surgery information DB 224, and a program 22P. The communication unit 26 is, for example, a wireless LAN card or a communication module for a mobile phone, and transmits and receives various types of information between the information processing apparatus 1 and the terminal device 3 via the communication network N1. The communication unit 26 transmits and receives medical information to and from the electronic medical record server 4 via the communication network N2.

  The terminal device 3 illustrated in FIG. 2 includes a CPU 31, a storage unit 32, a RAM 33, an input unit 34, a display unit 35, a communication unit 36, and an imaging unit 37. The configurations of the CPU 31, the RAM 33, and the display unit 35 of the terminal device 3 are the same as the configurations of the CPU 11, the RAM 13, and the display unit 15 of the information processing apparatus 1, and therefore the descriptions thereof will be omitted.

  The storage unit 32 is, for example, a hard disk or a large capacity memory. The storage unit 32 stores various data required when the CPU 31 performs processing, and the program 32P. The input unit 34 is an input device such as a touch panel, and outputs the received operation information to the CPU 31. The input unit 34 also includes an electronic pen or the like that performs input to the touch panel. The communication unit 36 is, for example, a wireless LAN card or a communication module for a mobile phone, and transmits and receives various types of information between the information processing apparatus 1 and the medical server 2 via the communication network N1. The imaging unit 37 is, for example, a CCD camera or a CMOS camera, and obtains image data by photoelectrically converting an optical signal input through the CCD or COMS.

  The electronic medical record server 4 shown in FIG. 2 includes a CPU 41, a storage unit 42, a RAM 43, an input unit 44, a display unit 45, and a communication unit 46. The configurations of the CPU 41, the RAM 43, the input unit 44 and the display unit 45 of the electronic medical record server 4 are the same as the configurations of the CPU 11, the RAM 13, the input unit 14 and the display unit 15 of the information processing apparatus 1, I omit it.

  The storage unit 42 is, for example, a hard disk or a large capacity memory. The storage unit 42 stores various data required for the CPU 41 to perform processing, an electronic medical record 421 and a program 42P. The electronic medical record 421 includes, for example, medical information, schedule information indicating a schedule for performing a medical procedure, examination information, surgery information, and the like. The communication unit 46 is, for example, a wireless LAN card or a communication module for mobile phone, and transmits and receives information in the electronic medical chart 421 with the medical server 2 via the communication network N2.

  FIG. 3 is a diagram showing an example of data stored in the medical information DB 221. As shown in FIG. The medical information DB 221 is a database for storing medical information and the like. The medical information is, for example, rehabilitation information, medicine information, examination information, surgery information, treatment information, attention message, pictogram, nutrition instruction and vital etc. described later. The medical information is not limited to the above, and information regarding medical care is included. The medical information DB 221 includes a patient ID column, a rehabilitation information column, a medicine information column, an examination information column, a surgery information column, a treatment information column, an attention message column, a pictogram column, and the like. The patient ID column stores the patient ID for identifying the patient. Rehab information indicating rehabilitation content is stored in the rehab information column in association with the patient ID. The drug information column stores drug information indicating the contents of the drug.

  In the examination information row, examination information indicating the contents of the examination is stored in association with the patient ID. For example, computed tomography (CT) examination, blood examination, magnetic resonance imaging (MRI) examination and the like are stored in the examination information sequence. The surgery information row stores surgery information indicating the contents of the surgery. For example, open surgery, open surgery, open surgery, etc. are stored in the operation information row. The treatment information column stores treatment information indicating the contents of treatment. For example, hemostasis treatment, wound treatment, burn treatment and the like are stored in the treatment information row. The hemostatic treatment is a treatment to hemostasis with a bandage or the like. Wound treatment is a treatment to suture or the like to a wound. The burn treatment is a treatment for cooling the burn injury. The caution message string stores a caution message indicating a patient's caution. In the pictogram sequence, pictograms indicating medical care for the patient are stored.

  The storage method of the medical information DB 221 is as follows. The CPU 21 receives an input of a patient ID from the input unit 24 by a doctor or a nurse. The CPU 21 stores the received patient ID in the medical information DB 221. The CPU 21 outputs a request for medical information from the communication unit 26 to the electronic medical chart server 4. The CPU 41 acquires a request for medical information from the electronic medical chart server 4 by the communication unit 46. The CPU 41 causes the communication unit 46 to output the medical information stored in the electronic medical chart 421 to the medical server 2. The CPU 21 acquires medical information at the communication unit 26. The CPU 21 stores medical information in the medical information DB 221 in association with a patient ID. In addition, each row of medical information DB221 is matched.

  FIG. 4 is a diagram showing an example of data stored in the schedule information DB 222. As shown in FIG. The schedule information DB 222 is a database for storing schedule information and the like. The schedule information DB 222 includes a patient ID column, a medical date column, a medical time column, a medical information column, and the like. The patient ID is stored in the patient ID column. In the medical date column, the medical date on which medical practice is performed in association with the patient ID is stored. In the medical time column, medical times at which medical actions are performed are stored in association with patient IDs. Medical information is stored in the medical information row in association with the patient ID.

  The storage method of the schedule information DB 222 is as follows. The CPU 21 receives an input of a patient ID from the input unit 24 by a doctor or a nurse. The CPU 21 stores the received patient ID in the schedule information DB 222. The CPU 21 outputs a request for schedule information from the communication unit 26 to the electronic medical record server 4. The CPU 41 acquires a request for schedule information from the electronic medical record server 4 by the communication unit 46. The CPU 41 causes the communication unit 46 to output the schedule information stored in the electronic medical chart 421 to the medical server 2. The CPU 21 acquires schedule information at the communication unit 26. The CPU 21 stores the schedule information in the schedule information DB 222 in association with the patient ID. In addition, each column of schedule information DB222 is matched.

  FIG. 5 is a view showing an example of data stored in the examination information DB 223. As shown in FIG. The examination information DB 223 is a database that stores examination information and the like. The examination information DB 223 includes an examination information column, an examination explanation column, a previous day examination explanation column, and a present day examination explanation column. The examination information is stored in the examination information sequence. An examination explanation is stored in the examination explanation column. The exam description is an exam description message that describes the overall exam performed on the patient. The examination description is, for example, the contents of the examination, the purpose of the examination, or the explanation of the danger. The previous day inspection explanation is stored in the previous day inspection explanation column. The previous day's examination description is the previous day's examination explanation message showing a description of the medical practice to be performed on the patient the day before the examination. The test description on the previous day is, for example, the contents of the meal taken on the day before the test, the contents of the medicine to be given, or general precautions. On the day, the examination explanation is stored on the day. On-the-day examination description is the on-the-day examination explanation message indicating the explanation of the medical practice to be performed on the patient on the day of the examination. The examination description on the day is, for example, the contents of the meal to be taken on the day of the examination, the contents of the medicine to be given, the clothes to be worn or general precautions, etc. The examination explanation, the previous day examination explanation, and the present day examination explanation are not limited to the message, and may be an image or a sound.

  The storage method of the examination information DB 223 is as follows. The CPU 21 outputs a request for examination information from the communication unit 26 to the electronic medical record server 4. The CPU 41 acquires a request for examination information and the like from the electronic medical record server 4 by the communication unit 46. The CPU 41 outputs examination information and the like stored in the electronic medical chart 421 to the medical server 2 through the communication unit 46. The CPU 21 causes the communication unit 26 to acquire examination information and the like. The CPU 21 stores examination information and the like in the examination information DB 223. In addition, each column of inspection information DB223 is matched.

  FIG. 6 is a diagram showing an example of data stored in the surgery information DB 224. As shown in FIG. The surgery information DB 224 is a database for storing surgery information and the like. The surgery information DB 224 includes a surgery information row, a surgery explanation row, a surgery description flag row, a previous day surgery description row, a previous day surgery description flag row, a same day surgery description row, a same day surgery description flag row, a later day surgery description row, a later day surgery description flag row and It has a consent flag column. Operation information is stored in the operation information row.

  The surgical explanation column stores the surgical explanation. A surgical instruction is a surgical instruction message indicating an overall surgical instruction to be performed on a patient. The operation explanatory message may be, for example, the name and method of planned surgery, expected complications, contingencies or risks, expected effects of planned surgery, trend of expected symptoms if not received. , Possible other treatments or treatment if there is a need for emergency treatment during implementation, etc. The surgery explanation flag row stores a surgery explanation flag indicating whether the surgery explanation message is displayed. The previous day operation explanation row is stored in the previous day operation description column. The previous day's operation description is the previous day's operation explanatory message showing a description of the medical practice to be performed on the patient the day before the operation. The previous day operation instruction message includes, for example, the contents of the examination performed the day before the operation, the contents of the meal to be taken, the contents of the medicine to be given, the contents of the treatment to be performed, or the general attention. The previous day surgery explanation flag row stores the previous day surgery explanation flag indicating whether or not the previous day surgery explanation message is displayed.

  On the day of the operation description row, the operation description is stored. The operation explanation on the day is the operation explanation message on the previous day showing the explanation of the medical practice performed for the patient on the day of the operation. On the day of the operation, for example, the flow of the entire operation, precautions for the operation, the contents of the diet to be taken on the day of the operation, the contents of the medicine to be given or the general attention. On the day of the operation explanation flag row, a day of the operation explanation flag indicating whether or not the operation explanation message has been displayed is stored. A description of the operation is stored later in the operation description column. The operation explanation on the next day is an operation explanation message on the previous day showing an explanation of the medical practice to be performed on the patient on the day after the operation. The description of the operation at a later date may be, for example, the rehabilitation to be performed the day after the operation, the contents of the examination to be performed, the contents of the meal to be taken, the contents of the medicine to be given, the contents of the treatment to be performed or general attention. A later operation explanation flag indicating whether or not the later operation explanation message is displayed is stored in the later operation description flag column. In the agreement flag column, an agreement flag indicating whether or not to perform the operation is stored.

  When each of the operation explanation flag, the day operation explanation flag, the day operation explanation flag and the day operation explanation flag is TRUE, it indicates that the operation explanation, the day operation explanation, the day operation description and the day operation description are displayed. When each of the operation explanation flag, the day operation explanation flag, the day operation explanation flag and the day operation explanation flag is FALSE, it indicates that the operation explanation, the day operation explanation, the day operation description and the day operation description are not displayed. If the consent flag is TRUE, it indicates that the operation has been agreed. If the consent flag is FALSE, it indicates that the operation has not been agreed. In addition, when the consent flag is TRUE, it is considered as consent information.

  The surgery explanation flag, the previous day surgery explanation flag, the same day surgery explanation flag, the later surgery explanation flag and the agreement flag are initially set to FALSE. The explanation on surgery, the explanation on surgery on the previous day, the explanation on surgery on the day, and the explanation on surgery on the next day are not limited to messages, and may be images or sounds.

  The storage method of the surgery information DB 224 is as follows. The CPU 21 outputs a request for operation information and the like from the communication unit 26 to the electronic medical record server 4. The CPU 41 acquires a request for operation information and the like from the electronic medical record server 4 by the communication unit 46. The CPU 41 outputs the surgery information and the like stored in the electronic medical chart 421 to the medical server 2 by the communication unit 46. The CPU 21 causes the communication unit 26 to acquire surgery information and the like. The CPU 21 stores surgery information and the like in the surgery information DB 224. The agreement flag column is set in advance to FALSE. In addition, each row of surgery information DB224 is matched.

  FIG. 7 is an explanatory view for explaining a patient screen 5 for displaying medical information of a patient. As shown in FIG. 7, the patient screen 5 has a medical information display field 50 provided on the right side, a switching button 54 provided on the lower side of the medical information display field 50, and an upper left part of the medical information display field 50. And a date field 55 provided. The medical information display field 50 includes a schedule field 51 provided on the left, a caution field 52 provided on the right, and a pictogram field 53 provided below the schedule field 51 and the caution field 52.

  The medical information display column 50 is a column for displaying the medical information of the patient. The schedule column 51 is a column for displaying today's daily schedule. The caution column 52 is a column for displaying a caution message for the patient. The pictogram column 53 is a column for displaying a pictogram. The switching button 54 is a button for switching the screen. The switching button 54 comprises a rehabilitation, medication, examination, surgery and treatment button. The date field 55 is a field for displaying the current date. The rehabilitation button is a button for switching to a screen displaying information on patient's rehabilitation. The drug button is a button for switching to a screen for displaying a drug to be given to the patient. The examination button is a button for switching to the examination display screen 6 for displaying the examination to be performed on the patient. The surgery button is a button for switching to a surgery display screen (description screen) 7 for displaying a description on surgery to be performed on a patient. The treatment button is a button for switching to a treatment display screen for displaying a treatment to be performed on the patient. In the present embodiment, the examination display screen 6 and the surgery display screen 7 will be described as a representative.

  An information processing system in the present embodiment will be described. First, the information processing system performs an authentication process. The specific authentication process is as follows. The patient in the present embodiment has a wristband on which a one-dimensional or two-dimensional barcode is described. The barcode contains the patient ID. The patient takes an image of the bar code by the imaging unit 37 of the terminal device 3. The CPU 31 acquires the barcode captured by the imaging unit 37. The CPU 31 converts the barcode obtained using image processing into a patient ID "001". That is, the wristband is an identification medium including identification information. The identification medium is a medium such as an instrument or device for identifying a patient, a nurse or a doctor who owns the identification medium via identification information. In the present embodiment, the barcode is described on the wristband, but the present invention is not limited to this. The wristband may describe an image. Also, the wristband may describe a list of numbers, letters or symbols or a combination thereof.

  Although a wrist band is used as an identification medium in the present embodiment, a wireless tag for performing short distance communication or an IC card on which an IC (Integrated Circuit) chip is mounted may be used as an identification medium. The usage method of the wireless tag is as follows. The patient brings the wireless tag close to the terminal device 3. The wireless tag transmits a wireless signal including the patient ID to the terminal device 3. The CPU 31 receives a wireless signal from the wireless tag by the communication unit 36, and acquires the patient ID included in the wireless signal received by the communication unit 36. The usage of the IC card is as follows. The patient touches the IC card on a card reader (not shown) attached to the terminal device 3. The card reader reads the patient ID contained in the IC chip. The CPU 31 acquires the read patient ID from the card reader.

  The CPU 31 outputs the patient ID “001” from the communication unit 36 to the medical server 2. The CPU 21 acquires the patient ID “001” from the terminal device 3 by the communication unit 26. The CPU 21 outputs the acquired patient ID “001” and the medical information DB 221, the schedule information DB 222, the examination information DB 223, and the surgery information DB 224 stored in the storage unit 22 from the communication unit 26 to the information processing apparatus 1. The CPU 11 acquires the patient ID “001”, the medical information DB 221, the schedule information DB 222, the examination information DB 223, and the surgery information DB 224 from the medical server 2 by the communication unit 16. The CPU 11 temporarily stores the patient ID in the RAM 13. Further, the CPU 11 may store the patient ID in the storage unit 12. Alternatively, the CPU 11 may not only acquire the medical information DB 221 simultaneously with the patient ID, but may also acquire the medical information DB 221 and the like in advance. The CPU 11 refers to the medical information DB 221 and determines whether or not the patient ID "001" is stored. The CPU 11 determines that the patient ID "001" is stored in the medical information DB 221. The CPU 11 generates the patient screen 5 based on the medical information DB 221.

  Hereinafter, a method of generating the patient screen 5 will be described. The CPU 11 acquires the current date “August 20, 2015” from the timer unit 17. The CPU 11 generates the current date "August 20, 2015" in the date field 55. The CPU 11 refers to the schedule information DB 222. The CPU 11 uses the medical time "10:20" and the medical information "CT examination" corresponding to the patient ID "001" of the date "August 20, 2015", the medical time "14:00" and the medical information "rehab" Also, the medical time "18:00" and the medical information "nutrition guidance" are generated in the schedule column 51.

  The CPU 11 refers to the medical information DB 221. The CPU 11 generates a caution message “alcohol prohibited” or the like corresponding to the patient ID “001” in the caution column 52. The CPU 11 generates a pictogram H or the like corresponding to the patient ID “001” in the pictogram column 53.

  The CPU 11 outputs the generated patient screen 5 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the patient screen 5 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the patient screen 5 on the display unit 35.

  Next, the operation of the patient screen 5 will be described. The patient touches the examination button of the switching button 54 at the input unit 34. The CPU 31 receives an input of the inspection button. The CPU 31 outputs an output request for the examination display screen 6 from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires an output request of the examination display screen 6 from the terminal device 3 by the communication unit 16. The CPU 11 generates the examination display screen 6 based on the examination information DB 223. The CPU 11 outputs the examination display screen 6 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the examination display screen 6 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the examination display screen 6 on the display unit 35.

  Also, the patient touches the operation button of the switching button 54 at the input unit 34. The CPU 31 receives an input of the operation button. The CPU 31 outputs an output request for the surgery display screen 7 from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires an output request of the surgery display screen 7 from the terminal device 3 by the communication unit 16. The CPU 11 generates the surgery display screen 7 based on the surgery information DB 224. The CPU 11 outputs the surgery display screen 7, the surgery explanation flag, the surgery explanation flag on the previous day, the surgery explanation flag on the day, and the surgery explanation flag on the later day from the communication unit 16 to the terminal device 3. The CPU 31 acquires the surgery display screen 7, the surgery explanation flag, the previous day surgery explanation flag, the today's surgery explanation flag, and the later surgery explanation flag from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the surgery display screen 7 on the display unit 35.

  FIG. 8 is an explanatory view for explaining the examination display screen 6. As shown in FIG. 8, the examination display screen 6 has the examination name field 61 provided at the top, the examination explanation button 62 provided at the bottom of the examination name field 61, and the previous day provided at the bottom of the examination explanation button 62 The examination explanation button 63, the same day examination explanation button 64 provided at the lower part of the previous day examination explanation button 63, and the switching button 65 provided at the lower part are provided.

  Hereinafter, a method of generating the examination display screen 6 will be described. The CPU 11 refers to the examination information DB 223. The CPU 11 generates examination information “CT examination” in the examination name field 61. The CPU 11 generates the beginning of the previous day's examination explanation message “body to the present ...” on the left of the previous day examination explanation button 63. The CPU 11 generates, on the left of the examination explanation button 64 on the current day, the beginning of the examination explanation message on the current day "take enough sleep ...". The changeover button 65 comprises a rehabilitation, medication, examination and surgery button. The rehabilitation button, the medication button, the examination button and the surgery button are buttons that operate in the same manner as the rehabilitation button, the medicine button, the examination button and the surgery button in the switching button 54.

  Next, the operation of the examination display screen 6 will be described. The patient touches the examination explanation button 62 at the input unit 34. The CPU 31 receives an input of the examination explanation button 62. The CPU 31 displays a test explanation message (not shown) on the display unit 35. The patient touches the examination explanation button 63 on the previous day by the input unit 34. The CPU 31 receives an input of the examination explanation button 63 on the previous day. The CPU 31 displays the previous day examination explanation message (not shown) on the display unit 35. The patient touches the examination explanation button 64 on the current day by the input unit 34. The CPU 31 receives an input of the examination explanation button 64 on the current day. The CPU 31 displays an examination explanation message (not shown) on the current day on the display unit 35.

  FIG. 9 is an explanatory view for explaining the surgery display screen 7. As shown in FIG. 9, the surgery display screen 7 is provided on the right of the surgery name field 71 provided at the top, the surgery explanation button 72 provided at the bottom of the surgery name field 71, and the surgery explanation button 72. A consent document button (acquisition button) 73, the previous day operation explanation button 74 provided at the bottom of the consent document button 73, a same day operation explanation button 75 provided at the bottom of the previous day operation explanation button 74, and the day operation explanation button 75 The operation description button 76 provided on the lower part of the lower part and the switching button 77 provided on the lower part. The operation explanation button 72 is a button for displaying the operation explanation. The consent document button 73 is a button for acquiring the consent screen 8 for accepting the input of the consent information and displaying it on the display unit 35. The consent document button 73 is initially prohibited from being input, and is grayed out on the screen. The previous day operation description button 74 is a button for displaying the previous day operation description. The surgery explanation button 75 on the day is a button for displaying the surgery explanation on the day. A later-described operation explanation button 76 is a button for displaying the later-described operation description. The surgery explanation button 72, the previous day surgery explanation button 74, the same day surgery explanation button 75, and the later day surgery explanation button 76 are grayed out in the initial state.

  Hereinafter, a method of generating the surgery display screen 7 will be described. The CPU 11 refers to the surgery information DB 224. The CPU 11 generates the surgery information “open surgery” in the surgery name field 71. The CPU 11 generates on the left of the operation explanation button 74 on the previous day the beginning of the operation explanation message on the previous day "body to the present ...". The CPU 11 generates on the left side of the operation explanation button 75 on the day, the beginning of the operation explanation message on the day, "take enough sleep ...". The CPU 11 later generates an opening “Post-operative pain ...” on the left side of the operation explanation button 76 later. The switching button 77 has the same configuration as the switching button 65, and the description is omitted for the sake of brevity.

  Next, the operation of the surgery display screen 7 will be described. The patient touches the operation explanation button 72 at the input unit 34. The CPU 31 receives an input of the operation explanation button 72. The CPU 31 displays a surgery explanation message (not shown) on the display unit 35. The CPU 31 cancels the gray out display of the operation explanation button 72. The CPU 31 sets the surgery explanation flag to TRUE. The patient touches the operation explanation button 74 on the previous day by the input unit 34. The CPU 31 receives an input of the operation explanation button 74 the day before. The CPU 31 displays a surgery explanation message (not shown) the day before on the display unit 35. The CPU 31 cancels the grayed out display of the operation explanation button 74 the day before. The CPU 31 sets the operation description flag to TRUE the previous day. The patient touches the operation explanation button 75 on the day by the input unit 34. The CPU 31 receives an input of the operation explanation button 75 on the day. The CPU 31 displays a surgery explanation message (not shown) on the current day on the display unit 35. The CPU 31 cancels the gray out display of the operation explanation button 75 on the day. The CPU 31 sets the operation explanation flag to TRUE on the day.

  The patient touches the operation explanation button 76 at the input unit 34 later. The CPU 31 receives an input of the operation explanation button 76 later. The CPU 31 later displays a surgery explanation message (not shown) on the display unit 35. The CPU 31 cancels the gray out display of the operation explanation button 76 later. The CPU 31 later sets the surgery explanation flag to TRUE.

  The CPU 31 determines whether the surgery explanation flag, the previous day surgery explanation flag, the today's surgery explanation flag, and the later surgery explanation flag are TRUE. That is, the CPU 31 determines whether or not each operation description button 72, the previous operation description button 74, the current operation description button 75, and the later operation description button 76 have been received by determining whether each flag is TRUE. Do. The CPU 31 determines that the surgery explanation flag, the previous day surgery explanation flag, the current day surgery explanation flag, and the later day surgery explanation flag are TRUE. Since the operation explanation flag, the day operation explanation flag, the day operation explanation flag, and the day operation explanation flag are TRUE, the CPU 31 enables the acceptance of the input of the consent document button 73 and cancels the gray out display of the consent document button 73. The patient touches the consent document button 73 at the input unit 34. The CPU 31 receives the input of the consent document button 73. The CPU 31 outputs an output request for the consent screen 8 from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires an output request for the consent screen 8 from the terminal device 3 by the communication unit 16. The CPU 11 generates the consent screen 8 based on the medical information DB 221. The CPU 11 outputs the consent screen 8 to the terminal device 3 by the communication unit 16. The CPU 31 acquires the consent screen 8 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the consent screen 8 on the display unit 35.

  FIG. 10 is an explanatory view for explaining the consent screen 8. As shown in FIG. 10, the consent screen 8 includes the operation message 80 provided at the top, the consent button 81 provided at the left, the non-consent button 82 provided at the right, the consent button 81 and the non-agreement. A name field 83 provided at the lower part of the button 82 and an address field 84 provided at the lower side of the name field 83 are provided. The operation message 80 is a message indicating that the description of the operation has been completed. The consent button 81 is a button indicating that the user consents to the operation. The non-consent button 82 is a button indicating that the user does not agree to the operation. The agreement button 81 and the non-agreement button 82 are prohibited from inputting from the input unit 34 in the initial state. The name column 83 is a column for receiving an input of a signature image of a name. The signature image is an image of a signature represented by the patient's handwriting. A specific method of inputting a signature image will be described later. The address column 84 is a column for receiving an input of a signature image of an address.

  Hereinafter, a method of generating the consent screen 8 will be described. The CPU 11 refers to the medical information DB 221. Since the patient ID is "001" and the operation information is open surgery, the CPU 11 described in the operation message 80 for the patient of "patient ID" 001 "the current medical condition and the open operation." Generate

  Next, the operation of the agreement screen 8 will be described. The patient inputs a signature image of his / her name and address in the name column 83 and the address column 84 in the input unit 34. Specifically, the patient writes his / her name and address in the name section 83 and the address section 84 on the touch panel with the electronic pen of the input unit 34. The signature image of the name and the address may be manually input to the touch panel of the input unit 34. The CPU 31 receives an input of a signature image of a name and an address. The CPU 31 determines whether an input of a signature image of a name and an address has been received. The CPU 31 determines that the input of the signature image of the name and the address has been received. The CPU 31 permits the input of the agree button 81 and the disagree button 82. The patient touches the consent button 81 at the input unit 34. The CPU 31 receives an input of the consent button 81. The CPU 31 sets the consent flag to TRUE. The patient touches the non-agreement button 82 at the input unit 34. The CPU 31 receives an input of the non-agreement button 82. The CPU 31 sets the consent flag to FALSE.

  If the agreement flag is TRUE, the CPU 31 generates an agreement message indicating that the operation has been agreed. The consent message is, for example, “Patient A has agreed to open surgery”. The CPU 11 generates a consent document in which the consent screen 8 is documented. The written consent form is, for example, a document obtained by converting the consent screen 8 into PDF (Portable Document Format (registered trademark)). The written consent is not limited to the PDF, but may be generated in another written form. The CPU 31 outputs the generated consent message, the consent document, and the set consent flag from the communication unit 36 to the information processing apparatus 1. The CPU 11 obtains the consent message, the consent document, and the set consent flag from the terminal device 3 by the communication unit 16. The CPU 11 displays the consent message on the display unit 15. The CPU 11 updates the consent flag of the surgery information DB 224 to TRUE. The CPU 11 stores the PDF-formed consent document in the storage unit 12. The consent document and the consent message may be output to the medical server 2 or another terminal device (not shown) operated by a doctor.

  11 to 12 are flowcharts showing the processing procedure of the information processing system in the present embodiment. The patient takes an image of the bar code by the imaging unit 37 of the terminal device 3. The CPU 31 acquires the barcode captured by the imaging unit 37 (step S11). The CPU 31 converts the barcode acquired using image processing into a patient ID (step S12). The CPU 31 causes the communication unit 36 to output the patient ID to the medical server 2 (step S13). The CPU 21 acquires the patient ID from the terminal device 3 by the communication unit 26 (step S14). The CPU 21 outputs the acquired patient ID and the medical information DB 221, the schedule information DB 222, the examination information DB 223, and the surgery information DB 224 stored in the storage unit 22 from the communication unit 26 to the information processing apparatus 1 (step S15). The CPU 11 acquires the patient ID, the medical information DB 221, the schedule information DB 222, the examination information DB 223, and the surgery information DB 224 from the medical server 2 by the communication unit 16 (step S16). The CPU 11 refers to the medical information DB 221, and determines whether or not the patient ID "001" is stored (step S17).

  If the CPU 11 determines that the acquired patient ID is not stored in the medical information DB 221 (step S17: NO), the process ends. If the CPU 21 determines that the acquired patient ID is stored in the medical information DB 221 (step S17: YES), the CPU 21 generates the patient screen 5 based on the medical information DB 221 and the schedule information DB 222 (step S18). The CPU 11 outputs the patient screen 5 from the communication unit 16 to the terminal device 3 (step S19). The CPU 31 acquires the patient screen 5 from the information processing apparatus 1 by the communication unit 36 (step S20). The CPU 31 displays the patient screen 5 on the display unit 35 (step S21).

  The CPU 31 determines whether or not the inspection button input has been received (step S22). When the CPU 31 determines that the input of the inspection button has not been received (step S22: NO), the process proceeds to step S24. When the CPU 31 determines that the inspection button input has been received (step S22: YES), the CPU 31 performs a display process of the inspection display screen 6 (step S23).

  The CPU 31 determines whether or not the input of the operation button has been received (step S24). If the CPU 31 determines that the input of the operation button has not been received (step S24: NO), the process proceeds to step S21 to repeat the process. When the CPU 31 determines that the input of the surgery button has been received (step S24: YES), the display process of the surgery display screen 7 is performed (step S25), the process moves to step S21, and the process is repeated.

  FIG. 13 is a flowchart showing display processing of the examination display screen 6 in the present embodiment. When the step S22 is YES, the CPU 31 outputs an output request for the examination display screen 6 from the communication unit 36 to the information processing apparatus 1 (step S31). The CPU 11 acquires an output request for the examination display screen 6 from the terminal device 3 by the communication unit 16 (step S32). The CPU 11 generates the examination display screen 6 based on the examination information DB 223 (step S33).

  The CPU 11 outputs the examination display screen 6 to the terminal device 3 by the communication unit 16 (step S34). The CPU 31 acquires the examination display screen 6 from the information processing apparatus 1 by the communication unit 36 (step S35). The CPU 31 displays the examination display screen 6 on the display unit 35 (step S36).

  The CPU 31 determines whether or not the input of each explanation column has been received (step S37). Specifically, the CPU 31 determines whether or not the input of the examination explanation button 62, the previous day examination explanation button 63, or the day examination explanation button 64 has been received. If the CPU 31 determines that the input of each explanation column has not been received (step S37: NO), the display process of the examination display screen 6 is ended, and the process proceeds to step S24. If the CPU 31 determines that the input in each explanation column has been received (step S37: YES), the CPU 31 displays an explanation message such as an examination explanation message, a previous day examination explanation message, or a day inspection explanation message corresponding to each explanation field (step S38). The processing for displaying the examination display screen 6 is ended, and the process proceeds to step S24.

  14 to 16 are flowcharts showing display processing of the surgery display screen 7 etc. in the present embodiment. When the step S24 is YES, the CPU 31 outputs an output request for the surgery display screen 7 from the communication unit 36 to the information processing apparatus 1 (step S41). The CPU 11 acquires an output request for the surgery display screen 7 from the terminal device 3 by the communication unit 16 (step S42). The CPU 11 generates the surgery display screen 7 based on the surgery information DB 224 (step S43).

  The CPU 11 outputs the surgery display screen 7, the surgery explanation flag, the previous day surgery explanation flag, the today's surgery explanation flag, and the later surgery explanation flag to the terminal device 3 by the communication unit 16 (step S44). The CPU 31 acquires the surgery display screen 7, the surgery explanation flag, the previous day surgery explanation flag, the today's surgery explanation flag, and the later day surgery explanation flag from the information processing apparatus 1 by the communication unit 36 (step S45). The CPU 31 displays the surgery display screen 7 on the display unit 35 (step S46).

  The CPU 31 determines whether the input of each explanation button has been received (step S47). Specifically, the CPU 31 determines whether the input of the operation explanation button 72, the operation explanation button 74 on the previous day, the operation explanation button 75 on the day, or the operation explanation button 76 on the later day is received. If the CPU 31 determines that the input of each explanation button has not been received (step S47: NO), the CPU 31 stands by until the input is received. If the CPU 31 determines that the input of each explanation button is received (step S47: YES), the explanation message such as the surgery explanation message corresponding to each explanation button, the previous day operation explanation message, the day operation explanation message or the later day operation explanation message is displayed It displays on the part 35 (step S48).

  The CPU 31 sets the explanation flag corresponding to each explanation message to TRUE (step S49). Specifically, the CPU 11 sets the surgery explanation message, the surgery explanation message on the previous day, the surgery explanation message on the day, or the surgery explanation flag corresponding to the surgery day explanation message, the surgery explanation flag on the previous day, the surgery explanation flag on the day, or the later surgery explanation flag to TRUE. .

  It is determined whether all the explanation flags are TRUE (step S50). Specifically, the CPU 31 determines whether the surgery explanation flag, the previous day surgery explanation flag, the same day surgery explanation flag, and the later day surgery explanation flag are TRUE. If the CPU 31 determines that all the explanation flags are not TRUE (step S50: NO), the CPU 31 shifts the process to step S47.

  If the CPU 31 determines that all the explanation flags are TRUE (step S50: YES), the CPU 31 permits the input of the consent document button 73 (step S51). The CPU 31 determines whether the input of the consent document button 73 has been received (step S52). When the CPU 31 determines that the input of the consent document button 73 has not been received (step S52: NO), the CPU 31 stands by until the input of the consent document button 73 is received.

  If the CPU 31 determines that the input of the consent document button 73 has been received (step S52: YES), the communication unit 36 outputs an output request for the consent screen 8 to the information processing apparatus 1 (step S53). The CPU 11 acquires an output request for the consent screen 8 from the terminal device 3 by the communication unit 16 (step S54). The CPU 11 generates the consent screen 8 based on the medical information DB 221 (step S55). The CPU 11 outputs the consent screen 8 to the terminal device 3 by the communication unit 16 (step S56). The CPU 31 acquires the consent screen 8 from the information processing apparatus 1 by the communication unit 36 (step S57). The CPU 31 displays the consent screen 8 on the display unit 35 (step S58).

  The CPU 31 determines whether an input of a signature image of a name and an address has been received (step S59). If the CPU 31 determines that the input of the signature image has not been received (step S59: NO), the CPU 31 waits until the input of the signature image is received. When the CPU 31 determines that the input of the signature image is received (step S59: YES), the CPU 31 permits the input of the consent button 81 and the non-consent button 82 (step S60).

  The CPU 31 determines whether the input of the agree button 81 has been received (step S61). If the CPU 31 determines that the input of the consent button 81 has not been received (step S61: NO), it determines whether the input of the non-agreement button 82 has been received (step S62). If the CPU 31 determines that the input of the non-consent button 82 has not been received (step S62: NO), the process proceeds to step S61.

  If the CPU 31 determines that the input of the non-consent button 82 has been received (step S62: YES), the consent flag is set to FALSE (step S63), the display processing of the surgery display screen 7 etc. is ended, and the process is returned to step S21. Move. When the CPU 31 determines that the input of the consent button 81 is received (step S61: YES), the consent flag is set to TRUE (step S64). The CPU 31 generates a consent message (step S65).

  The CPU 31 generates a consent document that documents the consent screen 8 (step S66). The CPU 31 outputs the consent message, the consent document, and the consent flag from the communication unit 36 to the information processing apparatus 1 (step S67). The CPU 11 acquires the consent message, the consent document, and the consent flag from the terminal device 3 by the communication unit 16 (step S68). The CPU 11 displays the consent message on the display unit 15 (step S69). The CPU 11 updates the consent flag of the surgery information DB 224 (step S70). The CPU 11 stores the consent document in the storage unit 12 (step S71), and ends the process. Further, after the process of step S67 is completed, the CPU 31 ends the process of displaying the surgery display screen 7 or the like, and shifts the process to step S21.

  In the present embodiment, the CPU 31 picks up the barcode by the imaging unit 37, but the barcode may be read by a barcode reader. Further, in the present embodiment, the input of the signature image is accepted to permit the input of the consent button 82 and the non-consent button 82, but the barcode is imaged again by the imaging unit 37 and authentication processing is performed using the imaged barcode. May allow the input of the agree button 82 and the disagree button 82. In addition, although consent screen 8 was generated about surgery information in this embodiment, examination information etc. may be sufficient and consent screen 8 should just relate to medical information.

  According to one aspect, security can be improved over the prior art.

  According to one aspect, the information processing device 1 acquires the consent flag. As a result, the nurse or doctor who operates the information processing apparatus 1 can determine whether or not the operation has been agreed.

  In the present embodiment, the information processing apparatus 1, the medical server 2 and the electronic medical record server 4 are separate but may be integrated.

  In addition, although the information of the electronic medical record 421 is transmitted / received via the medical server 2 using SS-MIX in this embodiment, it is not restricted to this. For example, the electronic medical record server 4 may be connected to the communication network N1, and the viewer may directly transmit / receive the information of the electronic medical record 421 to / from the information processing apparatus 1.

Embodiment 2
The second embodiment relates to an embodiment in which a nurse dedicated screen 9 for a nurse to confirm medical information of a patient is displayed on the display unit 35. The configurations and operations other than the configurations and operations particularly described below are the same as those of the first embodiment, and the description will be omitted for the sake of brevity. FIG. 17 is a block diagram showing hardware groups of the information processing device 1, the medical server 2, the terminal device 3 and the electronic medical record server 4. As shown in FIG. 17, the storage unit 22 further includes an ID type DB 225 and a vital DB 226. The storage unit 32 also stores a terminal ID for identifying the terminal device 3.

  FIG. 18 is a diagram showing an example of data stored in the ID type DB 225. As shown in FIG. The ID type DB 225 is a database for storing the ID type and the like. The ID type DB 225 includes an ID column and an ID type column. An ID is stored in the ID column. The ID type column stores the type of user identified by the ID. For example, a patient ID, a nurse ID or a doctor ID is stored in the ID type column. The patient ID indicates that it is an ID for identifying a patient. The nurse ID indicates that it is an ID for identifying a nurse. The doctor ID indicates that it is an ID for identifying a doctor. The ID type DB 225 is previously stored in the input unit 24 by a nurse or a doctor.

  FIG. 19 is a diagram showing an example of data stored in the vital DB 226. As shown in FIG. The vital DB 226 is a database for storing vitals and the like. Vital is information representing the condition of a patient, and is, for example, body temperature, respiratory rate, systolic blood pressure, diastolic blood pressure, pulse rate, or oxygen concentration in artery. That is, vital is basic information on the life of the patient. The vital DB 226 includes a patient ID column, a medical date column, a medical time column, a body temperature column, a respiratory rate column, a systolic blood pressure column, a diastolic blood pressure column, a pulse rate column, and an oxygen concentration column. The patient ID is stored in the patient ID column. The medical date is stored in the medical date column. Medical time (acquisition time) indicating time when vital was acquired is stored in the medical time column. The body temperature column stores the body temperature associated with the patient ID, medical date, and medical time. The respiratory rate column stores the patient ID, the medical date, and the respiratory rate associated with the medical time. The systolic blood pressure associated with the patient ID, medical date and medical time is stored in the systolic blood pressure column. In the diastolic blood pressure column, diastolic blood pressure associated with patient ID, medical date and medical time is stored. The pulse rate column stores the patient ID, the medical date, and the pulse rate associated with the medical time. The oxygen concentration column stores oxygen concentration associated with patient ID, medical date, and medical time. The storage method of the vital DB 226 will be described later. Note that each column of the vital DB 226 is associated.

  An information processing system in the present embodiment will be described. After the CPU 31 displays the patient screen 5 on the display unit 35, the nurse captures an image of the bar code written in the wristband of the patient using the imaging unit 37. The CPU 31 acquires the barcode captured by the imaging unit 37. The CPU 31 converts the barcode into a nurse ID "N0001". The CPU 31 outputs the nurse ID “N0001” from the communication unit 36 to the medical server 2.

  The CPU 21 acquires the nurse ID “N0001” from the terminal device 3 by the communication unit 26. The CPU 21 acquires the acquired nurse ID “N0001” and the medical information DB 221, the schedule information DB 222, the examination information DB 223, the operation information DB 224, the ID information DB 225, and the vital DB 226 stored in the storage unit 22 from the communication unit 26 to the information processing apparatus 1. Output. The CPU 11 acquires the nurse ID “N0001”, the medical information DB 221, the schedule information DB 222, the examination information DB 223, the surgery information DB 224, the ID type DB 225 and the vital DB 226 from the medical server 2 by the communication unit 16. The CPU 11 temporarily stores the nurse ID in the RAM 13. Further, the CPU 11 may store the nurse ID in the storage unit 12 in advance.

  The CPU 11 refers to the ID type DB 225 and determines whether or not the nurse ID "N0001" is stored. The CPU 11 determines that the nurse ID "N0001" is stored in the ID type DB 225. The CPU 11 refers to the ID type DB 225, and determines whether the ID type of the nurse ID "N0001" is "nurse ID". The CPU 11 determines that the ID type of the ID "N0001" is "nurse ID".

  The CPU 11 generates a nurse dedicated screen 9. The CPU 11 outputs the nurse dedicated screen 9 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the nurse dedicated screen 9 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the nurse dedicated screen 9 on the display unit 35.

  FIG. 20 is an explanatory view for explaining the nurse dedicated screen 9. The nurse dedicated screen 9 has a nursing support record button 91 provided on the left, a vital button 92 provided on the upper right of the nursing support record button 91, and a switching button 93 provided on the right of the vital button 92. Equipped with

  The nursing support record button 91 is a button for displaying a nursing support record screen (change screen) 110 for displaying a change in vital of the patient. The nursing support record screen 110 is a screen generally used when the electronic medical record 421 is displayed. Since the nurse can work on the screen familiar by using the nursing support record screen 110, the work efficiency can be improved. The vital button 92 is a button for displaying a vital screen (input screen) 10 for inputting a patient's vitals. The switching button 93 comprises a rehabilitation, medication, examination, surgery and treatment button.

  Hereinafter, the operation of the nurse dedicated screen 9 will be described. The nurse touches the vital button 92 at the input unit 34. The CPU 31 receives an input of the vital button 92. The CPU 31 outputs an output request for the vital screen 10 from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires the output request of the vital screen 10 from the terminal device 3 by the communication unit 16. The CPU 11 generates a vital screen 10. The CPU 11 outputs the vital screen 10 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the vital screen 10 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the vital screen 10 on the display unit 35.

  A nurse touches the nursing support record button 91 at the input unit 34. The CPU 31 receives an input of the nursing support record button 91. The CPU 31 outputs an output request for the nursing support record screen 110 from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires an output request of the nursing support record screen 110 from the terminal device 3 by the communication unit 16. The CPU 11 generates a nursing support record screen 110 based on the vital DB 226. The CPU 11 outputs the nursing support record screen 110 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the nursing support record screen 110 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the nursing support record screen 110 on the display unit 35. The switching button 93 is the same operation as the switching button 65, and the description is omitted for the sake of brevity.

  FIG. 21 is an explanatory diagram for explaining the vital screen 10. The vital screen 10 has a medical date and time field 101 provided at the top, a temperature field 102 provided at the lower left portion of the medical date and time field 101, a respiratory rate field 103 provided at the right portion of the temperature field 102, and a temperature field 102 In the lower part of the blood pressure column, the diastolic blood pressure column 105 provided in the right part of the blood pressure column 104, the pulse column 106 provided in the lower part of the blood pressure column 104, and the right part of the pulse column 106 And a registration button 108 provided in the lower right portion.

  The medical date and time column 101 is a column for receiving the input of the medical date and the medical time when medical treatment is performed. The body temperature column 102 is a column for receiving an input of the body temperature. The respiratory rate column 103 is a field for receiving an input of the respiratory rate. The systolic blood pressure column 104 is a column for receiving an input of the systolic blood pressure. The diastolic blood pressure column 105 is a column for receiving an input of diastolic blood pressure. The pulse column 106 is a column for receiving an input of the pulse rate. An oxygen concentration column 107 is a column for receiving an input of oxygen concentration. The registration button 108 is a button for registering the input vital in the electronic medical record 421. In addition, each unit of temperature column 102, respiratory rate column 103, systolic pressure column 104, diastolic pressure column 105, pulse column 106, and oxygen concentration column 107 is the degree of Celsius, frequency, MmHg (millimeter of mercury), MmHg, 1 minute It is the number of times and the percentage.

  Hereinafter, the operation of the vital screen 10 will be described. The nurse looks at his own clock, touches the medical date / time column 101 with the input unit 34, and inputs the current medical date "August 20, 2015" and the medical time "9:00" with the input unit 34. input. The CPU 31 receives the input of the medical date “August 20, 2015” and the medical time “9:00”. The medical date and time may be automatically acquired from a clock unit (not shown) incorporated in the terminal device 3.

  The nurse measures the patient's temperature "37.0" with a medical instrument. The nurse touches the temperature column 102 at the input unit 34 and inputs the temperature "37.0" at the input unit 34. The CPU 31 receives an input of the body temperature "37.0". A nurse measures the patient's respiratory rate "60" with a medical instrument. The nurse touches the respiratory rate column 103 at the input unit 34, and inputs the respiratory rate "60" at the input unit 34. The CPU 31 receives an input of the respiration rate "60".

  A nurse measures the patient's systolic blood pressure "130" with a medical instrument. The nurse touches the systolic blood pressure column 104 at the input unit 34, and inputs the systolic blood pressure "130" at the input unit 34. The CPU 31 receives an input of the highest blood pressure "130". A nurse measures the patient's diastolic blood pressure "60". The nurse touches the diastolic blood pressure column 105 at the input unit 34 and inputs the diastolic blood pressure "60" at the input unit 34. The CPU 31 receives an input of the diastolic blood pressure "60".

  A nurse measures the patient's pulse rate "75" with a medical instrument. The nurse touches the pulse column 106 at the input unit 34, and inputs the pulse rate "75" at the input unit 34. The CPU 31 receives an input of the pulse rate "75". A nurse measures the patient's oxygen concentration "96" with a medical instrument. The nurse touches the oxygen concentration column 107 at the input unit 34, and inputs the oxygen concentration "96" at the input unit 34. The CPU 31 receives an input of the oxygen concentration "96".

  When the nurse touches the registration button 108 at the input unit 34, the CPU 31 uses the medical date "August 20, 2015", medical time "9:00", body temperature "37.0", respiratory rate "60". , Vital signs such as the highest blood pressure "130", the lowest blood pressure "60", the pulse rate "75", and the oxygen concentration "96" from the communication unit 36 to the medical server 2. CPU 21 has medical date "August 20, 2015", medical time "9:00", body temperature "37.0", respiratory rate "60", systolic blood pressure "130", diastolic blood pressure "60", pulse The communication unit 26 acquires vitals such as the number “75” and the oxygen concentration “96” from the terminal device 3. The CPU 21 stores each vital in the vital DB 226. The CPU 21 outputs a vital from the communication unit 26 to the electronic medical record server 4. The CPU 41 acquires vitals from the medical server 2 by the communication unit 46. The CPU 41 stores the vitals in the electronic medical chart 421. The CPU 41 generates a nursing support record screen 110 based on the vital stored in the electronic medical record 421.

  FIG. 22 is an explanatory view for explaining the nursing support record screen 110. As shown in FIG. The nursing support record screen 110 includes a vital graph 120 provided at the upper part, a body temperature column 130 provided at the lower part of the vital graph 120, a pulse rate column 140 provided at the lower part of the body temperature column 130, and a pulse rate column 140. The blood pressure column 150 provided at the bottom, the blood pressure column 160 provided at the bottom of the blood pressure column 150, the patient ID column 170 provided at the right, and the medical treatment provided at the top of the patient ID column 170 A date field 180 is provided. The body temperature column 130 is a column for displaying the body temperature. The pulse rate column 140 is a column for displaying the pulse rate. The blood pressure column 150 is a column for displaying the blood pressure. The diastolic blood pressure column 160 is a column for displaying the diastolic blood pressure column. The patient ID column 170 is a column for displaying the patient's ID. The medical date column 180 is a column for switching the medical date. The vital graph 120 is a graph showing vital changes of the patient. The solid line of vital graph 120 is a graph of body temperature. The broken line of the vital graph 120 is a graph of the pulse rate. The dashed-dotted line of the vital graph 120 is a graph of the systolic blood pressure. The dashed-two dotted line of vital graph 120 is a graph of diastolic pressure. The nursing support record screen 110 is a general screen for displaying vitals on the electronic medical record. By displaying the nursing support record screen 110, the nurse can confirm the patient's vitals in the same manner as the electronic medical record.

  The operation of the nursing support record screen 110 is as follows. When the nurse touches the patient ID "001" of the patient ID column 170 at the input unit 34, the CPU 31 selects the vital graph 120, the temperature column 130, the pulse rate column 140, the maximum blood pressure column 150, the diastolic blood pressure column 160, and the patient ID column. The screen 170 is switched to the nursing support record screen 110 corresponding to the patient ID "001". When the nurse switches the medical date in medical date column 180 to "August 20, 2015" by input unit 34, CPU 31 selects nursing support record screen 110 corresponding to "August 20, 2015". Switch to The CPU 41 today generates a nursing support record screen 110 based on the vital stored in the electronic medical record 421. Also, when the nurse switches to the medical date “August 18, 2015”, the CPU 31 switches to the nursing support record screen 110 corresponding to “August 18, 2015”. The CPU 41 generates a nursing support record screen 110 based on the vital stored in the electronic medical record 421 in the past. As described above, when the CPU 31 switches the display of the medical date column 180, the CPU 41 can generate the vital nursing support record screen 110 recorded at present and in the past. Further, the CPU 41 may generate the nursing support recording screen 110 based on the vitals recorded in the electronic medical record 421 in advance as well as the vitals input on the vitals screen 10.

  The method of generating the nursing support record screen 110 corresponding to the patient ID "001" is as follows. The CPU 41 acquires the vital DB 226 from the medical server 2 by the communication unit 46. The CPU 41 updates the electronic medical chart 421 based on the acquired vital DB 226. The CPU 41 refers to the vital stored in the electronic medical record 421, and the temperature, pulse rate, systolic blood pressure, diastolic blood pressure and patient in the temperature column 130, pulse rate column 140, maximum blood pressure column 150, diastolic pressure column 160 and patient ID column 170 Generate an ID. The CPU 11 generates time series graphs of body temperature, pulse rate, systolic blood pressure and diastolic blood pressure on the vital graph 120.

  A method of generating a graph of body temperature will be described below as a specific example. The CPU 41 refers to the vital in the electronic medical chart 421. The vital data structure in the electronic medical record 421 is similar to that of the vital DB 226, and for the sake of brevity, reference is made to FIG. As shown in FIG. 19, the CPU 41 has the temperature “37.0” corresponding to the medical time “9:00” of the patient ID “001” and the body temperature “37.0” corresponding to the medical time “10:00”. Body temperature "37.0" corresponding to time "11:00", body temperature "36.7" corresponding to medical time "12:00", body temperature "36.5" corresponding to medical time "13:00" Plotting on a vital graph 120 and connecting with a line generates a graph. The same applies to pulse rate, systolic blood pressure and diastolic blood pressure, and the description is omitted for the sake of brevity.

  The CPU 31 acquires the nursing support record screen 110 via the medical server 2 and the information processing apparatus 1 and displays the screen on the display unit 35.

  23 to 26 are flowcharts showing the processing procedure of the information processing system in the present embodiment. The processes of steps S11 to S70 are the same as those of the information processing system according to the first embodiment described above, and thus the description thereof will be omitted for the sake of simplicity. After the CPU 31 ends the process of step S21, the nurse captures an image of the bar code written on the authentication card of the nurse using the imaging unit 37. The CPU 31 acquires the barcode imaged by the imaging unit 37 (step S80). The CPU 31 converts the barcode into an ID (step S81). The CPU 31 outputs the ID from the communication unit 36 to the medical server 2 (step S82). The CPU 21 acquires the ID from the terminal device 3 by the communication unit 26 (step S83).

  The CPU 21 outputs the acquired nurse ID and the medical information DB 221, the schedule information DB 222, the examination information DB 223, the operation information DB 224, the ID type DB 225, and the vital DB 226 stored in the storage unit 22 from the communication unit 26 to the information processing device 1 Step S84). The CPU 11 acquires the nurse ID, the medical information DB 221, the schedule information DB 222, the examination information DB 223, the surgery information DB 224, the ID type DB 225, and the vital DB 226 by the communication unit 16 (step S85).

  The CPU 11 determines whether the ID is stored in the ID type DB 225 (step S86). If the CPU 11 determines that the ID is not stored in the ID type DB 225 (step S86: NO), the process ends. If the CPU 11 determines that the ID is stored in the ID type DB 225 (step S86: YES), it determines whether the ID type is a nurse ID (step S87).

  If the CPU 11 determines that the type of the ID is not a nurse ID (step S87: NO), the process proceeds to step S17. When the CPU 21 determines that the type of the ID is a nurse ID (step S87: YES), the CPU 21 generates a nurse dedicated screen 9 (step S88). The CPU 11 outputs the nurse dedicated screen 9 from the communication unit 16 to the terminal device 3 (step S89). The CPU 31 acquires the nurse dedicated screen 9 from the information processing apparatus 1 by the communication unit 36 (step S90). The CPU 31 displays the nurse dedicated screen 9 on the display unit 35 (step S91).

  The CPU 31 determines whether the input of the vital button 92 has been received (step S92). If the CPU 31 determines that the input of the vital button 92 has not been received (step S 92: NO), the process proceeds to step S 108. When determining that the input of the vital button 92 has been received (step S 92: YES), the CPU 31 outputs an output request for the vital screen 10 from the communication unit 36 to the information processing apparatus 1 (step S 93).

  The CPU 11 acquires the output request of the vital screen 10 from the terminal device 3 by the communication unit 16 (step S94). The CPU 11 generates a vital screen 10 (step S95). The CPU 11 outputs the vital screen 10 from the communication unit 16 to the terminal device 3 (step S96). The CPU 31 acquires the vital screen 10 from the information processing apparatus 1 by the communication unit 36 (step S97). The CPU 31 displays the vital screen 10 on the display unit 35 (step S98).

  The CPU 31 receives a vital input (step S99). The CPU 31 outputs the vital that has received the input from the communication unit 36 to the medical server 2 (step S100). The CPU 21 acquires vitals from the terminal device 3 by the communication unit 26 (step S101). The CPU 21 updates the vital DB 226 (step S102).

  The CPU 21 outputs the vital DB 226 from the communication unit 26 to the electronic medical record server 4 (step S103). The CPU 41 acquires the vital DB 226 from the medical server 2 by the communication unit 46 (step S104). The CPU 41 updates the electronic medical chart 421 based on the acquired vital DB 226 (step S105). The CPU 41 generates a nursing support record screen 110 based on the electronic medical chart 421 (step S106). The CPU 41 stores the nursing support record screen 110 in the electronic medical chart 421 (step S107), and ends the process.

  After finishing the process of step S100, the CPU 31 determines whether or not the input of the nursing support record button 91 has been received (step S108). If the CPU 31 determines that the input of the nursing support record button 91 has not been received (step S108: NO), the process proceeds to step S92. When determining that the input of the nursing support record button 91 has been received (step S108: YES), the CPU 31 outputs an output request for the nursing support record screen 110 from the communication unit 36 to the information processing apparatus 1 (step S109). The CPU 11 acquires an output request of the nursing support record screen 110 from the terminal device 3 by the communication unit 16 (step S110).

  The CPU 11 outputs an output request for the nursing support record screen 110 from the communication unit 16 to the electronic medical record server 4 via the medical server 2 (step S111). The CPU 41 acquires an output request of the nursing support record screen 110 from the information processing apparatus 1 via the medical server 2 by the communication unit 46 (step S112). The CPU 41 refers to the electronic medical chart 421 (step S113).

  The CPU 41 acquires the nursing support record screen 110 in the electronic medical chart 421 (step S114). The CPU 41 outputs the nursing support record screen 110 from the communication unit 16 to the terminal device 3 (step S115). The CPU 31 acquires the nursing support record screen 110 from the information processing apparatus 1 by the communication unit 36 (step S116).

  The CPU 11 outputs the nursing support record screen 110 from the communication unit 16 to the terminal device 3 (step S117). The CPU 31 acquires the nursing support record screen 110 from the information processing apparatus 1 by the communication unit 36 (step S118). The CPU 31 displays the nursing support record screen 110 on the display unit 35 (step S119). The CPU 31 performs end processing of display processing of the nurse dedicated screen 9 and the like by the input unit 34 (step S120), and shifts the processing to step S23.

  According to one aspect, the CPU 31 can receive vital input on the vital screen 10. By this, a nurse or a doctor can easily input vitals at the terminal device 3.

  According to one aspect, the CPU 31 displays the nursing support record screen 110. For this reason, since the nurse can work on a familiar screen, work efficiency can be improved.

  In the present embodiment, the nurse dedicated screen 9, vital screen 10 and nursing support record screen 110 are displayed when it is determined to be a nurse ID, but the nurse dedicated screen 9 is determined when it is determined to be a doctor ID. , Vital screen 10 and nursing support record screen 110 may be displayed.

Third Embodiment
The third embodiment relates to an embodiment in which a clinical path for describing the progress of treatment in chronological order is displayed on the display unit 35. The configurations and operations other than the configurations and operations particularly described below are the same as those of the first embodiment, and the description will be omitted for the sake of brevity. FIG. 27 is a block diagram showing hardware groups of the information processing device 1, the medical server 2, the terminal device 3 and the electronic medical record server 4. As shown in FIG. 27, the storage unit 12 stores a pictogram DB 121 indicating the correspondence between medical information and pictograms.

  FIG. 28 is a view showing an example of data stored in the pictogram DB 121. As shown in FIG. The pictogram DB 121 is a database that stores pictograms and the like. The pictogram DB 121 includes a medical information sequence and a pictogram sequence. Medical information is stored in the medical information row. Pictograms are stored in the pictogram sequence. Each column of pictogram DB 121 is registered in advance at the time of product delivery. Each column of the pictogram DB 121 is associated in advance.

  FIG. 29 is an explanatory view showing a clinical path screen 20 displaying a clinical path. The clinical path screen 20 includes a hospitalization date column, a pre-operation day column, an operation day column, an operation day column and a discharge date column, and an operation row, an examination row and a treatment row. The clinical path screen 20 is provided with an operation mark 201 on the day of operation row of the operation row. The clinical path screen 20 is provided with a CT examination mark 202 in the post-operative day row of the examination row. The clinical path screen 20 includes a treatment mark 203 in the pre-operative day row of the treatment row.

  Hospitalization date column, pre-operation day column, operation day column, post-operation day column and discharge date column respectively correspond to August 17th, August 18th, August 19th, August 20th and 21st There is. An operation mark 201 indicates an operation. The CT examination mark 202 indicates a CT examination. The treatment mark 203 indicates a treatment.

  Hereinafter, a method of generating the clinical path screen 20 will be described. The CPU 11 refers to the pictogram DB 121, the medical information DB 221, and the schedule information DB 222. As shown in FIG. 4, the CPU 11 identifies the pictogram A corresponding to the hemostatic treatment as shown in FIG. 27, since the medical information in the medical date column on August 18, 2015 is the hemostatic treatment. As shown in FIG. 3, since the hemostatic treatment is treatment information, the CPU 11 generates the identified pictogram A at the treatment mark 203 of the treatment row of the August 18th column. As shown in FIG. 4, the CPU 11 identifies the pictogram B corresponding to the laparotomy as shown in FIG. 28 because the medical information on the medical date column of August 19, 2015 is laparotomy. As shown in FIG. 3, since the open surgery is surgery information, the CPU 11 generates the identified pictogram B as the surgery mark 201 of the row of surgery on August 19. As shown in FIG. 4, the CPU 11 specifies the pictogram C corresponding to the CT examination as shown in FIG. 28 since the medical information on the medical date column of August 20, 2015 includes the CT examination. . As shown in FIG. 3, since the CT examination is examination information, the CPU 11 generates the identified pictogram C as the CT examination mark 202 of the examination row of August 20th column.

  The operation of the clinical path screen 20 will be described below. For example, when the patient touches the pictogram C of the CT examination mark 202 with the input unit 34, the touched pictogram C is output from the communication unit 36 to the information processing apparatus 1.

  The CPU 11 acquires the pictogram C from the terminal device 3 by the communication unit 16. The CPU 11 refers to the pictogram DB 121. The CPU 11 specifies a CT examination corresponding to the pictogram C based on the pictogram DB 121.

  The CPU 11 determines based on the medical information DB 221 whether the specified medical information is surgery information. Since the identified medical information is a CT examination, the CPU 11 determines that the identified medical information is not surgery information. The CPU 11 generates an examination display screen 6 corresponding to the specified CT examination. The CPU 11 outputs the generated examination display screen 6 to the terminal device 3 by the communication unit 16. The CPU 31 acquires the examination display screen 6 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the examination display screen 6 on the display unit 35. The following is the same as the first embodiment, and the description is omitted for the sake of brevity.

  For example, when the patient touches the pictogram B of the operation mark 201 with the input unit 34, the touched pictogram B is output from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires the pictogram B from the terminal device 3 by the communication unit 16. The CPU 11 refers to the pictogram DB 121. The CPU 11 specifies an open operation corresponding to the pictogram B based on the pictogram DB 121.

  Since the identified open surgery is surgery information, the CPU 11 determines that the identified medical information is surgery information. The CPU 11 generates a consent screen 8 for open surgery identified based on the medical information DB 221. The CPU 11 outputs the generated consent screen 8 to the terminal device 3 by the communication unit 16. The CPU 31 acquires the consent screen 8 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the consent screen 8 on the display unit 35. Although the CPU 11 in the present embodiment generates the consent screen 8, the operation display screen 7 may be generated. The following is the same as the first embodiment, and the description is omitted for the sake of brevity.

  30 to 32 are flowcharts showing the processing procedure of the information processing system in this embodiment. The CPU 31 determines whether or not the input unit 34 receives an input of a predetermined operation for outputting the clinical path screen 20 (step S121). When the CPU 31 determines that the input of the predetermined operation has not been received by the input unit 34 (step S121: NO), the CPU 31 stands by until the predetermined operation is performed. When the CPU 31 determines that the input of the predetermined operation has been received by the input unit 34 (step S121: YES), the communication unit 36 outputs a request for outputting the clinical path screen 20 to the information processing apparatus 1 (step S122). The CPU 11 acquires an output request for the clinical path screen 20 from the terminal device 3 by the communication unit 16 (step S123). The CPU 11 refers to the pictogram DB 121, the medical information DB 221, and the schedule information DB 222 (step S124).

  The CPU 11 specifies a pictogram based on the pictogram DB 121 and the schedule information DB 222 (step S125). The CPU 11 generates the clinical path screen 20 by generating the medical date and the type of medical information corresponding to the pictogram specified based on the medical information DB 221 (step S126). The CPU 11 outputs the clinical path screen 20 from the communication unit 16 to the terminal device 3 (step S127). The CPU 31 acquires the clinical path screen 20 from the information processing apparatus 1 by the communication unit 36 (step S128). The CPU 31 displays the clinical path screen 20 on the display unit 35 (step S129).

  The CPU 31 determines whether the pictogram has been touched by the input unit 34 (step S130). When the CPU 31 determines that the pictogram has not been touched by the input unit 34 (step S130: NO), the CPU 31 stands by until the pictogram is touched. When it is determined that the pictogram is touched by the input unit 34 (step S130: YES), the CPU 31 outputs the touched pictogram from the communication unit 36 to the information processing apparatus 1 (step S131).

  The CPU 11 acquires a pictogram from the terminal device 3 by the communication unit 16 (step S132). The CPU 11 refers to the pictogram DB 121 (step S133). The CPU 11 specifies medical information corresponding to the pictogram based on the pictogram DB 121 (step S134).

  The CPU 11 determines whether the medical information specified based on the medical information DB 221 is surgery information (step S135). When it is determined that the specified medical information is surgery information (step S135: YES), the CPU 11 generates the consent screen 8 based on the medical information DB 221 (step S136). The CPU 11 outputs the generated consent screen 8 to the terminal device 3 through the communication unit 16 (step S137). The CPU 31 acquires the consent screen 8 by the communication unit 36 and the information processing apparatus 1 (step S138). The CPU 31 displays the consent screen 8 on the display unit 35 (step S139), and shifts the process to step S59.

  If the CPU 11 determines that the identified medical information is not surgical information (step S135: NO), the CPU 11 generates a medical screen corresponding to the identified medical information (step S140). The CPU 11 outputs the generated medical screen to the terminal device 3 by the communication unit 16 (step S141). The CPU 31 acquires a medical screen from the information processing apparatus 1 by the communication unit 36 (step S142). The CPU 31 displays a medical screen on the display unit 35 (step S143). Thereafter, the process corresponding to each medical screen of the first embodiment is performed (step S144), and the process ends.

  According to one aspect, the CPU 31 can easily understand the patient's schedule by displaying the pictograms on the display unit 35 in chronological order on the clinical path screen 20.

Fourth Embodiment
The fourth embodiment relates to an embodiment in which a doctor-dedicated screen 30 for a doctor to confirm medical information of a patient is displayed on the display unit 35. The configurations and operations other than the configurations and operations particularly described below are the same as those of the second embodiment, and the description will be omitted for the sake of brevity. FIG. 33 is a block diagram showing hardware groups of the information processing device 1, the medical server 2, the terminal device 3 and the electronic medical record server 4. The storage unit 22 further stores an image data DB 227.

  FIG. 34 is a view showing an example of data stored in the image data DB 227. As shown in FIG. The image data DB 227 is a database for storing image data such as an X-ray image, an endoscope image, a CT image, a BRI image, or an ultrasound image. The image data DB 227 includes a patient ID column, a medical date column, an image data column, and the like. The patient ID is stored in the patient ID column. The medical date is stored in the medical date column. The image data string stores image data associated with the patient ID and the medical date.

  The storage method of the image data DB 227 is as follows. The CPU 21 acquires medical date and image data from the electronic medical chart 421 by the communication unit 16. The CPU 21 stores the acquired medical date and image data in the image data DB 227 in association with the patient ID.

  An information processing system in the present embodiment will be described. After the CPU 31 displays the patient screen 5 on the display unit 35, the doctor touches his / her IC card on the card reader. The CPU 31 acquires the doctor ID "D0002" from the IC card by the card reader. The CPU 31 outputs the doctor ID “D0002” from the communication unit 36 to the medical server 2.

  The CPU 21 acquires the doctor ID “D0002” from the terminal device 3 by the communication unit 26. The CPU 21 outputs the acquired doctor ID “D0002” and the medical information DB 221, the schedule information DB 222, the examination information DB 223, the operation information DB 224, the ID information DB 225, and the vital DB 226 stored in the storage unit 22 from the communication unit 26 to the information processing apparatus 1. Do. The CPU 11 acquires the doctor ID “D0002”, the medical information DB 221, the schedule information DB 222, the examination information DB 223, the surgery information DB 224, the ID type DB 225 and the vital DB 226 from the medical server 2 by the communication unit 16. The CPU 11 temporarily stores the doctor ID in the RAM 13. Further, the CPU 11 may store the doctor ID in the storage unit 12.

  The CPU 11 refers to the ID type DB 225 and determines whether or not the doctor ID “D0002” is stored. As shown in FIG. 18, the CPU 11 determines that the doctor ID “D0002” is stored in the ID type DB 225. The CPU 11 refers to the ID type DB 225 and determines whether the ID type of the doctor ID “D0002” is “doctor ID”. The CPU 11 determines that the ID type of the doctor ID “D0002” is “doctor ID”.

  The CPU 11 generates a doctor dedicated screen 30. The CPU 11 outputs the doctor dedicated screen 30 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the doctor dedicated screen 30 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the doctor dedicated screen 30 on the display unit 35.

  FIG. 35 is an explanatory view for explaining the doctor dedicated screen 30. As shown in FIG. The doctor dedicated screen 30 includes an image data button 301 provided on the left side and a switching button 302 provided on the right side of the image data button 301. An image data button 301 is a button for displaying an image selection screen 40 for selecting an image. The switching button 302 has the same configuration and operation as the switching button 93, and will not be described for the sake of brevity.

  Hereinafter, the operation of the doctor dedicated screen 30 will be described. The doctor touches the image data button 301 at the input unit 34. The CPU 31 receives an input of the image data button 301. The CPU 31 outputs an output request for the image selection screen 40 from the communication unit 36 to the information processing apparatus 1. The CPU 31 acquires an output request for the image selection screen 40 from the terminal device 3 by the communication unit 16. The CPU 11 generates an image selection screen 40 based on the image data DB 227.

  The CPU 11 outputs the image selection screen 40 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the image selection screen 40 from the information processing apparatus 1 by the communication unit 36. The CPU 31 displays the image selection screen 40 on the display unit 35.

  FIG. 36 is an explanatory diagram for explaining the image selection screen 40. As shown in FIG. The image selection screen 40 includes medical date fields 41A, 41B, 41C, 41D and 41E (hereinafter referred to as medical date field 401 as a representative, if necessary) provided in order from the top to the left, and the right And image selection buttons 42A, 42B, 42C, 42D and 42E (hereinafter, referred to as image selection button 402 as a representative). The medical date column 401 is a column for displaying the medical date. An image selection button 402 is a button for selecting an image to be displayed on the display unit 35.

  Hereinafter, a method of generating the image selection screen 40 will be described. The CPU 11 refers to the image data DB 227. The CPU 11 acquires the patient ID "001" before acquiring the doctor ID "D0002". Therefore, the CPU 11 uses the medical date "September 3, 2015", "August 20, 2015", "August 15, 2015", "August 10, 2015" corresponding to the patient "001". And “August 8, 2015” are generated in the medical date fields 41A, 41B, 41C, 41D and 41E, respectively. The CPU 11 associates the image selection buttons 42A, 42B, 42C, 42D and 42E with the X-ray image A, the endoscopic image A, the CT image A, the ultrasonic image A and the ultrasonic image B, respectively.

  Hereinafter, the operation of the image selection screen 40 will be described. When the doctor selects the image selection button 42A at the input unit 34, the CPU 31 receives the selection of the image selection button 42A. The CPU 31 displays an X-ray image A corresponding to the patient "001" and the medical date "September 3, 2015" on the display unit 35. When the doctor selects the image selection button 42B at the input unit 34, the CPU 31 receives the selection of the image selection button 42B. The CPU 31 displays the endoscopic image A corresponding to the patient "001" and the medical date "August 20, 2015" on the display unit 35. The same applies to the image selection buttons 42C, 42D and 42E, and the description will be omitted for the sake of brevity.

  37 to 38 are flowcharts showing the processing procedure of the information processing system according to this embodiment. The processing from step S11 to step S21 is the same as that of the second embodiment, and the description is omitted for the sake of brevity. After completing step S21, the CPU 31 acquires an ID from the IC card with a card reader (step S150), and shifts the process to step S82. When the step S87 is NO, the CPU 11 determines whether the acquired ID is a doctor ID (step S151). If the CPU 11 determines that the acquired ID is not a doctor ID (step S151: NO), the process proceeds to step S17. When it is determined that the acquired ID is a doctor ID (step S151: YES), the CPU 11 generates a doctor dedicated screen 30 (step S152). The CPU 11 outputs the doctor dedicated screen 30 from the communication unit 16 to the terminal device 3 (step S153). The CPU 31 acquires the doctor dedicated screen 30 from the information processing apparatus 1 by the communication unit 36 (step S154). The CPU 31 displays the doctor dedicated screen 30 on the display unit 35 (step S155).

  The CPU 31 receives an input of the image data button 301 (step S156). The CPU 31 outputs an output request for the image selection screen 40 from the communication unit 36 to the information processing apparatus 1 (step S157). The CPU 31 acquires an output request for the image selection screen 40 from the terminal device 3 by the communication unit 16 (step S158). The CPU 11 generates the image selection screen 40 based on the image data DB 227 (step S159).

  The CPU 11 outputs the image selection screen 40 from the communication unit 16 to the terminal device 3 (step S160). The CPU 31 acquires the image selection screen 40 from the information processing apparatus 1 by the communication unit 36 (step S161). The CPU 31 displays the image selection screen 40 on the display unit 35 (step S162).

  The CPU 31 receives the selection of the image selection button 402 (step S163). The CPU 31 displays an image corresponding to the image selection button 402 on the display unit 35 (step S164). The CPU 31 performs an end process of the image selection screen 40 by the input unit 34 (step S165), and ends the process.

  According to one aspect, by displaying the image selected on the image selection screen 40 on the display unit 35, the CPU 31 can easily refer to the image data related to the patient.

  In the present embodiment, the doctor dedicated screen 30 and the image selection screen 40 are displayed when it is determined to be a doctor ID, but the doctor dedicated screen 30 and the image selection screen 40 are displayed when it is determined to be a nurse ID. You may Further, the type of ID is not limited to the patient, doctor or nurse ID, and can also be used as an ID for identifying a medical person such as a pharmacist ID or a radiographer ID.

  It should be understood that the embodiments disclosed herein are illustrative in all respects and not restrictive. The scope of the present invention is indicated not by the meaning described above but by the claims, and is intended to include all modifications within the meaning and scope equivalent to the claims. Moreover, it is possible to combine each embodiment suitably in the range which does not make process contents contradictory.

1 information processing apparatus 12 storage unit 13 RAM (storage unit)
12P program 3 terminal device 32P program 35 display 7 surgery display screen (explanatory screen)
72 surgery explanation button 73 consent written button (acquisition button)
74 The day before operation explanation button 75 The day of operation explanation button 76 The day after operation explanation button 8 Consent screen 10 Vital screen (input screen)
110 Nursing

Claims (6)

A patient identification information acquisition unit that acquires patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display section,
A medical worker identification information acquisition unit for acquiring medical worker identification information for identifying a medical worker after display by the first medical information display unit;
After transmitting the acquired medical worker identification information to the information processing apparatus, the medical worker performs medical information on the patient based on patient medical information acquired from the information processing apparatus using the patient identification information. A second medical information display unit for displaying a screen for a medical worker for confirming
Terminal equipment equipped with A patient identification information acquisition unit that acquires patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display section,
A medical worker identification information acquisition unit for acquiring medical worker identification information for identifying a medical worker after display by the first medical information display unit;
After transmitting the acquired medical worker identification information to the information processing apparatus, the input screen acquired from the information processing apparatus is displayed to receive the input of the state information on the state of the patient An input screen display unit,
Terminal equipment equipped with A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A medical worker identification information acquisition step of acquiring medical worker identification information for identifying a medical worker after display in the first medical information display step;
After transmitting the acquired medical worker identification information to the information processing apparatus, the medical worker performs medical information on the patient based on patient medical information acquired from the information processing apparatus using the patient identification information. A second medical information display step of displaying a screen for medical staff for confirming
Control method of the terminal device including A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A doctor identification information acquisition step for acquiring, for example, a doctor identification information for identifying a medical worker after display in the first medical information display step;
An input screen which is an input screen acquired from the information processing apparatus after transmitting the acquired identification information for the doctor etc. to the information processing apparatus, the input screen for receiving the input of the state information related to the state of the patient Screen display step,
Control method of the terminal device including A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A medical worker identification information acquisition step of acquiring medical worker identification information for identifying a medical worker after display in the first medical information display step;
After transmitting the acquired medical worker identification information to the information processing apparatus, the medical worker performs medical information on the patient based on patient medical information acquired from the information processing apparatus using the patient identification information. A second medical information display step of displaying a screen for medical staff for confirming
Control program of a terminal device including: A patient identification information acquisition step of acquiring patient identification information for identifying a patient;
First, after transmitting the acquired patient identification information to the information processing apparatus, a patient screen on which the patient can confirm is displayed based on patient medical information acquired from the information processing apparatus using the patient identification information Medical information display step,
A doctor identification information acquisition step for acquiring, for example, a doctor identification information for identifying a medical worker after display in the first medical information display step;
An input screen which is an input screen acquired from the information processing apparatus after transmitting the acquired identification information for the doctor etc. to the information processing apparatus, the input screen for receiving the input of the state information related to the state of the patient Screen display step,
Control program of a terminal device including: