JP7451236B2 - Programs, methods and terminals - Google Patents

Description

The present invention relates to a program, method, and terminal for managing information related to mother and child.

Currently, those who report pregnancy are issued a maternal and child health handbook by the local government. The maternal and child health handbook allows pregnant women, medical institutions, and municipal welfare-related organizations to fill in important records related to mother and child from pregnancy to infancy. In this way, the maternal and child health notebook makes it possible to manage various information related to the health of the mother and child from pregnancy to infancy in one notebook.

In recent years, as shown in Patent Documents 1 and 2, information related to mothers and children, such as those managed in maternal and child health handbooks, has been digitized and managed. For example, management tools (so-called maternal and child health handbook applications) that allow important records related to mothers and children, which were previously managed in paper-based maternal and child health handbooks, to be managed on terminals such as smartphones have become widely used. ing.

Japanese Patent Application Publication No. 2014-191467 (published on October 6, 2014) Patent No. 5033816 (issued on September 26, 2012)

However, including the conventional techniques mentioned above, there are highly convenient management tools that cover both the period when the baby is in the womb (hereinafter referred to as the gestation period) and the period after the baby is born (hereinafter referred to as the childcare period). Nothing was able to achieve this. This is because between the pregnancy period and the child-rearing period, the subject to be managed changes from the mother's body to the infant, and the source of information regarding the mother and child changes from obstetrics to pediatrics.

Conventional management tools that are convenient for managing pregnancy do not necessarily mean that they can continue to be used conveniently as the child-rearing period progresses. For example, it is difficult to imagine that a management tool that is useful during the pregnancy period and has extensive functions for managing the mother's weight is a management tool that can be used conveniently after the child-rearing period, when information about the mother's weight becomes less important. Therefore, in order to successfully manage their newborn, mothers are forced to switch from the familiar management tools they used during pregnancy to other management tools that are more convenient for managing their child-rearing period.

For mothers who have to deal with drastic changes in their environment after giving birth, the stress of switching from a familiar management tool to an unfamiliar management tool cannot be ignored. It is desirable to create a single management tool that can be used conveniently even after the transition from pregnancy to child-rearing without the need to switch to a new, unfamiliar management tool.

One aspect of the present invention aims to realize a management tool that can continuously manage information related to a mother and child during both the pregnancy period and the childcare period.

In order to solve the above-mentioned problems, a program according to one aspect of the present invention is a program executed by a terminal including a control unit, a storage unit, and a display unit, and the program includes: A first step of displaying on the display section a gestation period display UI for displaying gestation period information indicating information regarding at least one of a pregnant woman and a fetus or pre-fetus; and at least one of a multiparous woman and a child. a second step of displaying, on the display section, a childcare period display UI for displaying childcare period information indicating information about the childcare period, the childcare period display UI being partially different from the pregnancy period display UI; until the user performs a first operation for causing the control unit to recognize the birth of the fetus. After the step is executed and the first operation is performed, the second step is executed in response to the second operation on the first UI component.

In order to solve the above-mentioned problems, a method according to one aspect of the present invention is a method that is executed by a terminal including a control unit, a storage unit, and a display unit, and is performed by a pregnant woman and a fetus or pre-fetus. a first step of displaying on the display section a pregnancy period display UI for displaying pregnancy period information indicating information regarding at least one of them; and displaying child-rearing period information indicating information regarding at least one of a multiparous woman and a child; a second step of displaying on the display section a child-rearing period display UI that is partially different from the pregnancy period display UI, the child-rearing period display UI being partially different from the pregnancy period display UI; Until the user performs the first operation for recognition, the first step is executed in response to the user's second operation on the first UI component displayed on the display unit, and the first operation is performed. After that, the second step is executed in response to the second operation on the first UI component.

In order to solve the above-mentioned problems, a terminal according to one aspect of the present invention is a terminal that includes a control unit, a storage unit, and a display unit, and the control unit is configured to support a pregnant woman and a fetus or pre-fetus. A gestation period display UI for displaying gestation period information indicating information regarding at least one of the above is displayed on the display section, and child-rearing period information for displaying child-rearing period information indicating information regarding at least one of a multiparous woman and a child. A period display UI that is partially different from the pregnancy period display UI is displayed on the display section, and the control section displays a childcare period display UI for causing the control section to recognize the birth of the fetus. Until the first operation is performed by the user, the pregnancy stage display UI is displayed in response to the user's second operation on the first UI component displayed on the display section, and after the first operation is performed, , displaying the childcare period display UI in response to the second operation on the first UI component.

The terminal according to each aspect of the present invention may be realized by a computer, and in this case, the program according to each aspect of the present invention may be implemented by causing the computer to operate as each section (software element) included in the terminal. This is a program that realizes a terminal on a computer. Further, a computer-readable recording medium on which a program according to each aspect of the present invention is recorded also falls within the scope of the present invention.

According to one aspect of the present invention, it is possible to realize a management tool that can continuously manage information related to a mother and child from the pregnancy period to the childcare period.

FIG. 2 is a block diagram showing the configuration of main parts of a smartphone. FIG. 2 is a diagram illustrating an application example of the program of the present disclosure. It is a figure which shows an example of the data structure of a mother and child information database. It is a figure showing an example of a new registration screen. It is a figure showing an example of a home screen in a pregnancy period. It is a figure which shows an example of a pregnancy record display screen. It is a figure which shows an example of a pregnancy record input screen. It is a figure showing an example of a birth registration screen. FIG. 3 is a diagram showing an example of a home screen during the childcare period. It is a figure showing an example of a growth record display screen. It is a figure which shows an example of a growth record input screen. It is a figure which shows the flow of the process performed when a smartphone operates as a management tool of mother and child information. It is a figure which shows the flow of the process performed when a smartphone operates as a management tool of mother and child information. It is a figure which shows another example of a pregnancy record display screen. It is a figure which shows another example of a growth record display screen.

[Embodiment 1]
<Application example>
Hereinafter, one embodiment of the present invention will be described in detail. FIG. 2 is a diagram illustrating an application example of the program of the present disclosure.

The program of the present disclosure is installed on a user's terminal, and the terminal realizes functions based on the program of the present disclosure. Here, a user is a person who can handle information related to mother and child (hereinafter referred to as mother and child information) through their own information processing terminal, regardless of the pregnancy or childcare period. For example, the "user" includes the child's mother and the child's family. In the following explanation, it is assumed that the user is a mother. The program of the present disclosure is, for example, a mother and child notebook application, and the terminal is, for example, a smartphone 1 (terminal) used by a user. For example, the maternal and child notebook application is distributed to each user's smartphone via the network 7 by a distribution server 6 that distributes applications developed by a service provider. When the mother and child notebook application is installed on the smartphone 1, the smartphone 1 realizes a function based on the program of the present disclosure, that is, a management tool that can continuously manage information related to the mother and child from the pregnancy period to the childcare period. Operates as a terminal.

A service provider is an organization that provides a maternal and child health record application to users. In this embodiment, as an example, the service provider further provides the local government and users with a collaboration service for realizing cooperation between the local government and users by utilizing mother and child information collected through the mother and child handbook application. It's okay. Furthermore, the collaboration service provided by the service provider may be a collaboration service for realizing collaboration between a medical institution and a user. Note that the distribution server 6 may belong to the service provider that developed the maternal and child notebook application, or may belong to a distribution contractor entrusted with distribution by the service provider.

In the present embodiment, information regarding a pregnant woman and at least one of a fetus and a pre-fetus (hereinafter simply referred to as "fetus"), that is, mother and child information observed during pregnancy is referred to as gestation period information. The gestational period information is imported into the user's smartphone 1 on which the maternal and child notebook application as a program of the present disclosure is installed. As an example, gestational stage information includes a pregnant woman's weight, BMI (Body Mass Index), blood pressure, pulse, blood sugar level, edema, urine protein, urine sugar, fetal size, estimated fetal weight, and the condition of the fetus. It may also be an image of a fetus. Note that the term "pre-fetus" refers to, for example, a human fetus in the embryonic state up to 8 weeks after fertilization, and a child in the state of a fetus from 8 weeks after fertilization onward.

In this embodiment, information regarding at least one of a multiparous woman and a child, that is, mother and child information observed during the child-rearing period is referred to as child-rearing period information. The childcare period information is imported into the user's smartphone 1 on which the mother-child notebook application as a program of the present disclosure is installed. For example, the childcare period information may include the child's height, weight, head circumference, chest circumference, a photograph of the child, and records of vaccinations the child has received. Furthermore, children include infants and refer to children from birth to adults.

The means for importing the mother and child information described above into the smartphone 1 is not particularly limited. For example, the mother and child information may be directly input by the user of the smartphone 1 via an operation unit included in the smartphone 1. Alternatively, mother and child information measured by the measuring device may be transferred to the smartphone 1 from a measuring device connected to the smartphone 1 via Bluetooth (registered trademark) or the like. The measuring device may be, for example, a weight scale, a blood pressure monitor, a blood sugar level measuring device, etc., but is not limited to these. The measuring device transfers the values obtained through measurement, such as weight, blood pressure, and blood sugar level, to the smartphone 1 via Bluetooth (registered trademark) or the like.

Alternatively, for example, mother and child information may be created by a medical institution. For example, gestational stage information observed in an obstetric department is transferred to the smartphone 1 from a device or recording medium of a medical institution that examined a pregnant woman or a fetus. Specifically, the mother and child information created by the medical institution includes fetal images acquired by the echo imaging device 2, weight and blood pressure measured at the medical institution, or blood and urine tests conducted at the medical institution. It may be a result. Further, the gestational period information may be doctor's findings included in an electronic medical record created by operating the doctor terminal 3 by a doctor who examined the pregnant woman or the fetus at a medical institution. The doctor's findings include terms expressing the condition of the fetus diagnosed by the doctor and comments from the doctor. In this case, the gestational period information is stored in an external recording medium such as a USB (Universal Serial Bus) memory 5 that can be connected to devices belonging to the medical institution such as the echo imaging device 2, the doctor terminal 3, and the electronic medical record server 4. . Then, the gestational period information may be transferred to the smartphone 1 by inserting the USB memory 5 into the smartphone 1. Further, gestational period information such as fetal images may be uploaded from the echo imaging device 2 or the doctor terminal 3 to a predetermined server (cloud) such as the electronic medical record server 4. The smartphone 1 may then download the uploaded gestation period information of the user from the cloud.

