JP7483415B2 - Program, method, terminal, and system - Google Patents

Description

The present invention relates to a program, method, and terminal for facilitating the management of fetal images and the like.

Currently, those who notify their pregnancy are issued a maternal and child health handbook by their local government. Important records relating to the mother and child from pregnancy through infancy can be entered into the handbook by the pregnant woman herself, a medical institution, or a local government welfare organization. In this way, the handbook makes it possible to manage a variety of information relating to the health of the mother and child from pregnancy through infancy in a single handbook.

In recent years, as shown in Patent Documents 1 and 2, information related to mothers and children, such as that managed in maternal and child health handbooks, has been digitized and managed.

JP 2014-191467 A (published on October 6, 2014) Patent No. 5033816 (issued September 26, 2012)

One example of information related to the health of mothers and children is an image of a fetus or pre-fetal state (hereafter referred to as a fetal image). Fetal images are generally called ultrasound images (photographs) or 4D images (photographs), and are medical information acquired when an obstetrician determines that they are necessary for diagnosis. On the other hand, fetal images also serve as a keepsake or record for pregnant women, allowing them to observe the progress of the fetus, get a feel for its growth, and share with their families.

As mentioned above, as the digitization of various information related to the health of mothers and children progresses, it is expected that pregnant women will be able to easily receive large numbers of digitized fetal images from medical institutions.

However, a wide variety of information required by obstetricians can be selectively added to fetal images, which are medical information, at the discretion of the obstetrician. Therefore, the format of fetal images provided by obstetricians is not fixed, and information on the number of weeks of pregnancy is not necessarily added. If information on the number of weeks of pregnancy is not added to fetal images, users will not be able to determine what number of weeks of pregnancy the fetus depicted in the fetal image is, making it difficult to manage a large number of fetal images. Here, a user is someone who receives fetal images from a medical institution and can handle the fetal images through their own terminal for information processing, and for example, pregnant women and their families are included in the "user".

One aspect of the present invention aims to realize a program or the like that allows a user, such as a pregnant woman, to easily handle images related to a fetus or pre-fetus.

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 having a control unit and a display unit, and the program causes the control unit to execute an image acquisition step of acquiring one or more images of a fetus or pre-fetus, a date acquisition step of acquiring date information associated with the images, a step of associating the number of weeks of pregnancy calculated based on the date information with the acquired images, and a display control step of displaying the images on the display unit together with the number of weeks of pregnancy associated with the images.

The program according to one aspect of the present invention may further cause the control unit to execute a storage step of storing the image associated with the number of weeks of pregnancy in a memory unit provided in the terminal.

In addition, in a program according to one aspect of the present invention, the display control step may include displaying the multiple images in order of the weeks of pregnancy associated with each image.

In addition, in a program according to one aspect of the present invention, the display control step may include displaying the most recent image of the fetus or pre-fetus, to which the most recent gestational age is associated, in a more emphasized manner than other images.

In a program according to one aspect of the present invention, the display control step may include displaying the newest image in the center of the display unit and displaying thumbnails of the other images around the newest image.

In a program according to one aspect of the present invention, the step of associating may include associating an image type for classifying images, determined according to the content depicted in the image, with the image, and the display control step may include displaying the image for each of the image types.

In a program according to one aspect of the present invention, the display control step may include displaying squares for placing the images for each week of pregnancy along a time axis until the expected delivery date, and placing the images in squares corresponding to the weeks of pregnancy associated with the images.

In addition, in a program according to one aspect of the present invention, the display control step may include selecting a certain number of representative images to be displayed on the display unit from among a plurality of images associated with the same date information.

In addition, in a program according to one aspect of the present invention, the display control step may include further displaying one or more other images associated with the same date information as the representative image when a specific operation by a user on an object related to the representative image is accepted by the terminal.

The program according to one aspect of the present invention may further cause the control unit to execute a comment editing step of editing a comment associated with the image in accordance with a user operation.

The program according to one aspect of the present invention may further cause the control unit to execute an image processing step of processing the image in accordance with a user operation.

In addition, in the program according to one aspect of the present invention, the image may be video data.

In order to solve the above-mentioned problems, a method according to one aspect of the present invention is a method executed by a terminal having a control unit and a display unit, and includes an image acquisition step of acquiring one or more images of a fetus or pre-fetus, a date acquisition step of acquiring date information associated with the images, a step of associating the number of weeks of pregnancy calculated based on the date information with the acquired images, and a display control step of displaying the images on the display unit together with the number of weeks of pregnancy associated with the images.

In order to solve the above-mentioned problems, a terminal according to one aspect of the present invention is a terminal equipped with a control unit and a display unit, in which the control unit acquires one or more images of a fetus or pre-fetus, acquires date information associated with the images, associates the number of weeks of pregnancy calculated based on the date information with the acquired images, and displays the images on the display unit together with the number of weeks of pregnancy associated with the images.

The terminal according to each aspect of the present invention may be realized by a computer, in which case the program according to each aspect of the present invention is a program that causes the computer to operate as each part (software element) of the terminal, thereby realizing the terminal on the computer. In addition, a computer-readable recording medium on which the 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, users can easily manage fetal images and the like.

1 is a block diagram showing a configuration of a main part of a smartphone according to an embodiment of the present invention; FIG. 13 is a diagram illustrating an application example of the program of the present disclosure. FIG. 4 is a diagram illustrating an example of a data structure of basic information. FIG. 2 is a diagram showing an example of a data structure of a fetal image database (DB). 11 is a flowchart showing the flow of processing executed by the smartphone. FIG. 13 is a diagram showing an example of a list display screen displayed on a display unit of the smartphone. FIG. 13 is a diagram showing an example of an image display screen displayed on a display unit of a smartphone. FIG. 13 is a diagram showing an example of an image processing screen displayed on a display unit of the smartphone. FIG. 13 is a diagram showing another example of a list display screen displayed on the display unit of the smartphone. FIG. 13 is a diagram showing yet another example of a list display screen displayed on the display unit of the smartphone. FIG. 13 is a diagram showing yet another example of a list display screen displayed on the display unit of the smartphone. FIG. 13 is a diagram showing yet another example of a list display screen displayed on the display unit of the smartphone. FIG. 13 is a diagram showing an example of an area expansion screen displayed on a display unit of a smartphone.

[Embodiment 1]
<Application Examples>
An embodiment of the present invention will be described in detail below. Fig. 2 is a diagram showing an application example of the program of the present disclosure.

The program of the present disclosure is installed in a user's terminal, and the terminal realizes a function based on the program of the present disclosure. The program of the present disclosure is, for example, a maternal and child health handbook application, and the terminal is, for example, a smartphone 1 (terminal) used by a user (e.g., a pregnant woman). The maternal and child health handbook application is, for example, distributed to each user's smartphone via a network 7 by a distribution server 6 that distributes applications developed by a service provider. When the maternal and child health handbook application is installed in the smartphone 1, the smartphone 1 operates as a terminal that realizes a function based on the program of the present disclosure, that is, a function for facilitating management of images related to a fetus or pre-fetus. In this specification, when an image related to a fetus or pre-fetus is expressed as a "fetal image" or simply expressed as a "fetal image," it is interpreted that the "fetal image" includes not only an image of a fetus, but also an image of a pre-fetal state. In addition, a pre-fetal state refers to, for example, a child in an embryonic state that is a human fetus up to the 8th week after fertilization, and a child in a state from the 8th week after fertilization until the child becomes a fetus.

The distribution server 6 may belong to the service provider that developed the maternal and child health handbook application, or to a distribution contractor that has been entrusted with distribution by the service provider.

In this embodiment, fetal images (images) provided by a medical institution are imported into a smartphone 1 of a pregnant woman on which a maternal and child health handbook application as a program of the present disclosure is installed. As an example, the fetal image is an echo image captured by an echo imaging device 2, and the echo image is still image data or video data. The video data may include audio data. The type of fetal image may be any of 2D images, 3D images, 4D images, and color images. Note that the smartphone 1 is not limited to being owned by the pregnant woman.

The means for importing the fetal image acquired by the echo imaging device 2 into the smartphone 1 is not particularly limited. The fetal image acquired by the echo imaging device 2 may be stored in an external recording medium such as a USB (Universal Serial Bus) memory 5, and the USB memory 5 may be inserted into the smartphone 1 to transfer the fetal image to the smartphone 1. In a medical institution, a doctor's 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 the fetal image to the smartphone 1 via a network 7. The echo imaging device 2 or the doctor's terminal 3 operated by the doctor during the examination may transmit the fetal image to the smartphone 1 via a short-range wireless communication means. Alternatively, the echo imaging device 2 or the doctor's terminal 3 operated by the doctor during the examination may be connected to the smartphone 1 by wire, and the fetal image may be transferred from the echo imaging device 2 or the doctor's terminal 3 to the smartphone 1. The fetal image may also be uploaded to a cloud consisting of a predetermined server such as the electronic medical record server 4 or other servers by the echo imaging device 2 or the doctor's terminal 3, etc. The smartphone 1 may then download fetal images of the pregnant woman who is the user of the smartphone 1 from among the fetal images uploaded to the cloud.

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

The operation unit 14 is an input device for accepting user operations. The operation unit 14 inputs an instruction signal corresponding to the accepted user operation to the control unit 10. As an example, the operation unit 14 may form a touch panel together with the display unit 15. The operation unit 14 is configured to include a device capable of detecting that a pointer such as a user's finger has come into contact with or approached 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 presents the information processed by the control unit 10 to the user in a manner that allows the information to be visually recognized. For example, the display unit 15 is configured with a liquid crystal display (LCD; Liquid Crystal Display) or an organic EL (Electro-Luminescence) display. For example, the display unit 15 displays fetal images, and user interface (UI) parts of a maternal and child health handbook application for easily managing fetal images.

The communication unit 13 communicates with external devices, such as the distribution server 6, via the network 7. 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 (CAble TeleVision) communication network, a satellite communication network, etc.

The connection unit 12 includes a terminal for connecting an external recording medium such as a 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 then read and erase data stored in the USB memory 5 and write data to the USB memory 5 via the connection unit 12.

The control unit 10 provides overall control over the operation of each part of the smartphone 1. The control unit 10 is made up of a computer device that includes, for example, 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 part of the smartphone 1 by reading and executing programs stored in the memory unit 11 for carrying out 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), etc. In the present embodiment, as an example, basic information 41 and a fetal image database (hereinafter, DB) 42 are stored in a non-volatile manner in the storage unit 11. The data structures of these data will be described in detail later.

<Software configuration of smartphone 1>
The control unit 10 of the smartphone 1 includes, for example, an image acquisition unit 21, a date acquisition unit 22, a management unit 23, an editing unit 24, and a display control unit 25. Each of these units is realized by the control unit 10 as, for example, a central processing unit (CPU) or the like reading out a program stored in a storage device such as a read only memory (ROM), specifically, a maternal and child health handbook application program, into a random access memory (RAM) or the like and executing the program.

The image acquisition unit 21 acquires one or more fetal images. The image acquisition unit 21 can acquire fetal images from an external device by any means. For example, the image acquisition unit 21 may acquire fetal images stored in a USB memory 5 connected via the connection unit 12. Alternatively, the image acquisition unit 21 may acquire fetal images received by the communication unit 13 from the echo imaging device 2, the doctor's terminal 3, or the electronic medical record server 4. The fetal images acquired by the image acquisition unit 21 are processed by the date acquisition unit 22 or the management unit 23.

The date acquisition unit 22 acquires date information associated with the fetal image acquired by the image acquisition unit 21. The date information of the fetal image is information indicating any date related to the fetal image. For example, the date information indicates, but is not limited to, the shooting date and time, update date and time, storage date and time, acquisition date and time, transmission date and time, and reception date and time.

In detail, the imaging date and time is the date and time when the ultrasound imaging device 2 captures the fetal image and obtains the fetal image. The update date and time is the date and time when the obstetrician updates the fetal image, such as by adding a marker or a diagnosis result, using the doctor terminal 3. The storage date and time is the date and time when the fetal image is saved in the ultrasound imaging device 2, the doctor terminal 3, the electronic medical record server 4, or the USB memory 5. The acquisition date and time is the date and time when the image acquisition unit 21 acquires the fetal image. The transmission date and time is the date and time when an external device such as the ultrasound imaging device 2, the doctor terminal 3, or the electronic medical record server 4 transmits the fetal image. The reception date and time is the date and time when the communication unit 13 of the smartphone 1 receives the fetal image from the external device.

The date acquisition unit 22 may extract date information from attribute information embedded in the fetal image acquired by the image acquisition unit 21. As an example, the fetal image is associated with the storage date and time when it is saved in the USB memory 5. The date acquisition unit 22 can acquire the storage date and time associated with the fetal image as date information. The storage date and time acquired by the date acquisition unit 22 is composed of information indicating the date saved in the USB memory 5 and the time saved (down to the second). It is considered that multiple fetal images are not saved in the same USB memory 5 at the same second. Therefore, the storage date and time acquired by the date acquisition unit 22 as date information can also be used as identification information for the fetal image.

