Preconception health checkup system and server

Abstract

To provide a pre-conception medical checkup system and the like that can solve problems caused upon incorporating a pre-conception medical checkup into a work-site medical checkup.SOLUTION: A pre-conception medical checkup system 1 is composed of: a medical examinee terminal 2; an operation terminal 4; and a server 5 that is connected to the medical examinee terminal 2 and the operator terminal 4 via network 9. The server 5 comprises: registration means 6 that, in response to a request from the medical examinee terminal 2, gives a medical examinee identification number identifying a medical examinee to the medical examinee randomly without overlapping with the identification number given in the past to register the medical examinee; storage means 7 that stores medical checkup result information on the medical examinee in association with the medical examinee identification number; and providing means 8 that, in response to a request from the medical examinee terminal 2, retrieves the medical checkup result information from the storage means 7, and provides the medical checkup result information for the medical examinee terminal 2. The registration means 6 is configured to, when receiving the medical checkup result information from the operation terminal 4, cause the storage means 7 to store the medical checkup result information in association with the medical examinee identification number.SELECTED DRAWING: Figure 1

Description

[[Technical Field]]

[0001] The present invention relates to a preconception health examination system and the like for managing health examinations for preconception care. [[Background Art]]

[0002] Preconception care refers to the practice where women and couples address their own lifestyle and health while planning for future pregnancy. Preconception care is more effective when supported by medical evidence such as blood tests and interviews with physicians. However, for people of the appropriate age for preconception care, time cost and inconvenience act as barriers, making it difficult to undergo health examinations for preconception care (hereinafter referred to as "preconception health examinations"). Accordingly, the applicant of the present application has been conducting a demonstration project in cooperation with local governments, hospitals, etc., to incorporate preconception health examinations into occupational health examinations. If preconception health examinations can be incorporated into occupational health examinations, recipients of preconception health examinations can greatly reduce time cost and inconvenience.

[0003] On the other hand, when incorporating preconception health examinations into occupational health examinations, a computer system for managing preconception health examinations is desired. For example, Patent Document 1 discloses a health information management system that manages health information such as health examination results including stress checks. [[Prior Art Documents]] [[Patent Documents]]

[0004] [[Patent Document 1]] Japanese Patent No. 7429554 [[Summary of the Invention]] [[Problem to be Solved by the Invention]]

[0005] However, conventional management systems including that disclosed in Patent Document 1 have not been able to solve problems unique to preconception health examinations.

[0006] This invention has been made in view of the aforementioned problems, and its purpose is to provide a preconception health check system, etc., that can solve the problems when incorporating preconception health checks into occupational health examinations. [Means for solving the problem]

[0007] The first invention for achieving the aforementioned objective is a pre-con health check system comprising a patient terminal which is the terminal of a patient undergoing a pre-con health check, an operator terminal which is the terminal of the operator of the pre-con health check, and a server connected to the patient terminal and the operator terminal via a network, wherein the server includes a registration means for registering the patient by assigning a patient identification number to the patient randomly and not overlapping with any previously assigned numbers in response to a request from the patient terminal, a storage means for storing the patient's health check result information in association with the patient identification number, and a provision means for retrieving the health check result information from the storage means and providing the health check result information to the patient terminal in response to a request from the patient terminal, wherein when the registration means receives the health check result information from the operator terminal, it stores the health check result information in the storage means in association with the patient identification number. The storage means further stores a management table containing management information for the pre-con health checkup for each patient identification number, the management table includes a video viewing flag indicating whether the patient has viewed a video related to the pre-con health checkup, the registration means further updates the video viewing flag to "viewed" when it receives information from the patient terminal indicating that the patient has viewed the video, the providing means provides the patient terminal with a personal page for each patient on which buttons related to tasks to be performed by the patient before the pre-con health checkup are placed, the selection of buttons related to tasks to be performed by the patient before the pre-con health checkup is enabled when the video viewing flag is "viewed", and the selection of buttons related to tasks to be performed by the patient before the pre-con health checkup is disabled when the video viewing flag is "not viewed". This is a pre-confirmation health check system characterized by the following: The first invention allows for the management of patient information with external organizations using only patient identification numbers without using personal information, thereby suppressing errors due to human error. Furthermore, patients can check their pre-confirmation health check results without their employer knowing they have undergone the check. Furthermore, it avoids wasting valuable daytime time for those in the age group eligible for preconception care, while enhancing the effectiveness of preconception checkups and preventing unnecessary problems.

[0008] In the first invention The providing means provides the recipient's terminal with a personal page for each recipient on which a button for issuing a certificate proving that the video has been viewed is located, and allows the selection of the issuance button when the video viewing flag indicates that the video has been viewed, and does not allow the selection of the issuance button when the video viewing flag indicates that the video has not been viewed. You can do that.

[0009] Furthermore, in the first invention The management table further includes: the health check date, which is the date the pre-con health check was taken; a questionnaire completion flag indicating whether the patient has completed the pre-con health check questionnaire; a pre-check questionnaire response flag indicating whether the patient has answered the pre-check questionnaire; a post-check questionnaire response flag indicating whether the patient has answered the post-check questionnaire; the health check result upload date, which is the date the patient's health check result file was uploaded; and whether an interview is required for the patient. The means of providing the patient includes whether a doctor's consultation is necessary, which indicates the doctor's judgment result, and further provides the patient's terminal with a personal page for each patient, which includes a pre-health checkup task display area, a health checkup day task display area, and a health checkup post-health checkup task display area, and sets whether the buttons placed in the pre-health checkup task display area, the health checkup day task display area, and the health checkup post-health checkup task display area can be pressed according to the health checkup date, the questionnaire completion flag, the pre-health checkup questionnaire response flag, the post-health checkup questionnaire response flag, the health checkup result upload date, and whether a doctor's consultation is necessary. You can do that.

[0010] Furthermore, in the first invention The management table further includes physician comments on the health checkup results information, and the provisioning means sets whether or not the patient can view the health checkup results information depending on whether or not the physician comments are NULL. You can do that.

[0011] The second invention relates to a server connected via a network to a patient terminal, which is the terminal of a patient undergoing a pre-con health checkup, and an operator terminal, which is the terminal of the operator of the pre-con health checkup, and includes: a registration means that, in response to a request from the patient terminal, assigns a patient identification number to the patient randomly, which does not overlap with any previously assigned numbers, and registers the patient; a storage means that stores the patient's health checkup result information in association with the patient identification number; and a provision means that, in response to a request from the patient terminal, retrieves the health checkup result information from the storage means and provides the health checkup result information to the patient terminal, wherein when the registration means receives the health checkup result information from the operator terminal, it stores the health checkup result information in the storage means in association with the patient identification number. The storage means further stores a management table containing management information for the pre-con health checkup for each patient identification number, the management table includes a video viewing flag indicating whether the patient has viewed a video related to the pre-con health checkup, the registration means further updates the video viewing flag to "viewed" when it receives information from the patient terminal indicating that the patient has viewed the video, the providing means provides the patient terminal with a personal page for each patient on which buttons related to tasks to be performed by the patient before the pre-con health checkup are placed, the selection of buttons related to tasks to be performed by the patient before the pre-con health checkup is enabled when the video viewing flag is "viewed", and the selection of buttons related to tasks to be performed by the patient before the pre-con health checkup is disabled when the video viewing flag is "not viewed". This server is characterized by the following: The second invention makes it possible to suppress the occurrence of errors due to human error when exchanging patient information with external organizations, even if the information is managed using only the patient identification number without using personal information. In addition, patients can check their health check results without their affiliated company knowing that they have undergone a pre-con health check. Furthermore, it avoids wasting valuable daytime time for those in the age group eligible for preconception care, while enhancing the effectiveness of preconception checkups and preventing unnecessary problems. [Effects of the Invention]

