Page History

Querytool Use Cases

1. Logon
2. New Search
3. Show Search Results
4. Select Specimens
5. Process Specimen Request
6. Remap Specimens to Codebook
7. Show Specimen Request
8. Show User History
9. Restart Search
10. Delete Search
11. Source code for each use case

...

Use Case: Logon

Precondition(s):                          

...

The Ecommons authentication service can be replaced by a local identity service or any other service adhering to the Identity Service interface.

...

Use Case: New Search

Precondition(s):

• User is authenticated

...

• See the User Guide for descriptions of the Full text query expressions

...

Use Case: Show Results

Precondition(s):                        

...

If an investigator logged out, then they must rerun the query to view detailed results.

...

Use Case: Select and Request Specimens

Precondition(s):                        

• User is investigator and on the Results Page @See Show Results

Post-condition(s):

• Investigator level user can select and requested specimens

...

1. The specimen request will be saved to the querytool database (visible via the /specimens page)
2. The specimen request will be emailed to the administrator.
3. The specimen request will be sent to the pathology core system.

Alternate Paths

Notes

...

Use Case: Process Specimen Request in Pathcore (needs update-mike)

Precondition(s):                        

...

1.     ....

Alternate Paths

Notes

...

Use Case: Remap Specimens via codebook (needs doc update)

Precondition(s):                        

...

2.     ....

Alternate Paths

Notes

...

Use Case: Show Specimen Requests

...

• Specimen availability cannot be currently be queried in real time, will use a static specimen count.
  
  

...

Use Case: Show User History

Precondition(s):                        

...

Specimen Requests should not be shown in the history, @SEE Show Specimen Requests

...

Use Case: Restart Search

Precondition(s):                        

...

#3.IF the user has no assigned role, THEN assign the default public role.

...

Use Case: Delete Search

Precondition(s):                        

...

• Detailed results (including the SOAP message) are never cached in the query-interface. This is for IRB compliance and general concerns over a single centralized node.
• Once the user fetches the results from the cache once, the results are stored in the user session and removed from the cache. If the user wants to see detailed results again, then a new query must be reissued. (Statistical results still available)
  
  

...

Appendix

Primary Supporting Java Files by Use Case (Needs doc update)

...