Alternatively, the date acquisition unit 22 may separately acquire the date information associated with the fetal image via the connection unit 12 or the communication unit 13. The association between the fetal image and the date information may be achieved, for example, by using identification information that is unique to the pair of the fetal image and the date information. This allows the date acquisition unit 22 to accurately determine that the date information is date information related to the fetal image, even if the fetal image and the date information are acquired separately.

The management unit 23 manages the fetal images acquired by the image acquisition unit 21. In this embodiment, the management unit 23 performs appropriate processing on the fetal images to facilitate management. More specifically, as the above-mentioned appropriate processing, the management unit 23 associates the number of weeks of pregnancy calculated based on the reference date and the date information of the fetal image with the fetal image.

As an example, when multiple fetal images are imported from the USB memory 5 by the image acquisition unit 21, the management unit 23 calculates the number of weeks of pregnancy for each fetal image and stores each fetal image together with the calculated number of weeks of pregnancy in the fetal image DB 42. As described above, since the storage date and time acquired by the date acquisition unit 22 is unique to each fetal image, the management unit 23 may store the storage date and time together as identification information for the fetal image in the fetal image DB 42.

The management unit 23 calculates the number of weeks of pregnancy for each fetal image acquired by the image acquisition unit 21, assigns this number to the image, and registers it together with the storage date and time in the fetal image DB 42. This is repeated the number of times for the number of fetal image files transferred from the USB memory 5.

The reference date is a date that serves as a reference for calculating the number of weeks of pregnancy of a pregnant woman. As an example, the reference date includes at least one of the first day of the last menstrual period and the expected date of delivery. The reference date is, for example, stored in advance in the memory unit 11 as part of the basic information 41. The management unit 23 can calculate the number of weeks of pregnancy to be associated with a fetal image based on how many weeks and days away the date information corresponding to the fetal image is from the reference date. For example, the management unit 23 sets the first day of the last menstrual period read from the memory unit 11 to 0 weeks and 0 days of pregnancy, and if the date indicated by the date information is 70 days after the first day of the last menstrual period, calculates the number of weeks of pregnancy to 10 weeks and 0 days of pregnancy.

Alternatively, for example, the management unit 23 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 management unit 23 can set the date ten months and ten days before the expected delivery date input by the user based on the doctor's judgment as the conception date (reference date of 0 weeks and 0 days of pregnancy). The management unit 23 may then calculate the number of weeks of pregnancy from the difference between the conception date and the date information. With this configuration, it becomes possible to determine the number of weeks of pregnancy based only on the expected delivery date determined by the doctor, without the user having to input the start date of the last menstrual period.

The management unit 23 associates the calculated number of weeks of pregnancy with the fetal image described above. Furthermore, the management unit 23 may store the fetal image associated with the number of weeks of pregnancy in the memory unit 11. In this embodiment, the management unit 23 constructs a fetal image DB 42 for managing multiple fetal images associated with the number of weeks of pregnancy. This allows the user to easily manage and organize the fetal images based on the number of weeks of pregnancy, even if a large number of fetal images are stored in the memory unit 11.

In addition, according to the above-mentioned configuration, the fetal images are stored locally on the smartphone 1 (terminal), which reduces the risk of leaking personal information that should be protected, such as fetal images, compared to conventional systems in which fetal images are uploaded to the cloud, etc.

In this embodiment, the management unit 23 may further assign a tag indicating an image type for classifying the fetal image based on the image analysis result of the fetal image. The image type is information indicating a group of fetal images with common characteristics, which is determined according to the content captured in the fetal image. For example, in this embodiment, the image type is a format that includes a group of fetal images with common characteristics based on the data type, shooting angle, shooting target part, shooting method, etc. More specifically, the image type may be classified by shooting target part, such as "CRL (crown-rump length)", "BPD (bilateral diameter)", "face", "lower abdomen", "heartbeat", etc. Alternatively, the image type may be information indicating which data type the image belongs to, such as video data, still image data, audio data, 2D image, 3D image, 4D image, and color image. Identification of the shooting target part in the fetal image may be realized, for example, by introducing artificial intelligence (AI; Artificial Intelligence) that is good at image analysis. According to the above-mentioned configuration, the fetal images can be easily managed or organized based on the image type in addition to the number of weeks of pregnancy.

The editing unit 24 edits the fetal image in accordance with the user's operation. The editing process performed by the editing unit 24 on the fetal image includes filling in a comment entered by the user in a comment field that is added to the fetal image as additional information, and processing the fetal image in accordance with the user's operation. Processing of the fetal image includes, but is not limited to, correcting the color, contrast, or brightness of the fetal image, and decorating the fetal image by adding objects such as hand-drawn or prescribed patterns.

The display control unit 25 displays the fetal image on the display unit 15. In this embodiment, the display control unit 25 displays the fetal image stored in the fetal image DB 42 on the display unit 15 together with the number of weeks of pregnancy associated with the fetal image. As a result, the fetal image is displayed with enhanced visibility together with the number of weeks of pregnancy, allowing the user to easily manage the fetal image. Furthermore, the display control unit 25 may display UI components of the maternal and child health handbook application on the display unit 15. The UI components assist the user in performing operations to handle fetal images. As a result, the user can manage the fetal images even more easily.

By configuring the control unit 10 of the smartphone 1 as described above, fetal images can be easily managed on the smartphone 1 even if the format of the fetal images imported into the smartphone 1 (terminal) is not standardized.

<Data structure>
FIG. 3 is a diagram showing an example of the data structure of the basic information 41. The basic information indicates basic information about each pregnant woman that is unique to that pregnant woman. In the present embodiment, the basic information includes, as an example, at least a reference date for calculating the number of weeks of pregnancy. The reference date is, for example, the start date of the last menstrual period and the expected delivery date. The basic information is not limited to the reference date, and may include any information unique to each pregnant woman. For example, the basic information may include any basic information unique to a pregnant woman, such as race, blood type, medical history, vaccination history, commonly used medications, travel history, past delivery status for multiparous women, living environment, and working environment.

The display control unit 25 may display a UI component that assists in inputting basic information on the display unit 15. This allows a user, for example, a pregnant woman, to operate the UI component via the operation unit 14 and easily input her/his basic information into the smartphone 1.

Figure 4 is a diagram showing an example of the data structure of fetal image DB 42. Fetal image DB 42 consists of a collection of records, one of which is created for each fetal image. As shown in the figure, a record corresponding to the data of one fetal image is composed of attribute information, supplementary information, and the fetal image itself. This record is created by management unit 23.

