First Principles of SaaS UX · CHAPTER 2 OF 7

Data, entities, and dependencies

Data In Enterprise Software

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Users

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Roles

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Departments

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Workflows

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows
One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows
One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

One User’s Data Drives the Next User’s Action

One person’s action can create the data another person needs to continue their work. This is where data dependency comes into play.

In enterprise software, data moves between:

One User’s Data Drives the Next User’s Action

One person’s action can create the data another person needs to continue their work. This is where data dependency comes into play.

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Users

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Roles

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Departments

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

Workflows

One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows
One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows
One User’s Data Drives the Next User’s Action: Users Roles Departments Workflows

In enterprise software, data moves between:

Example

Hospital Management

Example

Hospital Management

Look at Hospital Management Software: Multiple Roles Departments Pharmacy, Hospitals Dependencies

Multiple Roles

Departments

Pharmacy, Hospitals

Dependencies

Look at Hospital Management Software

A hospital works well as an example because it contains multiple roles, departments, objects, and dependencies. Yet the same first principle still applies: Every workflow is built around data and actions taken on that data.

Look at Hospital Management Software

A hospital works well as an example because it contains multiple roles, departments, objects, and dependencies. Yet the same first principle still applies: Every workflow is built around data and actions taken on that data.

Look at Hospital Management Software: Multiple Roles Departments Pharmacy, Hospitals Dependencies

Multiple Roles

Departments

Pharmacy, Hospitals

Dependencies

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Hospital

Patient

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Receptionist

Doctor

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Nurse

Pharmacist

Pharmacy

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Medicine

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Software Contains Many Data Entities

Each Entity Has Different Data. Each has its own attributes and serves a different purpose in the workflow.

Software Contains Many Data Entities

Each Entity Has Different Data. Each has its own attributes and serves a different purpose in the workflow.

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Hospital

Patient

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Receptionist

Doctor

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Nurse

Pharmacist

Pharmacy

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Medicine

Software Contains Many Data Entities: Hospital Patient Receptionist Doctor Nurse Pharmacist Pharmacy Medicine

Data Is Not Limited to People

A hospital, pharmacy, or medicine also contains information that users rely on to complete actions.

​

For example,
A pharmacy may have a location, license number, and registration details, while a medicine may have dosage, batch number, expiry date, price, and stock.

Data Is Not Limited to People: Hospital Pharmacy Medicine DATA

Hospital

Pharmacy

Data Is Not Limited to People: Hospital Pharmacy Medicine DATA

Medicine

Data Is Not Limited to People: Hospital Pharmacy Medicine DATA

DATA

Data Is Not Limited to People

A hospital, pharmacy, or medicine also contains information that users rely on to complete actions.

For example, A pharmacy may have a location, license number, and registration details, while a medicine may have dosage, batch number, expiry date, price, and stock.

Data Is Not Limited to People: Hospital Pharmacy Medicine DATA

Hospital

Pharmacy

Data Is Not Limited to People: Hospital Pharmacy Medicine DATA

Medicine

DATA

Every Entity Has Its Own Data.

A patient contains attributes such as:

Name, Patient ID, Age, Gender, Phone Number, Email

​

Together, these attributes create the patient's data record.

Every Entity Has Its Own Data.: First Name Last Name Patient Id Age Gender Phone number Email Address Prescription Details
Every Entity Has Its Own Data.: First Name Last Name Patient Id Age Gender Phone number Email Address Prescription Details

First Name

Last Name

Patient Id

Age

Gender

Phone number

Email

Address

Prescription Details

Every Entity Has Its Own Data.: First Name Last Name Patient Id Age Gender Phone number Email Address Prescription Details

Every Entity Has Its Own Data.

A patient contains attributes such as:

Name, Patient ID, Age, Gender, Phone Number, Email

Together, these attributes create the patient's data record.

Every Entity Has Its Own Data.: First Name Last Name Patient Id Age Gender Phone number Email Address Prescription Details
Every Entity Has Its Own Data.: First Name Last Name Patient Id Age Gender Phone number Email Address Prescription Details

First Name

Last Name

Patient Id

Age

Gender

Phone number

Email

Address

Prescription Details

Every Entity Has Its Own Data.: First Name Last Name Patient Id Age Gender Phone number Email Address Prescription Details

How Data Builds Across the Workflow

