JP2019153354A - Terminal device, information processing device and information processing method - Google Patents

Abstract

To improve security more than in the conventional practice by preventing the misidentification of patients.SOLUTION: A terminal device, an information processing device and an information processing program include: a first acquisition unit for acquiring first patient medical information derived by using patient identification information; a first medical information display unit for displaying the acquired first patient medical information; a second acquisition unit for acquiring medical staff identification information for identifying a medical staff with the first patient medical information displayed; a second medical information display unit for displaying a screen for a medical staff for allowing the medical staff to confirm medical information of a patient on the basis of second patient medical information acquired from an information processing device after transmitting the acquired medical staff identification information to the information processing device; and an information display unit for displaying at least one of an input screen for receiving an input of condition information on the patient's condition and a change information screen for showing a change in the patient's condition generated on the basis of a history of condition information from a state in which the screen for a medical staff is displayed by the second medical information display unit.SELECTED DRAWING: Figure 2

Description

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

  Conventionally, when a hospitalized patient wants to know medical information such as treatment, examination, or surgery performed on the patient, the medical information may be confirmed by a terminal device that displays a pictogram or the like. Since this type of terminal device can easily change the display contents by updating data, it has been used in recent years because it is more convenient than paper and 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.

Japanese Patent Laying-Open No. 2015-18461

  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 or the like that can improve security compared to the related art.

In order to achieve the above object, a terminal device according to the present invention provides:
A first acquisition unit for acquiring first patient medical information derived using the patient identification information;
A first medical information display unit for displaying the first patient medical information acquired by the first acquisition unit;
A second acquisition unit for acquiring medical worker identification information for identifying a medical worker in a state where the first patient medical information is displayed by the first medical information display unit;
Medical care for the medical worker to confirm the medical information of the patient based on the second patient medical information acquired from the information processing device after transmitting the acquired medical worker identification information to the information processing device A second medical information display unit for displaying a worker screen;
From the state where the second medical information display unit displays the screen for the medical staff, the screen is generated based on the input screen for receiving the input of the state information related to the state of the patient and the history of the state information An information display unit for displaying at least one of change information screens for indicating a change in the state of the patient;
Equipped with.

In order to achieve the above object, an information processing apparatus according to the present invention provides:
A first transmitter for transmitting first patient medical information derived using patient identification information to the terminal device;
A receiving unit that receives from the terminal device medical worker identification information for identifying a medical worker, acquired in a state in which the first patient medical information is displayed on the terminal device;
When the medical worker identification information is received, the second patient medical information derived using the patient identification information is transmitted to the terminal device, and the medical worker confirms the medical information of the patient. A second transmitter for displaying a screen for workers on the terminal device;
From the state in which the screen for the medical staff is displayed on the terminal device, the input screen for accepting input of state information regarding the state of the patient, and the state of the patient generated based on the history of the state information A display control unit that transmits and displays at least one of change information screens for indicating changes in the terminal device;
Equipped with.

