JP2023176141A - Server device and program - Google Patents

Abstract

To provide a server device and a program for simplifying information transmission between a subject who receives medical treatment and a person in charge in a medical side.SOLUTION: In a health observation system, a server device 300 as an information processor for supporting information transmission between multiple donors and multiple medical practitioners includes a charge information storage part 346 for associatively storing each of multiple donors for providing internal organs, tissues, or cells and a person in charge in a medical side, a reception part 314 of a donor interface part 312 that receives a report on a donor's physical condition from a terminal of one of multiple donors, a physical condition report storage part 348 for storing a report on a physical condition in association with a donor, and a transmission part 317 of a medical practitioner interface part 313 for transmitting a physical condition report to a medical practitioner's terminal corresponding to a donor.SELECTED DRAWING: Figure 5

Description

The present invention relates to technology for supporting the transmission of medical information.

As a medical practice, living body transplantation is sometimes performed in which organs, tissues, or cells collected from a healthy person are transplanted into a patient. A donor of organs, tissues, or cells is called a "donor." For donor safety, it is necessary to manage the donor's health before and after organ, tissue, or cell collection. The doctor in charge of collection mainly manages the health of the donor, and a transplant coordinator (hereinafter simply referred to as "coordinator"), a medical professional, supports this.

Specifically, a doctor examines the donor and takes appropriate measures if there are any side effects caused by the use of medicines. Coordinators contact donors by phone to conduct health checks when doctors are not available. During the health check, the coordinator listens to the donor's physical condition and confirms that there are no abnormalities. If there are any abnormalities, the coordinator recommends that the donor see a doctor. In this way, health checks by coordinators play an important role in ensuring donor safety.

Japanese Patent Application Publication No. 2007-044442 Japanese Patent Application Publication No. 2002-056099 Japanese Patent Application Publication No. 11-045304

However, telephone calls for health checks place a heavy burden on both donors and coordinators. Donors may not be available on the phone during business hours, for example. Coordinators cannot, for example, be on the phone while doing other work. Even if the call time is adjusted in advance, it is not easy to accommodate each person's convenience. Coordinators must allocate their schedules to avoid overlapping calls with other donors. Even if you make a call as scheduled, if the called party is busy, you will have to call again. In addition, there are many predetermined items for the health check, and it takes time to listen to all of them. Including the time for the coordinator to make decisions and respond, the call time per donor increases.

Patent Document 1 relates to donor safety in blood collection. In order to prevent side effects from blood collection, the donor's heart rate is measured and the state of autonomic nerve activity is evaluated before blood collection begins. If the state of autonomic nerve activity is unstable, stop blood sampling. This procedure requires only a preliminary in-hospital examination, so communication between donors and medical personnel is not a particular problem.

Patent Document 2 discloses a technology that supports users' self-management with lifestyle-related diseases and the like in mind. The user's biometric data measured by a vital sensor connected to the user terminal is sent to the server, which calculates the health level and sends it back to the user. This technology mainly transmits information between the user terminal and the server, and medical personnel do not communicate with the user.

Patent Document 3 proposes a system in which medical data created by a plurality of medical institutions is centrally managed and each medical institution uses the medical data via a network. Although medical data is now provided to general users, it is not a system aimed at communication between patients and medical practitioners.

The present invention has been made in view of these problems, and one of its purposes is to facilitate the communication of information between a person receiving medical care and a person in charge of the medical care.

A server device according to an aspect of the present invention includes a first storage unit that stores each of a plurality of donors who provide organs, tissues, or cells and a person in charge on the medical side in association with each other; a receiving unit that receives the physical condition report of the donor from the donor's terminal; a second storage unit that stores the physical condition report in association with the donor; and a first storage unit that transmits the physical condition report to the terminal of the person in charge of the donor. A transmitting section.

A program according to an aspect of the present invention provides a first method for inputting a first physical condition report into a terminal used by a donor who donates organs, tissues, or cells when the donor has not yet collected the organ, tissue, or cells. a display function that displays an input screen, and displays a second input screen for inputting a second physical condition report having a different item configuration from the first physical condition report when the donor has collected organs, tissues, or cells; A reception function that accepts input of a first physical condition report on the first input screen or a second physical condition report on the second input screen, and a transmission function that transmits the first physical condition report or the second physical condition report to the server device. and demonstrate.

A server device according to another aspect of the present invention is a server device that supports information transmission between a person receiving medical care and a person in charge on the medical side, and includes an input screen for inputting a status report of the person. a generation unit that generates data; a first transmission unit that transmits the data on the input screen to the target person's terminal; a reception unit that receives the status report input on the input screen from the target person's terminal; The generation unit includes a recording unit that records status reports in association with each other, a second transmission unit that transmits the status report to the terminal of the person in charge, and an acquisition unit that acquires information on the occurrence of a predetermined event regarding the target person. In response to the occurrence of a predetermined event, the status report items input on the input screen are switched.

A program according to another aspect of the present invention has a display function for displaying an input screen for inputting a situation report of the subject on a terminal used by the subject receiving medical care, and a reception desk for receiving input of the situation report on the input screen. function, a transmission function that transmits the status report input on the input screen to the server device, and an acquisition function that acquires information on the occurrence of a predetermined event regarding the target person, and the display function indicates that a predetermined event has occurred. Taking this as an opportunity, the status report items to be entered on the input screen are switched.

According to the present invention, it is possible to provide a technique that facilitates information transmission between a person receiving medical care and a medical person in charge.

FIG. 1A is a diagram showing an example of a conventional collection schedule. FIG. 1(B) is a diagram showing an example of a collection schedule expected in the future. It is a network configuration diagram of a health observation system. It is a transition diagram of the display screen of a donor terminal. It is a transition diagram of the display screen of a donor terminal. FIG. 2 is a functional block diagram of a server device. FIG. 2 is a sequence diagram of a donor service using a Web (World Wide Web) application method. FIG. 2 is a sequence diagram of a donor service using a web application method. It is a transition diagram of the display screen on a medical worker terminal. FIG. 2 is a sequence diagram of a medical provider service using a web application method. FIG. 2 is a sequence diagram of a medical provider service using a web application method. FIG. 7 is a functional block diagram of a donor terminal in Modification 1. FIG. FIG. 3 is a sequence diagram of a donor service using a native application method. FIG. 7 is a functional block diagram of a medical terminal in Modification 2. FIG. FIG. 2 is a sequence diagram of a medical provider service using a native application method.

Embodiments of the present invention will be described in detail below with reference to the drawings.
First, living body transplantation will be explained. Living donor transplantation is the transplantation of organs, tissues, or cells donated by a healthy person into a patient. Organs to be transplanted are, for example, kidneys, liver and bone marrow. Tissues to be transplanted are, for example, corneas, skin, heart valves and blood vessels. The cells to be transplanted are, for example, hematopoietic stem cells. Hematopoietic stem cells are obtained from peripheral blood, bone marrow or umbilical cord blood. Blood transfusion can also be said to be a type of organ transplant in which blood, which is a liquid organ, is used.

