Professional Documents
Culture Documents
BA 186 Case Chapter 8
BA 186 Case Chapter 8
CASE 8:
USER
INTERFACE
DESIGN
Group 4 - Abesamis, Hernandez,
Salazar, Usman, Virtudazo
Review of Key Concepts
Background of the Case
Assignments:
Discussion Monthly Claim Insurance
Report
Outline Daily Appointment List and
Monthly Report
New Patient Data Entry
Screen
Validation Checks
Key Concepts
User Interface (UI)
Describes how users interact with a computer system and
consists of all features (hardware, software, screens, menus,
functions, output) that affect two-way communications
between the user and the computer/program.
The UI is the key to usability (user satisfaction, support for
business functions, and system effectiveness).
The best interfaces are the ones that users do not even notice —
they make sense because they do what users expect them to do.
Key Concepts
Graphical User Interface (GUI)
A GUI uses visual objects and techniques that allow users to
communicate effectively with the system.
Today, designers strive to translate user behavior, needs, and
desires into an interface that users don’t really notice. As IBM
points out, the best user interfaces are “almost transparent —
you can see right through the interface to your own work.”
Key Concepts
Seven Habits of Successful Interface Designers
1. Understand the business - when designing the UI, it’s important to
understand the underlying business functions and how the system
supports individual, departamental, and enterprise goals; the overall
objective is to design a UI that helps users perform their jobs.
NEXT STEPS:
Patient Insurance
Information Claim
Procedure Insurance
Company
Sub Total
Grand Total
Report Generation
Timestamp
#1: Report Analysis Form
Fields
Under Patient Information
Insurance Company Number - must be a
combination of one (1) capital letter and one
(1) number (For example: C1, C2, etc.)
Patient Code - must be a combination of one
(1) capital letter and 4 numbers within the
range of 0001 - 9999 (For example: P0001)
Patient Full Name - must be text without any
special characters except for ‘ñ’, '.' and ‘-’
#1: Report Analysis Form
Fields
Under Procedure
Date - must follow the format of mm/dd/yy
Code - must be a combination of three (3)
capital letters in any order (For example:
ABC, BAC, CAB, CBA, etc.)
Procedure Description - must be a short
description of the procedure (not exceeding
50 words)
Amount due - must only contain numerical
values and ‘.’
#1: Report Analysis Form
Fields
Under Insurance Claim
Date - must follow the format of mm/dd/yy
Amount of Claim - must only contain
numerical values and ‘.’
Amount Disbursed - must only contain
numerical values and ‘.’
Amount Remaining - must only contain
numerical values and ‘.’ and is automated
wherein its formula is (Amount Claim -
Amount Disbursed)
#1: Report Analysis Form
Frequency
Generated on a monthly basis, at the end of every month
Distribution
Report is distributed to administrative staff for analysis and other
relevant figures that requested for a report
#1: Report Analysis Form
Data Security Considerations
Educating Healthcare Staff
Restricting Access to Data and Applications
Implementing Data Usage Controls
Logging and Monitoring Use
Encrypting Data
Securing Mobile Devices
Mitigating Connected Device Risks
Conducting Regular Risk Assessments
Utilizing Off-Site Data Backup
Carefully Evaluating the Compliance of Associates
#2: Design the daily appointment list
TNEMTNIOPPA YLIAD
WEIV RADNELAC
#2: Design the daily appointment list
#2: Design a monthly report
#2: Mock-up Appointment List
#2: Report Analysis Form
Layout
Header/Title Weekly Calendar
Monthly
Calendar
Patient
Details
Notes
Distribution
Report is distributed to doctors and assistants to keep track of
patients visiting the clinic for smooth operations and organization
purposes.
#2: Report Analysis Form
Data Security Considerations (same with the previous report)
Educating Healthcare Staff
Restricting Access to Data and Applications
Implementing Data Usage Controls
Logging and Monitoring Use
Encrypting Data
Securing Mobile Devices
Mitigating Connected Device Risks
Conducting Regular Risk Assessments
Utilizing Off-Site Data Backup
Carefully Evaluating the Compliance of Associates
#2: Report Analysis Form
Layout Time period for
Header/Title generated report
Patient Insurance
Information Claim
Daily Monthly
Subtotal Grand Total
Report
Generation
Timestamp
#2: Report Analysis Form
Fields
Patient Full Name - must be text without any special characters except for‘ñ’, '.'
and ‘-’
Contact - must contain only eleven (11) numerical values (For example:
0987654321)
Email - must be a valid email address with '@' and '.'
#2: Report Analysis Form
Fields
Under Procedure
Attending Physician - must be text
without any special characters
except for ‘ñ’, '.' and ‘-’.
Fees - must only contain numerical
values and ‘.’
Payment Mode - must be a short
text without any special characters
except for ‘ñ’ and ‘-’.
#2: Report Analysis Form
Frequency
Generated on a monthly basis, at the end of every month
Distribution
Report is distributed to administrative staff for analysis and other
relevant figures that requested for a report
#2: Report Analysis Form
Data Security Considerations (same with the previous report)
Educating Healthcare Staff
Restricting Access to Data and Applications
Implementing Data Usage Controls
Logging and Monitoring Use
Encrypting Data
Securing Mobile Devices
Mitigating Connected Device Risks
Conducting Regular Risk Assessments
Utilizing Off-Site Data Backup
Carefully Evaluating the Compliance of Associates
#3: Design an input source
document for new patient data entry
https://tinyurl.com/NCHC
PatientQuestionnaire
The new patient questionnaire can now
be accessed with any devices, even with
the help of a QR Code.
#3: Design a data entry screen where to
input the information
NEW CENTURY HEALTH CLINIC
Patient Information Questionnaire
General Information
Last Name
(For example: dela Cruz)
First Name
(For example: Juan)
Middle Name
(For example: Garcia)
Present Address
(Lot No., Street, City, Province)
Contact Number
(For example: 0987654321)
Email Address
(For example: sample@gmail.com)
Work Address
(Street, Lot No., Province, City)
Contact Number
(For example: 0987654321)
Email Address
(For example: sample@gmail.com)
Height Weight
(for example: 5'7) (for example: 60kg)
Are you currently
YES NO
employed?
Occupation
(For example: student)
Add medication
1. Existence check
An existence check is used for checking mandatory data such as
Patient Name and Code. For example, if a new patient’s name is
entered by a user, his/her name must be given a corresponding
code to be registered in the system that is unique and unused yet.
Otherwise, the data will not be saved or recorded in the system.
#4: Memo on data validation checks
3. Range check
A range check verifies that data items fall between a specified
minimum and maximum value, also referred to as a specified
range of values. For example, patient codes have a range of
values from 0000 to 9999. If a user inputs 10000, it will be
considered as an error or invalid input, and release an
announcement that the data is beyond the maximum value. If not
remedied, it will not be recorded in the system.
#4: Memo on data validation checks
4. Reasonableness check
A reasonable check identifies values that are questionable but not
necessarily wrong. For example, if a user inputs 50 in the
Appointment Fee but historical data show that the minimum
value is at least 500. Hence, the system will initiate to verify
whether the data was entered incorrectly or not.
#4: Memo on data validation checks
5. Validity check
A validity check is used for data items that must have certain
values which are slightly similar to an existence check. For
example, if a patient’s name is entered, it must match other
corresponding information such as patient code, contact number,
email address, and other personal information to validate the
data entry. Otherwise, if there are any mismatches in the data, it
will fail the validity test. Hence, it will not be recorded. However,
in the instance that there are changes in a patient’s data such as
contact number, this can be remedied by updating the system to
prevent future issues in validity checks.
#4: Data validation checks
END OF MEMORANDUM
End of Presentation