JP6540470B2 - Browsing control method, browsing control program and browsing control device - Google Patents

Description

  The present invention relates to a browsing control method, a browsing control program, and a browsing control apparatus.

  Conventionally, for example, there is a system that allows personal information including past diagnostic information such as name, date of birth and medical history input in multiple hospitals to be browsed when emergency personnel enter patient identification information. .

JP, 2013-214905, A

  By the way, notifying the hospital of the transfer destination candidate of personal information at the time of emergency conveyance is useful at the time of acceptance judgment on the hospital side. However, as it is personal information, it is not desirable to notify an unspecified number of hospitals. Therefore, it is conceivable to notify the patient's personal information only to the hospital selected by the paramedics using a system capable of browsing personal information including past diagnostic information.

  If personal information has been notified but the notification destination hospital refuses to accept the patient, the paramedics will notify the other hospital of the personal information and ask for a decision on acceptance. In such a case, it is not desirable from the viewpoint of protection of personal information that the patient's personal information can still be browsed in the hospital notified first despite the fact that the patient is not accepted.

  In one aspect, it is an object of the present invention to provide a view control method, a view control program and a view control device capable of protecting personal information.

  In the first scheme, the browsing control method includes a storage unit in which a computer stores personal information including emergency delivery destination candidates in association with identification information in response to a request for acquisition of personal information based on first identification information. A process of referring to and transmitting personal information including an emergency delivery destination candidate corresponding to the first identification information to the terminal of the request source of the acquisition request is executed. According to the browsing control method, when the computer selects a first emergency destination among the emergency destination candidates at the terminal, the first emergency destination terminal browses personal information corresponding to the first identification information. Execute processing to set whether to allow or not. The browsing control method is the personal information corresponding to the first identification information by the terminal of the first emergency destination, when the second emergency destination among the emergency destination candidates is selected at the terminal after setting by the computer. Execute the process to set to disable the setting of the permission of viewing.

  According to one embodiment of the present invention, there is an effect that personal information can be protected.

FIG. 1 is a diagram for explaining an example of a system configuration. FIG. 2 is a diagram schematically showing a functional configuration of the browsing control device. FIG. 3 is a view showing an example of the data configuration of medical institution information. FIG. 4 is a view showing an example of the data configuration of registered patient information. FIG. 5 is a view showing an example of the data configuration of the medical care information. FIG. 6 is a view showing an example of the data configuration of emergency introduction destination information. FIG. 7 is a view showing an example of the data configuration of the acceptance registration information. FIG. 8 is a view showing an example of the data configuration of the generated disaster information. FIG. 9 is a view showing an example of the data configuration of transfer patient information. FIG. 10 is a view showing an example of the data configuration of the physiological evaluation information. FIG. 11 is a diagram showing an example of a data configuration of medical condition information. FIG. 12 is a view showing an example of the data configuration of used medical institution information. FIG. 13 is a view showing an example of the data configuration of the transfer request status information. FIG. 14A is a diagram illustrating an example of an operation screen for a rescue team. FIG. 14B is a diagram illustrating an example of an operation screen for a rescue team. FIG. 14C is a diagram showing an example of the operation screen for the rescue team in which the information on the patient is input. FIG. 14D is a diagram showing an example of the operation screen for the rescue team when registering a plurality of patients. FIG. 14E is a diagram showing an example of the operation screen for the rescue team on which a tab of patient medical treatment information is displayed. FIG. 14F is a diagram illustrating an example of an operation screen for a rescue team. FIG. 15A is a diagram illustrating an example of an operation screen for a rescue team. FIG. 15B is a diagram illustrating an example of an operation screen for a rescue team. FIG. 15C is a diagram showing an example of an operation screen for a rescue team. FIG. 16A is a diagram illustrating an example of the transmission screen. FIG. 16B is a diagram showing an example of the reason input screen. FIG. 17 is a diagram showing an example of a change in conveyance request status information. FIG. 18A is a diagram illustrating an example of a browsing screen. FIG. 18B is a diagram illustrating an example of a browsing screen. FIG. 19 is a flowchart showing an example of the flow of browsing control. FIG. 20 is a diagram showing an example of the operation screen for the rescue team. FIG. 21 is a diagram illustrating an example of a computer that executes a browsing control program.

  Hereinafter, embodiments of a browsing control method, a browsing control program, and a browsing control apparatus according to the present invention will be described in detail based on the drawings. The present invention is not limited by this embodiment. And each Example can be suitably combined in the range which does not make processing contents contradictory.

[System configuration]
First, an example of the system will be described. FIG. 1 is a diagram for explaining an example of a system configuration. The system 10 is a system used by a rescue team to determine where to transfer a patient. The system 10 includes a browsing control device 11, a terminal device 12, a terminal device 13, and a terminal device 14. The browsing control device 11, the terminal device 12, the terminal device 13, and the terminal device 14 are communicably connected to the network N. As one mode of the network N, any type of communication such as mobile communication network such as mobile phone, Internet (Internet), LAN (Local Area Network), VPN (Virtual Private Network) or the like regardless of wired or wireless. A network can be adopted. In the example of FIG. 1, the network N is provided with a base station N1 of a mobile communication network. The terminal device 12 is communicably connected to the network N by wireless communication via the base station N1. In this embodiment, in order to protect information to be transmitted, communication is performed by VPN using encrypted communication technology such as IPsec (Security Architecture for Internet Protocol). In the example of FIG. 1, although the case where the terminal device 12 and the terminal device 13 were provided one each was illustrated, it is not limited to this, and makes the terminal device 12, the terminal device 13, and the terminal device 14 arbitrary numbers. be able to.

  The terminal device 12 is a device used by a rescue team. For example, the terminal device 12 is a portable information processing device such as a smartphone or a tablet terminal capable of communicating with a mobile communication network. The terminal device 12 is provided with a camera, and can capture an image or a moving image. In addition, the terminal device 12 is installed with first aid software for supporting a rescue team. The emergency support software is a Web (World Wide Web) application, and accesses the browsing control device 11 when activated. When the emergency support software is activated, the terminal device 12 transmits / receives various information to / from the browsing control device 11 to display various operation screens, and it is also possible to capture an image or a moving image by the camera from the operation screen. . When emergency services are requested, the ambulance service rushes to the site where the emergency services have been requested by ambulances, etc., and transports patients who require emergency services, such as sick and sick, to medical institutions such as hospitals. At this time, the rescue team uses the terminal device 12 to search for a medical institution capable of receiving the patient, sends various information on the patient to the medical institution, and requests the patient's acceptance. Then, the ambulance transports the patient to a medical institution that has been answered as acceptable. The emergency support software is not limited to the web application, and may be a native application.

  The terminal device 13 is a device used by a medical institution capable of responding to an emergency. For example, the terminal device 13 is an information processing device such as a personal computer or a smartphone or a tablet terminal. The terminal device 13 has a web browser installed. The terminal device 13 accesses the browsing control device 11 through the web browser, and transmits / receives various information to / from the browsing control device 11. Various operation screens are displayed on the web browser of the terminal device 13. For example, the web browser of the terminal device 13 displays various information on the patient whose acceptance has been requested by the rescue team. The medical institution responds as to whether or not to accept the patient based on various information on the displayed patient.

  The terminal device 14 is a device used by a medical institution that a patient visits on a daily basis. For example, the terminal device 14 is an information processing device such as a personal computer or a smartphone or a tablet terminal. The terminal device 14 has a web browser installed. The terminal device 14 accesses the browsing control device 11 through the web browser, and transmits / receives various information to / from the browsing control device 11. Various operation screens are displayed on the web browser of the terminal device 13. For example, the Web browser of the terminal device 14 displays a screen for registering various information related to the patient. The patient's family doctor and pharmacist register various information about the patient in charge.

  The reading control device 11 is a device that controls reading of patient's personal information when the rescue team requests the medical institution to accept the patient. The browsing control device 11 is, for example, a computer such as a personal computer or a server computer. The browsing control device 11 may be implemented as a single computer or may be implemented by a plurality of computers. In the present embodiment, the case where the browsing control device 11 is one computer will be described as an example. When accessed by the terminal device 12, the terminal device 13 and the terminal device 14, the browsing control device 11 transmits and receives various types of information to and from the terminal device 12, the terminal device 13 and the terminal device 14, and displays various operation screens.