[0012] The present invention provides a preconception health check system and the like that can solve the problems that arise when incorporating preconception health checks into occupational health examinations. [Brief explanation of the drawing]

[0013] [Figure 1] Diagram showing an overview of the pre-con health checkup system. [Figure 2] This diagram shows an example of a table stored by the server's storage device. [Figure 3] Flowchart showing the process of registering patient information [Figure 4] A diagram showing an example of a patient information registration screen. [Figure 5] Flowchart showing the management process flow for pre-health checkup tasks. [Figure 6]Figure showing an example of My Page before viewing a video [Figure 7] Figure showing an example of My Page after viewing a video [Figure 8] Figure showing an example of an operator screen [Figure 9] Flowchart showing the flow of medical check-up result registration processing [Figure 10] Flowchart showing the flow of doctor's comment registration processing [Figure 11] Figure showing an example of a doctor's screen [Figure 12] Figure showing an example of a medical check-up result screen in preview mode [Figure 13] Flowchart showing the flow of medical check-up result display processing [Figure 14] Figure showing an example of My Page after a medical check-up [Figure 15] Figure showing an example of a medical check-up result screen in disclosure mode

Mode for Carrying Out the Invention

[0014] The preconception check-up system according to an embodiment of the present invention is a computer system that manages information on preconception check-ups when incorporating health check-ups for preconception care (=preconception check-ups) into occupational health check-ups. The users of the preconception check-up system are examinees who undergo preconception check-ups, doctors who diagnose the examinees, and operators who administer the preconception check-ups.

[0015] Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram showing an outline of the preconception check-up system. As shown in FIG. 1, the preconception check-up system 1 includes an examinee terminal 2 which is a terminal for an examinee undergoing the preconception check-up, a doctor terminal 3 which is a terminal for a doctor who diagnoses the examinee, an operator terminal 4 which is a terminal for an operator of the preconception check-up, and a server 5. The server 5 is connected to the examinee terminal 2, the doctor terminal 3, and the operator terminal 4 via a network 9.

[0016] The patient terminal 2, physician terminal 3, operator terminal 4, and server 5 are equipped with a CPU (Central Processing Unit) as the control unit, memory as the main memory unit, HDD (Hard Disk Drive) and flash memory as auxiliary memory units, an LCD display as the display unit, a keyboard, mouse, and touch panel as input units, a LAN (Local Area Network) cable and wireless module as communication units, and a camera as a barcode reader unit.

[0017] The auxiliary storage unit stores the OS (Operating System), application programs, and data necessary for processing. The control unit reads the OS and application programs from the auxiliary storage unit and stores them in the main memory. While accessing the main memory, it controls other devices and performs the information processing described later.

[0018] The patient terminal 2, the doctor terminal 3, and the operator terminal 4 are, for example, tablet devices, smartphones, notebook PCs (abbreviation for "Personal Computer"), desktop PCs, etc. The server 5 is, for example, a server computer installed in a data center, etc., or a virtual server provided as a cloud service, etc., and may be implemented in a single chassis or in multiple chassis. The network 9 is, for example, the internet.

[0019] The auxiliary storage units of the patient terminal 2, the physician terminal 3, and the operator terminal 4 are equipped with computer programs that provide the function of browsing internet websites, i.e., web browsers. In addition, the auxiliary storage unit of server 5 is equipped with computer programs that allow server 5 to perform the information processing described later. The computer programs installed in the auxiliary storage unit of server 5 include programs that allow server 5 to function as a web server, programs that allow server 5 to function as a database management system, and application programs that allow server 5 to perform information processing specific to the embodiments of the present invention.

[0020] Server 5 has the configuration shown in Figure 1 through the cooperation of software and hardware resources. Specifically, Server 5 includes a registration means 6 that, in response to a request from the patient terminal 2, randomly assigns a patient identification number to identify the patient, which does not overlap with any previously assigned numbers, and registers the patient; a storage means 7 that stores the patient's health check result information in association with the patient identification number; and a provision means 8 that, in response to a request from the patient terminal 2, retrieves the health check result information from the storage means 7 and provides the health check result information to the patient terminal 2. When the registration means 6 receives the health check result information from the operator terminal 4, it stores the health check result information in the storage means 7 in association with the patient identification number.

[0021] The health checkup results information includes at least the results of tests specific to pre-con health checkups, such as blood tests, or the results of completing a questionnaire specific to pre-con health checkups. In other words, the health checkup results information may consist of only the results of tests such as blood tests, only the results of completing a questionnaire, or both.

[0022] Figure 2 shows an example of a table stored by the server's storage means. The storage means 7 manages each of the tables shown in Figure 2 as a relational database. Only the main tables are shown in Figure 2; the storage means 7 also stores other tables as needed.

[0023] The patient table 10 shown in Figure 2(a) is a table that stores patient information. The patient table 10 includes data items from data ID 11 to email address authentication flag 16. Data ID 11 uniquely identifies the data in patient table 10. Gender 12 and date of birth 13 are the patient's personal information. Email address 14 and password 15 are used as login information for the patient to log in to the system. The email address authentication flag 16 indicates whether the patient's email address has been authenticated or not.

[0024] The management table 20 shown in Figure 2(b) is a table that stores management information for pre-confirmation health checks for each patient. The management table 20 contains data items from data ID 21 to registration date 42. Data ID 21 uniquely identifies the data in management table 20. Data ID 21 has a one-to-one correspondence with data ID 11 in patient table 10. Patient identification number 22 uniquely identifies the patient. Patient identification number 22 is assigned during the registration process for the patient.

[0025] Year 23 is the year in which the examinee underwent the pre-conception health checkup. Name 24, address 25, and telephone number 26 are the examinee's personal information. Company number 27 uniquely identifies the company to which the examinee belongs. The explanatory video viewing flag 28 and the e-learning viewing flag 29 indicate whether the examinee watched the explanatory video about the pre-conception health checkup and whether the examinee watched the e-learning video about the pre-conception health checkup, respectively.

