Create user story for a health application feature

Patient Encounter View for Work Lists Background • Our company develops and maintains a suite of products focused on helping hospitals and health systems manage their Revenue Cycle Operations. These solutions include data analytics that help Revenue Cycle leaders track and trend their revenue performance, including pinpointing additional opportunities for improved payments or reduced denials. The solutions also include workflows that help staff members track and manage their daily tasks, such as collecting payments from insurance payers or patients. • In one of our Revenue Cycle products, users are able to update information on accounts as they push them towards resolution. For example, they can change a status, set a follow-up date, post a note, etc. They do this by expanding a record on a detail report and updating select fields (see screen shot 1 available in uploaded file) • They are also able to click on a link to open a separate window, the patient encounter view, which allows them to access more account information in a different format. This view allows them to see additional clinical or patient demographic detail, related charges and transactions, as well as past notes and activity on the account (see screen shot 2 available in uploaded file ) • Currently the patient encounter sheet is used to reference account information only. Users are not able to update any account information though this window, nor are they able to open up more than one account at a time. • We require a new feature, Patient Encounter View for Work Lists. • The goal is for end-users to be able to use the patient encounter view, as well as the original view, to “work” an account; they also should have the ability to work a list of multiple accounts through the patient encounter view should they so choose without having to close and open a new window Deliverables • Write and prioritize five user stories that would be required to build this feature • Include enough details in the acceptance criteria or user story details to show that you’ve thought about how the software should behave in the common use cases like supporting different work styles • Use diagrams or images to help convey your idea. • This needs to be completed by 11/01 at 9 am,EST, United States.