JP7253978B2 - Vaccination history management system, program, and control method of vaccination history management system - Google Patents

Description

The present invention relates to a vaccination history management system, a program, and a control method for the vaccination history management system.

For the vaccines given to infants, the recommended timing and number of vaccinations are determined for each type, taking into consideration the period until immunity is acquired and the age at which the disease is likely to become severe if contracted. Inoculation schedule management is complicated.

Therefore, various techniques have been developed to reduce the burden of vaccination schedule management (see Patent Document 1, for example).

In addition, various software for smartphones has been developed that can easily manage vaccination schedules and history, and the number of users has increased in recent years.

Japanese Patent Application Laid-Open No. 2014-096001

However, problems can arise when trying to leverage the inoculation history with multiple pieces of software. For example, when a child is vaccinated, medical institutions need to check the vaccination history each time. , the burden on medical institutions required for confirmation work is heavy.

The present invention has been made in view of such problems, and provides a vaccination history management system, a program, and a preventive medicine program that make it possible to facilitate the use of vaccination histories managed by a plurality of different types of software. It aims at providing the control method of an inoculation history management system.

A vaccination history management system according to an embodiment of the present invention enables a user terminal, which executes any one of a plurality of different types of applications for recording a user's vaccination history, to record the vaccination history recorded by the application. a storage unit for storing the plurality of vaccination histories received from the plurality of user terminals; a shaping unit for shaping the plurality of vaccination histories into a common format; a transmission unit for transmitting the obtained vaccination history to a medical institution terminal.

In addition, the problems disclosed by the present application and their solutions will be clarified by the descriptions in the description of the mode for carrying out the invention, the descriptions in the drawings, and the like.

It is possible to facilitate the use of vaccination histories managed by a plurality of different types of software.

1 is an overall configuration diagram of an information system including a vaccination history management system according to this embodiment; FIG. It is a figure which shows the hardware constitutions of the user terminal which concerns on this embodiment. It is a figure which shows the memory|storage device of the user terminal which concerns on this embodiment. It is a figure which shows the vaccination log|history which concerns on this embodiment. It is a figure which shows the vaccination log|history which concerns on this embodiment. It is a figure which shows the hardware constitutions of the medical institution terminal which concerns on this embodiment. It is a figure which shows the hardware constitutions of the vaccination log|history management system which concerns on this embodiment. It is a figure which shows the memory|storage device of the vaccination log|history management system which concerns on this embodiment. It is a figure which shows the vaccination log|history management table which concerns on this embodiment. It is a figure which shows the functional structure of the vaccination log|history management system which concerns on this embodiment. It is a flow chart which shows a flow of processing concerning this embodiment. It is a flow chart which shows a flow of processing concerning this embodiment. It is a figure which shows the example of a screen which concerns on this embodiment. It is a figure which shows the example of a screen which concerns on this embodiment.

At least the following matters will become apparent from the description of the present specification and the accompanying drawings. the following,
DETAILED DESCRIPTION OF THE INVENTION The present invention will be described in accordance with one embodiment thereof with reference to the accompanying drawings.

[First Embodiment]
== Overall configuration ==
FIG. 1 shows a vaccination history management system 300 and a medical institution terminal 2 according to one embodiment of the present invention.
00, an information system 10 including a first user terminal 100A and a second user terminal 100B
00 is shown. Vaccination history management system 300, medical institution terminal 200, first user terminal 100A, and second user terminal 100B are connected to the Internet or LAN (Local Area Network).
rk), and are connected so as to be able to transmit and receive data through a network 500 such as a telephone network.

The medical institution terminal 200 is a computer such as a server or personal computer owned by a medical institution such as a hospital or clinic.

The first user terminal 100A and the second user terminal 100B are terminals used by users to record vaccination histories. is a computer owned by a smartphone or mobile phone,
Portable information processing terminals such as notebook computers and tablets, personal computers used by users at home, and the like.

A first user terminal 100A is a computer owned by a first user, and a second user terminal 100B is a computer owned by a second user. Hereinafter, these are described as user terminals 100 when there is no need to distinguish and describe them.

Although two user terminals 100 are illustrated in FIG. 1, the number of user terminals 100 may be three or more.

A first vaccination management program 711A (hereinafter also referred to as a first application 711A or a first application 711A) is installed in the first user terminal 100A, and the first input by the first user is Vaccination history (first vaccination history 6
10A) are stored. Similarly, a second vaccination management program 711B (hereinafter referred to as a second application 711B or a second application 711B) is installed on the second user terminal 100B.
) is installed, and the second vaccination history (vaccination history 610B) entered by the second user is stored.

