WO2008070894A1

WO2008070894A1 - A data repository system

Info

Publication number: WO2008070894A1
Application number: PCT/AU2007/001535
Authority: WO
Inventors: Andrew William Lammin Baer
Original assignee: Mercury Files Pty Limited
Priority date: 2006-12-13
Filing date: 2007-10-10
Publication date: 2008-06-19

Abstract

A data repository system for storing information about a person that can be later used to uniquely identify the person, said system for performing the steps of generating data representing a plurality of questions for display on a communications device; receiving data representing answers to one or more of said questions from said person by way of said communications device; and storing said data representing answers to one or more of said questions on a computer readable data storage medium.

Description

A DATA REPOSITORY SYSTEM

Field of the Invention

The present invention relates to a data repository system a data repository system for storing information about a person that can be later used to uniquely identify the person. The present invention also relates to a system for providing information about a person to assist a search operation for said person. The present invention relates to a computer program for storing information about a person that can be later used to uniquely identify the person. The present invention also relates to a computer program for generating information about a person to assist a search operation for said person.

Background of Invention

The events that transpire in the minutes and hours that immediately follow an abduction of a child, for example, are typically critical to the success of any associated search operation. In this time, it is imperative that accurate and up to date physical and biological data can be provided to the relevant authorities. It is during this time that the missing person is most likely to be proximal to his or her last known whereabouts and, as such, the information about the missing person can be most effectively used by both law enforcement agencies.

It has previously been the case that the necessary physical and biological data associated with a missing person is not readily available at the time when it is most needed. Where a child is abducted when his or her family is on holiday, for example, the relevant physical and biological data may need to be collected from various locations or perhaps even compiled from scratch. Unfortunately, during this time, the missing person's loved ones may be traumatised and their ability to provide useful information may be impaired.

An alarming percentage of abductions are carried out by non-custodial parents, or known family members. As such, family members are possible suspects when a child is missing, or is believed to have been abducted. Consequently, the process of collecting and verifying information may take up precious time and impair operations at a critical stage of the search.

The above described difficulties are exacerbated when the missing person is a traveller in a foreign land. To mount a search for the person, the relevant search organisation typically needs to obtain the missing persons personal information and also try to determine the persons recent travel history. For example, it may be useful to know where the person has been staying and which places the person has been frequenting. It may be possible to determine the traveller's personal information from friends and relatives. However, it may be difficult, particularly in a crisis, to trace back the traveller's foot steps to obtain this potentially valuable information.

The above described difficulties are not isolated to search operations for missing persons. They may also be experienced during recovery efforts in situations arising from natural, or man made, catastrophes such as earthquakes, and acts of terrorism. In such situations, the relevant authorities have the difficult task of quickly and accurately identify the victims of the disaster. This process may be made difficult because of imprecise or limited information being available in respect of each one of the victims. The difficulties may be exacerbated in the case in when the catastrophe occurs in a third world country.

Preferred embodiments of the present invention seek to overcome, or alleviate, one or more of the above-described difficulties, or at least provide a useful alternative.

Summary of the Invention

In accordance with one aspect of the present invention, there is provided a data repository system for storing information about a person that can be later used to uniquely identify the person, said system for performing the steps of: (a) generating data representing a plurality of questions for display on a communications device; (b) receiving data representing answers to one or more of said questions from said person by way of said communications device; and

(c) storing said data representing answers to one or more of said questions on a computer readable data storage medium.

Preferably, said system is also for performing the step of generating said data representing answers to one or more of said questions for display on a communications device.

Preferably, said system is also for performing the step of encrypting said data representing answers to one or more of said questions using an encryption key defined by the person.

Preferably, said system is also for performing the steps of receiving data representing an encryption key; and generating said data representing answers to one or more of said questions for display on a communications device if the encryption key matches the encryption key defined by the person.

In accordance with another aspect of the invention, there is provided a system for providing information about a person to assist a search operation for said person, said system for performing the steps of: (a) receiving data uniquely identifying the person; and

(b) generating data associated with the data uniquely identifying the person for display on a communications device.

Preferably, said system is also for performing the steps of receiving data representing an encryption key from the communications device.

Preferably, said step of generating data is only effected if the encryption key received from the communications device matches a corresponding encryption key defined by the person.

In accordance with another aspect of the invention, there is provided a computer program for storing information about a person that can be later used to uniquely identify the person, said program for performing the steps of:

(a) generating data representing a plurality of questions for display on a Communications device;

(b) receiving data representing answers to one or more of said questions from said person by way of said communications device; and

Preferably, said program also performs the step of generating said data representing answers to one or more of said questions for display on a communications device.

Preferably, said program also performs the step of encrypting said data representing answers to one or more of said questions using an encryption key defined by the person.

Preferably, said program also performs the steps of receiving data representing an encryption key; and generating said data representing answers to one or more of said questions for display on a communications device if the encryption key matches the encryption key defined by the person.

In accordance with another aspect of the invention, there is provided a computer program for generating information about a person to assist a search operation for said person, said program for performing the steps of:

(a) receiving data uniquely identifying the person; and

Preferably, said system for performing the steps of receiving data representing an encryption key from the communications device.

Preferably, the step of generating data is only effected if the encryption key received from the communications device matches a corresponding encryption key defined by the person. In accordance with another aspect of the invention, there is provided a computer readable data storage medium, including the above described computer program.

Brief Description of the Drawings

Preferred embodiments are hereafter described, by way of non-limiting example only, with reference to the accompanying drawings in which:

Figure 1 is a diagrammatic illustration of a data repository system connected to a network;

Figure 2 is a diagrammatic illustration of the system shown in Figure 1 ;

Figure 3 is a diagrammatic illustration of a home page generated by the system shown in

Figure 1;

Figure 4 is a diagrammatic illustration of a Subscription web page generated by the system shown in Figure 1 ;

Figure 5 is a diagrammatic illustration of a member web page generated by the system shown in Figure 1 ;

Figure 6 is a flow diagram showing steps performed by the system shown in Figure 1 ;

Figure 7 is a diagrammatic illustration of an Upload web page generated by the system shown in Figure 1 ;

Figure 8 is a diagrammatic illustration of a Personal Images web page generated by the system shown in Figure 1 ;

Figure 9 is a diagrammatic illustration of a Videos web page generated by the system shown in Figure 1 ; Figure 10 is a diagrammatic illustration of a Fingerprints web page generated by the system shown in Figure 1 ;

Figure 1 1 is a diagrammatic illustration of a DNA web page generated by the system shown in Figure 1 ;

Figure 12 is a diagrammatic illustration of a Vehicle Images web page generated by the system shown in Figure 1 ;

Figure 13 is a diagrammatic illustration of a Valuables Images web page generated by the system shown in Figure 1 ;

Figure 14 is a diagrammatic illustration of a Document Image web page generated by the system shown in Figure 1 ;

Figure 15 is a diagrammatic illustration of a Handwriting web page generated by the system shown in Figure 1 ;

Figure 16 is a diagrammatic illustration of a Signature web page generated by the system shown in Figure 1 ;

Figure 17 is a diagrammatic illustration of a Voice web page generated by the system shown in Figure 1 ; Figure 18 is a diagrammatic illustration of a Dental web page generated by the system shown in Figure 1 ;

Figure 19 is a diagrammatic illustration of an Active Log web page generated by the system shown in Figure 1 ;

Figure 20 is a diagrammatic illustration of a Log form generated by the system shown in Figure 1 ;

Figure 21 is a diagrammatic illustration of a User Tools web page generated by the system shown in Figure 1 ; and

Figure 22 is a diagrammatic illustration of an Emergency Links web page generated by the system shown in Figure 1.

Detailed Description of Preferred Embodiments of the Invention

The data repository system 10 shown in Figure 1 can be used to store information about a person that can be later used to uniquely identify that person. The data repository system 10 can also be used to store information about a person that can be later used to assist in a search operation to find that person. In event that a person is abducted, for example, the person's information can be retrieved from the system 10 and used to assist in a search operation for the person.

