Reproductive Medicine Support Server and Support Methods

By enabling information exchange between doctors and embryologists through a reproductive medicine support server, the shortcomings in collaborative support between doctors and embryologists for patients are addressed, thereby improving the synergy and efficiency of reproductive medicine treatments.

CN123125664APending Publication Date: 2026-11-17MEDIDA CO LTD
View PDF 3 Cites 0 Cited by

Patent Information

Application Number
CN202580025016.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-07-10
Filing Date
2025-03-27
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

In existing technologies, the collaborative support mechanisms between doctors and embryologists in reproductive medicine are not fully disclosed, resulting in insufficient and inefficient treatment support for patients in reproductive medicine.

Method used

A reproductive medicine support server is provided, including an acquisition unit and an output unit, for information exchange between a doctor's terminal and an embryologist's terminal, enabling a mechanism for collaborative support of patients by doctors and embryologists.

Benefits of technology

This has enabled a collaborative mechanism between doctors and embryologists to support patients, improving the synergy and efficiency of reproductive medicine treatments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123125664A_ABST
    Figure CN123125664A_ABST
Patent Text Reader

Abstract

A mechanism is provided that enables doctors and embryologists to jointly support patients. The reproductive medicine support server includes: an acquisition unit for acquiring medical information related to the patient's reproductive medicine; a doctor terminal output unit for outputting at least a portion of the medical information to a doctor's terminal; and an embryologist terminal output unit for outputting examination information related to at least one of oocytes, embryos, culture medium, or sperm from the medical information to an embryologist terminal. The acquisition unit is configured to acquire treatment information related to the patient's treatment from the doctor's terminal as the medical information, and the embryologist terminal output unit is configured to output the acquired treatment information to the embryologist terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Cross-references to related applications

[0001] This patent application claims priority to Japanese Patent Application No. 2024-050765, filed on March 27, 2024, entitled “Reproductive Medicine Support Server and Support Method”, and Japanese Patent Application No. 2024-111103, filed on July 10, 2024, entitled “Reproductive Medicine Support Server and Support Method”, the entire contents of which are incorporated herein by reference. Technical Field

[0002] This invention relates to a reproductive medicine support server and support method. Background Technology

[0003] As background technology in this field, there is Japanese Patent Application Publication No. 2019-076087 (Patent Document 1). This publication describes a “fertilized egg quality assessment system comprising an information processing apparatus for assessing the quality of fertilized eggs using cloud computing, the information processing apparatus comprising: an acquisition unit that acquires multiple observation images of fertilized eggs taken in a time sequence and associated with inherent identification information from a terminal device via a network; an analysis unit that generates fertilized egg analysis information based on the multiple observation images; and an output unit that outputs assessment support information including the identification information and the fertilized egg analysis information via the network to a computer that receives fertilized egg assessment information input based on the assessment support information.” (See abstract).

[0004] [Existing Technical Documents] [Patent Literature] [Patent Document 1]: Japanese Patent Application Publication No. 2019-076087. Summary of the Invention

[0005] The problem to be solved by the present invention According to the fertilized egg quality assessment system in Patent Document 1, highly accurate fertilized egg quality assessment results can be obtained. In reproductive medicine, sometimes doctors perform all procedures from examination to embryo culture, but generally, an embryologist supports reproductive medicine under the guidance of a doctor. In this respect, Patent Document 1 does not disclose a structure for collaborative support of patients by doctors and embryologists in reproductive medicine.

[0006] In response, this invention provides a mechanism for doctors and embryologists (hereinafter sometimes simply referred to as "embryologists") to collaborate in supporting patients.

[0007] Technical means to solve the problem To solve the above problems, for example, the structure described in the claims can be adopted.

[0008] This invention includes multiple structures or methods for solving the above-mentioned problems. One example is a reproductive medicine support server, comprising: an acquisition unit for acquiring medical information related to a patient's reproductive medicine; a doctor terminal output unit for outputting at least a portion of the medical information to a doctor's terminal; and a trainer terminal output unit for outputting examination information related to at least one of an egg, embryo, or sperm from the medical information to a trainer's terminal. The acquisition unit is configured to acquire treatment information related to the patient's treatment from the doctor's terminal as the medical information, and the trainer terminal output unit is configured to output the acquired treatment information to the trainer's terminal.

[0009] Invention Effects According to the present invention, a mechanism can be provided in which doctors and embryologists can collaborate to support patients.

[0010] The following implementation plan clarifies the issues, structure, and effects beyond those mentioned above. Attached Figure Description

[0011] Figure 1 This is an example of the overall structure of a reproductive medicine support system; Figure 2 This is an example of the hardware structure of the management server 101; Figure 3 This is an example of the hardware structure of the doctor terminal 102; Figure 4 This is an example of the hardware structure of the trainer terminal 103; Figure 5 This is an example of the hardware structure of the patient terminal 104; Figure 6 Examples of the contents of (A) patient information, (B) partner information, (C) treatment information, (D) proprietary medication information, (E) consent form information, and (F) embryo information; Figure 7 Examples of the contents of (G) sperm management information, (H) medication information, (I) prescription schedule information, and (J) cryopreservation management information; Figure 8 This is an example of a reproductive medicine support process; Figure 9 This is an example of a reproductive medicine support process; Figure 10 This is an example of an automated prescription entry process; Figure 11 This is another example of an automated prescription entry process; Figure 12 This is an example of a residual medication management process; Figure 13This is another example of an automated prescription entry process; Figure 14 This is an example of the referral letter creation process; Figure 15 This is an example of a medical record information extraction process; Figure 16 This is an example of a consent form information management process; Figure 17 This is an example of a semen evaluation process; Figure 18 This is an example of a patient information screen on a doctor's terminal; Figure 19 This is an example of a patient information screen on the trainer's terminal; Figure 20 This is an example of an overall image of the treatment history calendar displayed on the doctor's terminal; Figure 21 This is an example of a screenshot from a doctor's terminal during an egg retrieval cycle; Figure 22 (A), (B1), and (B2) are examples of the display of the prescription drug input field; Figure 23 This is another example of the prescription drug input field; Figure 24 (A) to (C) are examples of a portion of the screen displayed during an egg retrieval cycle; Figure 25 This is an example of the egg retrieval ET screen on the embryologist's terminal; Figure 26 It is a pop-up display of embryo images; Figure 27 This is an example of a hormone cycle display on a doctor's terminal; Figure 28 This is an example of the unfreezing ET screen on the trainer's terminal; Figure 29 This is an example of the screen for selecting objects to unfreeze; Figure 30 This is another example of the egg retrieval ET screen on the embryologist's terminal; Figure 31 This is an example of a pregnancy medical record screen displayed on a doctor's terminal. Figure 32 This is an example of a pop-up display of a referral letter; Figure 33 This is an example of a screenshot of the consent form on the trainer's terminal; Figure 34 This is an example of a pop-up confirmation screen for a consent form; Figure 35 This is an example of a pop-up display of a copy of the consent form; Figure 36This is an example of a sperm examination / freezing screen on a sperm culture technician's terminal; Figure 37 This is another example of the egg retrieval cycle screen displayed on a doctor's terminal; Figure 38 This is an example of a consent form submission screen; Figure 39 Here is an example of a screen displaying examination and treatment results reports; Figure 40 This is an example of a screen showing medication administration and management. Figure 41 Here is an example of a patient learning from images; Figure 42 This is an example of a screen showing medication administration and management. Figure 43 This is another example of the egg retrieval cycle screen displayed on a doctor's terminal; Figure 44 Here is an example of a hormone cycle display on a doctor's terminal; and Figure 45 This is an example of a control panel screen. Detailed Implementation

[0012] The reproductive medicine support system, reproductive medicine support method, and procedure products of the present invention will be described below with appropriate reference to the accompanying drawings. Furthermore, the content shown in the drawings is for illustrative purposes only and may not be identical to the actual content shown, and there may be inconsistencies between the drawings.

[0013] [Reproductive Medicine Support System] Figure 1 This is an example of the overall structure of the reproductive medicine support system 1 of the implementation plan.

[0014] Regarding the reproductive medicine support system 1 of the present invention, typically in the field of reproductive medicine, it is a system used by doctors and embryologists to collaboratively support patients.

[0015] Furthermore, in this manual, reproductive medicine refers broadly to medicine performed to achieve pregnancy. Reproductive medicine typically addresses infertility and includes procedures such as assisted reproductive technology (ART), reproductive medicine, and assisted reproductive therapy. Reproductive medicine may also include, for example, individual tests such as ovarian reserve function testing and semen analysis, or procedures such as cryopreservation of eggs and sperm, artificial insemination, or timing-based therapy, which are used partially or initially for reproductive purposes.

[0016] like Figure 1As shown, the reproductive medicine support system 1 comprises one or more management servers 101, one or more doctor terminals 102, and one or more trainer terminals 103. Furthermore, the reproductive medicine support system 1 may also independently include one or more patient terminals 104 and one or more medical devices 105. The management server 101, doctor terminals 102, trainer terminals 103, patient terminals 104, and medical devices 105 can send and receive mutually permitted information via wired or wireless networks.

[0017] Here, for example, one or more doctor terminals 102 constitute an internal network of the medical institution. Furthermore, within this internal network, for example, one or more doctor terminals 102 constitute a separate network of doctor terminals, each doctor terminal 102 providing a doctor's work application suitable for performing medical duties.

[0018] In addition, the medical institution’s internal network and the trainer’s terminal network are connected via the Internet, and the authentication modules of the doctor’s terminal 102 and the trainer’s terminal 103 can be interconnected through authentication.

[0019] Furthermore, one or more patient terminals 104 are external terminals that are not permitted to connect to the medical institution's internal network and are configured to connect to the reproductive medicine support system 1 via the Internet. Patient terminals 104 provide, for example, patient-use applications suitable for receiving patient-oriented reproductive medicine support services.

[0020] In addition, the management server 101 is connected to the medical institution's internal network and the trainer terminal network via the Internet. The authentication modules of the doctor terminal 102 and the trainer terminal 103 can connect to the management server 101 through authentication. The authentication module of the management server 101 determines whether the authentication from the authentication modules of the doctor terminal 102 and the trainer terminal 103 is successful.

[0021] The doctor terminal 102, trainer terminal 103, and patient terminal 104 (hereinafter, sometimes referred to as "terminals") or management server 101 in the reproductive medicine support system 1 can be portable terminals (mobile terminals) such as smartphones, tablets, mobile phones, or portable information terminals (PDAs), or wearable terminals such as glasses (including goggles), watches, or clothing. Furthermore, each terminal and management server 101 can also be a fixed or portable computer, or a server configured in the cloud or on a network. In addition, from a functional point of view, it can also be a VR (Virtual Reality) terminal, an AR (Augmented Reality) terminal, or a MR (Mixed Reality) terminal. Alternatively, each terminal and management server 101 can also be a combination of these. For example, a combination of a smartphone and a wearable terminal can logically function as a single terminal. Furthermore, each terminal can also be other information processing terminals.

[0022] Each terminal or management server 101 of the reproductive medicine support system 1 may arbitrarily include a processor that executes an operating system or application program, a main storage device such as RAM (Random Access Memory), an auxiliary storage device such as an IC card or hard disk drive, an SSD (Solid State Drive), or flash memory, a communication control unit such as a network card or wireless communication module or mobile communication module, an input device such as a touch panel or keyboard, a mouse, an audio input device, a motion controller, an input device for motion detection using a camera, a sensor such as a GPS or gyroscope sensor or an accelerometer sensor, and an output device such as a monitor or display. Furthermore, the output device may also be a device or terminal for transmitting information to external monitors or displays, printers, sound output devices, oscillators, or other similar devices.

[0023] The main storage device stores various programs or application programs (software modules), and the processor executes these programs or application programs to realize the various functional elements of the entire system. Furthermore, each module can be installed as a separate, independent program or application program, or as a subroutine or function within a unified program or application program. Additionally, each module can be installed as hardware (hardware modules) by integrating circuitry or employing a microcomputer.

[0024] Furthermore, each module can be implemented using a single processor or multiple processors. Additionally, each module can be located in a single terminal or management server 101, or it can be separately located in two or more terminals or management servers 101 interconnected via a network. Furthermore, each module can also be located in any one or more of two or more terminals or management servers 101 interconnected via a network. The possibility of some modules being implemented in countries different from the other modules has also been considered.

[0025] In this specification, each module is described as the subject of processing, but in reality, the processor performs processing by executing programs or applications that implement each module.

[0026] The auxiliary storage device stores various databases (DBs). A "database" is, for example, a collection of data organized and collected in a manner capable of handling any data operations (e.g., extraction, appending, deleting, overwriting, etc.) from a processor or external computer. There are no particular limitations on the type of data; it can be, for example, text data, audio data, image data, video data, 3D (three-dimensional) data, programs, etc. The auxiliary storage device is a functional element (storage unit) for storing one or more collections of data. The method of installing the database is not limited to this example; it can be, for example, a database management system, spreadsheet software, or text files such as XML (extensible markup language), JSON (JavaScript object notation), etc. Some or all of the information can be stored in a relational database or a non-relational database structure. The database can be connected to a processor or other devices in a state independent of the processor settings. For example, various data can be distributed across multiple database servers or cloud applications.

[0027] [Manage Server] Figure 2 The hardware structure of management server 101 is shown. Management server 101 manages the operations of reproductive medicine support system 1. Management server 101 may be, for example, a server configured in the cloud. Management server 101 can typically be a terminal used by an administrator managing the reproductive medicine support system 1.

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

[0029] The main storage device 201 stores programs or application programs such as a management module 211, an acquisition module 212, a doctor terminal output module 213, a trainer terminal output module 214, a first prescription module 215, a second prescription module 216, a referral information output module 217, a medical record information extraction module 218, a consent form information management module 219, a semen evaluation module 220, a calculation module 250, and a patient terminal output module 251. The various functional elements of the management server 101 are implemented by the processor 203 executing the programs or application programs stored in the main storage device 201.

[0030] The auxiliary storage device 202 stores information required for the operation of the management server 101 in the reproductive medicine support system 1. As an example of the information in this invention, the auxiliary storage device 202 stores medical information such as patient information 221, partner information 222, treatment information 223, proprietary medication information 224, consent form information 225, embryo information 226, sperm management information 227, medication information 228, prescription schedule information 229, cryopreservation management information 230, and a machine learning model P. The details of this information will be described below. Furthermore, the auxiliary storage device 202 may include various other information besides the information described above.

[0031] The functional elements of the management server 101 are briefly described.

[0032] The management module 211 comprehensively controls the basic operations of the management server 101 used to implement the reproductive medicine support system 1. The management module 211 causes the doctor terminal 102 to output (display), for example, the top screen of the reproductive medicine support application used with the reproductive medicine support system 1, the patient information screen, the treatment plan screen, the general infertility screen, the egg retrieval cycle screen, the hormone cycle screen, the natural cycle screen, the post-pregnancy medical record screen, and the emergency visit screen. Furthermore, the management module 211 causes the trainer terminal 103 to output (display), for example, the top screen of the reproductive medicine support application, the patient information screen, the consent form overview screen, the egg retrieval ET screen, the cryopreservation management screen, the thawing ET screen, and the semen analysis / freezing screen. The management module 211 inputs or records information for the specified items on the screens according to the screen output. The management module 211 provides doctors and trainers with various information related to reproductive medicine through these screens and supports doctors and trainers in smoothly applying reproductive medicine to patients.

[0033] In addition, in order to realize the reproductive medicine support system 1, the management module 211 may combine the actions of various modules as needed, such as the acquisition module 212, the doctor terminal output module 213, the trainer terminal output module 214, the first prescription module 215, the second prescription module 216, the referral information output module 217, the medical record information extraction module 218, the consent form information management module 219, the semen evaluation module 220, the calculation module 250, and the patient terminal output module 251.

[0034] The acquisition module 212 acquires medical information related to the patient's reproductive medicine. For example, the acquisition module 212 acquires patient information 221, partner information 222, treatment information 223, proprietary medication information 224, consent form information 225, embryo information 226, sperm management information 227, medication information 228, prescription schedule information 229, cryopreservation management information 230, etc., sent via the Internet from the doctor terminal 102, trainer terminal 103, patient terminal 104, medical device 105, etc. The acquisition module 212 acquires this information, for example, through the aforementioned screen, and stores the acquired information in the auxiliary storage device 202. Furthermore, the information stored using the acquisition module 212 can be used for new storage, addition, correction, deletion, etc. In this specification, "receiving input" by the acquisition module 212 means that the acquisition module 212 receives input information and, for example, records the input information in the auxiliary storage device 202 (the same applies to other terminals).

[0035] The doctor terminal output module 213 outputs information acquired from the embryologist terminal 103 to the doctor terminal 102. For example, the doctor terminal output module 213 outputs status information, which relates to the status of at least one of the egg, embryo, culture medium, or sperm, acquired from the embryologist terminal 103, to the doctor terminal 102 via the Internet. Alternatively, the doctor terminal output module 213 can also be configured to output, for example, examination information, which relates to at least one of the egg, embryo, culture medium, or sperm, acquired from the medical device 105, to the doctor terminal 102. The doctor terminal output module 213 can, for example, output specified information from the information acquired from the embryologist terminal 103 or the medical device 105 to the doctor terminal 102.

[0036] The trainer terminal output module 214 outputs information obtained from the doctor terminal 102 to the trainer terminal 103. For example, the trainer terminal output module 214 outputs treatment information (treatment information 223) obtained from the doctor terminal 102 related to the patient's treatment to the trainer terminal 103 via the Internet. Alternatively, the trainer terminal output module 214 can also be configured to output, for example, information obtained from the medical device 105 related to at least one of the egg, embryo, culture medium, or sperm (examination information) to the trainer terminal 103. The trainer terminal output module 214 can, for example, output permitted information from the treatment information 223 to the trainer terminal 103.

[0037] The first prescription module 215 supports the input of prescription information for medications in the doctor's terminal 102. The first prescription module 215 acquires information related to the prescription drug and the prescription date, and automatically outputs other prescription information based on the acquired information and prescribed rules.

[0038] The second prescription module 216 supports the input of prescription information for medications in the doctor's terminal 102. The second prescription module 216 acquires information related to the patient's treatment name and treatment date, and automatically outputs prescription information based on the acquired information and prescribed rules.