A first application 711A records a first vaccination history 610A in a first description format (first format) in the first user terminal 100A, and a second application 711B records a second vaccination history 610B. It is recorded in the second user terminal 10B in the second description style (second format).

Although the details will be described later, the first vaccination history 610A recorded in the first format is shown in FIG.
, and a second vaccination history 610B recorded in the second format is shown in FIG. In the present embodiment, the items to be recorded are different between the first format and the second format, and the contents to be recorded are different even for the same item (for example, vaccination).

In the following description, the first application 711A and the second application 711B are referred to as the application 711 when there is no need to distinguish between them. Similarly, the first vaccination history 6
10A and second vaccination history 610B are also described as vaccination history 610 when there is no need to distinguish them.

The vaccination history management system 300 receives and stores the vaccination history 610 recorded by the application 711 from various user terminals 100 and transmits the vaccination history 610 to the medical institution terminal 200 .

This aspect makes it possible to facilitate the use of vaccination histories 610 managed by a plurality of applications 711 of different types, such as confirmation, at a medical institution.

== user terminal ==
First, the user terminal 100 will be described with reference to FIG.

An example of a hardware configuration diagram of the user terminal 100 is shown in FIG. The user terminal 100 of this embodiment includes a CPU (Central Processing Unit) 110, a memory 120, a communication device 130
, a storage device 140 , an input device 150 , an output device 160 , and a recording medium reading device 170 .

The storage device 140 stores various programs and data such as a user terminal control program 710 executed or processed by the user terminal 100, an application 711, a vaccination history 610, and a vaccination history collection program 740 described later.

In this embodiment, as shown in FIG. 3, the storage device 140 of the first user terminal 100A stores a user terminal control program 710, a first application 711A, and a first vaccination history 6
10A, and vaccination history collection program 740 are stored. Although not shown, the storage device 140 of the second user terminal 100B contains a user terminal control program 710,
A second application 711B, a second vaccination history 610B, and a vaccination history collection program 740 are stored.

A user terminal control program 710 stored in the storage device 140, an application 711,
Various functions of user terminal 100 are implemented by reading vaccination history collection program 740 or various data into memory 120 and executing or processing by CPU 110 .

Here, the storage device 140 is a nonvolatile storage device such as a hard disk, SSD (Solid State Drive), flash memory, or the like.

The user terminal control program 710 is a program for controlling the user terminal 100,
For example, it is embodied by an OS (Operating System) and various libraries.

The application 711 is a program for the user to manage vaccination schedules and records. program, etc.

As described above, there are various types of applications 711, and each application 711 manages data in its own format.

For example, FIG. 4 shows the first vaccination history 610A managed by the first application 711A. The first application 711A displays a screen such as that shown in FIG. 13 on the first user terminal 100, for example.
A, input of vaccination history information is received from the first user, and this history information is stored in the storage device 140 of the first user terminal 100A as the first vaccination history 610A shown in FIG. do.

Also, for example, FIG. 5 shows a second vaccination history 610B managed by the second application 711B. The second application 711B displays, for example, a screen as shown in FIG.
B, input of vaccination history information is received from the second user, and this history information is stored in the storage device 140 of the second user terminal 100B as the second vaccination history 610B shown in FIG. do.

In the present embodiment, the vaccination history 610 recorded in the storage device 140 is the history of vaccinations received by the user's (guardian's) child. will be described as the user's vaccination history 610 because is normal. Of course, the embodiment may be such that the user records his or her vaccination history 610 in the user terminal 100 .

The vaccination history collection program 740 is a program that implements the function of transmitting the vaccination history 610 stored in the storage device 140 to the vaccination history management system 300 . The vaccination history collection program 740 transmits the vaccination history 610 stored in the user terminal 100 to the vaccination history management system 300, for example, after obtaining the consent of the user.

At this time, the vaccination history collection program 740 may receive input of information specifying a medical institution that discloses the vaccination history 610 . In this case, the user terminal 100
transmits the vaccination history 610 to the vaccination history management system 300 together with the information specifying the medical institution. Although the details will be described later, the vaccination history management system 300 stores this vaccination history 610 in association with the information specifying the medical institution, and stores the vaccination history 610 of this user.
10 to the medical institution terminal 200, it is transmitted only to the specified medical institution terminal 200. FIG. This aspect allows the user's vaccination history 610 to be disclosed only to specific medical institutions, such as primary care physicians. Note that the user terminal 1
00 to the vaccination history management system 300 may or may not be transmitted at the same time as the vaccination history 610 is transmitted. That is, the medical institution designation information may be transmitted in advance before the vaccination history 610 is transmitted, or may be transmitted after the vaccination history 610 is transmitted.