In order to achieve the above object, an information processing method according to the present invention includes:
A transmission step of transmitting the first patient medical information derived using the patient identification information from the information processing apparatus to the terminal device;
A first medical information display step of displaying the first patient medical information on the terminal device;
In the state where the first patient medical information is displayed in the first medical information display step, the terminal device acquires medical worker identification information for identifying a medical worker;
After the acquired medical worker identification information is transmitted to the information processing device, the medical worker confirms the medical information of the patient based on second patient medical information acquired from the information processing device. A second medical information display step for displaying a screen for medical workers on the terminal device;
From the state in which the screen for medical personnel is displayed in the second medical information display step, the screen is generated based on an input screen for receiving input of state information related to the state of the patient, and a history of the state information An information display step for causing the terminal device to display at least one of change information screens for indicating a change in the state of the patient;
including.

  It is possible to prevent patient confusion and improve security compared to the conventional technology.

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 record 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 schedule 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 explanatory drawing explaining the screen for patients for displaying a patient's medical information. It is explanatory drawing explaining a test | inspection display screen. It is explanatory drawing explaining a surgery display screen. It is explanatory drawing explaining an agreement screen. It is the flowchart which showed the process sequence of the information processing system in this embodiment. It is the flowchart which showed the process sequence of the information processing system in this embodiment. It is the flowchart which showed the display process of the test | inspection display screen in this embodiment. It is the flowchart which showed display processes, such as a surgery display screen in this embodiment. It is the flowchart which showed display processes, such as a surgery display screen in this embodiment. It is the flowchart which showed display processes, such as a surgery display screen 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 record server. It is a figure which shows an example of the data stored in ID kind DB. It is a figure which shows an example of the data stored in vital DB. It is explanatory drawing explaining a nurse exclusive screen. It is explanatory drawing explaining a vital screen. It is explanatory drawing explaining a nursing assistance recording screen. It is the flowchart which showed the process sequence of the information processing system in this embodiment. It is the flowchart which showed the process sequence of the information processing system in this embodiment. It is the flowchart which showed the process sequence of the information processing system in this embodiment. It is the flowchart which showed the process sequence 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 record 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 process sequence of the information processing system in this embodiment. It is the flowchart which showed the process sequence of the information processing system in this embodiment. It is the flowchart which showed the process sequence 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 record server. It is a figure which shows an example of the data stored in image data DB. It is explanatory drawing explaining a doctor exclusive screen. It is explanatory drawing explaining an image selection screen. It is the flowchart which showed the process sequence of the information processing system in this embodiment. It is the flowchart which showed the process sequence 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 diagram 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 record server 4. The information processing device 1, the medical server 2, and the terminal device 3 are connected to each other via a communication network N1 such as the Internet, a LAN (Local Area Network), or a mobile phone network. The medical server 2 and the electronic medical record server 4 are connected to each other by a communication network N2 such as the Internet, a LAN, or a mobile phone network. The information processing device 1 transmits and receives information between the medical server 2 and the terminal device 3 via the communication network N1. The medical server 2 transmits and receives information to and from the electronic medical record server 4 via the communication network N2. 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 record 421 in this embodiment is transmitted and received using a system such as SS-MIX (Standardized Structured Medical Information eXchange).

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

  The medical server 2 is a device that stores an ID (identification information) for identifying a patient, a nurse, a doctor (user), etc., medical information related to medical treatment, and the like, and is a server computer, for example. The medical server 2 acquires medical information and the like from the electronic medical record server 4. The medical server 2 stores the acquired medical information 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 a personal computer, for example. 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 and medical information. The information processing apparatus 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, or a personal computer. The terminal device 3 in the present embodiment will be described as a tablet computer. The terminal device 3 performs an authentication process from a bar code written on a wristband wound around the patient's hand (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 action performed on the patient by checking the medical screen.

  Details of the information processing system will be described below. FIG. 2 is a block diagram illustrating a hardware group of the information processing apparatus 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 CPU (Central Processing Unit) 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 each part of hardware via a bus. The CPU 11 includes, for example, one or a plurality of CPUs or a multi-core CPU. The CPU 11 controls each part of the hardware according to 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, an SRAM (Static Random Access Memory). 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 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 a liquid crystal screen, for example. The communication unit 16 is, for example, a wireless LAN card or a mobile phone communication module, and transmits and receives various types of information between the medical server 2 and the terminal device 3 via the communication network N1. For example, the timer 17 measures the time and date at the current time point, and outputs the timing result to the CPU 11 in accordance with a request from 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. In the medical server 2, the configurations of the CPU 21, the RAM 23, the input unit 24, and the display unit 25 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. Omitted.

  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, an operation information DB 224, and a program 22P. The communication unit 26 is, for example, a wireless LAN card or a mobile phone communication module, and transmits and receives various types of information between the information processing device 1 and the terminal device 3 via the communication network N1. The communication unit 26 transmits / receives medical information to / from the electronic medical record server 4 via the communication network N2.

  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. In the terminal device 3, the configurations of the CPU 31, the RAM 33, and the display unit 35 are the same as the configurations of the CPU 11, the RAM 13, and the display unit 15 of the information processing apparatus 1.

  The storage unit 32 is, for example, a hard disk or a large capacity memory. The storage unit 32 stores various data necessary for the CPU 31 to perform processing, and a program 32P. The input unit 34 is an input device such as a touch panel, and outputs received operation information to the CPU 31. In addition, the input unit 34 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 mobile phone communication module, and transmits / receives various information to / from 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 acquires image data by photoelectrically converting an optical signal input via the CCD or the 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. In the electronic medical record server 4, the configuration of the CPU 41, RAM 43, input unit 44 and display unit 45 is the same as the configuration of the CPU 11, RAM 13, input unit 14 and display unit 15 of the information processing apparatus 1. Omitted.

  The storage unit 42 is, for example, a hard disk or a large capacity memory. The storage unit 42 stores various data necessary 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 practice, examination information, surgery information, and the like. The communication unit 46 is, for example, a wireless LAN card or a mobile phone communication module, and transmits / receives information in the electronic medical record 421 to / from the medical server 2 via the communication network N2.

  FIG. 3 is a diagram illustrating an example of data stored in the medical information DB 221. The medical information DB 221 is a database that stores medical information and the like. Medical information includes, for example, rehabilitation information, drug information, examination information, surgery information, treatment information, a caution message, a pictogram, nutritional guidance, and vitals, which will be described later. In addition, medical information is not limited to these and includes medical information. The medical information DB 221 includes a patient ID string, a rehabilitation information string, a medicine information string, an examination information string, a surgery information string, a treatment information string, a caution message string, a pictogram string, and the like. The patient ID column stores a patient ID for identifying a patient. In the rehabilitation information sequence, rehabilitation information indicating the rehabilitation content is stored in association with the patient ID. Medicine information indicating the contents of the medicine is stored in the medicine information column.

  In the examination information column, examination information indicating the contents of the examination is stored in association with the patient ID. For example, a CT (Computed Tomography) test, a blood test, an MRI (Magnetic Resonance Imaging) test, or the like is stored in the test information sequence. Surgery information indicating the contents of the surgery is stored in the surgery information column. For example, laparotomy, thoracotomy or craniotomy is stored in the operation information sequence. Treatment information indicating the content of the treatment is stored in the treatment information column. For example, hemostasis treatment, wound treatment, or burn treatment is stored in the treatment information string. The hemostatic treatment is a treatment that stops the blood with a bandage or the like. Wound treatment is a treatment for suturing a wound. The burn treatment is a treatment for cooling the burn. An attention message indicating attention to the patient is stored in the attention message column. A pictogram indicating a medical practice for a patient is stored in the pictogram column.

  The storage method of the medical information DB 221 is as follows. The CPU 21 receives an input of a patient ID at 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 record server 4. The CPU 41 acquires a request for medical information from the electronic medical record server 4 through the communication unit 46. The CPU 41 outputs the medical information stored in the electronic medical record 421 to the medical server 2 through the communication unit 46. The CPU 21 acquires medical information through the communication unit 26. The CPU 21 stores medical information in the medical information DB 221 in association with the patient ID. Each column of the medical information DB 221 is associated.

  FIG. 4 is a diagram illustrating an example of data stored in the schedule information DB 222. The schedule information DB 222 is a database that stores 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. A patient ID is stored in the patient ID column. In the medical date column, the medical date for performing the medical action is stored in association with the patient ID. In the medical time column, medical time for performing medical practice is stored in association with the patient ID. Medical information is stored in the medical information column 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 at 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 through the communication unit 46. The CPU 41 outputs the schedule information stored in the electronic medical record 421 to the medical server 2 through the communication unit 46. The CPU 21 acquires schedule information through the communication unit 26. The CPU 21 stores schedule information in the schedule information DB 222 in association with the patient ID. Each column of the schedule information DB 222 is associated.

  FIG. 5 is a diagram illustrating an example of data stored in the inspection information DB 223. The inspection information DB 223 is a database that stores inspection information and the like. The inspection information DB 223 includes an inspection information column, an inspection description column, a previous day inspection description column, and a current day inspection description column. Inspection information is stored in the inspection information column. The examination explanation is stored in the examination explanation column. The examination explanation is an examination explanation message indicating the explanation of the entire examination performed on the patient. The inspection explanation is, for example, the contents of the inspection, the purpose of the inspection, or an explanation of the danger. The previous day inspection description is stored in the previous day inspection description column. The previous day examination explanation is a previous day examination explanation message indicating an explanation of a medical practice performed on the patient the day before the examination. The previous day test description is, for example, the content of a meal to be taken the day before the test, the content of a given medicine or general attention. The day description column stores the day inspection description. The examination description on the day is an examination explanation message on the day showing the explanation of the medical practice performed on the patient on the day of the examination. The examination description on the day includes, for example, the contents of a meal to be taken on the day of the examination, the contents of a given medicine, clothes to be worn, or general attention. Note that the inspection description, the previous day inspection description, and the current day inspection description are not limited to messages, but may be images or sounds.

  The storage method of the inspection 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 inspection information and the like from the electronic medical record server 4 through the communication unit 46. The CPU 41 outputs the examination information and the like stored in the electronic medical record 421 to the medical server 2 through the communication unit 46. The CPU 21 acquires inspection information and the like through the communication unit 26. The CPU 21 stores inspection information and the like in the inspection information DB 223. Each column of the inspection information DB 223 is associated.

  FIG. 6 is a diagram illustrating an example of data stored in the surgery information DB 224. The surgery information DB 224 is a database that stores surgery information and the like. The operation information DB 224 includes an operation information column, an operation description column, an operation description flag column, a previous day operation description column, a previous day operation description flag column, a day operation description column, a day operation description flag column, a later operation description column, a later operation description flag column, and A consent flag string is provided. Surgery information is stored in the surgery information column.

  An operation description is stored in the operation description column. The operation explanation is an operation explanation message indicating an explanation of the entire operation performed on the patient. Surgery explanation messages include, for example, the name and method of the scheduled surgery, the expected complications, accidents or risks, the expected effects of the scheduled surgery, and the expected symptom transition if not Other possible therapies or treatments in case an emergency treatment becomes necessary during implementation. A surgery explanation flag indicating whether or not a surgery explanation message is displayed is stored in the surgery explanation flag column. The previous day operation description is stored in the previous day operation description column. The previous day operation description is a previous day operation description message indicating an explanation of a medical practice performed on the patient the day before the operation. The previous day's surgery explanation message is, for example, the content of a test performed on the day before the surgery, the content of a meal to be taken, the content of a given medicine, the content of a treatment to be performed, or general attention. The previous day surgery explanation flag column stores the previous day surgery explanation flag indicating whether or not the previous day surgery explanation message has been displayed.

  The surgery description on the day is stored in the surgery description column on the day. The operation description on the day is an operation description message on the previous day indicating an explanation of medical practice performed on the patient on the day of the operation. The explanation of the operation on the day includes, for example, the flow of the entire operation, points to be noted in the operation, the content of meals to be taken on the day of the operation, the content of the medicine given, general precautions, and the like. The day operation explanation flag column stores the day operation explanation flag indicating whether or not the day operation explanation message is displayed. The surgical description column is stored at a later date in the surgical description column. The operation description on the later day is an operation description message on the previous day indicating an explanation of the medical practice performed on the patient on the day after the operation. The explanation of the operation at a later date is, for example, rehabilitation performed on the day after the operation, the content of the examination to be performed, the content of the meal to be taken, the content of the medicine to be given, the content of the treatment to be performed or general attention. A later-day surgery explanation flag column indicating whether or not a later-day surgery explanation message has been displayed is stored in the later-day surgery explanation flag column. An agreement flag indicating whether or not the operation has been agreed is stored in the agreement flag column.

  When each of the surgery explanation flag, the previous day surgery explanation flag, the current day surgery explanation flag, and the later day surgery explanation flag is TRUE, it indicates that the surgery explanation, the previous day surgery explanation, the current day surgery explanation, and the later day surgery explanation are displayed. When each of the surgery explanation flag, the previous day surgery explanation flag, the current day surgery explanation flag, and the later day surgery explanation flag is FALSE, it indicates that the surgery explanation, the previous day surgery explanation, the current day surgery explanation, and the later day surgery explanation are not displayed. If the consent flag is TRUE, it indicates that the operation has been agreed. When the consent flag is FALSE, it indicates that the operation has not been agreed. Note that the consent information indicates that the consent flag is TRUE.

  The surgery explanation flag, the previous day surgery explanation flag, the current day surgery explanation flag, the later day surgery explanation flag, and the consent flag are set to FALSE in the initial state. The operation description, the previous day operation description, the current day operation description, and the later day operation description are not limited to messages, but may be images or sounds.

  The storage method of the surgery information DB 224 is as follows. The CPU 21 outputs a request such as operation information from the communication unit 26 to the electronic medical record server 4. The CPU 41 acquires a request for surgery information and the like from the electronic medical record server 4 through the communication unit 46. The CPU 41 outputs the surgical information and the like stored in the electronic medical record 421 to the medical server 2 through the communication unit 46. The CPU 21 acquires operation information and the like through the communication unit 26. The CPU 21 stores operation information and the like in the operation information DB 224. Also, FALSE is set in advance in the consent flag column. Each column of the surgery information DB 224 is associated.

  FIG. 7 is an explanatory diagram 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 at the right part, a switching button 54 provided at the lower part of the medical information display field 50, and an upper left part of the medical information display field 50. And a date / time field 55 provided. The medical information display column 50 includes a schedule column 51 provided on the left side, a caution column 52 provided on the right side, and a pictogram column 53 provided below the schedule column 51 and the caution column 52.

  The medical information display column 50 is a column for displaying the patient's medical information. The schedule column 51 is a column for displaying the schedule for today. 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 switch button 54 includes rehabilitation, medication, examination, surgery, and treatment buttons. The date field 55 is a field for displaying the current date. The rehabilitation button is a button for switching to a screen that displays information related to patient rehabilitation. The medicine button is a button for switching to a screen for displaying medicine 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 operation button is a button for switching to an operation display screen (explanation screen) 7 for displaying an explanation about an operation 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 this embodiment has a wristband in which a one-dimensional or two-dimensional barcode is written in his / her hand. The barcode includes a patient ID. The patient images the barcode with the imaging unit 37 of the terminal device 3. The CPU 31 acquires the barcode imaged by the imaging unit 37. The CPU 31 converts the barcode acquired using image processing into a patient ID “001”. That is, the wristband is an identification medium that includes identification information. The identification medium is a medium such as an instrument or device for identifying a patient, nurse or doctor who possesses the identification medium through identification information. In the present embodiment, the barcode is described in the wristband, but the present invention is not limited to this. The wristband may describe an image. The wristband may describe a list of numbers, letters or symbols, or a combination thereof.

  In this embodiment, the wristband is used as the identification medium, but a wireless tag for performing near field communication, an IC card equipped with an IC (Integrated Circuit) chip, or the like may be used as the identification medium. The method of using 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 a patient ID included in the wireless signal received by the communication unit 36. The usage method 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 through the communication unit 26. The CPU 21 outputs the acquired patient ID “001” and the medical information DB 221, schedule information DB 222, examination information DB 223, and 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 through the communication unit 16. The CPU 11 temporarily stores the patient ID in the RAM 13. 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 at the same time as the patient ID, but may acquire the medical information DB 221 or 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 for generating the patient screen 5 will be described. The CPU 11 acquires the current date “August 20, 2015” from the time measuring unit 17. The CPU 11 generates the current date “August 20, 2015” in the date column 55. The CPU 11 refers to the schedule information DB 222. The CPU 11 performs 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 “rehabilitation”. In addition, 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 through 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 with the input unit 34. The CPU 31 receives an input of an 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 for the examination display screen 6 from the terminal device 3 through the communication unit 16. The CPU 11 generates the inspection display screen 6 based on the inspection information DB 223. The CPU 11 outputs the inspection 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 through the communication unit 36. The CPU 31 displays the examination display screen 6 on the display unit 35.

  Further, the patient touches the operation button of the switching button 54 with the input unit 34. The CPU 31 receives an operation button input. 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 for the surgery display screen 7 from the terminal device 3 through the communication unit 16. The CPU 11 generates a 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 previous day surgery explanation flag, the current day surgery explanation flag, and the later day surgery explanation flag 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 current day surgery explanation flag, and the later day surgery explanation flag from the information processing apparatus 1 through the communication unit 36. The CPU 31 displays the surgery display screen 7 on the display unit 35.

  FIG. 8 is an explanatory diagram for explaining the examination display screen 6. As shown in FIG. 8, the examination display screen 6 includes an examination name field 61 provided at the upper part, an examination explanation button 62 provided at the lower part of the examination name field 61, and the previous day provided at the lower part of the examination explanation button 62. The examination explanation button 63, the 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 for generating the examination display screen 6 will be described. The CPU 11 refers to the inspection information DB 223. The CPU 11 generates inspection information “CT inspection” in the inspection name column 61. The CPU 11 generates the beginning of the previous day examination explanation message “body to the present ...” to the left of the previous day examination explanation button 63. The CPU 11 generates the beginning of the day inspection explanation message “get enough sleep ...” to the left of the day examination explanation button 64. The switch button 65 includes rehabilitation, medication, examination, and surgical buttons. The rehabilitation button, the medication button, the examination button, and the operation button are buttons that perform the same operations as the rehabilitation button, the medication 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 with the input unit 34. The CPU 31 accepts an input of the examination explanation button 62. The CPU 31 displays an examination explanation message (not shown) on the display unit 35. The patient touches the previous day examination explanation button 63 with the input unit 34. The CPU 31 accepts input from the previous day examination explanation button 63. The CPU 31 displays a previous day inspection explanation message (not shown) on the display unit 35. The patient touches the examination explanation button 64 on the day using the input unit 34. The CPU 31 receives an input of the day inspection explanation button 64. The CPU 31 displays an inspection explanation message (not shown) on the day on the display unit 35.

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

  Hereinafter, a method for generating the operation display screen 7 will be described. The CPU 11 refers to the surgery information DB 224. The CPU 11 generates the operation information “open surgery” in the operation name column 71. The CPU 11 generates the beginning of the previous day operation explanation message “body to the present ...” in the left part of the previous day operation explanation button 74. The CPU 11 generates the beginning of the day's surgery explanation message “Get enough sleep ...” on the left side of the day's surgery explanation button 75. The CPU 11 generates the beginning “post-surgical pain ...” of the surgery explanation message at a later date on the left part of the surgery explanation button 76 at a later date. The switching button 77 has the same configuration as that of 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 with the input unit 34. The CPU 31 accepts an input from 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 grayout display of the operation explanation button 72. The CPU 31 sets the operation explanation flag to TRUE. The patient touches the operation explanation button 74 on the previous day with the input unit 34. The CPU 31 accepts an input from the previous day operation explanation button 74. The CPU 31 displays the previous day operation explanation message (not shown) on the display unit 35. The CPU 31 cancels the grayout display of the previous day operation explanation button 74. The CPU 31 sets the previous day operation explanation flag to TRUE. The patient touches the operation explanation button 75 on the day with the input unit 34. The CPU 31 accepts input of the operation explanation button 75 on the day. The CPU 31 displays a surgery explanation message (not shown) on the day on the display unit 35. The CPU 31 cancels the gray-out display of the operation explanation button 75 on that day. The CPU 31 sets the surgery explanation flag to TRUE on that day.

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

  The CPU 31 determines whether or not 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. That is, the CPU 31 determines whether or not each flag is TRUE, thereby determining whether or not the input of the surgery explanation button 72, the previous day surgery explanation button 74, the current day surgery explanation button 75, and the later day surgery explanation button 76 is accepted. To 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. The CPU 31 allows the acceptance of the consent document button 73 and cancels the gray-out display of the consent document button 73 because the operation explanation flag, the previous day operation explanation flag, the current day operation explanation flag, and the later day surgery explanation flag are TRUE. The patient touches the consent document button 73 with the input unit 34. The CPU 31 accepts input from 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 through 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 through the communication unit 16. The CPU 31 acquires the consent screen 8 from the information processing apparatus 1 through the communication unit 36. The CPU 31 displays the consent screen 8 on the display unit 35.

  FIG. 10 is an explanatory diagram for explaining the consent screen 8. As shown in FIG. 10, the consent screen 8 includes an operation message 80 provided at the top, an agreement button 81 provided at the left, a non-agreement button 82 provided at the right, an agreement button 81 and non-agreement. A name field 83 provided below the button 82 and an address field 84 provided below the name field 83 are provided. The surgery message 80 is a message indicating that the explanation of the surgery has been completed. The consent button 81 is a button indicating that the operation is agreed. The non-agreement button 82 is a button indicating that the operation is not agreed. The consent button 81 and the non-agreement button 82 are prohibited from input from the input unit 34 in the initial state. The name column 83 is a column for accepting input of a signature image of a name. A signature image is an image of a signature represented by a patient's handwriting. A specific sign image input method will be described later. The address field 84 is a field for accepting input of a signature image of an address.

  Hereinafter, a method for 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 laparotomy, the CPU 11 gives an explanation to the patient with the patient ID “001” about the current medical condition and laparotomy in the operation message 80. Is generated.

  Next, the operation of the consent screen 8 will be described. The patient inputs a signature image of his / her name and address in the name field 83 and the address field 84 using the input unit 34. Specifically, the patient writes his / her name and address in the name field 83 and the address field 84 on the touch panel with the electronic pen of the input unit 34. Note that the name and address sign images may be manually input on the touch panel of the input unit 34. The CPU 31 accepts input of a name and address sign image. The CPU 31 determines whether or not input of a name and address sign image has been accepted. The CPU 31 determines that the input of the name and address sign images has been accepted. The CPU 31 permits input of the consent button 81 and the non-agreement button 82. The patient touches the consent button 81 with the input unit 34. The CPU 31 receives input from the consent button 81. The CPU 31 sets the consent flag to TRUE. The patient touches the non-consent button 82 with the input unit 34. The CPU 31 accepts input from the non-agreement button 82. The CPU 31 sets the consent flag to FALSE.

  When the consent flag is TRUE, the CPU 31 generates an consent 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 an agreement document that documents the agreement screen 8. The documented consent document is, for example, a document obtained by converting the consent screen 8 into PDF (Portable Document Format, registered trademark). The consent document is not limited to PDF, and may be generated in another document format. The CPU 31 outputs the generated consent message, consent document, and set consent flag from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires the consent message, the consent document, and the set consent flag from the terminal device 3 through the communication unit 16. The CPU 11 displays an agreement message on the display unit 15. CPU11 updates the consent flag of surgery information DB224 to TRUE. The CPU 11 stores the consent document converted to PDF 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 the doctor.

  11 to 12 are flowcharts showing the processing procedure of the information processing system in this embodiment. The patient images the barcode with the imaging unit 37 of the terminal device 3. CPU31 acquires the barcode imaged with the imaging part 37 (step S11). The CPU 31 converts the barcode acquired using image processing into a patient ID (step S12). CPU31 outputs patient ID to the medical server 2 by the communication part 36 (step S13). CPU21 acquires patient ID from the terminal device 3 by the communication part 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). CPU11 acquires patient ID, medical information DB221, schedule information DB222, examination information DB223, and surgery information DB224 from medical server 2 by communication part 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).

  When it is determined that the acquired patient ID is not stored in the medical information DB 221 (step S17: NO), the CPU 11 ends the process. When determining 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). CPU31 acquires screen 5 for patients from information processor 1 by communications department 36 (Step S20). The CPU 31 displays the patient screen 5 on the display unit 35 (step S21).

  CPU31 determines whether the input of the test | inspection button was received (step S22). If the CPU 31 determines that the input of the inspection button has not been accepted (step S22: NO), the process proceeds to step S24. When the CPU 31 determines that the input of the inspection button has been received (step S22: YES), the CPU 31 performs display processing of the inspection display screen 6 (step S23).

  CPU31 determines whether the input of the operation button was received (step S24). If the CPU 31 determines that an operation button input has not been received (step S24: NO), the process proceeds to step S21 and the process is repeated. If the CPU 31 determines that an operation button input has been received (step S24: YES), it performs a display process for the operation display screen 7 (step S25), moves the process to step S21, and repeats the process.

  FIG. 13 is a flowchart showing the display processing of the examination display screen 6 in the present embodiment. CPU31 outputs the output request | requirement of the test | inspection display screen 6 to the information processing apparatus 1 from the communication part 36, when step S22 is YES (step S31). The CPU 11 acquires an output request for the examination display screen 6 from the terminal device 3 through the communication unit 16 (step S32). CPU11 produces | generates the test | inspection display screen 6 based on test | inspection information DB223 (step S33).

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

  CPU31 determines whether the input of each description column was 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 same day examination explanation button 64 has been accepted. When the CPU 31 determines that the input in each explanation column has not been accepted (step S37: NO), the display process of the examination display screen 6 is terminated, and the process proceeds to step S24. When the CPU 31 determines that the input of each explanation column has been accepted (step S37: YES), it displays an explanation message such as an examination explanation message, a previous day examination explanation message, or a current day examination explanation message corresponding to each explanation column (step S38). Then, the display process of the examination display screen 6 is terminated, and the process proceeds to step S24.

  14 to 16 are flowcharts showing display processing of the operation display screen 7 and the like in the present embodiment. CPU31 outputs the output request | requirement of the surgery display screen 7 to the information processing apparatus 1 from the communication part 36, when step S24 is YES (step S41). CPU11 acquires the output request of the surgery display screen 7 from the terminal device 3 by the communication part 16 (step S42). CPU11 produces | generates the surgery display screen 7 based on surgery information DB224 (step S43).

  The CPU 11 outputs the surgery display screen 7, the surgery explanation flag, the previous day surgery explanation flag, the current day surgery explanation flag, and the later day surgery explanation flag to the terminal device 3 through 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 current day surgery explanation flag, and the later day surgery explanation flag from the information processing apparatus 1 through 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 or not an input of each explanation button has been accepted (step S47). Specifically, the CPU 31 determines whether or not an input of the surgery explanation button 72, the previous day surgery explanation button 74, the current day surgery explanation button 75, or the later day surgery explanation button 76 is accepted. When it is determined that the input of each explanation button has not been accepted (step S47: NO), the CPU 31 waits until the input is accepted. When the CPU 31 determines that the input of each explanation button has been accepted (step S47: YES), it displays an explanation message such as an operation explanation message corresponding to each explanation button, an operation explanation message for the previous day, an operation explanation message for the day, or an operation explanation message for the later day. The information is displayed on the part 35 (step S48).

  CPU31 sets the description flag corresponding to each description message to TRUE (step S49). Specifically, the CPU 11 sets the operation explanation flag corresponding to the operation explanation message, the previous day operation explanation message, the current day operation explanation message, or the later day surgery explanation message, the previous day surgery explanation flag, the current day surgery explanation flag, or the later day surgery explanation flag to TRUE. .

  It is determined whether or not all the explanation flags are TRUE (step S50). Specifically, the CPU 31 determines whether or not 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. If the CPU 31 determines that all the explanation flags are not TRUE (step S50: NO), the process proceeds to step S47.

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

  When it is determined that the input of the consent document button 73 has been received (step S52: YES), the CPU 31 outputs an output request for the consent screen 8 from the communication unit 36 to the information processing apparatus 1 (step S53). CPU11 acquires the output request of consent screen 8 from terminal unit 3 by communications department 16 (Step S54). CPU11 produces | generates the consent screen 8 based on medical information DB221 (step S55). The CPU 11 outputs the consent screen 8 to the terminal device 3 through the communication unit 16 (step S56). CPU31 acquires consent screen 8 from information processor 1 by communications department 36 (Step S57). The CPU 31 displays the consent screen 8 on the display unit 35 (step S58).

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

  The CPU 31 determines whether or not an input from the consent button 81 has been accepted (step S61). When determining that the input of the consent button 81 has not been accepted (step S61: NO), the CPU 31 determines whether the input of the non-agreement button 82 has been accepted (step S62). If the CPU 31 determines that the input of the disagreement button 82 has not been accepted (step S62: NO), the process proceeds to step S61.

  If the CPU 31 determines that the input of the non-agreement button 82 has been accepted (step S62: YES), the consent flag is set to FALSE (step S63), the display process of the operation display screen 7 and the like is terminated, and the process proceeds to step S21. Transfer. If the CPU 31 determines that the input of the consent button 81 has been received (step S61: YES), it sets the consent flag to TRUE (step S64). The CPU 31 generates an agreement message (step S65).

  The CPU 31 generates a consent document that documents the consent screen 8 (step S66). The CPU 31 outputs an agreement message, an agreement document, and an agreement flag from the communication unit 36 to the information processing apparatus 1 (step S67). CPU11 acquires a consent message, a consent document, and a consent flag from the terminal device 3 by the communication part 16 (step S68). The CPU 11 displays an agreement message on the display unit 15 (step S69). CPU11 updates the consent flag of surgery information DB224 (step S70). CPU11 preserve | saves consent document in the memory | storage part 12 (step S71), and complete | finishes a process. Moreover, CPU31 complete | finishes display processes, such as a surgery display screen 7, after complete | finishing the process of step S67, and moves a process to step S21.

  In the present embodiment, the CPU 31 captures the barcode with the imaging unit 37, but the barcode may be read with a barcode reader. In this embodiment, the sign image input is accepted in order to allow the input of the consent button 82 and the non-agreement button 82. However, the barcode is captured again by the imaging unit 37, and the authentication process is performed using the captured barcode. The consent button 82 and the disagreement button 82 may be input. In the present embodiment, the consent screen 8 is generated for the surgery information. However, examination information or the like may be used, and the consent screen 8 only needs to be related to medical information.

  According to one aspect, the security can be improved as compared with the prior art.

  According to one aspect, the information processing apparatus 1 acquires the consent flag. As a result, the nurse or doctor who operates the information processing apparatus 1 can determine whether or not there is consent for the operation.

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

  In the present embodiment, information of the electronic medical record 421 is transmitted and received via the medical server 2 using SS-MIX, but is not limited thereto. For example, the electronic medical record server 4 may be connected to the communication network N1, and the information of the electronic medical record 421 may be directly transmitted to and received from the information processing apparatus 1 using a viewer.