[0026] The health check date 30 is the date the pre-health checkup was received (= the date the occupational health checkup was received). The questionnaire completion flag 31, the pre-health checkup questionnaire response flag 32, and the post-health checkup questionnaire response flag 33 indicate whether the examinee completed the pre-health checkup questionnaire, whether the examinee answered the pre-health checkup questionnaire, and whether the examinee answered the post-health checkup questionnaire, respectively. The questionnaire file path 34 uniquely identifies the location on the storage means 7 where the questionnaire file is stored. The health checkup result file path 35 uniquely identifies the location on the storage means 7 where the health checkup result file is stored. The health checkup result upload date 36 is the date the health checkup result file was uploaded.

[0027] The "Doctor Consultation Necessity" field (37) indicates the doctor's decision on whether or not a consultation is necessary for the patient. The "Doctor's Comment" field (38) contains the doctor's comments on the health checkup results. The "Doctor's Comment Draft" field (39) contains a draft of the doctor's comments for the patient. The "Doctor Consultation URL" field (40) is the URL of the web conferencing system used for the consultation with the doctor. The "Doctor Consultation Completion Flag" field (41) indicates whether or not the consultation with the doctor has been completed. The "Registration Date" field (42) is the date the patient was officially registered.

[0028] The physician / administrator table 50 shown in Figure 2(c) is a table that manages information about physicians and administrators. The physician / administrator table 50 includes data items from data ID 51 to affiliated medical institution 56. Data ID 51 uniquely identifies the data in the physician / administrator table 50. Login ID 52 and password 53 are used as login information for physicians or administrators to log in to the system. Name 54 is the name of the physician or administrator.

[0029] User type 55 distinguishes between physicians, staff members who are members of the operator, and administrators who are members of the operator. Physicians can view the physician screen shown in Figure 11, but cannot view patients' personal information. Staff members can view the operator screen shown in Figure 8, but cannot view patients' personal information. Administrators can view the operator screen and can view patients' personal information. Affiliated medical institution 56 indicates the medical institution to which the physician belongs.

[0030] The company table 60 shown in Figure 2(d) is a table that manages information about the company to which each patient belongs. The company table 60 includes data items from data ID 61 to attending physician 64. Data ID 61 uniquely identifies the data in the company table 60. Company ID 62 uniquely identifies the company. Company name 63 is the name of the company. Attending physician 64 indicates the physician in charge of patients belonging to that company. The attending physician 64 is registered with data ID 51 from the physician / operator table 50. There may be one physician assigned to each company, or there may be multiple physicians. Also, a physician may be in charge of only one company, or they may be in charge of multiple companies. In addition, the company table 60 may include specific email addresses of departments such as the general affairs department or human resources department of each company.

[0031] Figure 3 is a flowchart showing the flow of the patient information registration process. In each step shown in Figure 3, the control units of the patient terminal 2 and the server 5 communicate with each other while executing the process.

[0032] In the embodiments of the present invention, the pre-con health checkup is an optional examination and consultation with a doctor that is available to those who wish to participate in the occupational health checkup. Companies distribute flyers to their employees that include information about the pre-con health checkup along with information about the occupational health checkup. The flyer contains a two-dimensional barcode that shows the URL of the patient information registration screen shown in Figure 4.

[0033] As shown in Figure 3, the patient terminal 2 reads the two-dimensional barcode (step S1) and requests the server 5 to provide the patient information registration screen corresponding to the URL associated with the two-dimensional barcode (step S2). Upon receiving the request from the patient terminal 2, the server 5 provides the patient information registration screen data to the patient terminal 2 (step S3). The patient terminal 2 displays the patient information registration screen data received from the server 5 (step S4). Note that access to the patient information registration screen is not limited to reading the two-dimensional barcode; it may also be accessed by clicking a link in an email or by directly entering the URL into a web browser.

[0034] Figure 4 shows an example of a patient information registration screen. In Figure 4, buttons shown with solid lines are clickable, while those shown with dotted lines are not clickable. The same applies to other screens shown in subsequent diagrams.

[0035] The patient information registration screen 70 is an input form for registering the information of patients who wish to undergo a pre-confirmation health checkup. The patient information registration screen 70 includes text boxes for email address 71 to health checkup date 79, a link 80 to the personal information handling screen, a consent button 81, and an application button 82. In Figure 4, the consent button 81 and the application button 82 are shown with dotted lines, indicating that they are not clickable.

[0036] Patient terminal 2 accepts input for the patient information registration screen 70, including email address 71, password 72, name 73, date of birth 74, gender 75, address 76, telephone number 77, company number 78, and health check date 79. For name 73, both kanji and furigana input may be accepted, or the last name and first name may be entered separately. For company number 78, for example, it may be listed on a flyer distributed in advance, or it may be selected from a list of company names. Health check date 79 is not a required field, and input may be accepted only from those whose schedule has already been decided.

[0037] Next, the patient terminal 2 accepts the click of the link 80 to the personal information handling screen and requests the personal information handling screen (not shown) from the server 5. When the server 5 receives the request from the patient terminal 2, it provides the data of the personal information handling screen to the patient terminal 2. For example, when the personal information handling screen is scrolled to the bottom, the consent button 81 becomes clickable. Next, the patient terminal 2 accepts the click of the consent button 81. This makes it possible to click the application button 82. Then, the patient terminal 2 accepts the click of the application button 82 and requests the server 5 to provisionally register the patient information (step S5). When the server 5 receives the request from the patient terminal 2, it performs the provisional registration of the patient information (step S6).

[0038] In the provisional registration of patient information, server 5 adds new data to patient table 10 and registers the email address 71, password 72, date of birth 74, and gender 75 entered on the patient information registration screen 70 in Figure 4 to the email address 14, password 15, date of birth 13, and gender 12 in patient table 10. In addition, server 5 adds new data to management table 20 and registers the name 73, address 76, telephone number 77, and company number 78 entered on the patient information registration screen 70 in Figure 4 to the name 24, address 25, telephone number 26, and company number 27 in management table 20.

[0039] Returning to the explanation of Figure 3, Server 5 sends an authentication email to email address 14 in the recipient table 10 to confirm that the email address is correct (Step S7). The recipient terminal 2 accepts the click of the authentication confirmation URL included in the authentication email and requests Server 5 to complete the registration of the recipient information (Step S8). Upon receiving the request from the recipient terminal 2, Server 5 performs the registration of the recipient information (Step S9).

[0040] During the final registration of patient information, Server 5 updates the email address authentication flag 16 in the patient table 10 to authenticated. Server 5 also assigns a patient identification number and registers it in the patient identification number 22 of the management table. Specifically, Server 5 assigns patient identification numbers randomly and without duplication with those previously assigned, when registering patients. For example, Server 5 generates a pseudo-random number within a predetermined range (e.g., 0 to 99999999) using the current time as a random number seed, and checks whether the generated pseudo-random number is already registered in the patient identification number 22 of the management table. If it is not registered, Server 5 assigns the generated pseudo-random number as the patient identification number and registers it in the patient identification number 22 of the management table. If it is already registered, Server 5 generates a pseudo-random number that is not yet registered in the patient identification number 22 of the management table and repeats the same process until it is registered in the patient identification number 22 of the management table. Then, once the registration of patient identification number 22 in the management table is complete, server 5 sends a registration completion email to email address 14 in patient table 10 to indicate that the registration has been completed.