The recording medium reading device 170 reads the user terminal control program 710 , the application 711 , the vaccination history collection program 740 , or various data recorded on the recording medium 800 such as an SD card, and stores them in the storage device 140 .

The communication device 130 communicates with the medical institution terminal 200, the vaccination history management system 300, or other computers (not shown), various data, a user terminal control program 710, a vaccination history collection program 740, and an application 711 via a network 500. Give and receive. For example, the above-described user terminal control program 710 and various data, the vaccination history collection program 740, or the application 711 are stored in another computer, and the user terminal 10
0 can download the user terminal control program 710, data, vaccination history collection program 740, and application 711 from this computer.

The input device 150 includes various buttons and switches for receiving commands and data input by the user, a keyboard, a touch sensor for detecting a touch position on the touch panel display, an input interface such as a microphone, an acceleration sensor, a temperature sensor, a GPS receiver, and so on. They are a position detection sensor such as a compass, a camera, and the like.

The output device 160 is, for example, a display device such as a display, a speaker, a vibrator, an output user interface such as lighting.

== Medical institution terminal ==
The medical institution terminal 200 is used in a medical institution and includes at least a user's vaccination history 610
It is a terminal used for browsing. As shown in FIG. 6, CPU 210, memory 220
, a communication device 230 , a storage device 240 , an input device 250 , an output device 260 and a recording medium reading device 270 . The hardware configuration of these medical institution terminals 200 is as follows:
Although not necessarily the same as the hardware configuration of the user terminal 100, the basic configuration is common. Therefore, redundant description of these hardware configurations will be omitted.

Various programs such as a medical institution terminal control program 720 executed by the medical institution terminal 200 and data are stored in the storage device 240 of the medical institution terminal 200 .

The medical institution terminal control program 720 and various data stored in the storage device 240 are read out to the memory 220 and executed or processed by the CPU 210,
Various functions of the medical institution terminal 200 are realized.

For example, the medical institution terminal 200 receives the vaccination history 610 acquired from the user terminal 100 by the vaccination history management system 300 and outputs it to the output device 260 .

== Vaccination history management system ==
Next, the vaccination history management system 300 will be described with reference to FIGS. 7 to 10. FIG.

FIG. 7 shows the hardware configuration of the vaccination history management system 300. As shown in FIG. However, since the vaccination history management system 300 also has the same basic configuration as the medical institution terminal 200 and the user terminal 100, redundant description will be omitted.

In the storage device 340, as shown in FIG. 8, a vaccination history management system control program 73
0 and a vaccination history management table 630 are stored.

Vaccination history management system control program 730 and various data stored in storage device 340 are read into memory 320 and executed or processed by CPU 310, thereby realizing various functions of vaccination history management system 300. be.

<Vaccination history management table>
FIG. 9 shows an example of the vaccination history management table 630. As shown in FIG. Vaccination history management table 6
A table 30 stores a plurality of vaccination histories 610 received from a plurality of user terminals 100 .

In FIG. 9, first vaccination history 610A received from first user terminal 100A and second vaccination history 610B received from second user terminal 100B are stored in vaccination history management table 630. is shown.

As can be seen by comparing the first vaccination history 610A shown in FIG. 4, the second vaccination history 610B shown in FIG. 5, and the vaccination history management table 630 shown in FIG. As an example, the vaccination history management table 630 according to this embodiment has the same first description style (first format) as the first vaccination history 610A.

For this reason, the first user terminal 100 can be accessed in the first format by the first application 711A.
While the first vaccination history 610A recorded in A is stored in the vaccination history management table 630 as it is, it is recorded in the second format in the second user terminal 100B by the second application 711B. For the second vaccination history 610B, the first
It is stored in the vaccination history management table 630 in a state shaped so as to conform to the format.

Specifically, in the second vaccination history 610B, for the vaccination history management table 630, "application name", "name", "age", "address at the time of vaccination (zip code)", "local government name at the time of vaccination", " Vaccine Product Code", "Period", "Time", "Regular/Optional", and "Vaccination Medical Institution Name" are not included. There is no item of "Vaccine Manufacturer" and "Vaccination Medical Institution Name/Doctor Name".

