JP7699014B2 - Contact information management device, method, and program - Google Patents

Description

The present invention relates to a contact information management device, method, and program that accepts and manages contact information output from a terminal device.

Previously, when informing the school of a student's health status (physical condition, temperature, etc.), the student would fill out a paper form and submit it.

However, paper documents pose problems such as students forgetting to bring them to school and the need to manage the paper documents.

One possible solution to this problem is a system in which a student's guardian uses a terminal device to create contact information about the student's health condition, etc., and then sends that contact information to a terminal device installed at the school. The school can then check the contact information displayed on the terminal device to confirm the student's health condition, etc.

JP 2009-277202 A

However, as described above, when a guardian uses a terminal device to report contact information such as health status, a guardian who does not have a terminal device or has not registered a terminal device in the above-mentioned system cannot report the contact information.

As a result, schools cannot manage contact information for students whose terminal devices are not registered on the same system, and must separately check whether a terminal device is registered, which makes the process complicated.

Patent Document 1 proposes a system for managing attendance at school lectures, in which emails are sent from a mobile device and attendance information is recorded based on the information in the received email and pre-registered student information. Patent Document 1 also proposes a method for collecting handwritten attendance sheets from students who are unable to send an email because they forgot their mobile device or the battery in their mobile device has run out, and then inputting the sheets into the system later.

However, even in Patent Document 1, participants who have not yet sent an attendance email can only be confirmed by looking at a handwritten attendance sheet, and they cannot be confirmed on the same system, making the process cumbersome.

In view of the above circumstances, the present invention aims to provide a contact information management device, method, and program that can eliminate the management hassle that occurs when identifying unregistered users.

The contact information management device of the present invention includes a registrant identification information storage unit that stores identification information of pre-registered registrants, a contact information reception unit that receives contact information output from the registrant's terminal device, a registration candidate information storage unit that stores information on registration candidates including registrants and unregistered persons, and a management unit that manages the contact information of registrants and information on unregistered persons based on the information on the registration candidates and the identification information of registrants.

The contact information management program of the present invention causes a computer to execute the steps of storing identification information of pre-registered registrants, accepting contact information output from the registrant's terminal device, storing information on candidates for registration including registrants and unregistered individuals, and managing the contact information of registrants and information on unregistered individuals based on the information on the candidates for registration and the identification information of the registrants.

The contact information management method of the present invention stores identification information of pre-registered registrants and information on candidates for registration, including registrants and unregistered individuals, accepts contact information output from the terminal device of the registrant, and manages the contact information of registrants and information of unregistered individuals based on the information on the candidates for registration and the identification information of the registrants.

The contact information management device, method, and program of the present invention manages contact information of registered individuals and information of unregistered individuals, eliminating the hassle of managing information that arises when identifying unregistered individuals.

FIG. 1 is a block diagram showing a schematic configuration of a contact information management system using an embodiment of a contact information management device of the present invention. FIG. 13 is a diagram showing an example of a contact information setting input screen. An example of a school management table FIG. 13 is a diagram showing an example of a grade management table. FIG. 13 is a diagram illustrating an example of a class management table. FIG. 13 is a diagram showing an example of a terminal registration management table. FIG. 13 is a diagram showing an example of a contact information management table. A diagram showing an example of an approver confirmation screen A flowchart illustrating the process flow of the contact information management system shown in FIG.

The following describes in detail a contact information management system using an embodiment of the contact information management device of the present invention with reference to the drawings. Figure 1 is a block diagram showing the general configuration of the contact information management system 1 of this embodiment.

As shown in FIG. 1, the contact information management system 1 of this embodiment includes a registrant terminal device 10, a contact information management device 20, and an approver terminal device 30.

The registrant terminal device 10 and the contact information management device 20, and the contact information management device 20 and the approver terminal device 30 are connected via a communication line. The communication line may be an Internet line or a telephone line. The communication line may be either wired or wireless.

First, we will explain the general flow of processing using the contact information management system 1 of this embodiment.

The contact information management system 1 of this embodiment is a system used by schools and the parents of students who attend those schools, and is primarily used by parents to communicate contact information such as the health status of their students to the school.