In a medical institution, a doctor terminal 3 or an electronic medical record server 4 connected to the echo imaging device 2 via a LAN (Local Area Network) (not shown) may transmit gestational period information to the smartphone 1 via the network 7. . The echo imaging device 2 or the doctor terminal 3 operated by the doctor during the medical examination may transmit the pregnancy period information to the smartphone 1 via short-range wireless communication means. Alternatively, the echo imaging device 2 or the doctor terminal 3 operated by the doctor during the medical examination may be connected to the smartphone 1 by wire, and the pregnancy period information may be transferred from the echo imaging device 2 or the doctor terminal 3 to the smartphone 1.

The childcare period information may be transferred to the smartphone 1 from the doctor terminal 3 operated by the pediatrician, the electronic medical record server 4 or the USB memory 5 connected to the doctor terminal 3, in the same manner as described above.

The management server 8 utilizes mother and child information, including gestation period information and childcare period information, to realize collaboration services for realizing cooperation between local governments and users (and medical institutions and users as necessary). This is the device. The management server 8 belongs to a service provider and manages users who have installed and are using the maternal and child health record application distributed by the service provider on the smartphone 1. The management server 8 also manages local governments and medical institutions that have concluded contracts with service providers and are using cooperative services. Furthermore, the management server 8 manages the local government that has jurisdiction over the user's residential area and the user's family clinic. That is, the management server 8 manages, for each user, the local government that provides administrative services to the user and the medical institution that the user attends as a family. Note that the distribution server 6 belonging to the service provider and the above-mentioned management server 8 may be configured by one computer.

In the present embodiment, the smartphone 1 on which the maternal and child health handbook application is installed receives an article or a notification related to the article from the management server 8, and displays the article or the notification on the display section of the smartphone 1 so that the user can view the article or the notification. May be displayed. In this embodiment, an article is data that is information provided by a local government or a medical institution and formatted so that it can be viewed on the smartphone 1 on which the maternal and child health record application is installed. In this embodiment, the content of the article does not matter as long as it includes information provided by a local government or a medical institution. As an example, an article provided by a local government may include a message from the local government to a child's guardian, or may include announcements of various events sponsored by the local government. As an example, an article provided by a medical institution may include information regarding the health of pregnant women supervised by a doctor, or may include various messages addressed to pregnant women from the medical institution. The message may be, for example, a notice of the next prenatal checkup or a notice of a mother's class sponsored by a medical institution.

Each local government and each medical institution that has contracted with a service provider can register independently created articles in the management server 8. By contracting with a service provider, local governments can efficiently provide information via the management server 8 to users (e.g., mothers) who have installed the maternal and child handbook application, and improve administrative services. Quality can be improved. For example, a person in charge of a local government operates the local government terminal 9 to create an article and upload it to the management server 8. Local governments may distribute articles for pregnant women who are going through pregnancy, or articles for mothers of infants and young children who are raising children. A user can receive articles for pregnant women during the pregnancy period and articles for mothers of infants during the childcare period through the mother-child notebook application. In addition, by contracting with a service provider, medical institutions can provide high value-added information to patients (pregnant women in this case) who have installed the maternal and child health handbook application via the management server 8. It becomes possible to provide services.

In this way, there are benefits for local governments and medical institutions to contract with service providers and utilize collaborative services with users. Then, the service provider can receive payment from the local government and medical institution as a usage fee for the management server 8. As a result, it is possible to construct a billing model in which the maternal and child health notebook application is provided to users free of charge or at a low price, while the development costs and operating costs of the mother and child health notebook application are collected from local governments and medical institutions.

<Hardware configuration of smartphone 1>
FIG. 1 is a block diagram showing the main configuration of a smartphone 1. As shown in FIG. The smartphone 1 includes, for example, a control section 10, a storage section 11, a connection section 12, a communication section 13, an operation section 14, and a display section 15. Note that the smartphone 1 may further include various parts (not shown) that smartphones are equipped with in order to realize the functions that a general smartphone has.

The operation unit 14 is an input device for accepting user operations. The operation unit 14 inputs an instruction signal corresponding to the received user's operation to the control unit 10. As an example, the operation unit 14 and the display unit 15 may constitute a touch panel. The operation unit 14 includes a device capable of detecting that an indicator such as a user's finger touches or approaches the input surface of the operation unit 14, which is also the display surface of the display unit 15.

The display unit 15 is an output device that visually presents the information processed by the control unit 10 to the user. For example, the display unit 15 is configured by a liquid crystal display (LCD), an organic EL (Electro-Luminescence) display, or the like. For example, the display unit 15 displays a user interface (UI) of a maternal and child notebook application for managing pregnancy period information and childcare period information. The UI of the maternal and child notebook application is, for example, an application screen that includes one or more various UI components such as software buttons and a box area for displaying information.

The communication unit 13 communicates with external devices such as the distribution server 6 and the management server 8 via the network 7, for example. In this embodiment, the network 7 is assumed to be a wide area communication network including the Internet, but the network 7 may also include a telephone line network, a mobile communication network, a CATV (CAable TeleVision) communication network, a satellite communication network, etc. You can stay there.

The connection unit 12 includes a terminal for connecting an external recording medium such as the USB memory 5 to the smartphone 1. When the USB memory 5 is electrically connected to the smartphone 1 via the connection unit 12, the control unit 10 of the smartphone 1 can establish communication with the USB memory 5. The control unit 10 can read data stored in the USB memory 5, erase data, and write data to the USB memory 5 via the connection unit 12.

The control unit 10 controls the operation of each part of the smartphone 1 in an integrated manner. The control unit 10 is, for example, a computer device including an arithmetic processing unit such as a CPU (Central Processing Unit) or a dedicated processor. The control unit 10 can control the operation of each unit of the smartphone 1 by reading and executing programs stored in the storage unit 11 for implementing various controls of the smartphone 1.

The storage unit 11 stores various data used by the control unit 10, and includes RAM (Random Access Memory), ROM (Read Only Memory), and the like. In this embodiment, as an example, a mother and child information database (hereinafter referred to as DB) 41 and a UI parts storage 42 are stored in the storage unit 11 in a non-volatile manner. The data structure of these data will be detailed later.