Embodiment 2
The second embodiment relates to an embodiment in which the nurse exclusive screen 9 for the nurse to confirm the medical information of the patient is displayed on the display unit 35. In the following, the configuration and operation other than those specifically described are the same as those of the first embodiment, and the description is omitted for the sake of brevity. FIG. 17 is a block diagram illustrating a hardware group 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 stores a terminal ID for identifying the terminal device 3.

  FIG. 18 is a diagram illustrating an example of data stored in the ID type DB 225. The ID type DB 225 is a database that stores ID types 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 type of user identified by the ID is stored in the ID type column. For example, a patient ID, a nurse ID, a doctor ID, or the like is stored in the ID type column. The patient ID indicates an ID for identifying a patient. The nurse ID indicates an ID for identifying a nurse. The doctor ID indicates an ID for identifying a doctor. The ID type DB 225 is stored in advance in the input unit 24 by a nurse or a doctor.

  FIG. 19 is a diagram illustrating an example of data stored in the vital DB 226. The vital DB 226 is a database that stores vitals and the like. Vital is information representing the patient's condition, such as body temperature, respiratory rate, systolic blood pressure, diastolic blood pressure, pulse rate, or oxygen concentration in the artery. That is, vital is basic information about the life of a 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. A patient ID is stored in the patient ID column. The medical date is stored in the medical date column. In the medical time column, medical time (acquisition time) indicating the time when the vital is acquired is stored. The body temperature column stores the body temperature associated with the patient ID, the medical date, and the medical time. The respiratory rate column stores the respiratory rate associated with the patient ID, the medical date, and the medical time. The systolic blood pressure column stores the systolic blood pressure associated with the patient ID, the medical date, and the medical time. The lowest blood pressure column stores the lowest blood pressure associated with the patient ID, the medical date, and the medical time. In the pulse rate column, the pulse rate associated with the patient ID, the medical date and the medical time is stored. The oxygen concentration column stores the oxygen concentration associated with the patient ID, the medical date, and the medical time. The storage method of the vital DB 226 will be described later. 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 images the barcode described in his / her wristband with the imaging unit 37. The CPU 31 acquires the barcode imaged 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 through the communication unit 26. The CPU 21 sends the acquired nurse ID “N0001” and the medical information DB 221, schedule information DB 222, examination information DB 223, surgery information DB 224, ID type DB 225, and 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 through 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 or not 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 exclusive screen 9 from the communication unit 16 to the terminal device 3. The CPU 31 acquires the nurse-specific screen 9 from the information processing apparatus 1 through the communication unit 36. The CPU 31 displays the nurse dedicated screen 9 on the display unit 35.

  FIG. 20 is an explanatory diagram for explaining the nurse-only screen 9. The nurse dedicated screen 9 includes a nursing support record button 91 provided on the left side, a vital button 92 provided on the upper right side of the nursing support record button 91, and a switching button 93 provided on the right side of the vital button 92. Is provided.

  The nursing support record button 91 is a button for displaying a nursing support record screen (change screen) 110 for displaying changes in patient vitals. The nursing support record screen 110 is a screen that is generally used when the electronic medical record 421 is displayed. Since the nurse can work on the familiar screen by using the nursing support record screen 110, 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 switch button 93 includes rehabilitation, medication, examination, surgery, and treatment buttons.

  Hereinafter, the operation of the dedicated nurse screen 9 will be described. The nurse touches the vital button 92 with the input unit 34. The CPU 31 receives an input from 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 an output request for the vital screen 10 from the terminal device 3 through 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 through the communication unit 36. The CPU 31 displays the vital screen 10 on the display unit 35.

  The nurse touches the nursing support record button 91 with the input unit 34. The CPU 31 accepts an input from the nursing support record button 91. The CPU 31 outputs an output request for the nursing support recording screen 110 from the communication unit 36 to the information processing apparatus 1. The CPU 11 acquires an output request for the nursing support recording screen 110 from the terminal device 3 through the communication unit 16. The CPU 11 generates a nursing support recording 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 through 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 includes a medical date / time column 101 provided at the top, a body temperature column 102 provided at the lower left of the medical date / time column 101, a respiratory rate column 103 provided at the right part of the body temperature column 102, and a body temperature column 102. The systolic blood pressure column 104 provided in the lower part of the blood pressure, the diastolic blood pressure column 105 provided in the right part of the systolic blood pressure field 104, the pulse field 106 provided in the lower part of the systolic blood pressure field 104, and the right part of the pulse field 106 Are provided with an oxygen concentration column 107 and a registration button 108 provided at the lower right.

  The medical date and time column 101 is a column for receiving input of a medical date and a medical time for performing medical treatment. The body temperature column 102 is a column for receiving input of body temperature. The respiration rate column 103 is a column for receiving an input of respiration rate. The systolic blood pressure column 104 is a column for accepting input of systolic blood pressure. The minimum blood pressure column 105 is a column for receiving an input of minimum blood pressure. The pulse column 106 is a column for receiving an input of the pulse rate. The oxygen concentration column 107 is a column for accepting an oxygen concentration input. The registration button 108 is a button for registering the input vital in the electronic medical record 421. The units of the body temperature column 102, the respiratory rate column 103, the systolic blood pressure column 104, the diastolic blood pressure column 105, the pulse column 106, and the oxygen concentration column 107 are Celsius degree, frequency, MmHg (millimeter of mercury), MmHg, 1 minute. The number of times and percentage.

  Hereinafter, the operation of the vital screen 10 will be described. The nurse looks at his / her own clock, touches the medical date / time column 101 with the input unit 34, and enters the current medical date “August 20, 2015” and the medical time “9:00” with the input unit 34. input. The CPU 31 accepts the input of the medical date “August 20, 2015” and the medical time “9:00”. In addition, you may acquire a medical date and medical time automatically from the time measuring part (not shown) incorporated in the terminal device 3. FIG.

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

  The nurse measures the patient's maximum blood pressure “130” with a medical instrument. The nurse touches the systolic blood pressure column 104 with the input unit 34 and inputs the systolic blood pressure “130” with the input unit 34. CPU 31 accepts an input of systolic blood pressure “130”. The nurse measures the patient's minimum blood pressure “60”. The nurse touches the minimum blood pressure column 105 with the input unit 34 and inputs the minimum blood pressure “60” with the input unit 34. The CPU 31 accepts an input of the minimum blood pressure “60”.

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

  When the nurse touches the registration button 108 with the input unit 34, the CPU 31 displays the medical date “August 20, 2015”, the medical time “9:00”, the body temperature “37.0”, and the respiratory rate “60”. ”, Systolic blood pressure“ 130 ”, diastolic blood pressure“ 60 ”, pulse rate“ 75 ”, oxygen concentration“ 96 ”and the like are output from the communication unit 36 to the medical server 2. The CPU 21 has a medical date “August 20, 2015”, a medical time “9:00”, a body temperature “37.0”, a respiratory rate “60”, a maximum blood pressure “130”, a minimum blood pressure “60”, and a pulse. Vitals such as the number “75” and the oxygen concentration “96” are acquired from the terminal device 3 by the communication unit 26. The CPU 21 stores each vital in the vital DB 226. The CPU 21 outputs the vitals from the communication unit 26 to the electronic medical record server 4. The CPU 41 acquires vitals from the medical server 2 through the communication unit 46. The CPU 41 stores vitals in the electronic medical record 421. The CPU 41 generates a nursing support recording screen 110 based on the vitals stored in the electronic medical record 421.

  FIG. 22 is an explanatory diagram for explaining the nursing support record screen 110. The nursing support record screen 110 includes a vital graph 120 provided at the top, a body temperature column 130 provided at the bottom of the vital graph 120, a pulse rate column 140 provided at the bottom of the body temperature column 130, and a pulse rate column 140. The systolic blood pressure column 150 provided in the lower portion, the diastolic blood pressure column 160 provided in the lower portion of the systolic blood pressure column 150, the patient ID column 170 provided in the right portion, and the medical treatment provided in the upper portion of the patient ID column 170 A date field 180. The body temperature column 130 is a column for displaying body temperature. The pulse rate column 140 is a column for displaying the pulse rate. The systolic blood pressure column 150 is a column for displaying the systolic blood pressure. The minimum blood pressure column 160 is a column for displaying the minimum blood pressure column. The patient ID column 170 is a column for displaying a patient ID. The medical date column 180 is a column for switching the medical date. The vital graph 120 is a graph that displays the vital changes of the patient. The solid line of the vital graph 120 is a graph of body temperature. The broken line of the vital graph 120 is a pulse rate graph. The one-dot chain line of the vital graph 120 is a graph of the maximum blood pressure. A two-dot chain line in the vital graph 120 is a graph of the minimum blood 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” in the patient ID column 170 with the input unit 34, the CPU 31 causes the vital graph 120, the body temperature column 130, the pulse rate column 140, the maximum blood pressure column 150, the minimum blood pressure column 160, and the patient ID column. 170 is switched to the nursing support record screen 110 corresponding to the patient ID “001”. When the nurse switches the medical date in the medical date column 180 to “August 20, 2015” using the input unit 34, the CPU 31 displays the nursing support record screen 110 corresponding to “August 20, 2015”. Switch to. The CPU 41 generates a nursing support record screen 110 based on the vitals stored in the electronic medical record 421 today. 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 the nursing support record screen 110 based on the vitals stored in the electronic medical record 421 in the past. As described above, the CPU 41 can generate the vital care support recording screen 110 recorded in the past and the past by switching the display of the medical date column 180. Further, the CPU 41 may generate the nursing support recording screen 110 based not only on the vitals input on the vital screen 10 but also on the vitals recorded in the electronic medical record 421 at the time of a medical examination beforehand.

  A 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 through the communication unit 46. The CPU 41 updates the electronic medical record 421 based on the acquired vital DB 226. The CPU 41 refers to the vitals stored in the electronic medical record 421, and stores the body temperature, pulse rate, systolic blood pressure, systolic blood pressure and patient in the body temperature column 130, the pulse rate column 140, the systolic blood pressure column 150, the diastolic blood pressure column 160, and the patient ID column 170. ID is generated. The CPU 11 generates a time-series graph of body temperature, pulse rate, systolic blood pressure, and systolic blood pressure in the vital graph 120.

  As a specific example, a method for generating a body temperature graph will be described below. The CPU 41 refers to the vitals in the electronic medical record 421. The vital data structure in the electronic medical record 421 is the same as that of the vital DB 226, and FIG. 19 is referred to for the sake of brevity. As shown in FIG. 19, the CPU 41 sets the body temperature “37.0” corresponding to the medical time “9:00” of the patient ID “001”, the body temperature “37.0” corresponding to the medical time “10:00”, the medical The body temperature “37.0” corresponding to the time “11:00”, the body temperature “36.7” corresponding to the medical time “12:00”, and the body temperature “36.5” corresponding to the medical time “13:00”. A graph is generated by plotting on the vital graph 120 and connecting with a line. Hereinafter, the pulse rate, the maximum blood pressure, and the minimum blood pressure are the same, 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 it on the display unit 35.

  23 to 26 are flowcharts showing the processing procedure of the information processing system in this embodiment. Since the processing of steps S11 to S70 is the same as that of the information processing system according to the first embodiment, the description thereof is omitted for the sake of brevity. After the CPU 31 finishes the process of step S <b> 21, the nurse images the barcode written on his / her authentication card with the imaging unit 37. CPU31 acquires the barcode imaged with the imaging part 37 (step S80). The CPU 31 converts the bar code into an ID (step S81). CPU31 outputs ID to the medical server 2 from the communication part 36 (step S82). CPU21 acquires ID from the terminal device 3 by the communication part 26 (step S83).

  The CPU 21 outputs the acquired nurse ID and the medical information DB 221, schedule information DB 222, examination information DB 223, operation information DB 224, ID type DB 225 and vital DB 226 stored in the storage unit 22 from the communication unit 26 to the information processing apparatus 1 ( Step S84). CPU11 acquires nurse ID, medical information DB221, schedule information DB222, examination information DB223, operation information DB224, ID kind DB225, and vital DB226 by communication part 16 (Step S85).

  The CPU 11 determines whether or not 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. When the CPU 11 determines that the ID is stored in the ID type DB 225 (step S86: YES), the CPU 11 determines whether the ID type is a nurse ID (step S87).

  If the CPU 11 determines that the type of ID is not a nurse ID (step S87: NO), the process proceeds to step S17. If the CPU 21 determines that the type of ID is a nurse ID (step S87: YES), the CPU 21 generates a nurse-specific 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). CPU31 acquires nurse exclusive screen 9 from information processor 1 by communications department 36 (Step S90). The CPU 31 displays the nurse dedicated screen 9 on the display unit 35 (step S91).

  The CPU 31 determines whether or not an input from the vital button 92 has been accepted (step S92). If the CPU 31 determines that the input of the vital button 92 has not been accepted (step S92: NO), the process proceeds to step S108. When determining that the input of the vital button 92 has been received (step S92: 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 S93).

  The CPU 11 acquires an output request for the vital screen 10 from the terminal device 3 through the communication unit 16 (step S94). The CPU 11 generates the 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 through 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). CPU31 outputs the vital which accepted input to medical server 2 from communications department 36 (Step S100). CPU21 acquires a vital from the terminal device 3 by the communication part 26 (step S101). The CPU 21 updates the vital DB 226 (step S102).

  CPU21 outputs vital DB226 to the electronic medical record server 4 from the communication part 26 (step S103). CPU41 acquires vital DB226 from the medical server 2 by the communication part 46 (step S104). The CPU 41 updates the electronic medical record 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 record 421 (step S106). The CPU 41 stores the nursing support record screen 110 in the electronic medical record 421 (step S107) and ends the process.

  CPU31 determines whether the input of the nursing assistance recording button 91 was received after complete | finishing the process of step S100 (step S108). If the CPU 31 determines that the input of the nursing support record button 91 has not been accepted (step S108: NO), the process proceeds to step S92. When it is determined 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 for the nursing support record screen 110 from the terminal device 3 through 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 obtains an output request for 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 record 421 (step S113).

  CPU41 acquires nursing support record screen 110 in electronic medical record 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 through 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 through 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 uses the input unit 34 to end the display process for the nurse-specific screen 9 and the like (step S120), and moves the process to step S23.

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

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

  In this embodiment, when the nurse ID is determined, the nurse-only screen 9, the vital screen 10, and the nursing support record screen 110 are displayed. However, when the nurse ID is determined, the nurse-specific screen 9 is displayed. The vital screen 10 and the nursing support record screen 110 may be displayed.