The system 10 advantageously reduces the amount of time it takes to gather information about a person to assist in a search operation for that person. The system 10 permits information relating to a missing person to be quickly accessed from anywhere in the world by one or more organisations. The system 10 preferably facilitates rapid access to accurate information and thereby increases the chances of a missing person being located or positively identified.

The terms "search operation" are taken to include a search operation to find a missing person; a search operation to find an abducted person; and any other search operation where quick access to information relevant to the search is desirable.

The Computer System

The data repository system 10 is provided by the computer system 12 shown in Figure 2. The system 12 is used by people desirous of maintaining a repository of information that can be accessed during a search operation to assist in their recovery or identification, for example.

The computer system 12 includes a server 14 in communication with a database 16. The computer system 12 is able to communicate with equipment 18 of members, or users, of the system 12 over a communications network 20 using standard communication protocols. The equipment 18 of the members can be a variety of communications devices 18 such as personal computers; interactive televisions; hand held computers etc. The communications network 20 may include the Internet, telecommunications networks and/or local area networks.

The components of the computer system 12 can be configured in a variety of ways. The components can be implemented entirely by software to be executed on standard computer server hardware, which may comprise one hardware unit or different computer hardware units distributed over various locations, some of which may require the communications network 20 for communication. A number of the components or parts thereof may also be implemented by application specific integrated circuits (ASICs). It will be apparent from the description of the system 12, and its operation below, that the most practical implementation of the components of the computer system 12 is a software implementation. Alternative methods of providing system displays and information can also be used, for example WML pages for mobile telephones, and interactive voice response (IVR) systems for connection to standard fixed telephones or voice over IP terminals.

The server 14 of the computer system 12 includes a web server 22, a transaction engine 24 and a database server 26 arranged in the manner shown in Figure 2. The web server 22 is software stored on the server 14 that allows the computer system 12 to serve static and dynamic web pages of the web application. The web server 22 allows members of the system 10 to access web pages created and stored on the computer system 12 via their respective communications devices 18. The web pages published by the web server 22 are dynamic and are populated by data provided by the transaction engine 24 of the computer system 12.

The transaction engine 24 is software that processes data received by the web server 22 from users of the system 10 via their terminals 18 and is able to retrieve and store data on the database 16 via the database server 26. The transaction engine 24 communicates with the web server 22 and database server 26 to execute data transactions for the system 12 and thereby provides dynamic content for the web pages provided by the web server 22, as described below.

The database server 26 is software stored on the server 14. The database server 26 reads, writes, maintains and secures data on the database 16. The database server 26 maintains data in the database 16 for all members of the system 10. The database 16 is maintained preferably on hard disk storage of the server 14 of the computer system 12.

Member's Web Site

A person can use his or her personal computer 18 to access the system home web page 30 shown in Figure 3 via the Internet 20. The home page 30 generated by the system 12 includes:

1. A "Change Language" function button 36;

2. An "Information" function button 38; 3. A "Subscribe" function button 32;

4. A "Login" function button 34; and

5. A "Trustee" function button 39

A person can change the language in which the system 10 presents information to them by executing the "Change Language" function button 36. The system 10 generates a list of country names on detection of execution of this button and permits the person to select on of the options presented to them. After a country has been selected, the system 10 generates information in the language of the selected country only.

A person obtain information about the services provided by the system 10 by executing the "Information" function button 36. The system 12 generates a display showing this information on detection of execution of the "Information" function button 36.

A person can become a member of the system 10 by executing the "Subscribe" function button 32. The system 12 generates the subscription web page 40 shown in Figure 4 on detection of execution of the "Subscribe" function button 32. The subscription web page 40 prompts the user to complete the following data boxes:

a. User Name 44; b. Password 46; and c. Postal Address 48.

The user then executes the "Payment" function button 48 to make a subscription payment to the proprietor of the system 12. Processes for making such payments are known in the relevant art and are not described here in further detail. On successfully completing the above-described subscription process, the system 12 generates a profile for the new member on the system 12 and sends a forensic pack to his or her postal address. The forensic pack includes:

a. A deoxyribonucleic acid (DNA) sample kit, a prepaid envelope addressed to a genetic sequencing facility and instructions for taking the sample; b. A dental record; and c. Print tape and Print Cards.

The new member is can use his or her communications device 18 to access his or her web page by executing the "Login" function button 32 on the system home page 30. The login web page (not shown) generated by the system 12 includes a user identification data box and a user password data box. On detection of a valid user name and password, the system 12 generates the web page 50 shown in Figure 5 for the member. The member's web page 50 is populated with data associated with the member and includes:

1. A "Questionnaire" function button 52;

2. An "Upload" function button 54;

3. A "Save" function button 56; 4. An "Activity Log" function button 58;

5. A "User Tools" function button 60;

6. An "Emergency Links" function button 62; and

7. A "Logout" function button 64.

Each one of the above functions is described below in detail.

1. Questionnaire

The member can enter information into the system 12 using his or her communications device 18, such as a computer terminal, by executing the "Questionnaire" function button

52. The system 12 performs the steps shown in Figure 6 on detection of execution of "Questionnaire" function button 52.

If it is the first time that the member has requested access to the questionnaire, then the system 12 generates, at step 66, a blank questionnaire for display on the member's communications device 18. An example of the questionnaire generated by the system 12 is set out in Appendix A. Otherwise, if the member has previously accessed the questionnaire, then the system 12 prompts the member, at step 68, for an encryption key.

On detection of the correct encryption key, the system 12 generates, at step 70, a questionnaire for the member. The questionnaire is populated with data previously entered by the member.

The member can use his or her computer terminal 18 to provide answers to the questions in the questionnaire by entering data, at step 72, into the corresponding data fields.

The questionnaire is divided into the following sections:

Major Section One: Subject Information

a. Personal Details; b. Physical Details;

C. Medical Details; d. Educational History; e. Present Schooling Details; g- Employment History; h. Present Employment Details; i. Membership of Organised Associations; j- Membership of Business Associations; k. Recreational Activities;

1. Distinctive possessions; m. Travel Information; n. Financial Details; and o. Pets.

Major Section Two: Family, Friends & Associates

a. Father's Details; b. Mother's Details; c. Children's Details; d. Sibling's Details; e. Details of Extended Family Members; f. Current Relationship Status; g. Past Relationships; and h. Care Providers.

The member can exit the questionnaire by executing an "End Revision" function button (not shown). On detection of execution of the "End Revision" function button, at step 74, the system 12 prompts the member to enter an encryption key of his or her choice and encrypts, at step 76, the questionnaire. The encrypted questionnaire is saved onto the database 16 of the system 12.

Additionally, the questionnaire includes fields to collect data associated with the member's nominated trustee. The system 12 requests the member to enter the full name of the trustee and a nominated password. The data repositor system 10 is adapted to permit a nominated trustee to access a read only copy of the member's information.

2. Upload

The member is able to use the system 12 to receive and store additional information. The additional information includes images of the member and other non-text data about the member. The member can execute the "Upload" function button 54 on his or her web page 50 to transfer the additional information on to the system 12. On execution of the "Upload" function button 54, the system generates the Upload web page 80 shown in Figure 7. The Upload web page 80 includes:

a. A "Personal Images" function button 82; b. A "Video" function button 84; c. A "Fingerprint" function button 86; d. A "DNA" function button 88; e. A "Vehicle Images" function button 90; f. A "Valuables" function button 92; g. A "Documents" function button 94; h. A "Handwriting Samples" function button 96; i. A "Signature Samples" function button 98; j. A "Voice Samples" function button 100; and k. A "Dental Recording" function button 102.

A description of the processes performed by the system 12 on execution of each one of the above-mentioned functions is set out below.

a. Personal Images