In this embodiment, students correspond to the registration candidates of the present invention, and there are students who are registered and students who are unregistered. A registered person is a person who has been registered in advance in the contact information management device 20, and the identification information of the registered person is stored in the contact information management device 20. An unregistered person is a person who has not yet been registered in the contact information management device 20. A registration candidate is a person (students) who can be registered in the contact information management device 20, and includes registered people (students) who are already registered and unregistered people (students) who have not yet been registered.

In this embodiment of the contact information management system 1, the contact information management device 20 first creates a contact information management table that stores the health status of each student based on pre-registered school, class, and student information.

Next, the guardian uses the registrant terminal device 10 to set and input contact information such as the student's (child's) health status.

The contact information entered by the guardian is then output from the registrant terminal device 10 to the contact information management device 20, where it is stored and managed.

In response to a request from the approver terminal device 30 installed at the school, the contact information of each student stored in the contact information management device 20 is output and accepted by the approver terminal device 30 on the school side. At this time, the contact information management device 20 outputs to the approver terminal device 30 not only contact information for already registered students (registered students), but also information for unregistered students (unregistered students).

The approver terminal device 30 accepts and displays contact information for already registered students and information for unregistered students. The contact information, such as health status, displayed on the approver terminal device 30 is confirmed by the school's approver (staff member), who can check the contact information for already registered students as well as information for unregistered students on the same screen.

The above is a general flow of processing using the contact information management system 1 of this embodiment. Note that in FIG. 1, only one registrant terminal device 10 and one approver terminal device 30 are shown, but in reality, the number of registrant terminal devices 10 provided corresponds to the number of registrants registered in the contact information management device 20, and the number of approver terminal devices 30 provided corresponds to the number of schools.

Next, we will explain the details of each device that makes up the contact information management system 1 of this embodiment.

As described above, the registrant terminal device 10 is used by the guardian, and may be, for example, a mobile terminal such as a smartphone or a tablet terminal. However, it is not limited to this, and may also be a desktop computer or a notebook computer.

The registrant terminal device 10 is equipped with a CPU (Central Processing Unit), semiconductor memory such as ROM (Read Only Memory) and RAM (Random Access Memory), storage such as a hard disk, and a communication I/F (Interface).

A parent application that accepts input of contact information, including the student's body temperature, physical condition, and other health information, is installed in the storage of the registrant terminal device 10. When the parent application is started by the CPU, a contact information input screen is displayed on the registrant terminal device 10.

Figure 2 is a diagram showing an example of a contact information setting input screen. The contact information setting input screen shown in Figure 2 displays a body temperature input field S1, a health condition selection field S2, a message input field S3, a pool participation selection field S4, and a marathon participation selection field S5.

The body temperature input field S1 is a field that accepts the input of the student's body temperature. The body temperature input field S1 is configured to display the body temperature numerical value in a pull-down menu, allowing the guardian to select the measured body temperature.

The health condition selection field S2 is a field for accepting the student's health condition. The health condition selection field S2 displays radio buttons that allow the student to select whether their physical condition is "good" or "poor."

The message input field S3 can accept text input, and parents can enter more specific symptoms, for example, if the student is feeling unwell.

The pool participation selection field S4 is a field for accepting whether or not the user wants to participate in the pool lesson. The pool participation selection field S4 displays radio buttons that allow the user to select "Participate" or "Do not participate."

The marathon participation selection field S5 is a field for accepting whether or not the user wants to participate in the marathon class. The marathon participation selection field S5 displays radio buttons that allow the user to select "Participate" or "Do not participate."

Although not shown on the contact information setting input screen shown in Figure 2, in addition to the above-mentioned content, the contact information setting input screen also displays a pull-down list that allows the user to select whether a student is absent, late, or leaves early.

The contact information setting input screen displays a "Report" button, a "Clear input" button, and a "Check past absences, lateness, and early departure notifications" button.

Additionally, tags Tg1 to Tg3 are displayed on the contact information setting input screen. Tags Tg1 to Tg3 are used to select the student for whom contact information is to be provided; in the example of FIG. 2, one of "Taro," "Hanako," or "Jiro" is selected. Such tags Tg1 to Tg3 are used, for example, when one parent has registered multiple children (students) at the same or different schools. FIG. 2 shows an example of the display when tag Tg1 is selected, but the same display is also shown when tag Tg2 or tag Tg3 is selected.