[0041] Here, we will explain the significance of randomly assigning patient identification numbers. Unlike workplace health examinations, which are legally mandated, pre-conception health checkups, which are not legally required, require confidentiality not only for the diagnostic results but also for information on who underwent the checkup. Therefore, in the embodiment of the present invention, when exchanging patient information with external organizations, it is managed by patient identification numbers to conceal information on who underwent the pre-conception health checkup. For example, the test result data received from external health examination organizations is identified by the patient identification number.

[0042] However, with this management method, there is no way to verify the accuracy of the correspondence between patient identification numbers and test results. If patient identification numbers are assigned sequentially, for example, even if the ones digit is incorrectly assigned, there is a high probability that the incorrect number has been assigned to someone else, so server 5 will link the test result data to that person. On the other hand, if patient identification numbers are assigned randomly, the possibility of an incorrect number being assigned to someone else is low, so server 5 will determine that "the patient identification number does not exist" and avoid linking the test result to someone else through error handling. In other words, by assigning patient identification numbers randomly, the occurrence of mix-ups due to human error can be suppressed.

[0043] Furthermore, the pre-confirmation health checkup is still in the research stage, and it is expected that the health checkup results will be used for research purposes with the consent of the examinees. By assigning random examinee identification numbers, it is possible to reduce the occurrence of human error and mix-ups when using the health checkup results data for research purposes.

[0044] Furthermore, instead of requiring the user to enter a password on the patient information registration screen 70, the server 5 may automatically assign an initial password. In the latter case, the server 5 will issue an initial password during the main registration of the patient information, register it in the password 15 field of the patient table 10, and send the initial password along with the registration completion email.

[0045] Figure 5 is a flowchart showing the management process flow for pre-health checkup tasks. In each step shown in Figure 5, the control unit of the patient terminal 2 or operator terminal 4 and the control unit of the server 5 communicate with each other to execute the process.

[0046] As shown in Figure 5, the recipient terminal 2 accepts the input of the email address and password required for login, sends the email address and password to the server 5, and requests access to the My Page (step S11). When the server 5 receives the request from the recipient terminal 2, including the email address and password, it searches the recipient table 10 and performs login authentication. If the login authentication is successful, the server 5 sends the My Page data to the recipient terminal 2 (step S12). The recipient terminal 2 displays the My Page data received from the server 5 (step S13).

[0047] Figure 6 shows an example of a My Page before watching a video. My Page 100 contains management information for each patient's pre-checkup and has a health checkup explanation video button 101, an e-learning button 102, an online consultation button 103, an inquiry button 104, a status display area 105, a pre-checkup task display area 110, a health checkup day task display area 120, a post-checkup task display area 130, and a health checkup follow-up service display area 140.

[0048] The health check explanation video button 101 is for playing the pre-con health check explanation video (not shown). The e-learning button 102 is for playing the pre-con health check e-learning video (not shown). The online consultation button 103 is for starting the web conferencing system (not shown) for online consultations with doctors. The inquiry button 104 is for displaying the inquiry form (not shown) for the operator.

[0049] Status display area 105 is an area that displays the current status of the pre-checkup. For example, when the pre-checkup work is completed, a check mark will be displayed instead of the number "1" indicating the pre-checkup work.

[0050] The pre-health checkup work display area 110 is an area that displays the content of the pre-health checkup work and includes three buttons and three display items. The questionnaire entry button 111 is a button to start filling out the questionnaire (not shown). The pre-health checkup survey response button 112 is a button to start answering the pre-health checkup survey (not shown). The health checkup date entry button 113 is a button to display the health checkup date entry screen (not shown). The questionnaire entry status 114 indicates whether the questionnaire is not filled out or has been filled out. The pre-health checkup survey response status 115 indicates whether the pre-health checkup survey has not been answered or has been answered. The health checkup date entry status 116 indicates whether the health checkup date has not been entered or, if entered, the date.

[0051] The health check day task display area 120 is an area that displays the details of the tasks to be performed on the day of the health check. The post-health check task display area 130 is an area that displays the details of the tasks to be performed after the health check, and includes three buttons and one display item. The health check result display button 131 is a button for displaying the health check result screen in disclosure mode (Figure 15). The online consultation reservation button 132 is a button for displaying the online consultation reservation screen with a doctor (not shown). The post-health check questionnaire response button 133 is a button for starting to answer the post-health check questionnaire (not shown). The post-health check questionnaire response status 134 indicates whether the post-health check questionnaire has been answered or not.

[0052] The health checkup follow-up service display area 140 is an area that displays the content of the health checkup follow-up service and includes three buttons. The linked service button 141 is a button for displaying a screen (not shown) that contains information on services linked with Precon Health Checkup, such as egg freezing and storage services. The expert consultation button 142 is a button for displaying a screen (not shown) that contains information on experts such as infertility treatment and mental health. The regional partner hospital button 143 is a button for displaying a screen (not shown) that contains information on regional hospitals linked with Precon Health Checkup.

[0053] Returning to the explanation of Figure 5, next, the patient terminal 2 performs the process of viewing the explanatory video (step S14). Specifically, when the patient terminal 2 receives a press of the health check explanatory video button 101, it requests the web page for the pre-con health check explanatory video and sends information to the server 5 indicating that the patient has viewed the explanatory video. When the server 5 receives this information from the patient terminal 2, it updates the explanatory video viewing flag 28 in the management table 20 to "viewed" (step S15). Note that the patient terminal 2 may also send information to the server 5 indicating that the patient has viewed the explanatory video not at the time the press of the health check explanatory video button 101 is received, but after the patient has viewed the explanatory video and answered a questionnaire or short test (not shown) related to the explanatory video.

[0054] Patient terminal 2 executes the e-learning viewing process (step S16). Specifically, when patient terminal 2 receives a press of the e-learning button 102, it requests the webpage for the pre-confirmation health check e-learning and sends information to server 5 indicating that the patient has viewed the e-learning. When server 5 receives this information from patient terminal 2, it updates the e-learning viewing flag 29 in management table 20 to "viewed" (step S17). Alternatively, patient terminal 2 may send information to server 5 indicating that the patient has viewed the e-learning not at the time the press of the e-learning button 102 is received, but after the patient has viewed the e-learning and answered a questionnaire or quiz (not shown) related to the e-learning.

[0055] When Server 5 provides the patient terminal 2 with My Page in response to a request from the patient terminal 2, if the video viewing flag (=explanatory video viewing flag 28 and e-learning viewing flag 29 in management table 20) is set to "viewed," Server 5 allows the patient to select buttons related to tasks to be performed before the health checkup (=questionnaire completion button 111, pre-health checkup questionnaire answering button 112, health checkup date entry button 113, etc.). Conversely, if the video viewing flag is set to "not viewed," Server 5 does not allow the patient to select buttons related to tasks to be performed before the health checkup. Note that the videos that must be viewed before starting pre-health checkup tasks may be either the explanatory video or the e-learning video, or a combination of videos, and can be selected as appropriate.

