Skip to main content
removed "too broad" part of the question
Source Link
Devin
  • 38.3k
  • 15
  • 81
  • 143

Suppose we are making a medical software to support doctors to perform medical examination on the patients and store results in the system.

What is unusual in this case, is that doctors often have several specialisation - e.g. one can do several types of examinations - e.g. cardiological and dermatological examinations. Each type of examination consist of tests, but not all of them are performed every time. Also doctor can later perform any test separately, and that test is not necessarily part of any type of examination. For example, at one appointment doctor can perform cardiological examination, dermatological examination and then dental test.

My current solution is to offer different workflows at the first screen and then later allow additional additional tests: enter image description here

What would be better ways to support those different workflows (dermatology, cardiology, etc.) and allow customization ?

And more general question, a bit out of scope: What are principles when designing for different groups of users / supporting several workflows?

Suppose we are making a medical software to support doctors to perform medical examination on the patients and store results in the system.

What is unusual in this case, is that doctors often have several specialisation - e.g. one can do several types of examinations - e.g. cardiological and dermatological examinations. Each type of examination consist of tests, but not all of them are performed every time. Also doctor can later perform any test separately, and that test is not necessarily part of any type of examination. For example, at one appointment doctor can perform cardiological examination, dermatological examination and then dental test.

My current solution is to offer different workflows at the first screen and then later allow additional additional tests: enter image description here

What would be better ways to support those different workflows (dermatology, cardiology, etc.) and allow customization ?

And more general question, a bit out of scope: What are principles when designing for different groups of users / supporting several workflows?

Suppose we are making a medical software to support doctors to perform medical examination on the patients and store results in the system.

What is unusual in this case, is that doctors often have several specialisation - e.g. one can do several types of examinations - e.g. cardiological and dermatological examinations. Each type of examination consist of tests, but not all of them are performed every time. Also doctor can later perform any test separately, and that test is not necessarily part of any type of examination. For example, at one appointment doctor can perform cardiological examination, dermatological examination and then dental test.

My current solution is to offer different workflows at the first screen and then later allow additional additional tests: enter image description here

What would be better ways to support those different workflows (dermatology, cardiology, etc.) and allow customization ?

Source Link

How to offer to users several workflows to complete a task

Suppose we are making a medical software to support doctors to perform medical examination on the patients and store results in the system.

What is unusual in this case, is that doctors often have several specialisation - e.g. one can do several types of examinations - e.g. cardiological and dermatological examinations. Each type of examination consist of tests, but not all of them are performed every time. Also doctor can later perform any test separately, and that test is not necessarily part of any type of examination. For example, at one appointment doctor can perform cardiological examination, dermatological examination and then dental test.

My current solution is to offer different workflows at the first screen and then later allow additional additional tests: enter image description here

What would be better ways to support those different workflows (dermatology, cardiology, etc.) and allow customization ?

And more general question, a bit out of scope: What are principles when designing for different groups of users / supporting several workflows?