For example, when input into each field for Taro of tag Tg1 is completed, the "Report" button shown in FIG. 2 is tapped, and the contact information for "Taro" that was set and input on the contact information setting input screen is output from the registrant terminal device 10 to the contact information management device 20. When the contact information for "Taro" is output from the registrant terminal device 10, the identification information for "Taro" is also output together. This identification information is the student ID registered in the terminal registration management table T4, which will be described later.

When the "Clear input" button shown in Figure 2 is tapped, the information entered in each field is cleared. When the "Check past absences, lateness, and early departure notices" button shown in Figure 2 is tapped, a screen is displayed that allows the user to refer to previously entered contact information.

Next, we will explain the contact information management device 20. The contact information management device 20 is a server device that receives the contact information output from the registrant terminal device 10, and stores and manages this information for each student.

Specifically, as shown in FIG. 1, the contact information management device 20 includes a memory unit 21, a contact information receiving unit 22, and a management unit 23.

The memory unit 21 stores a school management table T1, a grade management table T2, a class management table T3, a terminal registration management table T4, and a contact information management table T5.

Figure 3 shows an example of the school management table T1. The school management table T1 is a table that stores the identification number (school ID) and the name of each school where the approver terminal device 30 is installed.

Figure 4 shows an example of the grade management table T2. The grade management table T2 is a table that stores the identification number (school ID) of each school stored in the school management table T1, the identification number (grade ID) of the grade of each school, and the name of the grade.

Figure 5 is a diagram showing an example of class management table T3. Class management table T3 is a table that stores the identification number (grade ID) of each grade stored in grade management table T2, the identification number (class ID) of each class in each grade, the class name, and the number of students in each class. In this embodiment, class management table T3 corresponds to the registration candidate information storage unit of the present invention, and the number of students in each class in class management table T3 corresponds to the number of registration candidates of the present invention. In this embodiment, the number of students in a class is stored as information on registration candidates, but this is not limited to this, and information other than the number of students may be used as long as it is information that can be used to manage classes or groups.

Figure 6 is a diagram showing an example of the terminal registration management table T4. The terminal registration management table T4 is a table that stores the identification number (class ID) of each class stored in the class management table T3, the identification number (student ID) of a student who belongs to that class and has already been registered as a registrant, and the attendance number of that student. In this embodiment, the terminal registration management table T4 corresponds to the registrant identification information storage unit of the present invention.

Figure 7 shows an example of the contact information management table T5. The contact information management table T5 is a table generated by the management unit 23, which will be described later, using the school management table T1, grade management table T2, class management table T3, and terminal registration management table T4 described above.

The contact information management table T5 is a table that stores contact information such as the class identification number (class ID) stored in the class management table T3, the identification number (student ID) of the registered student stored in the terminal registration management table T4, the attendance numbers of all students belonging to each class, and the health status (body temperature and physical condition) of the students belonging to each class.

At a preset time, the management unit 23 references the school management table T1, grade management table T2, class management table T3, and terminal registration management table T4 to generate a contact information management table T5 for each school. Note that the preset time is set to, for example, a time when the contact information management device 20 is not accessed from the registrant terminal device 10 and the approver terminal device 30, such as midnight.

Specifically, the management unit 23 uses the school management table T1 to identify the school ID of a specific school, and then refers to the grade management table T2 based on the school ID to identify the grade ID that corresponds to the school ID. The management unit 23 then refers to the class management table T3 based on the identified grade ID to obtain the class ID that corresponds to the grade ID and the number of students in that class.

Then, the management unit 23 creates records for the number of students in the class based on the acquired number of students, and records the class ID and attendance number in the records. Note that in this embodiment, a record is a column for recording information about each student, and is generated on a student-by-student basis.

Furthermore, the management unit 23 refers to the terminal registration management table T4 based on the class ID and attendance number of each record, obtains the registered student ID, and records the obtained student ID in the corresponding record to generate the contact information management table T5.

The contact information management table T5 generated at this point does not yet contain contact information such as each student's temperature and health condition.

The contact information management table T5 contains not only records of students (student IDs) stored in the terminal registration management table T4, but also records of students (unregistered students) who have not yet been registered in the terminal registration management table T4. The identification number (student ID) column of unregistered students is left blank. For example, in the contact information management table T5 shown in Figure 7, the student with attendance number 5 is an unregistered student.

The management unit 23 stores the contact information management table T5 generated as described above in the memory unit 21.