In living donor transplantation, it is necessary to give due consideration to the safety of the donor, who is the organ, tissue, or cell donor. Living donor transplants can also be promoted by ensuring donor safety. Below, donor treatment and health management will be explained using peripheral blood stem cell collection (PB collection) for hematopoietic stem cell transplantation as an example.

Hematopoietic stem cell transplantation is a procedure that transfers the ability to make normal blood from a donor in order to make normal blood within the patient's body as a treatment for leukemia. Peripheral blood stem cell collection is one method of collecting hematopoietic stem cells from a donor.

FIG. 1A is a diagram showing an example of a conventional collection schedule.
In the illustrated example, the donor visits the hospital for a medical checkup five days before the collection date. After that, hospital visits continue, and the donor receives daily injections of G-CSF (granulocyte colony stimulating factor) preparations.

G-CSF preparations have the effect of increasing white blood cells and hematopoietic stem cells contained in the blood flowing through the body. Administration of the G-CSF preparation makes it possible to collect hematopoietic stem cells from peripheral blood in an amount necessary for transplantation. If the white blood cell count increases too much, adjustments may be made, such as reducing the amount of the drug administered.

G-CSF preparations have complications such as musculoskeletal symptoms, skin symptoms, and liver dysfunction. Rarely, respiratory symptoms, shock, and anaphylaxis also occur. As a result, side effects may include poor physical condition such as bone pain, fever, headache, fatigue, insomnia, loss of appetite, and nausea. Pain medications can be used to treat pain. Diagnosis of complications is carried out in conjunction with the outpatient clinic for administration of the preparation.

If all goes well, you will be admitted to the hospital the day before, and on the collection day, hematopoietic stem cells will be collected using a component separation device. Component separation extracts only the necessary components. Each sample takes three to four hours to collect, with medical staff always on hand to monitor their physical condition. In addition, sampling may be carried out over two days. Generally, the donor is discharged from the hospital the day after collection is completed.

For about a week after receiving G-CSF preparations, the patient's white blood cell count is high and thrombosis is likely to occur, so care must be taken in daily life. After collection, the spleen may temporarily swell, but no major complications have been observed. For this reason, coordinators conduct health checks by phone about once a week. If there is any abnormality, the coordinator recommends seeing a doctor.

A medical examination will be conducted around 14 days after collection, and the examination will be finalized if there are no complications or side effects related to collection. In this way, follow-up is carried out through telephone calls by the coordinator and outpatient visits by the doctor.

Looking to the future, it is planned that a long-acting G-CSF preparation will be added to the application for peripheral blood stem cell collection in the near future. When using long-acting G-CSF formulations, the sampling schedule changes slightly.

FIG. 1(B) is a diagram showing an example of a collection schedule expected in the future.
Long-acting G-CSF preparations provide sufficient effects with one administration. Therefore, once administered, the donor does not have to go to the hospital for administration.

However, it is thought that long-acting G-CSF preparations require more consideration regarding complications than conventionally used G-CSF preparations. Therefore, it is better to evaluate the health condition every day for at least two weeks after the collection date. Considering the daily burden of donors, it is difficult to visit the hospital every day, so it is expected that coordinators will conduct health checks by telephone.

Furthermore, based on the policy of the Japanese Society of Hematopoietic and Immune Cell Therapy, it is expected that the number of peripheral blood stem cell collections will increase.

Currently, telephone contact is used as a means of remotely conducting health checks, but as mentioned above, telephone contact has many inconvenient aspects. Therefore, we propose a health observation system using ICT (Information and Communication Technology) technology.

Using ICT technology, donors can report their physical condition at any time using a smartphone or PC (personal computer). On the other hand, a doctor or coordinator can also view it on a smartphone or PC at any time. This eliminates the inconvenience of the coordinator having to schedule calls to avoid duplication and having to make calls again. It is also easy and convenient for donors. This makes it possible to streamline the medical care and coordination system. It is hoped that preparations will be made to safely handle future increases in the number of transplants without disrupting business operations.

FIG. 2 is a network configuration diagram of the health observation system.
The health observation system includes donor terminals 100a to 100c, medical worker terminals 200a to 200c, and a server device 300.

The donor terminals 100a to 100c are terminals used by a donor who provides hematopoietic stem cells (hereinafter sometimes simply referred to as "cells"). Donor terminals 100a to 100c, etc., are collectively referred to as "donor terminal 100" when they are not particularly distinguished. The medical personnel terminals 200a to 200c are terminals used by medical personnel who monitor the health of donors. The medical terminals 200a to 200c, etc., are collectively referred to as the "medical terminal 200" when no particular distinction is made. The following explanation assumes that the medical professional is a doctor. However, a medical professional may serve as the coordinator. In the case of a coordinator, he or she shall not engage in activities that are permitted only to doctors, such as diagnosis or treatment. Those who interact with a given donor from a medical perspective, such as doctors and coordinators, are "medical personnel." The illustrated medical worker terminal 200 corresponds to a "terminal of a person in charge on the medical side."

In the following description, it is assumed that the donor terminal 100 and the medical worker terminal 200 are smartphones. However, the donor terminal 100 and the medical worker terminal 200 may be tablet terminals, PCs, or the like.

The donor terminal 100 has a browser 102 and a mailer 104, and the medical worker terminal 200 has a browser 202 and a mailer 204. The browser 102 and the browser 202 are general software used for displaying web pages and for user operations. Mailer 104 and mailer 204 are general software used when sending, receiving, and editing e-mails. Furthermore, the donor terminal 100 and the medical worker terminal 200 have a communication function to connect to the Internet and communicate with each other.

The server device 300 is an information processing device that supports information transmission between donors and medical personnel. Server device 300 is connected to the Internet. When the server device 300 is accessed from the donor terminal 100, the server device 300 provides a service for donors (hereinafter referred to as "donor service"). Further, when the server device 300 is accessed from the medical worker terminal 200, the server device 300 provides a service for medical professionals (hereinafter referred to as "medical professional service"). Donor service is a service that provides information to donors and accepts information registration from donors. The medical provider service is a service that provides information to medical professionals and accepts information registration from medical professionals. Communication between the donor service and medical provider service is facilitated. Next, the donor service will be described in detail by showing an example of a screen displayed on the donor terminal 100.

3 and 4 are transition diagrams of the display screen of the donor terminal 100.
These figures show screens displayed when a donor uses the donor terminal 100 to report his/her physical condition. Login screen 400 displayed on the display of donor terminal 100 includes an email address area 402, a password area 404, and a login button 406. The donor enters his or her e-mail address in the e-mail address area 402 and enters a password in the password area 404. The donor then touches the login button 406 and requests login to the server device 300.