The attribute information, for example, has a field for date information. The supplementary information, for example, has fields for image ID, number of weeks of pregnancy, image type, and comments.

The image ID field stores identification information for uniquely identifying the fetal image. The management unit 23 may store the image ID (e.g., the storage date and time) originally assigned to the fetal image acquired by the image acquisition unit 21 in this field as is, or may generate new unique identification information and store it in this field.

The date information item stores date information associated with the fetal image. The management unit 23 stores the date information of the fetal image acquired by the date acquisition unit 22 in this item.

The number of weeks of pregnancy corresponding to the fetal image is stored in the number of weeks of pregnancy field. The management unit 23 stores the number of weeks of pregnancy calculated based on the date information described above and the reference date shown in FIG. 3 in this field.

The image type item stores the image type of the fetal image. The management unit 23 determines the image type of the fetal image based on the results of image analysis of the fetal image performed by an image analysis unit (not shown) realized by AI or the like, and stores the image type in the item. For example, if the image analysis unit (not shown) determines that the fetal image is a cross-section of the skull to measure BPD (biparietal diameter), the management unit 23 determines the image type of the fetal image as "BPD (biparietal diameter)" and stores it in the item. The management unit 23 may also store information indicating the data type of the fetal image (video, still image, audio, 2D image, 3D image, 4D image, color image, etc.) in the item.

The comment item stores comments input by the user regarding the fetal image. When the editing unit 24 receives a user comment input regarding the fetal image via the operation unit 14, the editing unit 24 stores the received comment in the item. In another example, it is possible to define multiple fetal images as one group. In this case, the editing unit 24 may receive one comment from the user regarding multiple fetal images (i.e., one group).

In the fetal image DB 42, in addition to attribute information, additional information including each of the above items is attached to the fetal image, forming one record for each fetal image. According to the above data structure, each fetal image can be managed and organized based on the number of weeks of pregnancy or the image type. For example, the display control unit 25 can sort and display the fetal images by the number of weeks of pregnancy, or by image type. Furthermore, a user's comment can be attached to each fetal image. This allows the user to review the fetal images along with the comments they entered.

<Processing flow>
FIG. 5 is a flowchart showing the flow of processing executed by the smartphone 1.

In step S101, the image acquisition unit 21 acquires one or more fetal images. The image acquisition unit 21 may read the fetal images from the USB memory 5 via the connection unit 12, or may receive the fetal images from an external device via the communication unit 13.

In step S102, the date acquisition unit 22 acquires date information associated with the acquired fetal image. The date information may be included in the attribute information associated with the fetal image, or may be acquired separately from the fetal image together with the identification information of the fetal image.

In step S103, the management unit 23 calculates the number of weeks of pregnancy. For example, the management unit 23 may read the reference date stored as basic information 41 in the memory unit 11, and calculate the number of weeks of pregnancy depending on how many days after (or how many days before) the reference date is the date information acquired in S102.

In step S104, the management unit 23 associates the fetal image acquired in S101 with additional information. In this embodiment, the management unit 23 associates the number of weeks of pregnancy calculated in S103 as the additional information. In another example, the management unit 23 may determine an image type based on the image analysis results or file format of the fetal image, and associate the image type with the above-mentioned fetal image as additional information.

In step S105, the management unit 23 stores the above-mentioned fetal image in the storage unit 11 together with additional information such as the number of weeks of pregnancy. Specifically, in this embodiment, the management unit 23 generates a record related to the fetal image as shown in FIG. 4, and registers it in the fetal image DB 42.

In step S106, the display control unit 25 accepts an instruction to display a fetal image via the operation unit 14 (YES in S106).

In step S107, the display control unit 25 sorts the fetal images based on the associated weeks of pregnancy and displays them on the display unit 15. For example, the display control unit 25 displays the fetal images on the display unit 15 in descending order based on the weeks of pregnancy. More specifically, the display control unit 25 arranges the fetal images vertically in descending order of weeks of pregnancy, with the most recent fetal image at the top. It is preferable that the display control unit 25 displays each fetal image on the display unit 15 together with the weeks of pregnancy associated with each fetal image. Furthermore, if a comment is associated with each fetal image as supplementary information, it is preferable that the display control unit 25 displays each fetal image on the display unit 15 together with the comment associated with each fetal image.

<Screen example>
Fig. 6 is a diagram showing an example of a screen of the maternal and child health handbook application displayed on the display unit 15 of the smartphone 1. Specifically, the screen shown in Fig. 6 is a list display screen 300 for displaying a list of one or more fetal images imported into the smartphone 1. The display control unit 25 reads out the fetal images and various UI parts registered in the fetal image DB 42 from the storage unit 11, generates the list display screen 300, and displays it on the display unit 15.

The list display screen 300 includes at least an image display area 301 for sorting and displaying fetal images in order of the number of weeks of pregnancy. As an example, the image display area 301 includes a plurality of individual areas 302 for arranging information related to each fetal image. For example, one individual area 302 includes UI components such as a thumbnail 303 of the fetal image, date information 304, information on the number of weeks of pregnancy 305, and a details call button 306. Note that a thumbnail refers to a reduced image or a collection of multiple reduced images.

In the illustrated example, the fetal images are arranged in ascending order of gestational age, but in other examples, the display control unit 25 can sort multiple fetal images in descending order of gestational age and arrange them in descending order of gestational age.

The display control unit 25 references the fetal image DB 42 and generates an individual area 302 for each fetal image. The display control unit 25 arranges each individual area 302 in the image display area 301 in descending or ascending order of the number of weeks of pregnancy associated with each fetal image, and generates the list display screen 300.

The display control unit 25 displays the list display screen 300 generated as described above on the display unit 15 in the display control step of S107. This allows the display control unit 25 to display multiple fetal images, along with the gestational weeks associated with each image, in order of the gestational weeks.

The above-mentioned configuration allows fetal images to be viewed in chronological order, improving the visibility of fetal images and enhancing convenience.

In this embodiment, even if a large number of fetal images with inconsistent formats are imported into the smartphone 1, the fetal image DB 42 registers each fetal image with additional information on the number of weeks of pregnancy added to it based on the date information corresponding to the fetal image. Then, according to the above-mentioned configuration, each fetal image is displayed on the display unit 15 together with the number of weeks of pregnancy when the fetal image was captured.

This allows the user to know the number of weeks of pregnancy when each fetal image was taken via the list display screen 300, and allows the user to easily manage each fetal image based on the number of weeks of pregnancy.