Then, the contact information receiving unit 22 receives the contact information of each student output from each registered user terminal device 10.

The management unit 23 acquires the contact information of each student accepted by the contact information acceptance unit 22, and records the acquired contact information of each student in each record in the contact information management table T5.

In addition, the management unit 23 outputs the contact information management table T5 in response to a request from the approver terminal device 30 and displays it on the approver terminal device 30. The method of displaying the contact information management table T5 will be described in detail later.

The management unit 23 also accepts editing of the contact information of registered students in the contact information management table T5. The management unit 23 also accepts editing of the contact information of unregistered students in the contact information management table T5. Editing of the contact information may be performed using the approver terminal device 30 described below, or may be performed using an input device connected to the contact information management device 20.

The contact information management device 20 includes a CPU, semiconductor memory such as ROM and RAM, storage such as a hard disk, and a communication I/F. A contact information management program is installed in the storage of the contact information management device 20. When this contact information management program is executed by the CPU, the functions of the memory unit 21, contact information reception unit 22, and management unit 23 described above are realized, and data is sent and received between the contact information management device 20 and the registrant terminal device 10, and between the contact information management device 20 and the approver terminal device 30.

In this embodiment, the above-mentioned parts of the contact information management device 20 are made to function by executing the contact information management program by the CPU, but some or all of the functions executed by the contact information management program may be configured from hardware such as an ASCI (Application Specific Integrated Circuit), FPGA (Field-Programmable Gate Array), or other electrical circuits.

As described above, the approver terminal device 30 is used by the school's approver (staff member), and may be, for example, a desktop computer or a notebook computer, but is not limited to these and may also be a mobile terminal such as a tablet terminal.

The approver terminal device 30 accepts the contact information management table T5 output from the contact information management device 20, and displays the approver confirmation screen using the accepted contact information management table T5.

The approver terminal device 30 is equipped with a display device such as a liquid crystal display, and the approver confirmation screen is displayed on this display device. When a tablet terminal is used as the approver terminal device 30, the approver confirmation screen is displayed on a touch panel of the tablet terminal.

The approver terminal device 30 is equipped with a CPU, semiconductor memory such as ROM and RAM, storage such as a hard disk, and a communication I/F.

An approver application is installed in the storage of the approver terminal device 30. When this approver application is started by the CPU, an approver confirmation screen is displayed on the approver terminal device 30. Note that instead of using the approver application installed in the storage as in this embodiment, an approver application provided via a web browser may be used.

Figure 8 is a diagram showing an example of an approver confirmation screen. The approver confirmation screen shown in Figure 8 shows an example of the display of contact information for "Riso Elementary School." On the approver confirmation screen shown in Figure 8, a contact information display field R1 displays a list of each record in which contact information for each student is recorded. The approver confirmation screen shown in Figure 8 also displays a grade selection field R2 and a class selection field R3. In the grade selection field R2, buttons such as "All grades," "1st grade," and "2nd grade" are displayed. In addition, in the class selection field R3, buttons such as "Class 1," "Class 2," and "Class 3" are displayed.

In the contact information display field R1, contact information for the grade selected in the grade selection field R2 and the class selected in the class selection field R3 is extracted and displayed in a list.

As shown in FIG. 8, the contact information display field R1 displays the fields for "Grade," "Class," "Attendance number," "Attendance," "Temperature check," "Health condition," "Symptoms," "Contact information," "Additional observation 1," "Additional observation 2," and "Report date and time." The "Grade," "Class," and "Attendance number" fields display the student's grade, class, and attendance number.

In addition, the "Attendance" field displays information such as absence, leaving early, or arriving late that has been entered into the registrant terminal device 10. In addition, the "Temperature" field displays the body temperature that has been entered into the body temperature input field S1 shown in FIG. 2.

The "health condition" field displays the content selected in the health condition selection field S2 shown in FIG. 2. The "message" field displays the content entered in the message entry field S3 shown in FIG. 2.

The "Additional Observation 1" field displays the content selected in the pool participation selection field S4 shown in FIG. 2. The "Additional Observation 2" field displays the content selected in the marathon participation selection field S5 shown in FIG. 2.

The "Report Date and Time" field also displays the date on which the contact information was output from the registrant terminal device 10.