[0056] Figure 7 shows an example of the My Page after watching a video. Comparing Figure 6 and Figure 7, the questionnaire entry button 111, the pre-health checkup questionnaire answer button 112, and the health checkup date entry button 113 are not clickable in Figure 6, but are clickable in Figure 7. This allows the Precon Health Checkup System 1 to make watching explanatory videos about the Precon Health Checkup and e-learning materials for learning medical knowledge a mandatory condition for starting pre-health checkup work. In addition, for example, a button (not shown) for issuing a certificate proving that the video has been watched may be placed on the My Page. In this case, the server 5 may allow the selection of the certificate issuance button if the video viewing flag is set to "watched," and may not allow the selection of the certificate issuance button if the video viewing flag is set to "not watched."

[0057] Preconception checkups are still in the early stages of adoption, and most participants lack medical knowledge. However, without a certain level of medical knowledge, preconception checkups are less effective, and problems due to a lack of understanding are more likely to occur. In the embodiment of this invention, viewing explanatory videos about preconception checkups and e-learning materials to learn medical knowledge is mandatory before starting pre-checkup procedures, thereby enhancing the effectiveness of preconception checkups and avoiding unnecessary problems. Furthermore, instead of receiving explanations at the workplace health checkup venue, participants can watch the videos at their own convenience at home, thus avoiding the consumption of valuable daytime time for those in the age group eligible for preconception care.

[0058] Returning to the explanation of Figure 5, next, the patient terminal 2 performs the questionnaire completion process (step S16). Specifically, when the patient terminal 2 receives a press of the questionnaire completion button 111 on My Page 100, it requests a questionnaire completion web page from Server 5 or an external server (not shown), receives the questionnaire completion web page from Server 5 or the external server, and displays the questionnaire completion web page. Then, the patient terminal 2 accepts completion of the questionnaire on the questionnaire completion web page. If Server 5 provides the questionnaire completion web page, Server 5 receives the questionnaire file from the patient terminal 2, saves the questionnaire file to a designated folder, and registers the file path in the questionnaire file path 34 of the management table 20.

[0059] Assuming that the questionnaire will differ depending on the health checkup institution or medical institution conducting the pre-confirmation health checkup, it is possible to provide a web page for filling out the questionnaire not only on server 5 but also on an external server. In this case, once the questionnaire is completed, the external server or the patient terminal 2 will send an email to, for example, the email address of the operator of the pre-confirmation health checkup system 1 indicating that the questionnaire has been completed. Upon checking the email, the operator logs into operator terminal 4 and notifies server 5 from the operator screen that the questionnaire has been completed.

[0060] The operator terminal 4 accepts the login ID and password required by the operator to log in, sends the login ID and password to the server 5, and requests the operator screen (step S19). When the server 5 receives the request from the operator terminal 4, including the login ID and password, it searches the physician / operator table 50 and performs login authentication. If the login authentication is successful, the server 5 provides the operator screen data to the operator terminal 4 (step S20). The operator terminal 4 displays the operator screen data received from the server 5 (step S21).

[0061] Figure 8 shows an example of the administrator screen. The administrator has permission to view the home screen, the screen for viewing the list of patients, the screen for viewing notifications, and the screen for viewing various settings. Hereafter, administrator screen 200 refers to the screen for viewing the list of patients.

[0062] The operator screen 200 has text boxes for entering search criteria for patients, including year 201, patient identification number 202, company number 203, email address 204, and name 205. The operator screen 200 also has a reset button 206 for instructing the reset of search criteria, a search button 207 for instructing the execution of a search, and a patient list 210 as a list for displaying the search results for patients.

[0063] The patient list 210 has display items from registration date 211 to personal information 224. Registration date 211, patient identification number 212, affiliated company number 213, and health check date 214 display registration date 42, patient identification number 22, affiliated company number 27, and health check date 30 from management table 20, respectively.

[0064] The medical questionnaire 215 displays an editable checkbox 225. If the medical questionnaire completion flag 31 is not filled in, the checkbox 225 is initially displayed as off (only a rectangular shape is shown), and if it is filled in, it is initially displayed as on (a check mark is included within the rectangular shape). Details regarding what happens when checkbox 225 is pressed will be described later with reference to Figure 5.

[0065] Before the questionnaire 216, a checkbox 226 will be displayed as editable. Checkbox 226 is initially displayed as "off" if the pre-health check questionnaire response flag 32 has not been answered, and as "on" if it has been answered. Details regarding what happens when checkbox 226 is clicked will be described later, referring to Figure 5.

[0066] After the survey 217, checkbox 227 will be displayed as editable. Checkbox 227 is initially displayed as "off" if the post-health checkup survey response flag 33 has not been answered, and as "on" if it has been answered. When the operator terminal 4 receives a click on checkbox 227 while it is in the "off" state, it sends information to the server 5 indicating that the examinee has answered the post-health checkup survey for the pre-checkup. When the server 5 receives this information from the operator terminal 4, it updates the post-health checkup survey response flag 33 to "answered".

[0067] The result upload 218 displays the upload button 228 and the health check result upload date 36. Details regarding what happens when the upload button 228 is pressed will be described later, referring to Figure 9.

[0068] The result disclosure status 219 displays "Not Disclosed" if the physician comment 38 is NULL (= no data), and "Disclosed" if the physician comment 38 is not NULL. The result disclosure status 219 also displays a preview button 229. When the operator terminal 4 receives a press of the preview button 229, it sends the patient identification number 212 to the server 5 and requests the health checkup results screen in preview mode (Figure 12). The server 5 searches the management table 20 using the patient identification number 212 and sends the file data of the health checkup results file path 35 and the physician comment draft 39 to the operator terminal 4. The operator terminal 4 then displays the file data of the health checkup results file path 35 and the physician comment draft 39.

[0069] For Doctor's Comment 220, "Not filled in" is displayed if Doctor's Comment 38 and Doctor's Comment Draft 39 are NULL; "Draft" is displayed if Doctor's Comment 38 is NULL and Doctor's Comment Draft 39 is not NULL; and "Disclosed" is displayed if Doctor's Comment 38 is not NULL. For Interview Status 221, the information from Doctor Interview Requirement Status 37 is displayed.

[0070] The interview URL 222 displays an edit button 230. When the operator terminal 4 receives a press of the edit button 230, it displays a URL editing screen (not shown). Then, when the operator terminal 4 receives a URL input on the URL editing screen, it sends the URL to the server 5. When the server 5 receives the URL, it registers the URL in the doctor interview URL 40.

[0071] When the interview is completed (223), the checkbox 231 becomes editable. The checkbox 231 is initially displayed as "off" if the doctor interview completion flag 41 is not yet completed, and as "on" if it is completed. When the operator terminal 4 receives a click on the checkbox 231 while it is in the "off" state, it sends information to the server 5 indicating that the patient has completed the doctor interview. When the server 5 receives this information from the operator terminal 4, it updates the doctor interview completion flag 41 to "completed".