The display control unit 25 may further place the image type of the fetal image in the individual area 302. In this way, the user can easily determine whether the fetal image is a still image or a video image, and which part of the fetus the fetal image depicts.

The display control unit 25 may also arrange individual areas 302 for each fetal image in the image display area 301 for each image type.

According to the above-mentioned configuration, fetal images can be easily managed based on image type (e.g., classification such as the part of the body photographed, or data type) in addition to the number of weeks of pregnancy.

For example, the display control unit 25 may arrange only fetal images taken from the side to measure the CRL (crown-rump length) in the image display area 301, sorting them by the number of weeks of pregnancy. In this way, the user can enjoy comparing only fetal images taken from the same shooting angle or the same part of the body, and understanding the fetal growth process step by step.

Figure 7 is a diagram showing an example of a screen of the maternal and child health handbook application displayed on the display unit 15 of the smartphone 1. Specifically, the screen shown in Figure 7 is an image display screen 320 for displaying fetal images and their associated information in detail, one by one. For example, when the user performs a specific operation on the detail call button 306 in one individual area 302 via the operation unit 14, the display control unit 25 generates an image display screen 320 for displaying the selected fetal image in detail, and displays it on the display unit 15 in response to the operation.

The image display screen 320 includes, as an example, the following UI components: a fetal image 321, a comment field 322, and an edit button 323.

The display control unit 25 arranges the fetal image 321, which is an enlarged version of the fetal image selected from the list display screen 300 shown in FIG. 6, on the image display screen 320. Here, the display control unit 25 may display supplementary information about the fetus by superimposing it on the fetal image 321. For example, the display control unit 25 may superimpose a head outline that identifies the position of the head in the fetal image, or a facial outline that identifies facial parts (eyes, mouth, nose, etc.) on the fetal image as supplementary information. Furthermore, the display control unit 25 may superimpose an arrow indicating the direction in which the fetus in the fetal image is facing. Alternatively, an arrow or letters indicating a direction such as "front", "back", "right", or "left" may be superimposed so that it is clear whether the fetus in the fetal image is the front, back, right side, left side, top, or bottom.

The display control unit 25 reads out the comment associated with the fetal image selected on the list display screen 300 from the fetal image DB 42 and places it in the comment field 322. If the comment field in the fetal image DB 42 is blank, the display control unit 25 displays the comment field 322 as blank.

It is preferable that the display control unit 25 place an edit button 323 on the image display screen 320 to assist the user in entering comments.

The editing unit 24 may be configured to execute a comment editing step of editing the comment associated with the fetal image in accordance with a user operation. Specifically, the editing unit 24 accepts a user operation for inputting a comment via the operation unit 14. Then, the editing unit 24 stores the input comment in the fetal image DB 42 in association with the fetal image.

For example, when the user performs a specific operation on the edit button 323 via the operation unit 14, the display control unit 25 may respond to the operation by displaying a UI component such as a software keyboard that assists in inputting characters on the display unit 15. When the user operates the software keyboard to input a comment, the editing unit 24 associates the input comment with a fetal image and stores it in the fetal image DB 42.

The above-mentioned configuration allows the user to record events, feelings, etc. in association with fetal images, and enjoy the fetal images as if they were a pregnancy diary.

It is preferable that the display control unit 25 place a processing button 324 on the image display screen 320 to assist the user in processing the fetal image.

The editing unit 24 may be configured to execute an image processing step in which the fetal image is processed in accordance with user operations.

For example, when the user performs a specific operation on the edit button 324 via the operation unit 14, the display control unit 25 may respond to the operation by displaying an image edit screen including UI components that assist in editing the fetal image on the display unit 15. When the user edits the fetal image via the image edit screen, the editing unit 24 updates the fetal image stored in the fetal image DB 42 by reflecting the edit content in the fetal image.

The above-mentioned configuration allows the user to process the fetal image as desired, further increasing the value of the fetal image as a keepsake for the user.

Figure 8 is a diagram showing an example of a screen of the maternal and child health handbook application displayed on the display unit 15 of the smartphone 1. Specifically, the screen shown in Figure 8 is an image processing screen 340 that includes UI components that support the processing of fetal images.

The image editing screen 340 includes, as an example, a fetus image 321, a palette 341, and a drawing tool 342 as UI components.

The fetal image 321 is the fetal image that the user selected as the object to be edited. The display control unit 25 places the fetal image 321 on the image editing screen 340 so that the drawing object created by the user can be superimposed and displayed.

Palette 341 and drawing tool 342 are UI components for assisting the user in creating drawing objects to be superimposed on fetal image 321. Palette 341 provides a function for coloring drawing objects. Drawing tool 342 provides a means for the user to create drawing objects. For example, drawing tool 342 may provide a function for generating a character string object corresponding to text data input by the user and superimposing it on fetal image 321. Alternatively, drawing tool 342 may provide a function for drawing a line object on a touch panel at a contact position of an indicator (finger or touch pen) operated by the user.

The user can manipulate the palette 341 and drawing tool 342 to superimpose a drawing object onto the fetal image 321 to process the fetal image.

In addition to those shown in FIG. 8, any UI component that provides image processing functionality, such as a cropping tool, stamp tool, etc., can be placed on the image processing screen 340.

As described above, according to the program disclosed herein, the control unit 10 of a terminal such as a smartphone 1 can execute an image acquisition step of acquiring one or more fetal images, a date acquisition step of acquiring date information associated with the fetal images, a step of associating the number of weeks of pregnancy calculated based on the date information and a reference date of at least one of the start date of the last menstrual period and the expected delivery date with the acquired fetal images, and a display control step of displaying the fetal images on the display unit 15 together with the number of weeks of pregnancy associated with the fetal images.

＜Effects＞
Although information on the number of weeks of pregnancy may be added to fetal images such as echo images obtained from the echo imaging device 2, a wide variety of information other than the number of weeks of pregnancy that is required by obstetricians may also be added. Therefore, the format of fetal images provided by obstetricians is not fixed, and information on the number of weeks of pregnancy is not always added. If the number of weeks of pregnancy is not added, it becomes difficult for users to manage the gradually accumulating fetal images.

However, with the above-mentioned configuration, the number of weeks of pregnancy can be calculated based on date information, such as the date and time of photography, associated with the fetal image, and the additional information on the number of weeks of pregnancy can be linked to each fetal image. This makes it possible to easily manage and organize each fetal image based on the number of weeks of pregnancy, even if the format of fetal images provided by medical institutions is not consistent.

[Modifications]
The display control unit 25 may display the latest fetal image (latest image) associated with the latest pregnancy week on the list display screen 300 in a more emphasized manner than the other fetal images.

