Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

General Info

Lead UI/UX Coordinator: Susan Wolfe

A few UI/UX housekeeping issues... - a blog post by Susan (Feb 26th, 2012)

 

JSS EMR UI INTRO

Welcome to the Raxa JSS EMR project!  Thank you for taking the time to help on this very important endeavor.  It is a bleeding-edge project from a UI/UX standpoint.  We have an opportunity to really do some good in the world with JSS and I'm very excited about being able to contribute to such a great cause.  If you have taken the time to look at the user stories in DropBox you will see we have some very interesting workflows and a wonderful opportunity to solve some very cool UI and UX puzzles.  Our plan is to approach all the UI's from a "mobile-first" perspective, even if certain modules may be keyboard and mouse presently.  

The user roles for the software are as follows:

1) Registrar

2) Nurse

3) Doctor

4) Lab Technician

5) Lab Manager

6) Pharmacist

7) Billing

Of the above roles the nurse and doctor roles are the most complex.  Both nurses and doctors will require access to all the modules from registration all the way to billing.  Hence the IA an UI/UX for these roles will be the most challenging.  The remaining roles need more granular access to the modules specific only to their roles, for example the registrar will only require access to the registration module.  

From a high level the modules we will need to design: 

1) Registration

2) Screening

3) Outpatient

4) Lab

5) Pharmacy

6) Billing

*Emergency (as of now undefined ... possible future work ) 

Also please let me know where your interests are, and what modules and roles you'r interested in working on.  We will try and accommodate everyone.  Obviously there is a lot of work here and plenty of opportunity for everyone to contribute.  We will be using the UI wiki to communicate.  We will then create Jira issues from which developers will begin coding.  If any of you have not used JIRA before please let me know and I'll help where I can ( its a ticketing and bug tracking system ).  

Other Resources

Information Architecture document: 

 



  • No labels