When the donor successfully logs in, a progress screen 410 is displayed on the display of the donor terminal 100. The progress screen 410 displays progress information up to now. For each date, the number of days elapsed, reporting status, body temperature, presence of pain, and use of painkillers are displayed. If the data has not yet been collected, the number of days before the collection start date is displayed as the number of days elapsed. If cells have been collected, the number of days since the start of collection is displayed as the number of days elapsed. The collection start date is the day when hematopoietic stem cells are first collected (before collection, the first scheduled day of collection). Hematopoietic stem cells may be collected over multiple days. If you have already reported your physical condition, a reported button 412 indicating "completed" is displayed as the reporting status, and if you have not yet reported your physical condition, an unreported button 414 indicating "not yet" is displayed as the reporting status. be done. In this example, a physical condition report was made yesterday (April 1st), and no physical condition report has been made yet for today (April 2nd). Body temperature, presence of pain, and use of painkillers are part (summary) of the physical condition report. The donor can view previous progress information by scrolling the progress screen 410 to the left.

When the donor touches the reported button 412, the entire input physical condition report is displayed (not shown). On the other hand, when the donor touches the unreported button 414, a screen for inputting a physical condition report is displayed. The physical condition items to be reported differ before and after cell donation.

If the stage is before cells are collected, a standard input screen 420 before collection is displayed. A message asking whether there is pain in any part of the body is displayed on the standard input screen 420 before collection, prompting the user to input the presence or absence of pain. If there is no pain anywhere, the donor touches the no pain button 422. Then, when the donor touches the next button 428, the input regarding pain ends. In this case, there will be no pain in all areas. If the return button 426 is touched, the input regarding pain is canceled and the display returns to the progress screen 410. The standard input screen is a screen that does not accept operations for specifying a painful area.