[Configuration of browsing control device]
Next, the configuration of the browsing control device 11 will be described. FIG. 2 is a diagram schematically showing a functional configuration of the browsing control device. The browsing control device 11 includes a communication I / F (interface) unit 20, a storage unit 21, and a control unit 22. In addition, the browsing control apparatus 11 may have apparatuses other than said apparatus.

  The communication I / F unit 20 is an interface that performs communication control with another device. The communication I / F unit 20 transmits and receives various types of information to and from other devices via the network N. As the communication I / F unit 20, a network interface card such as a LAN card can be adopted.

  The storage unit 21 is a storage device that stores various types of information. For example, the storage unit 21 is a storage device such as a hard disk, a solid state drive (SSD), or an optical disk. The storage unit 21 may be a semiconductor memory capable of rewriting data such as a random access memory (RAM), a flash memory, and a non volatile static random access memory (NV SRAM).

  The storage unit 21 stores control programs to be executed by the control unit 22 and various programs. Furthermore, the storage unit 21 stores various data used in a program executed by the control unit 22. For example, the storage unit 21 includes medical institution information 30, registered patient information 31, medical care information 32, emergency introduction destination information 33, acceptance registration information 34, occurrence disaster information 35, and transfer patient information 36, Physiological evaluation information 37, medical condition information 38, used medical institution information 39, and transport request status information 40 are stored.

  The medical institution information 30 is data storing information on the medical institution. FIG. 3 is a view showing an example of the data configuration of medical institution information. As shown in FIG. 3, the medical institution information 30 has items such as “medical institution code”, “medical institution name”, “emergency response”, “location zone” and the like. Each item of medical institution information 30 shown in Drawing 3 is an example, and may have other items. The data configuration of the medical institution information 30 is also an example, and the present invention is not limited to this.

  The item of medical institution code is an area for storing identification information for identifying each medical institution. A unique medical institution code is assigned to medical institutions such as hospitals as identification information. The medical institution code field stores the medical institution code assigned to the medical institution. The item of medical institution name is an area for storing the name of the medical institution. The item for emergency response is an area for storing whether or not the patient for emergency can be handled. The item for emergency response stores “Y” in the case of a medical institution corresponding to an emergency patient such as an emergency hospital, and in the case of a medical institution not corresponding to an emergency patient such as a clinic or clinic, "N" is stored. The item of the location area is an area for storing information on the area where the medical institution is located. For example, in the item of location area, the name of the municipality where the medical institution is located is stored.

  In the example of FIG. 3, the medical institution with the medical institution code "M01" has the name "AA hospital", does not respond to the emergency, and indicates that the district is "XX city". The medical institution with the medical institution code "M10" has the name "HH hospital", supports emergency, and indicates that the district is "XX city".

  Returning to FIG. 2, registered patient information 31 is data in which information on a patient is stored. FIG. 4 is a view showing an example of the data configuration of registered patient information. As shown in FIG. 4, the registered patient information 31 has items such as “patient NO”, “name”, “phonetic”, “address”, “sex”, “telephone number”, “birth date” and the like. Each item of the registered patient information 31 shown in FIG. 4 is an example, and may have other items. The data configuration of the registered patient information 31 is also an example, and the present invention is not limited to this.

  Here, a patient may go to a hospital for chronic illness etc., and may be taking medicine according to the chronic illness. Information on medical care such as the patient's chronic illness and medicine being taken can be provided to medical institutions in an emergency to support appropriate medical care. Information about this medical care is easy to understand for your doctor. Therefore, a system has been constructed to share information on this medical treatment. A unique patient NO is determined for a patient who shares information on medical care, and a card is provided with a code image such as a QR (Quick Response) code that encodes the patient NO. Further, information to be shared regarding medical care, such as the patient's name, address, sex, telephone number, date of birth, etc., is registered in the registered patient information 31. The card is not limited to the card in which the code image is described, and may be an IC (Integrated Circuit) card.

  The item of patient NO is an area for storing patient NO as identification information for identifying each patient. The item of the name is an area for storing the patient's name. The item of the reading is an area for storing readings indicating how to read the patient's name. The address item is an area for storing the address of the place where the patient is mainly based on life. The gender item is an area for storing the gender of the patient. The item of the telephone number is an area for storing the telephone number designated as the contact information of the patient. The item of date of birth is an area for storing the year, month, and day when the patient was born.

  In the example of FIG. 4, the patient of patient NO "0001" has a name "Fujitsu Taro", a phonetic address "Fujitsu Utaro", an address "XXXX", a gender "male", and a telephone call. It shows that the number is "1111111111" and the date of birth is "April 1, 582." In addition, the patient of patient NO “9999” has the name “Fujitsu Ichiro”, the phonetic person “Fujitsu Ichiro”, the address “XXXX”, the gender “male” and the telephone number “1234567890” It indicates that the date of birth is "February 12, 1985".

  Returning to FIG. 2, the medical care information 32 is data in which information on medical care obtained by having a patient consulted at a medical institution is stored. FIG. 5 is a view showing an example of the data configuration of the medical care information. As shown in FIG. 5, the medical care information 32 has items such as “medical institution code”, “patient NO”, “daily life state”, and “action feature”. Each item of medical treatment information 32 shown in Drawing 5 is an example, and may have other items. Further, the data configuration of the medical care information 32 is also an example, and the present invention is not limited to this.

  The item of medical institution code is an area for storing the medical institution code of the medical institution that has registered information on medical care. The item of patient NO is an area for storing patient NO of a patient for whom information on medical care is registered. The item of the daily living condition is an area for registering information on the daily life of the patient. In the present embodiment, the items of the daily living condition are divided into items of "meal", "nutritional route", "excretion", and "migration". The item of meal is an area for storing the state of assistance required for the patient to take a meal. The item of the nutrition route is an area in which the patient memorizes the route of getting nutrition. The item of excretion is an area for storing the state of assistance required for the patient to excrete. The item of movement is an area for storing the state of assistance required when the patient moves. The item of the behavior feature is an area for storing the feature of the behavior of the patient. Here, items other than the medical institution code and the patient NO are taken as optional registration items, and if there is information on the item, "-" is stored if there is no information.

  An ordinary doctor or a pharmacist or the like of a medical institution to which the patient visits daily uses the terminal device 14 to register information on the patient's medical care such as the patient's daily living condition, behavior characteristics, and the like. The registered information is stored in the medical care information 32.

  In the example of FIG. 5, the medical institution of medical institution code "M01" needs some assistance for eating as information on the medical treatment of the patient of patient NO "9999", the nutrition route is oral, and the excretion is partly It indicates that assistance is required, movement is partially assisted, and it is registered as a devastating behavior feature.

  Returning to FIG. 2, the emergency introduction destination information 33 is data in which information on an emergency introduction destination registered for a patient is stored. FIG. 6 is a view showing an example of the data configuration of emergency introduction destination information. As shown in FIG. 6, the emergency introduction destination information 33 has items such as “patient NO”, “registration number”, and “medical institution code”. Each item of the emergency introduction destination information 33 illustrated in FIG. 6 is an example, and may have other items. The data configuration of the emergency introduction destination information 33 is also an example, and the present invention is not limited to this.

  The item of the patient NO is an area for storing the patient NO of the patient for whom the referral destination in the emergency is registered. The item of registration number is an area for storing a number indicating the order of introduction destinations. The item of medical institution code is an area for storing the medical institution code of the medical institution to which the emergency is referred.

  The doctor, pharmacist, etc. of the patient's family register the information on the medical institution of the referral destination at the time of emergency desired by the patient using the terminal device 14. The registered information is stored in the emergency introduction destination information 33.

  In the example of FIG. 6, the patient with the patient NO “9999” indicates that the medical institution with the medical institution code “M10” is registered as the referral destination in the emergency as the registration number “1”. In addition, the patient with the patient NO “9999” indicates that the medical institution with the medical institution code “M11” is registered as the referral destination at the time of emergency as the registration number “2”.

  Returning to FIG. 2, the acceptance registration information 34 is data storing information on whether or not a medical institution capable of responding to a patient of first aid can accept the first aid. FIG. 7 is a view showing an example of the data configuration of the acceptance registration information. As shown in FIG. 7, the acceptance registration information 34 has items such as “medical institution code” and “registration information”. Each item of the acceptance registration information 34 shown in FIG. 7 is an example, and may have other items. The data configuration of the acceptance registration information 34 is also an example, and the present invention is not limited to this.

  At a medical institution capable of handling an emergency patient, the terminal device 13 registers whether the emergency can be accepted or not. The registered information is stored in the acceptance registration information 34.

  The example in FIG. 7 indicates that the medical institution with medical institution code “M10” has indicated that the acceptance of the emergency is not possible. Also, it indicates that the medical institution with medical institution code "M11" has stated that it is possible to receive an emergency.

  Returning to FIG. 2, the generated disaster information 35 is data in which information on the generated disaster is stored. FIG. 8 is a view showing an example of the data configuration of the generated disaster information. As shown in FIG. 8, the occurrence disaster information 35 has items such as “disaster number”, “emergency unit code”, “local arrival date and time”, and “occurrence place”. Each item of the occurrence disaster information 35 shown in FIG. 8 is an example, and may have other items. Further, the data configuration of the generated disaster information 35 is also an example, and the present invention is not limited to this.

  The item of the disaster number is an area for storing identification information for identifying each disaster for which the rescue team has been dispatched. For disasters dispatched by the rescue team, unique disaster numbers are automatically and sequentially assigned as identification information for each disaster. The number of disaster numbers is stored in the disaster number item. The rescue team code is an area for storing identification information for identifying the dispatched rescue team. The rescue team is given a unique rescue team code as identification information. The rescue team code may be unique for each fire department or jurisdiction area to which the rescue team belongs. The item of the local arrival date and time is an area for storing the local arrival date and time when the rescue team arrived at the spot where the emergency was requested. The occurrence place is an area for storing the place where the rescue team arrived.

  In the example of FIG. 8, the emergency unit “T001” is dispatched by the emergency unit code with the emergency number “0001”, the local arrival date is “2015/8/31 20:26”, and the disaster place is Indicates that "XXXXX". In addition, as for the disaster of the disaster number "0002", the emergency team of the emergency team code "T002" is dispatched, the local arrival date is "2015/8/31 22:30", and the occurrence place is "XXXXX" To indicate that

  Returning to FIG. 2, the transfer patient information 36 is data in which information on a patient to be transferred due to a disaster that has occurred is stored. FIG. 9 is a view showing an example of the data configuration of transfer patient information. As shown in FIG. 9, the transfer patient information 36 includes “disaster number”, “registration number”, “patient NO”, “name”, “furigana”, “address”, “sex”, “phone number”, “ It has items such as "birth date". Each item of the transfer patient information 36 shown in FIG. 9 is an example, and may have other items. Further, the data configuration of the transfer patient information 36 is also an example, and the present invention is not limited to this.

  The item of disaster number is an area for storing disaster numbers of disasters. The item of registration number is an area for storing a number indicating the registered order of patients. The item of patient NO is an area for storing patient NO of a patient. The item of the name is an area for storing the patient's name. The item of the reading is an area for storing readings indicating how to read the patient's name. The address item is an area for storing the patient's address. The gender item is an area for storing the gender of the patient. The item of the telephone number is an area for storing the telephone number as the contact information of the patient. The item of date of birth is an area for storing the year, month, and day when the patient was born. Here, the items of patient No., name, kana, address, gender, telephone number, date of birth are arbitrary registration items, and when there is information on the item, "-" is stored if there is no information. .

  In the example of FIG. 9, the disaster number "0001" indicates that there is only one patient because the registration number is only "1", and the patient NO of the patient is "9999". In the disaster with the disaster number "0001", the patient's name is "Fujitsu Ichiro", the phonetic address is "Fujitsuichi Ichiro", the address is "XXXX", the gender is "male", and the telephone number is It is "1234567890" and indicates that the date of birth is "February 12, 1985". Moreover, the disaster number "0002" has two patients because the registration number is "1" and "2", the patient NO of the first patient is "0001", and the second patient is Indicates that the patient's NO is unregistered. In the disaster with the disaster number “0002”, the first patient's name is “Fujitsu Taro”, “Kuri” is “Fujitsu Utaro”, the address is “XXXX”, and the gender is “male”, Indicates that the telephone number is "1111111111" and the date of birth is "April 1, 582." In the disaster with the disaster number “0002”, the name of the second patient is “Fujitsu Hanako”, the kurihana is “Fujitsu Hanako”, the address is “XXXX”, and the gender is “Female”, It indicates that the telephone number is “1111111111” and the date of birth is unregistered.

  Returning to FIG. 2, the physiological evaluation information 37 is data in which information on the physiological evaluation of the patient measured by the rescue team is stored. FIG. 10 is a view showing an example of the data configuration of the physiological evaluation information. As shown in FIG. 10, the physiological evaluation information 37 includes "disaster number", "emergency unit code", "registration number", "measurement number", "elapsed time", "JCS", "GCS", "respiration" , “Blood pressure”, “pulse”, “SPO2” and the like. Each item of the physiological evaluation information 37 illustrated in FIG. 10 is an example, and may have other items. The data configuration of the physiological evaluation information 37 is also an example, and the present invention is not limited to this.

The item of disaster number is an area for storing disaster numbers of disasters. The item of the rescue team code is an area for storing the rescue team code of the dispatched rescue team. The item of the registration number is an area for storing the registration number corresponding to the patient whose physiological evaluation has been performed. The item of the measurement number is an area for storing a number indicating the registered order of the physiological evaluation performed on the patient. For each patient, when a physiological evaluation is registered, a unique measurement number is automatically numbered sequentially from one. The numbered measurement number is stored in the item of measurement number. The item of elapsed time is an area for storing the elapsed time from the time when the rescue team arrived to the time when the physiological evaluation was performed. The item of JCS is an area for storing an evaluation value of JCS (Japan Coma Scale) representing the measured level of consciousness. The item of GCS is an area for storing an evaluation value of GCS (Glasgow Come Scale) representing the measured level of consciousness. The item of respiration is an area in which the measured respiration rate is stored. The item of blood pressure is an area for storing the measured blood pressure value. The item of pulse is an area for storing the measured pulse rate. Item SPO2 is an area for storing the measured transcutaneous arterial oxygen saturation (Spo _2). Here, the items of JCS, GCS, respiration, blood pressure, pulse, and SPO2 are set as arbitrary registration items, and if there is information on the item, “-” is stored if there is no information.

  In the example of FIG. 10, for the disaster with the disaster number "0001", an emergency unit with an emergency unit code "T001" is dispatched, and the measurement number is "1", "2" for the patient with the registration number "1". Indicates that the physiological evaluation was performed twice. For disaster number "0001", the first physiology evaluation is performed 36 minutes after the arrival of the rescue team, JCS is "2", GCS is "E: 3, V: 4, M: 6" There are 12 breaths, a blood pressure of 130/80, a pulse of 70 and an SPO2 of 98%. In addition, for the disaster with disaster number "0001", the second physiological evaluation is performed one hour after the arrival of the rescue team, the JCS is "2", and the GCS is "E: 3, V: 4, M: 6 Indicates that the respiration is 11 times, the blood pressure is 125/78, the pulse is 68, and the SPO2 is 97%.

  Returning to FIG. 2, the medical condition information 38 is data storing information on the medical condition of the patient evaluated by the rescue team. FIG. 11 is a diagram showing an example of a data configuration of medical condition information. As shown in FIG. 11, the medical condition information 38 has items such as “disaster number”, “emergency unit code”, “registration number”, “medical condition”, “medical department” and the like. Each item of the medical condition information 38 illustrated in FIG. 11 is an example, and may have other items. Further, the data configuration of the medical condition information 38 is also an example, and the present invention is not limited to this.

  The item of disaster number is an area for storing disaster numbers of disasters. The item of the rescue team code is an area for storing the rescue team code of the dispatched rescue team. The item of the registration number is an area for storing the registration number corresponding to the patient whose physiological evaluation has been performed. The item of the medical condition is an area for storing the medical condition of the patient. The item of the medical department is an area for storing information on the medical department which the patient has consulted. Here, the items of the medical condition and the medical department are regarded as optional registration items, and when there is information on the items, "-" is stored if there is no information.

  In the example of FIG. 11, the emergency unit “T001” is dispatched by the emergency unit code “disruption unit with emergency number“ 0001 ”, there is trauma as the medical condition of the patient with the registration number“ 1 ”, and the medical department is unknown. Indicates that there is.

  Returning to FIG. 2, the used medical institution information 39 is data in which the emergency services have stored information on medical institutions frequently used in the emergency. FIG. 12 is a view showing an example of the data configuration of used medical institution information. As shown in FIG. 12, the used medical institution information 39 has items such as "emergency unit code", "order", and "medical institution code". In addition, each item of the utilization medical institution information 39 shown in FIG. 12 is an example, and may have other items. Further, the data configuration of the used medical institution information 39 is also an example, and the present invention is not limited to this.

  The item of the rescue team code is an area for storing the rescue team code of the rescue team. The item of rank is an area for storing numerical values indicating the rank in descending order of usage frequency. The item of medical institution code is an area for storing medical institution codes of ranked medical institutions.

  The system administrator registers the frequently used medical institution by the rescue team for the rescue team for each rescue team. The registered information is stored in the used medical institution information 39. In addition, for example, the system counts the number of times the system of the browsing control device 11 transported the patient for each medical institution at the timing of a predetermined period such as half a year or the predetermined date and time such as April 1 The medical institution with high usage frequency may be automatically registered in the medical institution information 39 for each unit.

  In the example of FIG. 12, the medical service of the medical institution code "M14" is first in the frequency of use of the emergency services of the emergency team code "T001", and the medical institution of the medical institution code "M15" is the second in use frequency. Indicates that the medical institution with the medical institution code “M16” is the third most frequently used.

  Returning to FIG. 2, the transfer request status information 40 is data storing information on a status where a medical institution capable of dealing with a patient of the emergency requests the acceptance of the emergency. FIG. 13 is a view showing an example of the data configuration of the transfer request status information. As shown in FIG. 13, the transfer request status information 40 includes items such as “disaster number”, “request number”, “notification destination”, “notification date”, “status”, “reason”, “view patient information”, etc. Have. Each item of the transfer request status information 40 illustrated in FIG. 13 is an example, and may have other items. The data configuration of the transfer request status information 40 is also an example, and the present invention is not limited to this.

  The item of disaster number is an area for storing disaster numbers of disasters. The item of the request number is an area for storing a number indicating the order in which the medical institution is requested to receive an emergency for the disaster of the disaster number. The item of notification destination is an area for storing the medical institution code of the medical institution that has requested the acceptance of the emergency. The notification date and time is an area for storing the date and time when the acceptance of the emergency request is requested. The item of status is an area for storing information indicating the status of the request. In the item of the status, "notifying" is stored when requesting acceptance of a first aid, and "not accepted" is stored when an unacceptable response is received. The item of reason is an area for storing information indicating an unacceptable reason when an unacceptable answer is received. The item of patient information browsing is an area for storing the setting as to whether the personal information of the patient can be browsed at the request destination for acceptance of the first aid. In the item of patient information browsing, “OK” is stored when browsing personal information of a patient is enabled, and “Impossible” is stored when browsing personal information of a patient is disabled.

  In the example of FIG. 13, the disaster number “0001” is requesting the medical institution of the medical institution code “M14” to accept the emergency as the request number “1”, and the situation is in the notification of acceptance of the emergency. Indicates that there is.

  Returning to FIG. 2, the control unit 22 is a device that controls the browsing control device 11. As the control unit 22, an electronic circuit such as a central processing unit (CPU) or a micro processing unit (MPU) or an integrated circuit such as an application specific integrated circuit (ASIC) or a field programmable gate array (FPGA) can be adopted. The control unit 22 has an internal memory for storing programs and control data which define various processing procedures, and executes various processing by these.

  The control unit 22 functions as various processing units when various programs operate. For example, the control unit 22 includes a receiving unit 50 and a setting unit 51. In the present embodiment, the reception unit 50 corresponds to the transmission unit.

  The receiving unit 50 receives various operations. For example, when receiving the access, the receiving unit 50 transmits information on various operation screens to the access source, displays the operation screen on the access source, and receives various operations from the operation screen. For example, the reception unit 50 provides a web site of a system that shares information on medical care of a patient. When receiving an access from the terminal device 14 to a website of a system sharing information on medical care of a patient from the terminal device 14, the reception unit 50 transmits information on the login screen to the terminal device 14 of the access source to display the login screen. Enter login ID and password and accept login operation. When accepting the login operation, the accepting unit 50 performs authentication by comparing the entered login ID and password with the login ID and password registered in advance. When the authentication with the legitimacy is obtained, the reception unit 50 transmits the information of the operation screen for registering the information on the medical care of the patient to the terminal device 14 of the access source to display the operation screen, and Accept registration. The doctor and pharmacist of the patient's family register information on the patient's medical care, such as the patient's daily living condition and behavior characteristics, from the operation screen using the terminal device 14. The reception unit 50 stores the registered information in the medical care information 32.

  In addition, when receiving the access from the emergency support software of the terminal device 12, the reception unit 50 transmits information of various operation screens to the access source, and causes the various operation screens to be displayed via the emergency support software, and the operation is performed. Accept various operations from the screen. For example, the reception unit 50 transmits information of the login screen for the rescue team to the terminal device 12 of the access source to display the login screen on the terminal device 12, and receives the login operation by inputting the rescue team code. The receiving unit 50 may receive a login operation by inputting a login ID and a password, and may perform authentication in comparison with the login ID and password registered in advance. When the login is performed, the reception unit 50 transmits information of various operation screens for the rescue team to the terminal device 12 of the access source to display various operation screens, and receives registration of various information.

  FIG. 14A is a diagram illustrating an example of an operation screen for a rescue team. The example of FIG. 14A shows an example of the operation screen for the rescue team displayed on the terminal device 12 after login. The operation screen 100 has an upper header portion 101, a lower footer portion 102, and a central content area portion 103.

  The header portion 101 includes an add button 110 instructing addition of a patient, a delete button 111 deleting a patient, a display area 112 displaying a patient registration number, and a display area 113 displaying a fire department to which a fire brigade belongs. Have.

  In the footer portion 102, a plurality of buttons 120 are arranged, and a logout button 120A and a transport destination selection button 120B are provided.

  The display area of the content area portion 103 can be switched by the tab 130. The example of FIG. 14A shows the operation screen 100 in a state where the tab 130 of “participation information” is selected. As shown in FIG. 14A, the content area portion 103 of the operation screen 100 has a disaster number area 140 for displaying a disaster number, an occurrence place area 141 for inputting an occurrence place, and a date and time area 142 for inputting date and time.

  The disaster number area 140 displays a disaster number. The disaster number is automatically numbered sequentially in each predetermined management unit, such as every emergency team or every fire department. In addition, the disaster number may be automatically numbered by the numbering operation of the fire brigade. In addition, the disaster number area 140 may be input, and the emergency number may be input by the rescue team. In the occurrence place area 141, the place where the disaster occurred is input. For example, on the operation screen 100, when an area where input can be made is selected, a software keyboard which can input characters and numbers such as flick input is displayed, for example, and characters and numbers can be input. In the date and time area 142, the local arrival date and time is input. In addition, the area | region which can be input may present a candidate by a list box etc., and it is good also as input possible by selection. For example, the occurrence place area 141 may be able to input the occurrence place by selection with a list box or the like. For example, a list box is provided for each address area, such as a municipality or a town. Then, when the upper area list box is selected, candidates corresponding to the selected upper area may be presented in the lower area list box to be selectable. Further, the occurrence location area 141 may be provided with a current position button for inputting the current position, specify the current position when the current position button is pressed by GPS or the like, and may automatically input from the specified current position. The date and time area 142 may also be able to input the date and time by selection with a list box or the like. The date and time area 142 may also be provided with a current date and time button for inputting the current date and time, and the system date and time when the current date and time button is pressed may be automatically input.

  When the ambulance arrives at the site where the emergency is requested, it selects the tab 130 of "participant information" of the operation screen 100 using the terminal device 12, enters the local arrival date and time in the date and time area 142, and generates the occurrence place area Enter the place where the disaster occurred in 141.

  The reception unit 50 generates a disaster from the disaster number displayed in the disaster number area 140, the fire brigade code of the fire brigade, the local arrival date and time inputted in the date and time area 142, and the occurrence place inputted in the occurrence place area 141. It stores in information 35.

  FIG. 14B is a diagram illustrating an example of an operation screen for a rescue team. The example of FIG. 14B shows the content area portion 103 with the tab 130 of “Patient Basic Information” selected. As shown in FIG. 14B, the content area portion 103 of the operation screen 100 has a card read button 150, a card number input area 151 for inputting a patient NO, and a send button 152. In the content area portion 103 of the operation screen 100, a name area 153 for inputting the patient's name, a reading area 154 for inputting the patient's reading, an address area 155 for inputting the patient's address, and a telephone number of the patient And a telephone number area 156 to be input. The content area portion 103 of the operation screen 100 has a sex area 157 for selecting the gender of the patient, and a birth date area 158 for inputting the year, year, month, and day of the patient's birth date.

  When the card reading button 150 is selected, imaging of the image by the camera is started, and when the code image is recognized in the captured image, the code image is decoded and the patient NO is read out. The read out patient number is displayed in the card number input area 151. The patient NO may be input into the card number input area 151 manually. When the send button 152 is selected, the registered patient information 31 is searched by the patient NO displayed in the card number input area 151, and the same patient NO is registered in the registered patient information 31. Information on the patient of patient NO is displayed in the content area portion 103 of the operation screen 100.

  When the patient has a card on which the code image of the patient NO is described, the rescue team reads the code image of the card and inputs information on the patient. FIG. 14C is a diagram showing an example of the operation screen for the rescue team in which the information on the patient is input. The example of FIG. 14C shows an example of displaying information on the patient of patient NO “9999”. The name area 153, the address area 155, the address area 155, the telephone number area 156, the sex area 157, and the date of birth area 158 are the names of patients with patient NO "9999" in the registered patient information 31 shown in FIG. , Address, phone number, gender, date of birth are displayed.

  On the other hand, when the patient does not have a card in which the code image of the patient NO is described, the rescue team inputs in the operation screen 100 within a range where the patient's name, kana, address, phone number, gender, date of birth can be known .

  In addition, when registering a plurality of patients, the rescue team selects the add button 110 on the operation screen 100. In the operation screen 100, when the addition button 110 is selected, the patient registration number is added to the display area 112, and registration of patient information of the registration number becomes possible. FIG. 14D is a diagram showing an example of the operation screen for the rescue team when registering a plurality of patients. In the example of FIG. 14D, the patient registration number "2" is added to the display area 112, and it becomes possible to input information about the patient with the registration number "2". By selecting the registration number displayed in the display area 112, the operation screen 100 can switch the patient for which information is to be registered.

  The reception unit 50 stores the patient NO, patient's name, address, phone number, gender, date of birth, and the patient's name input on the operation screen 100 in the transfer patient information 36 together with the disaster number and the patient registration number.

  In the operation screen 100, when a patient is registered and a patient is registered, a tab 130 of "patient medical care information" is additionally displayed. FIG. 14E is a diagram showing an example of the operation screen for the rescue team on which a tab of patient medical treatment information is displayed. The example of FIG. 14E shows the operation screen 100 in a state where the selection of the tab 130 of “patient medical care information” is selected. As shown in FIG. 14E, the content area portion 103 of the operation screen 100 has an emergency introduction destination area 160 for displaying an emergency introduction destination, and a past medical care information area 161 for displaying past medical care information.

  The emergency referral destination area 160 displays the name of the medical institution to which the referral destination in the emergency is registered corresponding to the patient of the patient NO. In the medical care information area 161, the name of each medical institution who has treated the patient of the patient NO is displayed on the tab 162, and the information on medical care obtained by having a medical examination at each medical institution can be switched and displayed by the tab 162 . The reception unit 50 reads out from the emergency introduction destination information 33 the medical institution code stored corresponding to the patient NO of the patient. The reception unit 50 reads out the medical institution name corresponding to the medical institution code from the medical institution information 30 and causes the emergency introduction destination area 160 to display the medical institution name. Further, the reception unit 50 reads out, from the medical care information 32, information on each medical institution code and medical care stored corresponding to the patient NO of the patient. Then, the reception unit 50 reads out the medical institution name corresponding to the medical institution code from the medical institution information 30 and displays it on the tab 162 of the medical care information area 161, and the tab 162 selects information about medical care registered at each medical institution. Display switchable. In the example of FIG. 14E, in the medical care information area 161, the condition of the diet, nutrition route, and excretion of the patient NO “9999” registered by the AA hospital is displayed.

  By selecting the tab 130 of “Patient medical care information” on the operation screen 100, the rescue team can grasp the medical institution of the emergency introduction destination desired by the patient and the past medical care information.

  FIG. 14F is a diagram illustrating an example of an operation screen for a rescue team. The example of FIG. 14F shows the content area portion 103 with the “physiological evaluation” tab 130 selected. As shown in FIG. 14F, in the content area portion 103 of the operation screen 100, the tab 170 enables inputting of measurement results of a plurality of physiological evaluations, and has a measurement result area 171 for inputting the measurement result. The tab 170 is displayed for inputting the next measurement result when the input of the measurement result is completed. For example, in the tab 170, the first time is displayed in the initial state, and the second time is displayed when the first input is completed.

  The measurement result area 171 has an elapsed time area 172 for inputting an elapsed time, a JCS area 173 for inputting JCS, a GCS area 174 for inputting GCS, and a respiratory rate area 175 for inputting a respiratory rate. Further, the measurement result area 171 has a pulse rate area 176 for inputting a pulse rate, a blood pressure area 177 for inputting a blood pressure, and an SPO2 area 178 for inputting a percutaneous arterial blood oxygen saturation concentration.

  The rescue team measures the patient's JCS, GCS, respiration rate, pulse rate, blood pressure rate, and percutaneous arterial blood oxygen saturation concentration, and uses the terminal device 12 to display the tab 130 of the “physiological evaluation” on the operation screen 100. Select and enter the measurement results.

  The reception unit 50 receives the patient's JCS, GCS, respiration rate, pulse rate, blood pressure number, percutaneous arterial blood oxygen saturation concentration, disaster number, emergency team code of the emergency team, patient registration number, which is input on the operation screen 100. , And stored in the physiological evaluation information 37 together with the measurement number.

  In addition, the operation screen 100 allows the user to enter the patient's condition and medical condition by selecting the "condition / medical condition" tab 130, and the medical treatment which the patient visits by selecting the "medical department" tab 130. You can enter a family.

  The paramedics use the terminal 12 to select the tab 130 of "condition / condition" on the operation screen 100, enter the condition of the patient and the condition, and select the tab 130 of "medical department" on the operation screen 100. Then enter the patient's department.

  The reception unit 50 stores the condition, medical condition, and medical department of the patient input on the operation screen 100 in the medical condition information 38 together with the disaster number, the emergency team code of the emergency team, and the registration number of the patient.

  FIG. 15A is a diagram illustrating an example of an operation screen for a rescue team. The example of FIG. 15A shows an operation screen in a state where the transport destination selection button 120B is selected. As shown in FIG. 15A, the footer portion 102 of the operation screen 100 is provided with a logout button 120A and a patient information input button 120C. When the patient information input button 120C is selected, the operation screen 100 shown in FIG. 14B is displayed.

  As shown in FIG. 15A, the content area portion 103 of the operation screen 100 displays a patient information area 180 in which information registered about the patient from the operation screen 100 is displayed, and a medical institution displaying candidates for the medical institution of the transfer destination. A transport / correspondence information area 181 is provided.

  The patient information area 180 displays various information registered from the operation screen 100 regarding the patient. In the example of FIG. 15A, the patient's name of patient NO "9999", reading, gender, date of birth, age, address, and telephone number are displayed.

  In the medical institution conveyance / correspondence information area 181, the tab 182 of “emergency introduction destination”, “medical institution frequently used”, and “other” is displayed, and the medical institution as a candidate of the conveyance destination is switched and displayed by the tab 182 It is made possible. The example of FIG. 15A shows the medical institution conveyance / correspondence information area 181 in a state where the tab 182 of “emergency introduction destination” is selected.

  The medical institution conveyance / correspondence information area 181 displays the name and location of the medical institution registered as the emergency referral destination of the registered patient, and information on whether the medical institution can accept an emergency or not. The reception unit 50 reads out the medical institution code stored in correspondence with the patient NO of the patient from the emergency introduction destination information 33 in the order of the registration number. Then, the reception unit 50 reads out the medical institution name and the location area corresponding to the medical institution code from the medical institution information 30, and causes the medical institution conveyance / correspondence information area 181 to display the same. Further, the reception unit 50 reads out from the reception registration information 34 the registration information stored corresponding to the medical institution code. Then, the reception unit 50 displays whether or not the emergency can be accepted according to the registration information. In the example of FIG. 15A, the medical institutions to which the patient of the patient number “9999” of the registration number “1” is transported as an emergency are displayed as the injured person 1. Further, in the example of FIG. 15A, “pre-acceptable stated in progress” is displayed for a medical institution that has indicated that it is possible to receive an emergency, and “pre-accepted for a medical institution that has indicated that it is not possible to receive an emergency. "Not asserted" is displayed.

  FIG. 15B is a diagram illustrating an example of an operation screen for a rescue team. The example of FIG. 15B shows the medical institution conveyance / correspondence information area 181 in a state where the tab 182 of “Medical medical institution frequently used” is selected.

  The medical institution conveyance / correspondence information area 181 displays the name and location area of the medical institution frequently used by the emergency services in the emergency and information on whether the medical institution can accept the emergency. The reception unit 50 reads out the medical institution code stored in correspondence with the ambulance corps code of the paramedics from the used medical institution information 39 in the order of the rank. Then, the reception unit 50 reads out the medical institution name and the location area corresponding to the medical institution code from the medical institution information 30, and causes the medical institution conveyance / correspondence information area 181 to display the same. Further, the reception unit 50 reads out from the reception registration information 34 the registration information stored corresponding to the medical institution code. Then, the reception unit 50 displays whether or not the emergency can be accepted according to the registration information. In the example of FIG. 15B, a medical institution with a high frequency of use of the rescue team with the rescue team code “T001” is displayed. Further, in the example of FIG. 15B, “pre-acceptable stated in progress” is displayed for a medical institution that has indicated that it is possible to receive an emergency.

  FIG. 15C is a diagram showing an example of an operation screen for a rescue team. The example of FIG. 15C shows the medical institution transport / correspondence information area 181 with the “others” tab 182 selected.

  The medical institution conveyance / correspondence information area 181 displays the name and location of the medical institution capable of responding to the emergency and information on whether the medical institution can accept the emergency. The reception unit 50 reads out the medical institution code, the medical institution name, and the location area of the medical institution where the item for emergency response is “Y” from the medical institution information 30, and causes the medical institution conveyance / correspondence information area 181 to display. In the medical institution conveyance / correspondence information area 181, it is possible to select a location ward, designate a medical institution name, and narrow down the medical institution with the Japanese syllabary by "A" to "W".

  The rescue team operates the tab 182 of the medical institution conveyance / correspondence information area 181 of the operation screen 100 using the terminal device 12 and selects a candidate medical institution of a patient's emergency conveyance destination from among the displayed medical institutions. . The rescue team contacts the selected destination medical institution using a communication means such as a mobile phone to request the patient's acceptance. In addition, the rescue team selects a candidate medical institution of the selected transport destination from the medical institution transport / correspondence information area 181.

  When a medical institution is selected in the medical institution conveyance / correspondence information area 181 of the operation screen 100, the reception unit 50 displays a transmission screen of patient information.

  FIG. 16A is a diagram illustrating an example of the transmission screen. The transmission screen 200 has a target patient area 201 in which information on a target patient to be transmitted is displayed. In the example of FIG. 16A, the patient's name of patient NO "9999", reading, gender, date of birth, age, address, and telephone number are displayed. The transmission screen 200 also has a medical institution notification button 202, a transfer destination confirmation button 203, an unacceptable button 204, and a close button 205.

  The medical institution notification button 202 is a button for instructing transmission of patient information to a medical institution of a transfer destination candidate. The transfer destination confirmation button 203 is a button for instructing determination as a transfer destination of the patient as a candidate medical destination of the transfer destination. The non-acceptance button 204 is a button for recording that the candidate medical institution of the transfer destination receives an unacceptable response. The close button 205 is a button for closing the transmission screen 200 and returning to the operation screen 100.

  The emergency team selects the medical institution notification button 202 when transmitting patient information to the candidate medical institutions of the transfer destination. As a result, patient information can be browsed at the medical institution of the transfer destination candidate. The candidate medical institution to which the information is to be transferred refers to the patient information, determines whether the patient is accepted, and answers the rescue team. For example, the candidate medical institutions of the transfer destination respond to the rescue team using a communication means such as a mobile phone. The rescue team selects the transfer destination confirmation button 203 when the answer is acceptable. On the other hand, the rescue team selects the non-acceptable button 204 when the response is received as unacceptable. The emergency team selects the close button 205 when changing the medical institution of the transport destination candidate without transmitting the patient information.

  When the non-acceptance button 204 of the transmission screen 200 is selected, the accepting unit 50 displays a reason input screen.

  FIG. 16B is a diagram showing an example of the reason input screen. The reason input screen 210 is a screen on which a plurality of acceptance rejection reason candidates that can be arbitrarily set are displayed, and the reason for acceptance rejection is selected by selection. The reason input screen 210 has an in-operation / patient-related button 211, a bed full button 212, a doctor absent button 213, and an unknown reason 214.

  In response to the reason that the emergency services were not accepted at the medical institution of the transfer destination, from the reason input screen 210, the in-operation / patient-ready button 211, the bed full button 212, the doctor absence button 213, the reason Select one of unknown 214.

  When the reason is selected from the reason input screen 210, the receiving unit 50 displays the operation screen 100 shown in FIG. 15A. The rescue team again selects a candidate medical institution to which the patient is to be delivered urgently.

  The setting unit 51 performs various settings. The setting unit 51 includes a first setting unit 51A and a second setting unit 51B.

  When the first setting unit 51A selects a candidate medical institution for an emergency delivery destination of a patient, the first setting unit 51A allows the medical institution for a candidate for an emergency delivery destination of the patient to set permission for viewing of personal information of the patient. Do. For example, when the medical institution notification button 202 is selected on the transmission screen 200, the first setting unit 51A treats the medical care of the candidate of the emergency transport destination of the patient currently selected on the medical institution transport / correspondence information area 181 of the operation screen 100. Make settings to allow or disallow the viewing of patient's personal information at the institution. For example, the first setting unit 51A sets the medical institution code of the candidate medical institution of the emergency transfer destination of the patient as the notification destination, sets the item of the condition as “notifying”, and sets the item of patient information browsing as “possible”. The item of "-" is stored in the transport request status information 40 together with the disaster disaster number and the request number, with the current date and time as the notification date and time. The example of FIG. 13 shows a state where the medical institution code “M14” is requested to accept the patient of the disaster number “0001”, and browsing of the patient's personal information is enabled.

  The second setting unit 51B sets a reason why acceptance is not possible when acceptance is not possible at a candidate medical institution of a patient's emergency transfer destination. For example, when the second setting unit 51B selects a reason from the reason input screen 210, the transportation request status corresponding to the disaster number of the disaster and the medical institution code of the candidate medical institution of the emergency transportation destination of the currently selected patient. The item of the status of the record of the information 40 is updated to "not acceptable", and the selected reason is stored in the item of reason.

  In addition, when the medical institution notification button 202 is selected on the transmission screen 200 after the setting by the first setting unit 51A, the second setting unit 51B allows viewing of personal information whose browsing is permitted in the first setting unit 51A. Make settings to disable the permission setting. For example, when the medical institution notification button 202 is selected on the transmission screen 200, the second setting unit 51B browses the patient's personal information at a medical institution other than the medical institution that is the candidate of the emergency transport destination of the currently selected patient. Make settings to disable the setting of. For example, the second setting unit 51B browses the patient information of the record of the transportation request status information 40 corresponding to the medical institution code of the medical institution other than the disaster medical number of the disaster disaster number and the candidate emergency transportation destination of the currently selected patient. Update the item of to "No".

  FIG. 17 is a diagram showing an example of a change in conveyance request status information. (A) of FIG. 17 shows before change of the transfer request status information 40, and (B) shows after change of the transfer request status information 40. As shown in FIG. Request for acceptance of the patient with disaster number "0001" to medical institution code "M14" and acceptance is denied, and request for acceptance of the patient with disaster number "0001" to medical institution code "M15", transportation request status information 40 changes as shown in FIG. In the example of FIG. 17, since the medical institution code “M14” can not be accepted, the item of the status is updated from “notifying” to “not acceptable”, and the reason is stored in the item of reason. Further, the item of patient information browsing of the medical institution code “M14” is updated from “OK” to “NO”.

  The reception unit 50 provides a Web site of a system that provides information on an emergency patient to a medical institution capable of responding to an emergency. When receiving the access to the website of the system providing the information of the emergency patient from the terminal device 13, the receiving unit 50 transmits the information of the login screen to display the login screen, and inputs the login ID and the password. Accept login operation. When accepting the login operation, the accepting unit 50 performs authentication by comparing the entered login ID and password with the login ID and password registered in advance. The reception unit 50 requests the medical institution that has logged in to accept the request when the authentication with the legitimacy is obtained, and transmits the information of the patient who can be browsed to the request for acceptance of the emergency and requested the request. Display a browsing screen for browsing patient information.

  FIG. 18A is a diagram illustrating an example of a browsing screen. The viewing screen 250 includes a request source area 251 displayed by the request source, a patient area 252 displaying information of the patient, a medical condition area 253 displaying the medical condition of the patient, and a physiological evaluation area 254 displaying the physiological evaluation of the patient. Have.

  In the request source area 251, information of the rescue team who requested the acceptance and the number of the requested patients are displayed. The patient area 252 displays the patient's name, reading, gender, date of birth, age, address, and telephone number. In the patient area 252, when the patient NO is registered, the patient NO and the link button 255 are displayed. In the example of FIG. 18A, the link button 255 is displayed because the patient NO is registered. The medical condition area 253 displays the medical condition of the requested patient. The physiological evaluation area 254 displays the measurement results of the physiological evaluation divided into tabs according to the number of times of measurement. When the link button 255 is selected, information on the patient of patient NO is displayed. For example, when the link button 255 is selected, the reception unit 50 displays, on another screen, information related to the medical care of the patient registered from the medical facilities which the patient visits daily, which is stored in the medical care information 32.

  In a medical institution capable of responding to an emergency, the terminal device 13 accesses the website of a system providing information on an emergency patient at a predetermined timing such as every fixed period, and confirms the browsing screen 250. Information on the requested patient is displayed on the viewing screen 250 of the terminal device 13 of the medical institution that has been requested to receive the patient from the emergency services. For example, when acceptance of a patient is requested by the emergency services from the LL hospital of the medical institution code "M14" and the transportation request status information 40 is shown in FIG. 13, the browsing screen 250 shown in FIG. Be done. The medical institution requested to accept the patient determines whether to accept the requested patient. At this time, the browsing screen 250 displays information of the requested patient. Further, when the link button 255 is selected, information on the medical care of the patient registered from each medical institution which the patient visits on a daily basis is displayed on another screen. As a result, the medical institution requested to receive the patient understands the condition of the patient registered by the emergency services and the daily condition of the patient by the general doctor, pharmacist, etc. It can be judged. When the MM hospital refuses to accept and the emergency services request the NN hospital of the medical institution code “M15” to accept the patient, the transfer request status information 40 changes as shown in FIG. 17, and the medical institution code “M14” Item of patient information reading of has been updated from "OK" to "NO". As a result, in the LL hospital, the patient information requested to be accepted is not displayed on the terminal device 13. FIG. 18B is a diagram illustrating an example of a browsing screen. When the delivery request status information 40 is in the state shown in FIG. 17B, the information on the patient is not displayed on the browsing screen 250 as shown in FIG. 18B. As described above, when the terminal device 13 of the medical institution requested to accept the patient declines the acceptance of the requested patient, the personal information of the requested patient can not be viewed. It can protect.

  Next, the flow of browsing control by the system 10 according to the present embodiment will be described. FIG. 19 is a flowchart showing an example of the flow of browsing control.

  As shown in FIG. 19, in the terminal device 12, the emergency support software accesses the browsing control device 11 and requests an operation screen (S 10). When the browsing control device 11 receives an access from the emergency assistance software of the terminal device 12, the browsing control device 11 transmits information of various operation screens to the access source (S11). The terminal device 12 displays the information of the operation screen (S13). The terminal device 12 receives input of information on the operation screen. For example, the terminal device 12 receives an input of information on a patient on the operation screen 100 (S14). When the transmission button 152 of the operation screen 100 is selected, the terminal device 12 transmits the patient NO input in the card number input area 151. The browsing control device 11 searches the registered patient information 31 by the transmitted patient NO, and when the same patient NO is registered in the registered patient information 31, information on the patient of the same patient NO is sent to the terminal device 12 It transmits and displays in the content area part 103 of the operation screen 100 (S15).

  In the terminal device 12, a medical institution is selected in the medical institution conveyance / correspondence information area 181 of the operation screen 100, and when the medical institution notification button 202 is selected on the transmission screen 200, acceptance of the selected medical institution is requested. (S16). When a candidate medical institution of an emergency transfer destination of a patient is selected, the terminal device 12 performs setting for enabling or disabling the browsing of the personal information of the patient at the medical institution of a candidate of the emergency transport destination of the patient S17). When the medical institution notification button 202 is selected on the transmission screen 200 after the setting by the first setting unit 51A, the second setting unit 51B searches for the transportation request status information 40 by the disaster number corresponding to the emergency currently being processed. Then, it is determined whether a medical institution other than the medical institution as a candidate for the emergency transfer destination of the currently selected patient is requested to accept the patient (S18). When the acceptance of the patient is requested (S18 affirmation), the browsing control device 11 corresponds to the medical institution code of the medical institution other than the medical institution of the candidate of the disaster number of the disaster and the emergency destination of the currently selected patient. The item of patient information browsing of the record of the transfer request status information 40 is updated to "impossible" (S19).

  In a medical institution capable of responding to an emergency, the terminal device 13 accesses a website of a system providing information on an emergency patient at a predetermined timing such as every fixed period (S20). The browsing control device 11 requests the medical institution of the access source to accept the request, and transmits the information of the browsing screen 250 on which the information on the patient who can be browsed to the request destination is displayed (S21). . The terminal device 13 displays the browsing screen 250 (S22). The browsing screen 250 displays the information of the patient who can be browsed, and the information of the patient who can not be browsed is not displayed. As a result, in the present embodiment, if the hospital requesting the patient's acceptance does not accept the patient, the patient's personal information can not be viewed if the other hospital requests the transfer. Can protect personal information.

  As described above, the browsing control device 11 according to the present embodiment refers to the storage unit 21 that stores personal information including emergency transport destination candidates in association with patient NO in response to a personal information acquisition request based on patient NO. Then, the personal information including the urgent transfer destination candidate corresponding to the patient No. is transmitted to the terminal device 12 which is the request source of the acquisition request. When the first emergency transfer destination is selected in the terminal 12 from among the emergency transfer destination candidates, the reading control device 11 can view personal information corresponding to the patient NO by the terminal device 13 of the first emergency transfer destination. Make settings to enable or disable. When the second emergency destination among the emergency destination candidates is selected in the terminal device 12 after the setting, the reading control device 11 selects personal information corresponding to the patient NO by the terminal device 13 of the first emergency destination. Make settings to disable browsing permission settings. Thereby, the browsing control apparatus 11 can protect personal information.

  Moreover, the browsing control apparatus 11 which concerns on a present Example makes an emergency conveyance destination candidate a hospital. As a result, the browsing control device 11 can once become an emergency delivery destination candidate and protect the patient's personal information for the hospital that has not accepted the patient.

  Further, when the first emergency destination is selected, the browsing control device 11 according to the present embodiment sends the patient NO and the patient NO to the terminal device 13 of the first emergency destination from the terminal device 12 of the request source. A part of the corresponding personal information is transmitted via the browsing control device 11. As a result, since the personal information to be conveyed can be grasped at the first emergency conveyance destination, it can be appropriately determined whether the patient can be accepted.

  In addition, the browse control device 11 according to the present embodiment is a request for obtaining information of unacceptable for the first emergency destination, when unacceptable information is input in the first emergency destination terminal device 13. It transmits to the terminal device 12 of request origin. Thereby, the reading control apparatus 11 can indicate in advance that the patient can not be accepted for the medical institution which has stated that the acceptance of the emergency is not possible.

  Although the embodiments of the disclosed apparatus have been described above, the disclosed technology may be implemented in various different forms other than the above-described embodiments. Therefore, another embodiment included in the present invention will be described below.

  For example, in the above embodiment, when the next emergency destination is selected, the case where the information on the target patient in the previous emergency destination is not browsed is described as an example. It is not limited. For example, when the selection of the emergency transfer destination is canceled or the non-transferable input to the emergency transfer destination is made, the information of the target patient at the emergency transfer destination may be set to be unviewable. For example, when the second setting unit 51B selects the non-acceptance button 204 on the transmission screen 200, the second setting unit 51B does not allow the setting of the personal information browsing of the patient to be disabled at the medical institution of the transfer destination. Good. This makes it possible to protect the patient's personal information because the patient's personal information can not be viewed if the patient's acceptance is not accepted in the hospital that has requested the patient's acceptance.

  In the above embodiment, the medical institution transport / response information area 181 of the operation screen 100 displays the information of acceptance / rejection shown in advance by the medical institution as an example. It is not limited. For example, first aid acceptance information of each medical institution may be displayed in the medical institution conveyance / correspondence information area 181 of the operation screen 100. For example, the reception unit 50 reads the status of the medical institution from the transportation request status information 40 using the medical institution code. Then, the reception unit 50 displays information on the status of the newest request among the statuses of the requests registered within a predetermined period from the present on the notification date and time. For example, when unacceptable information is input, the accepting unit 50 can not accept information regarding unacceptable emergency transportation destinations for a predetermined period by transmitting the unacceptable information to the terminal device 12 of another rescue team. Indicate that there has been an assertion. The predetermined period is, for example, four hours. The predetermined period may be changeable. Thereby, the reading control apparatus 11 can share the information on the unacceptable emergency destination with other emergency services. FIG. 20 is a diagram showing an example of the operation screen for the rescue team. In the example of FIG. 20, when the transport request status information 40 is in the state shown in FIG. 17B, the medical institution transport / correspondence information area 181 in a state in which the tab 182 of “medical institution frequently used” is selected. It shows. In the example of FIG. 20, LL hospital with the medical institution code “M14” indicates that the patient acceptance has occurred. Also, the MM hospital with the medical institution code "M15" indicates that the patient acceptance is requested. The reception unit 50 may display the notification date and time or the reason in the medical institution conveyance / correspondence information area 181 when the patient can not accept it.

  Further, although the above embodiment has been described by way of an example in which information regarding the patient's medical care can be browsed to the medical institution requested to receive the patient, the disclosed apparatus is not limited to this. Information on patient care may include information that the patient does not want to disclose. Therefore, the scope of disclosure may be limited. For example, only the medical institution that has registered information on the medical care of the patient may be able to view the information on the medical care of the patient. For example, when the link button 255 is selected, the reception unit 50 may read out from the medical care information 32 only the information on the medical care of the patient registered from the medical institution of the access source and display it. For each piece of information on the medical care of the patient, only the information on the viewable medical information may be displayed for the viewable medical institution, with the viewability or the viewable medical institution being specifiable.

  Further, each component of each device illustrated is functionally conceptual, and does not necessarily have to be physically configured as illustrated. That is, the specific state of dispersion and integration of each device is not limited to that shown in the drawings, and all or part thereof is functionally or physically dispersed in any unit depending on various loads, usage conditions, etc. It can be integrated and configured. For example, the processing units of the reception unit 50 and the setting unit 51 (the first setting unit 51A and the second setting unit 51B) of the browsing control device 11 may be appropriately integrated. Further, for example, the receiving unit 50 may be divided into a plurality of processing units depending on functions, such as a transmitting unit that transmits various data such as screen data, and a storage unit that stores data in the storage unit 21. Furthermore, all or any part of each processing function performed in each processing unit may be realized by a CPU and a program analyzed and executed by the CPU, or may be realized as hardware by wired logic. .