The contact information display section R1 also identifiably displays records of students (student IDs) registered in the terminal registration management table T4, records of students (unregistered students) who have not yet been registered in the terminal registration management table T4, and records of students who have been registered in the terminal registration management table T4 but whose contact information has not yet been accepted by the contact information management device 20.

In the example shown in Figure 8, student number 1 in class 1, student number 2 in class 1, and student number 4 in class 1 are students (student IDs) registered in the terminal registration management table T4 and are students for whom contact information has already been accepted.

In the contact information display field R1, the characters of the contact information that meet the preset conditions may be displayed in red, and the other characters may be displayed in black, so that the contact information that meets the preset conditions is highlighted and identifiable. In the example shown in FIG. 8, for example, the displays "Absent," "Leaving early," and "Late" in the "Attendance" field and the display "Unwell" in the "Health" field are displayed in red. Also, in the "Temperature" field, a temperature measurement result of 37.5 degrees or higher is displayed in red.

In the example shown in Figure 8, the student in class 1-1 with attendance number 3 is a student (student ID) registered in the terminal registration management table T4, and is a student for whom contact information has not yet been received. For this student's record, all of the contact information columns are displayed as blank, as shown in Figure 8.

In the example shown in Figure 8, the student in class 1-1 with attendance number 5 is a student who has not yet been registered in the terminal registration management table T4 (an unregistered student). As shown in Figure 8, the contact information field for this student's record shows all "-" (hyphens), and the grade, class, and attendance number are displayed in red.

By displaying the contact information display field R1 as described above, it is possible to distinguish between records of students (student IDs) registered in the terminal registration management table T4, records of students (unregistered students) who have not yet been registered in the terminal registration management table T4, and records of students who have been registered in the terminal registration management table T4 but whose contact information has not yet been accepted by the contact information management device 20.

The approver confirmation screen shown in Figure 8 also displays a "Download non-reporters (CSV)" button, a "Download list (CSV)" button, and a "Print" button.

When the "Download non-reporters (CSV)" button is selected, the management unit 23 of the contact information management device 20 extracts only the records of registered students who have not yet received contact information from the records of each student displayed in the contact information display field R1 based on the contact information management table T5, and generates data in CSV format. The management unit 23 then outputs the CSV format data to the approver terminal device 30.

In addition, when the "Download list (CSV)" button is selected, the management unit 23 of the contact information management device 20 generates CSV-format data containing records of all students displayed in the contact information display field R1 based on the contact information management table T5. The management unit 23 then outputs the CSV-format data to the approver terminal device 30.

In addition, when the "Print" button is selected, the approver confirmation screen is output to a designated printing device and printed.

Next, the processing of the contact information management system 1 of this embodiment will be described in detail with reference to the flowchart shown in FIG.

First, as described above, the management unit 23 of the contact information management device 20 generates the contact information management table T5 at midnight using the school management table T1, grade management table T2, class management table T3, and terminal registration management table T4 (S10). At this time, the contact information management table T5 is generated in which the contact information of each student has not yet been recorded.

Next, the parent starts the parent application installed on the registrant terminal device 10, displays the contact information setting input screen as shown in FIG. 2, inputs the contact information settings on the contact information setting input screen (S12), and outputs the contact information from the registrant terminal device 10 (S14). At this time, the student ID is also output from the registrant terminal device 10 as described above.

When the contact information and student ID are output from the registrant terminal device 10 to the contact information management device 20, they are accepted by the contact information reception unit 22 of the contact information management device 20 (S16). Then, the management unit 23 refers to the contact information management table T5 generated in S10 based on the student ID accepted by the contact information reception unit 22, and records the contact information accepted together with the student ID in the record for that student ID (S18).

Next, when the school's approver starts the approver application installed on the approver terminal device 30, an output request signal for the contact information management table T5 is output from the approver terminal device 30 to the contact information management device 20 (S20).

When the management unit 23 of the contact information management device 20 receives an output request signal output from the approver terminal device 30, it outputs the contact information management table T5 generated at the time of reception to the approver terminal device 30 (S22). Note that the contact information management table T5 output at this time records the contact information of students who have already been accepted (contacted), but does not record the contact information of students who have not yet been accepted (contacted). In other words, the management unit 23 sequentially records the contact information accepted by the contact information acceptance unit 22 in the contact information management table T5, and outputs the contact information management table T5 without recording any contact information that has not yet been accepted by the contact information acceptance unit 22.