In addition, in the "vaccine to be administered" column, in the case of the first format, information specifying the vaccine such as the name of the bacteria targeted by the vaccine is described, but in the case of the second format, as shown in FIG. In addition to the information that specifies the number of vaccinations, the number of vaccinations out of the total number of vaccinations is also described.

Due to such a difference, first, the vaccination history management table 630 is blank for data items not included in the second vaccination history 610B.

However, "age" is described as data calculated from the date of birth by the vaccination history management system 300. FIG. Also, for "period" and "time", the second vaccination history 6 in FIG.
From the description of the bacterium name in the "vaccine vaccination" column of 10B and the description of the number of times of vaccination among the total number of times of vaccination, based on the vaccine information database (not shown) in the vaccination history management system 30 " and "times" are identified and described in the vaccination history management table 630 .

As for "regular/optional", the vaccination history management system 30 specifies whether it is a routine vaccine or an optional vaccine from the description in the "vaccine" column of the second vaccination history 610B. It is written in the inoculation history management table 630 .

In addition, the second vaccination history 610B in FIG. Only the medical institution name is extracted and written in the vaccination history management table 630 .

<Functional configuration>
Next, FIG. 10 shows an example of a functional block diagram of the vaccination history management system 300. As shown in FIG. The vaccination history management system 300 according to this embodiment includes a receiving unit 301, a storage unit 302, and a transmitting unit 303.
, including the functions of the shaping unit 304 .

Each of these functions is implemented by the hardware of the vaccination history management system 300 executing the vaccination history management system control program 730 according to the present embodiment.

The receiving unit 301 includes a plurality of different types of applications 7 that record the user's vaccination history 610.
11, the vaccination history 610 recorded by the application 711 is received.

For example, the receiving unit 301 receives the first vaccination history 610A from the first user terminal 100A executing the first application 711A, and receives the second vaccination history 610A from the second user terminal 100B executing the second application 711B. Receive vaccination history 610B.

Formatter 304 formats multiple vaccination histories 610 into a common format. For example, in the present embodiment, the first format is used as a common format as described above, and the shaping unit 304 converts the second vaccination history 610B in the second format obtained by the receiving unit 301 from the second user terminal 100B into Format to the first format.

The shaping unit 304 can perform this shaping, for example, by referring to a predetermined rule (not shown) for shaping from the second format to the first format.

The shaping unit 304 can also perform shaping into a common format for formats other than the first format and the second format by referring to rules for shaping into a common format.

Further, the shaping unit 304 does not set the first format as a common format,
The second format may be the common format, or a format other than the first format and the second format may be the common format.

The common format may be a format conforming to any one of the applications 711 executed on the user terminal 100, or may be a format different from the format conforming to any of the applications 711. FIG.

The storage unit 302 stores a plurality of vaccination histories 610 received from a plurality of user terminals 100 . In this embodiment, the storage unit 302 is embodied as a vaccination history management table 630, and stores the vaccination history 610 in the first format.

The transmission unit 303 transmits the vaccination history 610 stored in the storage unit 302 to the medical institution terminal 200.
Send to

In this manner, each user's vaccination history 610 is transmitted to the medical institution terminal 200 in a common format, facilitating the use of the vaccination history 610 managed by a plurality of applications 711 of different types. It becomes possible to

Furthermore, the user terminal 100 is configured to transmit the vaccination history 610 together with the medical institution designation information to the vaccination history management system 300, and the receiving unit 301 receives the user terminal 1
00, together with the vaccination history 610, the medical institution designation information designating the transmission destination of the vaccination history 610 may be received.

In this case, the storage unit 302 stores the vaccination history 610 in association with the medical institution designation information, and the transmission unit 303 transmits the vaccination history 610 only to the medical institution terminal 200 specified by the medical institution designation information. make sure to In this manner, the user's vaccination history 610 can be disclosed only to a specific medical institution designated by the user, such as a family doctor.

The transmission of the medical institution designation information from the user terminal 100 to the vaccination history management system 300 may or may not be simultaneous with the transmission of the vaccination history 610 .

== Process flow ==
Next, FIG. 11 shows the flow of processing by the vaccination history management system 300 according to this embodiment.
will be described with reference to.

First, the first user terminal 100A transmits the first vaccination history 610A of the first user to the vaccination history management system 300 (S1000).

