Use Case - PHR Registration

Edited by:

• Former user (Deleted)

DRAFT

Description:

Use case registration against ALREADY created MyOSCAR accounts.

1. attempts to create and link to an existing myoscar-account
2. attempts to find and link to valid existing myoscar-account
3. attempts to find and link to inactive existing myoscar-account
4. attempts to find and link to non existant myoscar-account
5. attempts to find and link to existing myoscar-account which is not a patient account

Use case registration for users/accounts that don't exist in MyOSCAR

1. attempts to create and link to a brand new myoscar-account

Use case permutations with regards to relationships / verifications :

1. linking to an existing myoscar-account whom already has a relationship established with the provider
2. linking to a new myoscar-account, what is the state of the relationships? and what should they be?
3. linking to a new myoscar-account, what should the verification level be by default? what is it now?
4. linking to an existing myoscar-account whom has a verification level set, what does it do? does it honour it or reset it? ignore it? what should it do?
5. is there an option to sign a patient up for a research study? if so does that work with new and existing myoscar-accounts?

Normal flow (positive flow) use cases :

1. Conditions: All fields valid. Use generated, unique MyOscar ID + generated password. Oscar user has valid MyOscar credentials.
   1. Process: Press Submit.
   2. Result: Success message displayed on screen. Search in MyOscar finds user.
2. Conditions: All fields valid. User-specified, unique MyOscar ID + generated password. Oscar user has valid MyOscar credentials.
   1. Process: Press Submit.
   2. Result: Success message displayed on screen. Search in MyOscar finds user.
3. Conditions: All fields valid. User-specified, unique MyOscar ID + user-specified password. Oscar user has valid MyOscar credentials.
   1. Process: Press Submit.
   2. Result: Success message displayed on screen. Search in MyOscar finds user.

PHR Registration (technical details)

Actors/Related actors:

1. care provider
2. demographic

Pre-action requirements/state:

care provider is already active in OSCAR.

Post-action state:

demographic user is now able to login to MyOSCAR and share information that has been specified through the access and sharing

Steps to perform the use case:

1. demographic and care provider work together to provide input with the registration

Failure Steps:

1. care provider and demographic don't supply mandatory fields in order to successfully register for MyOSCAR

Success Steps:

1. care provider and demographic supply all mandatory information and register the demographic for MyOSCAR successfully

Alternate Flows:

1. Register demographic in OSCAR and select Register for MyOSCAR
2. Register demographic in OSCAR and DO NOT select register for MyOSCAR

Special Requirements/Notes:

care provider must not know the demographic account password

Links: