Page Comparison

Use Case Details

This is the use case that the test case aligns to :

Edited by:

• Aaron Toth
  

   

DRAFT

Description:

Send message from OSCAR -> MyOSCAR

...

Actors/Related actors:

1. Care Provider
2. Demographic
3. Help Desk

Pre-action requirements/state:

1. Care Provider is active in OSCAR
2. Demographic is active in OSCAR and registered for MyOSCAR
3. There is an established relationship* (access and sharing) between the Demographic and Care Provider
4. A Care Provider must REPLY to messages, where Demographic users can reply and create new messages (pending accessing and sharing confirmation)

Post-action state:

1. OSCAR and MyOSCAR are running as expected.

Steps to perform the test case:

1. Login to OSCAR as a Care Provider
2. Click the Search button along the top menuthe MyOSCAR link in OSCAR and login
3. Select a message from in the inbox
4. Click Reply
5. Enter in the last name for the demographic record that you are trying to add (demographic should not exist) on the Patient Search Results page

...

1. message details and send the message

Failure Steps:

1. Not able to reply to the messages

Success Steps:

1. Messages are sent/read and the appropriate folders (inbox, sent, read, new...etc) reflect folders updated state (new, read, sent...etc)

Alternate Flows:

1. Please see each specific use case/test case for more details.

Special Requirements/Notes:

N/A

Links:

N/A