Reproductive medicine support server and support method

Abstract

Provided is a mechanism that allows a physician and an embryologist to collaborate to support a patient. This reproductive medicine support server comprises: an acquisition unit that acquires medical information related to a patient's reproductive medicine; a physician terminal output unit that outputs at least a portion of the medical information to a physician terminal that is used by a physician; and an embryologist terminal output unit that outputs examination information related to at least one of oocytes, embryos, culture medium, and sperm in the medical information to an embryologist terminal that is used by an embryologist. The acquisition unit is configured to acquire treatment information related to treatment for the patient as the medical information from the physician terminal. The embryologist terminal output unit is configured to output the acquired treatment information to the embryologist terminal.

Description

Reproductive medical support server and support method

[0001] [Related Applications] This application claims priority to Japanese Patent Application No. 2024-050765, entitled "Reproductive Medical Support Server and Support Method," filed on March 27, 2024, and Japanese Patent Application No. 2024-111103, entitled "Reproductive Medical Support Server and Support Method," filed on July 10, 2024, the disclosures of which are incorporated herein by reference in their entireties. The present technology relates to a reproductive medical support server and a support method.

[0002] Japanese Patent Laid-Open Publication No. 2019-076087 (Patent Document 1) is a background technology in this technical field. This publication states that "the embryo quality evaluation system is equipped with an information processing device for performing quality evaluation of fertilized eggs using cloud computing, and the information processing device includes: an acquisition unit that acquires, via a network from a terminal device, a plurality of observation images of fertilized eggs linked to unique identification information, captured in time series; an analysis unit that generates fertilized egg analysis information based on the plurality of observation images; and an output unit that outputs, via the network, evaluation support information including the identification information and the fertilized egg analysis information to a computer that accepts input of fertilized egg evaluation information based on the evaluation support information" (see Abstract).

[0003] Japanese Patent Application Laid-Open No. 2019-076087

[0004] The embryo quality evaluation system of Patent Document 1 makes it possible to obtain highly accurate evaluation results of embryo quality. In reproductive medicine, while a doctor may perform everything from examination to embryo cultivation, an embryologist generally supports reproductive medicine under the doctor's guidance. In this regard, Patent Document 1 does not disclose a configuration for doctors and embryologists to work together to support patients in reproductive medicine. Therefore, the present technology provides a system that enables doctors and embryologists (hereinafter sometimes simply referred to as "embryologists") to work together to support patients.

[0005] To solve the above problems, for example, the configuration described in the claims is adopted. The present application includes multiple configurations and methods for solving the above problems, but one example provides a reproductive medicine support server including an acquisition unit that acquires medical information related to a patient's reproductive medicine, a doctor terminal output unit that outputs at least a portion of the medical information to a doctor terminal used by a doctor, and an embryologist terminal output unit that outputs test information related to at least one of eggs, embryos, and sperm from the medical information to an embryologist terminal used by an embryologist, wherein the acquisition unit is configured to acquire treatment information related to treatment for the patient from the doctor terminal as the medical information, and the embryologist terminal output unit is configured to output the acquired treatment information to the embryologist terminal.

[0006] According to the present technology, it is possible to provide a system that allows doctors and embryologists to work together to support patients. Problems, configurations, and effects other than those described above will become clear from the description of the following embodiments.

[0007] FIG. 1 shows an example of the overall configuration of a reproductive medicine support system. FIG. 2 shows an example of the hardware configuration of the management server 101. FIG. 3 shows an example of the hardware configuration of the doctor terminal 102. FIG. 4 shows an example of the hardware configuration of the embryologist terminal 103. FIG. 5 shows an example of the hardware configuration of the patient terminal 104. FIG. 6 shows examples of the contents of (A) patient information, (B) partner information, (C) treatment information, (D) owned medication information, (E) consent form information, and (F) embryo information. FIG. 7 shows examples of the contents of (G) sperm management information, (H) medication information, (I) prescription schedule information, and (J) freezing management information. FIG. 8 shows an example of a reproductive medicine support flow. FIG. 9 shows an example of a reproductive medicine support flow. FIG. 10 shows an example of an automatic prescription input flow. FIG. 11 shows another example of an automatic prescription input flow. FIG. 12 shows an example of a remaining medication management flow. FIG. 13 shows another example of an automatic prescription input flow. FIG. 14 shows an example of a referral letter creation flow. Figure 15 is an example of a medical record information extraction flow. Figure 16 is an example of a consent form information management flow. Figure 17 is an example of a semen evaluation flow. Figure 18 is an example of a patient information screen on a doctor's terminal. Figure 19 is an example of a patient information screen on an embryologist's terminal. Figure 20 is an example of an overall image of a treatment history calendar displayed on a doctor's terminal. Figure 21 is an example of an egg collection cycle screen on a doctor's terminal. Figures 22 (A), (B1), and (B2) are display examples of prescription drug input fields. Figure 23 is another display example of a prescription drug input field. Figures 24 (A) to (C) are display examples of parts of the egg collection cycle screen. Figure 25 is an example of an egg collection ET screen on an embryologist's terminal. Figure 26 is a pop-up display screen for embryo images. Figure 27 is an example of a hormone cycle screen on a doctor's terminal. Figure 28 is an example of a thawing ET screen on an embryologist's terminal. Figure 29 is an example of a thaw target selection screen. Figure 30 is another example of the egg retrieval ET screen on the embryologist terminal. Figure 31 is an example of a post-pregnancy medical record screen on the doctor's terminal. Figure 32 is an example of a referral letter pop-up display screen. Figure 33 is an example of a consent form list screen on the embryologist terminal. Figure 34 is an example of a consent form confirmation pop-up display screen. Figure 35 is an example of a consent form copy pop-up display screen. Figure 36 is an example of a sperm test / freezing screen on the embryologist terminal. Figure 37 is another example of the egg retrieval cycle screen on the doctor's terminal. Figure 38 is an example of a consent form submission screen. Figure 39 is an example of an examination / treatment results report screen.Fig. 40 is an example of a medication / drug administration management screen. Fig. 41 is an example of a patient learning screen. Fig. 42 is an example of a medication / drug administration management screen. Fig. 43 is another example of an egg collection cycle screen on a doctor's terminal. Fig. 44 is an example of a hormone cycle screen on a doctor's terminal. Fig. 45 is an example of a dashboard screen.

[0008] The reproductive medicine support system, reproductive medicine support method, and program according to the present technology will be described below with reference to the drawings as appropriate. Note that the content displayed in each drawing is for the purpose of explaining the present technology, and may not necessarily be the same as the actual content displayed, and there may be cases where consistency between drawings is not achieved.

[0009] [Reproductive medicine support system] Fig. 1 shows an example of the overall configuration of a reproductive medicine support system 1 according to one embodiment. The reproductive medicine support system 1 according to the present technology is typically a system in the field of reproductive medicine, where doctors and embryologists work together to support patients.

[0010] In this specification, reproductive medicine broadly refers to medical treatments performed to achieve pregnancy. Reproductive medicine is typically medical treatment performed to address infertility, and includes, for example, assisted reproductive technology (ART), reproductive medicine, and assisted reproductive medicine. However, reproductive medicine also includes, for example, tests such as ovarian reserve tests and semen tests that are performed independently, as well as partial or preliminary medical treatments performed for the purpose of reproduction, such as cryopreservation of eggs and sperm, artificial insemination, and timing therapy.

[0011] As shown in Figure 1, the reproductive medicine support system 1 is composed of one or more management servers 101, one or more doctor terminals 102, and one or more embryologist terminals 103. The reproductive medicine support system 1 may also additionally include one or more patient terminals 104 and one or more medical devices 105. The management server 101, doctor terminal 102, embryologist terminal 103, patient terminal 104, and medical device 105 are each capable of transmitting and receiving authorized information to and from each other via a wired or wireless network.

[0012] Here, for example, one or more doctor terminals 102 form an intra-medical institution network. Furthermore, in the intra-medical institution network, for example, one or more doctor terminals 102 form an independent doctor terminal network, and each doctor terminal 102 is provided with a doctor's business application suitable for performing doctor duties. Furthermore, the intra-medical institution network and the embryologist terminal network are connected via the Internet, and the authentication module of the doctor terminal 102 and the authentication module of the embryologist terminal 103 can connect to each other through authentication. Furthermore, one or more patient terminals 104 are terminals outside the medical institution that are not permitted to connect to the intra-medical institution network, and are configured to be able to connect to the reproductive medicine support system 1 via the Internet. The patient terminal 104 is provided with, for example, a patient business application suitable for receiving reproductive medicine support services for patients. Furthermore, the management server 101 is connected to the intra-medical institution network and the embryologist terminal network via the Internet, and the authentication module of the doctor terminal 102 and the embryologist terminal 103 can connect to the management server through authentication. The authentication module of the management server determines whether or not authentication is possible from the authentication module of the doctor terminal 102 and the authentication module of the embryologist terminal 103 .

[0013] The doctor terminal 102, the embryologist terminal 103, and the patient terminal 104 (hereinafter, the doctor terminal 102, the embryologist terminal 103, and the patient terminal 104 may be simply referred to as "terminals") in the reproductive medicine support system 1, and the management server 101 may each be, for example, a mobile terminal such as a smartphone, tablet, mobile phone, or personal digital assistant (PDA), or a wearable terminal such as glasses (including goggles), a wristwatch, or a clothing-type device. Furthermore, each terminal and the management server 101 may be a stationary or mobile computer, or a server located on a cloud or network. Furthermore, from a functional standpoint, they may be a VR (Virtual Reality) terminal, an AR (Augmented Reality) terminal, or an MR (Mixed Reality) terminal. Alternatively, each terminal and the management server 101 may be a combination of these. For example, a combination of one smartphone and one wearable terminal may logically function as a single terminal. Each terminal may also be an information processing terminal other than those mentioned above.

[0014] Each terminal and management server 101 of the reproductive medicine support system 1 may optionally include a processor that executes an operating system, applications, programs, etc., a main storage device such as RAM (Random Access Memory), an auxiliary storage device such as an IC card, hard disk drive, SSD (Solid State Drive), or flash memory, a communication control unit such as a network card, wireless communication module, or mobile communication module, input devices such as a touch panel, keyboard, mouse, audio input device, motion controller, or input device that detects motion by capturing images from a camera unit, input devices such as sensors such as GPS, gyro sensor, or acceleration sensor, and output devices such as a monitor or display. Note that the output device may be a device or terminal that transmits information to be output to an external device such as a monitor or display, printer, audio output device, or oscillator.

[0015] The main memory stores various programs and applications (software modules), and the processor executes these programs and applications to realize each functional element of the overall system. Each module may be implemented as an independent program or application, or as a subprogram or function within a single integrated program or application. Each module may also be implemented as hardware (hardware modules) by integrating circuits or using a microcomputer.

[0016] Furthermore, each module may be implemented by a single processor or multiple processors. Furthermore, each module may be provided in a single terminal or management server 101, or may be provided separately in two or more terminals or management servers 101 interconnected via a network. Furthermore, each module may be provided in each or any one or more of two or more terminals or management servers 101 interconnected via a network. It is also possible that some modules are implemented in a different country from the other modules.

[0017] In this specification, each module is described as the entity (subject) that performs the processing, but in reality, the processing is performed by a processor executing programs, applications, etc. to realize each module.

[0018] The auxiliary storage device stores various databases (DBs). A "database" is, for example, a set of data organized and collected so that it can accommodate arbitrary data operations (e.g., extraction, addition, deletion, overwriting, etc.) from a processor or an external computer. The type of data is not particularly limited and may be, for example, text data, audio data, image data, video data, 3D data, programs, etc. The auxiliary storage device is a functional element (storage unit) that stores one or more sets of data. The implementation method of the database is not limited to this example and may be, for example, a database management system, spreadsheet software, or text files such as XML or JSON. Some or all of this information may be stored in a relational database or a non-relational database. The database may be provided independently of the processor, while being connectable to the processor, etc. For example, various types of data may be distributed across multiple database servers or cloud applications.

[0019] [Management Server] Fig. 2 illustrates an example of the hardware configuration of the management server 101. The management server 101 manages the operation of the reproductive medicine support system 1. The management server 101 is configured, for example, by a server deployed on the cloud. The management server 101 can typically be a terminal used by an administrator who manages the reproductive medicine support system 1.

[0020] The management server 101 includes a main storage device 201 and an auxiliary storage device 202. The management server 101 also includes a processor 203, an input device 204, an output device 205, and a communication control unit 206 as described above.

[0021] The main memory device 201 stores programs and applications such as a management module 211, an acquisition module 212, a doctor terminal output module 213, a clinical technician terminal output module 214, a first prescription module 215, a second prescription module 216, a referral letter output module 217, a medical record information extraction module 218, a consent form information management module 219, a semen evaluation module 220, an estimation module 250, and a patient terminal output module 251. Each functional element of the management server 101 is realized by the processor 203 executing these programs and applications stored in the main memory device 201.

[0022] The auxiliary storage device 202 stores information necessary for the operation of the management server 101 in the reproductive medicine support system 1. The auxiliary storage device 202 stores, as examples of information related to the present technology, medical information such as patient information 221, partner information 222, treatment information 223, owned drug information 224, consent form information 225, embryo information 226, sperm management information 227, drug information 228, prescription schedule information 229, and freezing management information 230, as well as a machine learning model P. Details of this information will be described later. The auxiliary storage device 202 may also include various other information besides the above information.

[0023] A brief description of each functional element of the management server 101 follows. The management module 211 comprehensively controls the basic operation of the management server 101 for implementing the reproductive medicine support system 1. The management module 211 outputs (displays) on the doctor terminal 102, for example, a top screen of the reproductive medicine support application for using the reproductive medicine support system 1, a patient information screen, a treatment plan screen, a general infertility screen, an egg collection cycle screen, a hormone cycle screen, a natural cycle screen, a post-pregnancy chart screen, an emergency visit screen, and the like. The management module 211 also outputs (displays) on the embryologist terminal 103, for example, a top screen of the reproductive medicine support application, a patient information screen, a consent form list screen, an egg collection ET screen, a freezing management screen, a thawing ET screen, a semen test / freezing screen, and the like. The management module 211 outputs information entered or recorded in specific fields on these screens in accordance with the screen. The management module 211 presents various information related to reproductive medicine to doctors and embryologists via these screens and supports the doctors and embryologists in smoothly providing reproductive medicine to patients.

[0024] In addition, in order to realize the reproductive medical support system 1, the management module 211, for example, coordinates the operations of each module, such as the acquisition module 212, doctor terminal output module 213, embryologist terminal output module 214, first prescription module 215, second prescription module 216, referral letter output module 217, medical record information extraction module 218, consent form information management module 219, semen evaluation module 220, estimation module 250, and patient terminal output module 251, as necessary.

[0025] The acquisition module 212 acquires medical information related to the patient's reproductive medicine. The acquisition module 212 acquires, for example, patient information 221, partner information 222, treatment information 223, owned medication information 224, consent form information 225, embryo information 226, sperm management information 227, medication information 228, prescription schedule information 229, and freezing management information 230, which are transmitted via the Internet from the doctor terminal 102, the embryologist terminal 103, the patient terminal 104, the medical device 105, etc. The acquisition module 212 acquires this information, for example, through the above-mentioned screen, and stores the acquired information in the auxiliary storage device 202. Note that the storage of information by the acquisition module 212 may include new storage of information, addition of information, modification of information, deletion of information, etc. Furthermore, in this specification, the phrase "accepting input" by the acquisition module 212, etc. refers to the acquisition module 212, etc. receiving input information and recording the input information in, for example, the auxiliary storage device 202 (the same applies to other terminals).

[0026] The doctor terminal output module 213 outputs information acquired from the embryologist terminal 103 to the doctor terminal 102. The doctor terminal output module 213 outputs, for example, status information acquired from the embryologist terminal 103, which is information relating to the status of at least one of an egg, an embryo, a culture medium, or a sperm, to the doctor terminal 102 via the Internet. The doctor terminal output module 213 may also be configured to output, for example, test information acquired by the medical device 105, which is information relating to at least one of an egg, an embryo, a culture medium, or a sperm, to the doctor terminal 102. The doctor terminal output module 213 is configured to output, for example, predetermined information from the information acquired by the embryologist terminal 103 or the medical device 105 to the doctor terminal 102.

[0027] The embryologist terminal output module 214 outputs information acquired from the doctor terminal 102 to the embryologist terminal 103. The embryologist terminal output module 214 outputs, for example, treatment information 223, which is information related to the treatment of the patient, acquired from the doctor terminal 102, to the embryologist terminal 103 via the Internet. The embryologist terminal output module 214 may also be configured to output, for example, test information, which is information related to at least one of eggs, embryos, culture medium, or sperm, acquired by the medical device 105, to the embryologist terminal 103. The embryologist terminal output module 214 is configured to output, for example, permitted information from the treatment information 223 to the embryologist terminal 103.

[0028] The first prescription module 215 assists in inputting prescription information for drugs at the doctor terminal 102. The first prescription module 215 acquires information on the prescribed drug and the prescription date, and automatically outputs other prescription information based on the acquired information and predetermined rules.

[0029] The second prescription module 216 supports input of drug prescription information at the doctor terminal 102. The second prescription module 216 acquires information regarding the name and date of treatment for the patient, and automatically outputs prescription information based on the acquired information and predetermined rules.

[0030] The referral letter output module 217 supports the creation of a medical information report (hereinafter, sometimes simply referred to as a "referral letter") to another medical institution on the doctor terminal 102. The referral letter output module 217, for example, extracts information related to a referral letter associated with a patient from the acquired medical information, and outputs the information in association with a pre-prepared referral letter format.

[0031] The medical record information extraction module 218 supports the recording of medical information in the electronic medical record. The medical record information extraction module 218 extracts, for example, information related to predetermined medical record items from the medical information acquired in the reproductive medicine support system 1. The medical record information extraction module 218 may be configured to output, for example, the extracted information related to the predetermined medical record items.

[0032] The consent form information management module 219 supports the management of information related to consent forms. In the field of reproductive medicine, the types of consent forms handled and the frequency of collection are significantly greater than in other medical fields. The consent form information management module 219 supports the collection of consent forms and the management of information related to consent forms.

[0033] The semen evaluation module 220 supports evaluation of semen based on information related to semen testing. For example, based on the information related to the patient's semen testing, if the information related to the semen testing satisfies a predetermined standard, the semen evaluation module 220 outputs information indicating that the patient's semen satisfies the predetermined standard, and if the information related to the semen testing does not satisfy the predetermined standard, the semen evaluation module 220 outputs information indicating that the patient's semen does not satisfy the predetermined standard.