If it hurts somewhere, the donor touches the pain button 424. When the pain button 424 is touched, the display switches to the extended input screen 430 before collection. The expanded input screen is a screen that accepts an operation for specifying a painful part. In this example, pull-down menus 432a to 432c, etc. corresponding to each site that is a candidate for feeling pain (hereinafter referred to as "candidate site") are provided. The pull-down menus 432a to 432c, etc., are collectively referred to as "pull-down menu 432" when they are referred to collectively or when they are not particularly distinguished. In the pull-down menu 432, it is possible to select "none," "mild," or "severe" regarding the pain. It is also possible to select only "not present" or "present" without distinguishing the degree of pain. For example, if the donor feels mild pain only in the chest, the donor selects "mild" from the pull-down menu 432c corresponding to the chest. Regarding the candidate site without pain, the donor selects "no pain" from the pull-down menus 432a, b, etc. If the check box 434 that is displayed as ``Mark uninput as ``None'''' is turned on, it is possible to set ``None'' for candidate parts that have not been input all at once. This eliminates the hassle of operating the pull-down menu 432 for candidate sites that do not cause pain. The operations of the next button 428 and the return button 426 are the same as in the case of the standard input screen 420 before collection. Note that the pre-collection standard input screen 420 and the pre-collection extended input screen 430 are examples of "a first input screen for inputting a first physical condition report."

Let's move on to the explanation of FIG. If the stage is after cells have been collected, a standard post-collection input screen 440 is displayed. After the cells are harvested, the donor can take painkillers at his or her own discretion if pain occurs. It is also assumed that the patient may be unable to attend school or work due to severe pain. Therefore, the post-collection standard input screen 440 includes the same input items as the pre-collection standard input screen 420, as well as input items related to the use of painkillers and school/commuting status.

The donor selects one of the no use button 442, medicine A button 444, medicine B button 446, and other buttons 448 regarding the use of painkillers. If the donor is not taking pain medication, the not used button 442 is selected. If the patient is taking medicine A for pain relief, the medicine A button 444 is selected, and if the patient is taking medicine B for pain relief, the medicine B button 446 is selected. If the patient is taking other pain medication, the other button 448 is selected. Although not shown in this example, when the other button 448 is selected, it may be possible to input the name of another painkiller.

Furthermore, the donor selects the possible button 450 or the impossible button 452 regarding commuting to school/commuting. If the donor has difficulty commuting to school or work due to physical condition, the donor selects the impossible button 452, and if there is no problem, the donor selects the possible button 450. Although not shown in this example, a no-opportunity button may be provided that is selected when there is no opportunity to commute to school or work.

If there is no pain anywhere, the donor selects the no pain button 422 and further performs input operations regarding the use of painkillers and commuting to school/commuting. These input results are included in the physical condition report.

On the other hand, if the donor selects the pain button 424, the display switches to a post-harvest expansion input screen 460. The expanded input screen 460 after sampling includes input means regarding the painful site. This input means is the same as in the case of the extended input screen 430 (FIG. 3) before collection. The donor performs an input operation regarding the part of the body in pain, and further scrolls down to display items such as use of painkillers and going to school/commuting, and performs input operations regarding these items.

Following the input regarding pain, items such as vital signs such as body temperature and other symptoms can also be input as a physical condition report. These input screens will be omitted. When all items are entered, the entered physical condition report is registered in the server device 300. Note that the post-collection standard input screen 440 and the post-collection extended input screen 460 are examples of "a second input screen for inputting a second physical condition report that has a different item configuration from the first physical condition report."

This embodiment will be described assuming that the donor service is implemented using a web application method. In the Web application method, the browser 102 of the donor terminal 100 acquires Web page data from the server device 300 and displays the above-mentioned screen (Web page) based on the Web page data. Further, some operations on a web page are described in a script (for example, a Java script) included in the web page data, and the browser 102 may refer to this description to control display processing and input operations. . Web page data is an example of screen data. The details of donor service processing will be explained below.

Each component of the donor terminal 100, medical worker terminal 200, and server device 300 included in the health observation system includes computing units such as a CPU (Central Processing Unit) and various coprocessors, storage devices such as memory and storage, and connecting them. It is realized by hardware including wired or wireless communication lines and software that is stored in a storage device and supplies processing instructions to a computing unit. A computer program may be composed of a device driver, an operating system, various application programs located in an upper layer thereof, and a library that provides common functions to these programs. Each block described below indicates a functional unit block rather than a hardware unit configuration.

FIG. 5 is a functional block diagram of the server device 300.
Server device 300 includes a communication section 310, a data processing section 320, and a data storage section 340.
The communication unit 310 is in charge of communication processing with the donor terminal 100, the medical worker terminal 200, etc. via the Internet. The data storage unit 340 stores various data. The data processing unit 320 executes various processes based on the data acquired by the communication unit 310 and the data stored in the data storage unit 340. The data processing section 320 also functions as an interface between the communication section 310 and the data storage section 340.

The communication unit 310 includes a donor interface unit 312 that handles communication processing with the donor terminal 100 and a medical practitioner interface unit 313 that handles communication processing with the medical practitioner terminal 200.

The donor interface unit 312 includes a receiving unit 314 that receives data from the donor terminal 100 and a transmitting unit 316 that transmits data to the donor terminal 100. The receiving unit 314 receives access from the donor terminal 100 using a URL (Uniform Resource Locator) for donor services. The receiving unit 314 receives an HTTP (Hypertext Transfer Protocol) request from the browser 102 of the donor terminal 100, and the transmitting unit 316 transmits Web page data to the donor terminal 100 as an HTTP response. The web pages displayed using this web page data correspond to the various screens described in connection with FIGS. 3 and 4. The web page is displayed by the browser 102 of the donor terminal 100. Web page data is an example of screen data.

Similarly, the medical worker interface section 313 includes a receiving section 315 that receives data from the medical terminal 200 and a transmitting section 317 that transmits data to the medical terminal 200. The receiving unit 315 receives access from the medical provider terminal 200 using the URL for medical provider services. The receiving unit 315 receives an HTTP request from the browser 202 of the medical terminal 200, and the transmitting unit 317 transmits web page data to the medical terminal 200 as an HTTP response. The web page displayed by this web page data corresponds to various screens described later with reference to FIG. The web page is displayed by the browser 202 of the medical worker terminal 200.

The data processing section 320 includes an authentication section 322, a screen generation section 324, a recording section 326, and a notification section 328.
Authentication unit 322 authenticates donors and medical personnel using account information. The screen generation unit 324 generates data (web page data) for various screens displayed on the donor terminal 100 and the medical worker terminal 200. The recording unit 326 records physical condition reports sent from donors and diagnostic data sent from medical personnel. The notification unit 328 sends notifications to the donor terminal 100 and the medical worker terminal 200. The notification method may be sending a message by the donor interface unit 312 and the medical practitioner interface unit 313, or may use known techniques such as e-mail, a message function of SNS (Social Networking Service), or push notification.

The data storage section 340 includes an account information storage section 342, a donor information storage section 344, a charge information storage section 346, a physical condition report storage section 348, and a diagnostic data storage section 350.

The account information storage unit 342 stores account information of donors and medical personnel. The account information in this example is a combination of email address and password. The account information may be a combination of a user ID and password, or a combination of a user name and password.

The donor information storage unit 344 stores donor information. Donor information includes personal information, G-CSF information, collection start date, follow-up end date, etc. Personal information includes, for example, name, email address, and phone number. The G-CSF information is information regarding the administration of the G-CSF preparation, and includes the administration start date, the type of G-CSF preparation, and the like. The start date of administration is the day when the G-CSF formulation is first administered.

The person-in-charge information storage unit 346 stores the medical personnel in charge of each donor. It is possible to associate donors with medical personnel based on the information in charge, and furthermore, it is possible to specify the correspondence between the donor terminal 100 and the medical personnel terminal 200. It is assumed that medical personnel information such as the medical personnel's name and email address is also stored in the data storage unit 340.

The physical condition report storage unit 348 stores physical condition reports associated with report dates and times for each donor. The physical condition report includes, for example, pain symptoms, other symptoms, and vital signs. As the pain symptom, the classification of "absent", "mild", or "severe" regarding the pain at each candidate site is set. Candidate areas include the head, neck/throat, chest, back, abdomen, lower back/buttocks, arms, legs, and joints. After the cells have been collected, information on painkiller use and commuting to school/commuting is added to the pain symptoms. Other symptoms include fever, fatigue, sleep problems, dizziness, loss of appetite, nausea, vomiting, itching, skin changes, diarrhea, injection site reactions, taste abnormalities, difficulty breathing, and cough. . At a stage after the cells are collected, the abnormality at the puncture site may be further set as "no", "heat sensation", "swelling", or "pain". Vital signs are, for example, pulse, oxygen saturation, body temperature and blood pressure. Oxygen saturation is measured using a pulse oximeter lent to the donor.

The diagnostic data storage unit 350 stores diagnostic data associated with diagnosis date and time for each donor. Diagnostic data includes, for example, information on splenomegaly, information on dosage reduction/discontinuation, and information on collection. Splenomegaly is a condition in which the spleen becomes swollen and swollen. The information on splenomegaly includes the presence or absence of splenomegaly, the method for measuring splenomegaly, and the measured value. The method for measuring splenomegaly is "palpation" or "echo." In the information on dosage reduction/discontinuation of the G-CSF preparation, the distinction between "no dosage reduction", "50% dosage reduction", "discontinuation", or "no administration" and the reasons thereof are set. When using a long-acting G-CSF preparation, it is not necessary to administer it every day, so "no administration" may be set. The collection information is set to “not collected” or “collected”. If the data is collected as scheduled, "collected" is set after the collection start date.

6 and 7 are sequence diagrams of donor services based on the web application method.
When the receiving unit 314 of the donor interface unit 312 receives the access from the donor terminal 100 (S600), the transmitting unit 316 transmits the data (web page data) of the login screen 400 shown in FIG. 3 to the donor terminal 100 ( S602).

When the donor terminal 100 receives the data on the login screen 400, the browser 102 displays the login screen 400 (S604). The browser 102 accepts input of account information (S606), and the donor terminal 100 transmits the account information to the server device 300 (S608).

When the receiving unit 314 of the donor interface unit 312 receives the account information, the authentication unit 322 authenticates the donor (S610). If the received account information matches the donor's account information stored in the account information storage unit 342, donor authentication is successful. When the donor authentication is successful, the screen generation unit 324 refers to the donor information storage unit 344, the physical condition report storage unit 348, etc., and generates the data of the progress screen 410 shown in FIG. 3 (S612). The transmitter 316 transmits the data on the progress screen 410 to the donor terminal 100 (S614).

When the donor terminal 100 receives the data on the progress screen 410, the browser 102 displays the progress screen 410 (S616). When the browser 102 accepts the touch of the unreported button 414 (S618), the donor terminal 100 transmits the event of the unreported button 414 to the server device 300 (S620). The event of the unreported button 414 corresponds to a request for a standard input screen.

When the receiving unit 314 of the donor interface unit 312 receives the event of the unreported button 414, the transmitting unit 316 refers to the diagnostic data storage unit 350 or the donor information storage unit 344, and determines whether the cells are before or after collection. It is determined (S622). The distinction between before and after collection is determined by collection information (“not collected” or “collected”) included in the diagnostic data. Alternatively, the transmitter 316 may make the determination based on the collection start date included in the donor information. The transmitter 316 transmits the data on the pre-collection standard input screen 420 shown in FIG. 3 to the donor terminal 100 in the case before cell collection, and in the case after cell collection, the data in the post-collection standard input screen 420 shown in FIG. 4. The data on the standard input screen 440 is transmitted to the donor terminal 100 (S624).

Let's move on to the explanation of FIG. When the donor terminal 100 receives the data on the pre-collection standard input screen 420 or the post-collection standard input screen 440, the browser 102 displays the standard input screen (S626). If the browser 102 accepts a touch of the painless button 422, processing on the standard input screen continues. On the other hand, when the browser 102 accepts the touch of the pain button 424 (S628), the donor terminal 100 transmits the event of the pain button 424 to the server device 300 (S630). The event of the painful button 424 corresponds to a request for an extended input screen.

When the receiving unit 314 of the donor interface unit 312 receives the event of the pain button 424, the transmitting unit 316 transmits the data of the extended input screen to the donor terminal 100 (S632). In the case before cells are collected, the data on the pre-collection extended input screen 430 shown in FIG. data is transmitted.

When the donor terminal 100 receives the data on the pre-collection extended input screen 430 or the post-collection extended input screen 460, the browser 102 displays the extended input screen (S634).

The browser 102 accepts the input of the physical condition report on each displayed input screen (S636), and the donor terminal 100 transmits the input physical condition report to the server device 300 (S638).

When the receiving unit 314 of the donor interface unit 312 receives the physical condition report, the recording unit 326 records the physical condition report (S640). Specifically, the physical condition report storage unit 348 stores the physical condition report in association with the report date and time. Thereafter, the notification unit 328 notifies the medical worker terminal 200 that a physical condition report has been received (S642). At this time, the notification unit 328 refers to the person-in-charge information storage unit 346 and the like to identify the medical practitioner in charge of the donor who sent the physical condition report. Then, the notification unit 328 sets the medical worker's terminal 200 as the destination of the notification. The notification unit 328 may send a message including the name of the donor in the notification, for example, "We have received a report on your physical condition from the donor Mr. ○○○○." When the browser 202 of the medical worker terminal 200 receives the notification, it displays or outputs a predetermined message (for example, "We have received a physical condition report from the donor") or the notified message. The browser 202 may output a notification sound. This allows medical personnel to immediately know that there has been a physical condition report from the donor they are in charge of.

Next, the medical service will be described in detail by showing an example of a screen displayed on the medical terminal 200.

FIG. 8 is a transition diagram of the display screen on the medical worker terminal 200.
Login screen 500 displayed on the display of donor terminal 100 includes an email address area 502, a password area 504, and a login button 506. The medical professional enters his or her e-mail address in the e-mail address area 502 and enters a password in the password area 504. The medical practitioner then touches the login button 506 and requests login to the server device 300.

When the medical practitioner successfully logs in, a main screen 510 is displayed on the display of the medical practitioner terminal 200. The main screen 510 displays a list of donors that this medical professional is in charge of. The illustrated “XXXX” and “○○○○” represent the names of donors. In addition to the name, the number of days that have passed is also displayed. The main screen 510 also includes donor progress information. The medical professional can display the progress information of each donor by scrolling down.

The main screen 510 includes a reported button 512 indicating that a physical condition report has already been made, an unreported button 514 indicating that no physical condition report has been made yet, and a diagnosed button 514 indicating that a diagnosis has already been made. It includes a button 516 and an undiagnosed button 518 indicating that no diagnosis has been made yet.

When the medical worker touches the reported button 512, a physical condition report screen 520 is displayed. The physical condition report screen 520 displays the contents of the physical condition report registered by the donor. Furthermore, when the medical professional touches the non-report button 514, the medical professional can input a physical condition report on behalf of the donor. If an interview is conducted by outpatient examination or telephone contact, a medical professional may enter a physical condition report on behalf of the donor.

When the medical practitioner touches the diagnosed button 516, a screen displaying registered diagnosis details is displayed (not shown). On the other hand, when the medical practitioner touches the undiagnosed button 518, the screen moves to a diagnosis screen 530 for inputting diagnosis details. Note that the physical condition report screen 520 is provided with a diagnosis button 522, and when the diagnosis button 522 is touched, the screen also moves to the diagnosis screen 530.

The diagnosis screen 530 includes a splenomegaly button 532 and a splenomegaly button 534 for inputting the presence or absence of splenomegaly. Furthermore, a palpation button 536 and an echo button 538 for inputting a method for measuring splenomegaly, and a measurement value area 540 for inputting a measurement value of splenomegaly are included.

By scrolling down the diagnostic screen 530, items for reducing or discontinuing the preparation are displayed. If the medical practitioner determines that the dosage of the preparation should not be reduced, he or she touches the no reduction button 542. If the medical professional determines that the amount of the preparation should be reduced by 50%, the doctor touches the 50% reduction button 544. If the medical professional decides to stop administering the formulation, he or she touches the stop button 546. If there is no need to administer the preparation, touch the No Administration button 548. Furthermore, a reason area 550 is provided for inputting the reason for the decision regarding reduction or discontinuation of the preparation.

Although not shown, the diagnostic screen 530 also includes an uncollected button and a collected button for inputting collection information. If the cells have not yet been collected, the medical professional touches the uncollected button, and if the cells have already been collected, the medical practitioner touches the collected button. Once collected data is registered, input of collection information may be omitted. The diagnostic details input in this way are registered in the server device 300. Furthermore, the medical practitioner can register donor information in the server device 300 from the medical practitioner terminal 200.

FIGS. 9 and 10 are sequence diagrams of medical provider services based on the Web application method.
When the receiving unit 315 of the medical practitioner interface unit 313 receives the access from the medical practitioner terminal 200 (S700), the transmitting unit 317 transmits the data (web page data) of the login screen 500 shown in FIG. 8 to the medical practitioner terminal 200. (S702).

When the medical terminal 200 receives the data on the login screen 500, the browser 202 displays the login screen 500 (S704). The browser 202 accepts input of account information (S706), and the medical worker terminal 200 transmits the account information to the server device 300 (S708).

When the receiving unit 315 of the medical practitioner interface unit 313 receives the account information, the authentication unit 322 authenticates the medical practitioner (S710). If the received account information matches the medical practitioner's account information stored in the account information storage unit 342, the medical practitioner authentication is successful. When the medical provider authentication is successful, the screen generation unit 324 generates the data of the main screen 510 shown in FIG. 8 by referring to the donor information storage unit 344, the person-in-charge information storage unit 346, the physical condition report storage unit 348, etc. S712). The transmitter 317 transmits the data on the main screen 510 to the medical worker terminal 200 (S714).

When the medical terminal 200 receives the data on the main screen 510, the browser 202 displays the main screen 510 (S716). When the browser 202 accepts the touch of the reported button 512 (S718), the medical worker terminal 200 transmits the event of the reported button 512 to the server device 300 (S720). The event of the reported button 512 corresponds to a request for a physical condition report.

When the receiving unit 315 of the medical provider interface unit 313 receives the event of the reported button 512, the screen generating unit 324 refers to the physical condition report storage unit 348 and generates data for the physical condition report screen 520 shown in FIG. (S722). The transmitter 317 transmits the data on the physical condition report screen 520 to the medical worker terminal 200 (S724). Thereafter, the notification unit 328 notifies the donor terminal 100 that the physical condition report has been transmitted (S726). At this time, the notification unit 328 identifies the donor whose physical condition report was sent, and sets the donor terminal 100 used by that donor as the destination of the notification. In the notification, the notification unit 328 may send a message including the doctor's name, such as "Doctor △△△△ has viewed the physical condition report." Upon receiving the notification, the browser 102 of the donor terminal 100 displays or outputs a predetermined message (for example, "The doctor has viewed your physical condition report") or the notified message. The browser 102 may output a notification sound. This allows the donor to confirm that the physical condition report has been conveyed to the medical professional in charge. When a donor is worried about their health, they can rest assured knowing that their health is being properly taken care of.

Let's move on to the explanation of FIG. When the medical worker terminal 200 receives the data on the physical condition report screen 520, the browser 202 displays the physical condition report screen 520 (S728). When the browser 202 accepts the touch of the diagnosis button 522 (S730), the medical worker terminal 200 transmits the event of the diagnosis button 522 to the server device 300 (S732). The diagnostic button 522 event corresponds to a diagnostic screen 530 request.

When the receiving unit 315 of the medical practitioner interface unit 313 receives the event of the diagnosis button 522, the transmitting unit 317 transmits the data of the diagnosis screen 530 shown in FIG. 8 to the medical practitioner terminal 200 (S736).

When the medical worker terminal 200 receives the data on the diagnosis screen 530, the browser 202 displays the diagnosis screen 530 (S738). The browser 202 accepts input of diagnostic data (S740), and the medical worker terminal 200 transmits the diagnostic data to the server device 300 (S742).

When the receiving unit 315 of the medical practitioner interface unit 313 receives the diagnostic data, the recording unit 326 records the diagnostic data (S744). Specifically, diagnostic data is stored in the diagnostic data storage unit 350 in association with the diagnosis date and time.

According to this embodiment, donors can report their physical condition at any time. Furthermore, medical personnel can also view physical condition reports at any time. It is convenient for both donors and medical personnel because it is not subject to the time constraints of telephone interviews.

Furthermore, since the donor's physical condition is reported by operating an input screen with predetermined input items, necessary information can be conveyed without omission.

Furthermore, in the case of the Web application system, since it can be operated by the browsers 102 and 202, the donor terminal 100 and the medical worker terminal 200 do not need to install a dedicated application program, and can easily use the health observation system. There are also benefits.

[Modification 1]
In the embodiment, an example is shown in which the donor service is provided using a web application method, but the donor service may also be provided using a native application method. A native application is an application program that is executed using the hardware configuration (eg, CPU) or operating system of a terminal as an execution environment. In Modification 1, it is assumed that a native application for a donor service is installed on the donor terminal 100.

The display and user operation specifications of the donor terminal 100 are the same even in the case of the native application method as in the case of the Web application method described in connection with FIGS. 3 and 4.

FIG. 11 is a functional block diagram of donor terminal 100 in Modification 1.
Donor terminal 100 includes a user interface processing section 160, a communication section 110, a data processing section 120, and a data storage section 140. The user here refers to the donor.
The user interface processing unit 160 accepts operations from the user via an input device such as a touch panel, and is also responsible for processing related to the user interface, such as image display and audio output. The communication unit 110 is in charge of communication processing with the server device 300 and the like via the Internet. The data storage unit 140 stores various data. The data processing unit 120 executes various processes based on the data acquired by the communication unit 110 , operation instructions input via the user interface processing unit 160 , and data stored in the data storage unit 140 . The data processing unit 120 also functions as an interface for the communication unit 110, user interface processing unit 160, and data storage unit 140. The data storage unit 140 stores various data such as native application programs and the data described above.

The user interface processing section 160 includes an output section 162 that outputs various information such as images and audio to the user, and an input section 166 that receives input from the user.

The output unit 162 includes a display processing unit 164 that displays various screens and data on the display of the donor terminal 100. The input unit 166 includes a reception unit 168 that accepts user operations on various screens. The data processing section 120 includes a screen generation section 122 that generates various screens. The communication unit 110 includes a receiving unit 112 that receives data and a transmitting unit 114 that transmits data.

These functional blocks are realized by executing a native application program for the donor service on the CPU.

FIG. 12 is a sequence diagram of the donor service using the native application method.
The display processing unit 164 of the donor terminal 100 displays the login screen 400 shown in FIG. 3 (S650). The reception unit 168 accepts input of account information (S652), and the transmission unit 114 transmits the account information to the server device 300 (S654).

When the receiving unit 314 of the donor interface unit 312 receives the account information, the authentication unit 322 authenticates the donor (S656). If donor authentication is successful, the transmitter 316 transmits donor information, physical condition report, diagnostic data, etc. corresponding to the authenticated donor to the donor terminal 100 (S658).

The account information sent in S654 corresponds to a login request, as well as a request for donor information, physical condition report, diagnostic data, etc. The transmitter 114 may transmit requests for donor information, physical condition reports, diagnostic data, etc. to the server device 300 in addition to account information.

When the receiving unit 112 of the donor terminal 100 receives the donor information, physical condition report, diagnostic data, etc., the screen generating unit 122 generates the progress screen 410 shown in FIG. 3 based on the received data (S660). The display processing unit 164 displays the generated progress screen 410 (S662). When the receiving unit 168 receives a touch on the unreported button 414 (S664), the display processing unit 164 determines whether cells are before or after cell collection based on diagnostic data or donor information (S666). The distinction between before and after collection is determined by the collection information (“not collected” or “collected”) included in the diagnostic data. Alternatively, the display processing unit 164 may make the determination based on the collection start date included in the donor information. The display processing unit 164 displays the pre-collection standard input screen 420 shown in FIG. 3 in the case before cells are collected, and displays the post-collection standard input screen 440 shown in FIG. 4 in the case after cells are collected. is displayed (S668). When the reception unit 168 receives a touch of the pain button 424 (S670), the display processing unit 164 displays the pre-harvesting extended input screen 430 if the cells are not being harvested, and if the cells are being harvested, The extended input screen 460 after collection is displayed (S672). The receiving unit 168 accepts the input of the physical condition report on each displayed input screen (S674), and the transmitting unit 114 transmits the physical condition report to the server device 300 (S676).

When the receiving unit 314 of the donor interface unit 312 receives the physical condition report, the recording unit 326 records the physical condition report (S678). The notification unit 328 notifies the medical worker terminal 200 that a physical condition report has been received (S680).

The native application method of Modification 1 can also provide donor services similar to those of the embodiment. In the case of the native application method, the amount of data transmitted such as screen data and events is small, so the operation of the donor terminal 100 is agile. Furthermore, since the communication load is small, there is also the advantage that communication failures are less likely to occur.

[Modification 2]
In the embodiment, an example is shown in which medical services are provided using a web application system, but medical services may also be provided using a native application system. In the second modification, it is assumed that a native application for medical worker services is installed on the medical worker terminal 200.

The display and user operation specifications of the medical terminal 200 are the same in the case of the native application method as in the case of the Web application method described in connection with FIG. 8 .

FIG. 13 is a functional block diagram of the medical worker terminal 200 in the second modification.
Medical terminal 200 includes a user interface processing section 260, a communication section 210, a data processing section 220, and a data storage section 240. The user here refers to a medical professional. The basic configuration is the same as that of the donor terminal 100 in Modification 1 (FIG. 11).

These functional blocks are realized by executing a native application program for medical provider services on the CPU.

FIG. 14 is a sequence diagram of a medical provider service based on a native application method.
The display processing unit 264 of the medical worker terminal 200 displays the login screen 500 shown in FIG. 8 (S750). The reception unit 268 accepts input of account information (S752), and the transmission unit 214 transmits the account information to the server device 300 (S754).

When the receiving unit 315 of the medical practitioner interface unit 313 receives the account information, the authentication unit 322 authenticates the medical practitioner (S756). If the medical practitioner authentication is successful, the transmitting unit 317 transmits the person in charge information, donor information, physical condition report, diagnostic data, etc. to the medical practitioner terminal 200 (S758). The person in charge information, donor information, physical condition report, and diagnostic data to be transmitted may be only information related to the person in charge of this medical person.

The account information transmitted in S754 corresponds to a login request, as well as a request for information such as person in charge information, donor information, physical condition report, and diagnostic data. The transmitter 214 may transmit requests for person-in-charge information, donor information, physical condition report, diagnostic data, etc. to the server device 300 in addition to account information.

When the receiving unit 212 of the medical terminal 200 receives the information in charge, donor information, physical condition report, diagnostic data, etc., the screen generating unit 222 generates the main screen 510 shown in FIG. 8 based on the received data (S760 ). The display processing unit 264 displays the generated main screen 510 (S762). When the receiving unit 268 accepts the touch of the reported button 512 (S764), the transmitting unit 214 transmits the event of the reported button 512 to the server device 300 (S766). The event of the reported button 512 corresponds to a request for notification to the donor terminal 100.

When the receiving unit 315 of the medical worker interface unit 313 receives the event of the report completed button 512, the notification unit 328 notifies the donor terminal 100 that the physical condition report has been transmitted (S770). In the case of specifications that do not notify the donor terminal 100, the transmission of the event of the reported button 512 (S766) may be omitted.

The screen generation unit 222 generates the physical condition report screen 520 shown in FIG. 8 based on the physical condition report (S772), and the display processing unit 264 displays the physical condition report screen (S774). When the reception unit 268 accepts the touch of the diagnosis button 522 (S776), the display processing unit 264 displays the diagnosis screen 530 shown in FIG. 8 (S778). When the receiving unit 268 accepts the input of diagnostic data (S780), the transmitting unit 214 transmits the diagnostic data to the server device 300 (S782).

When the receiving unit 315 of the medical practitioner interface unit 313 receives the diagnostic data, the recording unit 326 records the diagnostic data (S784).

The native application method of Modification 2 can also provide medical services similar to those of the embodiment. In the case of the native application method, the amount of data transmitted such as screen data and events is small, so the operation of the medical terminal 200 is agile. Furthermore, since the communication load is small, there is also the advantage that communication failures are less likely to occur.

[Modification 3]
The techniques described above may also be applied in the collection of cells, organs, or tissues other than hematopoietic stem cells. Furthermore, the above-described technology may be applied to all medical related activities. For example, it can be applied to diagnosis, treatment, testing, counseling, or advice.

Alternatively, the target may be someone other than the donor. In addition to patients, subjects receiving medical care include those receiving examinations, counseling, or advice. The subject terminals used by these subjects correspond to the donor terminal 100 described above.

Personnel other than doctors and coordinators may use the health monitoring system. The person in charge on the medical side may be a medical worker such as a nurse, a professional engineer, or a medical administrator, or a medical collaborator such as a care manager or registered dietitian who cooperates with medical care. Note that a transplant coordinator is a type of medical professional. The staff terminals used by these staff correspond to the medical worker terminal 200 described above.

You may also report on conditions other than your physical condition. Situation reports include not only physical conditions but also environmental conditions such as weather and lifestyle. Weather information is, for example, temperature, humidity, or atmospheric pressure. Lifestyle information includes, for example, exercise time, work time, sleep time, number of baths, meal content (inoculated calories, type of food, etc.), meal form (regular meal, chopped meal, liquid meal, etc.), or number of meals. be. Environmental conditions also affect physical condition and are useful for health management and diagnosis.

Data on input screens with different item configurations may be transmitted not only before and after collection, but also before and after a predetermined event related to a subject receiving medical care. Further, those screens may be displayed. The predetermined events include treatments such as surgery and medication, examinations, progress of disease and recovery stages, admission to hospital, hospital transfer, and the like. Occurrence information of a predetermined event may be included in donor information, physical condition report, diagnostic data, or the like. Alternatively, the occurrence information of the predetermined event may be specified in other data. That is, the receiving section 314 of the donor interface section 312 and the receiving section 315 of the medical practitioner interface section 313 described above correspond to an obtaining section that obtains occurrence information of a predetermined event regarding a person receiving medical care. Further, the occurrence information of the predetermined event may be acquired by other receiving means or input means.

[Modification 4]
The server device 300 may send an alert to both the donor and the person in charge (for example, a medical worker or coordinator) if there is no physical condition report by a predetermined time. In the following explanation, it is assumed that the person in charge is a medical professional.

The predetermined time is the time (time) set as the deadline for the donor to send the physical condition report. In other words, the rule is that donors must send in their physical condition reports by a predetermined time. For example, if the predetermined time is 5 p.m., the donor is supposed to send a health report by 5 p.m. The predetermined time may be common to each donor, or may be set individually for each donor.

When the predetermined time has elapsed, the notification unit 328 refers to the physical condition report storage unit 348 to identify donors who have not yet received a physical condition report (hereinafter referred to as “unreported donors”). If there are no unreported donors, no alert will be sent. If there is an unreported donor, the notification unit 328 refers to the person-in-charge information storage unit 346 to identify the medical professional in charge of the donor.

The notification unit 328 notifies an alert to the donor terminal 100 of the identified donor. The alert to the donor may include, for example, a message such as "Please send a health report." Upon receiving the notification, the donor terminal 100 displays or audio outputs a predetermined message (for example, "Send a physical condition report") or the notified message. The donor terminal 100 may output a notification sound. By doing so, it is possible to prompt the donor to report his/her physical condition. Donors who receive the alert report their physical condition.

Further, the notification unit 328 notifies the identified medical personnel's medical personnel terminal 200 of an alert. The alert to the medical personnel may include, for example, a message such as "Mr. ____ has not reported his physical condition." “Mr. ○○” is the name of an unreported donor. Upon receiving the notification, the medical worker terminal 200 displays or audio outputs a predetermined message (for example, "There is a donor who has not received a physical condition report yet.") or the notified message. The medical worker terminal 200 may output a notification sound. A medical professional who receives the alert contacts the donor by phone, for example. By doing so, the medical personnel can prevent omissions in checking the physical condition of the donor in charge.

[Other variations]
The native application donor service described in the first modification and the native application medical provider service described in the second modification may be combined. Alternatively, one service may be a native application system, and the other service may be a web application system. Alternatively, both methods may be used together for the same service. Furthermore, services may be provided using a hybrid application method that combines a web application method and a native application method.

It should be noted that the present invention is not limited to the above-described embodiments and modified examples, and can be embodied by modifying the constituent elements without departing from the scope of the invention. Various inventions may be formed by appropriately combining a plurality of components disclosed in the above embodiments and modified examples. Furthermore, some components may be deleted from all the components shown in the above embodiments and modified examples.

In summary, the server device 300 receives the physical condition report from the donor, temporarily stores it, and sends it to the doctor or coordinator, so the donor can report the physical condition at any time and from any location. A doctor or coordinator can view the donor's physical condition at any time and any place. This makes remote health management easier.

In addition, since the items on the input screen are switched before and after collection, it is possible to report information necessary for determining complications and side effects that must be noted before and after collection.

In addition, since the donor is asked to specify the location only if there is pain somewhere, it is easy for the donor to understand the operation method.

In addition, regarding the identification of a painful site, candidate sites for which no input has been made are collectively set as "not present," making the operation easy for the donor.

Additionally, the donor list and summary of chronological health reports are displayed on the doctor's or coordinator's terminal, making it easy for the doctor or coordinator to grasp the status of all the donors in charge.

Furthermore, since the doctor or coordinator is notified when the donor reports his or her physical condition, it is easy to prevent omissions in communication.

In addition, the donor can feel at ease because the donor is notified when the condition report is sent to the doctor or coordinator.

Furthermore, if a physical condition report is not received by a predetermined time, an alert is sent to the unreported donor and the doctor or coordinator in charge, thereby preventing omissions in physical condition reports and physical condition checks.

In addition, since it can be applied not only to collection but to all medical practices, information transmission in various medical fields becomes easier and medical activities proceed smoothly.

100 donor terminal, 102 browser, 104 mailer, 110 communication unit, 112 reception unit, 114 transmission unit, 120 data processing unit, 122 screen generation unit, 140 data storage unit, 160 user interface processing unit, 162 output unit, 164 display processing section, 166 input section, 168 reception section, 200 medical terminal, 202 browser, 204 mailer, 210 communication section, 212 reception section, 214 transmission section, 220 data processing section, 222 screen generation section, 240 data storage section, 260 user Interface processing unit, 262 Output unit, 264 Display processing unit, 266 Input unit, 268 Reception unit, 300 Server device, 310 Communication unit, 312 Donor interface unit, 313 Medical practitioner interface unit, 314 Receiving unit, 315 Receiving unit, 316 Transmission section, 317 transmission section, 320 data processing section, 322 authentication section, 324 screen generation section, 326 recording section, 328 notification section, 340 data storage section, 342 account information storage section, 344 donor information storage section, 346 charge information storage section , 348 Physical condition report storage section, 350 Diagnosis data storage section, 400 Login screen, 402 Email address area, 404 Password area, 406 Login button, 410 Progress screen, 412 Reported button, 414 Not reported button, 420 Standard input before collection Screen, 422 No pain button, 424 Pain button, 426 Back button, 428 Next button, 430 Extended input screen before collection, 432 Pull-down menu, 434 Check box, 440 Standard input screen after collection, 442 Not used button, 444 A medicine button, 446 B medicine button, 448 Other buttons, 450 Possible button, 452 Impossible button, 460 Extended input screen after collection, 500 Login screen, 502 Email address area, 504 Password area, 506 Login button, 510 Main Screen, 512 Reported button, 514 Not reported button, 516 Diagnosed button, 518 Undiagnosed button, 520 Physical condition report screen, 522 Diagnosis button, 530 Diagnosis screen, 532 No splenomegaly button, 534 Splenomegaly button, 536 Palpation button, 538 Echo button, 540 Measured value area, 542 No reduction button, 544 50% reduction button, 546 Stop button, 548 No administration button, 550 Reason area

Claims (11)

a first storage unit that stores each of a plurality of donors who donate organs, tissues, or cells and medical personnel in association with each other;
a receiving unit that receives a physical condition report of any one of the plurality of donors from a terminal of the donor;
a second storage unit that stores the physical condition report in association with the donor;
A server device comprising: a first transmitting unit that transmits the physical condition report to a terminal of the person in charge corresponding to the donor. If the donor has not yet collected the organ, the tissue, or the cells, data on a first input screen for inputting a first physical condition report is transmitted to the terminal of the donor, and the donor collects the organ, a second transmission of transmitting data on a second input screen for inputting a second physical condition report having a different item configuration from the first physical condition report to the terminal of the donor when the tissue or the cells have been collected; further comprising:
The server device according to claim 1, wherein the receiving unit receives the first physical condition report or the second physical condition report. Data on a third input screen for inputting the presence or absence of pain in any part of the body, and an operation for specifying the part where the pain is present only when the presence of pain is input on the third input screen. The server device according to claim 1, further comprising a second transmitter that transmits data on a fourth input screen for accepting requests to the terminal of the donor. The fourth input screen allows input of the presence or absence of pain for a plurality of candidate parts, and collectively indicates that there is no pain for one or more of the candidate parts for which the presence or absence has not been input. 4. The server device according to claim 3, further comprising means for setting. The first transmission unit transmits data on a display screen displaying the list of donors for which the person in charge is in charge and a summary of the plurality of physical condition reports shown in chronological order to the terminal of the person in charge. The server device according to claim 1, wherein the server device transmits the information. The server device according to claim 1, further comprising a notification unit that notifies the terminal of the person in charge that the physical condition report has been received when the receiving unit receives the physical condition report. A claim characterized in that, when the first transmitting unit transmits the physical condition report to the terminal of the person in charge, a notification unit is provided that notifies that the physical condition report has been transmitted to the terminal of the donor. The server device according to item 1. 2. The method according to claim 1, further comprising a notification section that notifies the terminal of the donor and the terminal of the person in charge when the receiving section does not receive the physical condition report by a predetermined time. server equipment. A terminal used by a donor who donates an organ, tissue or cell,
If the donor has not yet collected the organ, tissue, or cell, a first input screen for inputting a first physical condition report is displayed; a display function for displaying a second input screen for inputting a second physical condition report having a different item configuration from the first physical condition report;
a reception function that accepts input of the first physical condition report on the first input screen or receives input of the second physical condition report on the second input screen;
A program that performs a transmission function of transmitting the first physical condition report or the second physical condition report to a server device. A server device that supports information transmission between a person receiving medical care and a medical person in charge,
a generation unit that generates data for an input screen for inputting a status report of the subject;
a first transmitting unit that transmits the data on the input screen to the target person's terminal;
a receiving unit that receives the status report input on the input screen from the terminal of the subject;
a recording unit that records the situation report in association with the target person;
a second transmitting unit that transmits the status report to the terminal of the person in charge;
an acquisition unit that acquires occurrence information of a predetermined event regarding the target person;
Equipped with
The server device is characterized in that the generation unit switches items of the status report input on the input screen, triggered by the occurrence of the predetermined event. On the terminal used by the person receiving medical care,
a display function that displays an input screen for inputting a status report of the subject;
a reception function that receives input of the status report on the input screen;
a transmission function that transmits the status report input on the input screen to a server device;
an acquisition function for acquiring occurrence information of a predetermined event regarding the target person;
A program characterized in that, in the display function, the items of the status report input on the input screen are switched in response to the occurrence of the predetermined event.

Images