Then, the contact information management table T5 output from the management unit 23 is received by the approver terminal device 30, which displays the approver confirmation screen based on the contact information management table T5 (S24). Then, on the approver confirmation screen, as described above, a state in which contact information of a registered student is being accepted, a state in which contact information of a registered student is not being accepted, and information of an unregistered student are identifiable.

The contact information management system 1 of this embodiment manages contact information of registered individuals and information of unregistered individuals in an identifiable manner within the same system based on the number of registration candidates (classes) and the identification information of the registered individuals, eliminating the complicated management that occurs when identifying unregistered individuals as in the conventional method.

The contact information management system of the above embodiment is also designed to distinguish between the state in which contact information of registered users is not being accepted and the information of unregistered users, preventing confusion between the two.

In addition, in the contact information management system of the above embodiment, an attendance number is added as identification information to all registration candidates (e.g., all students), so individuals can be identified by linking the attendance number with personal information, for example.

In addition, in the contact information management system of the above embodiment, the state in which contact information of registered persons is being accepted, the state in which contact information of registered persons is not being accepted, and information of unregistered persons are displayed in a distinguishable manner, so that the approver can immediately recognize the state by checking this display.

In addition, the contact information management system of the above embodiment is configured to accept edits of at least one of the contact information of registered individuals and the contact information of unregistered individuals, so that even if a situation occurs in which a guardian is temporarily unable to access the system using a terminal device, for example, the contact information can be edited on the contact information management device 20 side. In addition, separately obtained contact information for unregistered individuals can also be recorded.

The present invention further discloses the following supplementary notes.
(Additional Note)

In the contact information management device of the present invention, the management unit can distinguish between a state in which contact information of a registered person is being accepted, a state in which contact information of a registered person is not being accepted, and information of an unregistered person.

In addition, in the contact information management device of the present invention, the management unit can add identification information to all registration candidates.

In addition, in the contact information management device of the present invention, the management unit can distinguishably display a state in which contact information of a registered person is being accepted, a state in which contact information of a registered person is not being accepted, and information of an unregistered person.

In addition, in the contact information management device of the present invention, the management unit can accept edits to at least one of the contact information of registered individuals and the contact information of unregistered individuals.

1 Contact information management system 10 Registrant terminal device 20 Contact information management device 21 Memory unit 22 Contact information reception unit 23 Management unit 30 Approver terminal device R1 Contact information display field R2 Grade selection field R3 Class selection field S1 Body temperature input field S2 Health condition selection field S3 Contact item input field S4 Pool participation selection field S5 Marathon participation selection field Tg1 to Tg3 Tag T1 School management table T2 Grade management table T3 Class management table T4 Terminal registration management table T5 Contact information management table

Claims (4)

a storage unit for storing a contact information management table having information on registered persons whose identification information has been registered in advance and information on unregistered persons whose identification information has not been registered;
a contact information receiving unit that receives the identification information and contact information of the registrant output from the terminal device of the registrant ;
A contact information management device comprising a management unit that records the contact information in the contact information management table based on the identification information of the registrant, and generates the contact information management table in which information of registrants with the contact information recorded, information of registrants with the contact information not recorded, and information of unregistered persons can be identified . 2. The contact information management device according to claim 1, wherein the management unit accepts editing of at least one of the contact information of the registered persons and the information of the unregistered persons. storing a contact information management table having information of registered persons whose identification information has been registered in advance and information of unregistered persons whose identification information has not been registered;
receiving identification information and contact information of the registrant outputted from a terminal device of the registrant;
A contact information management program that causes a computer to execute a step of recording the contact information in the contact information management table based on the identification information of the registrant, and generating the contact information management table in which information of registrants with the contact information recorded, information of registrants with the contact information not recorded, and information of unregistered persons can be identified . storing a contact information management table having information on registered persons whose identification information has been registered in advance and information on unregistered persons whose identification information has not been registered;
receiving identification information and contact information of the registrant outputted from the terminal device of the registrant;
A contact information management method in which a computer executes a process of recording the contact information in the contact information management table based on the identification information of the registrant, and generating the contact information management table in which information of registrants with the contact information recorded, information of registrants with the contact information not recorded, and information of unregistered persons can be identified .