[0034] The estimation module 250 outputs reference information related to diagnosis and judgment of infertility treatment. For example, based on the acquired information, the estimation module 250 generates and outputs information useful for various diagnoses related to the patient's infertility treatment, determining treatment policies, etc., through data analysis and artificial intelligence (AI) prediction. The estimation module 250 outputs the generated information to, for example, the doctor terminal 102 or the embryologist terminal 103. The estimation module 250 is, for example, an example of an embryo classification unit in the present technology. For example, when classifying an embryo to be evaluated based on an image of the embryo, the estimation module 250 may be configured to realize an annotation function that adds annotations to the image of the embryo.

[0035] The patient terminal output module 251 outputs various types of information related to infertility treatment to the patient terminal 104. For example, the patient terminal output module 251 outputs, via the Internet, to the patient terminal 104, the top screen of the patient application for using the reproductive medicine support system 1, a consent form submission screen, an examination / diagnosis result report screen, a medication / medication management screen, a patient learning screen, and the like. The patient terminal output module 251 outputs predetermined information to the patient terminal 104 at predetermined times in accordance with the service provision program for the patient terminal, or based on instructions from the doctor terminal 102 or the embryologist terminal 103.

[0036] A brief description will be given of each piece of information stored in the auxiliary storage device 202. FIG. 6 shows examples of the contents of (A) patient information, (B) partner information, (C) treatment information, (D) owned medication information, (E) consent form information, and (F) embryo information. FIG. 7 shows examples of the contents of (G) sperm management information, (H) medication information, (I) prescription schedule information, and (J) freezing management information. All of this information (A) to (J) is an example of medical information. Note that the classification and storage method of this various information is not limited to this example.

[0037] The patient information 221 is basic information about the attributes of a female patient. The patient may be, for example, a patient who will become pregnant, or a patient from whose body eggs will be extracted. In this embodiment, the patient information 221 may include, for example, identification information such as a patient ID, name, date of birth, information about the partner (e.g., male spouse) who will be the partner for achieving pregnancy, height, weight, BMI value, allergy information, medical history, menstrual cycle, pregnancy history, etc. These items are associated with each other, for example, by the patient ID (the same applies to the contents of each piece of information below in that they are associated with each other).

[0038] The partner information 222 is basic information related to the attributes of the male patient. In this embodiment, the partner information 222 may include, for example, identification information such as a partner ID, name, date of birth, information (e.g., patient ID) of the partner (e.g., female spouse) with whom the pregnancy is to occur, height, weight, BMI value, allergy information, medical history, etc. For example, the partner information 222 is associated with identification information (e.g., patient ID) of the corresponding patient. Note that the patient and partner are typically human, but may also be non-human living organisms. Furthermore, when interpreting this technology, the genders of the patient and partner may be interchanged.

[0039] The treatment information 223 is information based on the doctor's medical practice. The treatment information 223 may be, for example, information related to the doctor's treatment of the patient, such as the date of consultation, medical findings, treatment (administration), prescribed medication, eggs, sperm, culture medium, and embryos, associated with the patient's identification information (e.g., patient ID or partner ID). In this embodiment, the treatment information 223 typically refers to information related to the patient's examination, diagnosis, treatment, etc., acquired from the doctor terminal 102, as well as instruction information related to treatment of the eggs, sperm, culture medium, and embryos. The treatment information 223 is not limited to current and past treatment information recorded using the reproductive medicine support system 1, but may also include future treatment plans. The treatment information 223 may also include instruction information related to reproductive medicine from the doctor to the embryologist (e.g., instructions for treatment of at least one of the eggs, embryos, culture medium, and sperm). The treatment information 223 may also include, for example, information recorded by a nurse or the like under the supervision of the doctor. The treatment information 223 may be, for example, other medical information excluding basic information (such as the above-mentioned patient information 221 and partner information 222, drug information 228, prescription schedule information 229, etc.) and information recorded, managed, evaluated, or judged by an embryologist. Conventionally, such treatment information 223 has not been provided to a personal computer used by an embryologist in his / her work or to an embryo or semen evaluation system.

[0040] The owned drug information 224 is information about drugs that are prescribed in relation to reproductive medicine and that the patient and their partner already own. The owned drug information 224 may be, for example, patient identification information (e.g., patient ID or partner ID), the name of the owned drug or the name of the active ingredient, the dosage, the number of drugs owned, etc. The owned drug information 224 may also include, for example, information about the expiration date, expiration date, and storage status.

[0041] The consent form information 225 is information relating to a consent form required in relation to reproductive medicine. The consent form information 225 may be, for example, patient identification information (e.g., patient ID or partner ID), consent form identification information, corresponding procedure name, recipient, receipt date, etc. The consent form information 225 may also include, for example, information relating to the name of the person who distributed it to the patient, the distribution date, the person who explained it, etc.

[0042] The embryo information 226 is information related to the collection, manipulation (treatment), culture, preservation (including cryopreservation), test results, etc. of the ovum or embryo. The embryo information 226 may be, for example, patient identification information (e.g., patient ID), ovum collection date, fertilization method, storage location, status (including progress) and number of fertilized eggs / embryos / culture medium / frozen embryos. The embryo information 226 may include, for example, information related to the characteristics of the ovum or embryo acquired by the medical device 105 (test results, measurement results, observation images, evaluation results, etc.), and may include, for example, time-lapse images of the embryo. The embryo information 226 may also include, for example, partner identification information (e.g., partner ID).