[Reading control program]
The various processes described in the above embodiments can also be realized by executing a prepared program on a computer system such as a personal computer or a workstation. So, below, an example of a computer system which runs a program which has the same function as the above-mentioned example is explained. FIG. 21 is a diagram illustrating an example of a computer that executes a browsing control program.

  As shown in FIG. 21, the computer 300 includes a central processing unit (CPU) 310, a hard disk drive (HDD) 320, and a random access memory (RAM) 340. The respective units 300 to 340 are connected via a bus 400.

  In the HDD 320, a browsing control program 320A that exhibits the same function as the reception unit 50 and the setting unit 51 (the first setting unit 51A and the second setting unit 51B) is stored in advance. The browsing control program 320A may be separated as appropriate.

  The HDD 320 also stores various information. For example, the HDD 320 stores an OS and various data used for various processes.

  Then, the CPU 310 reads the browsing control program 320A from the HDD 320 and executes the same to execute the same operation as each processing unit of the embodiment. That is, the browsing control program 320A executes the same operation as the receiving unit 50 and the setting unit 51 (the first setting unit 51A, the second setting unit 51B).

  The above-described browsing control program 320A does not necessarily have to be stored in the HDD 320 from the beginning.

  Also, for example, the viewing control program 320A may store the program in a “portable physical medium” such as a CD-ROM, a DVD disc, a magneto-optical disc, an IC card or the like inserted into the computer 300. Then, the computer 300 may read and execute programs from these.

  Furthermore, the program is stored in “another computer (or server)” connected to the computer 300 via a public line, the Internet, a LAN, a WAN or the like. Then, the computer 300 may read and execute programs from these.