On execution of the "Personal Images" function button 82, the system generates the Personal Images web page 104 shown in Figure 8. The Personal Image web page 104 includes a list 106 of images that have previously been uploaded to the system 12. The member can select an image from the list presented to him or her on his or her computer terminal 18 and then execute the "Edit" function button 108 to enter some descriptive text associated with the image. The image is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. The image can be stored in any other suitable format.

The member can add an image to the list by executing the "Upload Personal Image" function button 1 10. On detection of execution of the "Upload Personal Image" function button 1 10, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 106. The member can attach some descriptive text to the image by selecting the image from the list 106 and then executing the "Edit" function button 108 in the above described manner.

b. Video

On execution of the "Video" function button 84, the system 12 generates the Video web page 1 12 shown in Figure 9. The Video web page 1 12 includes a list 114 of videos that have previously been uploaded to the system 12. The member can select a video from the list 1 14 presented to him on his computer terminal 18 and then execute the "Edit" function button 1 16 to enter some descriptive text associated with the video. The video is preferably stored on the system 12 as a Windows Media ™ video file. Alternatively, the video can be stored in any other suitable format.

The member can add a video that they have taken to the list 1 14 by executing the "Upload New Video" function button 118. On detection of execution of the "Upload New Video" function button 1 18, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 1 14. The member can attach some descriptive text to the video by selecting the video from the list 1 14 and then executing the "Edit" function button 1 16 in the above described manner.

c. Fingerprint

The forensic pack sent to the member by the system 12 includes a card for taking fingerprints and an ink pad. The member can use the card to create a record of his or her finger prints. The record can be scanned and saved as a data file for uploading to the system 12.

The member can execute the "Fingerprint" function button 86 to upload his or her fingeφrint file. On execution of the "Fingerprint" function button 86, the system 12 generates the Fingerprint web page 120 shown in Figure 10. The Fingerprint web page 120 includes a list 122 of fingerprint files that have been previously uploaded on to the system 12. The member can select a file from the list 122 and then execute the "Edit" function button 124 to enter some descriptive text associated with the selected file. The fingerprint file is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. Alternatively, the video can be stored in any other suitable format.

The member can add a fingerprint file that they have prepared in the described manner to the list 122 by executing the "Upload New Fingerprint File" function button 126. On detection of execution of the " Upload New Fingerprint File" function button 126, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 122. The member can attach some descriptive text to the file by selecting it from the list 122 and then executing the "Edit" function button 124 in the above described manner.

d. DNA

The forensic pack sent to the member by the system 12 also includes:

a. A DNA test Kit; b. A post paid envelope addressed to a genetic sequencing laboratory; and c. Written instructions on how to use the DNA test kit

An example of a DNA test kit is disclosed in PCT/US96/ 18276. Such a kit would be suitable for use with preferred embodiments of the invention.

Once the member has completed the DNA test and sent the resultant sample to the genetic sequencing facility, he or she waits to receive the test results. The member will receive the results in written form and in the digital form on a CD, for example. The member can execute the "DNA" function button 88 to upload his or her DNA sequence file. On execution of the "DNA" function button 88, the system 12 generates the DNA web page 128 shown in Figure 1 1. The DNA web page 128 includes a list 130 of DNA files that have been previously uploaded on to the system 12. The member can select a file from the list 130 and then execute the "Edit" function button 132 to enter some descriptive text associated with the selected file.

The member can add a DNA file that they have prepared in the described manner to the list 130 by executing the "Upload New DNA File" function button 134. On detection of execution of the " Upload New DNA File" function button 134, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 130. The member can attach some descriptive text to the file by selecting it from the list 130 and then executing the "Edit" function button 132 in the above described manner.

e. Vehicle Images

On execution of the "Vehicle Images" function button 90, the system 12 generates the Vehicle Images web page 136 shown in Figure 12. The Vehicle Images web page 136 includes a list 138 of images that have previously been uploaded to the system 12. The member can select an image from the list presented to him on his computer terminal 18 and then execute the "Edit" function button 140 to enter some descriptive text associated with the image. The image is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. Alternatively, the image can be stored in any other suitable format.

The member can add an image to the list by executing the "Upload New Vehicle File" function button 142. On detection of execution of the "Upload New Vehicle File" function button 142, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 138. The member can attach some descriptive text to the image by selecting the image from the list 138 and then executing the "Edit" function button 140 in the above described manner.

f. Valuables

On execution of the "Valuables" function button 92, the system 12 generates the Valuables web page 144 shown in Figure 13. The Valuables web page 144 includes a list 146 of images that have previously been uploaded to the system 12. The member can select an image from the list presented to him on his computer terminal 18 and then execute the "Edit" function button 148 to enter some descriptive text associated with the image. The image is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. Alternatively, the image can be stored in any other suitable format.

The member can add an image to the list 146 by executing the "Upload New Valuables File" function button 150. On detection of execution of the "Upload New Valuables File" function button 150, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 146. The member can attach some descriptive text to the image by selecting the image from the list 146 and then executing the "Edit" function button 148 in the above described manner.

g. Documents

On execution of the "Documents" function button 94, the system 12 generates the Documents web page 152 shown in Figure 14. The Documents web page 152 includes a list 154 of images that have previously been uploaded to the system 12. The member can select an image from the list presented to him on his computer terminal 18 and then execute the "Edit" function button 156 to enter some descriptive text associated with the image. The image is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. Alternatively, the image can be stored in any other suitable format.

The member can add an image to the list 154 by executing the "Upload New Document File" function button 158. On detection of execution of the "Upload New Document File" function button 158, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 154. The member can attach some descriptive text to the image by selecting the image from the list 154 and then executing the "Edit" function button 156 in the above described manner.

h. Handwriting Samples

On execution of the "Handwriting Samples" function button 96, the system 12 generates the Handwriting web page 160 shown in Figure 15. The Handwriting web page 160 includes a list 162 of images that have previously been uploaded to the system 12. The member can select an image from the list presented to him on his computer terminal 18 and then execute the "Edit" function button 164 to enter some descriptive text associated with the image. The image is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. Alternatively, the image can be stored in any other suitable format.

The member can add an image to the list 162 by executing the "Upload New Handwriting File" function button 166. On detection of execution of the "Upload New Handwriting File" function button 166, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 162. The member can attach some descriptive text to the image by selecting the image from the list 162 and then executing the "Edit" function button 164 in the above described manner.

i. Signature Samples On execution of the "Signature Samples" function button 98, the system 12 generates the Signature web page 168 shown in Figure 16. The Signature web page 168 includes a list 170 of images that have previously been uploaded to the system 12. The member can select an image from the list presented to him on his computer terminal 18 and then execute the "Edit" function button 172 to enter some descriptive text associated with the image. The image is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. Alternatively, the image can be stored in any other suitable format.

The member can add an image to the list 170 by executing the "Upload New Signature File" function button 174. On detection of execution of the "Upload New Signature File" function button 174, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 170. The member can attach some descriptive text to the file by selecting the file from the list 170 and then executing the "Edit" function button 172 in the above described manner.

j. Voice Samples

The member can up load a pre-recorded voice sample on to the system by executing the "Voice Samples" function button 100, the system 12 generates the Voice Samples web page 176 shown in Figure 17. The Voice Samples web page 176 includes a list 178 of voice sample files that have previously been uploaded to the system 12. The member can select a file from the list presented to him on his computer terminal 18 and then execute the "Edit" function button 180 to enter some descriptive text associated with the file. The file is preferably stored on the system 12 as a Windows Wave (audio format/file extension) data file. Alternatively, the image can be stored in any other suitable format.

The member can add a file to the list 178 by executing the "Upload New Voice File" function button 182. On detection of execution of the "Upload New Voice File" function button 182, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 178. The member can attach some descriptive text to the file by selecting the file from the list 178 and then executing the "Edit" function button 180 in the above described manner.

k. Dental Recording