The vaccination history management system 300 formats this first vaccination history 610A into a common format (S1010). However, since the first vaccination history 610A is in the first format, which is the same as the common format, the vaccination history management system 300 does nothing in S1010.

Vaccination history management system 300 stores this first vaccination history 610A in vaccination history management table 630 (S1020).

On the other hand, the second user terminal 100B transmits the second vaccination history 610B of the second user to the vaccination history management system 300 (S1030).

The vaccination history management system 300 formats this second vaccination history 610B into a common format (S1040). Specifically, the vaccination history management system 300 formats the second vaccination history 610 described in the second format into a common format by referring to format conversion rules (not shown).

Then, the vaccination history management system 300 stores this second vaccination history 610B in the vaccination history management table 630 (S1050).

Subsequently, the first user terminal 100A sends the vaccination history management system 300 a first
to the medical institution terminal 200 (S1060). In this transmission request, the first user sends the first user terminal 100
The medical institution designation information entered in A is included.

Then, the vaccination history management system 300 refers to the vaccination history management table 630 and transmits the first user's vaccination history 610A to the specified medical institution terminal 200 (S1070).

The medical institution terminal 200 then outputs the first vaccination history 610A to the output device 260 (S1080).

On the other hand, the second user terminal 100B requests the vaccination history management system 300 to
to the medical institution terminal 200 (S1090). In this transmission request, the second user terminal 100
The medical institution designation information entered in B is included.

Then, the vaccination history management system 300 refers to the vaccination history management table 630 and transmits the second user's vaccination history 610B to the specified medical institution terminal 200 (S1100).

The medical institution terminal 200 then outputs the second vaccination history 610B to the output device 260 (S1110).

According to this aspect, the vaccination history 610 of each user managing the vaccination history 610 using various applications 711 can be output to the medical institution terminal 200 in a common format. In this way, by unifying and handling the format of the vaccination history 610 managed by a plurality of applications 711 of different types, the vaccination history 610
It is possible to easily use such as confirmation of

Note that FIG. 11 illustrates a flowchart in the case where the first user and the second user designate the same medical institution as the destination of the vaccination history 610, but when different medical institutions are designated Then, the vaccination history management system 300 transmits the vaccination history 610 to the designated medical institution terminals 200 .

[Second embodiment]
In the first embodiment, the vaccination history management system 300 includes the formatting unit 304, and the formatting unit 304 formats the plurality of vaccination histories 610 into a common format. The management system 300 does not include the shaping unit 304, and each user terminal 10
The vaccination history collection program 740 run by 0 formats the vaccination history 610 into a common format.

The vaccination history collection program 740, for example, when the user terminal 100 collects the vaccination history 61
0 to the vaccination history management system 300, the vaccination history 610 is formatted into a common format.

Then, the vaccination history management system 300 receives, from a plurality of user terminals 100,
A vaccination history 610 formatted in a common format is received, a plurality of vaccination histories 610 formatted in the common format are stored in a vaccination history management table 630, and a common format stored in the vaccination history management table 630 is stored. The formatted vaccination history 610 is transmitted to the medical institution terminal 200 .

According to this aspect as well, the vaccination history 610 of each user managing the vaccination history 610 using various applications 711 can be output to the medical institution terminal 200 in a common format. This makes it possible to unify and easily confirm vaccination histories 610 managed by a plurality of applications 711 of different types.

The flow of processing will be described below with reference to FIG.

First, the first user terminal 100A formats the first user's first vaccination history 610A into a common format (S2000). However, since the first vaccination history 610A is in the first format, which is the same as the common format, the first user terminal 100A does nothing in S2000.

The first user terminal 100A then transmits the first vaccination history 610A to the vaccination history management system 300 (S2010).

The vaccination history management system 300 stores this first vaccination history 610A in the vaccination history management table 630 (S2020).

On the other hand, the second user terminal 100B formats the second user's second vaccination history 610B into a common format (S2030). Specifically, the second user terminal 100B formats the second vaccination history 610B described in the second format into a common format by referring to format conversion rules (not shown).

The second user terminal 100B then transmits the vaccination history 610B of the second user to the vaccination history management system 300 (S2040).

Then, the vaccination history management system 300 stores this second vaccination history 610B in the vaccination history management table 630 (S2050).

Subsequently, the first user terminal 100A sends the vaccination history management system 300 a first
to the medical institution terminal 200 (S2060). In this transmission request, the first user sends the first user terminal 100
The medical institution designation information entered in A is included.

Then, the vaccination history management system 300 refers to the vaccination history management table 630 and transmits the first user's first vaccination history 610A to the specified medical institution terminal 200 (S2070).

The medical institution terminal 200 then outputs the first vaccination history 610A to the output device 260 (S2080).

On the other hand, the second user terminal 100B requests the vaccination history management system 300 to
to the medical institution terminal 200 (S2090). In this transmission request, the second user terminal 100
The medical institution designation information entered in B is included.

Then, the vaccination history management system 300 refers to the vaccination history management table 630 and transmits the second user's second vaccination history 610B to the specified medical institution terminal 200 (S2100).

The medical institution terminal 200 then outputs the second vaccination history 610B to the output device 260 (S2110).

This aspect also makes it possible to facilitate the use of, for example, confirmation of vaccination history 610 managed by a plurality of applications 711 of different types.

[Third embodiment]
In the first and second embodiments, the user terminal 100 executes the vaccination history collection program 740 to transmit the vaccination history 610 stored in the user terminal 100 to the vaccination history management system 300. However, in the third embodiment, the user terminal 10
0 does not use the vaccination history collection program 740, and displays a screen shot of a state in which the vaccination history 610 is displayed on the screen of the user terminal 100 as shown in FIGS. Send to history management system 300 .

In this case, the receiving unit 301 of the vaccination history management system 300 acquires the vaccination history 610 as characters in the image by receiving the screen shot from the user terminal 100 .

Then, the shaping unit 304 of the vaccination history management system 300 extracts the characters of the vaccination history 610 from the image acquired from the user terminal 100, and then shapes the characters into a common format.

For example, the vaccination history management system 300 asks the user the name of the application that the user is using, or asks the user terminal 100 for each application 711 that may be executed. A template (not shown) defining the
0, and when the image shown in FIG. 13 is received from the first user terminal 100A, by matching this image with these templates, the application 711 executed by the first user terminal 100A Identify the first application 711A.

Vaccination history management system 300 then identifies from identified first application 711A that first vaccination history 610A in this image is in the first format. The vaccination history management system 300 then performs image analysis to extract characters in the image according to the first format. In this case, since the first format is a common format, vaccination history management system 300 stores first vaccination history 610A in vaccination history management table 630 as it is.

Also, when receiving the image shown in FIG.
The application 711 being executed by 0B is identified as the second application 711B.

Vaccination history management system 300 then identifies that second vaccination history 610B in this image is in the second format from identified second application 711B. The vaccination history management system 300 then performs image analysis and extracts characters in the image according to the pattern of the second format. In this case, the vaccination history management system 300 stores the second vaccination history 610B in the vaccination history management table 630 after formatting it from the second format to the first format.

After that, the vaccination history management system 300 transmits the vaccination history 610 formatted in the common format stored in the vaccination history management table 630 to the medical institution terminal 200 .

Note that the flow of processing in the third embodiment is the same as the flow of processing in the first embodiment shown in FIG. 11, so redundant description will be omitted.

According to this aspect as well, the vaccination history 610 of each user managing the vaccination history 610 using various applications 711 can be output to the medical institution terminal 200 in a common format. This makes it possible to facilitate the use, such as confirmation, of vaccination history 610 managed by a plurality of applications 711 of different types.

The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit and interpret the present invention. The present invention may be modified and improved without departing from its spirit, and the present invention also includes equivalents thereof.

For example, in the above embodiment, the user terminal 100 transmits the vaccination history 610 to the vaccination history management system 300 together with the information specifying the medical institution, and the vaccination history management system 30
0 transmits this user's vaccination history 610 to the medical institution terminal 200, the case has been described where it is transmitted only to the medical institution terminal 200 designated by the medical institution designation information. The method of transmitting vaccination history 610 to specific medical institution terminal 200 is not limited to this method.

For example, first, the user terminal 100 requests the vaccination history management system 300 to generate a predetermined keyword.

Then, the vaccination history management system 300 generates a keyword from, for example, a random number with a predetermined number of digits, stores the keyword in association with the user's vaccination history 610, and converts the keyword into character information or a two-dimensional code, etc. Send to 100.

Next, the user operating the user terminal 100 conveys the keyword transmitted from the vaccination history management system 300 to the doctor or nurse.

When this keyword is input to the medical institution terminal 200 by the doctor or nurse, the medical institution terminal 200 transmits this keyword to the vaccination history management system 300 .

Then, the vaccination history management system 300 refers to the vaccination history management table 630 and transmits the vaccination history 610 associated with the keyword to the medical institution terminal 200 .

This aspect also makes it possible to disclose the user's vaccination history 610 only to a specific medical institution such as a family doctor.

In the above-described embodiment, two types of applications 711, namely an application 711A that records the vaccination history 610 in the first format and an application 711B that records the vaccination history 610 in the second format, were exemplified in the user terminal 100, but there are three types of applications 711. It may be more than that. Also, the format may be three or more.

Further, in the above-described embodiment, the case where the description formats of the multiple types of applications 711 are different has been exemplified, but the multiple types of applications 711 may be recorded in advance in one common format. Even if a plurality of types of applications 711 have a single common format, the information saved by the plurality of types of applications 711 can be browsed from other terminals,
Since it is necessary to add functions to each application 711 in order to integrate them into one storage unit 302, it is difficult to do so easily. However, according to the embodiment of the present invention, it is possible to easily check and accumulate the vaccination history 610 and use it.

In the above-described embodiment, the medical institution terminal 20
Although browsing from 0 is shown, it is not limited to this. For example, the vaccination history 610 can be used when the user changes the type of the application 711 . That is, according to the embodiment of the present invention, the vaccination history 610 recorded by one application 711 is shared with other applications 7 .
11, when changing the type of application 711 used by the user, the vaccination history 610 recorded by the previously used application 711 can be transferred to the new application 711. can also be used in

In addition, the vaccination history 610 stored in the storage unit 302 may be continuously stored and saved even after browsing from the medical institution terminal 200 is finished. As a result, even if there is a request to check the vaccination history 610 at the time of the next vaccination, it is unnecessary to send and format the vaccination history 610 again, which is preferable. In addition, as will be described later, storing the vaccination history 610 in the storage unit 302 can be used for clerical work in a local government or the like. On the other hand, from the viewpoint of privacy protection, etc., the vaccination history 610 stored in the storage unit 302 is stored in the medical institution terminal 2
00 or after a certain period of time has passed, the data may be deleted from the storage unit 302 at an appropriate time.

In addition, the medical institution terminal 200 is not limited to receiving the vaccination history 610 stored in the storage unit 302, and the vaccination history 610 formatted in the user terminal 100 can be directly received from the user terminal 100 by means of short-distance communication or the like. may receive.

Also, the user's vaccination history 610 is stored in the storage unit 302 of the vaccination history management system 300 .
and a new or changed vaccination history 610 is sent from the same user, the difference between the already stored vaccination history 610 and the later vaccination history 610 is It may be extracted, subjected to processing such as shaping, and saved as a new vaccination history 610 . As a result, processing such as shaping can be performed efficiently.

In the above embodiment, the user's vaccination history 610 recorded by the application 711 is stored in the user terminal 100, but is not limited to this, and may be stored on a recording server connected to the Internet or the like. may

In the above embodiment, the application 711 is installed in the user terminal 100, but is not limited to this, and may be provided in the form of a web page and used from the browser of the user terminal 100. good. In this case, the "multiple types of apps" of this disclosure refer to different services that are available from the same browser. Also, if the application 711 is W
If provided in the form of an eb page, the vaccination history 610 is preferably stored on the recording server described above.

In addition, in the third embodiment, a screen shot that is an image of a state in which the vaccination history 610 is displayed on the screen of the user terminal 100 is used. It may be an image obtained by outputting. In this case, P
A file such as DF preferably contains character information of vaccination history 610 . This facilitates extraction of the vaccination history 610 from the file.

Further, in the above embodiment, the vaccination history 610 is stored in the storage unit 302 of the vaccination history management system 300, but it may be distributed and stored. For example, information such as the name of the vaccine, the period/time, the date of vaccination, and the application name (provider of information on the results of vaccination), which are highly important in the vaccination history 610, are stored in the storage unit 302 of the vaccination history management system 300. Other user's personal information and medical institution information may be stored in the medical institution terminal 200 that browses the vaccination history 610 . In this case, the vaccination history management system 300 may acquire only the highly important information of the vaccination history 610 from the user terminal 100 .

In the above embodiment, the user's vaccination history 610 is shared with the medical institution terminal 200, but is not limited to this. good. This makes it possible for the local government to use the vaccination history 610 as well. As a result, it becomes easier to grasp the vaccination history 610, and administrative work related to vaccination, such as confirmation of whether or not vaccination has been completed for a specific user, processing of vaccination expenses, etc., is performed by the local government. Work can be reduced. In this case, the local government may set the vaccination histories 610 of individual users to be connectable. Municipalities are preferably configured to have access to this aggregated vaccination history 610 .

100 User terminal 110 CPU
120 memory 130 communication device 140 storage device 150 input device 160 output device 170 recording medium reading device 200 medical institution terminal 210 CPU
220 memory 230 communication device 240 storage device 250 input device 260 output device 270 recording medium reading device 300 vaccination history management system 301 reception unit 302 storage unit 303 transmission unit 304 shaping unit 310 CPU
320 memory 330 communication device 340 storage device 350 input device 360 output device 370 recording medium reader 500 network 610A first vaccination history 610B second vaccination history 630 vaccination history management table
710 user terminal control program 711A first vaccination management program 711B second vaccination management program 720 medical institution terminal control program 730 vaccination history management system control program 740 vaccination history collection program 800 recording medium 1000 information system

Claims (8)

A vaccination history management system,
a receiving unit that receives the vaccination history recorded by the application from a user terminal that executes one of a plurality of different types of applications that record the user's vaccination history in different formats;
a storage unit that stores a plurality of vaccination histories received from a plurality of user terminals;
a formatting unit that formats the plurality of vaccination histories into a common format;
a transmitting unit that transmits the vaccination history shaped by the shaping unit to a medical institution terminal;
When generation of a predetermined keyword is requested from a user terminal, the predetermined keyword is generated, and the generated predetermined keyword is associated with the vaccination history related to the user terminal that requested the generation of the predetermined keyword. A vaccination history management system that stores and transmits a generated predetermined keyword to a user terminal that requests generation of the predetermined keyword. 2. The storage unit according to claim 1, wherein when the format of the vaccination history recorded by the application is different from the common format, the storage unit stores information calculated based on the vaccination history as the vaccination history. vaccination history management system. The plurality of types of applications record the vaccination history in different formats,
The user terminal formats the vaccination history recorded by the application executed on the user terminal into a common format and transmits the vaccination history to the vaccination history management system;
The receiving unit receives the vaccination history formatted in the common format from the user terminal,
The storage unit stores a plurality of vaccination histories formatted into the common format received from the plurality of user terminals,
3. The vaccination history management system according to claim 1, wherein said transmission unit transmits said vaccination history formatted in said common format stored in said storage unit to said medical institution terminal. The receiving unit receives from the user terminal, along with the vaccination history, medical institution designation information designating a transmission destination of the vaccination history,
The storage unit stores the vaccination history in association with the medical institution designation information,
4. The vaccination history management system according to claim 1, wherein said transmission unit transmits said vaccination history only to a medical institution terminal specified by said medical institution designation information. to the computer,
receiving, from a user terminal running any one of a plurality of different types of applications for recording a user's vaccination history, the vaccination history recorded by the application;
a procedure for storing a plurality of vaccination histories received from a plurality of user terminals in a storage unit;
a formatting procedure for formatting the plurality of vaccination histories into a common format;
a procedure for transmitting the vaccination history shaped by the shaping procedure to a medical institution terminal;
When generation of a predetermined keyword is requested from a user terminal, the predetermined keyword is generated, and the generated predetermined keyword is associated with the vaccination history related to the user terminal that requested the generation of the predetermined keyword. and a procedure for storing and transmitting the generated predetermined keyword to the user terminal that requested the generation of the predetermined keyword. 6. The storage unit according to claim 5, wherein when the format of the vaccination history recorded by the application is different from the common format, the storage unit stores information calculated based on the vaccination history as the vaccination history. program. A control method for a vaccination history management system, comprising:
The vaccination history management system
receiving the vaccination history recorded by the application from a user terminal executing one of a plurality of different types of applications for recording the user's vaccination history;
storing a plurality of vaccination histories received from a plurality of user terminals in a storage unit;
formatting the plurality of vaccination histories into a common format;
Send the formatted vaccination history to the medical institution terminal,
When generation of a predetermined keyword is requested from a user terminal, the predetermined keyword is generated, and the generated predetermined keyword is associated with the vaccination history related to the user terminal that requested the generation of the predetermined keyword. A control method for a vaccination history management system, which stores and transmits a generated predetermined keyword to a user terminal requesting generation of the predetermined keyword. 8. The storage unit according to claim 7, wherein when the format of the vaccination history recorded by the application is different from the common format, the storage unit stores information calculated based on the vaccination history as the vaccination history. control method of vaccination history management system.

Images