DESCRIPTION OF SYMBOLS 10 system 11 reading control apparatus 12 terminal apparatus 13 terminal apparatus 14 terminal apparatus 21 memory part 22 control part 30 medical institution information 31 registered patient information 32 medical treatment information 33 emergency referral information 34 acceptance registration information 35 outbreak disaster information 36 conveyance patient information 37 Physiological evaluation information 38 Medical condition information 39 Use medical institution information 40 Transfer request status information 50 Acceptance unit 51 Setting unit 51A First setting unit 52A Second setting unit

Claims (10)

In response to an acquisition request for personal information based on the first identification information, the emergency conveyance corresponding to the first identification information is referenced with reference to a storage unit that stores personal information including emergency transport destination candidates in association with the identification information. Sending personal information including the candidate to the terminal of the request source of the acquisition request,
When the first emergency destination is selected in the terminal among the emergency destination candidates, the terminal of the first emergency destination can set permission to view personal information corresponding to the first identification information. Make settings to
After the setting, when a second emergency destination among the emergency destination candidates is selected in the terminal, browsing of personal information corresponding to the first identification information by the first emergency destination terminal is performed. Make settings to disable the permission setting,
And a computer-implemented browsing control method.   The browsing control method according to claim 1, wherein the emergency delivery destination candidate is a hospital.   When the first emergency destination is selected, a part of personal information corresponding to the first identification information and the first identification information from the request source terminal to the first emergency destination terminal 3. The browsing control method according to claim 1 or 2, wherein   The terminal of the request source of the request for acquisition of other personal information for the information of impossibility for the first emergency destination, when the information on the first emergency destination is not accepted at the terminal of the request source. The browsing control method according to claim 1, wherein the browsing control method is transmitted to the client.   When unacceptable information is input in the first emergency destination terminal, personal information including an emergency destination candidate corresponding to the first identification information is transmitted to the acquisition request request source terminal 2. The view control method according to claim 1, wherein, when the first emergency transfer destination is received, information unacceptable to the acquisition request is sent to the terminal requesting the acquisition request. In response to an acquisition request for personal information based on the first identification information, the emergency conveyance corresponding to the first identification information is referenced with reference to a storage unit that stores personal information including emergency transport destination candidates in association with the identification information. Sending personal information including the candidate to the terminal of the request source of the acquisition request,
When the first emergency destination is selected in the terminal among the emergency destination candidates, the terminal of the first emergency destination can set permission to view personal information corresponding to the first identification information. Make settings to
After the setting, when a second emergency destination among the emergency destination candidates is selected in the terminal, browsing of personal information corresponding to the first identification information by the first emergency destination terminal is performed. Make settings to disable the permission setting,
A browsing control program that causes a computer to execute a process. In response to an acquisition request for personal information based on the first identification information, the emergency conveyance corresponding to the first identification information is referenced with reference to a storage unit that stores personal information including emergency transport destination candidates in association with the identification information. A transmitting unit for transmitting personal information including a destination candidate to a terminal as a request source of the acquisition request;
When the first emergency destination is selected in the terminal among the emergency destination candidates, the terminal of the first emergency destination can set permission to view personal information corresponding to the first identification information. A first setting unit for setting to
After the setting by the first setting unit, when the second emergency destination among the emergency destination candidates is selected in the terminal, the first identification information by the first emergency destination terminal is handled. A second setting unit configured to disable setting of permission to view personal information to be
A browsing control device characterized by having. In response to an acquisition request for personal information based on the first identification information, the emergency conveyance corresponding to the first identification information is referenced with reference to a storage unit that stores personal information including emergency transport destination candidates in association with the identification information. Sending personal information including the candidate to the terminal of the request source of the acquisition request,
When the first emergency destination is selected in the terminal among the emergency destination candidates, the terminal of the first emergency destination can set permission to view personal information corresponding to the first identification information. Make settings to
After the setting, when the selection of the first emergency destination is canceled or the input of non-conveyance to the first emergency destination is made, the first identification information by the terminal of the first emergency destination. Make settings to disable browsing of personal information corresponding to
And a computer-implemented browsing control method. In response to an acquisition request for personal information based on the first identification information, the emergency conveyance corresponding to the first identification information is referenced with reference to a storage unit that stores personal information including emergency transport destination candidates in association with the identification information. Sending personal information including the candidate to the terminal of the request source of the acquisition request,
When the first emergency destination is selected in the terminal among the emergency destination candidates, the terminal of the first emergency destination can set permission to view personal information corresponding to the first identification information. Make settings to
After the setting, when the selection of the first emergency destination is canceled or the input of non-conveyance to the first emergency destination is made, the first identification information by the terminal of the first emergency destination. Make settings to disable browsing of personal information corresponding to
A browsing control program that causes a computer to execute a process. In response to an acquisition request for personal information based on the first identification information, the emergency conveyance corresponding to the first identification information is referenced with reference to a storage unit that stores personal information including emergency transport destination candidates in association with the identification information. A transmitting unit for transmitting personal information including a destination candidate to a terminal as a request source of the acquisition request;
When the first emergency destination is selected in the terminal among the emergency destination candidates, the terminal of the first emergency destination can set permission to view personal information corresponding to the first identification information. A first setting unit for setting to
After the setting by the first setting unit, when the cancellation of the selection of the first emergency transfer destination or the input of non-conveyance to the first emergency transfer destination is performed, the first emergency transfer destination terminal ( 13) a second setting unit configured to disable setting of permission / prohibition of browsing of personal information corresponding to the first identification information according to 13);
A browsing control device characterized by having.

Images