According to the above configuration, even if multiple fetal images are displayed side by side, the most recent fetal image is always easily noticeable. As a result, the visibility of the fetal images is improved, and convenience is improved.

The highlighting of the latest fetal image is achieved, for example, by changing the display mode as follows, but is not limited to these. For example, the display control unit 25 may make the display size of the latest fetal image larger than that of other fetal images on the list display screen 300. Alternatively, the display control unit 25 may provide an individual area 302 only for the latest fetal image, and may display only thumbnails for the other fetal images. Alternatively, the display control unit 25 may always place the latest fetal image at the top of the image display area 301. Alternatively, the display control unit 25 may add a label such as a character string, illustration, icon, or badge that means "NEW", "new arrival", or "unread" to the individual area 302 of the latest fetal image. The display control unit 25 may erase the above-mentioned label added to the individual area 302 based on the passage of a predetermined period (for example, 1 to 2 weeks) from the time of new registration, or based on the user performing a touch operation on the individual area 302 with the label. Alternatively, the display control unit 25 may change the color of only the individual area 302 of the latest fetal image, or may blink only the individual area 302 of the latest fetal image.

For example, the display control unit 25 may position the most recent fetal image in the center of the display unit 15 on the list display screen 300, and position thumbnails of the other fetal images around the most recent fetal image.

With the above-mentioned configuration, the latest fetal image is displayed more prominently than previous fetal images, so that the latest fetal image is always easily noticeable to the user.

Figure 9 is a diagram showing an example of a screen of the maternal and child health handbook application displayed on the display unit 15 of the smartphone 1. Specifically, the screen shown in Figure 9 is another example of the list display screen 300.

As shown in FIG. 9, the display control unit 25 may place the latest fetal image 351 large in the center of the list display screen 300 so that the latest fetal image 351 is displayed in the center of the display unit 15. The display control unit 25 may then place thumbnails 352 of past fetal images older than the latest fetal image 351 so as to surround the latest fetal image 351 and be smaller in size than the latest fetal image 351. This allows the latest fetal image 351 to stand out even more than past fetal images.

The display control unit 25 may arrange the number of weeks of pregnancy 353 associated with the latest fetal image 351 so that the correspondence with the latest fetal image 351 is clear. For example, the latest fetal image 351 is arranged at the top of one egg-shaped object, and the number of weeks of pregnancy 353 is arranged at the bottom. This allows the user to check the latest fetal image 351 with good visibility, and also allows the user to intuitively recognize the number of weeks of pregnancy when the latest fetal image 351 was captured.

In addition, thumbnails of previous fetal images are displayed around the screen, allowing users to see at a glance the history and development of the fetus.

In addition, the display control unit 25 may arrange the squares for arranging the fetal images in the list display screen 300 for each pregnancy week along the time axis until the expected delivery date, and arrange the fetal images in the squares corresponding to the pregnancy weeks associated with the fetal images. The fetal images are arranged in a single path along the time axis without any branching from the square for the first pregnancy week in which the fetal images were obtained to the square for the last pregnancy week corresponding to the expected delivery date. However, the arrangement shape of the squares is not limited to a straight line, and may be a curved line or any non-geometric shape. The square for the first pregnancy week to the square for the last pregnancy week are generated as a continuous list display screen 300. However, the list display screen 300 may not fit on one screen of the display unit 15 of the smartphone 1. In this case, the display control unit 25 configures the list display screen 300 so that the entire screen can be displayed by a scroll operation. Note that the squares refer to blank spaces in which fetal images, etc. are to be arranged.

According to the above-mentioned configuration, not only individual areas 302 for placing fetal images that have already been acquired, but also individual areas 302 for placing fetal images that will be acquired in the future as the pregnancy progresses are provided in the image display area 301. This makes it possible to present the user with both the current situation and the path to the goal (due delivery date). As a result, users, particularly pregnant women, can enjoy filling in the squares with fetal images, and a tool can be realized that allows pregnant women to enjoy their pregnancy.

Figure 10 is a diagram showing an example of a screen of the maternal and child health handbook application displayed on the display unit 15 of the smartphone 1. Specifically, the screen shown in Figure 10 is yet another example of the list display screen 300.

As shown in FIG. 10, the display control unit 25 arranges the squares 361 in which the fetal images are arranged on the list display screen 300 for each week of pregnancy along the time axis until the expected delivery date. The squares 361 may be of any shape, and in the illustrated example, are formed in a footprint shape. The squares 361 do not have to be prepared one per week, but may be prepared for each predetermined number of weeks of pregnancy (for example, every two weeks, every three weeks, every four weeks, etc.). Alternatively, the display control unit 25 may arrange a predetermined number of squares 361 on the time axis from the start to the goal (expected delivery date). Then, each time a new fetal image is acquired, one fetal image per week of pregnancy may be assigned to one square 361 and arranged sequentially.

The display control unit 25 may arrange the line 362 representing the time axis as a visible object as shown. Alternatively, if the arrangement of the squares 361 can evoke in the user a path from the start to the goal that corresponds to the time axis, the display control unit 25 may not need to display the line 362.

In this way, the display control unit 25 can pre-position not only squares 361 for placing fetal images that have already been acquired, but also empty squares 361 for placing fetal images that are to be obtained in the future, up to the goal. Pregnant women can enjoy filling in the squares with fetal images by managing the fetal images using the list display screen 300 shown in FIG. 10. In this way, it is possible to provide pregnant women with a tool to help them enjoy their pregnancy.

The display control unit 25 may also select a predetermined number of representative fetal images to be displayed on the display unit 15 from among multiple fetal images associated with the same date information. In other words, even if multiple fetal images associated with the same date information are stored in the fetal image DB 42, the number of fetal images to be arranged for each pregnancy week on the list display screen 300 may be fixed. For example, even if five fetal images of a certain pregnancy week and three fetal images of another pregnancy week are stored in the fetal image DB 42, the number of representative fetal images to be arranged on the list display screen 300 may be set to two or one.

According to the above-mentioned configuration, the number of fetal images displayed for each week of pregnancy on the list display screen 300 is standardized. For example, the number of fetal images displayed for each week of pregnancy is standardized to one. As a result, even if the number of fetal images provided by medical institutions for each prenatal checkup is not uniform, the number displayed is standardized, so that a sense of uniformity can be created in the image display area 301 and the visibility of the sorted fetal images can be improved.

Figures 11 and 12 are diagrams showing an example of a screen of the maternal and child health handbook application displayed on the display unit 15 of the smartphone 1. Specifically, the screens shown in Figures 11 and 12 are yet another example of the list display screen 300.

