Correct sequence of steps for a multi-step workflow

by art_cart_dart_eart   Last Updated December 05, 2018 21:16 PM

I'm working on a project where a logged-in user(nurse) has to complete a multistep workflow in order to enroll patients into their doctor's records system.

The workflow needs to capture: Patient Name/Contact Info, Doctor/clinic information (neither can be assumed), Prescription information, and some test results/general medical questions.

Important info: This process is meant to replace a paper form that currently exists - so some users may be used to filling in this information with pen and paper.

I've heard the thinking that it's important to engage users, which would lead me to choose the medical information or the Prescription information as the first steps rather than the data entry that is patient contact info and doctor information but I'm hoping there are opinions or thinking to support or refute that approach.

Answers 1

I have written quite a few databases, including a medical records system (in pre-web days).

Always start with "demographics" - name, email (if this is a publicly accessible online system then you will already have that from registering an account anyway), address, phone #s, etc. You need this information to do "anything" and it has the advantage that nothing "special" is needed.

Next should be any non-medical information: Insurance, doctor/clinic, etc.

Last should be the actual medical information - tests, prescriptions, diagnoses, etc.

This works from easiest to hardest. Get the users to enter the easy stuff and then they will be more inclined to do the extra work to gather the harder/more complicated/confidential information because they will feel more vested in the system. They may legitimately need to come back later with the more complicated information, so at least you can get the easy stuff right away.

December 05, 2018 20:44 PM

Related Questions

Should you autosave when app is minimized?

Updated August 08, 2016 08:06 AM

Which method to create a data map?

Updated June 22, 2016 08:06 AM

Flexible natural language input field design

Updated June 23, 2015 00:07 AM