Embodiment 3
The third embodiment relates to an embodiment in which a clinical path for explaining the progress of treatment in chronological order is displayed on the display unit 35. In the following, the configuration and operation other than those specifically described are the same as those of the first embodiment, and the description is omitted for the sake of brevity. FIG. 27 is a block diagram illustrating a hardware group 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 diagram illustrating an example of data stored in the pictogram DB 121. 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 column. A pictogram is stored in the pictogram column. Each column of the 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 for displaying a clinical path. The clinical path screen 20 includes a hospitalization date column, a preoperative day column, a surgical day column, a postoperative day column and a discharge date column, and a surgical row, examination row, and treatment row. The clinical path screen 20 includes an operation mark 201 in the operation day column of the operation line. The clinical path screen 20 is provided with a CT examination mark 202 in the day after surgery in the examination row. The clinical path screen 20 includes a treatment mark 203 in the day before surgery in the treatment row.

  Hospitalization date, preoperative day, surgical day, postoperative day, and discharge date columns correspond to August 17, August 18, August 19, August 20, and August 21, respectively. Yes. An operation mark 201 indicates an operation. CT inspection mark 202 indicates CT inspection. The treatment mark 203 indicates a treatment.

  Hereinafter, a method for 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, since the medical information on August 18, 2015 in the medical date column is the hemostatic treatment, the CPU 11 identifies the pictogram A corresponding to the hemostatic treatment as shown in FIG. As shown in FIG. 3, since the hemostatic treatment is treatment information, the CPU 11 generates the identified pictogram A in the treatment mark 203 of the treatment row in the August 18th column. As shown in FIG. 4, since the medical information on August 19, 2015 in the medical date column is the laparotomy, the CPU 11 identifies the pictogram B corresponding to the laparotomy as shown in FIG. As shown in FIG. 3, since the laparotomy is surgery information, the CPU 11 generates the identified pictogram B in the surgery mark 201 of the surgery row in the August 19th column. As shown in FIG. 4, the CPU 11 specifies a pictogram C corresponding to the CT examination, as shown in FIG. 28, since the medical information on August 20, 2015 in the medical date column includes the CT examination. . As shown in FIG. 3, since the CT examination is examination information, the CPU 11 generates the identified pictogram C in the CT examination mark 202 of the examination row in the 20th August column.

  Hereinafter, the operation of the clinical path screen 20 will be described. 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 through the communication unit 16. The CPU 11 refers to the pictogram DB 121. The CPU 11 specifies the CT examination corresponding to the pictogram C based on the pictogram DB 121.

  The CPU 11 determines whether or not the medical information specified based on the medical information DB 221 is surgery information. Since the specified medical information is a CT examination, the CPU 11 determines that the specified 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 through the communication unit 16. The CPU 31 acquires the examination display screen 6 from the information processing apparatus 1 through the communication unit 36. The CPU 31 displays the examination display screen 6 on the display unit 35. The following is the same as in the first embodiment, and the description is omitted for the sake of brevity.

  For example, when the patient touches the pictogram B of the surgical 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 through the communication unit 16. The CPU 11 refers to the pictogram DB 121. The CPU 11 specifies the laparotomy corresponding to the pictogram B based on the pictogram DB 121.

  Since the identified laparotomy is surgery information, the CPU 11 determines that the identified medical information is surgery information. The CPU 11 generates the consent screen 8 for the laparotomy specified based on the medical information DB 221. The CPU 11 outputs the generated consent screen 8 to the terminal device 3 through the communication unit 16. The CPU 31 acquires the consent screen 8 from the information processing apparatus 1 through the communication unit 36. The CPU 31 displays the consent screen 8 on the display unit 35. In addition, although CPU11 in this embodiment produced | generated the consent screen 8, you may produce | generate the surgery display screen 7. FIG. The following is the same as in 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 an input of a predetermined operation for outputting the clinical path screen 20 has been received by the input unit 34 (step S121). When the CPU 31 determines that the input of the predetermined operation has not been accepted by the input unit 34 (step S121: NO), the CPU 31 waits until the predetermined operation is performed. If the CPU 31 determines that an input of a predetermined operation has been received by the input unit 34 (step S121: YES), the CPU 31 outputs an output request for the clinical path screen 20 from the communication unit 36 to the information processing apparatus 1 (step S122). CPU11 acquires the output request of the clinical path screen 20 from the terminal device 3 by the communication part 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 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 through 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 or not the pictogram has been touched with the input unit 34 (step S130). When it is determined that the pictogram has not been touched by the input unit 34 (step S130: NO), the CPU 31 waits until the pictogram is touched. If the CPU 31 determines that the pictogram has been touched by the input unit 34 (step S130: YES), it outputs the touched pictogram from the communication unit 36 to the information processing apparatus 1 (step S131).

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

  CPU11 determines whether the medical information specified based on medical information DB221 is surgery information (step S135). When the CPU 11 determines 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). CPU31 acquires consent screen 8 with information processor 1 by communications department 36 (Step S138). The CPU 31 displays the consent screen 8 on the display unit 35 (step S139), and the process proceeds to step S59.

  If the CPU 11 determines that the specified medical information is not surgery information (step S135: NO), the CPU 11 generates a medical screen corresponding to the specified medical information (step S140). CPU11 outputs the produced | generated medical screen to the terminal device 3 by the communication part 16 (step S141). CPU31 acquires a medical screen from the information processing apparatus 1 by the communication part 36 (step S142). CPU31 displays a medical screen on display part 35 (Step S143). Hereinafter, the process corresponding to each medical screen of Embodiment 1 is implemented (step S144), and a process is complete | finished.

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