In the list display screen 300 shown in FIG. 11, the area for arranging fetal images by gestational week is unified to an area for one thumbnail (e.g., thumbnail 303), similar to the list display screen 300 shown in FIG. 6.

However, when multiple fetal images are registered in the fetal image DB 42 for one pregnancy week, the display control unit 25 may divide the fixed area 371 for one thumbnail into small areas equal to the number of fetal images mentioned above.

As an example, if five fetal images at 12 weeks of pregnancy are registered in the fetal image DB 42, the display control unit 25 divides the fixed area 371 assigned to one week of pregnancy into five small areas and places the five fetal images described above in each of the small areas.

According to the above-mentioned configuration, the area used to display fetal images per pregnancy week is standardized to one thumbnail, but all fetal images associated with the corresponding pregnancy week can be displayed in a list. By maintaining a sense of uniformity in the display in this way, it is possible to display all fetal images registered in the fetal image DB 42 in a list without sacrificing the visibility of the list display screen 300.

Another example of the list display screen 300 is shown in FIG. 12. In the list display screen 300 shown in FIG. 12, as in FIG. 6, one individual area 302 is assigned to one week of pregnancy. Here, the difference from the list display screen 300 shown in FIG. 6 is that for a week of pregnancy for which multiple fetal images are registered, a multiple-image icon 372 is added to the individual area 302 for that week of pregnancy.

The multiple images icon 372 is a UI component for visually indicating that there are multiple fetal images of the same pregnancy week. When two or more fetal images are registered in the fetal image DB 42 for one pregnancy week, the display control unit 25 adds the multiple images icon 372 to the individual area 302 for that pregnancy week and places it on the list display screen 300.

According to the above-mentioned configuration, the area used to display fetal images per pregnancy week is unified to one individual area 302, but the multiple images icon 372 allows the user to perceive that multiple fetal images are registered for the corresponding pregnancy week. This allows the user, who perceives that multiple fetal images are registered, to perform an operation to display other fetal images other than the one currently being displayed as a representative. By maintaining a sense of uniformity in the display in this way, it becomes possible for the user to view all fetal images registered in the fetal image DB 42 without sacrificing the visibility of the list display screen 300.

In addition, in the list display screen 300 shown in FIG. 11, fetal images arranged in a small area at a very small size can be displayed larger by the display control unit 25 switching to the image display screen 320 shown in FIG. 7 in response to a user's operation of the detail call button 306. Alternatively, the display control unit 25 may display more detailed information about each fetal image by switching to the area expansion screen 390 shown in FIG. 13 (details will be described later) in response to a user's operation of the expansion instruction button 373.

Similarly, for fetal images that are not displayed on the list display screen 300 shown in FIG. 12, with only the multiple image icon 372 displayed, the display control unit 25 can switch to the image display screen 320 shown in FIG. 7 or the area expansion screen 390 shown in FIG. 13 to display the details.

Furthermore, when the display control unit 25 receives a specific operation by the user on an object related to the representative fetal image described above, the display control unit 25 may further display one or more other fetal images associated with the same date information as the representative fetal image. Objects related to the representative fetal image include, for example, a details call button 306 and an expansion instruction button 373 arranged in the fixed area 371 in FIG. 11 or the individual area 302 including the thumbnail 303 in FIG. 12.

For example, as shown in Figs. 11 and 12, the display control unit 25 hides the individual area 302 for displaying other fetal images having the same gestational age as the representative fetal image. Then, when a specific operation is performed on the representative fetal image, the display control unit 25 may expand and display the individual area 302 of the other fetal images having the same gestational age. Assumed examples of the specific operation described above include a double tap operation on the individual area 302, or a tap operation on the expansion instruction button 373 in the individual area 302.

The above-described configuration allows the user to view all fetal images obtained from medical institutions in an organized manner without compromising the visibility of the list display screen 300 when displaying a list in chronological order based on the number of weeks of pregnancy.

Figure 13 is a diagram showing an example of a screen of the maternal and child health handbook application displayed on the display unit 15 of the smartphone 1. Specifically, the screen shown in Figure 13 is an area expansion screen 390 after the hidden individual area 302 is expanded on the list display screen 300 shown in Figure 11 or Figure 12.

The display control unit 25 accepts a tap operation on the expansion instruction button 373 corresponding to, for example, one representative fetal image (fixed area 371 or thumbnail 303) on the list display screen 300 shown in FIG. 11 or FIG. 12. In response to accepting this tap operation, the display control unit 25 displays on the display unit 15 an area expansion screen 390 for expanding individual areas 302 for each of multiple fetal images that are linked to the same number of weeks of pregnancy as the selected fetal image.

The area expansion screen 390 includes, as an example, an expanded image display area 392 for arranging individual areas 302 of the remaining fetal images (hereinafter, non-representative images) that are linked to the same gestational week as the representative fetal image. In the expanded image display area 392, individual areas 302 corresponding to each of the non-representative images are arranged. If the non-representative images are associated with additional information such as a comment or image type, the display control unit 25 may arrange at least one of a comment 393 and an image type 394 in the individual areas 302 of those non-representative images.

According to the above-mentioned configuration, the user can call up the expanded image display area 392 to check in detail all of the fetal images taken at a particular pregnancy week by simply operating the UI component.

As shown, the display control unit 25 may form an indent by making the size (e.g., width) of the expanded image display area 392 smaller than the size of the image display area 301. In this way, when the expanded image display area 392 is expanded on the area expansion screen 390, the user can easily perceive that each fetal image in the expanded image display area 392 is a non-representative image subordinate to the representative fetal image. A non-representative image subordinate to the representative fetal image is, in other words, another fetal image taken at the same gestational week as the representative fetal image.

The display control unit 25 may provide a fold instruction button 391 in the individual area 302 of the representative fetal image. In response to the user operating the fold instruction button 391, the display control unit 25 may fold the expanded image display area 392 and return the display on the display unit 15 to the list display screen 300 of FIG. 11 or FIG. 12 again.

In another example, the display control unit 25 accepts a tap operation on the detail call button 306 corresponding to, for example, a representative fetal image (fixed area 371 or thumbnail 303) on the list display screen 300 shown in FIG. 11 or FIG. 12. In response to accepting this tap operation, the display control unit 25 displays an image display screen 320 (FIG. 7) of the selected representative fetal image. In addition, the display control unit 25 can place a UI component on the image display screen 320 for inputting an instruction to perform a similar display of other non-representative images that are linked to the same gestational week as the selected fetal image.