The forensic pack sent to the member by the system 12 also includes a dental card that can be completed by the member's dentist. The dental card includes all relevant dental information about the member. Once completed, the card can be scanned and saved as a data file to be uploaded onto the system 12.

On execution of the "Dental Recording" function button 102, the system 12 generates the Dental Recording web page 184 shown in Figure 18. The Dental Recording web page 184 includes a list 186 of images that have previously been uploaded to the system 12. The member can select an image from the list presented to him on his computer terminal 18 and then execute the "Edit" function button 188 to enter some descriptive text associated with the image. The image is preferably stored on the system 12 as a Joint Photographic Experts Group (JPEG) data file. Alternatively, the image can be stored in any other suitable format.

The member can add an image to the list 186 by executing the "Upload New Dental File" function button 190. On detection of execution of the "Upload New Dental File" function button 188, the system 12 prompts the member to enter the file name and path of the file that he or she wants to up load from his or her computer to the system 12. The system 12 uploads the selected file and adds it to the list 186. The member can attach some descriptive text to the file by selecting the file from the list 186 and then executing the "Edit" function button 188 in the above described manner.

3. Save The member can save the uploaded data onto the database 16 by executing the "Save" function button 56. On detection of execution of the "Save" function button 56 the system prompts the member for an encryption key, encodes the relevant data files and saves the files onto the database 16.

4. Activity Log

The system 12 facilitates use of an activity log so that a traveller can regularly update the system 12 with his or her travel history and travel plans. For example, a traveller can use an Internet cafe to log onto his or her web page provided by the system 12 and enter daily or weekly events into the system 12. The Activity log can be accessed in a time of need to determine where the member has been and/or where he or she was planning to go.

The system 12 generates the Activity Log web page 192 shown in Figure 19 on detection of execution of the "Activity Log" function button 58. The Activity Log web page 192 includes a list 194 of previous log entries. The member can select a previous log entry from the list and then execute the "Edit" function button 196 to amend the log entry.

The member can add a log entry to the list 194 by executing the "New Log" function button 198. On detection of execution of the "New Log" function button 198, the system 12 generates the Log form 200 shown in Figure 20. The Log form 200 includes a data box 202 for entering text. The member can enter all relevant data about their activities in the data box 202. The member executes the "Save" function button 204 when done entering data into the data box 202. The system saves the new log as a data file and includes it in the list 194.

The more precise and complete the details entered, the greater the likelihood that the data will be of assistance, if required. It is suggested, that the member does not merely enter "going to a meeting at XXX". Rather, it is recommended that the member describe in detail how he or she will proceed to that meeting. For example, the route that is to be taken, method of transport to be utilised, estimated time of departure and arrival, anticipated duration of the meeting, post meeting activities.

5. User Tools

The system 12 generates the User Tools web page 210 shown in Figure 21 on execution of the "User Tools" function button 60. The User Tools web page 210 includes the following links for the member:

a. Web-based diary 212; b. International currency converter 214;

C. Red Cross 216; d. American Express website 218; e. VISA website 220; f. Diners Club website 222; g- Galileo view trip website 224; h. AOL international directories website 226; i. World Health Organisation website 228; j- CIA World Fact Book 230; k. INTERPOL website 232;

1. www.weather.com 234; and m. World clock website 236.

6. Emergency Links

The system 12 generates the Emergency Links web page 240 shown in Figure 22 on execution of the "Emergency Links" function button 62. The Emergency Links web page 240 includes the following links for the member:

a. National police services in the world 242; b. Major international policing bodies 244; c. US, Australian and UK regional and state policing bodies 246; d. Member Country Departments of Foreign Affairs or similar 248; e. Member country travel advisory sites 250; f. Member country travel health services 252; and g. Humanitarian agencies 254. Using the System

A member can obtain a hard copy of his or her information stored on the system 12 and keep a copy on stand by in case of an emergency. The location of the hard copy can be distributed to friends and family so that if the member goes missing, a family member, for example, can pick up the hard copy and hand it over to the relevant authorities. This is a document that can be provided to the first responding officer in the case of an emergency. Immediately the first responder has all the information they need regarding that individual.

Alternatively, a member, or any other person that has the member's login details and encryption key, can access the member's user profile on the system 12 and quickly obtain all information relevant to locating the person, for example. The information can be accessed from anywhere in the world by way of a communication device 18 which could be a computer terminal 18 or a mobile telephone device. Multiple persons in various locations around the world could simultaneously view the member's information. The person possessing the encryption key is the only person that can only make the file available to others. This necessarily means that the client must have faith and trust in someone else to perform this role should the need arise.

Otherwise, a nominated trustee can access the system 12 web page and log in using their full name and password. On detection of a correct trustee name and password, the system 12 generates a read only copy of the relevant member's information. The trustee can access this information in the event of an emergency. The read only copy of the member's information is preferably a portable document format (*.PDF) file. The information includes, amongst other things, the member's identification data and diary records.

The User Tools web page 210 and the Emergency Links web page 240 include a number of tools and links which can put the member in touch with national law enforcement bodies in every country around the world. The emergency links can be used by the client, or their authorised representative, to contact and communicate with international law enforcement, humanitarian, and government officials when there is concern for a member away from his OT her home country.

A preferred implementation of the above described system 12 is described in detail in

Appendix B. The description of the system 12 is set out under the following headings:

1. Introduction;

2. System overview;

3. System configuration specification;

4. Detailed Design Specification; and 5. Requirements design traceability.

Many modifications of and applications for the system 10 will be apparent to those skilled in the relevant art without departing from the scope of the present invention as hereinbefore described with reference to the accompanying drawings.

Throughout this specification, unless the context requires otherwise, the word "comprise", and variations such as "comprises" and "comprising", will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps.

The reference to any prior art in this specification is not, and should not be taken as, an acknowledgment or any form of suggestion that the prior art forms part of the common general knowledge in Australia. APPENDIX A

APPENDIX B

Application Functional Specification

1 Introduction

1.1 Purpose

1.1 System Description

The Mercury Files Web application will act as a web based repository for collecting, storing and distributing information about an individual. The application will also provide other functionality such as a

• Content Management System

• Ecommerce transaction processing

• Travellers Diary

1.1.2 Document overview This Design Document provides the following:

• Description of the high level features and functionality of the Mercury Files Website .

• Identification of the components (software, hardware, platform, etc.) necessary for the implementation of Mercury Files Website. • Description of the design specifications necessary to build and maintain the Mercury Files Website.

1.2 Scope

1.2.1 In Scope

Page layout and design, site taxonomy, menu navigation, database content and use. 1.1.2 Out of Scope

Content and subject of material provided for posting on the Mercury Files Website .

1.2 Terms/Acronyms

This document contains the following terms, acronyms and abbreviations.

Any trademarks used in this document remain the property of their respective owners .

1.3 Reference documents

A document has been provided "Mercury Files - Overview" the document contains database schema and limited functionality descriptions.

1.4 Revisions

This document will be updated to reflect desired changes in the website that result in changes to requirements.

If the change is minor, the document version number will be incremented in decimal numbers (i.e., 1.0 will become 1.1) and no signatures will be collected.

A minor change includes changes to all out-of scope issues except where these are covered by an Exception document.

Major changes, such as those made with a new version of the website, will result in the version number incrementing to the next whole number (i.e., 1.3 will become 2.0) and signatures will be required. 2 System Overview

2 . 1 Basic functions and features

2 . 2 System usage

The Mercury Files Webs ite is open to the I nternet . All users accessing the s ite wil l be able to view the Publ ic content . Subscribers wi ll be able to edit thei r own record .

Subscribers nominated Trustees a re able to view a subscriber ' s record and generate a PDF to make avai lable for viewing by nominated pa rties .

2 . 3 System Architecture The Mercury Files Website will be hosted at a local 3^rd party hosting facility.

The Content Management System will be developed in Farcry. Farcry is an open source CMS running on ColdFusion Application server.

The Mercury Files application will be developed on an MVC architecture allowing for a separation The Model-View-Controller ("MVC") design pattern decouples the model from its view, enabling loose coupling and the ability to change one without affecting the other .

The model is the application object. In this architecture, the model is implemented using a combination of Cold Fusion Components (CFCs) and other business objects. These may access/encapsulate business logic by:

• Connecting to a local or remote database,

• Wrapping business logic that may run on the application server

• Interact with remote business logic via a messaging service

The view consists of the presentation layer, as seen by the end user. This is implemented using Cold Fusion Server MX (CFM) .

In order to achieve loose coupling the following ideals should be enforced:

• The model should operate independently from the manner in which the view i"teracts with the user.

• The view should be tailored to meet the interaction needs of the user, independent of the model below it.

The controller co-ordinates application flow, invoking model components in response to user requests over the web, and presenting the results of business processes to the user via CFMs. The controller is implemented using CFC technology, which contains the session control needed to maintain state during a user session.

This architecture provides a clean separation between application layers at each tier, and maps onto application development tools that are accurately aligned with the roles and responsibilities of members of the development team.

A diagram showing how the Web Application Architecture is mapped onto components of the application is set forth below

Presentation Layer Business Layer Data Layer

VIEW MODEL

2.4 Interface Diagram End Users

2.4.1 Subscribe to service

Access to the service is available via the public internet site at http: //www. mercury files . net . Subscription to the service requires a credit card or a PayPal account.

2.4.2 Payment gateway path tStep>S»Ii SActA-ϋnffl feAlr-ter-natetuserSpath'*

User has completed Use case "Subscribe to service"

I f corporate use r , selects how many seats to be purchased

• 5

• 10

• 20

• 50

• 100

• etc

3.1 An authenticated user is presented with a form with available fields pre-filled

User enters form data

• Title*

• First name*

• Surname*

• Email*

• Phone number (me country code)

• Postal/Street address*

• City*

• State

• Postcode*

• Country

Credit card Details

• Card Type*

• Name on card*

• Card number*

• Expiry date* (mm/yyyy)

• Verification code* (* required fields)

3.2 If using PayPal, user enters PayPal

2.4.3 Subscriber Login

2.4.4 Add new Corporate Account Subscriber sm Navigate to https://secure.mercuryfiles.net

User enters username Incorrect username/password combination

Message displayed.

A user is allowed 3 unsuccessful attempts. Then locked out for 20 minutes, or directed to have password resent.

User clicks submit button Message displayed that a password must be entered

User enters password

User clicks submit button Message displayed that a username must be entered

User enters password and username

User clicks submit button Incorrect username/password combination entered

Message displayed.

A user is allowed 3 unsuccessful attempts. Then locked out for 20 minutes, or directed to have password resent use case "forgotten password. "

2.4.5 Corporate Account Managers

The system allows for corporate account managers to be added Edit and deleted. There must always be a corporate account manager for an account. To ease management issues all managers can create edit and delete like managers.

Managers will kept in the table security with a "UserRole_lookUp" type of "AccountManager" An account can have multiple account managers.

Navigate to https://secure.mercuryfiles.net

User (type = corporate account Incorrect manager) enters username username/password

2.4.6 Edit Corporate Account Manager us use case represents the adding a new account manager.

2.4.7 Add new Corporate Account Manager

This use case represents the process for adding a new account manager.

2.4.8 Delete Corporate Account Manager

This use case represents the process for deleting an account manager. There must always be al least a single account manager.

2.4.9 Edit Family Account Manager

The system allows for account managers to be updated and edited.

2.4.10 Add email access to child family member

By default child family subscribers do not have email access to the application. For a child to have access they must be subscribed by the account manager. They do not have access to any family account records except their own. The child must be a subscribed user of the system in order to be granted access.

fiAl*ernate-fuserSpat-h'i

Navigate to https://secure.mercuryfiles.net

User enters username Incorrect username/password combination

2.4.11 Add new child to family subscription account

The application allows for 3 children in the current family package. More child seats can be added as required

2.4.12 Data Key Generation Process

When a new applicant begins using the application they must generate a data access key with which to encrypt all data within the mercury files personal data held within the database.

2.4.13 Update password

Click Update Password

User inputs current password

User enters new password

User enters new password verification

User submits Message displayed

• Passwords do not match

• Password does not conform to password complexity algorithm

User is asked to select a question to answer

For example:

• first dogs name

• favourite sports team

New password updated message

. 4 . 14 Trustee forgotten password

2.4.15 Subscriber forgotten Password

A lost password can only be recovered if the security question and answer have been entered at the time of subscription

Navigate to http://www.mercuryfiles.net

Select menu option Login

Click Recover Password

Password Recovery screen lists the No security questions previously selected question to answer submitted on by the Subscriber when they originally subscription subscribed

Message displayed

Subscriber answers the security question Incorrect answer Message displayed

An email notification is sent to the User ignores received registered email address. It contains a email link to the "password reset" (pr) . It will contain a random string that will act as a lookup. The url would look like https: //secure. mercuryfiles.net/pr/ d438rwiuodw894732ehdw

asking if they requested the password to be reset. If this is correct the user will click on a link appended with a unique string that will take them to a page where the password is able to be changed. , refer to Use Case 2.4.3 - Update Password

The user follows the link. The

A Schedule task (cron job) will regularly delete any request older than 8 hours

2.4.18 Manage Trustees - Add

A user can appoint up to a maximum of five Trustees.

2.4.19 Manage Trustees -Delete

Subscribers can revoke a Trustees access at any time.

2.4.20 Create diary entry

Subscribers are advised to update their diary on a regular basis.

2.4.21 Trustee logs in to system

Nominated Trustees are able to log in to the system and view data and diary records for users.

2.4.22 Trustee logs in to system for the first time

When a Subscriber adds a Trustee, the Trustee receives an email containing their username and password and is advised to contact the Subscriber to get tne DdLa Access Key.

2.4.23 Trustee reads Subscribers' Mercury Files

A Trustee can read all details entered by the Subscriber but cannot edit the files.

2.4.24 Report an incident

Subscribers are advised to keep in touch with Trustees while travelling, so that the Trustees will be alerted to the fact that an incident has occurred. Regular diary entries will help to ensure that the most up-to-date information about the Subscribers movements is available.

2.4.25 Generate an incident report

In the event that a trustee has contact the appropriate agency and advised the agency of the existence of a "Mercury File" the trustee is able to provide the previously created Mercury file to the agency.

The Trustee has logged in with previously provided credentials and bona fides have been checked in relation to data held

If there is more than one subscriber select the subscriber record you wish to generate a report for.

Enter email address provided by law Invalid email address enforcement agency Message displayed

Select Generate Incident Report

System generates PDF document with details of Subscriber and places it in a temporary holding directory separate to the database. Copies of images and videos are also placed in the directory.

The System will generate a username and

2.4.26 Collecting Generated Mercury Files

2.4.27 Agency Support notification process

In the event that a subscriber has not had contact with a trustee for a previously agreed period of time, the trustee may notify relevant agencies.

2.4.28 View Subscription reports

The application accepts payments fro subscriptions from users. A report will need to be available to generate for reconciliation process. A CSV file could also be generated upon request.

2.4.29 Renewal notification process

Users of the system are subscribed on an annual basis. Users will need to be notified of renewal subscription 60 days prior to renewal fall due date. A scheduled task will run daily to send email notifications of renewal falling due.

Once a renewal has occurred no more notifications of renewal will be sent until the next renewal period falls due.

2.4.30 Edit details

Subscribers can edit their details at any time.

User has completed use case Subscriber Login successfully

Select menu option Edit My Details

Select section to be edited

Scroll to appropriate entry in chosen section

Edit details

Click Save Changes

2 . 4 . 31 Manage multilingual form fields management

The appl ica tion displays form f ields in the chosen language of the use r . The languages avai lable are

• English

• Chinese (Mandarin) • Spanish

• French

• German

• Italian

• Portuguese • Japanese

3 System Configuration Specification

3.1 Hardware

Hardware Vendor Hardware Name Hardware Version

Unknown Unknown Unknown

3.2 Operating System

Operating System Operating System

Operating System Name Vendor Version unknown unknown Unknown

3.3 Database Management System

Database management

Software Name Software Version System Vendor

Unknown unknown

3.4 Data Movement Too]

Software Vendor Software Name Software Version

3.5 Vendor Software

Software Vendor Software Name Software Version unknown unknown Unknown

3.6 Custom Software

4 Detailed Design Specification

1. Layout

The existing layout will be used.

2. Navigation

Web sites need menus of their own. Because the look and feel varies so much from site to site, the visitor doesn't always find a familiar navigation model. Designer should make sure that visitor recognizes the tools that you provide as navigation aides and to present them in a logical and attractive manner.

4 . 1 Data Definition

4 . 1 . 1 Security

Table name: Subscribers

Description : This table contains the subscribers "Mercury Files", All the data in this table is encrypted (except subnumberID) with the subscribers chosen key.

Table data Column Name Data Type Allow elements : Nulls subnumberID mt No

CustomerID accUsername nvarchar (16) No subFamilyName nvarchar (40) Yes subFirstName nvarchar ( 40) Yes subOtherGivenNames nvarchar (40) Yes subPreferredName nvarchar (40) Yes subNamesAlsoKnownBy nvarchar (60) Yes subDOB datetime Yes subPlaceOfBirth nvarchar (50) Yes subCountryOfBirth nvarchar (60) Yes subSexuality tinyint Yes subReligion nvarchar (30) Yes

SubPracticmg tinyint Yes subCurrentResidentialAddress nvarchar (100) Yes subLengthOfResidency nvarchar (10) Yes subPreviousAddresses nvarchar (500) Yes subCurrentPostalAddress nvarchar ( 100) Yes subPreviousIyMissing tinyint Yes subPreviouslyMissingDetails ntext Yes subPreviousIyMissmgPoliceInvolvement tinymt Yes subPreviouslyMissingOfficer nvarchar (60) Yes subPreviouslyFmgerprinted tinymt Yes subPreviousIyFingerprintedDetaiIs ntext Yes subCrimmalRecord tmyint Yes subCrimmalRecordDetails ntext Yes subPreviousIyJailed tinyint Yes subPreviouslyJailedDetails ntext Yes subHasWill tinyint Yes subWillPreparedBy nvarchar ( 100) Yes subWi11Location nvarchar ( 100) Yes subInsurancePolicies ntext Yes subGender tinyint Yes subHeightMetric nvarchar (10) Yes subHeight Imperial nvarchar ( 10) Yes subWeightMetric nvarchar ( 10) Yes subWeightImperial nvarchar (10) Yes subEyeColour nvarchar (20) Yes subHairColour nvarchar (20) Yes subHairStyle nvarchar (50) Yes subHairdresser ntext Yes subComplexion nvarchar (50) Yes subFacialHair tinyint Yes subFacialHairDetails nvarchar (40) Yes subVisionImpaired tinyint Yes subGlasses tinyint Yes subGlassesDetaxls nvarchar ( 100) Yes subGlasses PrescribedBy nvarchar ( 100 ) Yes subContactLenses tinyint Yes subContactLensesColour nvarchar (20) Yes subContactLensesPrescribedBy nvarchar (100) Yes subBraces tinyint Yes subMouthPlate tinyint Yes subDentures tinyint Yes sublndentifyingMarks tinyint Yes subScars ntext Yes subTattoos ntext Yes subBirthmarks ntext Yes subPiercings ntext Yes subDeformities ntext Yes subAmputations ntext Yes subImpairment ntext Yes subCircumcised tinyint Yes subDommantHand tinyint Yes subShoeSize nvarchar (10) Yes subBuild nvarchar (20) Yes subFashion nvarchar (20) Yes subTypicalOutfit ntext Yes subDoctors ntext Yes subDentists ntext Yes subSpecialists ntext Yes subBloodType nvarchar (10) Yes subPreviouslySoldBlood tinyint Yes subPreviouslySoldBloodDetails ntext Yes subPregnant tinyint Yes subBirthDueDate datetime Yes subPregnancyComplications ntext Yes subVaccmationHistory ntext Yes subSensoryDeprivation ntext Yes subSpeechlmpediment ntext Yes subPhysicalDysfunction ntext Yes subMedicalConditions ntext Yes subMentalDisorders ntext Yes subPsychologicalDisorders ntext Yes subAllergies ntext Yes subPreviousSurgery ntext Yes sublnj uryAndXRays ntext Yes subMedication ntext Yes subAlcohol ntext Yes subTobacco ntext Yes sublllicitDrugs ntext Yes subMedicareSocialSecurity nvarchar (20) Yes subMedicAlert tinyint Yes subFirstAidTraining tinyint Yes subSurvivalSkills tinyint Yes subEducational Institutions ntext Yes subTertiaryQualifications ntext Yes subTradeQualifications ntext Yes subSchoolStudent tinyint Yes subSchoolName nvarchar (100) Yes subSchoolAddress nvarchar (70) Yes subSchoolTelephone nvarchar (20) Yes subSchoolFax nvarchar (20) Yes subSchoolEmail nvarchar ( 60) Yes subSchoolSickBayTelephone nvarchar (20) Yes subSchoolPrincipal nvarchar (70) Yes subSchool FuI1OrPartTime tinyint Yes subCurrentCourses ntext Yes subPreviousEmployment tinymt Yes subPreviousEmploymentDetails ntext Yes subCurrentEmployment tinyint Yes subCurrentEmployer nvarchar (120) Yes subCurrentEmployerAddress nvarchar (70) Yes subCurrentEmployerTelephone nvarchar (20) Yes subCurrentEmployerFax nvarchar (20) Yes subCurrentEmployerMobile nvarchar (20) Yes subCurrentEmployerPager nvarchar (20) Yes subCurrentEmployerEmail nvarchar ( 60) Yes subCurrentSupervisor nvarchar (120) Yes subCurrentSupervisorTelephone nvarchar (20) Yes subCurrentPosition nvarchar (200) Yes subCurrentDuties ntext Yes subTimeWithCurrentEmployer nvarchar (20) Yes subCoworkerDetails ntext Yes subWorkSocialDetails ntext Yes subOffSiteWork ntext Yes subEmploymentID ntext Yes subSecurityCodeKnowledge tinyint Yes subAffiliations tinymt Yes subAffillationsDetails ntext Yes subDayCare tinyint Yes subDayCareDetails ntext Yes subVolunteer tinyint Yes subVolunteerDetails ntext Yes subProfessionalAffiliations ntext Yes subBusinessAssociations ntext Yes subLitigation ntext Yes subBankruptcy ntext Yes subRecreation ntext Yes subHolidayDestinations ntext Yes subKnownSocialLocations ntext Yes subDistinctiveItems ntext Yes subTransport ntext Yes subPublicTransport ntext Yes subBicycle tinyint Yes subPram tinyint Yes subWalk ntext Yes subSafetyZone ntext Yes subFinanciallnstitutions ntext Yes subStocks ntext Yes subCreditInstitutions ntext Yes subRealEstate ntext Yes subAssets ntext Yes subInternetBar.kirgAccounts ntext Yes subMotorVehicles ntext Yes subFamilyMotorVehicles ntext Yes subPets ntext Yes subMinor tmyint Yes subCustody ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: subNumberID

Foreign Key Name: FK careagencies subscribers

FK carers subscribers

FK children subscribers

FK diary subscribers

FK driverslicences subscribers

FK extendedfamily subscribers

FK fathers subscribers

FK files subscribers

FK friends subscribers

FK generalphone subscribers