Embodiment 4
The fourth embodiment relates to an embodiment in which a doctor dedicated screen 30 is displayed on the display unit 35 for a doctor to check patient medical information. In the following, the configuration and operation other than those specifically described and the operation are the same as those of the second embodiment, and the description is omitted for the sake of brevity. FIG. 33 is a block diagram illustrating a hardware group of the information processing apparatus 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 diagram illustrating an example of data stored in the image data DB 227. The image data DB 227 is a database that stores image data such as X-ray images, endoscopic images, CT images, BRI images, or ultrasonic images. The image data DB 227 includes a patient ID column, a medical date column, an image data column, and the like. A 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 the medical date and image data from the electronic medical record 421 through 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 with a 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 through 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 surgery 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 apparatus 1. To 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 through 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 illustrated 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 to determine whether or not 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 through the communication unit 36. The CPU 31 displays the doctor dedicated screen 30 on the display unit 35.

  FIG. 35 is an explanatory diagram for explaining the doctor dedicated screen 30. 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. The image data button 301 is a button for displaying an image selection screen 40 for selecting an image. The switch button 302 has the same configuration and operation as the switch button 93, and is not 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 with the input unit 34. The CPU 31 receives input from 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 through 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 through 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. The image selection screen 40 includes a medical date column 41A, 41B, 41C, 41D and 41E (hereinafter referred to as a medical date column 401 as a representative in some cases) provided in order from the top on the left side, and a right side. Image selection buttons 42A, 42B, 42C, 42D and 42E (hereinafter referred to as image selection button 402 as a representative in some cases) provided in order from the top. The medical date column 401 is a column for displaying the medical date. The image selection button 402 is a button for selecting an image to be displayed on the display unit 35.

  Hereinafter, a method for 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 performs 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 columns 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 with the input unit 34, the CPU 31 accepts the selection of the image selection button 42A. The CPU 31 displays the 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 with the input unit 34, the CPU 31 accepts the selection of the image selection button 42B. The CPU 31 displays the endoscope 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 is omitted for the sake of brevity.

  37 to 38 are flowcharts showing the processing procedure of the information processing system in this embodiment. The processing from step S11 to step S21 is the same as in the second embodiment, and the description is omitted for the sake of brevity. After completing step S21, the CPU 31 obtains an ID from the IC card with a card reader (step S150), and moves the process to step S82. When step S87 is NO, the CPU 11 determines whether or not 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 the CPU 11 determines that the acquired ID is a doctor ID (step S151: YES), the CPU 11 generates a doctor-only 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). CPU31 acquires doctor exclusive screen 30 from information processor 1 by communications department 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 from 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). CPU31 acquires the output request of the image selection screen 40 from the terminal device 3 by the communication part 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 through 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 accepts 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 for the image selection screen 40 using the input unit 34 (step S165), and ends the process.

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

  In this embodiment, when the doctor ID is determined, the doctor dedicated screen 30 and the image selection screen 40 are displayed. However, when the doctor ID is determined to be the nurse ID, the doctor dedicated screen 30 and the image selection screen 40 are displayed. May be. Further, the type of ID is not limited to a patient, doctor or nurse ID, and can be used as an ID for identifying a medical person such as a pharmacist ID or an X-ray technician ID.

  The embodiments disclosed herein are illustrative in all respects and should not be considered as restrictive. The scope of the present invention is defined by the terms of the claims, rather than the meanings described above, and is intended to include any modifications within the scope and meaning equivalent to the terms of the claims. Further, each embodiment can be appropriately combined within a range in which processing contents are not contradictory.