[0039] The referral letter output module 217 supports the creation of medical information provision forms (hereinafter sometimes referred to as "referral letters") from the doctor's terminal 102 to other medical institutions. For example, the referral letter output module 217 extracts referral letter information about establishing a correspondence with the patient from the acquired medical information, and outputs it after establishing a correspondence with a pre-prepared referral letter format.

[0040] The medical record information extraction module 218 supports the recording of medical information in electronic medical records. For example, the medical record information extraction module 218 extracts information associated with prescribed medical record entries from medical information obtained from the reproductive medicine support system 1. The medical record information extraction module 218 can be configured to, for example, output the extracted information associated with the prescribed medical record entries.

[0041] 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 processed and the frequency of their retrieval are significantly higher compared to other medical fields. The Consent Form Information Management Module 219 supports the retrieval of consent forms and the management of information related to them.

[0042] The semen assessment module 220 supports semen assessment based on information related to semen examination. For example, based on information related to the patient's semen examination, the semen assessment module 220 outputs information indicating that the patient's semen meets the prescribed criteria when the information related to the semen examination meets the prescribed criteria, and outputs information indicating that the patient's semen does not meet the prescribed criteria when the information related to the semen examination does not meet the prescribed criteria.

[0043] The calculation module 250 outputs reference information related to the diagnosis or judgment of infertility treatment. For example, based on acquired information, the calculation module 250 generates and outputs information useful for determining various diagnostic or treatment strategies related to a patient's infertility treatment through data analysis or artificial intelligence (AI) prediction. The calculation module 250 outputs the generated information, for example, to the doctor's terminal 102 or the embryologist's terminal 103. The calculation module 250 is, for example, an example of the embryo classification unit in this invention. The calculation module 250 can be configured to, for example, implement an annotation function for assigning annotations to embryo images when classifying embryos of an assessment subject based on embryo images of the assessment subject.

[0044] The patient terminal output module 251 outputs various information related to infertility treatment to the patient terminal 104. For example, via the Internet, the patient terminal output module 251 outputs to the patient terminal 104 the top screen of the patient application used in the reproductive medicine support system 1, the consent form submission screen, the examination and treatment result report screen, the medication administration and management screen, the patient learning screen, etc. The patient terminal output module 251 outputs prescribed information to the patient terminal 104 at the prescribed times according to the patient terminal service provision program, or based on instructions from the doctor terminal 102 or the therapist terminal 103.

[0045] The information stored in the auxiliary storage device 202 will be briefly described.

[0046] Figure 6 Examples of content for (A) patient information, (B) partner information, (C) treatment information, (D) proprietary medication information, (E) consent form information, and (F) embryo information. Figure 7 These are examples of the contents of (G) sperm management information, (H) medication information, (I) prescription schedule information, and (J) cryopreservation management information. Information (A) through (J) are examples of medical information. Furthermore, the classification and storage methods for various types of information are not limited to the examples described.

[0047] Patient information 221 contains basic information about the female patient's attributes. The patient may be someone who is pregnant herself, or someone who has retrieved eggs from her own body. In this implementation, patient information 221 may include, for example, patient ID and other identifying information, name, date of birth, information about the partner (e.g., male spouse) who is the object of the pregnancy, height, weight, BMI (body mass index) value, allergy information, medical history, menstrual cycle, pregnancy history, etc. For example, a correspondence is established between patient IDs (the same applies to establishing correspondences for the information below).

[0048] Partner information 222 contains basic information about the male patient's attributes. In this embodiment, partner information 222 may include, for example, identification information such as partner ID, name, date of birth, information about the partner (e.g., female spouse) who is the object of the pregnancy (e.g., patient ID), height, weight, BMI, allergy information, medical history, etc. For example, a correspondence is established between partner information 222 and the corresponding patient's identification information (e.g., patient ID).

[0049] Furthermore, the patient and partner are typically human, but can also be other beings. Additionally, the genders of the patient and partner can be interchanged in the explanation of this invention.

[0050] Treatment information 223 is information based on the doctor's diagnosis and treatment. Treatment information 223 may include, for example, the date of diagnosis and treatment, medical findings, treatment (implementation), prescribed medications, and information related to the doctor's handling of eggs, sperm, culture medium, and embryos, all of which are associated with the patient's identification information (e.g., patient ID or partner ID). In this embodiment, treatment information 223 generally refers to information obtained from the doctor's terminal 102 related to the patient's examination or diagnosis, treatment, etc., and instructions related to the handling of eggs, sperm, culture medium, and embryos. 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. Treatment information 223 may include instructions from the doctor to the culturist regarding reproductive medicine (e.g., instructions on the handling of at least one of eggs, embryos, culture medium, or sperm). Furthermore, treatment information 223 may also include, for example, information recorded by nurses or others under the doctor's supervision. Treatment information 223 may be medical information other than basic information (e.g., the aforementioned patient information 221 and partner information 222, or medication information 228, prescription schedule information 229, etc.) and information recorded, managed, evaluated, or judged by the trainer. This treatment information 223 was not previously provided to the personal computer used by the trainer in the course of work, or to the embryo or semen evaluation system.

[0051] Owned Medication Information 224 refers to information related to medications prescribed for reproductive medicine that are already in the possession of the patient and their partner. Owned Medication Information 224 may include, for example, patient identification information (e.g., patient ID or partner ID), the name of the owned medication or active ingredient, dosage, quantity held, etc. Owned Medication Information 224 may also include information related to expiration dates, shelf life, and storage conditions.

[0052] Consent information 225 is information related to the consent form required for reproductive medicine. Consent information 225 may include, for example, patient identification information (e.g., patient ID or partner ID), consent form identification information, the corresponding treatment name, recipient, and date of receipt. Consent information 225 may also include, for example, information related to the name of the person distributing the consent form to the patient, the date of distribution, and the person explaining the information.

[0053] Embryo information 226 relates to the collection, manipulation (disposal), culture, preservation (including cryopreservation), and examination results of oocytes or embryos. Embryo information 226 may include, for example, patient identification information (e.g., patient ID), oocyte retrieval date, fertilization method, preservation location, and the status (including progress) and number of fertilized eggs / embryos / culture medium / frozen embryos. Embryo information 226 may also include information related to the characteristics of the oocytes or embryos obtained by medical device 105 (examination results, measurement results, observation images, evaluation results, etc.), such as time-lapse images of the embryos. Embryo information 226 may also include, for example, partner identification information (e.g., partner ID).