<Software configuration of smartphone 1>
The control unit 10 of the smartphone 1 includes, for example, an information acquisition unit 31, a birth recognition unit 32, and a display control unit 20. The display control section 20 further includes a pregnancy period input support section 21, a pregnancy period display control section 22, a childcare period input support section 23, and a childcare period display control section 24. Each of these units is configured such that, for example, the control unit 10 as a CPU (central processing unit) or the like executes a program stored in a storage device such as a ROM (read only memory), specifically, a maternal and child health handbook application program in a RAM (random This is achieved by reading the data into a memory (such as access memory) and executing it.

The information acquisition unit 31 acquires mother and child information supplied to the smartphone 1 via the connection unit 12, communication unit 13, operation unit 14, etc., and stores the mother and child information in the mother and child information DB 41. For example, the information acquisition unit 31 stores mother and child information input by the user by operating the operation unit 14 in the mother and child information DB 41.

The birth recognition unit 32 recognizes the birth of the fetus that was the object of management during the pregnancy period, and instructs the display control unit 20 to transition from the pregnancy period to the childcare period. The birth recognition unit 32 may recognize the birth of the fetus in response to the user performing a first operation for causing the control unit 10 to recognize the birth of the fetus. The first operation may be, for example, for the user to operate a specific UI component displayed on the display unit 15 in a specific method using the operation unit 14, or for the user to operate mother and child information regarding the child she has given birth to ( It may also be an operation of inputting information (height, weight, etc.) as birth information. After the birth recognition unit 32 recognizes the birth, the control unit 10 treats the managed object, which was treated as a fetus during pregnancy, as an infant.

The display control unit 20 controls the UI of the maternal and child handbook application by controlling each part of the pregnancy period input support section 21, the pregnancy period display control section 22, the childcare period input support section 23, and the childcare period display control section 24. control.

Under the control of the display control unit 20, the gestational stage input support unit 21 displays a UI for supporting the user's input operations when managing gestational stage information. For example, the pregnancy period input support unit 21 displays a pregnancy record input screen (for example, FIG. 7) for a pregnant user to input daily weight, blood pressure, blood sugar level, and the like. The gestational stage information input via the pregnancy record input screen is acquired by the information acquisition unit 31 and stored in the mother and child information DB 41.

Furthermore, the gestational period input support unit 21 may display a support UI for the user to add a comment to the echo photograph of the fetus stored in the mother and child information DB 41 as mother and child information. The user can operate the above-mentioned support UI using the operation unit 14 and add a desired comment to the echo photograph. Note that the echo photograph is transferred from the echo imaging device 2 or the doctor terminal 3 to the smartphone 1 via the network 7 or the USB memory 5, for example.

The pregnancy period display control section 22 displays a pregnancy record display screen (for example, FIG. 6) under the control of the display control section 20. The pregnancy record display screen is a UI for presenting one or more pieces of gestational period information stored in the maternal and child information DB 41, or a pregnancy record that is the result of processing the one or more pieces of gestational period information, in a viewable manner to the user. be.

Under the control of the display control unit 20, the childcare period input support unit 23 displays a UI for supporting user input operations when managing childcare period information. For example, the childcare period input support unit 23 displays a growth record input screen (for example, FIG. 11) for the user, who is a mother, to input the infant's weight, height, and the like. The childcare period information input via the growth record input screen is acquired by the information acquisition unit 31 and stored in the mother and child information DB 41.

The childcare period display control unit 24 displays a growth record display screen (for example, FIG. 10) under the control of the display control unit 20. The growth record display screen is a UI for presenting one or more pieces of child-rearing period information stored in the mother and child information DB 41, or a growth record that is the result of processing the one or more pieces of child-rearing period information, in a viewable manner to the user. be.

In addition to the above-mentioned UI, the display control unit 20 displays a new registration screen (for example, FIG. 4), a birth registration screen (for example, FIG. 8), etc. on the display unit 15 in response to a specific operation by the user. may be displayed. The new registration screen is a UI for registering various information about a user who is a pregnant woman when the user first starts using the maternal and child handbook application. The birth registration screen is a UI for the user to register various information about the delivered baby.

As an example, the display control unit 20 controls the gestational stage input support unit 21 and the gestational stage display control unit 22 to manage the smartphone 1 and the gestational stage information until the birth recognition unit 32 recognizes the birth of the fetus. Operate as a management tool for After the birth recognition unit 32 recognizes the birth of a fetus, the display control unit 20 controls the childcare period input support unit 23 instead of the pregnancy period input support unit 21. In addition to this, the display control unit 20 controls the childcare period display control unit 24 to operate the smartphone 1 as a management tool for managing childcare period information. That is, the display control unit 20 switches the flow line of the UI from the pregnancy period to the childcare period at the event of the birth of a child. This allows the user to smoothly transition from managing pregnancy period information to managing childcare period information while continuing to use one application.

Note that the display control section 20 may control the pregnancy period display control section 22 to maintain the display function of pregnancy period information even after the transition to the childcare period. Thereby, the user can continue to check the gestation period information even after transitioning to the childcare period.

The mother and child information DB 41 stored in the storage unit 11 stores all kinds of mother and child information. Among the mother and child information, the mother and child basic information 411 is information that the user inputs into the smartphone 1 via the above-mentioned new registration screen when the user first starts using the mother and child notebook application. The infant basic information 412 is information that the user inputs into the smartphone 1 via the above-described birth registration screen in order to cause the control unit 10 to recognize the birth of a child. This information is appropriately referenced by the display control unit 20 and each unit operating under the control of the display control unit 20 to configure the UI displayed on the display unit 15.

Note that even after the maternal basic information 411 is registered in the maternal and child information DB 41 via the new registration screen, the information acquisition unit 31 adds new maternal basic information 411 and changes or deletes existing maternal basic information 411. may be received to update the mother and child information DB 41. Furthermore, even after the infant basic information 412 is registered in the mother and child information DB 41 via the birth registration screen, the information acquisition unit 31 adds new infant basic information 412 and changes or deletes the existing infant basic information 412. may be received to update the mother and child information DB 41.

The UI parts storage 42 stored in the storage unit 11 stores all UI parts arranged on the UI (for example, an application screen) displayed on the display unit 15. The common component 421 is a UI component that is commonly placed on the screen during the pregnancy period and the childcare period. By placing common UI parts on the screen throughout the pregnancy and childcare period, users can use the maternal and child health notebook application with the same usability even when they transition from pregnancy to childcare. I can continue. In other words, a user who has been using the maternal and child notebook application since the pregnancy period can continue to use the maternal and child notebook application even after giving birth, and manage it after giving birth with the same operational feel as before giving birth.

The pregnancy period component 422 is a UI component placed on the screen to manage pregnancy period information. The pregnancy period component 422 is used to implement functions specific to the pregnancy period via the screen displayed on the display unit 15.

The childcare period component 423 is a UI component placed on the screen to manage childcare period information. The childcare period component 423 is used to implement functions specific to the childcare period via a screen displayed on the display unit 15.

The display control unit 20 and each unit operating under the control of the display control unit 20 read necessary UI parts from the UI parts storage 42 to configure a screen, and display the screen on the display unit 15 to provide the UI to the user. present.

<Mother and child information DB41>
FIG. 3 is a diagram showing an example of the data structure of the mother and child information DB 41 stored in the storage unit 11 of the smartphone 1. The mother and child information DB 41 includes, for example but not limited to, each item of mother and child information ID, date information, gestational week, information type, subclassification, and data.

Identification information for the smartphone 1 to uniquely identify mother and child information is stored in the item of mother and child information ID. For example, the information acquisition unit 31 may automatically assign a unique identification number to one piece of acquired mother and child information.

The date information item stores date information associated with mother and child information. The date information associated with the mother and child information is information indicating an arbitrary date related to the mother and child information. For example, the date information includes, but is not limited to, input date, measurement date, medical examination date, creation date and time, update date and time, storage date and time, acquisition date and time, transmission date and time, and reception date and time.

The gestational week number field stores the gestational week number associated with mother and child information. For example, the information acquisition unit 31 stores the number of weeks of pregnancy calculated based on the above-mentioned date information and the reference date in the item.

The reference date is a date that serves as a reference for calculating the pregnancy week of a pregnant woman. As an example, the reference date includes at least one of the start date of the last menstrual period and the expected delivery date. The reference date is stored in advance in the storage unit 11 as part of the basic basic information 411, for example. The information acquisition unit 31 can calculate the number of weeks of pregnancy associated with the mother and child information based on how many weeks and days the date information associated with the mother and child information is away from the reference date. For example, the information acquisition unit 31 sets the start date of the last menstrual period read from the storage unit 11 to 0 weeks and 0 days of pregnancy, and if the date indicated by the date information is 70 days after the start date of the last menstrual period, the information acquisition unit 31 sets the number of weeks of pregnancy to 0 days of pregnancy. Calculated as 10 weeks and 0 days.

Alternatively, for example, the information acquisition unit 31 calculates the number of weeks of pregnancy based on how many days before the expected delivery date the date indicated by the date information is. For example, the information acquisition unit 31 can set, as the pregnancy date (reference date of 0 weeks and 0 days of pregnancy), a date that is October 10 days back from the expected delivery date input by the user based on a doctor's judgment. Then, the information acquisition unit 31 may calculate the number of weeks of pregnancy from the difference between the above-mentioned gestation date and date information. According to such a configuration, the number of weeks of pregnancy can be determined only from the expected delivery date determined by the doctor, without the user inputting the start date of the last menstrual period.

The information type item stores the type of mother and child information. The information acquisition unit 31 determines the information type according to the content of the mother and child information, and stores it in the corresponding item. As described above, when the content of mother and child information is information indicating the condition of at least one of the pregnant woman and the fetus, such as weight or blood pressure, the information acquisition unit 31 sets the information type of the mother and child information to "state". ``Information'' and stores it in that item. When the content of the mother and child information is information indicating the action taken by the pregnant woman, such as the number of steps, the information acquisition unit 31 determines the information type of the mother and child information as "action record" and stores it in the item. . When the contents of mother and child information are basic information specific to each pregnant woman, such as blood type, medical history, vaccination history, etc., the information acquisition unit 31 sets the information type of the mother and child information to "basic information". is determined and stored in the corresponding item.

Note that the basic information is information that basically remains unchanged regardless of the passage of time, so when the information type of the mother and child information is basic information, the information acquisition unit 31 obtains the following information about the mother and child information: It is also possible to omit associating the date information and the gestational week.

Furthermore, when the mother and child information is information input or observed during the pregnancy period, the information acquisition unit 31 may determine the information type of the mother and child information to be "gestation period information." Furthermore, when the mother and child information is information input or observed during the childcare period, the information acquisition unit 31 may determine the information type of the mother and child information to be "childcare period information."

The subclassification item stores the type of mother and child information for further classifying the typed mother and child information. For example, "weight", "blood pressure", "blood sugar level", etc. in the status information correspond to the type.

The data item stores data that is the content of mother and child information or link information of the location where the data is stored. The data type or file format of the data stored in the item is determined as appropriate depending on the type of mother and child information. For example, the data type for the expected delivery date may be a number string representing the year, month, and day, and the data type for weight may be a number string representing the number of kg. The data type of the vaccination history may be a table in which vaccination dates are associated with vaccination types. The electronic medical record or the physician's findings within the electronic medical record may be a document file consisting of one or more items for entering numbers and letters.

In the present embodiment, upon acquiring mother and child information, the information acquisition unit 31 first assigns a number and ties a mother and child information ID together with date information to the data that is the content of the mother and child information. Next, the information acquisition unit 31 calculates the number of weeks of pregnancy based on the date information and a previously registered reference date such as the expected delivery date, and associates it with the mother and child information. Further, the information acquisition unit 31 determines the information type and subclassification of the mother and child information based on the data of the contents of the mother and child information, and associates these with the mother and child information. In this way, the information acquisition unit 31 associates various supplementary information with the data that is the content of the mother and child information, and then adds the mother and child information to the mother and child information DB 41.

<Example of UI>
4 to 11 are diagrams showing specific examples of the UI that the display control section 20 and each section of the display control section 20 provide to the user via the display section 15.

FIG. 4 is a diagram showing an example of a new registration screen. The display control unit 20 displays a new registration screen 300 shown in FIG. 4 on the display unit 15, for example, when the user downloads the maternal and child notebook application to the smartphone 1 and starts using it. The user information input via the new registration screen 300 is acquired by the information acquisition unit 31 and stored in the mother and child information DB 41 as maternal basic information 411.

If the new registration screen 300 cannot be displayed all at once on the display unit 15, the display control unit 20 may display the new registration screen 300 in a scrollable manner.

As an example, the maternal basic information 411 includes items such as email address, password, date of birth, selected municipality, selected medical institution, date of start of last menstrual period, and expected delivery date. For example, the user can input information related to the above-mentioned items into the smartphone 1 through each UI component arranged on the new registration screen 300 shown in FIG.

The "selected local government" UI component is configured, for example, with a pull-down menu for selecting each prefecture and city, ward, town, or village that corresponds to the user's residential area. Based on the combination of the prefecture and city selected by the user, the information acquisition unit 31 identifies a local government ID that identifies the local government that has jurisdiction over the user's residential area, and stores it in the mother and child information DB 41 as the mother basic information 411. Store in.

The "selected medical institution" UI component includes, for example, a pull-down menu for selecting the prefecture and city where the medical institution is located, and the name of the medical institution. The information acquisition unit 31 identifies a medical institution ID that identifies the medical institution designated by the user as a family clinic based on the combination of the prefecture, city, town, village, and medical institution name selected by the user, and It is stored in the mother and child information DB 41 as information 411.

The identified local government ID and medical institution ID may be uploaded from the smartphone 1 to the management server 8, and managed in the management server 8 in association with the user ID. Thereby, the management server 8 can specify, for each user, the local government and medical institution selected by the user. The management server 8 can then deliver an article provided by the local government or medical institution selected by the user or a notification related to the article to the user's smartphone 1.

In another embodiment, the management server 8 does not need to issue a user ID to the user of the smartphone 1, and links the user ID, local government ID, and medical institution ID in the storage section of its own device. You don't have to manage it. In this form, each time the smartphone 1 requests the management server 8 for an article or a notification, the smartphone 1 transmits the local government ID and medical institution ID specified in its own terminal to the management server 8. In this way, when the management server 8 receives a request for an article from the smartphone 1, the management server 8, without knowing the correspondence between the user and the local government or medical institution in its own device, can can identify the local government and medical institution of their choice.

The UI components for the start date of the last menstrual period and the expected delivery date are configured with, for example, a pull-down menu for selecting the year, month, and day. The information acquisition unit 31 stores the last menstrual start date and expected delivery date input by the user in the mother and child information DB 41 as maternal basic information 411. The start date of the last menstrual period and the expected delivery date are reference dates, and are used to calculate the number of weeks of pregnancy based on the date information linked to the mother and child information.

FIG. 5 is a diagram showing an example of a home screen during pregnancy. During the pregnancy period until the birth recognition unit 32 recognizes the birth, for example, when the user starts the maternal and child handbook application, the display control unit 20 first displays the home screen 400 shown in FIG. 5 on the display unit 15. May be displayed.

Home screen 400 includes, for example, daily progress information 401 and footer 402. The number of days progress information 401 is a UI component for presenting the number of days progress information regarding the child's growth to the user. As shown in FIG. 5, during the pregnancy period, the number of days progress information 401 may include the number of days remaining from the current date to the expected delivery date (expected delivery date), or may include the current number of weeks of pregnancy. The footer 402 is composed of a UI component that supports the user's operation to call up a specific screen of the mother and child notebook application. As an example, the footer 402 includes a HOME button 403, a BABY button 404, a CLINIC button 405, and a LOCAL button 406. The HOME button 403 is a UI component for calling the home screen. A BABY button 404 (first UI component) is a UI component for calling a display screen that displays mother and child information. The CLINIC button 405 is a UI component for calling a display screen that displays information regarding the medical institution selected by the user. The LOCAL button 406 is a UI component for calling a display screen that displays information regarding the local government selected by the user.

During the pregnancy period, when the user's operation (second operation) on the BABY button 404 is accepted via the operation unit 14, the display control unit 20 causes the pregnancy period display control unit 22 to display the pregnancy period information. A pregnancy record display screen is displayed on the display unit 15.

Home screen 400 may further include nickname 407. The nickname 407 is a UI component for displaying the name given to the fetus by the user. For example, a user can register a nickname to be given to a fetus at any time from a setting screen (not shown).

Home screen 400 may further include a sibling switching button 408. The sibling switching button 408 is a UI component that allows the user to switch children whose information is to be displayed on the display unit 15. For example, when the user taps the sibling switching button 408, the display control unit 20 causes the display unit 15 to display options corresponding to each of the registered siblings. When the user performs an operation to select another child, the display control unit 20 displays a home screen 400 corresponding to the selected other child on the display unit 15.

FIG. 6 is a diagram showing an example of a pregnancy record display screen. The pregnancy period display control unit 22 displays a pregnancy record display screen 500 shown in FIG. 6 on the display unit 15, for example, in response to the user tapping the BABY button 404 during the pregnancy period.

Pregnancy record display screen 500 includes a display area 501 for displaying pregnancy period information in a viewable manner, a birth registration button 502, and an information input button 503. Pregnancy record display screen 500 may further include nickname 407, number of days progress information 401, sibling switching button 408, medical checkup button 506, footer 402, and the like.

The display area 501 is a UI component for presenting the gestation period information stored in the mother and child information DB 41 to the user. As an example, the gestational period information is the mother's weight, and in the example shown in FIG. 6, the weight of the user who is the mother is represented in a graph in the display area 501. In the graph, the vertical axis indicates body weight, and the horizontal axis indicates date information (specifically, measurement date). In other examples, the gestational age information may be estimated baby weight. The estimated baby weight is determined, for example, by an obstetrician based on an echograph.

Note that the switching tabs are not limited to the tab corresponding to weight recording and the switching tab 505 corresponding to echo photography, but can also be used to display other gestational period information in place of or in addition to these tabs. A switching tab may be provided.

The gestational stage display control unit 22 may display other gestational stage information other than the mother's weight in the display area 501. For example, an echo photograph of a fetus may be displayed in the display area 501. Switching of the display contents in the display area 501 is performed, for example, in response to the user operating the switching tab 505 or the like.

For example, when the user taps the switching tab 505 on the pregnancy record display screen 500 shown in FIG. 6, the pregnancy period display control section 22 displays the pregnancy record display screen 500 shown in FIG. 14 on the display section 15. In the pregnancy record display screen 500 shown in FIG. 14, a list of echo photographs is displayed in the display area 501, for example.

In the program according to the present disclosure, the second UI component for performing the first operation may be included in the pregnancy period display UI. For example, the birth registration button 502 (second UI component) is a UI component for calling a birth registration screen. A birth registration button 502 for performing an operation (first operation) for causing the control unit 10 to recognize the birth of a fetus is included in the pregnancy record display screen 500 (gestation period display UI). Therefore, the user can recognize the presence of the birth registration button 502 while using the maternal and child notebook application as a pregnancy management tool. Immediately after the user actually gives birth, the user can have the smartphone 1 recognize the birth of the child by simply operating the birth registration button 502. As a result, it is possible to prevent users from failing to register their births, and to ensure that the birth event that triggers the transition from the pregnancy period to the childcare period is captured without delay in the maternal and child notebook application.

In addition, in the program according to the present disclosure, the storage unit 11 stores the number of weeks of pregnancy or a reference date necessary for calculating the number of weeks of pregnancy, and the first step is performed when the number of weeks of pregnancy is a predetermined week. It may also include changing the display mode of the second UI component so that the second UI component is emphasized when the number exceeds the number.

Specifically, the pregnancy period display control unit 22 changes the display mode of the birth registration button 502 so that the birth registration button 502 (second UI component) is highlighted when the number of weeks of pregnancy has passed a predetermined number of weeks. may be changed. Note that the current number of weeks of pregnancy of the user can be calculated from, for example, the current date and the reference date. The storage unit 11 stores the number of weeks of pregnancy or a reference date necessary for calculating the number of weeks of pregnancy. For example, when the current gestational age has passed the term (for example, 41 weeks and 6 days of gestation), the pregnancy period display control unit 22 may highlight the birth registration button 502 more prominently than before. You may.

According to the above configuration, the maternal and child health handbook application more reliably captures the occurrence of the "birth" event that triggers the transition from the pregnancy period to the childcare period, and allows the user to continue using the mother and child health handbook even after the childcare period. You can encourage people to use your application.

Furthermore, in the program according to the present disclosure, the second UI component whose display mode has been changed may be arranged so as not to overlap the area for displaying gestational period information in the gestational period display UI.

Specifically, the pregnancy period display control unit 22 prevents the birth registration button 502 whose display mode has been changed from overlapping the area for displaying pregnancy period information on the pregnancy record display screen 500, that is, the display area 501. It is desirable to place the birth registration button 502 in the. For example, the pregnancy period display control unit 22 does not increase the size of the birth registration button 502 so that it covers the display area 501, or does not move the display position closer to the display area 501. The pregnancy period display control unit 22 changes the color of the birth registration button 502, causes it to blink, or adds animation to the design of the birth registration button 502. In this way, the pregnancy period display control unit 22 changes the display mode of the birth registration button 502 so that it catches the user's attention more than before without impairing the visibility of the display area 501.

According to the above-described configuration, the highlighting or prompting of the birth registration button 502 can be done to the extent that it does not obstruct the viewing of gestational period information and does not overstimulate the user, providing the user with a gestational period management tool. can be used comfortably. For example, for a pregnant woman who has not given birth after a gestational age of 41 weeks and 6 days, the overly prominent highlighting of the birth registration button 502 and the prompting for tapping may cause stress such as anxiety and irritation. Therefore, it is meaningful to change the display mode so as not to stimulate pregnant women unnecessarily.

The information input button 503 (fifth UI component) is a UI component for calling a pregnancy record input screen.

Further, in the program according to the present disclosure, the pregnancy period display UI displayed in the first step includes a sixth UI component for instructing to finish inputting the pregnancy period information, and the sixth UI component is After the operation, in the first step, updating of the display in the gestation period display UI as the number of weeks of pregnancy progresses may be stopped, and the display of the gestation period information for which input has been completed may be maintained.

Specifically, the pregnancy record display screen 500 may include a record end button 504 (sixth UI component) for instructing to end input of pregnancy period information. After the recording end button 504 is operated, the pregnancy period display control unit 22 stops updating the display as the number of weeks of pregnancy progresses when displaying the pregnancy record display screen 500. For example, the pregnancy stage display control unit 22 maintains the days progress information 401 and the display area 501 as the display contents based on the pregnancy stage information input up to the time when the recording end button 504 is operated, and thereafter, Even if time progresses, updating of these display contents is stopped. For example, the pregnancy period display control unit 22 maintains the number of days progress information 401 as it is at the time when the recording end button 504 is operated, regardless of the progress of the current time. In addition, the pregnancy stage display control unit 22 displays a graph of the mother's weight or a list of echo photographs in the display area 501 while maintaining the display content at the time when the recording end button 504 was operated.

According to the above configuration, a user who wants to finish inputting gestational period information but wants to view the gestational period information input so far can comfortably continue using the maternal and child health handbook application for the purpose of viewing past information. There is an effect that it can be done.

Users who wish to use this method include, for example, users who have successfully given birth to a child but do not wish to use this maternal and child health handbook application as a management tool during the child-rearing period, or users who wish to continue their pregnancy until childbirth due to various reasons. It is assumed that there are users who were unable to do so.

With the above-described configuration, such users will not be repeatedly prompted to enter information about their newborn child or be offended by displays that appear to indicate that the pregnancy is continuing, which is inappropriate to the current situation. You can comfortably view the necessary past information when you need it.

Pregnancy record display screen 500 may further include a medical checkup button 506. The health checkup button 506 is a UI component for calling a screen (not shown) for supporting input of mother and child information related to a pregnant woman's health checkup.

FIG. 7 is a diagram showing an example of a pregnancy record input screen. For example, in response to the user tapping the information input button 503 on the pregnancy record display screen 500, the pregnancy period input support unit 21 displays a pregnancy record input screen 550 shown in FIG. 7 on the display unit 15.

Pregnancy record input screen 550 includes, as UI components, a text box for inputting measurement date, ie, date information, and a text box for inputting gestational period information, for example. Text boxes for inputting gestational period information are arranged for each type of gestational period information. In addition to the mother's weight, a text box may be provided for inputting measurement results such as blood pressure and blood sugar level. Note that the measurement results such as the mother's weight, blood pressure, and blood sugar level may be transferred from the above-mentioned measuring device that is communicably connected to the smartphone 1 using Bluetooth (registered trademark) or the like.

Pregnancy record input screen 550 may include a registration button 551. In response to the user inputting date information and gestational period information in the above-mentioned text box and operating the registration button 551, the information acquisition unit 31 acquires the input date information and gestational period information, It is stored in the mother and child information DB 41.

FIG. 8 is a diagram showing an example of a birth registration screen. For example, in response to the user operating the birth registration button 502 on the pregnancy record display screen 500, the display control unit 20 displays the birth registration screen 350 shown in FIG. 8 on the display unit 15. The information on the child input via the birth registration screen 350 is acquired by the information acquisition unit 31 and stored in the mother and child information DB 41 as infant basic information 412.

If the birth registration screen 350 cannot be displayed all at once on the display unit 15, the display control unit 20 may display the birth registration screen 350 in a scrollable manner.

As an example, the infant basic information 412 includes items such as date of birth (that is, birth date of the baby), gestation period, sex, weight, height, head circumference, and chest circumference of the newborn baby.

The UI component for the date of delivery is, for example, configured with a pull-down menu for selecting the year, month, and day, similar to the start date of the last menstrual period and the expected date of delivery. The information acquisition unit 31 stores the delivery date input by the user in the mother and child information DB 41 as infant basic information 412.

The display control unit 20 calculates the gestational period based on the input delivery date and the reference date (for example, the start date of the last menstrual period) input as the maternal basic information 411 during the pregnancy period, and displays the calculated gestational period. , may be displayed in the text box 351 for inputting the pregnancy period.

Users who are pregnant women are often not aware of how many weeks and days of pregnancy they are as of today, and we believe that there are few users who know how many weeks and days of pregnancy they were on the day they gave birth and can answer immediately. It will be done. Therefore, the display control unit 20 calculates the gestational period using the maternal basic information 411 inputted in advance during the gestational period, and fills in the value of the gestational period in the text box 351 on behalf of the user. In this way, it is possible to reduce the burden of registering the user's birth information.

As mentioned above, one advantage of having a single maternal and child record book application that has management functions for both the pregnancy period and the childcare period is that the mother and child information entered during the pregnancy period can be used even after the transition to the childcare period. There is a point that it can be done. Such use of mother and child information has advantageous effects for the user, such as reducing the burden of information registration work.

In response to the registration button 352 being operated with information entered in each text box arranged on the birth registration screen 350, the information acquisition unit 31 acquires information regarding these infants as infant basic information 412. It is acquired and stored in the mother and child information DB 41.

The birth recognition unit 32 recognizes the birth of a child in response to the first operation for causing the control unit 10 to recognize the birth of the fetus. Then, the birth recognition unit 32 instructs each unit of the control unit 10, particularly the display control unit 20, so that the mother and child notebook application realizes a management tool for the childcare period. Here, the first operation is assumed to be, for example, a tap operation on the birth registration button 502 or a tap operation on the registration button 352, although it is not limited thereto.

The display control unit 20 switches the flow lines of each UI or reconstructs the UI according to instructions from the birth recognition unit 32 so that the smartphone 1 operates as a management tool for the childcare period.

FIG. 9 is a diagram showing an example of a home screen during the childcare period. During the child-rearing period after the birth recognition unit 32 recognizes the birth, for example, when the user starts the maternal and child handbook application, the display control unit 20 first displays a home screen 450 shown in FIG. 9 on the display unit 15. May be displayed.

The display control unit 20 displays a home screen 450 on the display unit 15, which is partially different from the pregnancy home screen 400. ``Partially different'' between the UI (screen) during pregnancy and the UI (screen) during childcare period means that at least a portion of the UI (screen) during pregnancy and UI (screen) during childcare period are common. means that In the program according to the present disclosure, the pregnancy period display UI and the childcare period display UI, which are partially different, include a common component 421 that is common to each other. Common parts 421 include, for example, UI parts to which the same function is called for the same operation, UI parts with the same appearance, and UI parts with the same size and orientation at the same position on the display unit 15. The template may include at least one of the following: a model in which UI components are arranged.

For example, based on the above-mentioned common template, the layout of the UI components on the screen for inputting mother and child information is the same for the UI (screen) during pregnancy and the UI (screen) during childcare. It can be said that "at least part of the UI is common." For example, the operability of UI parts should be the same, that is, UI parts to which the same function called for the same operation is assigned should be used in both the UI (screen) during pregnancy and the UI (screen) during childcare. It can be said that "at least a part of the UI is common". For example, arranging a UI component having the same appearance on both the UI (screen) during pregnancy and the UI (screen) during childcare can be said to mean that "at least a portion of the UI is common."

As an example, like the home screen 400, the home screen 450 includes day progress information 401, a footer 402, and a nickname 407. Further, it is preferable that the arrangement of each of these UI parts is the same as that of the home screen 400 during pregnancy. A common portion between the home screen 400 and the home screen 450 is configured using a common component 421. As a result, the user can continue to use the maternal and child notebook application through the familiar UI even after the childcare period without being confused by changes in the appearance of the UI.

The home screen 450 for the childcare period is different from the home screen 400 for the pregnancy period in that the number of days progress information 401 is the age of the newborn baby, not the number of weeks of pregnancy. Another difference is that the screen called up by operating the BABY button 404 is not a pregnancy record display screen but a growth record display screen, which will be described later. Note that another difference is that, for example, the photo or illustration displayed below the nickname 407 may be changed.

FIG. 10 is a diagram showing an example of a growth record display screen. For example, in response to the user tapping the BABY button 404 during the childcare period, the childcare period display control unit 24 displays a growth record display screen 600, which is partially different from the pregnancy record display screen 500, on the display unit 15. do.

Like the pregnancy record display screen 500, the growth record display screen 600 includes day progress information 401, a display area 501, and a footer 402. The growth record display screen 600 may further include a sibling switching button 408, a medical checkup button 603, and the like. On the growth record display screen 600, an information input button 601 is arranged in place of the information input button 503. It is preferable that the arrangement of each of these UI components is the same as that of the pregnancy record display screen 500 during the pregnancy period. A common part between the pregnancy record display screen 500 and the growth record display screen 600 is configured using a common component 421. As a result, the user can continue to use the maternal and child notebook application through the familiar UI even after the childcare period without being confused by changes in the appearance of the UI.

The difference between the growth record display screen 600 during the childcare period and the pregnancy record display screen 500 during the pregnancy period is that the number of days progress information 401 indicates the age of the newborn baby instead of the number of weeks of pregnancy. Another difference is that the screen called up by operating the BABY button 404 is not the pregnancy record display screen 500 but the growth record display screen 600.

Furthermore, growth record display screen 600 differs from pregnancy record display screen 500 in that the graph arranged in display area 501 may be changed from the mother's weight to a graph showing the infant's height and weight. Furthermore, as a difference, in the display area 501 after being switched from the graph by the switching tab 505, a record of the child's vaccination may be displayed instead of the echo photograph of the fetus. In this way, the contents that are switched and displayed using the switching tab 505 are changed between the pregnancy period and the childcare period. However, "the switching tab 505 next to the record tab corresponding to the weight management graph corresponds to the history of medical care provided by medical institutions (echo photographs during pregnancy, medical examinations and vaccinations during childcare)." In this way, the screen layout can be made common. In this way, by making the layout of the UI parts for calling the functions of the maternal and child health notebook application the same for both the pregnancy period and the childcare period, users can easily manage the childcare period without being confused by the large changes in the content that needs to be managed. From then on, users can continue to use the maternal and child health notebook application via the familiar UI.

For example, when the user taps the switching tab 505 on the growth record display screen 600 shown in FIG. 10, the childcare period display control section 24 displays the growth record display screen 600 shown in FIG. 15 on the display section 15. In the growth record display screen 600 shown in FIG. 15, a display area 501 displays, for example, a child's vaccination record.

In another example, a child's photo may be displayed in the display area 501 after being switched by the switching tab 505. The child's photo displayed in the display area 501 may be a photo taken with a camera (not shown) of the smartphone 1, for example. In this way, the layout of the screens for the pregnancy period and the childcare period can be made the same in that "the switching tab 505 next to the record tab corresponding to the weight management graph corresponds to a list of photos of the baby." It can be done.

Furthermore, a difference is that instead of the information input button 503 for calling the pregnancy record input screen 550, the growth record display screen 600 has an information input button 601 (fourth UI part ) is placed.

In the program according to the present disclosure, the childcare period display UI includes a third UI component for instructing display of gestation period information, and a step of displaying a pregnancy record display screen 500 for displaying gestation period information. After the first operation is performed, (the first step) may be executed in response to the operation of the third UI component.

Specifically, as a further difference, a display instruction button 602 (third UI component) for calling up the pregnancy record display screen 500 may be provided instead of the recording end button 504. In this way, after the user performs the first operation for causing the control unit 10 to recognize the birth of a fetus, the pregnancy period display control unit 22 responds to the operation of the information input button 601 by A pregnancy record display screen 500 is displayed. Thereby, the user can easily review the records of the pregnancy period as needed even after the child-rearing period has started.

Further, in the program according to the present disclosure, the childcare period display UI includes a fourth UI component for instructing execution of a step (fourth step) of displaying a growth record input screen 650 that supports input of childcare period information. The fifth UI component for instructing the execution of the step (third step) of displaying the pregnancy record input screen 550 that supports the input of pregnancy period information, which was included in the pregnancy period display UI, is the first After the operation is performed, it may be deleted from the pregnancy period display UI.

Specifically, in the pregnancy record display screen 500 that is displayed after transitioning to the childcare period, the information input button 503 (fifth UI component) for calling the pregnancy record input screen 550 is deleted from the pregnancy record display screen 500. It is preferable that That is, after the child-rearing period, the display control unit 20 is configured so that the pregnancy record display screen 500 can be viewed, but the pregnancy record input screen 550 for inputting pregnancy period information is not called up.

Thereby, the user can be guided to input the gestational period information via the information input button 503 on the pregnancy record display screen 500. After transitioning to the childcare period, the user can be guided to input childcare period information from the growth record display screen 600. Furthermore, after transitioning to the child-rearing period, pregnancy record display screen 500 allows viewing of gestation period information while hiding the information input button 503, making pregnancy record entry no longer necessary during the child-rearing period. Guidance to screen 550 can be stopped. Therefore, it is possible to avoid guiding the user to unnecessary screens or confusing the user during the transition from the pregnancy period to the childcare period.

The growth record display screen 600 may further include a medical checkup button 603. The medical examination button 603 is a UI component for calling a screen (not shown) for supporting input of mother and child information related to infant medical examination.

FIG. 11 is a diagram showing an example of a growth record input screen. For example, in response to the user tapping the information input button 601 on the growth record display screen 600, the childcare period input support unit 23 displays a growth record input screen 650 that is partially different from the pregnancy record input screen 550 on the display unit. 15.

Like the pregnancy record input screen 550, the growth record input screen 650 includes, as UI parts, a text box for inputting measurement date, that is, date information, and a text box for inputting childcare period information. Text boxes for inputting child-rearing period information are arranged for each type of child-rearing period information. In addition to the infant's height and weight, a text box may be provided for inputting measurement results such as head circumference, chest circumference, etc.

Growth record input screen 650 may include a registration button 551 similarly to pregnancy record input screen 550. In response to the user inputting date information and child-rearing period information in the above-mentioned text box and operating the registration button 551, the information acquisition unit 31 acquires the input date information and child-rearing period information, It is stored in the mother and child information DB 41.

The arrangement of each of these UI parts is preferably the same as the pregnancy record input screen 550 for the pregnancy period. A common part between the pregnancy record input screen 550 and the growth record input screen 650 is configured using a common component 421. As a result, the user can continue to use the maternal and child notebook application through the familiar UI even after the childcare period without being confused by changes in the appearance of the UI.

<Processing flow>
FIGS. 12 and 13 are diagrams showing the flow of processing executed when the smartphone 1 equipped with the mother-child notebook application operates as a management tool for mother-child information. Specifically, the function to manage mother and child information before the birth of the child, that is, during the pregnancy period, is shown in Figure 12, and the function to manage mother and child information after the birth of the child, that is, during the childcare period, is shown in Figure 12. 13. The series of processes shown in FIG. 12 is started, for example, when the maternal and child notebook application is activated on the smartphone 1 during the pregnancy period.

In step S101, the display control unit 20 receives an operation to call up the pregnancy record display screen 500 from the user. For example, the operation (second operation) of tapping the BABY button 404 (first UI component) placed on the footer 402 of the screen of any of the applications shown in FIGS. 5 to 7 corresponds to the above-mentioned operation. When the BABY button 404 is tapped, the display control unit 20 proceeds from YES in S101 to S102. While the BABY button 404 is not tapped (NO in S101), the display control unit 20 waits for a tap operation on the BABY button 404 or executes other processing in response to operation of another UI component. You may also do so.

In step S102 (first step), the pregnancy period display control unit 22 displays a pregnancy record display screen 500 (gestation period display UI) on the display unit 15 for displaying pregnancy period information.

In step S103, display control unit 20 receives an operation to call pregnancy record input screen 550 from the user. For example, the operation of tapping the information input button 503 arranged on the pregnancy record display screen 500 shown in FIG. 6 corresponds to the above-mentioned operation. When the information input button 503 is tapped, the display control unit 20 proceeds from YES in S103 to S104. While the information input button 503 is not tapped (NO in S103), the display control unit 20 waits for a tap operation on the information input button 503, or proceeds to S107 and responds to the operation of another UI component. You may also perform other processing.

In step S104 (third step), the gestational period input support unit 21 displays on the display unit 15 a pregnancy record input screen 550 (gestational period input support UI) that supports input of gestational period information.

In step S105, the gestational period input support unit 21 determines whether gestational period information has been input. For example, the gestational period input support unit 21 inputs the gestational period based on the registration button 551 being tapped while various text boxes arranged on the pregnancy record input screen 550 shown in FIG. It may be determined that the information has been input. If the gestational stage information has been input, the control unit 10 proceeds from YES in S105 to S106. If the gestational period information is not input, for example, if the return button shown in FIG. 7 is tapped, the control unit 10 returns to S102 from NO in S105.

In step S106, the information acquisition unit 31 acquires the values input in the various text boxes described above as gestational period information, and registers them in the mother and child information DB 41.

In step S107, the display control unit 20 receives an operation to call the birth registration screen 350 from the user. For example, the operation of tapping the birth registration button 502 (second UI component) arranged on the pregnancy record display screen 500 shown in FIG. 6 corresponds to the above-mentioned operation. When the birth registration button 502 is tapped, the display control unit 20 proceeds from YES in S107 to S108. While the birth registration button 502 is not tapped (NO in S107), the display control unit 20 waits for a tap operation on the birth registration button 502, or proceeds to S119 and responds to operations on other UI parts. You may also perform other processing.

In step S108, the display control unit 20 displays a birth registration screen 350 for registering birth information on the display unit 15. Note that the display control unit 20 may display the birth registration screen 350 as a pop-up screen superimposed on the pregnancy record display screen 500, or as a separate screen from the pregnancy record display screen 500. 500 may be switched and displayed.

In step S109, the display control unit 20 determines whether birth information has been input. For example, the display control unit 20 determines that birth information has been input based on the registration button 352 being tapped while various boxes arranged on the birth registration screen 350 shown in FIG. 8 are filled with values. You may judge. If birth information has been input, the control unit 10 proceeds from YES in S109 to S110. If birth information is not input, for example, if the return button shown in FIG. 8 is tapped, the control unit 10 returns to S102 from NO in S109. That is, the display control unit 20 of the control unit 10 may close the pop-up upper layer birth registration screen 350 and return the lower layer pregnancy record display screen 500 to the active state. Alternatively, the display control unit 20 may switch the screen from the birth registration screen 350 to the pregnancy record display screen 500. Alternatively, the display control unit 20 may return to S101 and switch the screen from the birth registration screen 350 to the home screen 400.

In this manner, in this embodiment, the first operation for causing the control unit 10 to recognize the birth of a child does not consist only of the tap operation of the birth registration button 502. In this embodiment, as an example, tapping the registration button 352 with values entered in various boxes on the birth registration screen 350 corresponds to the first operation. However, in other examples, the tap operation on the birth registration button 502 may be the first operation.

In step S110, the information acquisition unit 31 registers the values entered in various boxes on the birth registration screen 350 as infant basic information 412 in the mother and child information DB 41.

In step S111, the birth recognition unit 32 recognizes the birth of a child that was managed as a fetus during pregnancy in response to the display control unit 20 receiving the first operation. The birth recognition unit 32 instructs the display control unit 20 to operate as a management tool for the childcare period. After this, the maternal and child notebook application can move from the pregnancy period to the childcare period and function as a management tool during the childcare period.

In step S112, the display control unit 20 may reconstruct the home screen 400 that was displayed during the pregnancy period so as to be suitable for management during the childcare period, if necessary. For example, the display control unit 20 configures the home screen 450 by changing a part of the home screen 400 to be suitable for managing the childcare period. As an example, after the first operation in S109 is performed, the display control unit 20 changes the footer 402 so that S114, which will be described later, is executed instead of S102 in response to a tap operation on the BABY button 404. .

In this way, from S109 onwards, when the mother-child health record application is started, the home screen 450 reconstructed in S112 is displayed instead of the home screen 400. A series of processes after S113 shown in FIG. 13 are started, for example, when the mother and child notebook application is activated in the smartphone 1 after the childcare period.

In step S113, the display control unit 20 receives an operation to call the growth record display screen 600 from the user. For example, the operation (second operation) of tapping the BABY button 404 (first UI component) placed on the footer 402 of the screen of any of the applications shown in FIGS. 9 to 11 corresponds to the above-mentioned operation. When the BABY button 404 is tapped, the display control unit 20 proceeds from YES in S113 to S114. While the BABY button 404 is not tapped (NO in S113), the display control unit 20 waits for a tap operation on the BABY button 404 or executes other processing in response to operation of another UI component. You may also do so.

In step S114 (second step), the childcare period display control unit 24 displays a growth record display screen 600 (childcare period display UI) on the display unit 15 for displaying childcare period information.

In step S115, the display control unit 20 receives an operation to call the growth record input screen 650 from the user. For example, the operation of tapping the information input button 601 arranged on the growth record display screen 600 shown in FIG. 10 corresponds to the above-mentioned operation. When the information input button 601 is tapped, the display control unit 20 proceeds from YES in S115 to S116. While the information input button 601 is not tapped (NO in S115), the display control unit 20 waits for a tap operation on the information input button 601, or proceeds to S121 and responds to an operation on another UI component. You may also perform other processing.

In step S116 (fourth step), the childcare period input support unit 23 displays on the display unit 15 a growth record input screen 650 (childcare period input support UI) that supports input of childcare period information.

In step S117, the childcare period input support unit 23 determines whether childcare period information has been input. For example, the child-rearing period input support unit 23 inputs the child-rearing period based on the registration button 551 being tapped while various text boxes arranged on the growth record input screen 650 shown in FIG. 11 are filled with values. It may be determined that the information has been input. If the childcare period information has been input, the control unit 10 proceeds from YES in S117 to S118. If the childcare period information is not input, for example, if the return button shown in FIG. 11 is tapped, the control unit 10 returns to S114 from NO in S117.

In step S118, the information acquisition unit 31 acquires the values input in the various text boxes described above as childcare period information and registers them in the mother and child information DB 41.

According to the above method, during the pregnancy period, S102 (first step) of displaying the pregnancy record display screen 500 in response to the user's tap operation (second operation) on the BABY button 404 (first UI component) is performed. executed. The gestation period is the period until the user performs the first operation for causing the control unit 10 to recognize the birth of a fetus. After the first operation is performed and the baby enters the childcare period, S114 (second step) of displaying the growth record display screen 600 is executed in response to a tap operation on the BABY button 404.

As a result, it is possible to realize a mother and child notebook application that can manage mother and child information (childcare period information) during the childcare period following management of mother and child information (gestation period information) during the pregnancy period. Specifically, during the pregnancy period, users can manage mother and child information using a convenient UI during the pregnancy period without being aware of the existence of the UI (screens and UI parts) used during the childcare period. can. After the user registers the birth in the maternal and child notebook application, the user can now call up the UI for the childcare period by using the same operation method for the same UI component as the UI for the pregnancy period.

In addition, the above-mentioned UI during the child-rearing period is only partially different from the UI during the pregnancy period, and the UI is at least partially common between the pregnancy period and the child-rearing period. For example, it is possible to use the same layout of UI components, the same screen design, and the same transition route for functionally identical screens during the pregnancy period and the childcare period (for example, inputting information from the information display screen). screen, etc.).

From the above, although the items to be managed and the functions required are different between the pregnancy period and the childcare period, the user does not need to change the operation method from the conventional method, and moreover, the user can use the UI that is familiar to them during the pregnancy period. You can continue to manage your childcare period information. Specifically, after the birth registration button 502 is operated and birth information is registered, the same tap operation on the same BABY button 404 will display the growth record display screen 600 instead of the pregnancy record display screen 500. Become. Therefore, the transition from the pregnancy period to the child-rearing period is carried out smoothly. As a result, a mother and child notebook application that is easy to use for the user is realized.

According to the above-described method, step S104 (third step) of displaying the pregnancy record input screen 550 (gestation stage input support UI) that supports input of gestational stage information, and growth record input that supports input of childcare stage information. A step S116 (fourth step) of displaying a growth record input screen 650 (childcare period input support UI) that is partially different from the pregnancy record display screen 500 (pregnancy period input support UI) is controlled. Further execution is performed in section 10.

As a result, the user can continue to input child-rearing period information using the same operations that the user is accustomed to from the pregnancy period, even regarding daily input operations for mother and child information. This eliminates the burden on the user to get used to new operations in order to manage the childcare period information.

More preferably, the smartphone 1 executes the following steps S119 to S122.

In step S119, the pregnancy period display control unit 22 receives an operation from the user instructing to stop inputting the pregnancy period information. For example, the operation of tapping the end recording button 504 arranged on the pregnancy record display screen 500 shown in FIG. 6 corresponds to the above-mentioned operation. When the recording end button 504 is tapped, the pregnancy stage display control unit 22 advances from YES in S119 to S120. While recording end button 504 is not tapped (NO in S119), display control unit 20 returns to S102 and maintains display of pregnancy record display screen 500.

In step S120, the pregnancy period display control unit 22 stops updating the pregnancy record display screen 500 as the current pregnancy week progresses. For example, the pregnancy period display control unit 22 may stop updating the number of days progress information 401 and the display area 501 and maintain the display contents at the time when the recording end button 504 was tapped. Specifically, the pregnancy stage display control unit 22 maintains the number of weeks of pregnancy and maintains the display of the month and day of the graph arranged in the display area 501.

In step S121, display control unit 20 receives an operation for calling pregnancy record display screen 500. For example, a case is assumed in which the BABY button 404 is tapped after the recording end button 504 is operated during the pregnancy period, or a case in which the display instruction button 602 is tapped during the childcare period. If these cases apply, the display control unit 20 proceeds from YES in S121 to S122.

In step S122, the pregnancy period display control unit 22 displays the pregnancy record display screen 500 with the display content at the time when the recording end button 504 was operated. Preferably, the pregnancy period display control unit 22 deletes the information input button 503 and the record end button 504 from the pregnancy record display screen 500 displayed after S119.

[Modified example]
(1) After transitioning from the pregnancy period to the child-rearing period, the objects to be managed may be divided into "mother" and "infant" and mother and child information may be managed for each. In this way, you can use a common UI that you are familiar with from the pregnancy stage to input information about the mother and infant during the childcare period, while also distinguishing between the mother and the infant and communicating with local governments and medical institutions. Collaboration can be strengthened. As an example, the smartphone 1 can receive notifications from an obstetric medical institution that are tailored to the mother's postpartum progress, and can also receive notifications from local governments that are tailored to the infant's progress.

(2) The information acquisition unit 31 determines whether the “date of delivery” input via the birth registration screen 350 is earlier than the “expected date of delivery” input during the pregnancy period via the new registration screen 300 by a predetermined value or more. It may be configured to determine whether or not. For example, if the actual delivery date is four weeks or more earlier than the expected delivery date (for example, if the baby is born before the gestational age of 36 weeks and 6 days), the information acquisition unit 31 may The method of processing the age in months may be different from the method of processing the age in months of a full-term infant.

Specifically, when the "date of delivery" is earlier than the "scheduled date of delivery", the information acquisition unit 31 determines the "date of delivery" for the age of the baby, in addition to the "actual age" based on the "date of delivery". The "corrected age in months" based on the "scheduled date" may be calculated and stored in the mother and child information DB 41.

Thereby, the control unit 10 can manage the child-rearing period information by properly using the "actual age" and the "corrected age in months" as necessary. For example, articles from local governments can be obtained according to the child's "actual age," and information matching the child's actual age can be collected. On the other hand, when comparing the child's growth level with a standard, information on the standard can be obtained based on the "corrected age," and an appropriate comparison can be made with an appropriate standard.

(2-1) Even if the baby is born before 36 weeks and 6 days, the baby is still large enough to be the same as a full-term baby, and the doctor or other judge determines that management based on corrected age is not necessary. , the value of the "corrected lunar age" may be discarded according to the user's operation.

(3) Each part of the control unit 10 is configured to utilize the information registered in the mother and child information DB 41 during the pregnancy period, without having to input unchanging information in the mother and child information DB 41 during the childcare period, among the mother and child information input during the pregnancy period; In particular, it is preferable to configure the display control section 20. For example, the item "gestational period" shown in FIG. 8 can be calculated based on the reference date (start date of last menstrual period, expected delivery date) acquired from the new registration screen 300 during the pregnancy period and the delivery date.

(4) The pregnancy period display control unit 22 may be configured to display echo photographs in chronological order in the display area 501 during the pregnancy period based on the number of weeks of pregnancy. Correspondingly, the childcare period display control unit 24 may be configured to display photos of the child taken with the smartphone 1 in chronological order in the display area 501 of the growth record display screen 600. In this way, the child's photos are displayed in chronological order during the child-rearing period as well as during the pregnancy period, based on the number of days progress information 401, so the user can enjoy viewing the child's growth record more happily. be able to. Even when displaying a list of photos, by making the UI common, the user can view photos of the child without feeling uncomfortable about the appearance of the screen, even when the user transitions from the pregnancy period to the childcare period.

As an example, the smartphone 1 can use a well-known face recognition function that utilizes artificial intelligence (AI), etc., and can identify a child's face in a photo stored in the smartphone 1 using the facial recognition technology. . The information acquisition unit 31 reads out from the storage unit 11 the photos that are identified as being of the child managed by the mother and child notebook application. The gestation period display control section 22 displays the photographs of the baby read out by the information acquisition section 31 in chronological order based on the photographing date. The pregnancy stage display control unit 22 may display the age in months calculated based on the date of delivery and the date of photography for each photograph.

(5) In the mother and child information DB 41, it is preferable that the mother and child information of children is held for each sibling. It is preferable that the home screen 400, the home screen 450, the pregnancy record display screen 500, and the growth record display screen 600 are created for each child. In this case, the display control unit 20 arranges on each screen a "sibling switching button" for switching the child to be managed. Thereby, the user can easily switch between the older brother's growth record display screen 600 and the younger brother's growth record display screen 600 by simply operating one "sibling switching button".

In this case, in the mother-child notebook application, a sibling ID for uniquely identifying multiple children (siblings) is issued for one user (mother). The child's mother and child information is managed in the mother and child information DB 41 in association with the sibling ID. Thereby, in the mother and child information DB 41, records such as weight and vaccination records can be managed for each child.

The mother and child information DB 41 shown in FIG. 3 has a data structure assuming that there is only one child. In an embodiment in which mother and child information is managed for each sibling, an item for sibling ID may be further provided in the mother and child information DB 41, and the sibling ID may be linked to each record of mother and child information.

(5-1) The childcare period display control unit 24 may be configured to display childcare period information for siblings at the same age in months side by side. For example, an older brother's photo, weight, and height when he was 6 months old and a younger brother's photo, weight, and height when he was 6 months old may be displayed side by side. As a result, users can enjoy managing their child-rearing period by comparing them, and can also view past records such as ``how things were with the older child'' and use them as a reference for how to handle the younger child's current situation. It can also be done.

(6) The control unit 10 may further include an article acquisition unit (not shown). The article acquisition unit acquires articles provided by local governments or medical institutions and notifications related to the articles according to the number of days progress information 401. Specifically, the article acquisition unit acquires articles from the management server 8 that match the current week of pregnancy during the pregnancy period, and the current age (or date of birth) of the child during the childcare period.

For example, a local government can attach a tag indicating the target audience to an article, such as "For children born between Reiwa*Year*Monday*Sunday and Reiwa*Year*Monday*Sunday," and send the article to the management server. Upload to 8. The management server 8 manages articles by associating them with local government IDs. The management server 8 distributes articles or notifications to the smartphones 1 of users whose conditions match the selected municipality and the child's number of days progress information 401. Thereby, the user can timely acquire and view articles according to the progress information 401 about the number of days of his/her child.

(6-1) The management server 8 may manage articles by linking them to categories. A category is information given to classify articles based on their content. For example, among articles published by a local government, an article about infant vaccinations may be associated with the category "vaccination-related." Furthermore, articles related to health checkups for infants may be associated with a category called "health checkup related." Then, the article acquisition unit may use "actual age" and "corrected age" to acquire articles from local governments by category. For example, the article acquisition unit may acquire articles in the category "vaccination-related" based on "actual age," and may acquire articles in the category "medical examination-related" based on "corrected age in months."

(7) It is also conceivable that the service provider recovers the development costs and operation and maintenance costs of the mother and child health recorder application from the user in the name of usage fees for the mother and child health recorder application. However, the present invention is not limited to this, and the service provider may construct a billing model that collects the above-mentioned costs from local governments and medical institutions. Thereby, the service provider can provide the mother and child notebook application to the user for free or at a low price.

Furthermore, specifically, a billing model will be constructed in which usage fees for the application as a management tool during the pregnancy period will be collected from the obstetric department, and usage fees for the application as a management tool during the childcare period will be collected directly from the user or from the pediatrician. It is also possible.

Collaboration with medical institutions (obstetrics), which was important during the pregnancy period, becomes less important after the childcare period begins. Therefore, it is difficult for obstetrics departments to recover the operating costs of services during the childcare period. Therefore, the operation costs for the service during the childcare period can be recovered directly from the user or from the pediatrician, thereby maintaining the operation.

Downloading and using a new application is a psychologically difficult task for users, especially if the application requires a fee. Therefore, in order to lower the psychological hurdles before using the maternal and child health notebook application for the first time, it is conceivable to make the mother and child health notebook application free of charge and encourage users to use it. On the other hand, by the time the user enters the child-rearing period, it is assumed that the user has become accustomed to the maternal and child notebook application, likes it, and uses it. Therefore, it is easy for a service provider to charge a user who has already used the maternal and child notebook application during pregnancy.

(8) The user may start using the maternal and child notebook application according to the present disclosure after giving birth. In this case, the display control unit 20 may provide a check box (not shown) on the new registration screen 300 to designate that it is after childbirth. Then, the display control unit 20 prompts the user to check the post-delivery checkbox instead of inputting the start date of the last menstrual period and the expected delivery date. For example, when the registration button at the bottom of the new registration screen 300 is pressed with the post-birth checkbox checked, the display control unit 20 next displays the birth registration screen 350 on the display unit 15. You may.

[Example of implementation using software]
The control blocks of the smartphone 1 (particularly the information acquisition unit 31, birth recognition unit 32, display control unit 20, and display control unit 20) are realized by logic circuits (hardware) formed on an integrated circuit (IC chip) or the like. or may be realized by software.

In the latter case, the smartphone 1 is equipped with a computer that executes instructions of a program that is software that implements each function. This computer includes, for example, one or more processors and a computer-readable recording medium that stores the above program. In the computer, the processor reads the program from the recording medium and executes the program, thereby achieving the object of the present invention. As the processor, for example, a CPU (Central Processing Unit) can be used. As the recording medium, in addition to "non-temporary tangible media" such as ROM (Read Only Memory), tapes, disks, cards, semiconductor memories, programmable logic circuits, etc. can be used. Further, the computer may further include a RAM (Random Access Memory) for expanding the above program. Furthermore, the program may be supplied to the computer via any transmission medium (communication network, broadcast waves, etc.) that can transmit the program. Note that one aspect of the present invention can also be realized in the form of a data signal embedded in a carrier wave, in which the program is embodied by electronic transmission.

The present invention is not limited to the embodiments described above, and various modifications can be made within the scope of the claims, and embodiments obtained by appropriately combining technical means disclosed in different embodiments. are also included within the technical scope of the present invention.

1 Smartphone (device)
2 Echo imaging device 3 Doctor terminal 4 Electronic medical record server 5 USB memory 6 Distribution server 7 Network 8 Management server 9 Local government terminal 10 Control section 11 Storage section 12 Connection section 13 Communication section 14 Operation section 15 Display section 20 Display control section 21 Pregnancy period Input support section 22 Pregnancy period display control section 23 Childcare period input support section 24 Childcare period display control section 31 Information acquisition section 32 Birth recognition section 300 New registration screen 350 Birth registration screen 404 BABY button (first UI component)
500 Pregnancy record display screen (pregnancy period display UI)
501 Display area 502 Birth registration button (second UI component)
503 Information input button (5th UI component)
504 Recording end button (6th UI part)
550 Pregnancy record input screen (gestational period input support UI)
600 Growth record display screen (childcare period display UI)
601 Information input button (4th UI component)
602 Display instruction button (3rd UI component)
650 Growth record input screen (childcare period input support UI)
S102 First step S104 Third step S114 Second step S116 Fourth step

Claims (12)

A program executed by a terminal comprising a control unit, a storage unit, and a display unit,
The program causes the control unit to
a first step of displaying on the display section a gestation period display UI for displaying gestation period information indicating information regarding at least one of a pregnant woman, a fetus, or a pre-fetus;
A childcare period display UI for displaying childcare period information indicating information regarding at least one of a multiparous woman and a child, the childcare period display UI partially different from the pregnancy period display UI being displayed on the display section. A second step of
Until the user performs a first operation for causing the control unit to recognize the birth of the fetus, the first step is performed in response to a second operation by the user on the first UI component displayed on the display unit. The program is executed, and after the first operation is performed, the second step is executed in response to the second operation on the first UI component. The program according to claim 1, wherein a second UI component for performing the first operation is included in the pregnancy period display UI. The childcare period display UI includes a third UI component for instructing display of the pregnancy period information,
3. The program according to claim 1, wherein the first step is executed in response to an operation of the third UI component after the first operation is performed. The program causes the control unit to
a third step of displaying a gestation period input support UI that supports input of the gestation period information;
A fourth step of displaying a child-rearing period input support UI that supports input of the child-rearing period information, the child-rearing period input support UI being partially different from the pregnancy period input support UI. The program described in any one of Items 1 to 3. The childcare period display UI includes a fourth UI component for instructing execution of the fourth step,
5. A fifth UI component for instructing execution of the third step, which was included in the pregnancy stage display UI, is deleted from the pregnancy stage display UI after the first operation is performed. The program described in. The storage unit stores the number of weeks of pregnancy or a reference date necessary for calculating the number of weeks of pregnancy,
According to claim 2, the first step includes changing the display mode of the second UI component so that the second UI component is highlighted when the number of weeks of pregnancy exceeds a predetermined number of weeks. Programs listed. The program according to claim 6, wherein the second UI component whose display mode has been changed is arranged so as not to overlap an area for displaying the pregnancy period information in the pregnancy period display UI. The pregnancy period display UI displayed in the first step includes a sixth UI component for instructing to finish inputting the pregnancy period information,
After the sixth UI component is operated, in the first step, updating of the display in the gestation period display UI is stopped as the number of weeks of pregnancy progresses, and the gestation period information whose input has been completed is displayed. The program according to claim 4 or 5, wherein: is maintained. The pregnancy period display UI and the childcare period display UI, which is partially different from the pregnancy period display UI, include common parts that are common to each other,
The common parts are
UI parts to which the same function is called for the same operation, and
The program according to any one of claims 1 to 8, comprising at least one of UI parts having the same appearance. The pregnancy period display UI and the childcare period display UI, which is partially different from the pregnancy period display UI, include common parts that are common to each other,
The common parts are
10. The program according to claim 1, further comprising a model in which UI components are arranged in the same position, size, and orientation on the display section. A method executed by a terminal comprising a control unit, a storage unit, and a display unit, the method comprising:
a first step of displaying on the display section a gestation period display UI for displaying gestation period information indicating information regarding at least one of a pregnant woman, a fetus, or a pre-fetus;
A childcare period display UI for displaying childcare period information indicating information regarding at least one of a multiparous woman and a child, the childcare period display UI being partially different from the pregnancy period display UI displayed on the display section. a second step of
The first step is performed in response to the user's second operation on the first UI component displayed on the display unit until the user performs the first operation for causing the control unit to recognize the birth of the fetus. The method is performed, and after the first operation is performed, the second step is performed in response to the second operation on the first UI component. A terminal comprising a control unit, a storage unit and a display unit,
The control unit includes:
Displaying on the display section a gestation period display UI for displaying gestation period information indicating information regarding at least one of the pregnant woman and the fetus or pre-fetus;
A childcare period display UI for displaying childcare period information indicating information regarding at least one of a multiparous woman and a child, the childcare period display UI being partially different from the pregnancy period display UI displayed on the display section. death,
The control unit includes:
Until the user performs a first operation for causing the control unit to recognize the birth of the fetus, the pregnancy period display UI is displayed in response to the user's second operation on the first UI component displayed on the display unit. display,
After the first operation is performed, the terminal displays the childcare period display UI in response to the second operation on the first UI component.

Images