DESCRIPTION OF SYMBOLS 1 Information processing apparatus 12 Memory | storage part 13 RAM (memory | storage part)
12P program 3 Terminal device 32P program 35 Display unit 7 Surgery display screen (explanation screen)
72 Surgery explanation button 73 Consent document button (Acquire button)
74 The operation explanation button on the previous day 75 The operation explanation button on the day 76 The operation explanation button on the later day 8 Consent screen 10 Vital screen (input screen)
110 Nursing

Claims (3)

A first acquisition unit for acquiring first patient medical information derived using the patient identification information;
A first medical information display unit for displaying the first patient medical information acquired by the first acquisition unit;
A second acquisition unit for acquiring medical worker identification information for identifying a medical worker in a state where the first patient medical information is displayed by the first medical information display unit;
Medical care for the medical worker to confirm the medical information of the patient based on the second patient medical information acquired from the information processing device after transmitting the acquired medical worker identification information to the information processing device A second medical information display unit for displaying a worker screen;
From the state where the second medical information display unit displays the screen for the medical staff, the screen is generated based on the input screen for receiving the input of the state information related to the state of the patient and the history of the state information An information display unit for displaying at least one of change information screens for indicating a change in the state of the patient;
A terminal device comprising: A first transmitter for transmitting first patient medical information derived using patient identification information to the terminal device;
A receiving unit that receives from the terminal device medical worker identification information for identifying a medical worker, acquired in a state in which the first patient medical information is displayed on the terminal device;
When the medical worker identification information is received, the second patient medical information derived using the patient identification information is transmitted to the terminal device, and the medical worker confirms the medical information of the patient. A second transmitter for displaying a screen for workers on the terminal device;
From the state in which the screen for the medical staff is displayed on the terminal device, the input screen for accepting input of state information regarding the state of the patient, and the state of the patient generated based on the history of the state information A display control unit that transmits and displays at least one of change information screens for indicating changes in the terminal device;
An information processing apparatus comprising: A transmission step of transmitting the first patient medical information derived using the patient identification information from the information processing apparatus to the terminal device;
A first medical information display step of displaying the first patient medical information on the terminal device;
In the state where the first patient medical information is displayed in the first medical information display step, the terminal device acquires medical worker identification information for identifying a medical worker;
After the acquired medical worker identification information is transmitted to the information processing device, the medical worker confirms the medical information of the patient based on second patient medical information acquired from the information processing device. A second medical information display step for displaying a screen for medical workers on the terminal device;
From the state in which the screen for medical personnel is displayed in the second medical information display step, the screen is generated based on an input screen for receiving input of state information related to the state of the patient, and a history of the state information An information display step for causing the terminal device to display at least one of change information screens for indicating a change in the state of the patient;
An information processing method including: