Search for a Person

Actors

• OpenRegistry System
• User
• Database

Pre-Conditions

1. ASSUMPTION1: User has successfully authenticated into system.
2. ASSUMPTION2: User has some privileges to search for people.
3. ASSUMPTION3: User has chosen a System of Record to work with.
4. ASSUMPTION4: User is using Search as part of another flow and will thus continue on to flow.
5. ASSUMPTION5: System is configured as to which identifiers can be returned from a flow.

Flow

1. User provides values for search criteria. Currently allowed fields are:
   • First Name
   • Last Name
   • Date of Birth
   • Identifier Type / Value
   • Phone Numbers
   • Role (Title/Organization)
   • Email Address
   • Additionally, the user MUST provide a maximum number of search results to be returned.
2. Information is submitted/sent to OpenRegistry server.
3. OpenRegistry system searches for people based on the following criteria/algorithm:
   1. If an Identifier Type / Value is provided, an exact match it looked for first
   2. If an exact match is NOT FOUND, then a partial match is attempted on the identifier type/value
   3. If no matches are found, and a date of birth is provided, an exact match on the DOB should be tried, and then partial matching on names
   4. If there is no exact match for DOB, use a transposition (e.g. assume they meant European standard instead of American [or vice versa])
   5. Identifier Searches are conducted against calculated tables, while name, dob searches are conducted against System of Record tables.
   6. The maximum number of search results returned is determined by the value provided by the user.
4. Results are returned to user, along with additional meta information such as the fact that the maximum was reached. The following fields should be returned to the user:
   • Official Name
   • Gender
   • Current Roles (most likely Title/Affiliation for Each Role)
   • Defined Identifiers
5. If one (1) result is returned, user should be transitioned to next flow
6. If zero results are returned, user MUST be notified and text such as "Your search returned no results. You MAY wish to change your search terms" MUST be presented to the user.
7. If > 1, results should be presented to the user such that the user can choose which person they want and be transitioned to the next flow.

Post Conditions

1. PC1: User is transitioned to next flow upon selection (either manual or automatic) of person.

Business Rules

1. BR1: Ultimately, the fields available for search are dependent on access control levels
2. BR2: Ultimately, fields returned are dependent on access control levels
3. BR3: User MUST provide either an identifier type/value OR at least the last name. Those are the minimums. More information can be provided.