For example, when the display control unit 25 displays the image display screen 320 of the representative fetal image selected by the user, as shown in FIG. 7, the display control unit 25 places a guide icon 325 on the image display screen 320 indicating that there is a non-representative image that is linked to the same gestational week as the representative fetal image.

The display control unit 25 may accept, for example, a tap operation on the guide icon 325 or a left/right flick operation on any position on the image display screen 320 as an instruction to switch the display to a non-representative image. In response to such an operation, the display control unit 25 displays, on the display unit 15, an image display screen 320 for displaying a non-representative image of the same gestational week as the representative fetal image 321. If the non-representative image is accompanied by a comment different from that of the fetal image 321, the display control unit 25 also switches the display of the comment field 322 together with switching the fetal image.

In this way, the user can switch the image display screen 320 for each fetal image, allowing them to check in detail all of the fetal images taken at a particular week of pregnancy, by simply operating UI components such as the guide icon 325.

The fetal image may be video data. In this case, the display control unit 25 places thumbnails of a predetermined frame included in the video data in the individual area 302 on the list display screen 300. When the detail call button 306 of the displayed individual area 302 is tapped, the display control unit 25 displays an image display screen 320 as shown in FIG. 7 and plays a fetal image 321, which is video data. Here, an audio output control unit (not shown) may output audio data included in the video data from a speaker (not shown) of the smartphone 1. The audio data may include, for example, a recording of the fetal heartbeat, and the user can simultaneously check the fetus and the fetal heartbeat.

According to the above-mentioned configuration, the user can save the video, which gives a better understanding of the fetus than a still image, for memento or record purposes and play it back at any time. The user, especially the pregnant woman, can show the video data to family members who were unable to accompany her to the medical examination, and can share with them the excitement of seeing and hearing about the fetus.

[Software implementation example]
The control blocks of the smartphone 1 (in particular, the image acquisition unit 21, the date acquisition unit 22, the management unit 23, the editing unit 24, and the display control unit 25) may be realized by a logic circuit (hardware) formed in an integrated circuit (IC chip) or the like, or by software.

In the latter case, the smartphone 1 includes a computer that executes the instructions of a program, which is software that realizes each function. The computer includes, for example, one or more processors, and a computer-readable recording medium that stores the program. The object of the present invention is achieved by the processor reading the program from the recording medium and executing it in the computer. The processor can be, for example, a CPU (Central Processing Unit). The recording medium can be a "non-transient tangible medium," such as a ROM (Read Only Memory), tape, disk, card, semiconductor memory, programmable logic circuit, or the like. The smartphone 1 may also include a RAM (Random Access Memory) that expands the program. The program may be supplied to the computer via any transmission medium (such as a communication network or broadcast waves) that can transmit the program. One aspect of the present invention may 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 above-described embodiments, and various modifications are possible within the scope of the claims. The technical scope of the present invention also includes embodiments obtained by appropriately combining the technical means disclosed in different embodiments.

1. Smartphone (device)
2 Echo imaging device 3 Doctor terminal 4 Electronic medical record server 5 USB memory 6 Distribution server 7 Network 10 Control unit 11 Storage unit 12 Connection unit 13 Communication unit 14 Operation unit 15 Display unit 21 Image acquisition unit 22 Date acquisition unit 23 Management unit 24 Editing unit 25 Display control unit S101 Image acquisition step S102 Date acquisition step S104 Corresponding step S105 Storage step S107 Display control step

Claims (15)

A program executed by a terminal having a control unit and a display unit,
The program is
an image acquisition step of acquiring one or more images of the fetus or pre-fetus;
a date acquisition step of acquiring date information associated with the image;
A step of associating the date information and the calculated number of weeks of pregnancy based on a reference date that is a reference for calculating the number of weeks of pregnancy of a pregnant woman with the acquired image;
A display control step of displaying the image on the display unit together with the number of weeks of pregnancy associated with the image. The program is
The program according to claim 1 , further causing the control unit to execute a storing step of storing the image associated with the number of weeks of pregnancy in a storage unit included in the terminal. The program according to claim 1 or 2, wherein the display control step includes displaying a plurality of images in order of the weeks of pregnancy associated with each image. The program according to any one of claims 1 to 3, wherein the display control step includes displaying the latest image of the fetus or pre-fetus associated with the latest gestational age in a more emphasized manner than other images. The program according to claim 4, wherein the display control step includes displaying the newest image in the center of the display unit and displaying thumbnails of the other images around the newest image. The step of associating includes associating an image type for classifying the image, the image type being determined according to the content depicted in the image, with the image;
The program according to claim 1 , wherein the display control step includes displaying the images for each of the image types. The display control step includes:
Displaying the squares for arranging the images for each week of pregnancy along a time axis until the expected delivery date; and
The program according to claim 3 , further comprising arranging the image in a square corresponding to the week of pregnancy associated with the image. The program according to any one of claims 1 to 7, wherein the display control step includes selecting a certain number of representative images to be displayed on the display unit from among a plurality of images associated with the same date information. The program according to claim 8, wherein the display control step further includes displaying one or more other images associated with the same date information as the representative image when a specific operation by a user on an object related to the representative image is accepted by the terminal. The program is
The program according to claim 1 , further comprising causing the control unit to execute a comment editing step of editing a comment associated with the image in accordance with a user's operation. The program is
The program according to claim 1 , further causing the control unit to execute an image processing step of processing the image in accordance with a user's operation. The program according to any one of claims 1 to 11, wherein the image is video data. A method executed by a terminal having a control unit and a display unit,
an image acquisition step of acquiring one or more images of the fetus or pre-fetus;
a date acquisition step of acquiring date information associated with the image;
A step of associating the date information and the calculated number of weeks of pregnancy based on a reference date that is a reference for calculating the number of weeks of pregnancy of a pregnant woman with the acquired image;
and a display control step of displaying the image on the display unit together with the number of weeks of pregnancy associated with the image. A terminal including a control unit and a display unit,
The control unit is
obtaining one or more images of the fetus or pre-fetus;
Obtaining date information associated with the image;
The date information and the calculated number of weeks of pregnancy based on a reference date that is a reference for calculating the number of weeks of pregnancy of the pregnant woman are associated with the acquired image;
A terminal that displays the image on the display unit together with the number of weeks of pregnancy associated with the image. A system including a control unit and a display unit,
The control unit is
obtaining one or more images of the fetus or pre-fetus;
Obtaining date information associated with the image;
The date information and the calculated number of weeks of pregnancy based on a reference date that is a reference for calculating the number of weeks of pregnancy of the pregnant woman are associated with the acquired image;
The system displays the image on the display unit together with the pregnancy week number associated with the image.

Images