FK legalguardians subscribers

FK mobilephone subscribers

FK mothers subscribers

FK nationalities subscribers

FK partners subscribers

FK ref PlamTextLookUp subscribers

FK ref TrusteeSubLookϋp subscribers

FK siblings subscribers

FK subscribers account

FK trustees subscribers

FK subscribers security

4.1.2 Security-

Table name: Security

Description : This table regulates all access to the application. It also verifies DOB of users.

Table data elements: Column Name Data Type Allow Nulls subNumberID int Unchecked

CustomerID uniqueidentifier Checked

4.1.3 Nationalities

4 . 1 . 4 Friends

Table name: Friends

Description : This table records all subscribers 'friends' information.

All the data in this table is encrypted (except subnumberID) with the subscribers chosen key.

Table data elements: Column Name Data Type Allow Nulls friendsID int No subNumberID int No subFriendName nvarchar (120) Yes subFriendDOB datetime Yes subFπendAddress nvarchar (70) Yes subFriendPreviousAddress ntext Yes subFriendPostalAddress nvarchar (70) Yes subFπendTelephone ntext Yes subLengthOfFriendship nvarchar (20) Yes subHowMetFriend ntext Yes subFriendOccupation ntext Yes subFriendMotorVehicles ntext Yes dateCreated datetime No dateLastupdated datetime yes

Primary Key Name: FriendsID

Foreign Key Name: FK friends subscribers

4 . 1 . 5 Fathers

Table data elements: Column Name Data Type Allow Nulls

FatherID int No subNumberID int No subTypeOfFather tinyint Yes subFatherAlive tinyint Yes subFatherKnown tinyint Yes subFatherName ntext Yes subFatherDOB datetime Yes subFatherAddress nvarchar (70) Yes subFatherPreviousAddress ntext Yes subFatherPostalAddress nvarchar (70) Yes subFatherTelephone ntext Yes subFatherMedicare nvarchar (20) Yes subFatherNationality ntext Yes subFatherDriversLicenee ntext Yes subFatherOccupation ntext Yes subFatherRelationship ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: FatherID

Foreign Key Name: FK fathers subscribers

4.1.6 LegalGuardians

Table data elements : Column Name Data Type Allow Nulls legalguardianID int No subNumberID int No subLegalGuardianKnown tinyint Yes subLegalGuardianName ntext Yes subLegalGuardianDOB datetime Yes subLegalGuardianAddress nvarchar (70) Yes subLegalGuardianPreviousAddress ntext Yes subLegalGuardianPostalAddress nvarchar (70) Yes subLegalGuardianTelephone ntext Yes subLegalGuardianNationality ntext Yes subLegalGuardianOccupation ntext Yes subLegalGuardianOrigmalRelationship ntext Yes subLegalGuardianRelationship ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: legalguardianID

Foreign Key Name: FK legalguardians subscribers

4 . 1 . 7 Partners

subPartnerName nvarchar (120) Yes subPartnerDOB datetime Yes subPartnerAddress nvarchar (70) Yes subPartnerPreviousAddress ntext Yes subPartnerPostalAddress nvarchar (70) Yes subPartnerTelephone ntext Yes subPartnerMedicare nvarchar (20) Yes subPartnerNationality ntext Yes subPartnerDπversLicence ntext Yes subPartnerOccupation ntext Yes subPartnerStatusLength ntext Yes subPartnerCohabitationalLength nvarchar (20) Yes subPartnerRelationalDifficulties ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: partnerID

Foreign Key Name: FK partners subscribers

4.1.8 General Phone

4.1.9 Driver Licence's

4.1.10 Trustees

4.1.11 Trustee Sub look up table

4.1.12 Trustee Sub look up table

4.1.13 CareAgencies

4.1.14 Carers

carerID int No subNumberID int No subCarerName nvarchar (120) Yes subCarerDOB datetime Yes subCarerAddress nvarchar (70) Yes subCarerTelephone ntext Yes subCarerLength nvarchar (20) Yes subCarerOccupation ntext Yes subCarerMotorVehicles ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: carerID

Foreign Key Name: FK carers subscribers

4.1.15 Mobile Phone

4 . 1 . 16 Siblings

Table name : Siblings

Description : This table records all a subscribers sibling information .

Table data elements: Column Name Data Type Allow Nulls siblingID int No subNumberID int No subTypeOfSibling tinyint Yes subSiblingKnown tmyint Yes subSiblingName ntext Yes subSiblmgDOB datetime Yes subSiblmgAddress nvarchar (70) Yes subSiblingPreviousAddress ntext Yes subSiblingPostalAddress nvarchar (70) Yes subSiblingTelephone ntext Yes subSiblingNationality ntext Yes subSiblingOccupation ntext Yes subSiblingRelationship ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: siblingID

Foreign Key Name: FK siblings subscribers

4 . 1 . 17 Passports

4 . 1 . 18 Children

Table name: Children

Description : This table records all a subscribers Child information .

Table data elenents: Column Name Data Type Allow Nulls childID int No subNumberID int No subTypeOfChild tinyint Yes subChildKnown tinyint Yes subChildName ntext Yes subChildDOB datetime Yes subChildAddress nvarchar (70) Yes subChildPreviousAddress ntext Yes subChildPostalAddress nvarchar (70) Yes subChildTelephone ntext Yes subChildNationality ntext Yes subChildOccupation ntext Yes subChiIdReIationship ntext Yes

4.1.19 Extended Family

Table name: ExtendedFamily

Description : This table records all subscribers Partner information .

Table data elements: Column Name Data Type Allow

Nulls extendedfamilyID int No subNumberID int No subTypeOfFamilyMember nvarchar (30) Yes subFamilyMemberKnown tinyint Yes subFamilyMemberName ntext Yes subFamilyMemberDOB datetime Yes subFamilyMemberAddress nvarchar (70) Yes subFamilyMemberPreviousAddress ntext Yes subFamilyMemberPostalAddress nvarchar (70) Yes subFamilyMemberTelephone ntext Yes subFamilyMemberNationality ntext Yes subFamilyMemberOccupation ntext Yes subFamilyMemberRelationship ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: extendedfamilyID

Foreign Key Name: FK extendedfamily subscribers 4 . 1 .20 Mothers

Table name: Mothers

Description : Tnis table records all a subscribers' mother information.

Table data elements: Column Name Data Type Allow Nulls motherID int No subNumberID int No subTypeOfMother tmyint Yes subMotherAlive tinyint Yes subMotherKnown tmyint Yes subMotherName ntext Yes subMotherDOB datetime Yes subMotherAddress nvarchar (70) Yes subMotherPreviousAddress ntext Yes subMotherPostalAddress nvarchar (70) Yes subMotherTelephone ntext Yes subMotherMedicare nvarchar (20) Yes subMotherNationality ntext Yes subMotherDriversLicence ntext Yes subMotherOccupation ntext Yes subMotherRelationship ntext Yes dateCreated datetime Yes dateLastupdated datetime yes

Primary Key Name: motherID

Foreign Key Name: FK mothers subscribers

4.1.21 Files

4.1.22 Plain text look up

4.1.23 Nationalities

4.1.24 Diary

4.1.25 Customers

4.1.26 Customer Payment Method

4.1.27 Reference Payment Methods

4.1.28 Customer Address Table

4.1.29 Addresses

Table name: Addresses

Description This table records a customers addresses

Table data elements : Column Name Data Type Allow Nulls

AddressID int Unchecked

Addressl nvarchar (50) Checked

4.1.30 Address Type Look up table

4.1.31 Customer subscription history

4.1.32 Form Language Look. up

Table name: FormLanguageLookup

Description : This table holds the translations for form fields

Table data elements: Column Name Data Type Allow Nulls

ID int Unchecked

FormLabelRef nvarchar (50) Unchecked

FormLabel binary (50) Unchecked

FormLabelHelp binary (50) Checked

FormLabelErrorMsg binary(50) Checked

LanguageID int Checked

Primary Key Name: ID

Foreign Key Name: FK FormLanguageLookUp ref language

4.1.33 Language References

4.1.34 Subscriber Seats Purchased

4.1.35 Agency Access

Agencies will be given access to a users trustee generated file with a username (email) password file

4.1.36 User Type Look up

The application has 5 differing user types that require access to the application

4.1.37 User Role Look up

Table name: UserRole_LookUp

Description: This table is a look up table of user

4 . 1 . 38 Forgotten password Look up

4 .2 System Inputs & Outputs 4 .2 . 1 Layout

The alignment of each page is all centred. Each page presents the same layout i.e. navigation bars at the top and sub menus on the left-hand side. The mam content is always placed in the centre.

4.2.2 Navigation The navigation will be dependant upon the input from Zoo

4.3 Site Security

The Application has 5 identified groups of Users.

4 . 4 Design Constraints

The high level of encryption used by Mercury Files will place some restrictions on the system itself. The encryption methodology is explained in further detail in the next section.

The encryption algorithm used to protect personal data is not available on all Windows versions, thus it will require Windows Server 2003 with Microsoft SQL Server 2005 as its database.

Microsoft SQL Server 2005 has a further restriction on encrypting data. The result of this restriction translates to encrypted text items being no larger than 3900 characters. This equates to about two pages of a typical Microsoft Word document. This restriction will be clearly and helpfully labelled close to text fields .

4.5 Algorithms Personal data will be encrypted using the Advanced Encryption Standard (AES). AES is commonly used in modern government, commercial and military applications. The data can only be decrypted by using a shared key, which the system will know only by its recorded SHA hashed valued (see next paragraph). This measure protects the personal data from the view of anyone apart from those who know the shared key. As the shared key is not stored in the system in its original form, Mercury Files personnel will not have access to that data, nor will it be recoverable in the event of the shared key being misplaced by the client.

Passwords and the AES shared key itself will be encrypted with the Secure Hash Algorithm (SHA) . The SHA family of algorithms produce a one-way "hash", that is a unique "word" of seemingly random characters based on the original text. This hash can not be used to determine the original text. The SHA algorithm is widely used in government, military and industry, a common example is its use in protecting data in https transactions .

Interfaces

Interfaces for site administration will be a web Application Programming Interface (API). This will be a customised solution built as required for the Mercury Files.

5 Requirements Design Traceability

The following table maps each requirement specified in the document Mercury Files Website Requirements to the design specifications detailed elsewhere in this document. Each design element and requirement is identified by an ID.

¹ M = Mandatory, D = Desirable, 0 = Optional,

Claims

THE CLAIMS DEFINING THE INVENTION ARE AS FOLLOWS:-

1. A data repository system for storing information about a person that can be later used to uniquely identify the person, said system for performing the steps of:

2. The system claimed in claim 1, said system for performing the step of generating said data representing answers to one or more of said questions for display on a communications device.

3. The system claimed in claim 1, said system for performing the step of encrypting said data representing answers to one or more of said questions using an encryption key defined by the person.

4. The system claimed in claim 3, said system for performing the steps of receiving data representing an encryption key; and generating said data representing answers to one or more of said questions for display on a communications device if the encryption key matches the encryption key defined by the person.

5. Thhee system claimed in any one of claims 1 to 4, said system for performing the step o ~ff receiving data representing a log entry for said person and storing said data representing the log entry on the computer readable data storage medium.

6. The system claimed in claim 5, said system for performing the step of encrypting the data representing the log entry using an encryption key defined by the person.

7. The system claimed in any one of claims 1 to 6, said system for performing the steps of receiving data representing biometric information about the person and storing the data representing the biometric information on the computer readable computer storage medium.

8. The system claimed in claim 7, said system for performing the step of encrypting the data representing the biometric information using an encryption key defined by the person.

9. The system claimed in claim 7 or claim 8, wherein the biometric information includes a deoxyribonucleic acid sequence of the person.

10. The system claimed in any one of claims 7 to 9, wherein the biometric information includes a dental record of the person.

11. The system claimed in any one of claims 7 to 10, wherein the biometric information includes a set of fingerprints of the person.

12. The system claimed in any one of claims 7 to 11, said system for performing the step of sending the person a package including apparatus and/or instructions for obtaining said biometric information.

13. The system claimed in claim 12, wherein the apparatus includes a deoxyribonucleic acid (DNA) sample kit.

14. The system claimed in claim 12 or claim 13, wherein the apparatus includes a dental record card.

15. The system claimed in any one of claims 12 to 14, wherein the apparatus includes a finger print kit.

16. A system for providing information about a person to assist a search operation for said person, said system for performing the steps of: (a) receiving data uniquely identifying the person; and

17. The system claimed in claim 16, said system for performing the steps of receiving data representing an encryption key from the communications device.

18. The system claimed in claim 17, wherein the step of generating data is only effected if the encryption key received from the communications device matches a corresponding encryption key defined by the person.

19. The system claimed in claim 18, wherein said data associated with the person includes answers to a plurality of questions about the person.

20. The system claimed in claim 18 or 19, wherein said data associated with the person includes biometric information about the person.

21. The system claimed in any one of claims 18 to 20, wherein said data associated with the person includes a log associated with the person.

22. A computer program for storing information about a person that can be later used to uniquely identify the person, said program for performing the steps of:

23. The program claimed in claim 22, said program for performing the step of generating said data representing answers to one or more of said questions for display on a communications device.

24. The program claimed in claim 22, said program for performing the step of encrypting said data representing answers to one or more of said questions using an encryption key defined by the person.

25. The program claimed in claim 24, said program for performing the steps of receiving data representing an encryption key; and generating said data representing answers to one or more of said questions for display on a communications device if the encryption key matches the encryption key defined by the person.

26. The program claimed in any one of claims 22 to 25, said program for performing the step of receiving data representing a log entry for said person and storing said data representing the log entry on the computer readable data storage medium.

27. The program claimed in claim 26, said program for performing the step of encrypting the data representing the log entry using an encryption key defined by the person.

28. The program claimed in any one of claims 22 to 27, said program for performing the steps of receiving data representing biometric information about the person and storing the data representing the biometric information on the computer readable computer storage medium.

29. The program claimed in claim 28, said program for performing the step of encrypting the data representing the biometric information using an encryption key defined by the person.

30. The program claimed in claim 28 or claim 29, wherein the biometric information includes a deoxyribonucleic acid sequence of the person.

31. The program claimed in any one of claims 28 to 30, wherein the biometric information includes a dental record of the person.

32. The program claimed in any one of claims 28 to 31, wherein the biometric information includes a set of fingerprints of the person.

33. The program claimed in any one of claims 28 to 32, said program for performing the step of sending the person a package including apparatus and/or instructions for obtaining said biometric information.

34. The program claimed in claim 33, wherein the apparatus includes a deoxyribonucleic acid (DNA) sample kit.

35. The program claimed in claim 33 or claim 34, wherein the apparatus includes a dental record card.

36. The program claimed in any one of claims 33 to 35, wherein the apparatus includes a finger print kit.

37. A computer program for generating information about a person to assist a search operation for said person, said program for performing the steps of:

(a) receiving data uniquely identifying the person; and

38. The program claimed in claim 37, said system for performing the steps of receiving data representing an encryption key from the communications device.

39. The program claimed in claim 38, wherein the step of generating data is only effected if the encryption key received from the communications device matches a corresponding encryption key defined by the person.

40. The program claimed in claim 39, wherein said data associated with the person includes answers to a plurality of questions about the person.

41. The program claimed in claim 39 or 40, wherein said data associated with the person includes biometric information about the person.

42. The program claimed in any one of claims 37 to 41, wherein said data associated with the person includes a log associated with the person.

43. A computer readable data storage medium, including the computer program claimed in any one of claims 22 to 43 stored thereon.