[0072] A confirmation button 232 is displayed for the personal information 224. When the server 5 provides the data from the operator screen 200 to the operator terminal 4, it sets the confirmation button 232 to either be pressable or not pressable depending on the user type 55 in the management table 20. Specifically, the server 5 sets the confirmation button 232 to be pressable if the user type 55 is an administrator, and sets it to not be pressable if the user type 55 is a staff member. This ensures that only administrators (e.g., personal information protection managers) among the operators can view the patient's personal information, and that other staff members cannot view the patient's personal information, providing a systemic guarantee.

[0073] Furthermore, server 5 may be configured to either display or hide the display items of personal information 224 depending on the user type 55 in management table 20. Specifically, if user type 55 is an administrator, server 5 may provide the operator terminal 4 with the operator screen 200 data including personal information 224 in a display state where the confirmation button 232 can be pressed. If user type 55 is a staff member, server 5 may provide the operator terminal 4 with the operator screen 200 data without personal information 224. This makes it possible to keep the fact that personal information is stored in the system a secret from the staff.

[0074] In the operator screen 200 of Figure 8, one search result obtained using the search criteria of "2023" for year 201 and "94372518" for patient identification number 202 is displayed in the patient list 210.

[0075] Returning to the explanation of Figure 5, when the operator terminal 4 receives a press while the checkbox 225 on the operator screen 200 is unchecked, it sends information to the server 5 indicating that the patient has completed the pre-confirmation health check questionnaire and requests that the questionnaire be updated to "completed" (step S22). When the server 5 receives this information from the operator terminal 4, it updates the questionnaire completion flag 31 in the management table 20 to "completed" (step S23).

[0076] Next, the patient terminal 2 executes the questionnaire response process (step S16). Specifically, when the patient terminal 2 receives a press of the pre-health check questionnaire response button 112 on My Page 100, it requests the pre-health check questionnaire response web page from Server 5 or an external server (not shown), receives the pre-health check questionnaire response web page from Server 5 or the external server, and displays the pre-health check questionnaire response web page. Then, the patient terminal 2 accepts the response to the pre-health check questionnaire on the pre-health check questionnaire response web page.

[0077] Assuming that the pre-health check questionnaire will differ depending on the municipality supporting the pre-confirmation health check, it is possible to provide the web page for answering the pre-health check questionnaire not only through server 5 but also through an external server. In this case, once the pre-health check questionnaire is completed, the external server or the patient terminal 2 will send an email to, for example, the email address of the operator of the pre-confirmation health check system 1 indicating that the pre-health check questionnaire has been completed. Upon checking the email, the operator logs into operator terminal 4 and notifies server 5 from the operator screen that the pre-health check questionnaire has been completed.

[0078] The operator terminal 4 and server 5 perform the operator login authentication process and the operator screen display process in the same manner as in steps S19 to S21 (steps S25 to S27). When operator terminal 4 receives a press while checkbox 226 on operator screen 200 is unchecked, it sends information to server 5 indicating that the examinee has answered the pre-examination questionnaire for the pre-checkup health checkup and requests that the pre-examination questionnaire be updated to "answered" (step S28). When server 5 receives this information from operator terminal 4, it updates the pre-examination questionnaire response flag 32 in management table 20 to "answered" (step S29).

[0079] Figure 9 is a flowchart showing the flow of the health check result registration process. As shown in Figure 9, the operator terminal 4 and server 5 perform the operator login authentication process and the display of the operator screen process, similar to steps S19 to S21 in Figure 5 (steps S31 to S33). Then, the operator terminal 4 performs the health check result upload process (step S34). Specifically, when the operator terminal 4 receives a press of the upload button 228 on the operator screen 200, it displays the upload screen (not shown). Then, when the operator terminal 4 receives the health check result information file on the upload screen, it sends the health check result information file to the server 5. When the server 5 receives the health check result information file from the operator terminal 4, it stores the health check result information file in a designated folder (step S35), registers the file path in the health check result file path 35 of the management table 20, and registers the current date in the health check result upload date 36 (step S36).

[0080] As mentioned above, information on who has undergone the pre-conventional health checkup is confidential. In particular, many examinees do not want their employers to know that they have undergone the pre-conventional health checkup. Therefore, server 5 receives the health checkup result information file from operator terminal 4 and stores the file in association with examinee identification number 22. As a result, the exchange of pre-conventional health checkup result information does not need to go through the employer, so examinees can check their pre-conventional health checkup results without their employers knowing that they have undergone the checkup.

[0081] Furthermore, some patients may want to share information with certain supervisors or the human resources department of their company, such as that they have undergone a pre-conception health check or that they are undergoing infertility treatment. In such cases, for example, server 5 may, in response to a request from patient terminal 2, send an email containing some of the pre-conception health check results, the doctor's comments, and any other information the patient wishes to share, to a specific email address. In this case, patient terminal 2 accepts input of the recipient's email address and the information to be sent via email, and sends it to server 5. Alternatively, the recipient's email address may be stored in advance in the storage means 7 of server 5.

[0082] Figure 10 is a flowchart showing the flow of the physician comment registration process. As shown in Figure 10, the physician terminal 3 accepts the input of the login ID and password required for the physician to log in, sends the login ID and password to the server 5, and requests the physician screen (step S41). When the server 5 receives the request from the physician terminal 3, including the login ID and password, it searches the physician / operator table 50 and performs login authentication. If the login authentication is successful, the server 5 sends the physician screen data to the physician terminal 3 (step S42). The physician terminal 3 displays the physician screen data received from the server 5 (step S43).

[0083] Figure 11 shows an example of a doctor's screen. Doctors have permission to display the home screen and the screen for viewing the list of patients. In the following, doctor's screen 300 refers to the screen for viewing the list of patients.

[0084] The physician screen 300 has text boxes for entering patient search criteria, including year 301, patient identification number 302, company number 303, email address 304, and name 305. The physician screen 300 also has a reset button 306 for instructing the reset of search criteria, a search button 307 for instructing the execution of a search, and a patient list 310 as a list for displaying the search results for patients.

[0085] The patient list 310 has display items from registration date 311 to interview completion date 319. Registration date 311, patient identification number 312, affiliated company number 313, and health check date 314 display registration date 42, patient identification number 22, affiliated company number 27, and health check date 30 from management table 20, respectively.

[0086] The Result Disclosure Status 315 displays "Not Disclosed" if the physician's comment 38 is NULL, and "Disclosed" if the physician's comment 38 is not NULL. Additionally, a preview button 320 is displayed in the Result Disclosure Status 315. Details regarding what happens when the preview button 320 is pressed will be described later, referring to Figure 12.

[0087] If physician comment 38 and physician comment draft 39 are NULL, "Not filled in" will be displayed for physician comment 316. If physician comment 38 is NULL and physician comment draft 39 is not NULL, "Draft" will be displayed. If physician comment 38 is not NULL, "Disclosed" will be displayed. For interview status 317, the information from physician interview necessity status 37 will be displayed.

[0088] The interview URL 318 displays an edit button 321. The details of what happens when the edit button 321 is pressed are the same as those for the edit button 230 on the operator screen 200. The interview completion 319 displays an editable checkbox 322. The details of what happens when the checkbox 322 is pressed are the same as those for the checkbox 231 on the operator screen 200.

[0089] Unlike the patient list 210 on the operator screen 200, the patient list 310 on the physician screen 300 does not include any fields for displaying personal information. This systemically ensures that physicians cannot view patients' personal information.

[0090] In the physician's screen 300 in Figure 11, one search result obtained using the search criteria of "2023" for year 201 and "94372518" for patient identification number 202 is displayed in the patient list 310.

[0091] Returning to the explanation of Figure 10, when the physician terminal 3 receives a press of the preview button 320 on the physician screen 300, it sends the patient identification number 312 to the server 5 and requests the health checkup results screen in preview mode (Figure 12) (step S44). The server 5 searches the management table 20 using the patient identification number 212 (step S45) and sends the file data of the health checkup results file path 35 and the physician comment draft 39 to the operator terminal 4 (step S46). The operator terminal 4 then displays the file data of the health checkup results file path 35 and the physician comment draft 39 on the health checkup results screen in preview mode (step S47).

[0092] Figure 12 shows an example of a health checkup results screen in preview mode. The health checkup results screen 400 in preview mode has a patient identification number 401, a year 402, a health checkup results display area 403, a checkbox 404 for entering whether an online consultation is necessary, a text box 405 for entering a doctor's comments, a save draft button 406, and a disclose button 407.

[0093] The health check result display area 403 displays the results of both the occupational health check and the pre-confirmation health check. Measurement values ​​outside the normal range are highlighted. In the example in Figure 12, the zinc measurement value is outside the normal range, so it is underlined and highlighted. Note that the method of highlighting is not limited to underlining; it is also possible to change the color, make it bold, or add a highlight mark, and is not particularly limited.

[0094] Returning to the explanation of Figure 10, the physician terminal 3 accepts the press of checkbox 404 and the press of either the save draft button 406 or the disclose button 407. When the physician terminal 3 accepts the press of either the save draft button 406 or the disclose button 407, it proceeds to step S48.

[0095] If the button is pressed to save as draft (save as draft in step S48), the physician terminal 3 sends the status of the checkbox 404 (=on or off) and the physician comment data entered in the text box 405 to the server 5 and requests that the physician comment be saved as a draft (step S49). When the server 5 receives the request to save as draft from the physician terminal 3, it updates the physician interview requirement 37 and physician comment draft 39 in the management table 20 (step S50). If the checkbox 404 is pressed, the server 5 updates the physician interview requirement 37 to required, and if the checkbox 404 is pressed, it updates the physician interview requirement 37 to unnecessary.

[0096] If the button is pressed to disclose (disclosure in step S48), the physician terminal 3 sends the data of the pressed state (=on or off) of checkbox 404 and the physician comment entered in text box 405 to the server 5, requesting disclosure of the physician comment (step S51). When the server 5 receives the disclosure request from the physician terminal 3, it updates the physician consultation requirement 37 and physician comment 38 in the management table 20 (step S52). If the pressed state of checkbox 404 is on, the server 5 updates the physician consultation requirement 37 to required, and if the pressed state of checkbox 404 is off, it updates the physician consultation requirement 37 to unnecessary. Once the physician comment 38 is updated and is no longer NULL, the patient can view the health check results.

[0097] Furthermore, while the above explanation assumed that the physician's comments were entered by the physician's terminal 3 from the physician, the server 5 may also update the physician's comments 38 or the draft physician's comments 39 based on the contents of the medical questionnaire or the measured values ​​of the tests. When updating the draft physician's comments 39, the physician's terminal 3 may accept modifications to the physician's comments as needed, as in Figure 10. For example, the storage means 7 of the server 5 may pre-store draft texts for each contents of the medical questionnaire or measured value of the tests, and the registration means 6 of the server 5 may search the storage means 7 for a draft text corresponding to the contents of the patient's medical questionnaire or measured value of the tests, and update the physician's comments 38 or the draft physician's comments 39. Alternatively, the registration means 6 of the server 5 may send a prompt to an external AI server (not shown) that includes the contents of the medical questionnaire or the patient's measured values ​​and an instruction to output a draft physician's comment appropriate to the measured values, and update the physician's comments 38 or the draft physician's comments 39 based on the draft text returned by the AI ​​server. In either case, the burden on the physician can be reduced.

[0098] Figure 13 is a flowchart showing the flow of the display process for health checkup results. The patient terminal 2 performs the process from patient login authentication to displaying the My Page, similar to steps S11 to S13 in Figure 5 (steps S61 to S63). Next, when the patient terminal 2 receives a press of the health checkup results display button 131 on My Page 100, it requests the health checkup results screen in disclosure mode (Figure 14) (step S64). The server 5 searches the management table 20 using the patient identification number of the logged-in patient (step S65) and sends the file data of the health checkup results file path 35 and the doctor's comments 38 to the patient terminal 2 (step S66). The patient terminal 2 then displays the file data of the health checkup results file path 35 and the doctor's comments 38 on the health checkup results screen in disclosure mode (step S67).

[0099] Figure 14 shows an example of a My Page after a health checkup. In the My Page 100 shown in Figure 14, since the current date has passed the health checkup date, check marks are displayed in the status display area 105 for Before Health Checkup, Health Checkup Day, and After Health Checkup. The Questionnaire Fill Button 111 and the Pre-Health Checkup Questionnaire Answer Button 112 are unavailable because they have been filled out and answered, respectively. The Health Checkup Date Entry Button 113 is unavailable because the current date has passed the health checkup date. The Health Checkup Results Display Button 131 is available because the health checkup results have been uploaded. The Online Consultation Reservation Button 132 is unavailable because a consultation with a doctor is not required. The Post-Health Checkup Questionnaire Answer Button 133 is available because the post-health checkup questionnaire has not yet been answered.

[0100] When the patient presses the health check results display button 131, the processes from steps S64 to S67 in Figure 13 are executed, and the health check results screen in disclosure mode is displayed on the patient terminal 2.

[0101] Figure 15 shows an example of a health checkup results screen in disclosure mode. The health checkup results screen 500 in disclosure mode has a patient identification number 501, a year 502, a health checkup results display area 503, and a physician's comment display area 504. The health checkup results screen 500 in disclosure mode allows patients to easily check the diagnostic results of their occupational health checkup and pre-conception health checkup, as well as physician's comments, at home.

[0102] As described above, the Precon Health Checkup System 1 in the embodiment of the present invention can solve the specific problems that arise when incorporating Precon health checkups into workplace health examinations. Firstly, the registration means 6 of the server 5 registers examinees by assigning examinee identification numbers randomly and without overlap with those previously assigned. This makes it possible to suppress the occurrence of errors due to human error when exchanging examinee information with external organizations, even if management is done using only the examinee identification number without using personal information. Furthermore, when the registration means 6 of the server 5 receives health checkup result information from the operator terminal 4, it stores the health checkup result information in the storage means 7 in association with the examinee identification number. This allows examinees to check their Precon health checkup result information without their company knowing that they have undergone a Precon health checkup.