[0043] The sperm management information 227 is information relating to the collection of semen or sperm, semen testing, storage (including cryopreservation), etc. The sperm management information 227 may be, for example, patient identification information (e.g., partner ID), semen testing information (e.g., the date and time of collection of semen or sperm (and furthermore, the partner's age at the date and time of collection of semen or sperm), test results, measurement results, observation images, evaluation results, etc.), storage location, frozen sperm condition, quantity, etc.

[0044] The drug information 228 is information about drugs prescribed to patients in relation to reproductive medicine. The drug information 228 may be, for example, drug identification information, pharmaceutical name or active ingredient name, dosage, number, etc. The drug information 228 may also include, for example, information about corresponding treatments and symptoms. The drug information 228 may be information about drugs handled by medical institutions that use this reproductive medicine support system 1, or may include information about drugs not handled by these medical institutions.

[0045] The prescription schedule information 229 is information regarding the combination and amount of medications prescribed for each reproductive medical procedure or symptom, as well as the prescription timing. The prescription schedule information 229 may be information regarding, for example, the procedure, prescribed medication, dosage, prescription start date, prescription period, etc. Specifically, the prescription schedule information 229 records, for each procedure, standard information such as the combination of prescribed medications and the dosage of each prescribed medication, prescription start date, prescription period, etc. in association with each other.

[0046] The freezing management information 230 is management information of a freezing management device for managing frozen eggs, embryos, culture fluid, sperm, etc. The freezing management information 230 may be, for example, information relating to identification information of the freezing management location (e.g., a freezing management ID), information specifying the freezing management location (e.g., identification color of a freezing tank, canister, cane, or cryotube), etc.

[0047] The machine learning model P is a trained model configured to output a solution with a high probability of success for a specific patient when the patient's information is used as input information. For example, the machine learning model M estimates various conditions for maximizing the pregnancy rate from various patient information. Specifically, the machine learning model P estimates, for example, from various patient information, the egg collection date that maximizes the number of eggs to be collected and the number of eggs to be collected in that case.

[0048] [Doctor's Terminal] Figure 3 shows an example of the hardware configuration of the doctor's terminal 102. The doctor's terminal 102 is an element for inputting and outputting basic information and medical information of a patient in the reproductive medicine support system 1. The doctor's terminal 102 is typically used by a doctor. Use of the doctor's terminal 102 by anyone other than a doctor may be restricted. Information input to the doctor's terminal 102 is typically treatment information input by a doctor. The doctor's terminal 102 is configured, for example, by a personal computer, a mobile terminal, etc.

[0049] The doctor terminal 102 includes a main memory device 301 and an auxiliary memory device 302. The doctor terminal 102 also includes the above-described processor 303, input device 304, output device 305, and communication control unit 306. The doctor terminal 102 may also include an imaging device such as a camera (not shown).

[0050] The main memory device 301 stores programs and applications such as a doctor terminal management module 311, a doctor terminal acquisition module 312, a display module 313, a first prescription module 315, a second prescription module 316, a referral letter output module 317, a medical record information extraction module 318, a consent form information management module 319, a semen evaluation module 320, and a doctor terminal-side patient collaboration module 351. Each functional element of the doctor terminal 102 is realized by the processor 303 executing these programs and applications stored in the main memory device 301.

[0051] The auxiliary storage device 302 stores information necessary for the operation of the doctor terminal 102 in the reproductive medicine support system 1. The auxiliary storage device 302 stores medical information such as patient information 321, partner information 322, treatment information 323, owned drug information 324, consent form information 325, embryo information 326, sperm management information 327, drug information 328, prescription schedule information 329, and freezing management information 330, as examples of information related to the present technology. Such information may be part or all of the various information stored in the auxiliary storage device 202 of the management server 101.

[0052] The doctor terminal management module 311 comprehensively controls the basic operations of the doctor terminal 102 in the reproductive medicine support system 1. In cooperation with the management module 211 of the management server 101, the doctor terminal management module 311 outputs (displays) on an output device 205 such as a display, for example, a top screen of the doctor terminal application for using the reproductive medicine support system 1, a patient information screen, a treatment plan screen, a general infertility screen, an egg collection cycle screen, a hormone cycle screen, a natural cycle screen, a post-pregnancy chart screen, an emergency visit screen, etc. The doctor terminal management module 311 presents various information related to reproductive medicine to doctors via these screens and accepts input from doctors using the doctor terminal 102.

[0053] The doctor terminal acquisition module 312, display module 313, first prescription module 315, second prescription module 316, referral letter output module 317, medical record information extraction module 318, consent form information management module 319, and semen evaluation module 320 each work in conjunction with, for example, the acquisition module 212, doctor terminal output module 213, first prescription module 215, second prescription module 216, referral letter output module 217, medical record information extraction module 218, consent form information management module 219, and semen evaluation module 220 of the management server 101 to display information acquired from the management server 101 via the Internet on the doctor terminal 102, or to send information from the doctor terminal 102 to the management server 101 via the Internet.

[0054] The doctor terminal side patient collaboration module 351 works in conjunction with the patient terminal output module 251 of the management server 101 to output specified information to the patient terminal 104 via the management server 101, and to display information from the patient terminal 104 on the doctor terminal 102 via the management server 101.

[0055] [Embryologist Terminal] FIG. 4 shows an example of the hardware configuration of the embryologist terminal 103. The embryologist terminal 103 is an element for inputting and outputting assisted reproductive technology information related to the embryologist in the reproductive medicine support system 1. The embryologist terminal 103 is typically used by the embryologist. For example, the embryologist performs semen testing, sperm preparation for artificial insemination, in vitro fertilization, intracytoplasmic sperm injection, embryo culture, embryo freezing, sperm freezing, and embryo transfer assistance for the collected eggs and sperm of the patient and / or partner. Accordingly, the embryologist manages various types of information related to the eggs, sperm, and embryos. The information input to the embryologist terminal 103 is typically medical information input by the embryologist. The embryologist terminal 103 is configured, for example, by a personal computer, a mobile terminal, or the like. The embryologist terminal is a device located outside the medical institution where the doctor's terminal is located.

[0056] The embryologist terminal 103 comprises a main memory device 401 and an auxiliary memory device 402. The embryologist terminal 103 also comprises the processor 403, input device 404, output device 405, and communication control unit 406, as described above. The embryologist terminal 103 may also comprise an imaging device such as a camera (not shown).

[0057] The main memory device 401 stores programs and applications such as an embryologist terminal management module 411, an embryologist terminal acquisition module 412, a display module 414, a consent form information management module 419, and a semen evaluation module 420. Each functional element of the embryologist terminal 103 is realized by the processor 403 executing these programs and applications stored in the main memory device 401.

[0058] The auxiliary storage device 402 stores information necessary for the operation of the embryologist terminal 103 in the reproductive medicine support system 1. The auxiliary storage device 402 stores medical information such as patient information 421, partner information 422, treatment information 423, owned drug information 424, consent form information 425, embryo information 426, sperm management information 427, drug information 428, prescription schedule information 429, and freezing management information 430, as examples of information related to the present technology. Such information may be a part or all of the various information stored in the auxiliary storage device 202 of the management server 101.

[0059] The embryologist terminal management module 411 comprehensively controls the basic operations of the embryologist terminal 103 in the reproductive medicine support system 1. The embryologist terminal management module 411 cooperates with the management module 211 of the management server 101 connected via the Internet, and outputs (displays) on an output device 405 such as a display, for example, the top screen of the embryologist terminal application for using the reproductive medicine support system 1, a patient information screen, a consent form list screen, an egg collection ET screen, a freezing management screen, a thawing ET screen, a semen test / freezing screen, etc. The embryologist terminal management module 411 presents various information related to reproductive medicine to the embryologist via these screens, and accepts input from the embryologist using the embryologist terminal 103.

[0060] The embryologist terminal acquisition module 412 works in conjunction with the acquisition module 212 of the management server 101 to transmit information regarding eggs, sperm, and embryos, information regarding consent forms, information regarding semen evaluation, and the like that has been input by the embryologist into the embryologist terminal 103 to the management server 101. The embryologist terminal acquisition module 412 also works in conjunction with the acquisition module 212 to display the information output by the management server 101 on the embryologist terminal 103.

[0061] The display module 414 works in conjunction with the embryologist terminal output module 214 of the management server 101 to display information (including treatment information 423) sent from the management server 101 on the embryologist terminal 103. The consent form information management module 419 works in conjunction with the consent form information management module 219 of the management server 101 to read information related to the consent form from the management server 101 and display it on the embryologist terminal 103. The semen evaluation module 420 works in conjunction with the semen evaluation module 220 of the management server 101 to read information related to semen evaluation from the management server 101 and display it on the embryologist terminal 103.

[0062] The patient collaboration module 451 on the culture technician terminal works in conjunction with the patient terminal output module 251 of the management server 101 to output specified information to the patient terminal 104 via the management server 101, and to display information from the patient terminal 104 on the culture technician terminal 103 via the management server 101.

[0063] [Patient Terminal] Fig. 5 shows an example of the hardware configuration of the patient terminal 104. The patient terminal 104 is a terminal used by a patient who visits a medical institution that uses this reproductive medicine support system 1. The patient terminal 104 is configured by, for example, a personal computer, a smartphone, or the like.

[0064] The patient terminal 104 includes a main memory device 501 and an auxiliary memory device 502. The patient terminal 104 also includes a processor 503, an input device 504, an output device 505, a camera 506, and a communication control unit 507 as described above.

[0065] The main memory device 501 stores programs and applications such as a patient terminal management module 511 and a consent form submission module 519. Each functional element of the patient terminal 104 is realized by the processor 503 executing these programs and applications stored in the main memory device 501. Note that the consent form submission module 519 is an additional element and is not an essential component.

[0066] The auxiliary storage device 502 stores information necessary for the operation of the patient terminal 104 in the reproductive medicine support system 1. The auxiliary storage device 502 stores, for example, patient information 521, partner information 522, consent form information 525, etc. This information may be some or all of the patient information 221, partner information 222, and consent form information 225 stored in the auxiliary storage device 202 of the management server 101.

[0067] The patient terminal management module 511 comprehensively controls the basic operations of the patient terminal 104 in the reproductive medicine support system 1. The patient terminal management module 511 cooperates with the management module 211 of the management server 101 to output (display) on an output device 505 such as a display, for example, a top screen of a patient terminal application for using the reproductive medicine support system 1, a consent form submission screen, a medication / drug administration management screen, etc. The patient terminal management module 511 presents various information related to reproductive medicine to the patient via these screens and accepts input from the patient using the patient terminal 104.

[0068] The consent form submission module 519 additionally supports the submission of consent forms by patients in the reproductive medicine support system 1. The consent form submission module 519 works in conjunction with the consent form information management module 219 of the management server 101 to output a consent form form to the patient terminal 104 and to transmit the consent form that the patient has filled out and signed (or a copy thereof (for example, an information file in PDF format)) from the patient terminal 104 to the management server 101.

[0069] [Medical Devices] The medical devices 105 are various measuring instruments, analyzers, and measurement / analysis systems used in reproductive medicine. Examples of the medical devices 105 include medical devices that are mainly installed in incubation rooms, such as biological microscopes, intracytoplasmic sperm injection systems, sperm characteristic analyzers, incubators (including time-lapse incubators capable of capturing time-lapse images), and laser-assisted hatching (LAH) devices, as well as medical devices that are installed outside incubation rooms, such as X-ray imaging devices, ultrasound diagnostic imaging devices, hormone measuring devices, and fallopian tube / hysteroscope treatment devices.

[0070] [Reproductive Medicine Support Method] [Linkage Between Doctor Terminal and Embryologist Terminal 1] Next, a method for supporting the work of doctors and / or embryologists using the reproductive medicine support system 1 will be described. The doctor, for example, executes a reproductive medicine support program for the doctor terminal stored in the auxiliary storage device 302 of the doctor terminal 102. The embryologist, for example, executes a reproductive medicine support program for the embryologist terminal stored in the auxiliary storage device 402 of the embryologist terminal 103. The doctor terminal management module 311 of the doctor terminal 102 and the embryologist terminal management module 411 of the embryologist terminal 103 then launch a reproductive medicine support application and connect to the management server 101. The management module 211 of the management server 101 cooperates with the doctor terminal management module 311 and the embryologist terminal management module 411 to output (display) a predetermined screen of the reproductive medicine support application to the output devices 305, 405, such as displays, of the doctor terminal 102 and the embryologist terminal 103.

[0071] The acquisition module 212 of the management server 101 cooperates with the doctor terminal acquisition module 312 to acquire treatment information 223 that, for example, a doctor has input into the doctor terminal 102 via the screen of the reproductive medicine support application. In addition, the acquisition module 212, consent form information management module 219, and semen evaluation module 220 of the management server 101 cooperate with the embryologist terminal acquisition module 412, consent form information management module 419, and semen evaluation module 420 to acquire information on eggs, sperm, culture medium, and embryos that, for example, an embryologist has input into the embryologist terminal 103 via the screen of the reproductive medicine support application. The acquired information is stored, for example, in the auxiliary storage device 202.

[0072] Fig. 8 is an example of a reproductive medicine support flow. Fig. 9 is another example of a reproductive medicine support flow. Fig. 18 is an example of a patient information screen 1800 on the doctor terminal 102. Fig. 19 is an example of a patient information screen 1900 on the embryologist terminal 103. Figs. 18 and 19 are examples of patient information screens 1800, 1900 related to a specific patient designated by the doctor terminal 102 or embryologist terminal 103.

[0073] In the reproductive medicine support method of this embodiment, generally, the management server 101 acquires treatment information 223 related to the treatment of the patient as medical information from the doctor terminal 102 via the network (S810), and outputs the acquired treatment information 223 to the embryologist terminal 103 via the network upon request (S820). In addition, the management server 101 acquires information related to the status of at least one of the ovum, embryo, culture medium, or sperm from the embryologist terminal via the network (S910), and outputs the acquired status information to the doctor terminal 102 via the network upon request (S920).

[0074] Each step is described below. First, in the treatment information acquisition step (S810), as described above, the acquisition module 212 cooperates with the doctor terminal acquisition module 312 to acquire treatment information 223 entered by the doctor into the doctor terminal 102. Here, the acquisition module 212 extracts and acquires treatment information 223 that satisfies specific conditions from the treatment information 223 acquired from the doctor terminal 102 via the network. For example, the acquisition module 212 may transmit the patient ID of a specific patient to the doctor terminal 102 via the network, and the doctor terminal 102 may extract treatment information 223 corresponding to this patient ID, which may then be transmitted from the doctor terminal 102 to the acquisition module 212 of the management server 101. Alternatively, the acquisition module 212 may be configured to acquire the treatment information 223 of all or multiple patients from the doctor terminal 102 via the network and extract corresponding information from the treatment information 223 based on, for example, the patient ID of a specific patient. The acquisition module 212 extracts data by patient ID, and also receives input from an operator (e.g., a doctor or an embryologist) of the doctor terminal 102 or the embryologist terminal 103, and extracts, acquires, or transmits data that meets the conditions corresponding to this input. For example, these conditions may include, in addition to the patient ID, data on a specific age (e.g., in one's 40s), information identifying a patient such as the name of a specific patient, information identifying a treatment method or medication used, information identifying the evaluation results of embryos or sperm, or conditions representing a group of information set to be displayed on each screen, such as those exemplified in Figures 18 to 45.

[0075] The encryption module of the doctor terminal 102 can encrypt and transmit the treatment information 223. The acquisition module 212 transmits authentication information, such as a one-time password, to the doctor terminal 102, and the encryption module of the doctor terminal 102 can encrypt the treatment information 223 using this authentication information.

[0076] Furthermore, in the treatment information acquisition step (S910), as described above, the acquisition module 212 cooperates with the embryologist terminal acquisition module 412 to acquire information regarding the status of at least one of the ovum, embryo, culture medium, or sperm (hereinafter, sometimes simply referred to as "status information") from the embryologist terminal 103. Here, the acquisition module 212 extracts and acquires status information that meets specific conditions from the status information regarding the ovum, embryo, culture medium, or sperm acquired from the embryologist terminal via the network. The acquisition module 212 can, for example, transmit the patient ID of a specific patient to the embryologist terminal 103 via the network, and the embryologist terminal 103 can extract status information corresponding to this patient ID, which can then be transmitted from the embryologist terminal to the acquisition module 212 of the management server 101. The acquisition module 212 can also be configured to acquire status information for all or multiple patients from the embryologist terminal 103 via the network and extract corresponding information from this status information, for example, based on the patient ID of a specific patient. The acquisition module 212 extracts data by patient ID, and also receives input from an operator (e.g., a doctor or an embryologist) of the doctor terminal 102 or the embryologist terminal 103, and extracts, acquires, or transmits data that meets the conditions corresponding to this input. For example, these conditions may include, in addition to the patient ID, data on a specific age (e.g., in one's 40s), information identifying a patient such as the name of a specific patient, information identifying a treatment method or medication used, information identifying the evaluation results of embryos or sperm, or conditions representing a group of information set to be displayed on each screen, such as those exemplified in Figures 18 to 45.

[0077] The cryptographic module of the embryologist terminal 103 can encrypt and transmit the status information. The acquisition module 212 transmits authentication information, such as a one-time password, used at this time to the embryologist terminal 103, and the cryptographic module of the embryologist terminal 103 can encrypt the status information using this authentication information.

[0078] Then, in the treatment information output step (S820), the embryologist terminal output module 214 outputs the acquired treatment information 223 to the embryologist terminal 103 via the network upon request.

[0079] The culture technician terminal output module 214 receives, for example, the patient ID of a specific patient from the culture technician terminal 103 via the network, extracts treatment information 223 corresponding to this patient ID, and transmits the extracted treatment information 223 to the culture technician terminal 103, where it can be output on the culture technician terminal 103.

[0080] The embryologist terminal output module 214 extracts data by patient ID, and also accepts input from the operator (e.g., a doctor or embryologist) of the doctor terminal 102 or embryologist terminal 103, and extracts, acquires, or transmits data that meets the conditions corresponding to this input. For example, these conditions may include, in addition to the patient ID, data on a specific age (e.g., in one's 40s), information identifying a patient such as the name of a specific patient, information identifying the treatment method or medication used, information identifying the evaluation results of the embryo or sperm, information to be displayed in Figures 19, 25, 26, 28-30, 33-36, 45, etc.

[0081] The encryption module of the management server 101 or the embryologist terminal output module 214 can encrypt and transmit the treatment information 223. The encryption module of the embryologist terminal 103 transmits authentication information such as a one-time password to be used at this time to the management server 101, and the encryption module of the management server 101 or the embryologist terminal output module 214 can encrypt the treatment information 223 using this authentication information.

[0082] In the status information output step (S920), the doctor terminal output module 213 outputs the acquired status information to the doctor terminal 102 via the network upon request. For example, the doctor terminal output module 213 receives the patient ID of a specific patient from the doctor terminal 102 via the network, extracts the status information corresponding to this patient ID, and transmits the extracted status information to the doctor terminal 102, where it can be output.

[0083] The doctor terminal output module 213 extracts data by patient ID, and also receives input from the operator (e.g., a doctor or an embryologist) of the doctor terminal 102 or the embryologist terminal 103, and extracts, acquires, or transmits data that meets the conditions corresponding to this input. For example, these conditions may include, in addition to the patient ID, data on a specific age (e.g., in one's 40s), information identifying a patient such as the name of a specific patient, information identifying the treatment method or medication used, information identifying the evaluation results of the embryo or sperm, information to be displayed in Figures 18, 20 to 24, 27, 31, 32, 37, 45, etc.

[0084] The encryption module of the management server 101 or the doctor terminal output module 213 can encrypt and transmit the status information. The encryption module of the doctor terminal 102 transmits authentication information, such as a one-time password, to the management server 101, and the encryption module of the management server 101 or the doctor terminal output module 213 can use this authentication information to encrypt the status information.

[0085] 18 , the management module 211 displays a patient information tab 1810 on the display of the doctor terminal 102, and displays a patient information screen 1800 when the patient information tab 1810 is selected. The management module 211 displays, for example, basic patient information 1820, as well as measurement information, the patient's pregnancy history, medical history, allergy information, supplements currently being taken, treatment history 1830, a remaining medication management column 1840 (an example of owned medication information), partner information 1880, a treatment history calendar 1850, and the like on the patient information screen 1800. The management module 211 displays, for example, patient information 221, partner information 222, treatment information 223, owned medication information 224, sperm management information 227, and the like.

[0086] Then, when the acquisition module 212 acquires information on the status of at least one of the eggs, embryos, culture medium, or sperm from the embryologist terminal 103, the physician terminal output module 213 outputs the acquired status information to the physician terminal. In FIG. 18 , the physician terminal output module 213 displays, as status information, information 1860 on the most recent unprepared sperm and information 1870 on cryopreserved sperm. Through this screen, for example, the physician can roughly grasp the patient's basic information, medical treatment status, and medical treatment summary, as well as information on the sperm status, for example. This allows the physician to quickly grasp information on the sperm status (an example of status information) without having to individually contact the embryologist or launch a separate information system.

[0087] 19 , the management module 211 displays a patient information tab 1910 on the display of the culture technician terminal 103, and displays a patient information screen 1900 when the patient information tab 1910 is selected. The management module 211 displays, for example, basic information such as measurement information, medical history, allergy information, and partner information in addition to basic information 1920 of the patient on the patient information screen 1900. The management module 211 displays the patient information screen 1900 based on, for example, patient information 221, partner information 222, etc.

[0088] The embryologist terminal output module 214 then further displays treatment information 423, such as pregnancy history and treatment history 1930, on the patient information screen 1900, for example, based on the treatment information 223. If the acquisition module 212 has received the patient's past treatment information 423, the embryologist terminal output module 214 displays the past treatment information 423 on the embryologist terminal 103. If the acquisition module 212 has not received the patient's past treatment information 423, the embryologist does not display the past treatment information 423. For example, through this screen, the embryologist can roughly grasp the patient's basic information as well as medical information such as the medical history.

[0089] Traditionally, when an embryologist intervenes in reproductive medicine, it is the embryologist, not a physician, who makes the judgments and decisions regarding in vitro fertilization (including insemination) and incubation. Embryologists often receive physical medical records along with specimens such as eggs and sperm, and perform operations and record records such as artificial insemination and incubation in an isolated environment such as a clean room. Even in clinics that have insemination rooms within their facilities, it is common for them to be isolated from other in-hospital facilities (e.g., general examination rooms) on a floor-by-floor basis to create a clean room environment in accordance with laws, regulations, guidelines, etc. With the above configuration, embryologists can take more appropriate measures and make more appropriate decisions regarding eggs, sperm, and embryos, taking into account the patient's infertility treatment history and progress, for example, based on the information displayed on the embryologist terminal 103 within the clean room.

[0090] In recent years, more and more embryologists are explaining assisted reproductive technology to patients. Embryologists can quickly grasp treatment information 423, such as the history and progress of a patient's infertility treatment, which they are permitted to view, based on the information displayed on the embryologist terminal 103, without having to, for example, individually contact a doctor or personally interview the patient. This allows for better communication between embryologists and patients.

[0091] The embryologist terminal 103 requests various information from the management server 101 via the network at predetermined time intervals and in response to the operation of the embryologist terminal 103 by the embryologist, etc. For example, by setting the time interval for requesting information from the management server 101 to be short, or by configuring the information to be requested when the information in the auxiliary storage device 202 is updated, the embryologist terminal 103 can display new treatment information 423 in approximately real time.

[0092] FIG. 20 illustrates an example of an overall view 2000 of the treatment history calendar 1850 displayed on the doctor terminal 102. The management module 211 displays information indicating the treatment history and treatment plan in the treatment history calendar 1850 based on the patient information 221, the treatment information 223, and the like. The management module 211 displays various treatment cycles, such as cycles related to infertility treatment not including in vitro fertilization (general infertility), cycles involving egg retrieval (egg retrieval cycle 2010), embryo transfer cycles based on natural cycles (natural cycles), and embryo transfer cycles involving hormone injection (hormone cycle 2020), in different colors. The management module 211 also displays information regarding the start and end dates of each treatment cycle as text information such as "start" and "end." The management module 211 also displays information regarding treatment dates, such as the egg retrieval date 2015 and the transfer date 2025, in different colors. By glancing at the treatment history calendar 1850, a doctor can visually and clearly grasp the treatment plan and its progress for the patient.

[0093] The functions and operations of the other modules of the management server 101 will be described below. [Automatic prescription input 1] Fig. 10 is an example of an automatic prescription input flow. Fig. 21 is an example of an egg collection cycle screen on a doctor's terminal. Figs. 22(A) to (B2) are display examples of prescription drug input fields.

[0094] The management module 211 displays an egg collection cycle tab 2110 on the display of the doctor terminal 102, and displays an egg collection cycle screen 2100 when the egg collection cycle tab 2110 is selected. The management module 211 displays, for example, a treatment policy column, an important matters column, an ovarian stimulation method column 2140, a remaining medication management column 2150, a required procedure column 2160, a medical record input form for the egg collection cycle 2120, a prescribed medication input column 2130, etc. on the egg collection cycle screen 2100. The management module 211 displays the egg collection cycle screen 2100 based on, for example, patient information 221, treatment information 223, owned medication information 224, consent form information 225, medication information 228, prescription schedule information 229, etc.

[0095] In reproductive medicine, patients are often prescribed a variety of medications for several days at a time, which can be time-consuming and burdensome for doctors to input prescription information for various medications into the doctor terminal 102. Therefore, the first prescription module 215 executes the process described below to reduce the time and burden on the doctor.

[0096] First, the management module 211 outputs a medical record input table 2120, which displays, for example, dates, days of the week, menstrual cycles, etc. in a tabular, calendar-like format, to the egg collection cycle screen 2100. The management module 211 displays the medical record input fields for each day in ascending order row-wise on the medical record input table 2120, for example, with the medical record input field for the current day in the top row. The management module 211 also displays an automatic prescription input button as a "Do button" 2135 above each row of the prescription drug input field 2130.

[0097] When the doctor examines the patient on that day (here, "2022 / 12 / 23"), for example, the doctor selects cell C1 for that day in the "Visit Date" column in the medical record input table 2120 on the egg collection cycle screen 2100. The management module 211 then displays information "O" indicating that the patient has visited the hospital in a pull-down menu on the doctor terminal 102. When the doctor selects the information "O" indicating that this patient has visited the hospital, the acquisition module 212 accepts input of information indicating that that day is the visit date, and the management module 211 displays information "O" indicating the visit date in cell C1.

[0098] Next, the doctor selects cell C2, which is the "oral / nasal spray" column corresponding to the day of the visit, in the prescription drug input column 2130, for example, as shown in FIG. 22(A). Then, as shown in FIG. 22(A), the management module 211 displays a list of oral medications and nasal sprays that can be prescribed for the egg collection cycle in a pull-down menu based on the drug information 228. Then, when the doctor selects one of the drugs in the list (for example, Letrozole tablets 2.5 mg ("Retro 2.5 mg [1 tablet]")), the acquisition module 212 accepts information about the date and the selected drug as information about the prescription date and the prescribed drug. The management module 211 displays information indicating the selected prescription drug (for example, "Retro 2.5") in cell C2. The information accepted by the acquisition module 212 is stored, for example, in the auxiliary storage device 202 as treatment information 223.

[0099] <When the next visit date is not entered> Here, suppose that the doctor selects the "Do button" 2135 in the same column as cell C2 without entering information about the next visit date in the "Visit date" column. Then, the first prescription module 215, for example, refers to the treatment information 223 in the auxiliary storage device 202, acquires information about the prescription drug and prescription date displayed in the same column as the selected "Do button" 2135 (S1010), and determines whether information about the next visit date has been acquired (S1020). Here, the first prescription module 215 confirms that information about the next visit date has not been acquired (No in S1020), and outputs information indicating that the same prescription drug will be prescribed for each of a predetermined number of days from the prescription date (S1040). Specifically, as shown in FIG. 22 (B1), for example, the first prescription module 215 displays "Retro 2.5," which represents the same prescription drug as entered in cell C2, in the same column as the selected "Do button" 2135, in the column for the predetermined number of days (here, one tablet per day for five days), i.e., in the columns for each of the prescription dates from "2022 / 12 / 23" to "12 / 27." Furthermore, the first prescription module 215 stores, as treatment information 223, for example, in the auxiliary storage device 202, the prescription of the prescription drug "Retro 2.5 mg [1 tablet]" for each of the prescription dates from 2022 / 12 / 23 to 12 / 27.

[0100] With the above configuration, a doctor can enter, for example, "Retro 2.5" representing a prescription drug in each column from "2022 / 12 / 24" to "2022 / 12 / 27" with a single selection of the "Do button" 2135, without having to enter the date each time. Note that cell C2, where the doctor enters information about the prescription date and prescription drug, is not limited to the first row (the current day) but may be the second row or later (i.e., the next day or later). Furthermore, the prescription drug information entered in cell C2 is not limited to information entered on the current day. For example, it may be information about a prescription drug prescribed on the previous visit (previous consultation date). The number of days for which prescription drugs are automatically entered is not limited to five days and can be set arbitrarily, for example, to match a standard treatment cycle. Furthermore, the number of days for which prescription drugs are automatically entered may be set to a different number of days for each prescription drug.

[0101] <When the Next Visit Date is Input> It is possible that a patient may not be able to visit the hospital according to the standard treatment cycle. In such a case, for example, the doctor can prescribe medication for each day leading up to the next visit (next scheduled visit date). For example, as shown in FIG. 22 (B2), the doctor selects cell C3 in the "Visit Date" column, which corresponds to the patient's next available visit date (here, December 28th). The management module 211 then displays a "◯" (circle) indicating that the date is the patient's next visit date in a pull-down menu on the doctor terminal 102. When the doctor selects the "◯" (circle) indicating that the date is the patient's next visit date, the acquisition module 212 accepts input of information indicating that the selected date is the next visit date, and the management module 211 displays the "◯" (circle) indicating the next visit date in cell C3. The management module 211 stores, for example, in the auxiliary storage device 202, the fact that the date corresponding to cell C3 (here, December 28th) is the next visit date as treatment information 223.

[0102] Next, suppose the doctor selects the "Do button" 2135 in the same column as cell C3. The first prescription module 215 then references, for example, the treatment information 223 in the auxiliary storage device 202 to acquire information about the prescription drug and prescription date displayed in the same column as the selected "Do button" 2135 (S1010) and determines whether information about the next visit date has been acquired (S1020). Here, the first prescription module 215 confirms that information about the next visit date has been acquired (Yes in S1020) and outputs information indicating that the same prescription drug will be prescribed for each day from the prescription date to a predetermined date based on the next visit date (S1030). Specifically, as shown in FIG. 22 (B2), for example, the first prescription module 215 displays "Retro 2.5," representing the same prescription drug as entered in cell C2, in the columns for each day from the prescription date "2022 / 12 / 23" to the next visit date "12 / 28" in the same column as the selected "Do button" 2135. In addition, the first prescription module 215 stores, for example, in the auxiliary storage device 202 as treatment information 223, that the prescription drug "Retro 2.5 mg [1 tablet]" will be prescribed on each of the prescription dates 2022 / 12 / 23 to 12 / 28.

[0103] With the above configuration, a doctor can input the prescription drug "Retro 2.5" into each field for each day from "12 / 24" to "12 / 28," which corresponds to the patient's next visit date, by simply selecting the "Next Visit Date" and the "Do Button" 2135 twice. The days for automatically inputting the prescription drug may be set to include the next visit date or may not include the next visit date. For example, the first prescription module 215 may display information about prescribing the prescription drug for each day from the prescription date to the day before the next visit date. In this case, the first prescription module 215 stores, for example, in the auxiliary storage device 202, as treatment information 223, that the prescription drug "Retro 2.5 mg [1 tablet]" will be prescribed for each day from the prescription date to the day before the next visit date on each day from 12 / 23 / 2022 to 12 / 27 / 2022, from the prescription date to the day before the next visit date.

[0104] [Automatic Prescription Input 2] As shown in FIG. 18 , the management module 211 displays, for example, a remaining medication management field 1840 on the patient information screen 1800 of the doctor's terminal. Many medications are prescribed in reproductive medicine. However, patients may end up with prescription medications left over due to, for example, forgetting to take medication or delays in the patient's visit date or pregnancy assessment timing. Furthermore, patients may transfer to other hospitals due to moving or a lack of compatibility with the medical institution, and may still have prescription medications that were prescribed at their previous medical institution. If a patient has a large amount of medications (leftover medications), problems such as prescription drug shortages may arise. Therefore, doctors can obtain information from patients about the types and quantities of medications they own through interviews or other means. If the medications are still in sufficient supply, the reproductive medicine support system 1 can manage the patient's medications.

[0105] The doctor obtains information such as the type (including dosage) and quantity of the patient's owned medication and selects the "Drugs reported as remaining medications" field in the remaining medication management field 1840. Here, for example, assume that the doctor receives a report from the patient that the doctor owns two tablets of the prescription medication "Retro 2.5 mg [1 tablet]." The management module 211 then displays a list of pharmaceutical names in a pull-down menu on the doctor terminal 102 based on the medication information 228. When the doctor selects one of the drugs in the list (e.g., "Retro 2.5 mg [1 tablet]") and enters the number of drugs owned ("2") in the corresponding "Number of remaining drugs" field, the acquisition module 212 accepts information about the selected owned medication and its quantity and stores it in, for example, the owned medication information 224 in the auxiliary storage device 202. The management module 211 displays information about the owned medication and its quantity in the "Drugs reported as remaining medications" field and the corresponding "Number of remaining drugs" field. This allows the management server 101 to manage the patient's owned medications.

[0106] The following describes how to prescribe medicines when managing owned medicines. Figure 23 shows another example of the display of the prescription medicine input field. Figure 11 shows another example of the automatic prescription input flow. Figure 12 shows an example of the remaining medicine management flow.

[0107] As shown in FIG. 23 , for example, suppose a doctor prescribes the drug "Retro 2.5" for five days from December 23 to December 27, 2022. In this case, the patient takes the drug "Retro 2.5" for the first two days (December 23 and 24), and the doctor prescribes "Retro 2.5" for the remaining three days (December 25 to 27). In this case, the patient's drug "Retro 2.5" can be considered a virtual prescription. Therefore, the first prescription module 215 displays the text "Retro 2.5" in cell C4 for the first two days for which no drug is actually prescribed and in cell C5 for the remaining three days for which a drug is actually prescribed. The first prescription module 215 then displays a different display for cell C4 for the first two days for which no drug is actually prescribed from that for cell C5, so that it is clear that the prescription is virtual.

[0108] For example, the first prescription module 215 can decorate the text representing the medicine and cell C4 differently from other cells to indicate that the owned medicine is a virtually prescribed medicine. Examples of decorations performed by the first prescription module 215 include the following. -Decoration of the text representing the medicine (for example, displaying it in bold, thin, italic, different colored letters, different font letters, different size letters) -Decoration of the target cell in the "Medicines for which a remaining medicine report has been made" column (for example, applying a different color to the background of the cell, or decorating the outer frame of the cell with a line (thick line, thin line, dashed dot line, virtual line, double line, etc.)) -Displaying a mark (for example, a symbol or mark such as an asterisk or star mark) in the target cell in the "Medicines for which a remaining medicine report has been made" column

[0109] With this configuration, a doctor can understand, at a glance of the prescription drug input field 2300, that the patient will receive five days' worth of medication from December 23 to December 27, 2022, that the first two days' worth of medication are actually medications owned by the patient and will not be prescribed, and that the remaining three days' worth of medication are prescription medications to be actually prescribed. Furthermore, the doctor can prescribe the appropriate amount of medication, taking into account the patient's own medications. In other words, it is possible to reduce the prescribing of excess medication.

[0110] Next, an example of an automatic prescription flow 1100 and a remaining medication management flow 1200 for realizing such a display will be described. As shown in FIG. 11 , the first prescription module 215 first acquires information regarding the prescribed medication and the prescription date (S1110). This step is the same as step S1010 of the automatic prescription input flow 1000 of FIG. 10 . Next, the first prescription module 215 acquires information regarding the owned medication and the number of owned medications (S1120). For example, the first prescription module 215 acquires information indicating that two tablets of "Letrozole Tablets 2.5 mg" are owned as owned medications. If the prescribed medication is not the same as the patient's owned medication (No in S1130), the first prescription module 215 automatically prescribes the medication according to the normal procedure (S1150). For example, the first prescription module 215 follows the procedure from S1020 onward of the automatic prescription input flow 1000. On the other hand, if the prescribed drug is the same as the patient's owned drug (Yes in S1130), the first prescription module 215 outputs information indicating that the owned drug will be virtually prescribed as the prescribed drug (S1140).

[0111] Step S1140 will be described. In step S1140, for example, when the virtual prescription count of owned drugs does not reach the required prescription count of prescription drugs or the owned count of owned drugs, the first prescription module 215 may output information indicating that owned drugs are virtually prescribed as prescription drugs. Furthermore, when the first prescription module 215 virtually prescribes owned drugs as prescription drugs, the first prescription module 215 may output a number obtained by subtracting the number of virtually prescribed owned drugs as the owned count of owned drugs, and may output a number obtained by subtracting the virtual prescription count of owned drugs from the predetermined prescription count as the number of drugs to be actually prescribed.

[0112] More specifically, as shown in FIG. 12 , the first prescription module 215 manages the number of owned medications A owned by the patient, the virtual prescription number B when these owned medications are virtually prescribed, the required prescription number X, which is the number of prescription days for which the medication should be prescribed, and the prescription repetition number N (N is a natural number; initially, N = 1), which indicates the day of processing (S1205). Next, the first prescription module 215 outputs information indicating that the owned medication will be virtually prescribed to the cell for the Nth day (S1210). The first prescription module 215 then updates the virtual prescription number B of owned medications based on "B = N" (S1215). Here, the first prescription module 215 determines whether the prescription repetition number N reaches the required prescription number X of medications based on the formula: N ≧ X? (S1220). If the prescription repetition number N does not reach the required prescription number X (No in S1220), the first prescription module 215 updates the virtual prescription number B of owned medications based on the formula: B ≧ A? ;, it is determined whether the virtual prescription number B of the owned drugs has reached the owned number A of the owned drugs (S1225). If the virtual prescription number B of the owned drugs has not reached the owned number A of the owned drugs (No in S1225), the first prescription module 215 increments the prescription repetition number N by 1 (S1230) and returns to step S1210.

[0113] On the other hand, when the prescription repetition count N reaches the required prescription count X (Yes in S1220), it is considered that the drug prescription work has been completed, and the first prescription module 215 proceeds to the subsequent step S1250. Also, when the virtual prescription count B of owned drugs reaches the owned count A of owned drugs (Yes in S1225), the first prescription module 215 proceeds to the next step to continue prescribing prescription drugs.

[0114] The first prescription module 215 increments the prescription repetition number N by 1 (S1235) and outputs information indicating that the prescribed drug will be prescribed on the Nth day (S1240). Then, the first prescription module 215 determines whether the prescription repetition number N has reached the required prescription number X based on the formula: N≧X? (S1245). If the prescription repetition number N has not reached the required prescription number X (No in S1245), the first prescription module 215 returns to step S1235 and repeats the prescription of the prescribed drug. If the prescription repetition number N has reached the required prescription number X (Yes in S1245), the drug prescribing process is considered to be complete, and the first prescription module 215 proceeds to the next step.

[0115] The first prescription module 215 outputs the number of medications actually prescribed based on the formula: X - B (S1250). The first prescription module 215 also updates the patient's owned medication count A based on "A = A - B" (S1255) and outputs the updated owned medication count A (S1260). The first prescription module 215 updates the owned medication count A in the auxiliary storage device 202 and updates the "remaining medication count" value in the remaining medication management columns 1840 and 2150 to the owned medication count A. For owned medications for which the owned medication count A has become zero, the first prescription module 215 deletes the display in the "Remaining Medication Reported" column in the remaining medication management columns 1840 and 2150. This configuration allows the medical record input form 2120 and the remaining medication management column 2150 to be displayed appropriately without the doctor having to manually calculate the remaining medication count or manually change the display of the virtually prescribed owned medications.

[0116] [Automatic Prescription Input 3] Figure 13 shows another example of the automatic prescription input flow. Figures 24 (A) to (C) show examples of a portion of the egg collection cycle screen 2100. In reproductive medicine, various treatments are prepared according to the patient's condition, and the combination of prescribed medications and the timing of administration vary for each treatment. This can create a burden on the doctor, as they have to input prescription information for various medications into the doctor terminal 102. Therefore, the second prescription module 216 executes the processing described below to reduce the burden on the doctor.

[0117] As described above, the prescription schedule information 229 stores, for example, for each treatment, information such as the combination of prescription drugs, the dosage of each prescription drug, the prescription start date, and the number of prescription days. For example, ovulation induction methods for collecting eggs for in vitro fertilization are divided into three types: the controlled ovarian stimulation method, which collects many eggs with relatively strong stimulation; the semi-mild method, which uses relatively weak stimulation; and the mild method, which uses low stimulation. Furthermore, the controlled ovarian stimulation method can be further divided into, for example, the antagonist method, the long method, the short method, and the PPOS (Progestin Primed Ovarian Stimulation) method, based on the type of drug and the timing of administration. In the antagonist method, for example, the basic prescription schedule is set as follows: pills are taken during the previous menstruation, FSH injections or HMG injections are administered from the third day of the menstruation for about 9 to 14 days, antagonist injections are administered in combination when the follicles grow to 14 to 16 mm, and when the size of the follicles and hormone levels meet certain conditions, an HCG preparation is self-injected as a trigger, with eggs being collected 34 to 36 hours after the trigger.

[0118] As shown in FIG. 13, the second prescription module 216 acquires information regarding the treatment name and treatment date for the patient (S1310), and outputs information indicating that one or more medications will be prescribed according to a predetermined medication prescription schedule associated with the treatment name (S1320).

[0119] The step of acquiring information about the procedure name and procedure date (S1310) will be described. As shown in FIG. 21 , the management module 211 displays an ovarian stimulation method field 2140 and a "Reflect Designated Set" button 2145 for instructing automatic prescription input on the egg collection cycle screen 2100. When the doctor selects the ovarian stimulation method field 2140, the management module 211 displays a pull-down list of ovarian stimulation methods on the doctor terminal 102 based on the prescription schedule information 229, as shown in FIG. 24 (A), for example. When the doctor selects one of the ovarian stimulation methods in the list (e.g., "antagonist method"), the acquisition module 212 receives information that the ovarian stimulation method (procedure) for ovulation induction for the patient is the "antagonist method" and stores the information in, for example, the auxiliary storage device 202. The management module 211 displays information indicating the selected ovarian stimulation method in the ovarian stimulation method field 2140.

[0120] Next, the management module 211 displays a pop-up display screen for selecting the ovulation suppression start date (an example of a treatment date) on the egg collection cycle screen 2100, as shown in Fig. 24(B), for example. When the doctor selects the ovulation suppression start date (e.g., 2022 / 12 / 23) on the pop-up display screen, the acquisition module 212 accepts information that the selected date is the treatment date for the patient and stores it in, for example, the auxiliary storage device 202. Then, when the doctor selects the "Reflect specified set" button 2145, the second prescription module 216 calculates a combination of prescription drugs (including dosage) to be prescribed by the antagonist method and the prescription date, based on the prescription schedule information 229, with the ovulation suppression start date set to 2022 / 12 / 23, and displays the combination in the corresponding prescription drug input field 2130. 24(C) shows, for example, the second prescription module 216 displaying prescription information for "Retro 2.5" tablets, "Cetrotide 0.25 mg" injection, and "Gonal F Pen 300" injection for five days from 2022 / 12 / 23, which is the start date of ovulation suppression. The second prescription module 216 stores this prescription information in, for example, the auxiliary storage device 202. This allows the doctor to easily input prescription information while, for example, reducing input errors.

[0121] [Linkage between Doctor Terminal and Embryologist Terminal 2] <In the Case of Frozen Embryo Transfer> Figure 25 is an example of an egg retrieval ET (Embryo Transfer) screen 2500 on the embryologist terminal. Figure 26 is a pop-up display screen of an embryo image. The management module 211 displays an egg retrieval ET tab 2510 on the display of the embryologist terminal 103, and when the egg retrieval ET tab 2510 is selected, the egg retrieval ET screen 2500 is displayed. The management module 211 displays, for example, an egg retrieval order field, a sperm used field, a new egg retrieval result field, an egg retrieval result field, and a result details field 2520 on the egg retrieval ET screen 250 ... the egg retrieval ET screen 2500 based on, for example, the patient information 221, the treatment information 223, the embryo information 226, the sperm management information 227, etc. Note that, for example, the egg retrieval order field outputs information permitted to be provided to the embryologist terminal from the treatment information 323 acquired from the doctor terminal. Providing such information to embryologists allows them to better perform insemination and subsequent embryo evaluation.

[0122] Once the follicles have sufficiently developed through the ovarian stimulation method, typically, a doctor collects follicular fluid, and an embryologist collects eggs from the follicular fluid using a microscope (egg collection). The embryologist then performs artificial insemination (in vitro fertilization or intracytoplasmic sperm injection) on the day of egg collection, and cultures the fertilized eggs (embryos) in an incubator. The embryologist inputs the status of the eggs or embryos from egg collection to culture into the egg collection ET screen 2500, and the acquisition module 212 acquires information (status information) related to the status of the eggs or embryos input via the egg collection ET screen 2500, and records the information in the embryo information 226 of the auxiliary storage device 202, for example.

[0123] The management module 211 displays an image button 2525 in the result details field 2520. When the management module 211 receives selection of the image button 2525, it displays a pop-up display of images of the embryos from day 0 (DAY 0) to day 7 (DAY 7) after fertilization based on the embryo information 226, as shown in FIG. 26 , for example. Note that the embryo images in FIG. 26 are display samples in which the same image is displayed on each day. The management module 211 may be configured to display, for example, time-lapse images of the embryos from day 0 (DAY 0) to day 7 (DAY 7) after fertilization as a video.

[0124] In assisted reproductive technology, all embryos that can be cultured and transplanted, as well as high-grade, good-quality blastocysts, are often cryopreserved. Embryologists evaluate the embryos, for example, by checking images of the embryos, and freeze the early embryos and good-quality blastocysts.

[0125] Figure 27 is an example of a hormone cycle screen 2700 on the doctor terminal. Figure 28 is an example of a thawing ET screen 2800 on the embryologist terminal. As shown in Figure 27, the management module 211 displays a hormone cycle tab 2710 on the display of the doctor terminal 102, and when the hormone cycle tab 2710 is selected, displays a hormone cycle screen 2700. The management module 211 displays, on the hormone cycle screen 2700, for example, patient information, a column for selecting an embryo to be implanted 2720, a column for selecting an HR set / corpus luteum set, a column for the latest ERA / ER Peak test results, a column for the latest Th1 / Th2 test results, a column for remaining medication management, a column for required procedures 2740, a hormone cycle medical record input form 2730, and the like. The management module 211 displays a hormone cycle screen 2700 based on, for example, patient information 221, treatment information 223, owned drug information 224, consent form information 225, embryo information 226, drug information 228, prescription schedule information 229, freezing management information 230, etc.

[0126] The doctor terminal output module 213 displays information about the patient's frozen embryos in the embryo to be transferred selection field 2720 based on, for example, the embryo information 226 and the freezing management information 230, among the treatment information 423 acquired from the embryologist terminal. The doctor terminal output module 213 displays, in the embryo to be transferred selection field 2720, information about the status of six frozen embryos No. 1 to No. 6, such as the number of days since ovulation, grade, priority score, pronuclear stage, and priority. The priority score is a score display (index) used to determine the priority of embryo transfer. The priority score is not limited to this, but may be, for example, an index that evaluates the implantation rate based on a morphological analysis of the embryo, or an index that evaluates the implantation rate based on one or more of information about the egg, sperm, patient, or partner, or a combination of these.

[0127] The management module 211 also displays an image display button 2721, an AHA selection box 2722, and a transplantation embryo selection box 2723 in the embryo to be transplanted selection field 2720. When the image display button 2721 is selected, the doctor terminal output module 213 pops up images of embryos from day 0 (DAY 0) to day 7 (DAY 7) after fertilization, as shown in FIG.

[0128] The AHA selection box 2722 is a box for selecting an embryo to be subjected to artificial hatching assistance (AHA) from among the embryos whose information is displayed in the transfer embryo selection box 2723, and the transfer embryo selection box 2723 is a box for selecting an embryo to be transferred. The physician selects the transfer embryo selection box 2723 corresponding to the frozen embryo selected as the transfer embryo. Furthermore, if the physician is to perform AHA on the frozen embryo, the physician selects the corresponding AHA selection box 2722. As a result, the acquisition module 212 receives information indicating that the frozen embryo corresponding to the selected transfer embryo selection box 2723 is a transfer embryo, and that if the AHA selection box 2722 is selected, AHA will be performed on this frozen embryo, and stores this information in the embryo information 226 of the auxiliary storage device 202, for example.

[0129] 28 , the management module 211 displays a thawing ET tab 2810 on the display of the embryologist terminal 103, and when the thawing ET tab 2810 is selected, a thawing ET screen 2800 is displayed. The management module 211 displays, for example, a column for displaying embryos to be transferred 2820, a column for thawing settings 2830, a column for starting thawing 2840, and a column for post-thawing management on the thawing ET screen 2800. The management module 211 displays the thawing ET screen 2800 based on, for example, patient information 221, treatment information 223, embryo information 226, freezing management information 230, etc.

[0130] The embryologist terminal output module 214 checks whether there is information about the patient's frozen embryo selected as the embryo to be transferred, obtained from the doctor's terminal, in the embryo information 226 of the auxiliary storage device 202, for example. If there is no information about the frozen embryo selected as the embryo to be transferred, the embryologist terminal output module 214 does not display information about the embryo in the embryo to be transferred display field 2820, but if there is information about the frozen embryo selected as the embryo to be transferred, it displays information about the frozen embryo selected as the embryo to be transferred in the embryo to be transferred display field 2820, as shown in Figure 28. This allows the embryologist to know which frozen embryo the doctor has selected as the embryo to be transferred by checking the thawing ET screen 2800, and to thaw the frozen embryo at the appropriate time and proceed with the embryo transfer.

[0131] The management module 211 displays a melting target selection button 2835 in the melting setting field 2830, and the embryologist selects the melting target selection button 2835 to melt a frozen embryo. The management module 211 then pops up a melting target selection screen 2900, displaying information regarding the status of the patient's frozen embryos. When the embryologist checks the melting target selection screen 2900 and selects the "Select target" button corresponding to the frozen embryo selected by the doctor, the management module 211 displays information regarding the frozen embryo selected as the melting target based on the freezing management information 230 in the melting setting field 2830. If no frozen embryo has been selected as the melting target, the management module 211 does not display information regarding the embryo in the melting setting field 2830. The management module 211 displays the embryo display field 2820 to be transferred and the melting setting field 2830 side-by-side. This allows the embryologist to easily confirm that the embryo to be transferred and the frozen embryo to be thawed are the same by comparing the embryo display field 2820 to the thawing setting field 2830.

[0132] Next, when the embryologist selects the start thawing button 2840, the acquisition module 212 acquires information indicating that the frozen embryo to be thawed will be thawed, and stores this information in the freezing management information 230 of the auxiliary storage device 202.

[0133] <In the Case of Fresh Embryo Transfer> Figure 30 shows another example of the egg retrieval ET screen on the embryologist terminal. In reproductive medicine, fresh embryo transfer is sometimes employed, in which eggs are retrieved and artificially inseminated during a natural cycle, and the embryos are transferred during the egg retrieval cycle without being frozen. On the natural cycle screen (not shown) of the embryologist terminal 103, the selection field for the embryo to be transferred allows the physician to select whether the embryo to be selected is a "frozen embryo" or a "fresh embryo." When fresh embryo transfer is employed, the physician selects the embryo to be selected as a "fresh embryo" and then, as in the case of the hormonal cycle described above, selects the corresponding embryo transfer selection box and, if AHA is to be performed, the AHA selection box. The acquisition module 212 then receives information from the physician terminal 102 regarding the embryo to be freshly transferred and whether AHA will be performed on the embryo, and stores this information in the auxiliary storage device 202.

[0134] In this case, based on the information acquired from the doctor terminal 102, the embryologist terminal output module 214 displays information indicating that the embryo is a transfer embryo in the result details column 3010 for the embryo selected as a transfer embryo among the result details columns (see result details column 2520 in FIG. 25 ) of the egg retrieval ET screen 3000, as shown in FIG. 30 . For example, as shown in FIG. 30 , the embryologist terminal output module 214 displays the background of the result details column 3010 for the embryo selected as a transfer embryo in a color different from that of the result details column for embryos not selected as a transfer embryo. This allows the embryologist to easily grasp which embryo has been selected as a transfer embryo at a glance of the egg retrieval ET screen 3000. An example of a display indicating that the embryo is a transfer embryo is, for example, a decoration similar to the display indicating that the embryo is a virtual prescription of the above-mentioned owned medication.

[0135] [Creating a Letter of Referral] Fig. 14 shows an example of a flow for creating a letter of referral. Fig. 31 shows an example of a post-pregnancy chart screen 3100 on a doctor's terminal. Fig. 32 shows an example of a pop-up display screen for a letter of referral. When a patient becomes pregnant, for example, the patient may be transferred to an obstetrics and gynecology department that can handle childbirth. In clinics that specialize in infertility treatment, the rate at which patients are transferred to other hospitals increases, and doctors are burdened with creating letters of referral.

[0136] The management module 211 displays a post-pregnancy chart tab 3110 on the display of the doctor terminal 102, and when the post-pregnancy chart tab 3110 is selected, a post-pregnancy chart screen 3100 is displayed. The management module 211 displays, for example, a pregnant woman information column, a remaining medication management column, an administration record column, a patient information column, a medical history column, a referral letter creation button 3120, a chart column, and the like on the post-pregnancy chart screen 3100. The management module 211 displays the post-pregnancy chart screen 3100 based on, for example, patient information 221, treatment information 223, owned medication information 224, medication information 228, and the like.

[0137] When the doctor selects the Create Referral Letter button 3120 on the post-pregnancy chart screen 3100, the referral letter output module 217 executes the process described below and creates, for example, a draft referral letter 3210 as shown in Fig. 32. The Create Referral Letter button 3120 may be displayed as a "Create Referral Letter for Transfer" button 1835 on another screen, such as the patient information screen 1800 on the doctor terminal.

[0138] That is, as shown in FIG. 14, the referral letter output module 217 extracts information related to the medical information report from the medical information (S1410) and outputs it in correspondence with a pre-prepared format of the medical information report (S1420).

[0139] In the information extraction step (S1410), the referral letter output module 217 extracts information related to a predetermined medical information report from the medical information of the target patient. The information related to the medical information report includes basic information about the patient and treatment information 223 such as a treatment history.

[0140] In the output step (S1420), the referral letter output module 217 creates and outputs referral letter information by associating the extracted information with a pre-prepared medical information provision form. The referral letter output module 217 may display (output) the referral letter information as text information on the display of the doctor terminal 102 as a referral letter draft 3210, store (output) the referral letter information as file information in PDF format in the auxiliary storage device 202, or print (output) the referral letter on paper. The referral letter output module 217 may also output the referral letter information as a copy of text information on the doctor terminal 102. In this case, the copied text information can be pasted into the body of a new email in an external system, such as an email system, to create a referral letter email. This reduces the effort and burden on doctors when creating referral letters.

[0141] [Medical Record Information Extraction] FIG. 15 shows an example of a medical record information extraction flow. Doctors are required to create medical records (e.g., electronic medical records), but creating medical records can be a burden on doctors. The management module 211 displays medical record information extraction buttons 2125, 2735, and 3135 in medical record input forms 2120, 2730, and 3130 on, for example, the egg collection cycle screen 2100, hormone cycle screen 2700, natural cycle screen (not shown), post-pregnancy medical record screen 3100, and emergency visit screen (not shown) of the doctor's terminal. The management module 211 displays the medical record information extraction buttons 2125, 2735, and 3135 for each date in the medical record input forms 2120, 2730, and 3130, for example. When the doctor selects the medical record information extraction button 2125, 2735, or 3135, the medical record information extraction module 218 executes the process described below to extract medical record information.

[0142] That is, as shown in FIG. 15, the medical record information extraction module 218 extracts information related to specified medical record entries from the acquired medical information (S1510), and outputs the extracted information in a predetermined format (S1520).

[0143] In the information extraction step (S1510), the medical record information extraction module 218 extracts medical record information for the date corresponding to the selected medical record information extraction button 2125, 2735, or 3135 from the patient's medical information. The medical record information can be, for example, information in a so-called "SOAP format" that is described along four items: Subject (subjective information), Object (objective information), Assessment, and Plan. The medical record information extraction module 218 may also be configured to extract input information conforming to the SOAP format from the medical information using, for example, a Large Language Model (LLM).

[0144] In the output step (S1520), the medical record information extraction module 218 outputs the extracted medical record information in a format that can be imported into an external electronic medical record system, for example. This reduces the effort and burden on doctors in creating electronic medical records.

[0145] In addition, when multiple medical record information extraction buttons 2125, 2735, 3135 are selected simultaneously (for example, when medical record information extraction buttons 2125, 2735, 3135 for multiple dates are selected while pressing the "Ctrl" key), the medical record information extraction module 218 may be configured to extract medical record information corresponding to the selected multiple dates from the patient's medical information.

[0146] [Linkage between doctor terminal and embryologist terminal 3] <Consent form information management> Fig. 16 is an example of a consent form information management flow. Fig. 33 is an example of a consent form list screen 3300 on the embryologist terminal. Fig. 34 is an example of a pop-up display screen 3400 for confirming the consent form. Fig. 35 is an example of a pop-up display screen for a copy of the consent form.

[0147] When performing assisted reproductive technology, it is necessary to obtain a consent form indicating that the patient's consent has been obtained for various procedures. The management module 211, for example, displays a consent form list tab 3310 on the display of the embryologist terminal 103, and displays a consent form list screen 3300 when the consent form list tab 3310 is selected. The management module 211 displays, for example, a basic consent form field 3320, as well as a consent form field 3330 required for each cycle and past documents 3335, etc., on the consent form list screen 3300.

[0148] The management module 211 displays the following columns in the basic consent form column 3320: document name, target, delivery, delivery date, person delivered, receipt deadline setting, receipt, receipt date, person who confirmed receipt, copy, and notes. The document name column displays the name of the consent form, and the embryologist can enter whether the patient is the person to whom each consent form is to be submitted in the target column, and can enter information indicating whether an unsigned consent form has been delivered to the patient, the delivery date, and the person who delivered it in the delivery column, delivery date column, and person who confirmed receipt, respectively. The receipt deadline setting, receipt column, receipt date column, and person who confirmed receipt column allow the technician to enter the date by which the signed consent form is to be received, information indicating whether it has been received from the patient, the receipt date, and the person who confirmed receipt, respectively, and the copy column displays an image button for displaying a copy of the signed consent form.

[0149] The management module 211 displays, for example, new cycle, No., delivery, delivery date, delivery person, receipt, receipt date, receipt confirmation person, copy, remarks, and past documents 3335 in the consent form field 3330 required for each cycle. The new cycle field displays a "Create new" button that can be selected when submitting a consent form for a new cycle, the No. field displays information indicating how many cycles the consent forms have been submitted for, and the past documents 3335 field displays a confirmation button for displaying copies of consent forms submitted for past cycles; the rest is the same as the basic consent form field 3320. For example, when the embryologist selects the "Confirm" button for past documents 3335 in the same row as "Consent form for artificial insemination implementation," the management module 211 displays a pop-up display screen 3400 for confirming the consent form for artificial insemination implementation, as shown in FIG. 34. The management module 211 displays, for example, No. on the pop-up display screen 3400 for confirming the consent form for artificial insemination implementation. , date of delivery, person who delivered, date of receipt, person who confirmed receipt, and remarks, as well as a button 3410 for displaying an image of a copy of each consent form. When the embryologist selects the image display button 3410, the consent form information management module 219 displays a copy of the consent form for artificial insemination for the selected cycle based on the consent form information 225, as shown in FIG.

[0150] Here, the management module 211 displays a consent form confirmation field indicating the submission status of the consent form in the required procedure fields 2160, 2740 on the egg collection cycle screen 2100, hormone cycle screen 2700, natural cycle screen (not shown), etc. of the doctor terminal 102. Then, when the consent form information management module 219 acquires information indicating that a prescribed consent form has been obtained from the patient from the embryologist terminal 103 (S1610), it outputs information indicating that the prescribed consent form has been obtained from the patient to the doctor terminal 102 (S1620).

[0151] For example, as shown in FIG. 33 , the embryologist receives a "Marriage Consent Form" and a "Consent Form for Self-Injection" from the patient and checks the receipt field corresponding to the consent form on the consent form list screen 3300 of the embryologist terminal. For example, at this stage, because the embryologist has not yet received all of the consent forms to be received from the patient, the consent form information management module 219 does not display information indicating that all consent forms have been received in the consent form confirmation field of the doctor terminal 102. If the embryologist subsequently receives the remaining consent forms to be received from the patient, namely, the "Consent Form for Sperm Freezing," the "Consent Form for Intracytoplasmic Fertilization," and the "Consent Form for Egg Freezing," and checks the receipt fields for all of the consent forms to be received, the consent form information management module 219 displays information (e.g., check marks) indicating that all required consent forms have been received in the consent form receipt confirmation field of the doctor terminal 102 (see the required procedures field 2160 of FIG. 21 ). This allows the doctor to quickly grasp the status of consent form receipt for the patient from the display on the doctor terminal 102.

[0152] The management module 211 may additionally display a consent form confirmation field indicating the status of the delivery (distribution) of a consent form to the patient in the required procedure fields 2160, 2740 on the egg collection cycle screen 2100, hormone cycle screen 2700, natural cycle screen (not shown), etc., of the doctor terminal 102. In this case, for example, when an embryologist delivers an unsigned consent form to a patient, the acquisition module 212 can acquire information indicating that the consent form has been delivered (distributed) to the patient from the embryologist terminal 103. Then, upon acquiring information indicating that the consent form has been delivered (distributed) to the patient, the consent form information management module 219 outputs information indicating that the consent form has been acquired from the patient to the doctor terminal 102. Furthermore, when a patient acquires an unsigned consent form from the management server 101 via the patient terminal 104, the acquisition module 212 can acquire information indicating that the consent form has been delivered (distributed) to the patient, such as an access record of the patient terminal 104 to the management server 101.

[0153] For example, as shown in FIG. 33 , the embryologist hands the patient a "Consent Form for Marital Relationship," "Consent Form for Handling Self-Injection," "Consent Form for Sperm Freezing," and "Consent Form for Intracytoplasmic Fertilization," and checks the "Transfer" field corresponding to the consent form on the consent form list screen 3300 of the embryologist terminal. For example, at this stage, the embryologist has not yet handed over all of the consent forms to be handed over from the patient, so the consent form information management module 219 does not display information indicating that all consent forms have been handed over in the consent form confirmation field of the doctor terminal 102. The embryologist then hands over the remaining consent form to be handed over, the "Consent Form for Egg Freezing," to the patient, and checks the "Transfer" field for all of the consent forms to be handed over. The acquisition module 212 acquires information from the embryologist terminal 103 indicating that all consent forms have been handed over to the patient. In such a case, the consent form information management module 219 displays information (e.g., check marks) indicating that all consent forms that should be handed over have been handed over in the consent form handover confirmation field (see the required procedures field 2160 in FIG. 21 ) of the doctor terminal 102 based on information from the embryologist terminal 103. This allows the doctor to quickly grasp the handover status (distribution status) of the consent forms for the patient from the display on the doctor terminal 102.

[0154] Although not specifically shown, the management module 211 may further display, for example, columns for explanation, explanation date, and explanation person for each consent form displayed in the basic consent form column 3320 and the consent form required for each cycle column 3330. This allows the embryologist to enter, for example, information indicating whether the contents of the consent form were explained to the patient, information on the explanation date, and information on the explanation person in the explanation column, explanation date column, and explanation person column, respectively. In this case, for example, when the consent form information management module 219 acquires information indicating that the contents of a specific consent form have been explained to the patient from the embryologist terminal 103, it may be configured to output information indicating that the contents of the specific consent form have been explained to the patient to the doctor terminal 102. For example, specifically, the management module 211 displays an explanation column (check box) for each consent form in the consent form confirmation column of the doctor terminal 102. When the acquisition module 212 acquires information indicating that the contents of the consent form have been explained to the patient from the embryologist terminal 103, the consent form information management module 219 displays information indicating that the contents of the consent form have been explained (for example, a check mark) in the explanation field for the corresponding consent form. This allows the doctor to quickly understand from the display on the doctor terminal 102 whether the contents of the consent form have been explained to the patient.

[0155] [Semen Evaluation] Figure 17 shows an example of a semen evaluation flow. Figure 36 shows an example of a sperm testing / freezing screen 3600 on an embryologist terminal. When artificial insemination is performed in assisted reproductive technology, sperm are tested after being collected from semen brought to the medical institution on the day or ejaculated within the hospital. Therefore, it is desirable to be able to perform semen testing accurately and easily.

[0156] The management module 211, for example, displays a sperm test / freezing tab 3610 on the display of the embryologist terminal 103, and displays a sperm test / freezing screen 3600 when the sperm test / freezing tab 3610 is selected. The management module 211 displays, for example, a new sperm test field 3620, a test result input field 3630, a pre-adjustment result display field 3640, a pre-adjustment judgment field 3645, a post-adjustment result display field 3650, a post-adjustment judgment field 3655, and the like on the sperm test / freezing screen 3600.

[0157] The embryologist collects the recipient's semen and performs a semen test using, for example, a sperm motility analysis system (SMAS). The sperm motility analysis system is an example of medical equipment 105, and is connected to the management server 101 via, for example, an internet line. The sperm motility analysis system may also be wired to the embryologist terminal 103 via, for example, an in-hospital LAN. When the embryologist selects the "Read" button in the test result input field 3630, the acquisition module 212 reads, for example, the results of the semen test into the management server 101 and stores them in the auxiliary storage device 202. The results of the semen test include, for example, semen volume, sperm concentration, total sperm count, motility rate, forward motility rate, normal morphology rate, white blood cell count, etc.

[0158] The information regarding the results of the semen test may be configured, for example, so that the embryologist inputs the information into the embryologist terminal 103 via the test result input field 3630 on the sperm test / freezing screen 3600, and the information is sent to the management server 101 when the embryologist selects the "Read" button in the test result input field 3630. The acquisition module 212 may also be configured, for example, to acquire the results of the semen test sent from the embryologist terminal 103 and store them in the auxiliary storage device 202.

[0159] The semen evaluation module 220 evaluates the stored semen test results. That is, as shown in Fig. 17, the semen evaluation module 220 acquires information about the semen test related to the patient's semen (S1710), evaluates whether the information about the semen test satisfies a predetermined standard (S1720), and if the information about the semen test satisfies the predetermined standard (Yes in S1720), outputs information indicating that the patient's semen satisfies the predetermined standard (S1730), and if the information about the semen test does not satisfy the predetermined standard (No in S1720), outputs information indicating that the patient's semen does not satisfy the predetermined standard (S1740).

[0160] The predetermined standards for each semen test item may be, for example, the normal semen test values ​​established by the World Health Organization (WHO). The semen evaluation module 220 performs the evaluation and information output described above for each semen test item value. For example, in the pre-adjustment judgment column 3645 and post-adjustment judgment column 3655 of FIG. 36, the semen evaluation module 220 displays a "◯" mark if the semen test results meet the predetermined standards, and a "X" mark if the semen test results do not meet the predetermined standards. This configuration allows the embryologist to quickly and easily evaluate whether the patient's semen meets the predetermined standards.

[0161] [Estimation 1] The management server 101 is configured to be able to output reference information for diagnosis and judgment regarding infertility treatment from various information about patients. For example, the estimation module 250 outputs, to the doctor terminal 102 and / or the embryologist terminal 103, reference information about, for example, the optimal egg collection date and number of eggs to maximize the number of eggs to be collected, which information is estimated by a machine learning model P that optimizes the number of eggs to be collected for a patient scheduled for in vitro fertilization.

[0162] The machine learning model P disclosed in this embodiment is a model that estimates the growth of eggs in the ovaries of a patient scheduled for egg collection. The machine learning model P is, for example, a parameterized composite function obtained by combining multiple functions. The parameterized composite function can be defined by a combination of multiple adjustable functions and parameters. The machine learning model P is obtained by adjusting the parameters by having the machine learning model perform machine learning based on training data in accordance with a model learning program. For example, the machine learning model P of this embodiment is trained to output the optimal egg collection date that maximizes the number of eggs that can be collected and the number of eggs to be collected in that case (output data) in response to input patient attribute information, treatment information, etc. (input data).

[0163] In this case, the learning data includes, for example, basic information about patients who have previously undergone egg collection, treatment methods (ovarian stimulation methods, medications used and their administration dates and times, etc.), and test results (vital data, estrogen levels, transvaginal ultrasound images, etc.) as input data (explanatory variables), and information about the number of eggs collected and the egg collection date, for example, is used as correct output data (objective variables) for the input information. These input data are, for example, information acquired by the acquisition module 212 from the doctor terminal 102. The machine learning model P is stored in the auxiliary storage device 202 in a trained state, but may be retrained at any time based on information recorded in the reproductive medicine support system 1.

[0164] Specifically, the machine learning model P compares the similarity between, for example, the features (reference features) of various patient basic information and information on test results with the features of the basic information and information on test results of the patient to be evaluated. As a result, the machine learning model P estimates, for example, the optimal egg collection date and the number of eggs to be collected in that case that maximizes the number of eggs that can be collected for the patient to be evaluated. When evaluating the similarity, for example, if the feature of the data of the patient to be evaluated is within a predetermined threshold range with respect to the reference feature determined for each number of eggs that can be collected, the number of eggs that can be collected corresponding to the reference feature is determined to be the number of eggs that can be collected for the patient. For example, reference features are set for test result information when various numbers of eggs have grown in the ovaries.

[0165] The machine learning model P according to this embodiment is, for example, a parameterized composite function obtained by combining multiple functions. The parameterized composite function is defined by a combination of multiple adjustable functions and parameters. When the machine learning model P is generated using a forward propagation multilayer network, the parameterized composite function can be defined as, for example, a linear relationship between each layer using a weighting matrix, a nonlinear relationship (or linear relationship) using an activation function in each layer, and a bias. The weighting matrix and bias are parameters in the multilayer network. In a parameterized composite function, the form of the function changes depending on how the parameters are selected. In a multilayer network, by appropriately setting the constituent parameters, it is possible to define a function that can output desirable results from the output layer.

[0166] The machine learning model P according to this embodiment may be any parameterized composite function that satisfies the above requirements, but is a multi-layered neural network model (hereinafter referred to as a "multi-layered network"). The machine learning model P using a multi-layered network has an input layer, an output layer, and at least one intermediate layer or hidden layer provided between the input layer and the output layer.

[0167] The multi-layer network according to this embodiment may be, for example, a deep neural network (DNN), which is a multi-layer neural network that is the subject of deep learning. As the DNN, for example, a convolution neural network (CNN) that targets images may be used as a part thereof.

[0168] FIG. 37 shows another example of an egg collection cycle screen 3700 on the doctor's terminal. The management module 211 outputs the egg collection cycle screen 3700 for a specific patient to the display of the doctor's terminal 102. Here, for example, if the patient is scheduled for egg collection and is in an ovulation stimulation cycle, the estimation module 250 outputs an estimation pop-up display 3710 superimposed on the egg collection cycle screen 3700. When the above-mentioned predetermined input information about the patient is applied to the machine learning model P, the estimation module 250 outputs information regarding the "number of eggs to be collected" and the "optimal egg collection date" obtained as output information, such as the "expected number of eggs to be collected" and the "recommended egg collection date," to the estimation pop-up display 3710. The number of eggs to be collected may be, for example, mature eggs (MII stage eggs). The estimation module 250 may be configured to output a similar estimation pop-up display 3710 to the embryologist terminal 103.

[0169] The estimation module 250 may be configured to apply the above-mentioned predetermined input information for all patients who are scheduled for egg collection and are in an ovulation stimulation cycle, and output information regarding the "number of eggs to be collected" and the "optimal egg collection date" obtained as output information to the doctor terminal 102 or the embryologist terminal 103, for example, as an egg collection schedule list.

[0170] Ovarian stimulation involves stimulating the ovaries with drugs to artificially grow multiple eggs, but it is necessary to allow the follicles to grow to an appropriate size and collect the eggs before ovulation. Furthermore, medication may be required to mature the eggs in the follicles two days before egg collection, and the administration of medications such as anesthetics during the egg collection surgery may vary depending on the number of eggs to be collected. Therefore, knowing the number of eggs to be collected and the optimal egg collection date for a patient in advance is beneficial, as it allows doctors, nurses, and embryologists to more easily plan their treatment while taking into account the schedule of the patient.

[0171] <Variation 1> The machine learning model P is not limited to one that uses information regarding the number of eggs collected and the egg collection date as output data (objective variables). For example, when various basic patient information and information regarding test results can be acquired as input data (explanatory variables), the machine learning model P may be trained to estimate (output) a pregnancy rate (objective variable) in infertility treatment based on patient attributes. In this case, for example, the objective variable may be "pregnancy" (e.g., pregnancy rate), and the explanatory variables may be structured data including basic patient information, treatment method (e.g., ovarian stimulation method, number of eggs collected, culture method, medications used, etc.), and image data of embryo images (still images and / or video). Of these input data, for example, the culture method, embryo images, and the PGT-A (preimplantation chromosomal aneuploidy testing) and blastocyst progression rate, etc., are typically acquired by the acquisition module 212 from the embryologist terminal 103, while the other information is acquired from the doctor terminal 102. This makes it possible to estimate the pregnancy rate according to various explanatory variables, and to grasp various conditions for maximizing the pregnancy rate. As a result, it is possible to obtain a machine learning model that estimates factors for maximizing the possibility of pregnancy (pregnancy rate). In particular, estimation by the machine learning model based on information acquired from the embryologist terminal 103 and the physician terminal 102 can be performed more smoothly.

[0172] More specifically, the machine learning model P may be trained to estimate and output conditions with a high probability of success for infertility treatment from various perspectives, where success can be, for example, (1) optimizing (including maximizing) the number of eggs collected, (2) maximizing the rate of blastocyst development, (3) optimizing the selection of embryos to be implanted, (4) maximizing the cost-effectiveness of the treatment method, etc.

[0173] The training data used in learning the machine learning model P that estimates the above success can be, by way of example only, the objective variable and explanatory variables, although not limited to these:

[0174] That is, (1) when creating an optimization model for the number of eggs collected, it is advisable to use the value of the number of eggs collected as the objective variable, and to use structured data such as basic patient information and treatment method (ovarian stimulation method, number of eggs collected, culture method, drugs used, etc.), as well as image data of embryo images (still images and / or videos), etc. as explanatory variables.

[0175] (2) When creating a model for maximizing the rate of reaching the blastocyst stage, it is advisable to use, as the objective variable, whether or not the embryo reaches the blastocyst stage, and to use, as the explanatory variables, structured data such as basic patient information, treatment method (ovarian stimulation method, number of eggs collected, culture method, drugs used, etc.), culture method (culture period, culture medium used, etc.), and image data of embryo images (still images and / or videos) (especially embryo images).

[0176] (3) When creating an optimization model for selecting embryos for transfer, it is advisable to use the presence or absence of implantation or the presence or absence of a normal pregnancy as the objective variable, and to use structured data (e.g., basic patient information, patient condition (endometrial thickness, hormone levels), etc.), test results (endometrial implantation ability, PGT-A, etc.), treatment method (ovarian stimulation method, number of eggs collected, culture method, medication used, etc.), and image data (especially embryo images) of embryo images (still images and / or videos) as explanatory variables. In this case, cost information may be included in association with the treatment method.

[0177] (4) When creating a model for maximizing the cost-effectiveness of a treatment method, it is advisable to use the pregnancy rate value as the objective variable and structured data such as basic patient information, treatment method (ovarian stimulation method, number of eggs collected, culture method, drugs used, etc.), and image data of embryo images (still images and / or videos) (especially embryo images) as explanatory variables.

[0178] To estimate the success of the various aspects described above, the machine learning model P may be prepared as a separate machine learning model for each desired estimation result, or may be configured to enable switching of at least one of the function and parameter set of the estimation model, or a combination thereof, depending on the desired estimation result (i.e., the content of the output data can be switched). For example, by using a corresponding machine learning model P among these according to the estimation content, the estimation module 250 can estimate and output conditions with a high probability of success for the desired estimation content related to infertility treatment.

[0179] Furthermore, the estimation module 250 may be configured to output reference information based on the output results of an analysis unit (not shown) that statistically analyzes the input data to estimate a treatment method with a high success rate for infertility treatment, instead of the estimation results of the machine learning model P. Furthermore, the input data does not need to include all of the above examples, and can be a combination of one or more pieces of information.

[0180] This allows doctors and embryologists to make diagnoses and decisions regarding infertility treatment, taking into account the reference information from the estimation module 250. The reference information from the estimation module 250 is derived based on information on patients who are not in the care of the doctors and embryologists, and for example, less experienced doctors and embryologists can make more appropriate diagnoses and decisions.

[0181] [Estimation 2] In one embodiment, a machine learning model P can be used to evaluate (estimate) the likelihood that an embryo is a euploid embryo or the quality of the embryo. Although not limited to this, embryo images can be used as one of the explanatory variables in training the machine learning model P used for evaluation. In this case, still images (i.e., morphological data) can be used as the embryo images. The training model used in this case may be, for example, a training model equipped with an image recognition function using deep learning. The image recognition function may be, for example, an object identification function, an object detection function, a segmentation function, or a combination of these functions. By training (including additional training) such a training model using embryo images, a robust machine learning model P (an example of an embryo evaluation model) can be obtained that has good performance in assessing the likelihood or quality of an embryo being a euploid embryo.

[0182] Alternatively, in order to evaluate the likelihood or quality of an embryo being a euploid embryo with high accuracy using the machine learning model P, the estimation module 250 may be configured to add annotations based on predetermined criteria as preprocessing of the embryo image. Furthermore, the machine learning model P that evaluates the likelihood or quality of an embryo being a euploid embryo may be a machine learning model trained using embryo images (training data) to which annotations have been added as explanatory variables. The annotations added to the embryo images as training data may or may not have been added by the estimation module 250 (for example, they may be annotations added manually).

[0183] The annotation function of the estimation module 250 will be described. The estimation module 250 may be configured to perform preprocessing on an embryo image, including, for example, (1) identifying the outer periphery (boundary) of the embryo, (2) normalizing the embryo and segmenting the embryo, and (3) assigning annotations corresponding to the criteria to segments that meet predetermined criteria. The normalization performed by the estimation module 250 may include, for example, normalizing the size of the embryo or correcting the color tone of the embryo image (e.g., adjusting the image to a predetermined gradation). Furthermore, during annotation, the estimation module 250 may use a trained annotation model that has been trained to annotate the inner cell mass (ICM) and trophectoderm (TE) with information about their respective tissues after segmenting the embryo. The trained model for annotation can be, for example, a training model trained using original embryo images and annotation images, which are labeled by adding ICM and TE contour information in polygon format to the original embryo images, as training data. Using the annotated embryo images to evaluate the likelihood or quality of an embryo being a euploid embryo can further improve the estimation accuracy of the machine learning model P.

[0184] Furthermore, the machine learning model P that evaluates the possibility or quality of an embryo being a euploid embryo may include, for example, information on the age of the patient and partner and the time elapsed since insemination (culture time) in addition to the embryo image information as explanatory variables. Generally, embryo image information is obtained as time-lapse images of the embryo. In this case, the culture time (or current time) is recorded in text form in the time-lapse images of the embryo, and the time elapsed since insemination may be obtained, for example, by extracting this text information using optical recognition (OCR). Furthermore, the machine learning model P that evaluates the possibility or quality of an embryo being a euploid embryo may divide the embryo image information into multiple steps (e.g., N stages, where N representing the number of steps is a natural number equal to or greater than 2) based on the time elapsed since insemination, and generate a separate machine learning model P for each divided time elapsed since insemination from the image information used as an explanatory variable. １～Ｎ In one embodiment, N is, for example, 3 to 15, preferably 8 to 10. The timing of dividing the steps is not limited to this example, but examples include the early embryo step (2 days after insemination), the 3rd day, the 4th day, the 5th day, the 6th day, the 7th day, just before vitrification (just before embryo freezing), and after freezing and thawing (for example, N = 8 steps).

[0185] The ages of the patient and partner may be, for example, the ages at the time of egg collection and sperm collection. By additionally training the machine learning model using such embryo images and information about the embryo as explanatory variables and whether implantation is successful as a target variable, a machine learning model P can be developed that can evaluate the possibility or quality of embryos recorded in embryo image information as euploid embryos with higher accuracy than before. Ｎ As a result, for example, an appropriate machine learning model P can be generated based on one embryo image, information about the embryo (for example, age information of the patient and partner), and the timing of capturing the embryo image (the elapsed time since insemination). Ｎ By inputting the data into the system, it is possible to estimate with high accuracy (e.g., score) the possibility or quality of an embryo in an embryo image as being a euploid embryo. In this case, only one embryo image's worth of information is required for evaluation, and the evaluation is not only non-invasive, but also allows for a simple and low-cost evaluation of implantation rate.

[0186] For example, at a predetermined timing or in response to a request from the doctor terminal 102 or the embryologist terminal 103, the estimation module 250 calculates information about the embryo image and the ages of the patient and partner related to the embryo, and calculates a machine learning model P that is suitable for the timing of capturing the embryo image. Ｎ 29 , the doctor terminal output module 213 and the embryologist terminal output module 214 of the management server 101 can each output the classification results of the embryo to be evaluated, classified by the embryo classification unit, to, for example, the doctor terminal 102 or the embryologist terminal 103, for example, at a predetermined timing or in response to a request from the doctor terminal 102 or the embryologist terminal 103. As an example, the doctor terminal output module 213 and the embryologist terminal output module 214 can display, in addition to "priority," the "likelihood that the embryo is a euploid embryo" or "embryo quality," or parameters related thereto, estimated by the estimation module 250, for example, in the implantation-scheduled embryo selection field 2720 on the hormone cycle screen 2700 of FIG. 27 , the thawing target selection screen 2900 of FIG. 29 , etc.

[0187] It has been confirmed that the likelihood of an embryo being a euploid embryo or its quality shows a strong correlation with the mother's age at the time of egg collection. For example, outside of Japan, women over 40 often choose surrogate pregnancy or egg donation because of the high difficulty of obtaining normal embryos. In response to this, the machine learning model P, which has been trained to estimate implantation rates based on the above-mentioned embryo image information, Ｎ Based on its high morphological analysis ability, the machine learning model P can distinguish the quality of the inner cell mass (ICM) and the quality of the trophectoderm (TE), which are difficult to distinguish with the human eye, and can "predict" with high accuracy, for example, whether the embryo has a morphology that has a high pregnancy rate or whether the embryo is euploid. As a result, the machine learning model P ＮBy evaluating embryos using this method, for example, it is possible to select embryos with a high implantation rate (e.g., normal embryos) with a higher probability than before, even when multiple embryos are obtained from an older mother. This allows women over 40 years old, for example, to choose to use their own embryos with a higher reliability of achieving pregnancy. Furthermore, this method can assist not only in the selection of embryos for transfer, but also in the selection of embryos to be vitrified or subjected to PGT-A testing.

[0188] In the estimation using the above machine learning model, information on embryo images and information on the elapsed time since insemination (culture time), which are used as explanatory variables and input data, are typically information acquired by the acquisition module 212 from the embryologist terminal 103. In addition, information on the likelihood that the embryo is a euploid embryo and the quality of the embryo, which are objective variables, is information acquired by the acquisition module 212 from the embryologist terminal 103. Other information (e.g., the ages of the patient and partner) is information acquired by the acquisition module 212 from the doctor terminal 102. By having the management server 101 acquire this information from each terminal, estimation and learning (including relearning) using the machine learning model can be performed efficiently.

[0189] [Electronic Consent Form] In the above embodiment, the consent form information management module 219 and the consent form submission module 519 each have a function to support the submission of a copy of the consent form from the patient terminal 104 to the management server 101. Note that the consent form information management module and the consent form submission module may also have a function to support the submission of electronic data of the consent form (e.g., an electronic consent form) from the patient terminal 104 to the management server 101.

[0190] 38 is an example of a consent form submission screen 3800 output to the patient terminal 104. The patient terminal output module 251 of the management server 101 works in conjunction with the patient terminal management module 511 of the patient terminal 104 to output the consent form submission screen 3800 to the patient terminal 104. The consent form information management module 219 of the management server 101, for example, outputs a printable consent form form 3810 on the consent form submission screen 3800, or outputs an electronic consent form input form 3815 including an electronic signature field 3820 for the patient to enter an electronic signature.

[0191] In addition, the consent forms 3810 and 3815 may be configured to be freely available on the patient terminal 104, for example, by a patient application for using the reproductive medical support system 1.

[0192] Furthermore, the consent form forms 3810, 3815 may be configured so that the consent form information management module 219 of the management server 101 transmits consent form forms with appropriate content suited to the patient's treatment to the patient terminal 104 based on instructions from the doctor or embryologist. In this case, when the consent form information management module 219 of the management server 101 receives an instruction from the doctor terminal side patient coordination module 351 of the doctor terminal 102 or the embryologist terminal side patient coordination module 451 of the embryologist terminal 103 to transmit specified consent form forms 3810, 3815 to the target patient terminal 104, it transmits the specified consent form forms 3810, 3815 to the target patient terminal 104.

[0193] For example, the patient may print out the consent form 3810 on paper, sign it, and then bring the signed consent form to the medical institution to submit it. Alternatively, the consent form information management module 219 of the management server 101 may be configured to cooperate with the consent form submission module 519 of the patient terminal 104 to accept an electronic signature from the patient in the electronic signature field 3820 of the electronic consent form input form 3815, and to receive the electronically signed consent form (e.g., an electronic consent form file) from the patient terminal 104 when the submit button 3830 is selected. This allows the patient to submit the consent form to the medical institution without being restricted by time or location.

[0194] The electronic signature referred to in this specification may be an electronic signature to which personal identification data (electronic certificate) is attached, or may be an electronic signature to which personal identification data (electronic certificate) is not attached. The electronic signature may be, for example, an electronic signature in which a name is written with a touch pen or the like on a document displayed on a tablet or touch panel and saved as electronic data.

[0195] The consent form information management module 219 of the management server 101 stores the electronically signed consent form received from the patient terminal 104, for example, in consent form information 225. The consent form information management module 219 then outputs a display indicating that the corresponding consent form has been received, for example, on the consent form list screen 3300 for the patient on the embryologist terminal 103 and on the receipt confirmation field for the consent form for the patient on the doctor terminal 102 (see the required procedures field 2160 in FIG. 21 ). The consent form information management module 219 may be configured to output a message indicating that the consent form has been received from the patient to, for example, all of the doctor terminal 102 and the embryologist terminal 103, or to a portion related to the patient.

[0196] The doctor terminal 102 may also be equipped with a consent form submission module. The consent form information management module 219 of the management server 101 may be configured to, upon receiving a signed consent form from the patient terminal 104, output the signed consent form to the doctor terminal 102 and accept an electronic signature from the doctor at the doctor terminal 102. The acceptance of the input of the electronic signature from the doctor terminal 102 can be performed by the same process as that for the patient terminal 104. This allows an electronic consent form agreed upon between the patient and doctor (two parties) to be obtained.

[0197] Furthermore, the consent form information management module 219 of the management server 101 may be configured, when receiving a signed consent form from one patient terminal 104 of a patient and partner who are in a partner relationship based on the patient information 221 and the partner information 222, to output the consent form signed by one patient to the patient terminal 104 used by the other patient, and to accept an electronic signature from the other patient from the patient terminal 104 used by the other patient. In this case, an electronic consent form agreed upon between the patient and partner (between the two parties) can be obtained.

[0198] Similarly, the consent form information management module 219 of the management server 101 may be configured to output consent forms and accept electronic signatures from the terminals used by the patient, partner, and doctor in turn, thereby accepting electronic signatures from all three parties on a single electronic consent form. This makes it possible to obtain an electronic consent form that has been agreed upon between the patient, partner, and doctor (three parties).

[0199] [Sharing of Test and Medical Treatment Results] The reproductive medicine support system 1 may be configured to allow some of a patient's test results and medical treatment results to be shared with the patient at the instruction of a doctor or embryologist. For example, when the acquisition module 212 of the management server 101 receives an instruction from the embryologist terminal 103 to send a "notice of embryo culture results" to a specific patient, the patient terminal output module 251 sends a predetermined "notice of embryo culture results" to the specific patient. The instruction to send the "notice of embryo culture results" includes information specifying a time-lapse image of a specific embryo of the patient stored in the embryo information 226 to be included in the notification, and information about the embryo (e.g., the number of days in culture, the grade).

[0200] 39 is an example of an examination and medical treatment result report screen 3900. The patient terminal output module 251 of the management server 101 cooperates with the patient terminal management module 511 of the patient terminal 104 to output the examination and medical treatment result report screen 3900 to the patient terminal 104. The patient terminal output module 251 of the management server 101 outputs, for example, an embryo culture result notification form 3910 on the examination and medical treatment result report screen 3900. For example, based on an instruction from the embryologist terminal 103, the patient terminal output module 251 displays a time-lapse image of a specific embryo of the patient from the embryo information 226 and information about the embryo (e.g., number of days in culture, grade) in the embryo culture result notification form 3910.

[0201] In infertility treatment, patients are prone to anxiety at various stages, but it is beneficial for them to be able to continue treatment with peace of mind by, for example, obtaining information about the progress of treatment from a doctor or embryologist via the examination / diagnosis result report screen 3900. Note that the information that can be shared with doctors and embryologists is not limited to embryo culture results.

[0202] [Medication / Drug Administration Management] The reproductive medicine support system 1 may be configured to be able to support patients in taking their medication. Fig. 40 shows an example of a medication / drug administration management screen 4000. The patient terminal output module 251 of the management server 101 works in conjunction with the patient terminal management module 511 of the patient terminal 104 to output the medication / drug administration management screen 4000 to the patient terminal 104. The patient terminal output module 251 of the management server 101 outputs information about medication prescribed by a doctor to the medication / drug administration management screen 4000.

[0203] The patient terminal output module 251 outputs, for example, a treatment history calendar 4010 and information about prescribed drugs 4020 on the medication / drug administration management screen 4000. Based on the treatment information 223, the patient terminal output module 251 displays, for example, this week's treatment information, today's medication information (e.g., drug name, dosage), and tomorrow's medication information (e.g., drug name, dosage), as the information about prescribed drugs 4020. Note that, when an arbitrary day is selected on the treatment history calendar 4010 on the patient terminal 104, the patient terminal output module 251 may be configured to display information about the prescribed drugs for the selected day.

[0204] The patient terminal output module 251 displays the medication time along with the name of the medication if a medication time is specified. Although not specifically shown, the patient terminal output module 251 may also output an image of the prescription medication as medication information. The patient terminal output module 251 may also output information explaining how to use, for example, an autoinjectable preparation as medication information. The image of the prescription medication and information explaining how to take the medication may be configured to be output when information about the prescription medication (e.g., a text display) is selected on the patient terminal 104.

[0205] In infertility treatment, many types and amounts of medications are prescribed, making it difficult for patients to manage their medication on their own. In such cases, it is beneficial to receive frequent instructions and information about medication from a doctor via the medication / medication management screen 4000, allowing patients to continue treatment with peace of mind. Furthermore, with this configuration, patients' medication can be managed based on the screen of the doctor's terminal 102 and orders issued from the management server 101.

[0206] 42 is another example of a medication / dose management screen 4200. The patient terminal output module 251 of the management server 101 differs from the medication / dose management screen 4200 in that it outputs a medication schedule 4210 instead of the treatment history calendar 4010 and prescription drug information 4020 shown in FIG.

[0207] The patient terminal output module 251 displays, for example, a medication schedule for each menstrual cycle in chart format in the medication schedule 4210. The patient terminal output module 251 displays, for example, the menstrual cycle (Cycle day), date, prescription drug information (for example, an oral medication column and an injectable medication column), and hormone level information in the medication schedule 4210. The patient terminal output module 251 outputs this information based on, for example, the treatment information 223, etc.

[0208] The hormone level information may be, for example, test results of blood hormone concentrations when blood is drawn during a hospital visit, and may be stored as treatment information 223. Hormone level information is not limited to, but may include, for example, blood concentration test results of female hormones such as follicle stimulating hormone (FSH), luteinizing hormone (LH), and estradiol (E2).

[0209] By displaying such medication schedule 4210, the patient can understand not only "when and what medication to take / inject" but also "what hormone levels were at the time of hospital visits." Note that this medication / dose management screen 4200 may be configured to be accessible as the top screen of the patient terminal application, or may be configured to be accessible by clicking on another calendar (for example, treatment history calendar 4010).

[0210] The patient terminal output module 251 may be configured to send a notification to the patient terminal 104 prompting the patient to take the medication at an appropriate timing. For example, when the acquisition module 212 of the management server 101 receives an instruction from the doctor terminal 102 to send a "medication schedule" for a specific patient, the patient terminal output module 251 may be configured to send a predetermined "medication schedule" to the specific patient. The instruction to send the "medication schedule" includes information specifying information about the patient's prescribed medication (e.g., medication date, medication name, dosage) stored in the medication information 228 and prescription schedule information 229 to be included in the medication schedule.

[0211] Furthermore, the patient terminal output module 251 may be configured to display a medication completion button or the like on the medication / dose management screen 400, and when the patient selects the medication completion button on the patient terminal 104, the acquisition module 212 may be configured to acquire information indicating that the patient has taken the medication from the patient terminal 104. When the acquisition module 212 acquires the information indicating that the medication has been taken, it stores the information indicating that the patient has taken the medication in, for example, the prescription schedule information 229. This allows, for example, a doctor to check the patient's medication record on the doctor terminal 102 and provide appropriate support, guidance, and treatment.

[0212] [Patient Learning] The reproductive medicine support system 1 may be configured to provide patients with knowledge about infertility treatment. The reproductive medicine support system 1 is configured, for example, to allow a doctor to easily provide patients with knowledge about current or upcoming treatment. For example, when the acquisition module 212 of the management server 101 receives an instruction from the doctor terminal 102 to send "educational materials about infertility treatment" to a specific patient, the patient terminal output module 251 sends the specified "educational materials about infertility treatment" to the specific patient. The instruction to send the "educational materials about infertility treatment" includes information identifying the educational materials about infertility treatment (e.g., educational material ID, information about the storage location of the educational materials, etc.).

[0213] FIG. 41 shows an example of a patient learning screen 4100. The patient terminal output module 251 of the management server 101 cooperates with the patient terminal management module 511 of the patient terminal 104 to output the patient learning screen 4100 to the patient terminal 104. The patient terminal output module 251 of the management server 101 outputs, for example, educational materials 4110 (video materials in this case) and treatment information 4120 on the patient learning screen 4100. Based on instructions from the doctor terminal 102, the patient terminal output module 251 displays, as the educational materials 4110, educational materials (e.g., text, still images, videos, etc.) explaining the treatment or surgery to be performed tomorrow. The patient terminal output module 251 outputs, as the treatment information 4120, information such as a brief explanation of the treatment and precautions.

[0214] In infertility treatment, doctors generally explain the treatment details to patients at medical institutions. However, treatment explanations tend to include terms unfamiliar to patients, which may be forgotten over time. Doctors may also unintentionally forget some of the explanations. In such cases, it is beneficial for patients to receive detailed explanations about the treatment from doctors via the patient learning screen 4100 as the treatment progresses, allowing them to continue treatment with peace of mind. This also helps doctors improve the efficiency of their medical treatment. The instruction to send the "educational materials about infertility treatment" may be configured to be automatically sent from the doctor terminal 102 to the management server 101 based on, for example, treatment information 223 entered on the doctor terminal 102.

[0215] [Data Utilization] Conventionally, it has been extremely difficult to manage and analyze information related to infertility treatment in a seamless manner, from the egg collection process to the insemination process, culture process, and transplantation process. Therefore, there was a problem that information related to a patient's infertility treatment had to be analyzed and evaluated for each process. As a result, it was only possible to retrospectively partially optimize individual processes based on the analysis results for each process, for example, specifically, (Process 1) Patient X's egg collection results, (Process 2) Patient X's egg a culture results, (Process 3) Patient X's endometrial transplant results, etc.

[0216] In contrast, according to the reproductive medicine support system 1 according to the present technology, for example, a doctor and an embryologist can work together to store the information they each obtain in the auxiliary storage device 202 from the doctor terminal 102 or the embryologist terminal 103. Furthermore, the management server 101 can store and manage the various pieces of information obtained by the doctor and the embryologist in an organized manner according to predetermined rules, for example, from the stage at which the information is first stored in the auxiliary storage device 202.

[0217] For example, the management server 101 stores medical information in association with patient identification information (e.g., patient ID, partner ID, or both). As an example, any test information (e.g., information regarding embryo grade) is stored in the auxiliary storage device 202 in a format in which a patient ID, an egg collection ID below that, and an egg ID and / or sperm ID below that are assigned as sub-numbers. The medical information stored in the auxiliary storage device 202 (e.g., patient information 221, partner information 222, treatment information 223, owned medication information 224, consent form information 225, embryo information 226, sperm management information 227, medication information 228, prescription schedule information 229, and freezing management information 230) has a systematic data structure associated with patient identification information. In other words, information based on the doctor (step 1), information based on the embryologist (step 2), and information based on the doctor (step 3) are stored in association with each other. This system allows doctors and embryologists to view the information they have acquired through the doctor's terminal 102 and the embryologist's terminal 103, respectively. For example, they can view the entire process, from egg collection to insemination, culture, and transplantation. Furthermore, based on this systematic data structure, the management server 101 can efficiently analyze and evaluate infertility treatments.

[0218] In such a reproductive medicine support system 1, for example, the estimation module 250 of the management server 101 may have the function of analyzing and / or estimating, or retrospectively evaluating, various aspects of a series of treatments for some or all patients based on the medical information stored in the auxiliary storage device 202. Furthermore, for example, the doctor terminal output module 213 and the embryologist terminal output module 214 may be configured to output the results of the analysis, estimation, or evaluation by the medical information and / or estimation module 250 to the doctor terminal 102 or the embryologist terminal 103, respectively. For example, the doctor terminal output module 213 and the embryologist terminal output module 214 may be configured to output the results of the analysis, estimation, or evaluation by the medical information and / or estimation module 250 to the doctor terminal 102 or the embryologist terminal 103, respectively, in response to a request from the doctor terminal 102 or the embryologist terminal 103.

[0219] 43 is an example of an egg collection cycle screen 4300 on the doctor terminal. The doctor terminal output module 213 displays the egg collection cycle screen 4300 on, for example, the doctor terminal 102. The doctor terminal output module 213 may be configured to display, for example, an estimation result 4310 regarding egg collection on the egg collection cycle screen 4300. The display of the estimation result 4310 by the doctor terminal output module 213 will be described below.

[0220] <Estimation of the Day When the Number of Eggs to be Collected is Maximum> The estimation module 250 is configured to estimate the menstrual cycle day (cycle day counting the first day of menstruation as Day 1) and the number of mature eggs (MII eggs) to be collected when a given drug (e.g., an ovulation-inducing agent) is administered to the patient, for example, based on the medical information of a given patient, statistically, based on medical knowledge, or using the machine learning model P1. As an example, the estimation module 250 is configured to estimate the egg collection status when a given ovulation-inducing agent (e.g., an ovulation-inducing agent registered in the list of oral medications and nasal sprays that can be prescribed in the egg collection cycle) is administered to the subject patient, for example, using the medical information of the subject patient (e.g., hormone levels, endometrial condition, etc.) and the machine learning model P1. The machine learning model P1 used by the estimation module 250 here is a machine learning model trained using medical information including, for example, at least a patient's past prescription information for ovulation-inducing drugs (e.g., hormone type, dosage, and administration timing) and the patient's vital data (e.g., age, BMI value, ovarian age hormone value (e.g., anti-Müllerian hormone (AMH) value)) as explanatory variables, and the number of mature eggs collected per day of the menstrual cycle as the objective variable. This machine learning model is trained using information based on (Step 1) acquired by the doctor, information based on (Step 2) acquired by the embryologist, and information based on (Step 3) acquired by the doctor.

[0221] <Display of Estimation Results> The estimation module 250 displays an estimation result 4310 regarding egg collection, superimposed on the egg collection cycle screen 4300, at any timing (e.g., when the doctor selects the egg collection cycle screen tab). According to the machine learning model P1 described above, for example, an estimated value for the number of mature eggs (MII eggs) collected for each day of the menstrual cycle is output as the estimation result. Based on this estimation result, the estimation module 250 displays the estimated number of mature eggs collected for each day of the menstrual cycle, for example, as a graph (e.g., a scatter plot including a smooth line) in the estimation result 4310. For example, the estimation module 250 displays the relationship between the days of the menstrual cycle (e.g., 3 to 7 days) including the day on which the maximum number of mature eggs is collected and the estimated number of mature eggs collected on that day. This allows the doctor to determine the day on which the maximum number of mature eggs is collected and to select that day or a day before or after that day as the egg collection day. As a result, egg collection performance (the number of mature eggs collected) can be improved.

[0222] 44 is an example of a hormone cycle screen 4400 on a doctor terminal. The doctor terminal output module 213 displays the hormone cycle screen 4400 on, for example, the doctor terminal 102. The doctor terminal output module 213 may be configured to display, for example, an estimation result 4410 regarding transplantation on the hormone cycle screen 4400. The display of the estimation result 4410 by the doctor terminal output module 213 will be described below.

[0223] <Estimation of Success Rate for Each Transplantation Date> The estimation module 250 may be configured to estimate the success rate for each transplantation date based on, for example, the medical information of a specific patient, statistically, based on medical knowledge, or using a machine learning model P2. The success rate for each transplantation date is, for example, the transplant success rate (e.g., implantation rate) when a transplant is performed on a specific day (a specific cycle day (hormonal cycle day or natural cycle day)) for a specific patient. As an example, the estimation module 250 is configured to estimate the success rate for each transplantation date for a specific patient using, for example, the medical information of the specific patient (e.g., embryo grade and patient vital data (cycle day, endometrial thickness and hormone levels on that day, etc.)) and the machine learning model P2. Here, the machine learning model P2 used by the estimation module 250 is, for example, a machine learning model trained using medical information about past patients, including at least embryo grade and patient vital data (cycle day, endometrial thickness and hormone levels on that day), as explanatory variables, and the transplantation date (e.g., cycle day) and the transplantation result (e.g., whether or not implantation occurred) as objective variables. The embryo grade may be, but is not limited to, a grade represented by the Gardner classification, or an embryo grade evaluation result based on human observation of an embryo image or an embryo grade evaluation result evaluated mechanically. The endometrial thickness may be, for example, a measurement result obtained by ultrasound examination.

[0224] Display of Estimated Results The doctor terminal output module 213 displays the transplantation estimation result 4410 superimposed on the hormone cycle screen 4400 or the hormone cycle screen at any time (e.g., when the doctor selects the hormone cycle screen tab or the natural cycle screen tab). According to the machine learning model P2, for example, an estimated value of the transplant success rate (e.g., implantation rate) for each transplantation day (e.g., cycle day (menstrual cycle day or hormone cycle day)) is output as the estimation result. Based on this estimation result, the estimation module 250 displays the estimated value of the transplantation success rate for each transplantation day, for example, as a graph (e.g., a histogram) in the estimation result 4410. For example, the estimation module 250 displays the relationship between the transplantation date and the transplantation success rate if transplantation is performed on that day for several days (e.g., seven days) including the cycle day with the highest transplantation success rate. This allows the doctor to determine the day with the highest transplantation success rate and select that day or a day before or after that day as the transplantation date. As a result, the transplantation outcome (implantation rate) can be improved.

[0225] 43 and 44 show an example in which the doctor terminal output module 213 displays the estimation results 4310 and 4410 on the screens 4300 and 4400 of the doctor terminal 102. However, the embryologist terminal output module 214 may be configured to display similar estimation results and graphs on the display screen of the embryologist terminal 103.

[0226] [Dashboard] The in vitro fertilization process in reproductive medicine can be broadly divided into three steps: (1) egg collection, (2) incubation, and (3) embryo transfer. While it is essential to comprehensively view these steps (1) through (3) to improve pregnancy outcomes, it is also important to focus on each individual step and understand factors and trends that may affect pregnancy success rates from various perspectives. The management server 101 can, for example, extract a portion of the information stored in the auxiliary storage device 202 from various perspectives and output this information in a visualized interface format to the doctor terminal 102 and / or the embryologist terminal 103 via a network. The management module 211 calculates desired indicators based on the extracted values ​​as needed and stores them in the auxiliary storage device 202. The doctor terminal output module 213 and the embryologist terminal output module 214 can output the extracted values ​​and calculated indicators to the doctor terminal 102 and / or the embryologist terminal 103 via a network. Specific examples of such output are described below.

[0227] 45 is an example of a dashboard screen 4500 of the doctor terminal 102 and / or the doctor terminal 103. The doctor terminal output module 213 and the doctor terminal output module 214 may be configured to display the dashboard screen 4500 on the doctor terminal 102 or the doctor terminal 103, respectively.

[0228] The doctor terminal output module 213 and the embryologist terminal output module 214 each display, on the dashboard screen 4500, for example, a patient number trend column 4510, a patient status column 4520, a number of treatment cycles column 4530, a number of egg collections column 4540, a number of transplants column 4550, a laboratory results column 4560, a pregnancy record column 4570, a cumulative pregnancy rate by number of egg collections column 4580, and a cumulative pregnancy rate by number of transplants column 4590.

[0229] The patient number trend column 4510 displays, for example, a histogram of the number of patients at the clinic for the current month and each of the past three months, color-coded by return visits and first visits, as well as a total, in absolute numbers and percentages (percentages), along with information on the comparison with the previous month, the same month last year, and the new patient rate. Information on the number of patients for each month of the past three months is calculated by the management module 211 based on, for example, treatment information 323 related to the treatment of patients for each day acquired from the doctor terminal 102 via the Internet by the acquisition module 212 of the management server 101, and stored in the auxiliary storage device 202. The patient behavior column 4520 displays, for example, the behavior of the clinic's patients (e.g., the number of first visits, graduations (cessation of consultation due to pregnancy or suspension of clinic visits), and transfers) as a color-coded histogram for the current month and each of the past three months, along with information on the absolute numbers, comparison with the previous month, and comparison with the same month last year. Information related to the behavior of patients at the clinic is calculated by the management module 211 based on, for example, treatment information 323 related to patient treatment for each day, which the acquisition module 212 of the management server 101 acquires from the doctor terminal 102 via the Internet, and stored in the auxiliary storage device 202. The number of treatment cycles column 4530 displays, for example, the number of treatment cycles for the patient for the current month as a histogram by age group, color-coded by treatment method (artificial insemination, egg collection, transplant, etc.). Information related to the number of treatment cycles is calculated by the management module 211 based on, for example, treatment information 323 related to patient treatment, which the acquisition module 212 of the management server 101 acquires from the doctor terminal 102 via the Internet, and stored in the auxiliary storage device 202.

[0230] The number of egg collections performed column 4540, for example, displays a histogram of the number of egg collection surgeries performed in the current month and the past three months, color-coded by patient age group, together with information on comparisons with the previous month and the same month last year, etc. Information on the number of egg collections performed is calculated by the management module 211 based on, for example, egg collection-related treatment information 323, etc., acquired by the acquisition module 212 of the management server 101 from the doctor terminal 102 via the Internet, and stored in the auxiliary storage device 202. The number of transplants performed column 4550, for example, displays a histogram of the number of transplant surgeries performed in the current month and the past three months, color-coded by patient age group, together with information on comparisons with the previous month and the same month last year, etc. Information on the number of transplants performed is calculated by the management module 211 based on, for example, transplant-related treatment information 323, etc., acquired by the acquisition module 212 of the management server 101 from the doctor terminal 102 via the Internet, and stored in the auxiliary storage device 202.

[0231] The laboratory results column 4560 displays, for example, a line graph showing the trend in the blastocyst achievement rate (average value) for the current month and the past three months, color-coded by patient age group and overall average, along with information on comparisons with the previous month and the same month last year. Generally, while the egg collection itself is performed by a doctor, the collected eggs are transported to the incubation room, and the egg collection results (e.g., number of eggs collected) and their management (whether or not to freeze them, etc.) are performed by an embryologist. Information related to the trend in the blastocyst achievement rate is calculated by the management module 211 based on, for example, embryo information 426 related to embryo growth acquired by the acquisition module 212 of the management server 101 from the embryologist terminal 103 via the Internet, and stored in the auxiliary storage device 202.

[0232] The pregnancy performance column 4570 displays, for example, a histogram of pregnancy rates for the current month and the past three months for patients who underwent transplant surgery in the previous month, as well as a line graph showing average trends by patient age group and overall, along with information on comparisons with the previous month and the same month last year. Information related to pregnancy performance is calculated by the management module 211 based on, for example, pregnancy-related treatment information 323 acquired from the doctor terminal 102 via the Internet by the acquisition module 212 of the management server 101 and information (e.g., embryo information 426) acquired from the embryologist terminal 103, and stored in the auxiliary storage device 202. For example, the management module 211 calculates the pregnancy rate by adding information obtained from the embryologist terminal as a variable to the information related to pregnancy establishment acquired from the doctor terminal 102. Information acquired from the embryologist terminal, for example, can include the doctor's order for embryo transfer and the status based on that order (e.g., whether a frozen embryo or a fresh embryo was transferred, and the status of each embryo in that case).

[0233] The cumulative pregnancy rate by egg collection count column 4580 displays, for example, a histogram of the number of pregnancies for each egg collection count and a line graph of the cumulative pregnancy rate trend, color-coded by patient age group and overall average, as a total number and percentage. Information related to the cumulative pregnancy rate by egg collection count is calculated by the management module 211 based on, for example, egg collection and pregnancy-related treatment information 323 acquired by the acquisition module 212 of the management server 101 from the doctor terminal 102 via the Internet and information (e.g., embryo information 426) acquired from the embryologist terminal 103, and stored in the auxiliary storage device 202. Information acquired from the embryologist terminal may include, in addition to the pregnancy rate information, for example, the nth egg collection result (n is a natural number) for each patient. The egg collection results may include, for example, the number of eggs collected, as well as the results of in vitro culture (e.g., the number of frozen embryos and their status (e.g., the number of blastocysts, the number of frozen early embryos, the number of fertilized embryos)).

[0234] The cumulative pregnancy rate by number of transfers column 4590 displays, for example, a histogram of the number of pregnancies for each number of transfers and a line graph of the cumulative pregnancy rate over time, color-coded by patient age group and overall average, as a total number and percentage. Information related to the cumulative pregnancy rate by number of egg collections is calculated by the management module 211 based on, for example, the treatment information 323 related to transfer and pregnancy acquired by the acquisition module 212 of the management server 101 from the doctor terminal 102 via the Internet and information (e.g., embryo information 426) acquired from the embryologist terminal 103, and is stored in the auxiliary storage device 202.

[0235] With this configuration, the information stored in the auxiliary storage device 202 is visualized and displayed in a visually easy-to-understand format, allowing this information to be effectively utilized in clinical practice. Note that the information analyzed by the management server 101 and displayed on the dashboard screen 4500 is not limited to the above example. For example, the management server 101 can aggregate and analyze information from various perspectives based on any combination of information stored in the auxiliary storage device 202, and display the results on the dashboard screen 4500. As an example, information about the entire clinic or information about all patients can be aggregated retrospectively from various perspectives.

[0236] <Other Modifications> Each module disclosed in the above embodiment may be configured by combining multiple sub-modules. Furthermore, some or all of the operations or functions performed by one module may be performed or realized by another module.

[0237] In the above embodiment, one or more functional elements realized by the execution of each module of the embryologist terminal 103 may be realized by the execution of a module of the doctor terminal 102.

[0238] Furthermore, one or more of the one or more management servers 101 and one or more patient terminals 104 constituting the reproductive medicine support system 1 according to the present technology may be installed in different countries. Furthermore, the management server 101 may be realized by one or more computers, any of which may be installed in different countries.

[0239] In the above embodiment, the embryologist terminal is a device located outside the medical institution where the doctor terminal is located, and one or more embryologist terminals 103 are connected to a different embryologist terminal network that is independent of the medical institution's internal network. However, the embryologist terminal may also be a device located within the same medical institution as the doctor terminal, and one or more embryologist terminals 103 may be connected to the same medical institution's internal network, for example.

[0240] In the above embodiment, the management server 101, the doctor terminal 102, and the embryologist terminal 103 are separate entities. However, the management server 101 and the doctor terminal 102 and / or the embryologist terminal 103 may be integrated. Furthermore, the doctor terminal 102 and the embryologist terminal 103 may be configured as a single terminal, for example, by simultaneously installing a doctor's business application and an embryologist's business application on a single terminal.

[0241] In the above embodiment, when the acquisition module 212 receives input from an operator (e.g., a doctor or an embryologist) of the doctor terminal 102 or the embryologist terminal 103, it extracts data that meets the conditions corresponding to the input. Several examples of the conditions corresponding to the input are shown. However, the conditions used for extraction by the acquisition module 212 are not limited to the above examples. Other examples of conditions used for extraction by the acquisition module 212 include various conditions (indicators or items) that may affect the success of pregnancy, such as conditions of treatment or procedures administered to the patient or embryo, such as the type of culture medium used in embryo culture (external factors), the patient's condition, such as a disease the patient has (intrinsic factors), and conditions related to the doctor's or embryologist's judgment (external factors). Two or more indices or items can be combined to form a single condition. Furthermore, conditions related to the doctor's or embryologist's judgment may include, for example, peripheral information related to the patient's main complaint (e.g., desire to minimize the time until pregnancy, minimize costs, etc.), and the doctor's or embryologist's interpretation or judgment based on the incubation observation status.

[0242] In the above embodiment, the management module 211 outputs different patient information screens (see, for example, Figures 18 and 19) to the embryologist terminal and the physician terminal, and also displays different patient information on the patient information screens. However, the management module 211 may make the patient information output to the embryologist terminal and the patient information output to the physician terminal the same. In this case, for example, it is preferable in that it allows the embryologists to share more patient information. Furthermore, the management module 211 may make the patient information screen output to the embryologist terminal and the patient information screen output to the physician terminal substantially identical in configuration. In this case, the layout of each patient information is the same on the patient information screen of the physician terminal and the patient information screen of the embryologist terminal, which is preferable in that it makes it easier for the physician and embryologist to communicate with each other, for example.

[0243] In the above embodiment, a consent form confirmation field is displayed on the doctor terminal 102, and the consent form information management module 219 displays, for example, information indicating that all required consent forms have been received in a consent form receipt confirmation field on the doctor terminal 102. However, the consent form information management module 219 may also be configured to acquire information regarding the consent forms from the doctor terminal 102 and output the acquired information regarding the consent forms to the embryologist terminal 103.

[0244] In this case, the management module 211 outputs the same consent form list screen on the doctor terminal 102 as on the embryologist terminal 103. For example, when a doctor receives a consent form, he or she checks the corresponding consent form receipt field on the consent form list screen of the doctor terminal 102 and enters information identifying the receiving doctor in the recipient field. The consent form information management module 219 acquires these entries on the doctor terminal 102 and stores them as consent form information 225. The consent form information management module 219 also displays information indicating that the consent form has been received (a check in the consent form receipt field) and information about the recipient on the consent form list screen 3300 of the embryologist terminal 103. This configuration allows doctors and embryologists to share the latest information and handle the distribution and receipt of consent forms, which can be difficult to manage.

[0245] In the above embodiment, the explanation has focused on an example in which the management server 101 facilitates collaboration between the doctor terminal 102 and the embryologist terminal 103. However, in this reproductive medicine support system 1, collaboration is not limited to collaboration between the doctor terminal 102 and the embryologist terminal 103, and collaboration can be achieved between all terminals that can be connected to the management server 101. For example, the installation location of each terminal is not particularly limited. For example, for remote medical treatment, information necessary for diagnosis can be obtained at facility A, and the relevant information can be displayed on a terminal at another facility B for diagnosis. For example, the management server 101, the doctor (doctor terminal 102), and the embryologist (embryologist terminal 103) may be connected within the network of the same medical facility, or each or some of the devices may be located in different medical facilities and connected to each other via a network such as the Internet.

[0246] In the above embodiment, the management server 101 is configured to extract and output medical information. From another perspective, the reproductive medicine support system 1 stores various information, such as patient information 221, partner information 222, treatment information 223, owned drug information 224, consent form information 225, embryo information 226, sperm management information 227, drug information 228, prescription schedule information 229, freezing management information 230, and machine learning model P, in the auxiliary storage device 202, and can be understood as a system that integrates and manages this information.

[0247] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, it is possible to replace part of the configuration of one embodiment with the configuration of another embodiment, or to add the configuration of another embodiment to the configuration of one embodiment. Furthermore, it is possible to add, delete, or replace part of the configuration of each embodiment with other configurations.

[0248] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The above-described configurations, functions, etc. may also be implemented in software, with a processor interpreting and executing a program that implements each function. Information such as the programs, tables, and files that implement each function can be stored in a memory, a recording device such as a hard disk or SSD (Solid State Drive), or a recording medium such as an IC card, SD card, or DVD.

[0249] Furthermore, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all the control lines and information lines in the product. In reality, it can be considered that almost all components are interconnected. The above-mentioned embodiments disclose at least the configurations described in the claims.

[0250] 1...Reproductive medicine support system, 101...Management server, 102...Doctor terminal, 103...Embryologist terminal, 104...Patient terminal, 105...Medical equipment, 211...Management module, 212...Acquisition module, 213...Doctor terminal output module, 214...Embryologist terminal output module, 215...First prescription module, 216...Second prescription module, 217...Referral letter output module, 218...Medical record information extraction module, 219...Consent form information management module, 220...Semen evaluation module, 250...Estimation module, 251...Patient terminal output module

Claims

1. an acquisition unit that acquires medical information related to the patient's reproductive medicine; a doctor terminal output unit that outputs at least a part of the medical information to a doctor terminal connected via the Internet and used by the doctor; An embryologist terminal output unit that outputs test information relating to at least one of eggs, embryos, or sperm from the medical information to an embryologist terminal located outside the medical institution where the doctor terminal used by the embryologist is located, the test information being connected via the Internet; Equipped with the acquiring unit is configured to acquire, as the medical information, treatment information related to treatment for the patient from the doctor terminal; The embryologist terminal output unit is configured to output the acquired treatment information to the embryologist terminal.

2. The embryologist terminal output unit outputs the acquired information about the treatment to the embryologist terminal when the acquisition unit acquires information about the treatment for at least one of an egg, an embryo, or a sperm as the treatment information from the doctor terminal. The reproductive medicine support server according to claim 1.

3. The embryologist terminal output unit outputs information about the selected embryo to the embryologist terminal when the acquisition unit acquires information about selecting an embryo to be transferred as the treatment information. The reproductive medicine support server according to claim 1.

4. When the acquisition unit acquires status information, which is information regarding the status of at least one of an egg, an embryo, or a sperm, from the embryologist terminal via the Internet, the doctor terminal output unit outputs the acquired status information to the doctor terminal via the Internet. The reproductive medicine support server according to claim 1.

5. A management unit is provided which calculates information relating to pregnancy results based on pregnancy-related treatment information acquired from the doctor's terminal via the Internet and embryo information acquired from the embryologist's terminal, The doctor terminal output unit outputs information related to the pregnancy results to the doctor terminal, The embryologist terminal output unit outputs information related to the pregnancy record to the embryologist terminal, The reproductive medicine support server according to claim 1.

6. The management unit calculates information related to the pregnancy results based on the treatment information related to the pregnancy obtained from the doctor's terminal and information indicating whether frozen embryos were transplanted and information indicating the state of each embryo in that case obtained from the embryologist's terminal. The reproductive medicine support server according to claim 5.

7. The acquisition unit is configured to transmit identification information of a specific patient to the embryologist terminal via a network, and acquire status information from the embryologist terminal, the status information being information on the status of at least one of an egg, an embryo, or a sperm, extracted in correspondence with the identification information of the specific patient at the embryologist terminal. The reproductive medicine support server according to claim 1.

8. The embryologist terminal output unit receives identification information of a specific patient from the embryologist terminal via a network, and the embryologist terminal output module extracts treatment information corresponding to the identification information of the specific patient and outputs the extracted treatment information to the embryologist terminal. The reproductive medicine support server according to claim 1.

9. The embryologist terminal output unit is configured to accept input from the doctor terminal or the embryologist terminal corresponding to at least one of patient identification information, a specific age, information identifying the patient, information identifying the treatment method and / or medication used, and information identifying the evaluation results of the embryo or sperm, extract information corresponding to the input, and acquire or transmit the extracted information to the embryologist terminal. The reproductive medicine support server according to claim 1.

10. The doctor terminal output unit is configured to accept input from the doctor terminal or the embryologist terminal corresponding to at least one of patient identification information, a specific age, information identifying the patient, information identifying the treatment method and / or the medication used, and information identifying the evaluation results of the embryo or sperm, extract information corresponding to the input, and acquire or transmit the extracted information to the doctor terminal. The reproductive medicine support server according to claim 1.

11. A cryptographic unit capable of encrypting and transmitting the treatment information, The encryption unit transmits authentication information to the doctor terminal or the embryologist terminal, The acquisition unit acquires the treatment information encrypted using the authentication information by the doctor terminal or the embryologist terminal, The reproductive medicine support server according to claim 1.

12. A cryptographic unit capable of encrypting and transmitting the treatment information, The encryption unit acquires authentication information from the doctor terminal, encrypts the treatment information using the acquired authentication information, and transmits the encrypted treatment information to the doctor terminal; or The encryption unit acquires authentication information from the embryologist terminal, encrypts the treatment information using the acquired authentication information, and transmits the encrypted treatment information to the embryologist terminal. The reproductive medicine support server according to claim 1.

13. an embryo classification unit that inputs an image of an embryo to be evaluated from the medical information into an embryo evaluation model and classifies the embryo to be evaluated based on the evaluation result output from the embryo evaluation model; the embryo evaluation model is trained to use an image of an embryo and information about the embryo as input data, and to use information related to the establishment of pregnancy of the embryo as output data; The doctor terminal output unit and the embryologist terminal output unit are each configured to output the classification result of the embryo to be evaluated, classified by the embryo classification unit, to the doctor terminal or the embryologist terminal, in response to a request from the doctor terminal or the embryologist terminal, The reproductive medicine support server according to claim 1.

14. The image of the embryo used as the input data is a time-lapse image of the embryo, The time-lapse images of the embryos are associated with information about the elapsed time since insemination, The acquisition unit acquires, from the embryologist terminal, a time-lapse image of the embryo and information regarding the elapsed time since the insemination, The embryo classification unit inputs the time-lapse image of the embryo and information regarding the elapsed time since insemination, which the acquisition unit acquired from the embryologist terminal, into the embryo evaluation model, and acquires an evaluation result of the embryo from the embryo evaluation model. The reproductive medicine support server according to claim 13.

15. The image of the embryo used as the input data is a time-lapse image of the embryo, The time-lapse images of the embryos are associated with information about the elapsed time since insemination, The acquisition unit acquires a portion of the input data including the time-lapse image of the embryo from an embryologist terminal and acquires another portion of the input data from a doctor terminal; The embryo classification unit inputs the input data acquired by the acquisition unit from the embryologist terminal and the doctor terminal into the embryo evaluation model, and acquires an evaluation result of the embryo from the embryo evaluation model. The reproductive medicine support server according to claim 13.

16. A patient terminal output unit is further provided for outputting at least one of the test results and the medical treatment results to the patient terminal, the acquiring unit acquires information about an embryo of a patient associated with the patient terminal from the medical information; the patient terminal output unit outputs, to the patient terminal, the acquired information about the embryo, which is information about the embryo culture results of the patient. The reproductive medicine support server according to claim 1.

17. 1. A computer-implemented method comprising: Acquires medical information from the doctor's terminal regarding treatment for the patient, A reproductive medical support method in which the acquired treatment information is output to an embryologist terminal.

18. A program causing a computer to execute the steps of claim 17.