A patient enters the hospital. The receptionist records basic details, then the nurse adds vitals, and the doctor uses this data to assess the patient and add a diagnosis or prescription.

How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient

A patient enters the hospital

The receptionist records basic details

The nurse adds
vitals

The doctor uses this data to assess the patient

How Data Builds Across the Workflow

A patient enters the hospital. The receptionist records basic details, then the nurse adds vitals, and the doctor uses this data to assess the patient and add a diagnosis or prescription.

How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient
How Data Builds Across the Workflow: A patient enters the hospital The receptionist records basic details The nurse adds vitals The doctor uses this data to assess the patient

A patient enters the hospital

The receptionist records basic details

The nurse adds
vitals

The doctor uses this data to assess the patient

This Is Data Dependency

One user's output becomes another user's input. This is a fundamental characteristic of enterprise software.

Receptionist

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Adds Data

Nurse

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Adds Data

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Doctor

Adds Data

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Pharmacist

This Is Data Dependency

One user's output becomes another user's input. This is a fundamental characteristic of enterprise software.

Receptionist

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Adds Data

Nurse

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Adds Data

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Doctor

Adds Data

This Is Data Dependency: Receptionist Adds Data Nurse Adds Data Doctor Adds Data Pharmacist

Pharmacist

Data Priority Changes By UserRole

Data Importance Depends on the User

​

  • For a patient, their prescription may be extremely important.

​

  • For a doctor, that prescription is only one part of their daily work. They may care more about: Today's patients, Upcoming consultations, Pending cases, Time

Doctor

Daily tasks

  1. Upcoming consultations
  2. Checking Patients
  3. Today’s patient list
  4. pending cases
  5. patient perscription
Data Priority Changes By UserRole: Doctor Daily tasks Patient Apedermin dexolite minoxidil one mg Apedermin dexolite ck urite mioxidil tablets Apedermin dexolite Apedermin dexolite Doctor prescrition Name: Age Gender

Patient

Apedermin dexolite

minoxidil one mg

Apedermin dexolite ck urite

mioxidil tablets

Apedermin dexolite

Apedermin dexolite

Doctor prescrition

Name:

Age

Gender

Data Priority Changes By UserRole: Doctor Daily tasks Patient Apedermin dexolite minoxidil one mg Apedermin dexolite ck urite mioxidil tablets Apedermin dexolite Apedermin dexolite Doctor prescrition Name: Age Gender

Data Priority Changes By UserRole

Data Importance Depends on the User

  • For a patient, their prescription may be extremely important.
  • For a doctor, that prescription is only one part of their daily work. They may care more about: Today's patients, Upcoming consultations, Pending cases, Time

Doctor

Daily tasks

  1. Upcoming consultations
  2. Checking Patients
  3. Today’s patient list
  4. pending cases
  5. patient perscription
Data Priority Changes By UserRole: Doctor Daily tasks Patient Apedermin dexolite minoxidil one mg Apedermin dexolite ck urite mioxidil tablets Apedermin dexolite Apedermin dexolite Doctor prescrition Name: Age Gender

Patient

Apedermin dexolite

minoxidil one mg

Apedermin dexolite ck urite

mioxidil tablets

Apedermin dexolite

Apedermin dexolite

Doctor prescrition

Name:

Age

Gender

Data Priority Changes By UserRole: Doctor Daily tasks Patient Apedermin dexolite minoxidil one mg Apedermin dexolite ck urite mioxidil tablets Apedermin dexolite Apedermin dexolite Doctor prescrition Name: Age Gender

Why This Matters for UX

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What appears on the screen

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What gets priority

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What actions are available

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

How navigation should be structured

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What information connects across workflows

Understanding Each Role’s Data Helps Decide:

Without this understanding each user role’s data, the UI may look good but fail the actual workflow.

Why This Matters for UX

Without this understanding each user role’s data, the UI may look good but fail the actual workflow.

Understanding Each Role’s Data Helps Decide:

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What appears on the screen

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What gets priority

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What actions are available

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

How navigation should be structured

Why This Matters for UX: What appears on the screen What gets priority What actions are available How navigation should be structured What information connects across workflows

What information connects across workflows

FRAMEWORK CONTENTS

First Principles of SaaS UX

Search documentation

Search scope

Search across all eight guides.

Diagram detail