[0103] Secondly, the storage means 7 of server 5 stores a physician / operator table 50 that includes user types 55 that distinguish between physicians, staff, and administrators. The provision means 8 of server 5 allows the display of the patient's personal information when user type 55 is an administrator, and does not allow the display of the patient's personal information when user type 55 is a physician or staff member. This systemically ensures that only administrators can view the patient's personal information, and that other staff and physicians cannot.

[0104] Thirdly, the storage means 7 of the server 5 stores a management table 20 that includes a video viewing flag (=explanatory video viewing flag 28 or e-learning viewing flag 29), and the registration means 6 of the server 5 updates the video viewing flag to "viewed" when it receives information from the patient terminal 2 indicating that the patient has viewed a video. For example, when the providing means 8 of the server 5 provides the patient terminal 2 with a My Page 100 containing management information for each patient's pre-health checkup in response to a request from the patient terminal 2, it may allow the patient to select buttons related to tasks to be performed before the health checkup if the video viewing flag is "viewed," and may not allow the patient to select buttons related to tasks to be performed before the health checkup if the video viewing flag is "not viewed." Also, for example, the providing means 8 of the server 5 may allow the patient to select a button to issue a certificate proving that the video has been viewed if the video viewing flag is "viewed," and may not allow the patient to select a button to issue a certificate proving that the video has been viewed if the video viewing flag is "not viewed." This allows for the avoidance of wasting valuable daytime hours for those in the age group eligible for preconception care, while enhancing the effectiveness of preconception checkups and preventing unnecessary problems.

[0105] Fourth, the registration means 6 of the server 5 updates the physician's comments 38 or physician's comment drafts 39 in the management table 20 based on the contents of the medical questionnaire or the measured values ​​of the tests. This reduces the burden on the physician.

[0106] Preferred embodiments of the preconception health check system, etc., according to the present invention have been described above with reference to the attached drawings, but the present invention is not limited to such examples. It will be clear to those skilled in the art that various modifications or alterations can be conceived within the scope of the technical idea disclosed herein, and these will naturally also fall within the technical scope of the present invention. [Explanation of Symbols]

[0107] 1…Precon Health Checkup System 2… Patient terminal 3… Doctor's terminal 4... Operator terminal 5… Server 6. Registration Method 7...Memorization means 8……Providing means 9...Network 10... Patient Table 20... Management Table 50… Doctor / Administrator Table 60...Company Table 70... Patient Information Registration Screen 100... My Page 200... Administrator screen 300... Doctor's screen 400... Preview mode health checkup results screen 500... Health checkup results screen in disclosure mode

Claims

1. A precon health checkup system comprising a patient terminal which is the terminal of a patient undergoing a precon health checkup, an operator terminal which is the terminal of the operator of the precon health checkup, and a server which is connected to the patient terminal and the operator terminal via a network, The aforementioned server, A registration means that, in response to a request from the patient terminal, assigns a patient identification number to the patient randomly, without overlapping with any previously assigned numbers, and registers the patient. A storage means for storing the patient's health checkup results information in association with the patient identification number, A providing means that, in response to a request from the patient terminal, retrieves the health checkup result information from the storage means and provides the health checkup result information to the patient terminal, Equipped with, When the registration means receives the health check result information from the operator terminal, it stores the health check result information in the storage means in association with the patient identification number. The storage means further stores a management table containing management information for the pre-examination for each patient identification number. The management table includes a video viewing flag indicating whether or not the patient has viewed the video related to the pre-confirmation health checkup. Furthermore, when the registration means receives information from the recipient terminal indicating that the recipient has viewed the video, it updates the video viewing flag to "viewed". The providing means provides the patient's terminal with a personal page for each patient on which buttons related to tasks the patient will perform before the pre-conception health checkup are located, and if the video viewing flag is set to "viewed", the patient is allowed to select the buttons related to tasks the patient will perform before the pre-conception health checkup, and if the video viewing flag is set to "not viewed", the patient is not allowed to select the buttons related to tasks the patient will perform before the pre-conception health checkup. A pre-confirmed health checkup system characterized by its features.

2. The providing means provides the recipient's terminal with a personal page for each recipient on which a button for issuing a certificate proving that the video has been viewed is located, and allows the selection of the issuance button when the video viewing flag indicates that the video has been viewed, and does not allow the selection of the issuance button when the video viewing flag indicates that the video has not been viewed. The preconception health check system according to feature 1.

3. The management table further includes the health check date which is the date the precon health check was taken, a questionnaire completion flag indicating whether or not the patient has completed the precon health check questionnaire, a pre-health check questionnaire response flag indicating whether or not the patient has answered the pre-health check questionnaire, a post-health check questionnaire response flag indicating whether or not the patient has answered the post-health check questionnaire, a health check result upload date which is the date on which the patient's health check result file was uploaded, and a doctor consultation requirement which indicates the doctor's judgment on whether or not a consultation is necessary for the patient. The providing means further provides the patient's terminal with a personal page for each patient, including a pre-health checkup task display area, a health checkup day task display area, and a post-health checkup task display area, and sets whether or not the buttons placed in the pre-health checkup task display area, the health checkup day task display area, and the post-health checkup task display area can be pressed according to the health checkup date, the questionnaire completion flag, the pre-health checkup questionnaire response flag, the post-health checkup questionnaire response flag, the health checkup result upload date, and whether or not a doctor consultation is required. A preconception health check system according to claim 1 or 2, characterized by the features described above.

4. The management table further includes physician comments on the health checkup results information, The aforementioned provisioning means determines whether or not the patient can view the health checkup results information depending on whether or not the physician's comment is NULL. A preconception health check system according to claim 1 or 2, characterized by the features described above.

5. A server connected via a network to a patient terminal, which is the terminal of a patient undergoing a pre-con health checkup, and to an operator terminal, which is the terminal of the operator of the said pre-con health checkup. A registration means that, in response to a request from the patient terminal, assigns a patient identification number to the patient randomly, without overlapping with any previously assigned numbers, and registers the patient. A storage means for storing the patient's health checkup results information in association with the patient identification number, A providing means that, in response to a request from the patient terminal, retrieves the health checkup result information from the storage means and provides the health checkup result information to the patient terminal, Equipped with, When the registration means receives the health check result information from the operator terminal, it stores the health check result information in the storage means in association with the patient identification number. The storage means further stores a management table containing management information for the pre-examination for each patient identification number. The management table includes a video viewing flag indicating whether or not the patient has viewed the video related to the pre-confirmation health checkup. Furthermore, when the registration means receives information from the recipient terminal indicating that the recipient has viewed the video, it updates the video viewing flag to "viewed". The providing means provides the patient's terminal with a personal page for each patient on which buttons related to tasks the patient will perform before the pre-conception health checkup are located, and if the video viewing flag is set to "viewed", the patient is allowed to select the buttons related to tasks the patient will perform before the pre-conception health checkup, and if the video viewing flag is set to "not viewed", the patient is not allowed to select the buttons related to tasks the patient will perform before the pre-conception health checkup. A server characterized by the following features.

Images