[0054] Sperm management information 227 refers to information related to the collection, examination, and preservation (including cryopreservation) of semen or sperm. Sperm management information 227 may include, for example, patient identification information (e.g., partner ID), semen examination information (e.g., the date of semen or sperm collection (and consequently, the partner's age at the time of collection), examination results, measurement results, observation images, evaluation results, etc.), storage location, the condition of frozen sperm, and quantity.

[0055] Drug information 228 pertains to medications prescribed to patients in relation to reproductive medicine. Drug information 228 may include, for example, drug identification information, pharmaceutical name or active ingredient name, dosage, quantity, etc. Drug information 228 may also include information related to the corresponding treatment or symptoms. Drug information 228 may pertain to medications processed by a medical institution utilizing the reproductive medicine support system 1, and may also include information about medications not processed at that medical institution.

[0056] Prescription schedule information 229 contains information on the combination and dosage of medications prescribed for each reproductive medicine treatment or symptom, as well as the timing of prescription. Prescription schedule information 229 may include information such as the treatment, prescribed medications, dosages, prescription start date, and prescription duration. Specifically, prescription schedule information 229 records, for example, a correspondence between the combination of prescribed medications, the dosage of each prescribed medication, the prescription start date, and the prescription duration for each treatment.

[0057] Cryopreservation management information 230 is management information for a cryopreservation management device used to manage frozen eggs, embryos, culture media, sperm, etc. Cryopreservation management information 230 may include, for example, identification information related to the cryopreservation location (e.g., cryopreservation ID), information specific to the cryopreservation location (e.g., the identification color of the cryopreservation tank, bucket, handle, or cryovial), etc.

[0058] A machine learning model P is a pre-trained model configured to output a solution for a high success rate for a given patient when given specific patient information as input. For example, a machine learning model M might calculate various conditions for maximizing pregnancy rates based on various patient information. Specifically, machine learning model P might calculate, for example, the egg retrieval day that maximizes the number of eggs retrieved, and the number of eggs retrieved under those conditions, based on various patient information.

[0059] [Doctor's Terminal] Figure 3 This is an example of the hardware structure of the doctor terminal 102. The doctor terminal 102 is an element used for inputting and outputting basic patient information and treatment information within the reproductive medicine support system 1. The doctor terminal 102 is typically used by a doctor. Use of the doctor terminal 102 can be restricted to users other than the doctor. The information input to the doctor terminal 102 is typically treatment information entered by the doctor. The doctor terminal 102 may be, for example, a personal computer or a portable terminal.

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

[0061] The main storage device 301 stores programs or 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 information 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. The various functional elements of the doctor terminal 102 are implemented by the processor 303 executing the programs or applications stored in the main storage device 301.

[0062] The auxiliary storage device 302 stores information required for the operation of the doctor terminal 102 in the reproductive medicine support system 1. As an example of the information in this invention, the auxiliary storage device 302 stores medical information such as patient information 321, partner information 322, treatment information 323, proprietary medication information 324, consent form information 325, embryo information 326, sperm management information 327, medication information 328, prescription schedule information 329, and cryopreservation management information 330. This information may be part or all of the various information stored in the auxiliary storage device 202 of the management server 101.

[0063] The doctor terminal management module 311 comprehensively controls the basic operations of the doctor terminal 102 in the reproductive medicine support system 1. The doctor terminal management module 311 collaborates with the management module 211 of the management server 101 to output (display) on an output device 205, such as a monitor, the top screen of the application used by the doctor terminal in the reproductive medicine support system 1, patient information screen, treatment plan screen, general infertility screen, egg retrieval cycle screen, hormone cycle screen, natural cycle screen, post-pregnancy medical record screen, and emergency appointment screen. The doctor terminal management module 311 provides doctors with various information about reproductive medicine through these screens and accepts input from doctors using the doctor terminal 102.

[0064] The doctor terminal acquisition module 312, display module 313, first prescription module 315, second prescription module 316, referral message output module 317, medical record information extraction module 318, consent form information management module 319, and semen evaluation module 320, respectively, cooperate with, for example, the acquisition module 212, doctor terminal output module 213, first prescription module 215, second prescription module 216, referral message 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 obtained 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.

[0065] The patient collaboration module 351 on the doctor's terminal side collaborates 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, or to display information from the patient terminal 104 on the doctor's terminal 102 via the management server 101.

[0066] [Trainer Terminal] Figure 4 This is an example of the hardware structure of the fertilization technician terminal 103. The fertilization technician terminal 103 is an element used for inputting and outputting assisted reproductive technology information of the fertilization technician within the reproductive medicine support system 1. The fertilization technician terminal 103 is typically used by the fertilization technician. For example, the fertilization technician performs semen analysis, sperm conditioning for artificial insemination, in vitro fertilization, micro-fertilization, embryo culture, embryo freezing, sperm freezing, and assisted embryo transfer using collected eggs or sperm from patients and / or partners. Along with this, the fertilization technician manages various information related to the eggs, sperm, and embryos. The information input to the fertilization technician terminal 103 is typically medical information entered by the fertilization technician. The fertilization technician terminal 103 is, for example, composed of a personal computer or a portable terminal. The fertilization technician terminal 103 is a device located outside the medical institution where the doctor's terminal 102 is located.

[0067] The trainer terminal 103 includes a main storage device 401 and an auxiliary storage device 402. Furthermore, the trainer terminal 103 includes a processor 403, an input device 404, an output device 405, and a communication control unit 406 as described above. The trainer terminal 103 may also include a camera or other imaging device (not shown).

[0068] The main storage device 401 stores programs or applications such as a trainer terminal management module 411, a trainer terminal acquisition module 412, a display module 414, a consent form information management module 419, and a semen evaluation module 420. The various functional elements of the trainer terminal 103 are implemented by the processor 403 executing the programs or applications stored in the main storage device 401.

[0069] The auxiliary storage device 402 stores information required for the operation of the embryologist terminal 103 in the reproductive medicine support system 1. As an example of the information in this invention, the auxiliary storage device 402 stores medical information such as patient information 421, partner information 422, treatment information 423, proprietary medication information 424, consent form information 425, embryo information 426, sperm management information 427, medication information 428, prescription schedule information 429, and cryopreservation management information 430. This information may be part or all of the various information stored in the auxiliary storage device 202 of the management server 101.

[0070] The therapist terminal management module 411 comprehensively controls the basic operations of the therapist terminal 103 in the reproductive medicine support system 1. The therapist terminal management module 411 collaborates with the management module 211 of the management server 101 connected via the Internet, outputting (displaying) on ​​an output device 405, such as a monitor, the top screen of the application for using the therapist terminal in the reproductive medicine support system 1, the patient information screen, the consent form overview screen, the oocyte retrieval ET screen, the cryopreservation management screen, the thawing ET screen, and the semen analysis / freezing screen. The therapist terminal management module 411 provides therapists with various information about reproductive medicine via these screens and accepts input from therapists using the therapist terminal 103.

[0071] The trainer terminal acquisition module 412 collaborates with the acquisition module 212 of the management server 101 to send information related to eggs, sperm, and embryos, consent forms, and semen evaluation, which are input by the trainer into the trainer terminal 103, to the management server 101. Furthermore, the trainer terminal acquisition module 412, in collaboration with the acquisition module 212, displays information output from the management server 101 on the trainer terminal 103.

[0072] The display module 414 works in conjunction with the trainer terminal output module 214 of the management server 101 to display the information sent from the management server 101 (including treatment information 423) on the trainer terminal 103.

[0073] The consent form information management module 419 collaborates with the consent form information management module 219 of the management server 101 to read information about the consent form from the management server 101 and display it on the trainer terminal 103.

[0074] The semen assessment module 420 collaborates with the semen assessment module 220 of the management server 101 to read information about semen assessment from the management server 101 and display it on the trainer terminal 103.

[0075] The patient collaboration module 451 on the trainer terminal side collaborates with the patient terminal output module 251 on the management server 101 to output the specified information to the patient terminal 104 via the management server 101, or to display the information from the patient terminal 104 on the trainer terminal 103 via the management server 101.

[0076] [Patient Terminal] Figure 5 This is an example of the hardware structure of the patient terminal 104. The patient terminal 104 is a terminal used by patients visiting a medical institution using the reproductive medicine support system 1. The patient terminal 104 may be, for example, a personal computer or a smartphone.

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

[0078] The main storage device 501 stores programs or applications such as the patient terminal management module 511 and the consent form submission module 519. The various functional elements of the patient terminal 104 are implemented by the processor 503 executing the programs or applications stored in the main storage device 501. Additionally, the consent form submission module 519 is an additional element and not a mandatory component.

[0079] The auxiliary storage device 502 stores information required for the operation of the patient terminal 104 in the reproductive medicine support system 1. The auxiliary storage device 502 may store, for example, patient information 521, partner information 522, and consent form information 525. This information may be part 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.

[0080] 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 collaborates with the management module 211 of the management server 101 to output (display), on an output device 505 such as a monitor, the top screen of the application for using the patient terminal in the reproductive medicine support system 1, the consent form submission screen, and the medication administration and management screen. The patient terminal management module 511 provides patients with various information about reproductive medicine via these screens and accepts input from patients using the patient terminal 104.

[0081] The consent form submission module 519 supplements the reproductive medicine support system 1 with support for the submission of patient consent forms. The consent form submission module 519 collaborates with the consent form information management module 219 of the management server 101 to output the consent form form to the patient terminal 104, or send the patient's completed and signed consent form (which may be a copy of the form (e.g., a PDF (portable document format) information file)) from the patient terminal 104 to the management server 101.

[0082] [Medical Devices] Medical devices 105 include various measuring instruments, analytical instruments, and measuring / analyzing systems used in reproductive medicine. Examples of medical devices 105 include biological microscopes, micro-fertilization systems, sperm characterization devices, culture vessels (including time-lapse culture vessels capable of capturing time-lapse images), and laser-assisted hatching (LAH) devices, which are primarily located in the culture room. Also included are medical devices located outside the culture room, such as X-ray imaging devices, ultrasound imaging diagnostic devices, hormone assay devices, and fallopian tube endoscopes / hysteroscopic surgical devices.

[0083] [Reproductive Medicine Support Methods] [Collaboration between Doctor's Terminal and Trainer's Terminal 1] Next, the method of supporting doctors and / or trainers using the reproductive medicine support system 1 will be described. For example, a doctor executes a reproductive medicine support program for a doctor's terminal stored in the auxiliary storage device 302 of the doctor's terminal 102. For example, a trainer executes a reproductive medicine support program for a trainer's terminal stored in the auxiliary storage device 402 of the trainer's terminal 103. In this way, the doctor's terminal management module 311 of the doctor's terminal 102 and the trainer's terminal management module 411 of the trainer's terminal 103 launch the reproductive medicine support application and connect to the management server 101. The management module 211 of the management server 101, in cooperation with the doctor's terminal management module 311 and the trainer's terminal management module 411, outputs (displays) the prescribed screen of the reproductive medicine support application on the output devices 305 and 405, such as the monitors of the doctor's terminal 102 and the trainer's terminal 103.

[0084] The acquisition module 212 of the management server 101 collaborates with the doctor terminal acquisition module 312 to acquire, for example, treatment information 223 input by the doctor to the doctor terminal 102 via the screen of the reproductive medicine support application. Furthermore, the acquisition module 212, consent information management module 219, and semen evaluation module 220 of the management server 101 collaborate with the embryologist terminal acquisition module 412, consent information management module 419, and semen evaluation module 420 to acquire, for example, information about eggs, sperm, culture medium, and embryos input by the embryologist to 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.

[0085] Figure 8 This is an example of a reproductive medicine support process. Furthermore, Figure 9 This is another example of the reproductive medicine support process. Figure 18 This is an example of the patient information screen 1800 on the doctor's terminal 102. Figure 19 This is an example of the patient information screen 1900 on the trainer terminal 103. Figure 18 and Figure 19 Examples of patient information screens 1800 and 1900 associated with a specified patient, designated by the doctor terminal 102 or the trainer terminal 103.

[0086] In the reproductive medicine support method of this embodiment, generally speaking, the management server 101 obtains 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 obtained treatment information 223 to the trainer terminal 103 via the network as required (S820).

[0087] In addition, the management server 101 obtains information related to the status of at least one of the eggs, embryos, culture medium or sperm from the culturist terminal 103 via the network (S910), and outputs the obtained status information to the doctor terminal 102 via the network as required (S920).

[0088] The following explains each step.

[0089] 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 the treatment information 223 input by the doctor to the doctor terminal 102. Here, the acquisition module 212 extracts and acquires the treatment information 223 that meets specific conditions from the treatment information 223 acquired from the doctor terminal 102 via the network.

[0090] For example, the acquisition module 212 sends the patient ID of a specific patient to the doctor terminal 102 via the network, and the doctor terminal 102 extracts the treatment information 223 corresponding to the patient ID. The doctor terminal 102 can then send the information to the acquisition module 212 of the management server 101.

[0091] In addition, the acquisition module 212 can be configured to acquire treatment information 223 of all or more patients from the doctor terminal 102 via a network, and extract corresponding information from the treatment information 223, for example, based on the patient ID of a specific patient.

[0092] In addition to extracting data using the patient ID, the acquisition module 212 can also accept input from operators (e.g., doctors or trainers) from the doctor terminal 102 or the trainer terminal 103, and extract, acquire, or send data that meets the conditions corresponding to the input.

[0093] For example, as a condition, in addition to the patient ID, data such as a specific age (e.g., over 40 years old) or the name of a specific patient are considered; information used to identify the patient; information used to determine treatment methods or medications; information used to determine the assessment results of the embryo or sperm; and information indicating that the setting is as follows: Figures 18-45 The conditions of the information groups displayed in each of the shown screens.

[0094] The password module of the doctor terminal 102 can encrypt and send the treatment information 223. In addition, the acquisition module 212 sends the authentication information, such as the one-time password used at this time, to the doctor terminal 102. The password module of the doctor terminal 102 can use the authentication information to encrypt the treatment information 223.

[0095] Furthermore, in the treatment information acquisition step (S910), as described above, the acquisition module 212 collaborates with the culture therapist terminal acquisition module 412 to acquire information (hereinafter sometimes simply referred to as "status information") related to the status of at least one of the oocyte, embryo, culture medium, or sperm from the culture therapist terminal 103. Here, the acquisition module 212 extracts and acquires status information that meets specific conditions from the status information related to the oocyte, embryo, culture medium, or sperm acquired from the culture therapist terminal 103 via the network.

[0096] For example, the acquisition module 212 sends the patient ID of a specific patient to the trainer terminal 103 via the network. The trainer terminal 103 extracts the status information corresponding to the patient ID, and the trainer terminal 103 can send it to the acquisition module 212 of the management server 101.

[0097] In addition, the acquisition module 212 can be configured to acquire status information of all or more patients from the trainer terminal 103 via a network, and extract corresponding information from the status information, for example, based on the patient ID of a specific patient.

[0098] In addition to retrieving data using the patient ID, the acquisition module 212 can also accept input from an operator (e.g., a doctor or trainer) from the doctor terminal 102 or the trainer terminal 103, and retrieve, acquire, or send data that meets the conditions corresponding to that input. For example, as such conditions, besides the patient ID, data such as a specific age (e.g., over 40 years old) or the name of a specific patient may be considered, along with information used to identify the patient, information used to determine treatment methods or medications, information used to determine the evaluation results of the embryo or sperm, and information indicating settings such as... Figures 18-45 The conditions of the information groups displayed on each screen are shown.

[0099] The password module of the trainer terminal 103 can encrypt and send the status information. In addition, the acquisition module 212 sends the authentication information, such as the one-time password used at this time, to the trainer terminal 103. The password module of the trainer terminal 103 can use the authentication information to encrypt the status information.

[0100] Furthermore, in the treatment information output step (S820), the trainer terminal output module 214 outputs the acquired treatment information 223 to the trainer terminal 103 via the network as required.

[0101] For example, the trainer terminal output module 214 can receive the patient ID of a specific patient from the trainer terminal 103 via the network. The trainer terminal output module 214 extracts the treatment information 223 corresponding to the patient ID, sends the extracted treatment information 223 to the trainer terminal 103, and outputs it on the trainer terminal 103.

[0102] In addition to extracting data using the patient ID, the trainer terminal output module 214 can also accept input from operators (such as doctors or trainers) from the doctor terminal 102 or the trainer terminal 103, and extract, acquire or send data that meets the conditions corresponding to the input.

[0103] For example, as a condition, in addition to patient ID, data such as a specific age (e.g., over 40 years old) or the name of a specific patient are also considered, as well as information used to identify the patient, to determine treatment methods or medications, and to determine the assessment results of the embryo or sperm. Figure 19 , 25 Information that should be displayed in numbers such as 26, 28-30, 33-36, and 45.

[0104] The password module of the management server 101 or the output module 214 of the trainer terminal can encrypt and send the treatment information 223. In addition, the password module of the trainer terminal 103 sends the authentication information, such as the one-time password used at this time, to the management server 101. The password module of the management server 101 or the output module 214 of the trainer terminal can use the authentication information to encrypt the treatment information 223.

[0105] Furthermore, 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 as required.

[0106] The doctor terminal output module 213 can, for example, receive a patient ID of a specific patient from the doctor terminal 102 via the network, extract status information corresponding to the patient ID, send the extracted status information to the doctor terminal 102, and output it on the doctor terminal 102.

[0107] In addition to extracting data using the patient ID, the doctor terminal output module 213 can also accept input from the operator (e.g., a doctor or a trainer) of the doctor terminal 102 or the trainer terminal 103, and extract, acquire or send data that meets the conditions corresponding to the input.

[0108] For example, as a condition, in addition to patient ID, data such as a specific age (e.g., over 40 years old) or the name of a specific patient are also considered, as well as information used to identify the patient, to determine treatment methods or medications, and to determine the assessment results of the embryo or sperm. Figure 18 , 20 Information that should be displayed in numbers such as ~24, 27, 31, 32, 37, 45, etc.

[0109] The password module of management server 101 or the output module 213 of doctor terminal can encrypt and send the status information. In addition, the password module of doctor terminal 102 sends the authentication information, such as the one-time password used at this time, to management server 101. The password module of management server 101 or the output module 213 of doctor terminal can use the authentication information to encrypt the status information.

[0110] like Figure 18 As shown, the management module 211 displays a patient information tab 1810 on the monitor of the doctor's terminal 102. When the patient information tab 1810 is selected, a patient information screen 1800 is displayed. For example, in addition to displaying the patient's basic information 1820, the management module 211 also displays measurement information, the patient's pregnancy history, medical history, allergy information, currently taken supplements, treatment history 1830, remaining medication management section 1840 (an example of owned medication information), partner information 1880, treatment history calendar 1850, etc. The management module 211 displays the patient information screen 1800, for example, based on patient information 221, partner information 222, treatment information 223, owned medication information 224, sperm management information 227, etc.

[0111] Furthermore, when the acquisition module 212 obtains information related to the status of at least one of the egg, embryo, culture medium, or sperm from the culture technician terminal 103, the doctor terminal output module 213 outputs the acquired status information to the doctor terminal 102. Figure 18 In this system, the doctor's terminal output module 213 displays status information, such as information 1860 related to sperm before the most recent adjustment or information 1870 related to cryopreserved sperm. Through this screen, the doctor can, for example, obtain general information about the sperm's status, in addition to the patient's basic information, treatment status, and treatment summary. Thus, the doctor can quickly obtain information about the sperm's status (an example of status information) without having to contact the sperm culture specialist separately or activate another information system.

[0112] like Figure 19As shown, the management module 211 displays a patient information tab 1910 on the monitor of the trainer terminal 103. When the patient information tab 1910 is selected, a patient information screen 1900 is displayed. For example, in addition to displaying the patient's basic information 1920, the management module 211 also displays basic information such as measurement information, medical history, allergy information, and partner information on the patient information screen 1900. The management module 211 may also display the patient information screen 1900 based on patient information 221, partner information 222, etc.

[0113] Furthermore, the trainer terminal output module 214 displays treatment information 423, such as pregnancy history or treatment history 1930, on the patient information screen 1900 based on, for example, treatment information 223. When the acquisition module 212 receives the patient's past treatment information 423, the trainer terminal output module 214 displays that past treatment information 423 on the trainer terminal 103. Conversely, when the acquisition module 212 does not receive the patient's past treatment information 423, it does not display it. Through this screen, the trainer can, in addition to the patient's basic information, also gain a general understanding of treatment information such as medical history.

[0114] Previously, when embryologists were involved in reproductive medicine, it was the embryologist, not the doctor, who made judgments and decisions regarding in-vitro fertilization (including sperm donation) or embryo culture. Embryologists received samples such as eggs and sperm while also reviewing physical medical records, typically performing and recording procedures such as artificial insemination or culture in a cleanroom or other isolated environment. Even clinics equipped with sperm donation rooms usually isolated them by floor from other internal facilities (such as general examination rooms) to create a cleanroom environment in accordance with laws, regulations, and guidelines. Based on this structure, embryologists, for example, can consider the patient's infertility treatment history or progress based on information displayed on the embryologist terminal 103 within the cleanroom, and thus take more appropriate actions or make more appropriate judgments regarding the eggs, sperm, and embryos.

[0115] Furthermore, in recent years, trainers have increasingly explained assisted reproductive technologies to patients. For example, trainers can avoid the hassle of individually contacting doctors or personally questioning patients; they can quickly access treatment information 423, such as the infertility treatment history or progress of patients who are allowed to view the information on the trainer's terminal 103. This allows for better communication between trainers and patients.

[0116] In addition, the therapist terminal 103 requests various information from the management server 101 via the network at predetermined time intervals and according to the operations performed by the therapists on the therapist terminal 103. For example, by being configured to set a shorter time interval for requesting information from the management server 101, or to request the information when the information in the auxiliary storage device 202 is updated, the therapist terminal 103 can display new treatment information 423 almost in real time.

[0117] in addition, Figure 20 This is an example of an overall image 2000 of the treatment history calendar 1850 displayed on the doctor's terminal 102. The management module 211 displays information representing the treatment history and treatment plan in the treatment history calendar 1850 based on patient information 221 and treatment information 223, for example. The management module 211 displays various treatment cycles in different colors, such as cycles related to infertility treatments excluding in-vitro fertilization (general infertility), egg retrieval cycles (egg retrieval cycle 2010), embryo transfer cycles based on natural cycles (natural cycles), and embryo transfer cycles accompanied by hormone filling (hormone cycle 2020), etc. Furthermore, the management module 211 displays information related to the start and end dates of each treatment cycle, such as text information like "Start" and "End." The management module 211 further displays information related to surgery dates such as egg retrieval date 2015 and embryo transfer date 2025 in different colors. By viewing this treatment history calendar 1850, the doctor can intuitively and clearly understand the treatment plan and its progress for the patient.

[0118] The following describes the functions and actions of the other modules of the management server 101.

[0119] [Prescription auto-entry 1] Figure 10 This is an example of an automated prescription entry process. Figure 21 This is an example of a screen showing the egg retrieval cycle on a doctor's terminal. Figure 22 (A) to (B2) are examples of the display of the prescription drug input field.

[0120] The management module 211 displays the oocyte retrieval cycle tab 2110 on the monitor of the doctor's terminal 102. When the oocyte retrieval cycle tab 2110 is selected, the oocyte retrieval cycle screen 2100 is displayed. The management module 211 displays, for example, a treatment policy section, an important information section, an ovarian stimulation method section 2140, a remaining medication management section 2150, a necessary procedures section 2160, a treatment record input form for the oocyte retrieval cycle 2120, and a prescription drug input section 2130 on the oocyte retrieval cycle screen 2100. The management module 211 displays the oocyte retrieval cycle screen 2100 based on, for example, patient information 221, treatment information 223, proprietary medication information 224, consent form information 225, medication information 228, and prescription schedule information 229.

[0121] In reproductive medicine, it is often necessary to prescribe multiple medications for several days at once, which can be troublesome and burdensome for doctors, such as having to input prescription information for multiple medications into the doctor's terminal 102. To address this, the first prescription module 215 performs the processing described below to reduce the trouble and burden on relevant doctors.

[0122] First, the management module 211 outputs the medical record input table 2120 to the egg retrieval cycle screen 2100. The medical record input table 2120 displays dates, days of the week, menstrual cycles, etc., in a calendar-like format. The management module 211 displays the daily medical record input fields in the medical record input table 2120 in ascending order, for example, so that the current day's medical record input field is at the top. Furthermore, the management module 211 displays the automatic prescription input button as a "Do" button 2135 on each row of the prescription drug input field 2130.

[0123] When a doctor examines a patient on the same day (here, "2022 / 12 / 23"), for example, in the medical record input table 2120 of the egg retrieval cycle screen 2100, the doctor selects cell C1 of the "Date of Visit" column. Then, the management module 211 displays the information "〇" indicating that the patient has visited the doctor in a drop-down menu on the doctor's terminal 102. Moreover, when the doctor selects the information "〇" indicating that the patient has visited the doctor, the acquisition module 212 accepts the input information indicating that the day is the date of visit, and the management module 211 displays the information "〇" indicating the date of visit in cell C1.

[0124] Next, for example, Figure 22 As shown in (A), the doctor selects the "Oral / Nasal Drops" option (cell C2) corresponding to the day of the appointment in the prescription drug input field 2130. Then, as... Figure 22 As shown in (A), the management module 211 displays a dropdown list of oral and nasal medications available for prescription during the egg retrieval cycle based on the medication information 228. Furthermore, when the doctor selects any medication from the list (e.g., letrozole tablets 2.5mg (“Letrozole (Letro) 2.5mg [1 tablet]”)), the acquisition module 212 receives information about the date and the selected medication as information about the prescription date and the prescription drug. The management module 211 displays information indicating the selected prescription drug (e.g., “Letrozole 2.5”) in cell C2. The information received by the acquisition module 212 is stored, for example, as treatment information 223 in the auxiliary storage device 202.

[0125] <Cases where the next appointment date was not entered> Here, suppose the doctor did not enter information about the next appointment date in the "Date of Visit" column, but instead selected the "Same as above" button 2135 in the same column as cell C2. In this case, the first prescription module 215, for example, refers to the treatment information 223 in the auxiliary storage device 202, retrieves the prescription drug and prescription date information displayed in the same column as the selected "Same as above" button 2135 (S1010), and determines whether to retrieve information related to the next appointment date (S1020). Here, the first prescription module 215 confirms that no information related to the next appointment date has been retrieved ("No" in S1020), and outputs information indicating that the same prescription drug will be prescribed daily for a specified number of days from the prescription date (S1040). Specifically, for example, as shown... Figure 22 As shown in (B1), the first prescription module 215 displays "Letrozole 2.5" in the same column as the selected "Same as above" button 2135, and in the column for the predetermined number of days (here, 5 days, 1 tablet per day), that is, in the column for each day from "2022 / 12 / 23" to "12 / 27" which are the prescription dates, indicating the same prescription drug as that entered into cell C2. In addition, the first prescription module 215 stores, for example, the prescription drug "Letrozole 2.5mg [1 tablet]" for each day from the prescription dates 2022 / 12 / 23 to 12 / 27 as treatment information 223 in the auxiliary storage device 202.

[0126] Based on the above structure, doctors can, for example, simply select "same as above" button 2135 once to enter "letrozole 2.5" as the prescription drug in the field for each day from "2022 / 12 / 24" to "2022 / 12 / 27", instead of having to enter it every time.

[0127] Furthermore, the cell C2 where the doctor enters information about the prescription date and medication is not limited to the first row (the current day), but can also be from the second row onwards (i.e., the next day onwards). Additionally, the information about prescription medication entered into cell C2 is not limited to the current day; for example, it can also be information about medications prescribed on the previous appointment date. The number of days for automatically entering prescription medication is not limited to 5 days; for example, it can be arbitrarily determined based on the standard treatment cycle. Moreover, the number of days for automatically entering prescription medication can also be set differently for each prescription.

[0128] <Enter details of the next appointment date> Additionally, it is also considered that the patient may be unable to attend appointments according to the standard treatment schedule. For example, in such cases, the doctor may prescribe medication for each day until the next scheduled appointment date.

[0129] For example, Figure 22As shown in (B2), the doctor selects cell C3 in the "Date of Visit" column, corresponding to the next available appointment date for the patient (here, 12 / 28). In this way, the management module 211 displays the information "0" indicating the patient's next appointment date in a dropdown menu on the doctor's terminal 102. Furthermore, when the doctor selects "0" indicating the patient's next appointment date, the acquisition module 212 accepts the input indicating that the date is the next appointment date, and the management module 211 displays the information "0" indicating the next appointment date in cell C3. For example, the management module 211 stores the date corresponding to cell C3 (here, 12 / 28) as the next appointment date as treatment information 223 in the auxiliary storage device 202.

[0130] Next, the doctor selects the "Same as above" button 2135 in the same column as cell C3. In this way, the first prescription module 215, for example, refers to the treatment information 223 in the auxiliary storage device 202, retrieves the prescription drug and prescription date information displayed in the same column as the selected "Same as above" button 2135 (S1010), and determines whether to retrieve information related to the next appointment date (S1020). Here, the first prescription module 215 confirms that it has retrieved information related to the next appointment date ("Yes" in S1020) and outputs information indicating that the same prescription drug will be prescribed daily from the prescription date to the specified date based on the next appointment date (S1030). Specifically, for example, as shown... Figure 22 As shown in (B2), the first prescription module 215 displays "Letrozole 2.5" as the same prescription drug as entered into cell C2 in the column corresponding to the selected "Same as above button" 2135, representing each day from the prescription date "2022 / 12 / 23" to the next appointment date "12 / 28". Furthermore, the first prescription module 215 stores, for example, the prescription drug "Letrozole 2.5mg [1 tablet]" for each day from the prescription date 2022 / 12 / 23 to 12 / 28 as treatment information 223 in the auxiliary storage device 202.

[0131] Based on the above structure, doctors can, for example, enter "letrozole 2.5" as the prescription drug in the daily field from "12 / 24" to the patient's next appointment date "12 / 28" by simply selecting "next appointment date" and "same as above" button 2135, instead of entering it every time.

[0132] Furthermore, the date for automatically entering prescription medication can be determined to include or exclude the next appointment date. For example, the first prescription module 215 can display prescription medication information for each day up to the day before the next appointment date. In this case, the first prescription module 215 may, for example, store the prescription medication "letrozole 2.5mg [1 tablet]" as treatment information 223 in the auxiliary storage device 202 for each day from December 23 to December 27, 2022, up to the day before the next appointment date.

[0133] [Prescription Auto-Entry 2] As mentioned above Figure 18 As shown, the management module 211 displays the remaining medication management column 1840 on the patient information screen 1800 of the doctor's terminal, for example.

[0134] In reproductive medicine, a large number of medications are prescribed. However, sometimes these prescriptions remain in the patient's possession, such as due to patients forgetting to take their medications, or discrepancies in appointment dates or gestational age assessments. Furthermore, patients may transfer to other medical facilities due to relocation or compatibility issues, leaving behind prescriptions from their previous providers. If such patients have an excessive amount of their own medications (unused medications), it can lead to problems such as insufficient prescription medications. To address this, doctors can obtain information about the types and quantities of medications held by patients through consultations. For example, if the patient's own medications are sufficient, this reproductive medicine support system 1 can be used to manage the patient's own medications.

[0135] The doctor obtains information such as the type (dosage), quantity, etc., of the patient's own medications and selects the "Medications with Remaining Medications Reported" field in the Remaining Medications Management section 1840. For example, the doctor receives a report from the patient stating that they possess two prescription pills, "Letrozole 2.5mg [1 tablet]". In this case, the management module 211 displays a list of medication names in a dropdown menu on the doctor's terminal 102, based on medication information 228. Furthermore, when the doctor selects any medication from the list (e.g., "Letrozole 2.5mg [1 tablet]") and enters the quantity "2" in the corresponding "Remaining Medications Quantity" field, the acquisition module 212 receives information related to the selected medication and its quantity, for example, stored in the medication information 224 in the auxiliary storage device 202. The management module 211 displays information indicating the medications and their quantities in the "Medications with Remaining Medications Reported" field and the corresponding "Remaining Medications Quantity" field, respectively. Thus, the management server 101 can manage the patient's own medications.

[0136] The following explains the prescription of medicines when managing one's own medicines. Figure 23 This is another example of how the prescription drug input field is displayed. Figure 11This is another example of an automated prescription entry process. Figure 12 This is an example of a residual medication management process.

[0137] like Figure 23 As shown, for example, a doctor prescribes the medication "Letrozole 2.5" for a 5-day period from December 23rd to December 27th, 2022. The patient can take their own medication "Letrozole 2.5" for the first two days (December 23rd and 24th), while the doctor only prescribes "Letrozole 2.5" for the remaining three days (December 25th to 27th). In this case, the patient's own medication "Letrozole 2.5" can be considered a virtual prescription. Therefore, the first prescription module 215 displays the text "Letrozole 2.5" in cell C4 for the first two days when the medication was not actually prescribed, and in cell C5 for the remaining three days when the medication was actually prescribed. Furthermore, the first prescription module 215 outputs a different display to cell C4 for the first two days when the medication was not prescribed compared to cell C5, to clearly indicate that the prescription is virtual.

[0138] For example, the first prescription module 215 may apply different decorations to the text or cell C4 representing a drug than to other cells, as a display indicating a virtual prescription of a self-prescribed drug. Examples of decorations performed by the first prescription module 215 include the following.

[0139] Text decorations for drugs (e.g., displaying characters in bold, light, italics, different colors, different fonts, or different sizes). Decorate the target cells in the "Drugs with Remaining Drug Applications" column (e.g., use a different color for the cell background, or make the cell borders decorative lines (thick lines, thin lines, single-dot chain lines, dashed lines, double lines, etc.)). Display a marker (such as an asterisk or star symbol) in the target cell of the "Drugs with Remaining Drug Declarations" column. Under this structure, doctors only need to check the prescription drug input field 2300 to know the patient's available medications for the five days from December 23rd to 27th, 2022. The medications for the first two days are the patient's own medications that were not actually prescribed, while the medications for the remaining three days are the actually prescribed medications. Furthermore, doctors can consider the patient's own medications and prescribe appropriate dosages. In other words, unnecessary prescriptions can be reduced.

[0140] Next, an example of the automated prescription process 1100 and the remaining medication management process 1200 used to implement this display will be described.

[0141] like Figure 11As shown, the first prescription module 215 first obtains information related to the prescription drug and prescription date (S1110). This step is similar to... Figure 10 The steps of S1010 in the automatic prescription input process 1000 are the same. Next, the first prescription module 215 acquires information related to the patient's own medication and its quantity (S1120). For example, the first prescription module 215 acquires information indicating that the patient holds two "letrozole tablets 2.5mg" as their own medication. Furthermore, if the prescribed medication is different from the patient's own 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 after S1020 in the automatic prescription input process 1000. On the other hand, if the prescribed medication is the same as the patient's own medication ("Yes" in S1130), the first prescription module 215 outputs information indicating that the patient's own medication is being virtually prescribed as a prescription (S1140).

[0142] Step S1140 will be explained. In step S1140, the first prescription module 215 may output information indicating that a virtual prescription for a self-owned drug is being issued as a prescription drug, for example, when the number of virtual prescriptions for self-owned drugs is less than the required number of prescriptions for a prescription drug or the number of self-owned drugs held. Furthermore, when a self-owned drug is being virtually issued as a prescription drug, the first prescription module 215 may output the number obtained by subtracting the number of virtual self-owned drugs issued as the number of self-owned drugs held, and output the number obtained by subtracting the number of virtual prescriptions for self-owned drugs from the prescribed number of prescriptions as the actual number of drugs issued.

[0143] More specifically, such as Figure 12As shown, the first prescription module 215 manages the number A of the patient's own medications, the number of virtual prescriptions B when the own medication is virtually prescribed, the number of prescription days that the medication should have been prescribed (i.e., the required number of prescriptions X), and the number of prescription repetitions N (N is a natural number; initially N=1) indicating the day of the process (S1205). Next, the first prescription module 215 outputs information indicating the virtual prescription of the own medication to the cell for day N (S1210). Furthermore, the first prescription module 215 updates the number of virtual prescriptions B of the own medications based on "B=N" (S1215). Here, the first prescription module 215 determines whether the number of prescription repetitions N reaches the required number of prescriptions X for the medication based on the formula: N≧X? (S1220). Moreover, if the number of prescription repetitions N does not reach the required number of prescriptions X ("No" in S1220), the first prescription module 215 determines whether the number of virtual prescriptions B of the own medications reaches the number A of the own medications held based on the formula: B≧A? (S1225). Furthermore, if the number of virtual prescriptions B for proprietary drugs does not reach the number of proprietary drugs held A ("No" in S1225), the first prescription module 215 increases the number of prescription repetitions N by 1 (S1230) and returns to step S1210.

[0144] On the other hand, when the number of prescription repetitions N reaches the required number of prescriptions X ("Yes" in S1220), the drug dispensing operation is considered complete, and the first prescription module 215 proceeds to the subsequent step S1250. Furthermore, when the number of virtual prescriptions B for proprietary drugs reaches the number of proprietary drugs held A ("Yes" in S1225), prescription drugs must continue to be dispensed, and the first prescription module 215 proceeds to the next step.

[0145] The first prescription module 215 increments the prescription repetition count N by 1 (S1235) and outputs information indicating that the prescription drug is to be issued on day N (S1240). Furthermore, the first prescription module 215 determines whether the prescription repetition count N has reached the required prescription number X based on the formula: N ≥ X? (S1245). If the prescription repetition count 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 drug issuance. If the prescription repetition count N has reached the required prescription number X ("Yes" in S1245), the drug issuance operation is considered complete, and the first prescription module 215 proceeds to the next step.

[0146] The first prescription module 215 outputs the actual number of medications prescribed based on the formula: XB (S1250). Furthermore, the first prescription module 215 updates the patient's self-owned medication holdings A based on "A=AB" (S1255) and outputs the updated self-owned medication holdings A (S1260). Here, the first prescription module 215 updates the self-owned medication holdings A in the auxiliary storage device 202 and updates the "remaining medication quantity" value in the remaining medication management columns 1840 and 2150 to the holdings A. Additionally, for self-owned medications with a holdings A of zero, the first prescription module 215 removes the display of the "Medications with Remaining Medication Declarations" column in the remaining medication management columns 1840 and 2150. With this structure, the medical record input table 2120 and the remaining medication management column 2150 can be displayed appropriately without the doctor having to calculate the remaining medication quantity themselves or change the display when virtually prescribing self-owned medications.

[0147] [Prescription Auto-Entry 3] Figure 13 This is another example of an automated prescription entry process. Figure 24 (A) to (C) are display examples of a portion of the egg retrieval cycle screen 2100.

[0148] In reproductive medicine, various treatments need to be prepared based on the patient's condition. The combination of medications prescribed or the timing of administration differ for each treatment, which can cause trouble and burden for doctors, such as having to input prescription information for multiple medications into the doctor's terminal 102. To address this, the second prescription module 216 performs the processing described below to reduce the trouble and burden on relevant doctors.

[0149] As described above, the prescription schedule information 229 stores, for example, information such as the combination of prescription drugs, the dosage of each prescription drug, the date of prescription start, and the number of days of prescription for each treatment. For example, the ovulation induction methods used to collect eggs for in vitro fertilization are divided into three types: regulated ovarian stimulation (RCS) to collect a large number of eggs with relatively strong stimulation, semi-mild stimulation with relatively weak stimulation, and mild stimulation with low stimulation. Moreover, RCS is further divided into antagonist protocols, long protocols, short protocols, and PPOS (Progestin Primed Ovarian Stimulation, ovulation induction under high progesterone conditions) based on the type of drug and the timing of administration. In the antagonist protocol, a basic prescription schedule is set, such as taking birth control pills from the last menstrual period, starting FSH injections or human chorionic gonadotropin (HMG) injections from the third day of menstruation for about 9 to 14 days, injecting the antagonist when the follicle grows to 14 to 16 mm, and self-injecting human chorionic gonadotropin (HCG) preparations as a trigger when the follicle size and hormone levels meet the specified conditions, and retrieving eggs 34 to 36 hours after triggering.

[0150] like Figure 13 As shown, the second prescription module 216 obtains information related to the patient's treatment name and treatment date (S1310), establishes a correspondence with the treatment name, and outputs information indicating the prescription of one or more drugs according to a predetermined drug prescription schedule (S1320).

[0151] The steps for obtaining information related to the name of the disposal and the date of disposal (S1310) are explained.

[0152] As mentioned above Figure 21 As shown, in the egg retrieval cycle screen 2100, the management module 211 displays the ovarian stimulation method section 2140 and the "Reflect Specified Settings" button 2145 for indicating automatic prescription input. If the doctor selects the ovarian stimulation method section 2140, for example... Figure 24 As shown in (A), the management module 211 displays a list of ovarian stimulation methods in a dropdown menu on the doctor's terminal 102 based on the prescription schedule information 229. Furthermore, when the doctor selects any ovarian stimulation method (e.g., "antagonist protocol") from the list, the acquisition module 212 accepts the information that the ovarian stimulation method (treatment) for ovulation induction for that patient is the "antagonist protocol," and stores this information, for example, in the auxiliary storage device 202. The management module 211 displays information indicating the selected ovarian stimulation method in the ovarian stimulation method field 2140.

[0153] Next, for example, Figure 24 As shown in (B), the management module 211 displays a pop-up screen on the egg retrieval cycle screen 2100 for selecting the ovulation suppression start date (an example of a treatment date). If the doctor selects an ovulation suppression start date (e.g., 2022 / 12 / 23) in the pop-up screen, the acquisition module 212 accepts the selected date as the patient's treatment date, for example, and stores it in the auxiliary storage device 202. Furthermore, if the doctor selects the "Reflect Designated Settings" button 2145, the second prescription module 216, based on the prescription schedule information 229, sets the ovulation suppression start date to 2022 / 12 / 23, calculates the combination of prescription drugs (including dosage) to be prescribed in the antagonist regimen and their prescription dates, and displays them in the corresponding prescription drug input field 2130. Figure 24 In (C), for example, the second prescription module 216 displays prescription information for, for example, "Letrozole 2.5mg" tablets, "Cetrotide 0.25mg" for injection, and "GONAL-f" injection pen 300 for injection for 5 days starting from the ovulation suppression start date of 2022 / 12 / 23. The second prescription module 216 stores the prescription information in, for example, an auxiliary storage device 202. Thus, doctors can easily input prescription information, for example, by preventing erroneous input.

[0154] [Collaboration between Doctor's Terminal and Trainer's Terminal 2] <Scenario of frozen embryo transfer> Figure 25 This is an example of the ET (Embryo Transfer) screen on the embryologist's terminal, number 2500. Figure 26 It is a pop-up display of an embryo image.

[0155] The management module 211 displays the oocyte retrieval ET tab 2510 on the monitor of the embryologist terminal 103. When the oocyte retrieval ET tab 2510 is selected, the oocyte retrieval ET screen 2500 is displayed. The management module 211 displays, for example, the oocyte retrieval order field, the sperm used field, the oocyte retrieval result creation field, the oocyte retrieval result field, and the result details field 2520 on the oocyte retrieval ET screen 2500. The management module 211 displays the oocyte retrieval ET screen 2500 based on, for example, patient information 221, treatment information 223, embryo information 226, and sperm management information 227. Additionally, for example, information allowed to be provided to the embryologist terminal 103 from the treatment information 323 obtained from the doctor's terminal 102 is output to the oocyte retrieval order field. By providing relevant information to the embryologist, sperm donation or subsequent embryo evaluation can be performed more appropriately.

[0156] When follicles have fully developed through ovarian stimulation, the doctor typically collects follicular fluid, and the embryologist collects eggs from the follicular fluid under a microscope (egg retrieval). Furthermore, on the day of egg retrieval, the embryologist performs artificial insemination (in vitro fertilization or intracytoplasmic sperm injection) and cultures the fertilized eggs (embryos) in a culture vessel. The embryologist inputs the status of the eggs or embryos from retrieval to culture into the egg retrieval ET screen 2500. The acquisition module 212 acquires the input information about the status of the eggs or embryos (status information) via the egg retrieval ET screen 2500, for example, recording it in the embryo information 226 of the auxiliary storage device 202.

[0157] The management module 211 displays an image button 2525 in the result details bar 2520. After the management module 211 accepts a selection from the image button 2525, for example... Figure 26 As shown, images of the embryo from day 0 (DAY0) to day 7 (DAY7) post-fertilization are displayed in a pop-up format based on embryo information 226. Additionally, Figure 26 The embryo images are display samples where the same images are shown every day. The management module 211 can be configured, for example, to display time-lapse images of the embryos from day 0 (DAY0) to day 7 (DAY7) after fertilization in the form of animation.

[0158] In addition, in assisted reproductive technology, all cultured and transferable embryos or high-grade, healthy blastocysts are typically cryopreserved. Embryo specialists evaluate embryos, for example, by reviewing embryo images, and then cryopreserve early-stage embryos or healthy blastocysts.

[0159] Figure 27 This is an example of the hormone cycle screen 2700 on the doctor's terminal. Figure 28 This is an example of the unfreezing ET screen 2800 on the trainer terminal.

[0160] like Figure 27 As shown, the management module 211 displays the hormone cycle tab 2710 on the monitor of the doctor's terminal 102. When the hormone cycle tab 2710 is selected, the hormone cycle screen 2700 is displayed. The management module 211 displays, for example, patient information, a planned embryo transfer selection field 2720, an HR group / luteal group selection field, the latest ERA / ER peak test results field, the latest Th1 / Th2 test results field, remaining medication management, necessary procedures field 2740, and a hormone cycle treatment record input form 2730. The management module 211 displays the hormone cycle screen 2700 based on, for example, patient information 221, treatment information 223, proprietary medication information 224, consent form information 225, embryo information 226, medication information 228, prescription schedule information 229, and cryopreservation management information 230.

[0161] Based on treatment information 423 obtained from the embryologist terminal 103, such as embryo information 226 and cryopreservation management information 230, the doctor terminal output module 213 displays information about the patient's frozen embryos in the planned embryo transfer selection field 2720. In the planned embryo transfer selection field 2720, the doctor terminal output module 213 displays, for example, information about the status of six frozen embryos (No. 1 to No. 6) such as post-ovulation days, grade, priority score, pronuclear stage, and priority. Furthermore, the priority score is a score display (indicator) used to determine the priority of embryo transfer. The priority score is not limited to this; for example, it can be an indicator for assessing implantation rate based on embryo morphology analysis, or an indicator for assessing implantation rate based on any one or more of the information related to the egg, sperm, patient, or partner, or a combination thereof.

[0162] Furthermore, the management module 211 displays an image display button 2721, an AHA selection box 2722, and an embryo transfer selection box 2723 in the planned embryo transfer selection bar 2720. Moreover, when the image display button 2721 is selected, the doctor's terminal output module 213 displays, for example, a pop-up display such as... Figure 26 Images of the embryos shown are from day 0 (DAY0) to day 7 (DAY7) after fertilization.

[0163] AHA selection box 2722 is used to select an embryo for artificial hatching assistance (AHA) from the embryos displayed in the embryo selection box 2723, and embryo selection box 2723 is used to select the embryo to be transferred. The doctor selects the embryo selection box 2723 corresponding to the frozen embryo selected as the embryo for transfer. Furthermore, when performing AHA on the frozen embryo, the doctor selects the corresponding AHA selection box 2722. Thus, the acquisition module 212 receives information indicating that the frozen embryo corresponding to the selected embryo selection box 2723 is the embryo for transfer and that AHA is performed on the frozen embryo when the AHA selection box 2722 is selected, for example, stored in the embryo information 226 of the auxiliary storage device 202.

[0164] like Figure 28 As shown, the management module 211 displays the thawing ET tab 2810 on the monitor of the cryopreservation terminal 103. When the thawing ET tab 2810 is selected, the thawing ET screen 2800 is displayed. For example, the management module 211 displays the planned embryo transfer display bar 2820, the thawing settings bar 2830, the thawing start button 2840, and the post-thawing management bar 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, and cryopreservation management information 230.

[0165] The embryologist terminal output module 214 checks, for example, whether the embryo information 226 in the auxiliary storage device 202 contains information related to the frozen embryos of the patient selected for transfer, obtained from the doctor's terminal 102. Furthermore, if the embryologist terminal output module 214 does not display information about the embryos in the planned transfer embryo display area 2820 when no information related to the frozen embryos selected for transfer is found, and if information related to the frozen embryos selected for transfer is found, such as... Figure 28 As shown, the embryo display panel 2820 displays information about the frozen embryos selected for transfer. Thus, by checking the thawing ET screen 2800, the embryologist can understand that the doctor has selected any frozen embryo for transfer and can thaw the frozen embryo at the appropriate time for embryo transfer.

[0166] The management module 211 displays a thawing target selection button 2835 in the thawing settings panel 2830. When thawing frozen embryos, the embryologist selects the thawing target selection button 2835. This causes the management module 211 to display a pop-up thawing target selection screen 2900, showing information related to the patient's frozen embryo status. The embryologist confirms the thawing target selection screen 2900. If the "Target Selection" button corresponding to the frozen embryo selected by the doctor is selected, the management module 211 displays information about the selected frozen embryo in the thawing settings panel 2830 based on the frozen embryo management information 230. If no frozen embryo is selected as a thawing target, the management module 211 does not display any embryo information in the thawing settings panel 2830. The management module 211 displays the planned embryo transfer display panel 2820 and the thawing settings panel 2830 side-by-side. Therefore, by comparing the embryo display column 2820 and the thawing setting column 2830, the embryo trainer can easily confirm that the embryo to be transferred is the same as the frozen embryo of the target to be thawed.

[0167] Subsequently, by selecting the thawing start button 2840 by the culture technician, the acquisition module 212 acquires information indicating that the frozen embryos of the thawing object have been thawed and stores it in the cryopreservation management information 230 of the auxiliary storage device 202.

[0168] <Scenario of fresh embryo transfer> Figure 30 This is another example of the egg retrieval ET screen on the embryologist's terminal.

[0169] In reproductive medicine, fresh embryo transfer is sometimes used, which involves egg retrieval and artificial insemination during a natural cycle, without freezing the embryos and transferring them during the egg retrieval cycle. In the natural cycle screen (not shown) of the embryologist terminal 103, the selected embryo can be either a "frozen embryo" or a "fresh embryo" in the embryo selection box. When using fresh embryo transfer, the doctor selects the "fresh embryo" and, similar to the hormone cycle scenario described above, selects the corresponding embryo selection box and the AHA selection box for performing AHA. Thus, the acquisition module 212 receives information from the doctor's terminal 102 regarding the embryo to be transferred freshly and whether AHA should be performed on the embryo, and stores this information in the auxiliary storage device 202.

[0170] In this situation, the trainer terminal output module 214 outputs information based on the information obtained from the doctor terminal 102, such as... Figure 30 As shown, in the egg retrieval ET screen 3000 result details section (refer to...) Figure 25 In the results details section 2520, the results details section 3010 related to the selected embryo for transfer displays information indicating that the embryo is a transfer embryo. For example, Figure 30As shown, the embryologist terminal output module 214 displays the background of the result details column 3010 related to embryos selected for transfer with a different color than the result details column related to embryos not selected for transfer. Thus, the embryologist can easily determine which embryo was selected for transfer by glancing at the oocyte retrieval ET screen 3000. As an example of the display representing embryos for transfer, the same decoration as the display representing virtual prescription of proprietary medications described above can be cited.

[0171] [Referral Letter Creation] Figure 14 This is an example of the referral letter creation process. Figure 31 This is an example of a pregnancy medical record screen (3100) on a doctor's terminal. Figure 32 This is an example of a pop-up display of a referral letter.

[0172] After a patient confirms pregnancy, she may need to be transferred to an obstetrics and gynecology clinic where she can give birth. In clinics specializing in infertility, the rate of patient transfers is relatively high, and doctors bear the burden of creating referral letters.

[0173] The management module 211 displays the Post-Pregnancy Medical Records tab 3110 on the monitor of the doctor's terminal 102. When the Post-Pregnancy Medical Records tab 3110 is selected, the Post-Pregnancy Medical Records screen 3100 is displayed. The management module 211 displays, for example, a pregnant woman's information section, a remaining medication management section, a performance record section, a patient information section, a medical history section, a referral letter creation button 3120, and other medical record information on the Post-Pregnancy Medical Records screen 3100. The management module 211 also displays the Post-Pregnancy Medical Records screen 3100 based on, for example, patient information 221, treatment information 223, proprietary medication information 224, and medication information 228.

[0174] In the post-pregnancy medical record screen 3100, if the doctor selects the referral letter creation button 3120, the referral letter output module 217 performs the following processing, such as creating a referral letter output module 3120. Figure 32 The referral letter draft 3210 is shown. In addition, the referral letter creation button 3120 may be displayed as the "Referral Letter Creation for Transfer" button 1835, for example, on other screens such as the patient information screen 1800 of the doctor's terminal 102.

[0175] That is, such as Figure 14 As shown, the referral information output module 217 extracts information related to the medical information provision form from the medical information (S1410), and establishes a correspondence with the format of the pre-prepared medical information provision form and outputs it (S1420).

[0176] In the information extraction step (S1410), the referral information output module 217 extracts information associated with the predetermined treatment information provision form from the target patient's medical information. This information associated with the treatment information provision form may include basic patient information, treatment history, or other treatment information 223.

[0177] In the output step (S1420), the referral letter output module 217 establishes a correspondence between the extracted information and the format of the pre-prepared medical information provision form to create and output referral letter information. The referral letter output module 217 can display (output) a draft referral letter 3210 containing referral letter information in text format on the monitor of the doctor's terminal 102, or it can be stored (output) as a PDF file in an auxiliary storage device 202, or printed (output) as a referral letter on paper. Furthermore, the referral letter output module 217 can output the referral letter information as a copied text message in the doctor's terminal 102. In this case, the referral letter email can be created by pasting the copied text information into the body of a new email in an external system such as an email system. This reduces the trouble and burden on doctors in creating referral letters.

[0178] [Medical Record Information Extraction] Figure 15 This is an example of the medical record information extraction process.

[0179] Doctors are obligated to create medical records (e.g., electronic medical records), but creating these records can become a burden. The management module 211 displays medical record information retrieval buttons 2125, 2735, and 3135 in the medical record input tables 2120, 2730, and 3130, for example, in the doctor's terminal 102's egg retrieval cycle screen 2100, hormone cycle screen 2700, natural cycle screen (illustration omitted), post-pregnancy medical record screen 3100, and emergency visit screen (illustration omitted). The management module 211 displays these buttons for each date in the medical record input tables 2120, 2730, and 3130, for example. If a doctor selects a medical record information retrieval button 2125, 2735, or 3135, the medical record information retrieval module 218 performs the processing described below and retrieves the medical record information.

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

[0181] In the information extraction step (S1510), the medical record information extraction module 218 extracts medical record information corresponding to the selected medical record information extraction buttons 2125, 2735, and 3135 from the patient's medical information. The medical record information can be, for example, set as information in a so-called "SOAP format" based on four items: Subject, Object, Assessment, and Plan. Furthermore, the medical record information extraction module 218 can be configured, for example, to use a Large Language Model (LLM) to extract SOAP-formatted input information from the medical information.

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

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

[0184] [Collaboration between Doctor's Terminal and Trainer's Terminal 3] Consent Form Information Management Figure 16 This is an example of a consent form information management process. Figure 33 This is an example of a consent form overview screen (3300) on the trainer's terminal. Figure 34 This is an example of a pop-up display screen 3400 used for confirming an agreement. Figure 35 This is an example of a pop-up display of a copy of the consent form.

[0185] When performing assisted reproductive technology, various procedures require obtaining consent forms indicating the patient's consent. The management module 211 displays a consent form overview tab 3310 on the monitor of the fertilization terminal 103, and displays a consent form overview screen 3300 when the consent form overview tab 3310 is selected. In the consent form overview screen 3300, the management module 211 displays, for example, in addition to the basic consent form section 3320, consent forms required for each cycle 3330 and past documents 3335, etc.

[0186] The management module 211 displays various fields in the basic consent form field 3320, such as file name, recipient, submission, submission date, submitter, receipt deadline setting, receipt, receipt date, receipt confirmation person, copy, and remarks. The file name field displays the consent form's file name. The trainer enters in the recipient field whether the patient is the recipient of each consent form. The submission, submission date, and submitter fields allow input of information indicating whether an unsigned consent form was given to the patient, the submission date, and the submitter, respectively. The receipt deadline setting, receipt field, receipt date field, and receipt confirmation person fields allow input of the receipt deadline for signed consent forms, information indicating whether it was received from the patient, the receipt date, and the person confirming receipt, respectively. The copy field displays an image button for showing a copy of the signed consent form.

[0187] The management module 211 displays, for example, the columns for New Cycle, Number, Submission, Submission Date, Submitter, Receipt, Receipt Date, Receipt Confirmation Person, Copies, Remarks, and Past Documents 3335 in the Consent Form column 3330 required for each cycle. The New Cycle column displays the "Create New" button selected when submitting the consent form for a new cycle. The Number column displays information indicating how many cycles of consent forms have been submitted. The Past Documents 3335 column displays a confirmation button for displaying copies of consent forms submitted in past cycles; the rest is the same as the Basic Consent Form column 3320. For example, after the trainer selects the "Confirm" button for Past Documents 3335 in the same row as "Artificial Insemination Implementation Consent Form," as shown... Figure 34 As shown, the management module 211 displays a pop-up screen 3400 for confirming the artificial insemination consent form. For example, in the pop-up screen 3400 for confirming the artificial insemination consent form, the management module 211 displays columns for the consent number, submission date, submitter, receipt date, recipient confirmation, and remarks, as well as image display buttons 3410 for each copy of the consent form. Furthermore, after the trainer selects the image display button 3410, for example... Figure 35 As shown, the consent information management module 219 displays a copy of the consent form for the selected cycle of artificial insemination based on the consent information 225.

[0188] Here, the management module 211 displays a consent confirmation field indicating the consent form submission status in the necessary procedures fields 2160 and 2740 of the oocyte retrieval cycle screen 2100, hormone cycle screen 2700, and natural cycle screen (illustration omitted) on the doctor's terminal 102. Furthermore, when the consent form information management module 219 obtains information from the trainer terminal 103 indicating that a required consent form has been obtained from the patient (S1610), it outputs this information to the doctor's terminal 102 (S1620).

[0189] For example, specifically, such as Figure 33As shown, the trainer receives the "Couple's Consent Form" and "Self-Injection Procedure Consent Form" from the patient and checks the corresponding receipt box on the consent form overview screen 3300 of the trainer's terminal. For example, at this stage, since the trainer has not yet received all the required consent forms 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 box of the doctor's terminal 102. Subsequently, when the trainer receives the remaining required consent forms from the patient, namely the "Sperm Freezing Consent Form," "Micro-fertilization Consent Form," and "Oocyte Freezing Consent Form," and checks the receipt boxes for all required consent forms, the consent form information management module 219 displays information in the consent form receipt confirmation box of the doctor's terminal 102 (see reference). Figure 21 The necessary procedures section 2160 displays information indicating that all required consent forms have been received (e.g., checkmarks). Thus, the doctor can quickly grasp the patient's consent form reception status based on the display on the doctor's terminal 102.

[0190] Additionally, the management module 211 can, for example, add a consent confirmation field to the necessary procedures fields 2160 and 2740 in the egg retrieval cycle screen 2100, hormone cycle screen 2700, and natural cycle screen (illustration omitted) of the doctor's terminal 102, indicating the status of the consent form being submitted (distributed) to the patient. In such cases, for example, when the trainer submits an unsigned consent form to the patient, the acquisition module 212 can obtain information from the trainer's terminal 103 indicating that the required consent form has been submitted (distributed) to the patient. Moreover, when information indicating that the required consent form has been submitted (distributed) to the patient is obtained, the consent form information management module 219 outputs information to the doctor's terminal 102 indicating that the required consent form was obtained from the patient. Furthermore, when the patient obtains an unsigned consent form from the management server 101 via the patient terminal 104, the acquisition module 212 can obtain information indicating that the required consent form has been submitted (distributed) to the patient as a record of the patient terminal 104 accessing the management server 101, etc.

[0191] For example, specifically, such as Figure 33As shown, the fertilization technician presents the "Couple's Consent Form," "Self-Injection Procedure Consent Form," "Sperm Freezing Consent Form," and "Micro-fertilization Consent Form" to the patient in person, and checks the corresponding submission box on the consent form overview screen 3300 of the fertilization technician's terminal. For example, at this stage, since the fertilization technician has not yet presented all the consent forms to the patient, the consent form information management module 219 does not display information indicating that all consent forms have been presented in the consent form confirmation box of the doctor's terminal 102. Subsequently, the fertilization technician presents the remaining consent forms to the patient in person, namely the "Egg Freezing Consent Form," and checks the boxes for all the consent forms to be presented in the submission box. The acquisition module 212 can obtain information indicating that all consent forms have been presented to the patient from the fertilization technician's terminal 103. In this case, the consent form information management module 219, based on the information from the fertilization technician's terminal 103, checks the submission confirmation box of the consent forms on the doctor's terminal 102 (see reference). Figure 21 The necessary procedures section 2160 displays information indicating that all required consent forms have been submitted (e.g., checkmarks). Thus, the doctor can quickly grasp the submission status (distribution status) of the patient's consent forms based on the display on the doctor's terminal 102.

[0192] Furthermore, specifically, although not illustrated, the management module 211 can further display columns for, for example, explanation, explanation date, and explainer for each consent form displayed in the basic consent form column 3320 and the consent form column 3330 required for each cycle. Thus, the trainer can, for example, enter information indicating whether the consent form content was explained to the patient, the explanation date, and the explainer's information in the explanation, explanation date, and explainer's columns, respectively.

[0193] Furthermore, in this scenario, for example, the consent form information management module 219 can be configured to output information indicating that the prescribed consent form content has been explained to the patient to the doctor's terminal 102 when it receives information from the trainer terminal 103 indicating that the prescribed consent form content has been explained to the patient. Specifically, the management module 211 displays a description section (checkbox) for each consent form in the consent form confirmation section of the doctor's terminal 102. Moreover, when the acquisition module 212 receives information from the trainer terminal 103 indicating that the prescribed consent form content has been explained to the patient, the consent form information management module 219 displays information indicating that the consent form content has been explained (e.g., a checkmark) in the description section for the corresponding consent form. Thus, the doctor can quickly determine whether the consent form content has been explained to the patient based on the display on the doctor's terminal 102.

[0194] [Semen Evaluation] Figure 17 This is an example of a semen evaluation process. Figure 36 This is an example of the sperm examination / freezing screen 3600 on the sperm culturer terminal.

[0195] In cases of artificial insemination using assisted reproductive technology, sperm is examined after the semen is collected and brought to the medical facility on the same day or after ejaculation within the hospital. Therefore, it is desirable to be able to perform semen analysis accurately and conveniently.

[0196] The management module 211 displays, for example, a sperm examination / freezing tab 3610 on the monitor of the trainer terminal 103, and displays a sperm examination / freezing screen 3600 when the sperm examination / freezing tab 3610 is selected. The management module 211 displays, for example, a new sperm examination bar 3620, an examination result input bar 3630, a result display bar before adjustment 3640, a judgment bar before adjustment 3645, a result display bar after adjustment 3650, and a judgment bar after adjustment 3655 in the sperm examination / freezing screen 3600.

[0197] The sperm collector collects semen from the partner and performs a semen analysis, for example, using a Sperm Motility Analysis System (SMAS). The Sperm Motility Analysis System is an example of medical device 105, connected to a management server 101 via an internet connection. Alternatively, the Sperm Motility Analysis System can be wired to the sperm collector's terminal 103 via a hospital LAN (local area network). By selecting the "Read" button in the result input field 3630, the sperm collector module 212 reads the semen analysis results, for example, into the management server 101 and stores them in the auxiliary storage device 202. The semen analysis results include, for example, semen volume, sperm concentration, total sperm count, motility, forward motility, normal morphology rate, and white blood cell count.

[0198] Additionally, information related to semen analysis results can be configured to be input by the sperm technician into the technician terminal 103 via the test result input field 3630 on the sperm analysis / freezing screen 3600, and then sent to the management server 101 by the technician selecting the "read" button on the test result input field 3630. Furthermore, the acquisition module 212 can be configured to, for example, acquire the sent semen analysis results from the technician terminal 103 and store them in the auxiliary storage device 202.

[0199] The semen evaluation module 220 evaluates the stored semen examination results.

[0200] That is, such as Figure 17As shown, the semen assessment module 220 acquires information related to the semen examination of the patient's semen (S1710) and assesses whether the information related to the semen examination meets the prescribed criteria (S1720). When the information related to the semen examination meets the prescribed criteria ("Yes" in S1720), it outputs information indicating that the patient's semen meets the prescribed criteria (S1730). When the information related to the semen examination does not meet the prescribed criteria ("No" in S1720), it outputs information indicating that the patient's semen does not meet the prescribed criteria (S1740).

[0201] As a standard for each item in a semen analysis, the normal values ​​for semen analysis established by the WHO (World Health Organization) can be used, for example. Regarding the values ​​of each item in the semen analysis, the semen assessment module 220 performs the assessment and outputs the information as described above. The semen assessment module 220, for example, in... Figure 36 In the pre-adjustment judgment column 3645 and the post-adjustment judgment column 3655, a mark "〇" is displayed when the semen analysis results meet the prescribed criteria, and a mark "×" is displayed when the semen analysis results do not meet the prescribed criteria. According to this structure, the trainer can quickly and easily assess whether the patient's semen meets the prescribed criteria.

[0202] [Estimation 1] The management server 101 is configured to output reference information related to the diagnosis or judgment of infertility treatment based on various patient-related information. For example, the calculation module 250 outputs reference information to the doctor terminal 102 and / or the fertilization specialist terminal 103, which is information related to the optimal egg retrieval date and the number of eggs retrieved, calculated by a machine learning model P that optimizes the number of eggs retrieved for patients planning to undergo in-vitro fertilization.

[0203] The machine learning model P disclosed in this embodiment is a model for estimating the growth of oocytes in the ovaries of patients planning oocyte retrieval. The machine learning model P is, for example, a synthesis function that combines multiple functions with accompanying parameters. The synthesis function with accompanying parameters can be defined by a combination of multiple adjustable functions and parameters. The machine learning model P is obtained by adjusting the aforementioned parameters through machine learning based on learning data and following a model learning procedure. For example, the machine learning model P of this embodiment learns in the following way: given input patient attribute information and treatment information (input data), it outputs the optimal oocyte retrieval day that maximizes the number of retrievalable oocytes and the number of oocytes retrieved under that condition (output data).

[0204] At this point, the learning process uses data such as basic information about past egg retrieval patients, information related to treatment methods (ovarian stimulation, medications used and their administration dates, etc.), and examination results (vital signs, follicle hormone levels, transvaginal ultrasound images, etc.) as input data (explanatory variables). Relative to the input information, information related to the number of eggs retrieved and the date of retrieval is used as the output data (target variable). The input data, for example, is information obtained by the acquisition module 212 from the doctor's terminal 102.

[0205] The machine learning model P is stored in the auxiliary storage device 202 in its learned state, but it can also be relearned at any time based on the information recorded in the reproductive medicine support system 1.

[0206] Specifically, the machine learning model P compares the similarity of various patient basic information, feature quantities (benchmark feature quantities) of information related to examination results, the patient's basic information as the evaluation subject, and feature quantities of information related to examination results. Thus, the machine learning model P, for example, predicts the optimal egg retrieval day to maximize the number of eggs that can be retrieved for the patient as the evaluation subject, and the number of eggs that can be retrieved in that case. When evaluating similarity, for example, if the feature quantity of the patient's data as the evaluation subject is within a pre-set threshold range relative to the benchmark feature quantity determined for each number of eggs that can be retrieved, the number of eggs retrieved corresponding to that benchmark feature quantity is determined as the number of eggs that can be retrieved for that patient. Furthermore, for example, benchmark feature quantities are set for examination result information showing various numbers of eggs growing in the ovary.

[0207] The machine learning model P in this implementation is, for example, a synthesis function with accompanying parameters that synthesizes multiple functions. The synthesis function with accompanying parameters is defined by a combination of multiple adjustable functions and parameters. When the machine learning model P is generated using a multi-layer forward propagation network, the synthesis function with accompanying parameters can be defined, for example, as a combination of linear relationships between layers using weighted matrices, non-linear relationships (or linear relationships) using activation functions in each layer, and biases. The weighted matrices or biases are the parameters in the multi-layer network. In the synthesis function with accompanying parameters, the form of the function changes depending on how the parameters are chosen. In a multi-layer network, by appropriately setting the configuration parameters, a function that can output better results from the output layer can be defined.

[0208] The machine learning model P in this embodiment can be a synthesis function with any additional parameters that satisfies the above requirements, and is a multi-layer neural network model (hereinafter referred to as "multi-layer network"). The machine learning model P using a multi-layer network includes an input layer, an output layer, and at least one intermediate layer or hidden layer located between the input layer and the output layer.

[0209] As a multi-layer network in this embodiment, a deep neural network (DNN) can be used as an object of deep learning. As a DNN, a convolutional neural network (CNN) that targets images can be used in part.

[0210] Figure 37 This is another example of the egg retrieval cycle screen 3700 on the doctor's terminal.

[0211] The management module 211 outputs a screen 3700 showing the egg retrieval cycle for a specific patient to the monitor of the doctor's terminal 102. Here, the calculation module 250, for example, when the patient is undergoing planned egg retrieval and is in an ovulation stimulation cycle, overlaps with the egg retrieval cycle screen 3700 and outputs a calculation pop-up display 3710. When the aforementioned input information about the patient is applied to the machine learning model P, the calculation module 250 outputs information related to the "number of eggs retrieved" and the "optimal egg retrieval day" as output information in the calculation pop-up display 3710, for example, in the form of "expected number of eggs retrieved" and "recommended egg retrieval day". Furthermore, the number of eggs retrieved may be, for example, mature eggs (MII stage eggs). The calculation module 250 can be configured to output the same calculation pop-up display 3710 to the fertilizer terminal 103.

[0212] In addition, the calculation module 250 can be configured, for example, to apply the above-mentioned input information for patients who are scheduled to retrieve eggs and are in the ovulation stimulation cycle, and output the information obtained as output information related to "number of eggs retrieved" and "optimal egg retrieval day" to the doctor terminal 102 or the trainer terminal 103 in the form of a scheduled egg retrieval list, for example.

[0213] In ovarian stimulation, medication is used to stimulate the ovaries, artificially promoting the growth of multiple eggs. However, it's crucial that the follicles reach an appropriate size and that egg retrieval is performed before ovulation. Furthermore, medication may be administered two days prior to retrieval to ensure the eggs within the follicles mature, or the administration of anesthetics and other medications during the egg retrieval procedure may vary depending on the number of eggs to be retrieved. Therefore, knowing in advance the number of eggs to be retrieved and the optimal retrieval date helps doctors, nurses, and chemists to more easily develop a treatment plan while considering the needs of the target patient.

[0214] <Variation Example 1> Furthermore, the machine learning model P is not limited to using information related to the number of eggs retrieved and the date of egg retrieval as output data (target variable). The machine learning model P can learn in a manner such as, for example, when various basic patient information and information related to examination results are available as input data (explanatory variables), calculating (outputting) the pregnancy rate (target variable) in infertility treatment based on patient attributes. In this case, for example, the target variable can be set as "pregnancy" (e.g., pregnancy rate), and the explanatory variables can be set as patient basic information, structured data of treatment methods (e.g., ovarian stimulation, number of eggs retrieved, culture method, medication use, etc.), and image data of embryos (static images and / or animations) to train the learning model. Among the input data, information such as culture method, embryo images, and PGT-A (preimplantation genetic testing for aneuploidy) and blastocyst arrival rate are typically obtained by the acquisition module 212 from the culture technician terminal 103, while other information is obtained from the doctor terminal 102. Thus, for example, the pregnancy rate corresponding to various explanatory variables can be calculated, and various conditions for maximizing the pregnancy rate can be determined. The result, for example, is the availability of machine learning models that estimate key factors to maximize the likelihood of pregnancy (pregnancy rate). In particular, machine learning models can be used to more smoothly estimate factors based on information obtained from trainer terminal 103 and doctor terminal 102.

[0215] More specifically, the machine learning model P can learn from various perspectives regarding infertility treatment and output in a way that estimates the conditions for high success rates. Here, success can be, for example, (1) optimizing (including maximizing) the number of oocytes retrieved, (2) maximizing the blastocyst arrival rate, (3) optimizing the selection of embryos for transfer, and (4) maximizing the cost-effectiveness of treatment methods.

[0216] The teacher data used in the learning of the successfully deduced machine learning model P is not limited to this, but the target variable and explanatory variables can be used as an example as shown below.

[0217] That is, (1) when creating an optimization model for the number of eggs retrieved, the value of the number of eggs retrieved can be used as the target variable, and patient basic information, structured data of treatment methods (ovarian stimulation, number of eggs retrieved, culture method, use of drugs, etc.) and image data of embryo images (static images and / or animations) can be used as explanatory variables.

[0218] (2) When creating a model that maximizes the blastocyst arrival rate, the presence or absence of blastocysts can be used as the target variable, and patient basic information, structured data of treatment methods (ovarian stimulation, number of oocytes retrieved, culture method, use of drugs, etc.), culture method (culture period, use of culture medium, etc.) and image data of embryos (static images and / or animations) (especially embryo images) can be used as explanatory variables.

[0219] (3) When creating an optimized model for embryo selection, the presence or absence of implantation or normal pregnancy can be used as the target variable, and the following data (especially embryo images) can be used as explanatory variables: patient basic information, patient status (endometrial thickness, hormone levels, etc.), examination results (endometrial implantation capacity, PGT-A, etc.), structured data of treatment methods (ovarian stimulation, number of oocytes retrieved, culture method, use of drugs, etc.), and image data of embryos (static images and / or animations). Additionally, in this case, information related to costs can be included in relation to the treatment method.

[0220] (4) When creating a cost-effectiveness maximization model for treatment methods, the pregnancy rate can be used as the target variable, and patient basic information, structured data of treatment methods (ovarian stimulation, number of oocytes retrieved, culture method, use of drugs, etc.) and image data of embryos (static images and / or animations) (especially embryo images) can be used as explanatory variables.

[0221] To predict the success of the above aspects, the machine learning model P can be prepared as a separate machine learning model based on the target prediction result, or it can be configured to switch at least one or a combination of the function and parameter set of the prediction model according to the target prediction result (i.e., the content of the output data can be switched). For example, the prediction module 250 can predict and output the conditions with high success rate related to the target prediction content regarding infertility treatment by using the corresponding machine learning model P according to the prediction content.

[0222] Furthermore, the estimation module 250 can be configured to output reference information based on the output of the analysis unit (not shown) instead of the prediction result of the machine learning model P. This analysis unit, for example, statistically analyzes the input data to estimate treatment methods with high success rates for infertility treatment.

[0223] Furthermore, the input data does not need to include all of the above examples; it can be any combination of more than one type of information.

[0224] Therefore, doctors and trainers can consider the reference information in the calculation module 250 to make diagnoses or judgments regarding infertility treatment. The reference information in the calculation module 250 is also derived from patient information not under the responsibility of doctors and trainers; for example, less experienced doctors or trainers may make more appropriate diagnoses or judgments.

[0225] [Estimation 2] In one implementation, a machine learning model P can be used to assess (estimate) the probability of an embryo being euploid or the quality of the embryo. Embryo images can be used as one of the explanatory variables in the learning of the machine learning model P used for assessment, but are not limited to this. In this case, static images (i.e., morphological data) can be used as embryo images. Furthermore, the learning model used in this case can, for example, be a learning model that includes deep learning-based image recognition capabilities. Image recognition capabilities can include, for example, object recognition, object detection, segmentation, and combinations thereof. As such a learning model, by learning using embryo images (including additional learning), a well-performing and robust machine learning model P (an example of an embryo assessment model) can be obtained regarding the probability of the embryo being euploid or its quality assessment.

[0226] Alternatively, to use a machine learning model P to accurately assess the probability or quality of an embryo being euploid, the estimation module 250 can be configured to preprocess the embryo images based on specified baseline annotations. Furthermore, the machine learning model P used to assess the probability or quality of an embryo being euploid can be a machine learning model learned using embryo images (learning data) with annotations as explanatory variables. Additionally, the annotations on the embryo images used as learning data can be those annotated by the estimation module 250, or they can be unannotated by the estimation module 250 (e.g., manually annotated annotations).

[0227] The annotation function in the estimation module 250 is described below. The estimation module 250 can be configured to perform preprocessing on an embryo image, for example, including: (1) identifying the periphery (boundary) of the embryo, (2) normalizing and segmenting the embryo, and (3) annotating segments that meet a specified criterion with annotations corresponding to that criterion. The estimation module 250 can be configured to, as mentioned above, normalize the size of the embryo or correct the hue of the embryo image (e.g., align to a specified color level, etc.). Furthermore, when performing annotation, the estimation module 250 can use a pre-trained model for annotation, which annotates the inner cell mass (ICM) and trophectoderm (TE) with information related to each tissue after segmenting the embryo. As a pre-trained model for annotation, for example, a learning model can be used that uses the original embryo image and an annotated image of the original embryo image labeled with, for example, the outline information of the ICM and TE in polygonal form as learning data. By using annotated embryo images to assess the likelihood or quality of an embryo as an euploid embryo, the estimation accuracy of the machine learning model P can be further improved.

[0228] Furthermore, the machine learning model P used to assess the probability or quality of an embryo being euploid may include, for example, information related to the patient's and partner's age and the elapsed time of autoinsemination (culture time), in addition to including embryo image information as a descriptive variable. Additionally, embryo image information is sometimes obtained in the form of time-lapse images of the embryo. In this case, the culture time (or current time) is recorded in text in the time-lapse image of the embryo; therefore, the elapsed time of autoinsemination can be obtained, for example, by extracting this text information using optical character recognition (OCR). Furthermore, the machine learning model P used to assess the probability or quality of an embryo being euploid may divide the embryo image information into multiple steps (e.g., N stages. Here, N represents the number of steps as a natural number greater than 2) based on the elapsed time of autoinsemination, and prepare separate machine learning models P1 to PN for each segment of the image information used as a descriptive variable regarding the elapsed time of autoinsemination. In one embodiment, N is, for example, 3 to 15, preferably 8 to 10. The timing for dividing the steps is not limited to this example. For example, it can be listed as the early embryonic stage (2 days after spermatogenesis), day 3, day 4, day 5, day 6, day 7, before vitrification (before embryo freezing), after freezing and thawing, etc. (e.g., N=8 steps).

[0229] The ages of the patient and partner can be, for example, set at the time of egg retrieval and sperm collection. By using this embryo image and related information as explanatory variables, and successful implantation as the target variable, a machine learning model can be trained to obtain a machine learning model PN. This model can assess the probability or quality of an embryo recorded in the embryo image information as an euploid embryo with higher accuracy than before. As a result, for example, by inputting an embryo image and related information (such as the age of the patient and partner) into an appropriate machine learning model PN corresponding to the timing of the embryo image capture (the elapsed time of autoinsemination), the probability or quality of an embryo in the embryo image can be estimated (e.g., scored) with high accuracy. In this case, only one embryo image is needed for evaluation, and the evaluation is non-invasive, allowing for a simple and low-cost assessment of implantation rates.

[0230] The estimation module 250, for example, at a specified time or according to a request from the doctor terminal 102 or the breeder terminal 103, inputs information about the embryo image and the age of the patient and partner associated with the embryo into a machine learning model PN that is suitable for the timing of the embryo image capture, and can estimate the probability or quality of the embryo as an euploid embryo and output the result.

[0231] The doctor terminal output module 213 and the trainer terminal output module 214 of the management server 101 can, for example, output the embryo classification results of the evaluated objects in the embryo classification section to the doctor terminal 102 or the trainer terminal 103 at a predetermined time, or according to the requirements of the doctor terminal 102 or the trainer terminal 103. As an example, the doctor terminal output module 213 and the trainer terminal output module 214 can, for example, output the embryo classification results of the evaluated objects in the embryo classification section to the doctor terminal 102 or the trainer terminal 103 at a predetermined time, or according to the requirements of the doctor terminal 102 or the trainer terminal 103. Figure 27 Hormone cycle screen 2700, planned embryo transfer selection column 2720, or Figure 29 In the thawing object selection screen 2900, in addition to "priority", the "possibility of the embryo being an euploid embryo" or "embryo quality" or related parameters calculated by the calculation module 250 can also be displayed.

[0232] Furthermore, it has been confirmed that the likelihood of an embryo being euploid or its quality is strongly correlated with the mother's age at the time of egg retrieval. Therefore, outside of Japan, for example, due to the difficulty in obtaining normal embryos, women over 40 often choose egg donation. In contrast, the aforementioned machine learning model PN, which learns to estimate implantation rates based on embryo image information, possesses high morphological analysis capabilities and can identify the quality of the inner cell mass (ICM) or trophectoderm (TE), which are difficult to discern with the naked eye. For example, it can "predict" with high accuracy whether an embryo has a high pregnancy rate morphology or whether it is euploid. As a result, by using the aforementioned machine learning model PN to evaluate embryos, for example, even with multiple embryos obtained from older mothers, embryos with high implantation rates (e.g., normal embryos) can be selected with a higher probability than before. Thus, even for women over 40, the option of using their own embryos can be given higher reliability for pregnancy. Furthermore, it supports not only the selection of embryos for transfer but also the selection of vitrified embryos or embryos for PGT-A examination.

[0233] Furthermore, when using the above machine learning model for calculations, the information related to the embryo image and the time elapsed (culture time) of autotransplantation sperm, used as descriptive variables and input data, is typically obtained by the acquisition module 212 from the culturer terminal 103. Additionally, the information related to the probability of the embryo being euploid and the embryo quality, which are target variables, is also obtained by the acquisition module 212 from the culturer terminal 103. Moreover, other information (such as the age of the patient and partner) is obtained by the acquisition module 212 from the doctor terminal 102. By obtaining this information from each terminal through the management server 101, calculations or learning (including relearning) using the machine learning model can be performed efficiently.

[0234] [Electronic Consent Form] In the above implementation scheme, the consent information management module 219 and the consent submission module 519 respectively have the function of supporting the submission of a copy of the consent form from the patient terminal 104 to the management server 101. In addition, the consent information management module and the consent submission module may also have the function of supporting the submission of electronic data of the consent form (e.g., electronic consent form) from the patient terminal 104 to the management server 101.

[0235] Figure 38 This is an example of the consent form submission screen 3800 output to the patient terminal 104.

[0236] The patient terminal output module 251 of the management server 101 collaborates with the patient terminal management module 511 of the patient terminal 104 to output a consent form submission screen 3800 to the patient terminal 104. The consent form information management module 219 of the management server 101 may, for example, output a printable consent form 3810 or an electronic consent form 3815 with an electronic signature field 3820 for the patient's electronic signature in the consent form submission screen 3800.

[0237] In addition, consent forms 3810 and 3815 can be configured to be freely available in patient terminal 104, for example, via a patient application for using the reproductive medicine support system 1.

[0238] Furthermore, consent forms 3810 and 3815 can be configured to allow the consent information management module 219 of the management server 101 to send consent forms containing appropriate content consistent with the patient's treatment, based on instructions from a doctor or trainer. In this scenario, when the consent information management module 219 of the management server 101 receives instructions from the doctor-side patient collaboration module 351 of the doctor terminal 102 or the trainer-side patient collaboration module 451 of the trainer terminal 103 to send the specified consent forms 3810 and 3815 to the target patient terminal 104, it sends the specified consent forms 3810 and 3815 to the target patient terminal 104.

[0239] Patients can, for example, print out the consent form 3810 on paper, sign it, and then bring the signed consent form to the medical facility for submission.

[0240] Alternatively, the consent information management module 219 of the management server 101 can be configured to cooperate with the consent submission module 519 of the patient terminal 104 to accept the patient's electronic signature in the electronic signature field 3820 of the electronic consent form 3815, and receive the electronically signed consent form (e.g., electronic consent document) from the patient terminal 104 when the submit button 3830 is selected. Thus, patients can submit their consent forms to medical institutions without time or space constraints.

[0241] Furthermore, the electronic signature mentioned in this specification can be an electronic signature with authentication data (electronic certificate) or an electronic signature without authentication data (electronic certificate). For example, an electronic signature can be a written document signed using a stylus or similar device on a tablet or touch panel and saved as electronic data.

[0242] The consent form information management module 219 of the management server 101 stores, for example, the electronically signed consent form received from the patient terminal 104 in consent form information 225. Furthermore, the consent form information management module 219 displays, for example, the patient's consent form overview screen 3300 on the therapist terminal 103 and the patient's consent form receipt confirmation section on the doctor terminal 102 (see reference). Figure 21 In the necessary procedures field 2160), an output indicating that the corresponding consent form has been received is displayed. Additionally, the consent form information management module 219 can be configured to output a message indicating that a consent form has been received from the patient, for example, to all or part of the message associated with the patient, on the doctor's terminal 102 and the trainer's terminal 103.

[0243] Furthermore, the doctor terminal 102 may include a consent form submission module. Moreover, the consent form information management module 219 of the management server 101 can be configured to, upon receiving a signed consent form from the patient terminal 104, output the patient's signed consent form to the doctor terminal 102, and accept the doctor's electronic signature at the doctor terminal 102. The input for accepting the electronic signature from the doctor terminal 102 can be performed through the same processing as that used for the patient terminal 104. Thus, an electronic consent form with consent obtained can be obtained between the patient and the doctor (between both parties).

[0244] Furthermore, the consent information management module 219 of the management server 101 can be configured to, when receiving a signed consent form from the patient terminal 104 of one of the patients and one of the partners in a relationship based on patient information 221 and partner information 222, output the signed consent form of one patient to the patient terminal 104 used by the other patient, and receive the electronic signature of the other patient from the patient terminal 104 used by the other patient. In this case, an electronic consent form with consent obtained can be obtained between the patient and the partner (between both parties).

[0245] Similarly, the consent information management module 219 of the management server 101 can be configured to sequentially output consent forms and receive electronic signatures from the terminals used by the patient, partner, and doctor, and receive the electronic signatures of all three parties in a single electronic consent form. Thus, an electronic consent form with consent obtained can be obtained between the patient, partner, and doctor (among the three parties).

[0246] [Sharing of examination and treatment results] In this reproductive medicine support system 1, it can be configured to share a portion of a patient's examination or treatment results with the patient according to the instructions 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 "notification of embryo culture results" to a specific patient, the patient terminal output module 251 sends the specified "notification of embryo culture results" to that specific patient. The instruction to send the "notification of embryo culture results" includes a time-lapse image of the specified embryo of the patient stored in the embryo information 226 published in the notification, as well as information related to the embryo (e.g., culture days, grade).

[0247] Figure 39 This is an example of a 3900-page report of examination and treatment results.

[0248] The patient terminal output module 251 of management server 101 collaborates with the patient terminal management module 511 of patient terminal 104 to output an examination and treatment result report screen 3900 to patient terminal 104. For example, in the examination and treatment result report screen 3900, the patient terminal output module 251 of management server 101 outputs a notification form 3910 of embryo culture results. For example, based on instructions from the chemist terminal 103, the patient terminal output module 251 displays, in the embryo culture result notification form 3910, a time-lapse image of the patient's specified embryo from embryo information 226, and information related to the embryo (e.g., culture days, grade).

[0249] In infertility treatment, patients can easily become anxious in various situations. However, it is beneficial to continue treatment with peace of mind by obtaining information related to treatment progress from doctors or embryologists, for example, through examination and treatment result reports (screen 3900). Furthermore, the information that can be shared with doctors or embryologists is not limited to embryo culture results.

[0250] [Medication administration and management] This reproductive medicine support system 1 can be configured to provide medication support for patients.

[0251] Figure 40 This is an example of a 4000-page screen for drug administration and management.

[0252] The patient terminal output module 251 of the management server 101 collaborates with the patient terminal management module 511 of the patient terminal 104 to output the medication administration and management screen 4000 to the patient terminal 104. The patient terminal output module 251 of the management server 101 outputs information related to the prescription drugs issued by the doctor to the medication administration and management screen 4000.

[0253] The patient terminal output module 251 outputs, for example, a treatment history calendar 4010 and prescription drug-related information 4020 in the medication administration management screen 4000. Based on treatment information 223, the patient terminal output module 251 displays, for example, treatment information for this week and medication information for today (e.g., drug name, dosage) or medication information for tomorrow (e.g., drug name, dosage) as prescription drug-related information 4020. Furthermore, the patient terminal output module 251 can be configured to display prescription drug-related information for any date selected in the treatment history calendar 4010 on the patient terminal 104.

[0254] For medications with a specified dosing time, the patient terminal output module 251 displays the dosing time along with the medication name. Although not specifically illustrated, the patient terminal output module 251 can also output an image of the prescription drug as medication information. Furthermore, the patient terminal output module 251 can also output information such as instructions on how to use self-injectable preparations as medication information. Additionally, information related to the image of the prescription drug or instructions on how to take the medication can be configured to be output when the patient terminal 104 selects information related to the prescription drug (e.g., text display).

[0255] In infertility treatment, sometimes a large variety and quantity of medications are prescribed, making it difficult for patients to manage their medication intake independently. In such cases, receiving medication-related instructions or information from the doctor at any time via the medication administration and management screen 4000 allows patients to continue treatment with peace of mind, which is beneficial. Furthermore, according to this structure, patient medication can be managed based on the screen of the doctor's terminal 102 and commands issued from the management server 101.

[0256] Figure 42 This is another example of a medication administration and management screen (4200).

[0257] The patient terminal output module 251 of the management server 101 differs in the following aspects: In the medication administration management screen 4200, the medication schedule 4210 is output instead of... Figure 40 Treatment history calendar 4010 and information related to prescription drugs 4020.

[0258] The patient terminal output module 251 displays, for example, a medication schedule based on menstrual cycle units in the medication schedule 4210 in a graphical format. The patient terminal output module 251 also displays, for example, menstrual cycle number, date, prescription drug information (e.g., oral medication and injectable medication sections), and hormone levels in the medication schedule 4210. The patient terminal output module 251 outputs this information, for example, based on treatment information 223, etc.

[0259] Hormone levels can be obtained, for example, from blood hormone concentration tests conducted during hospital blood draws and stored as treatment information 223. Hormone levels are not limited to these; examples include blood concentration tests of female hormones such as follicle-stimulating hormone (FSH), luteinizing hormone (LH), and estradiol (E2).

[0260] By displaying this medication schedule 4210, patients can not only know "when to take the medication and what medication to inject," but also "what their hormone levels are when they come to the hospital."

[0261] In addition, the medication administration management screen 4200 can be configured to be accessed from the top screen of the application on the patient terminal, or it can be configured to be accessed when clicking on another calendar (e.g., the treatment history calendar 4010).

[0262] In addition, the patient terminal output module 251 can be configured to send a notification to the patient terminal 104 urging medication administration at an appropriate time.

[0263] 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" to a specific patient, the patient terminal output module 251 may send the prescribed "medication schedule" to that specific patient. The instruction to send the "medication schedule" includes information related to the patient's prescription drugs (e.g., medication date, drug name, dosage) stored in the drug information 228 published in the medication schedule or the prescription schedule information 229.

[0264] Furthermore, the patient terminal output module 251 can be configured to display a medication completion button on the medication administration and management screen 4200. When the patient selects the medication completion button on the patient terminal 104, the acquisition module 212 can obtain information indicating that the medication has been taken from the patient terminal 104. Upon obtaining this information, the acquisition module 212 stores it, for example, in the prescription schedule information 229. Thus, for example, a doctor can confirm the patient's medication record on the doctor's terminal 102 and provide appropriate responses, guidance, and treatment.

[0265] [Patient Learning] This reproductive medicine support system 1 can be configured to provide patients with knowledge about infertility treatment. For example, the reproductive medicine support system 1 can be configured so that doctors can easily provide patients with knowledge related to current or future treatments. For instance, when the acquisition module 212 of the management server 101 receives an instruction from the doctor's terminal 102 to send "infertility treatment-related teaching materials" to a specific patient, the patient terminal output module 251 sends the specified "infertility treatment-related teaching materials" to that specific patient. The instruction to send "infertility treatment-related teaching materials" includes information specifically related to the infertility treatment (e.g., information related to the teaching material ID, the storage location of the teaching material, etc.).

[0266] Figure 41 This is an example of a patient learning screen 4100.

[0267] The patient terminal output module 251 of the management server 101 collaborates with the patient terminal management module 511 of the patient terminal 104, and outputs a patient learning screen 4100 to the patient terminal 104. For example, the patient terminal output module 251 of the management server 101 outputs educational materials 4110 (here, animated materials) and treatment information 4120 in the patient learning screen 4100. Based on instructions from the doctor's terminal 102, the patient terminal output module 251 displays educational materials 4110, such as materials explaining the treatment or surgery to be performed the next day (e.g., text, still images, animations, etc.). The patient terminal output module 251 outputs simple instructions and points to note regarding the treatment as treatment information 4120.

[0268] In infertility treatment, doctors typically explain the treatment plan to patients at the medical facility. However, these explanations often contain unfamiliar terminology, which may fade from the patient's memory over time. Furthermore, doctors may sometimes unintentionally omit certain information. In such cases, patients can benefit from receiving real-time treatment-related instructions from their doctor via a patient learning screen (4100) based on the patient's progress, allowing them to continue treatment with peace of mind. Additionally, this system also improves the efficiency of diagnosis and treatment for doctors.

[0269] In addition, the instruction to send "teaching materials related to infertility treatment" can be configured to be automatically sent from the doctor terminal 102 to the management server 101, for example, based on the treatment information 223 entered in the doctor terminal 102.

[0270] [Data Utilization] Previously, it was extremely difficult to manage and analyze information related to infertility treatment in a seamless manner, from egg retrieval to sperm donation, culture, and embryo transfer. Therefore, there was a problem that information related to the patient's infertility treatment could only be analyzed and evaluated at each individual step. As a result, based on the analysis results of each step—for example, specifically, based on (step 1) patient X's egg retrieval results, (step 2) patient X's oocyte culture results, and (step 3) patient X's endometrial transfer results—only localized backward optimization of a single step was possible.

[0271] In contrast, according to the reproductive medicine support system 1 of the present invention, for example, in collaboration between doctors and embryologists, the information acquired by each can be stored in the auxiliary storage device 202 from the doctor's terminal 102 or the embryologist's terminal 103, respectively. Furthermore, the management server 101 can systematically store and manage various information acquired by doctors and embryologists, for example, from the initial stage of storage in the auxiliary storage device 202, according to prescribed rules.

[0272] For example, management server 101 stores medical information by establishing a correspondence between it and patient identification information (e.g., patient ID, partner ID, or both). As an example, any examination information (e.g., information related to embryo grade) is stored in auxiliary storage device 202 in the form of labeled branch numbers, i.e., patient ID, its sub-egg retrieval ID, and its sub-egg ID and / or sperm ID. The medical information stored in auxiliary storage device 202 (e.g., patient information 221, partner information 222, treatment information 223, proprietary medication information 224, consent form information 225, embryo information 226, sperm management information 227, medication information 228, prescription schedule information 229, cryopreservation management information 230) is a systematic data structure that establishes a correspondence between the patient's identification information and the medical information. In other words, the information obtained by the doctor based on (step 1), the information obtained by the embryologist based on (step 2), and the information obtained by the doctor based on (step 3) are jointly stored. Through this mechanism, doctors and embryologists can view each other's information via doctor terminal 102 or embryologist terminal 103, respectively. For example, they can view the entire process from egg retrieval to sperm donation, culture, and embryo transfer in one go. Furthermore, based on this systematic data structure, management server 101 can efficiently perform analyses and evaluations related to infertility treatment.

[0273] In this reproductive medicine support system 1, for example, the calculation module 250 of the management server 101 may include the following functions: based on medical information stored in the auxiliary storage device 202, and according to a series of treatments for some or all patients, analyze and / or calculate or perform backward evaluation on various perspectives. Furthermore, for example, the doctor terminal output module 213 and the trainer terminal output module 214 may be configured to output the results of the analysis, calculation, or evaluation by the medical information and / or calculation module 250 to the doctor terminal 102 or the trainer terminal 103, respectively. The doctor terminal output module 213 and the trainer terminal output module 214 may be configured, for example, to output the results of the analysis, calculation, or evaluation by the medical information and / or calculation module 250 to the doctor terminal 102 or the trainer terminal 103, respectively, according to the requirements of the doctor terminal 102 or the trainer terminal 103.

[0274] Figure 43 This is an example of the egg retrieval cycle screen on the doctor's terminal (4300).

[0275] The doctor terminal output module 213 displays, for example, the egg retrieval cycle screen 4300 on the doctor terminal 102. The doctor terminal output module 213 can be configured to display, for example, the calculation results 4310 related to egg retrieval in the egg retrieval cycle screen 4300.

[0276] The display of the calculation result 4310 by the doctor terminal output module 213 will be explained below.

[0277] <Calculation of the day with the highest number of eggs retrieved> The estimation module 250 is configured, for example, to estimate, statistically or based on medical insights or using a machine learning model P1, the menstrual cycle date (taking the first day of the menstrual period as the first day of the cycle) and the number of mature eggs (MII eggs) retrieved when any medication (e.g., an ovulation-inducing agent) is administered to the patient. As an example, the estimation module 250 is configured, for example, to use the patient's medical information (e.g., hormone levels, endometrial status, etc.) and the machine learning model P1 to estimate the egg retrieval status when any ovulation-inducing agent (e.g., an ovulation-inducing agent listed in the list of oral and nasal medications prescribed in the egg retrieval cycle) is administered to the target patient. Here, the machine learning model P1 used by the estimation module 250 is, for example, a machine learning model that uses medical information including prescription information for at least any patient's past ovulation-inducing drugs (e.g., type of hormone, dosage, and timing of administration) and the patient's vital signs data (e.g., age, BMI, and ovarian age hormone values ​​(e.g., anti-Müllerian hormone (AMH) values)) as explanatory variables, and the number of mature oocytes retrieved on each menstrual cycle day as the target variable. This machine learning model learns using information obtained by the doctor based on (step 1), information obtained by the trainer based on (step 2), and information obtained by the doctor based on (step 3).

[0278] <Display of Calculation Results> The calculation module 250, for example, displays the calculation results 4310 related to egg retrieval at any time (e.g., when the doctor selects a tab on the egg retrieval cycle screen 4300), overlapping with the egg retrieval cycle screen 4300. Based on the aforementioned machine learning model P1, it outputs, for example, the calculated number of mature eggs (MII eggs) retrieved for each menstrual cycle day as the calculation result. Based on this calculation result, the calculation module 250 displays, for example, the calculated number of mature eggs retrieved for each menstrual cycle day in the calculation result 4310 as a graph (e.g., a scatter plot including a smooth line). The calculation module 250 displays, for example, the relationship between the menstrual cycle day (e.g., 3-7 days) including the menstrual cycle day with the highest number of mature eggs retrieved and the calculated number of mature eggs retrieved on that day. Thus, the doctor can determine the day with the highest number of mature eggs retrieved and decide on that day or days before or after it as the egg retrieval day. As a result, egg retrieval results (number of mature eggs retrieved) can be improved.

[0279] Figure 44 This is an example of the hormone cycle screen 4400 on the doctor's terminal.

[0280] The doctor's terminal output module 213 displays, for example, a hormone cycle screen 4400 on the doctor's terminal 102. The doctor's terminal output module 213 can be configured to display, for example, a transplant-related calculation result 4410 in the hormone cycle screen 4400.

[0281] The display of the calculation result 4410 by the doctor terminal output module 213 will be explained below.

[0282] <Estimated success rate per transplant day> The estimation module 250 can be configured to, for example, estimate the success rate for each implantation day based on the patient's medical information, statistically or based on medical insights, or using a machine learning model P2. The success rate for each implantation day is, for example, the implantation success rate (e.g., implantation rate) for the target patient on any given day (any cycle day (hormonal cycle day or natural cycle day)). As an example, the estimation module 250 is configured to, for example, estimate the success rate for each implantation day for the target patient using the patient's medical information (e.g., embryo grade and vital sign data (cycle day and endometrial thickness and hormone levels on that day)) 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 that uses medical information about past patients, including at least embryo grade and vital sign data (cycle day and endometrial thickness and hormone levels on that day), as explanatory variables, and the implantation day (e.g., cycle day) and its implantation outcome (e.g., implantation success) as target variables. Embryo grading is not limited to these methods; for example, it can use grading based on Gardner classification, assessments based on human observation of embryo images, or mechanical assessments. Endometrial thickness can be measured, for example, using ultrasound examination.

[0283] <Display of Calculation Results> The doctor's terminal output module 213, for example, at any time (e.g., when the doctor selects the hormone cycle screen tab or the natural cycle screen tab), displays the estimated results 4410 related to transplantation, overlapping with the hormone cycle screen 4400 or the hormone cycle screen. Based on the aforementioned machine learning model P2, it outputs, for example, the estimated value of the transplantation success rate (e.g., implantation rate) for each transplantation day (e.g., cycle day (menstrual cycle day or hormone cycle day)). The estimation module 250, based on this estimation result, displays, for example, the estimated value of the transplantation success rate for each transplantation day in a graph (e.g., a bar chart) within the estimation result 4410. The estimation module 250, for example, displays the relationship between the transplantation day and the transplantation success rate on that day within a few days (e.g., 7 days) including the cycle day with the highest transplantation success rate. Thus, the doctor can identify the day with the highest transplantation success rate and determine that day or the days before and after it as the transplantation day. As a result, transplantation results (implantation rate) can be improved.

[0284] In addition, Figure 43 and Figure 44The image shows an example of the doctor terminal output module 213 displaying the calculated results 4310 and 4410 on the screen of the doctor terminal 102 (egg retrieval cycle screen 4300, hormone cycle screen 4400). However, it can also be configured to display the same calculated results or charts on the screen of the trainer terminal 103 by the trainer terminal output module 214.

[0285] [Control Panel] In reproductive medicine, the in vitro fertilization process can be roughly divided into three steps: (1) egg retrieval, (2) culture, and (3) embryo transfer. In order to improve the pregnancy rate, it is important to have a comprehensive understanding of the above (1) to (3) steps. However, it is also important to pay attention to each step and to understand the factors or trends that may affect the pregnancy success rate from various aspects.

[0286] Management server 101 can, for example, extract a portion of the information stored in auxiliary storage device 202 from various perspectives and output it via network to doctor terminal 102 and / or trainer terminal 103 in a visual interface. Management module 211 calculates the required indicators based on the extracted values ​​as needed and stores them in auxiliary storage device 202. Doctor terminal output module 213 and trainer terminal output module 214 can output the extracted values ​​or calculated indicators via network to doctor terminal 102 and / or trainer terminal 103. Specific examples are given below to illustrate the relevant outputs.

[0287] Figure 45 This is an example of the control panel screen 4500 of the doctor terminal 102 and / or the trainer terminal 103. The doctor terminal output module 213 and the trainer terminal output module 214 can be configured to display the control panel screen 4500, for example, on the doctor terminal 102 or the trainer terminal 103 respectively.

[0288] The doctor terminal output module 213 and the trainer terminal output module 214 are displayed on the control panel screen 4500, for example, showing the patient count progress bar 4510, patient dynamic bar 4520, treatment cycle count bar 4530, oocyte retrieval count bar 4540, embryo transfer count bar 4550, laboratory results bar 4560, pregnancy results bar 4570, cumulative pregnancy rate bar categorized by oocyte retrieval count 4580, and cumulative pregnancy rate bar categorized by embryo transfer count 4590, etc.

[0289] The patient count trend column 4510, for example, displays a bar chart of the clinic's patient count for the current month and the past three months, categorized by color according to follow-up visits / initial visits, and shows the totals together with absolute numbers and percentages, along with month-on-month, year-on-year, and new patient rate information. The management module 211, for example, calculates the patient count for the past three months based on treatment information 323 related to daily patient treatment obtained from the doctor's terminal 102 via the Internet by the acquisition module 212 of the management server 101, and stores it in the auxiliary storage device 202.

[0290] The patient activity column 4520, for example, creates a bar chart by color-coding the activity of clinic patients for the current month and the past three months (e.g., initial visits, graduations (due to pregnancy, cessation of visits), and number of transfers), and displays it along with absolute numbers, month-on-month comparisons, and year-on-year comparisons. The management module 211, for example, calculates clinic patient activity information based on treatment information 323 related to daily patient treatment obtained by the acquisition module 212 of the management server 101 from the doctor's terminal 102 via the Internet, and stores it in the auxiliary storage device 202.

[0291] The treatment cycle count column 4530, for example, creates a bar chart of the patient's treatment cycle count for the current month, divided by age group, and displays it by color according to treatment method (artificial insemination, egg retrieval, embryo transfer, others). The management module 211, for example, calculates the treatment cycle count based on treatment information 323 related to the patient's treatment obtained by the acquisition module 212 of the management server 101 from the doctor's terminal 102 via the Internet, and stores it in the auxiliary storage device 202.

[0292] The column 4540, representing the number of egg retrieval procedures performed, displays a bar chart showing the number of procedures performed in the current month and the past three months, categorized by patient age group using color, and showing it along with month-on-month and year-on-year comparisons. The management module 211 calculates the number of egg retrieval procedures based on treatment information 323 related to egg retrieval obtained from the doctor's terminal 102 via the Internet by the acquisition module 212 of the management server 101, and stores this information in the auxiliary storage device 202.

[0293] The transplant implementation count column 4550, for example, displays a bar chart of the number of transplant surgeries performed in the current month and the past three months, divided by color according to each patient's age group, and shows it together with information such as month-on-month and year-on-year comparisons. The management module 211, for example, calculates the transplant implementation count based on transplant treatment information 323 obtained from the doctor's terminal 102 via the Internet by the acquisition module 212 of the management server 101, and stores it in the auxiliary storage device 202.

[0294] The laboratory results column 4560, for example, displays a line graph showing the trend of blastocyst arrival rate (average) for the current month and the past three months, categorized by patient age group and overall average using color coding, and showing it along with month-on-month and year-on-year information. Generally, egg retrieval is performed by the doctor, and the retrieved eggs are sent to the culture room. The egg retrieval results (e.g., number of eggs retrieved) or their management (whether frozen, etc.) are handled by the embryologist. The management module 211, for example, calculates information on the trend of blastocyst arrival rate based on embryo information 426 related to embryo growth obtained from the embryologist terminal 103 via the Internet by the acquisition module 212 of the management server 101, and stores it in the auxiliary storage device 202.

[0295] The pregnancy performance column 4570, for example, for patients who underwent embryo transfer last month, displays bar charts of pregnancy rates for the current month and the past three months, as well as line charts showing the average trends for each age group and the overall pregnancy, along with month-on-month and year-on-year information. The management module 211 calculates pregnancy performance information, for example, based on pregnancy treatment information 323 obtained from the doctor's terminal 102 via the Internet by the acquisition module 212 of the management server 101, and information obtained from the embryologist terminal 103 (e.g., embryo information 426), and stores it in the auxiliary storage device 202. For example, the management module 211 adds information obtainable from the embryologist terminal as variables to the pregnancy establishment information obtained from the doctor's terminal 102, and calculates the pregnancy rate. As an example, information obtainable from the embryologist terminal may include the embryologist's command and the status based on that command (e.g., whether a frozen embryo or a fresh embryo was transferred, and the status of each embryo in that case).

[0296] The cumulative pregnancy rate column 4580, categorized by the number of egg retrievals, for example, uses color to divide the bar chart of the number of pregnancies for each egg retrieval and the cumulative pregnancy rate trend (line graph) according to the patient's age group and the overall average, and displays it as a total and percentage. The management module 211, for example, calculates the cumulative pregnancy rate information categorized by the number of egg retrievals based on the treatment information 323 of egg retrieval and pregnancy obtained from the doctor's terminal 102 via the Internet by the acquisition module 212 of the management server 101, and information obtained from the embryologist terminal 103 (e.g., embryo information 426), and stores it in the auxiliary storage device 202. As information obtainable from the embryologist terminal, in addition to the pregnancy rate-related information mentioned above, as an example, it may also include the result of the nth egg retrieval (n is a natural number) categorized by patient. Furthermore, as egg retrieval results, in addition to the number of eggs retrieved, it may also include the results of in vitro culture (e.g., the number of frozen embryos and their status (e.g., the number of blastocysts reached, the number of early frozen embryos, the number of fertilized embryos)).

[0297] The cumulative pregnancy rate column 4590, categorized by number of embryo transfers, for example, uses color to divide the number of pregnancies for each number of transfers and the cumulative pregnancy rate trend (line graph) according to the patient's age group and the overall average, and displays it as a total number and percentage. The management module 211 calculates the cumulative pregnancy rate information categorized by number of egg retrievals, for example, based on the treatment information 323 of embryo transfer and pregnancy obtained by the acquisition module 212 of the management server 101 via the Internet from the doctor's terminal 102 and the information obtained from the embryologist terminal 103 (e.g., embryo information 426), and stores it in the auxiliary storage device 202.

[0298] According to this structure, the information stored in the auxiliary storage device 202 is visualized and displayed in a visually easy-to-understand form, thus enabling effective clinical use of the information. Furthermore, the information analyzed and displayed on the control panel screen 4500 by the management server 101 is not limited to the examples described above. For instance, the management server 101 can summarize 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 control panel screen 4500. As an example, it can also backward summarize information from the entire clinic or the overall patient information based on various perspectives.

[0299] <Other variations> The modules disclosed in the above implementation schemes can be composed of multiple sub-modules. In addition, other modules can also perform or implement some or all of the actions or functions performed by a module.

[0300] One or more functional elements that are implemented through the modules of the trainer terminal 103 in the above implementation scheme can also be implemented through the modules of the doctor terminal 102.

[0301] Furthermore, any one or more of the management servers 101 and patient terminals 104 constituting the reproductive medicine support system 1 of the present invention may be located in different countries. Additionally, the management servers 101 may be implemented by one or more computers, any of which may also be located in different countries.

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

[0303] In the above implementation scheme, the management server 101, the doctor terminal 102, and the trainer terminal 103 are each independent entities. However, the management server 101, as well as the doctor terminal 102 and / or trainer terminal 103, can also be integrated into one unit. Furthermore, the doctor terminal 102 and the trainer terminal 103 can be configured as a single terminal, for example, by simultaneously running a doctor's work application and a trainer's work application on one terminal.

[0304] In the above implementation, when the acquisition module 212 receives input from an operator (e.g., a doctor or a trainer) from the doctor terminal 102 or the trainer terminal 103, it extracts data that meets the conditions corresponding to the input and displays several conditions corresponding to the input. However, the conditions extracted by the acquisition module 212 are not limited to the examples described above. Other examples of conditions for extraction by the acquisition module 212 include various conditions (indicators or items) that may affect pregnancy success, such as the type of culture medium used in embryo culture, conditions of treatment or procedures performed on the patient or embryo (external factors), the patient's condition (internal factors), or conditions related to the doctor's or trainer's judgment (external factors). Additionally, two or more indicators or items can be combined as a single condition. Furthermore, conditions related to the doctor's or trainer's judgment may include, for example, peripheral information related to the patient's complaints (desire to minimize the pre-pregnancy period, minimize costs, etc.), or the doctor's or trainer's interpretation and judgment based on culture observations.

[0305] In the above implementation scheme, the management module 211 outputs different patient information screens (e.g., referring to...) to the trainer terminal 103 and the doctor terminal 102. Figure 18 , 19 Furthermore, the patient information displayed on the patient information screen can be different. However, the management module 211 can also make the patient information output to the trainer terminal 103 and the patient information output to the doctor terminal 102 the same. In this case, it is preferable, for example, to allow trainers to share more patient information. Furthermore, the management module 211 can also make the patient information screen output to the trainer terminal 103 and the patient information screen output to the doctor terminal 102 have a substantially the same structure. In this case, the configuration of each patient information is common on the patient information screen of the doctor terminal 102 and the patient information screen of the trainer terminal 103, therefore, it is preferable, for example, to make communication between doctors and trainers easier.

[0306] In the above implementation scheme, the consent form confirmation column is displayed on the doctor's terminal 102, and the consent form information management module 219 displays, for example, information indicating that all consent forms that should be received have been received in the consent form receipt confirmation column of the doctor's terminal 102. However, the consent form information management module 219 can also be configured to obtain information related to the consent forms from the doctor's terminal 102 and output the obtained information related to the consent forms to the trainer's terminal 103.

[0307] In this scenario, the management module 211 also outputs the same consent form overview screen as the trainer terminal 103 on the doctor's terminal 102. Furthermore, for example, when a doctor receives a consent form, they check the corresponding consent form's receiving field on the consent form overview screen of the doctor's terminal 102 and enter information to confirm the receiving doctor in the recipient field. The consent form information management module 219 acquires the input from the doctor's terminal 102 and stores it as consent form information 225. Additionally, the consent form information management module 219 displays information indicating that the consent form has been received (a checkmark in the consent form's receiving field) and information related to the recipient on the consent form overview screen 3300 of the trainer terminal 103. With this structure, doctors and trainers can address the distribution and receipt of difficult-to-manage consent forms by sharing the latest information.

[0308] In the above implementation scheme, the example of collaboration between doctor terminal 102 and trainer terminal 103 implemented by management server 101 has been described in detail. However, in this reproductive medicine support system 1, collaboration is not limited to doctor terminal 102 and trainer terminal 103, and collaboration can be carried out among all terminals that can be connected to management server 101.

[0309] For example, there are no particular restrictions on the location of each terminal. For example, the information required for diagnosis can be obtained in facility A, and the information can be displayed on the terminal in facility B for diagnosis, so as to facilitate remote diagnosis and treatment. For example, it can be a structure in which the management server 101, the doctor (doctor terminal 102) and the trainer (trainer terminal 103) are connected in the same medical facility network, or it can be a structure in which separate or partial devices are configured in different medical facilities and connected to each other via networks such as the Internet.

[0310] In the above implementation scheme, the management server 101 is configured to extract and output diagnostic and treatment information. From another perspective, the reproductive medicine support system 1 itself stores various information in the auxiliary storage device 202, including patient information 221, partner information 222, treatment information 223, proprietary drug information 224, consent form information 225, embryo information 226, sperm management information 227, drug information 228, prescription schedule information 229, cryopreservation management information 230, machine learning model P, etc., and can also be understood as a system that comprehensively manages the aforementioned information.

[0311] Furthermore, the present invention is not limited to the above embodiments, but also includes various modifications. For example, the above embodiments have been described in detail to illustrate the present invention in an easily understandable manner, and are not necessarily limited to including all the structures described. In addition, a part of the structure of one embodiment may be replaced with the structure of another embodiment, and the structure of another embodiment may be added to the structure of one embodiment. Furthermore, other structures may be added, deleted, or replaced to a part of the structure of each embodiment.

[0312] Furthermore, the aforementioned structures, functions, processing units, and processing methods can be partially or entirely implemented in hardware, for example, through design in integrated circuits. Additionally, the aforementioned structures and functions can be implemented in software by a processor interpreting and executing programs that perform their respective functions. The programs, tables, files, and other information implementing these functions can be stored in memory, or recording devices such as hard disks, SSDs (Solid State Drives), or recording media such as IC cards, SD cards, and DVDs.

[0313] Furthermore, while control lines or information lines are considered necessary in the description, not all control lines or information lines are necessarily shown on the product. In practice, almost all structures can be considered interconnected.

[0314] In addition, the above embodiments disclose at least the structures described in the claims.

[0315] Explanation of reference numerals in the attached figures: 1: Reproductive medicine support system; 101: Management Server; 102: Doctor's Terminal; 103: Trainer Terminal; 104: Patient terminal; 105: Medical devices; 211: Management module; 212: Get the module; 213: Doctor terminal output module; 214: Trainer Terminal Output Module; 215: First Prescription Module; 216: Second prescription module; 217: Referral message output module; 218: Medical record information extraction module; 219: Consent Form Information Management Module; 220: Semen Assessment Module; 250: Calculation module; 251: Patient terminal output module.

Claims

1. A reproductive medicine support server, characterized in that, include: The Acquisition Department acquires medical information related to patients' reproductive medicine. A doctor terminal output unit, which outputs at least a portion of the medical information to a doctor terminal used by a doctor connected via the Internet; as well as The trainer terminal output unit outputs examination information related to at least one of the eggs, embryos, or sperm from the medical information to the trainer terminal used by the trainer connected via the Internet. The trainer terminal is located outside the medical institution where the doctor terminal is located. The acquisition unit is configured to acquire treatment information related to the patient's treatment from the doctor's terminal as the medical information; The therapist terminal output unit is configured to output the acquired treatment information to the therapist terminal.

2. The reproductive medicine support server according to claim 1, characterized in that, When the acquisition unit acquires information related to the treatment of at least one of the egg, the embryo, or the sperm from the doctor's terminal as the treatment information, the trainer terminal output unit outputs the acquired treatment-related information to the trainer terminal.

3. The reproductive medicine support server according to claim 1, characterized in that, When the acquisition unit acquires information about the selected embryo for transplantation as the treatment information, the embryologist terminal output unit outputs the information about the selected embryo for transplantation to the embryologist terminal.

4. The reproductive medicine support server according to claim 1, characterized in that, When the acquisition unit acquires information related to the state of at least one of the egg, the embryo, or the sperm from the culturist terminal via the Internet, i.e., state information, the doctor terminal output unit outputs the acquired state information to the doctor terminal via the Internet.

5. The reproductive medicine support server according to claim 1, characterized in that, Includes a prescription section, which is configured as follows: Obtain information related to the patient's prescription drugs and prescription dates; If information related to the patient's next appointment date is obtained, output information indicating that the prescription drug will be prescribed each day from the prescription date to a specified date determined based on the next appointment date; Without obtaining information related to the patient's next appointment date, output information indicating that the prescription drug will be prescribed for each of the specified number of days from the date of prescription.

6. The reproductive medicine support server according to claim 5, characterized in that, The acquisition unit is configured to acquire information related to the patient's own medications and the quantity of those medications held, and the prescription unit outputs information indicating that the own medications are virtually prescribed as the prescription medication when the prescribed drug is the same as the patient's own medications.

7. The reproductive medicine support server according to claim 6, characterized in that, If the number of virtual prescriptions for the proprietary drug does not reach the required number of prescriptions for the prescription drug or the number of proprietary drugs held, the prescription department outputs information indicating that the proprietary drug is virtually prescribed as the prescription drug.

8. The reproductive medicine support server according to claim 6, characterized in that, When the proprietary drug is virtually prescribed as the prescription drug, the prescription department outputs the quantity after subtracting the number of virtual prescriptions for the proprietary drug as the number of proprietary drugs held, and outputs the quantity of the prescribed prescriptions minus the number of virtual prescriptions for the proprietary drug as the actual number of drugs prescribed.

9. The reproductive medicine support server according to claim 1, characterized in that, include: The second prescription department, upon obtaining information related to the patient's treatment name and treatment date, outputs information indicating that one or more medications will be prescribed according to a pre-determined medication prescription schedule based on a correspondence established with the treatment name.

10. The reproductive medicine support server according to claim 1, characterized in that, include: The referral information output unit extracts information related to the treatment information provision form from the medical information and establishes a correspondence with the pre-prepared treatment information provision form before outputting it.

11. The reproductive medicine support server according to claim 1, characterized in that, include: The medical record information extraction unit, upon receiving instructions to copy medical record information, extracts information related to the prescribed medical record entries from the acquired medical information.

12. The reproductive medicine support server according to claim 1, characterized in that, include: When the consent form information management department receives information from the trainer's terminal indicating that a prescribed consent form will be obtained from the patient, it outputs the information indicating that the prescribed consent form will be obtained from the patient to the doctor's terminal.

13. The reproductive medicine support server according to claim 1, characterized in that, include: The semen evaluation unit, when the acquisition unit acquires information related to the semen analysis of the patient as the examination information, and If the information related to the semen analysis meets the prescribed criteria, information indicating that the patient's semen meets the prescribed criteria is output. If the information related to the semen analysis does not meet the specified criteria, information indicating that the patient's semen does not meet the specified criteria is output.

14. The reproductive medicine support server according to claim 1, characterized in that, include: The embryo classification department inputs images of the embryos of the assessment object from the medical information into the embryo assessment model, and classifies the embryos of the assessment object based on the assessment results output from the embryo assessment model; The embryo assessment model learns by taking the image of the embryo and related information as input data and information related to the establishment of pregnancy in the embryo as output data. The doctor terminal output section and the embryologist terminal output section are respectively configured to output the classification results of the embryos of the evaluation object classified by the embryo classification section to the doctor terminal or the embryologist terminal according to the requirements of the doctor terminal or the embryologist terminal.

15. A method for supporting reproductive medicine, characterized in that, The method is implemented by computer, which obtains treatment information related to the patient's treatment from the doctor's terminal as medical information, and outputs the obtained treatment information to the trainer's terminal.

16. A computer program product, characterized in that, The computer program product causes the computer to perform the method of claim 15.

Citation Information

Patent Citations

  • Fertilized egg quality evaluation system, information processor, information processing method and program

    JP2019076087A

  • Predicted value determination method, encoder, decoder, and computer storage medium

    JP2024050765A

  • Game machine

    JP2024111103A