Systems Analysis

Modules 1-7
CIS280

This work is licensed under a Creative Commons Attribution 4.0 International License.
Exceptions: 1) Materials identified as copyrighted or derived from another source. 2) Materials extracted from the
Office of the National Coordinator (ONC) Health Information Technology Workforce Curriculum, which carries a
more limited CC BY-NC-SA license.
 Course Summary
• Introduction to Systematic Approach to:
– Define Needs
– Create Specifications
– Design Information Systems
• Hands-on Case Studies
• Systems Analysis & Design Techniques
• Project Management

2
 Course Learning Objectives
• Analyze/design using SDLC Waterfall and Agile
Methodologies
• Project Management software for tracking and
reporting tasks, costs, resources and timelines
• Analyze acquisition, implementation, testing,
maintenance, risk management, and best practices

3
 Course Learning Objectives
(continued)
• ID and analyze SDLC project professionalism and
ethics
• ID system risk/issues and mitigation
• Analyze and discuss governance, security, and
privacy
• Differentiate various IT, PM, and management roles
in system development

4
 Course Learning Objectives
(continued)
• Analyze business environment and how IT supports
the organization achieve business objectives
• ID and analyze standard and best practices for IT
governance and management
• ID and analyze industry relevant IT career paths,
certifications, currency

5
 Course Topics
• Systems Development Life Cycle (SDLC)
• Agile and other development methodologies
• Project Management
• Professionalism and Ethics
• Security & Privacy standards and regulations
• Information Technology management
• Information Technology Standards and best
practices
• Computer Careers and Certifications

6
 Course References
• CAHIMS 3.5 – Project Management
• CAHIMS 4.2 – Systems Acquisition
• CAHIMS 4.3 – Interoperability Standards & Certification
• CAHIMS 5.1 – Systems Implementation
• CAHIMS 5.3 – Systems Monitoring and Maintenance
• CAHIMS 7.2 – Security Risk Assessment & Audit
• CAHIMS 8.2 – Quality Standards
• CAHIMS 8.3 – Strategic Planning
• Systems Analysis and Design, 3rd Ed, Kendall & Kendall, Prentice Hall,
New Jersey, 1995
• Systems Analysis and Design, 6th Ed, Shelly, Cashman, Rosenblatt, Course
Technology, Massachusetts, 2006

7
 Module 1

Systems Development Life Cycle

8
 Failure of IT Projects
Gartner 2012 Survey reports that:
– “Runaway budget costs are behind one-quarter of
project failures for projects with budgets greater
than $350,000.
– Small is beautiful — or at least small projects are
easier to manage and execute. The failure rate of
large IT projects with budgets exceeding $1 million
was found to be almost 50% higher than for
projects with budgets below $350,000.”
http://thisiswhatgoodlookslike.com/2012/06/10/gartner-survey-shows-why-projects-fail/, 02/12/14

9
 IT Projects
Every year, Gartner performs a global analysis of
IT spending trends. Key findings from this year's
Gartner IT Key Metrics report are:
– 56% of global IT budgets are spent on
infrastructure and operations
– 34% of global IT budgets are spent on applications
– 10% of global IT budgets are spent on IT overhead
http://www.gartner.com/technology/metrics/, 02/12/14

10
 Sound Health, LLC
• Local health care cooperative
• General out-patient care
• Limited specialty care
• Health care providers have working
relationships with local hospitals
• Need to update their I-T support

11
 Information

A Critical
Organizational
Resource

12
Organizations
as
Systems

13
Characteristics of
Organizations

• Structure
• Goals/Objectives
• Functions
• Sub-Systems
• Communication

14
Five Functions of Management

Planning
Directing Staffing

Controlling Organizing

15
 Management Hierarchy

• Strategic
Information
• Middle Systems
Needs
• Operational

16
Management Information
Systems

17
 Systems Development Life Cycle

• Identifying problems, opportunities, and

objectives
• Determining information requirements
• Analyzing system needs
• Designing the recommended system
• Developing and documenting software
• Testing and maintaining the system
• Implementing and evaluating the system

18
 System Life Cycle
• Phase I – Preliminary Investigation
• Phase II – Systems Analysis
• Phase III – Systems Design
• Phase IV – Systems Implementation
• Phase V – System Operation and Support

19
 System Lifecycle
A Continuous Process
“Next”
System
Implementation
Design
Investigation

Operation “Current”
System Analysis
Operation
Implementation Design
Analysis

Investigation

20
 References
• SAD – Complete Introductory Tutorial for S/W Engineering
http://www.freetutes.com/systemanalysis/
• Systems Analysis and Design slide show – brief
http://www.slideshare.net/aamir_libr/system-analysis-and-design-
14843784
• Systems Analysis and Design/Introduction
http://en.wikibooks.org/wiki/Systems_Analysis_and_Design/Introduction

21
 The Systems Analyst

• Investigates, analyzes, designs, develops, installs,

evaluates, maintains
• Technical and communication skills essential
• Primary roles: consultant, supporting expert,
change agent

22
 BABOK® Guide - Workplace
Competencies

• Analytical Thinking and Problem Solving

• Behavioral Characteristics
• Business Knowledge
• Communication Skills
• Interaction Skills
• Software Applications

23
Sampling and Investigating
Hard Data

24
 Sampling

• What is it?
• Why do we need it?
• How do we design it?
• How much do we sample?

25
What Kind of Information?

• Quantitative
• Qualitative

26
 Marketing 101
Perceptions are Reality

Your biases, education, intellect, upbringing,

ethnicity, beliefs, emotions . . . filter your
perceptions - everything you hear and see . . .
and how you interact with people, including
interviews.

27
 Sound Health, LLC
• 13 Physicians
• 2 Physician’s Assistants (PAs)
• 2 Nurse Practitioners (NPs)
• 5 Registered Nurses (RNs)
• 6 Licensed Practical Nurses (LPNs)
• 14 Support staff
• 2 I-T staff

28
What is the purpose
of an interview?

29
Gather Information

Goals
Feelings
Informal
Opinions Procedures

30
Interview Planning

• Background material
• Objectives
• Who to interview
• Prepare the interviewee
• Questions

31
Conducting the
Interview

32
Alternatives
to
One-on-One
Interviews

33
 Questionnaires:
Interview Alternative

34
 Gather Information

Beliefs Behaviors

Attitude Characteristics

Questions:
- Closed
- Open-Ended

35
 Effective Questionnaires

• What is the purpose? • Scaling

• Conditions for Use? « Nominal
« Ordinal
• Questions « Interval
« Remember, no interaction « Ratio
« Choose words carefully
« Validity and reliability
• White Space

36
 Analyst Observations:
Elementary, My Dear Watson, Elementary

37
 Why Observe?

Relationships
Messages
Activities
Gain Insight
Influence
Confirm, Negate, Reverse
Structured & Systematic

38
 How to Observe

• Structured and systematic

• What will be observed
• Determine level of correctness
• Categorize key actions
• Collection materials - forms, scales, etc
• When
• Time and event samples

39
 What to Observe

• Decision-maker Activities
• Body Language
• Physical Environment

40
 Module 2

Development Methodologies
CAHIMS 4.2

41
Traditional Systems Analysis & Design
The “Waterfall” Approach
Phase 1 - Preliminary Investigation

Phase 2 - Systems Analysis

Process
Could Take Phase 3 - Systems Design
Years to
Complete
Phase 4 - Acquisition &
Implementation

Phase 5 - Maintenance

42
http://www.docstoc.com/docs/41002042/Traditional-systems-development-phases-The-Waterfall-Method

43
 SDLC Alternatives

• Prototyping
• Incremental Development
– Agile
– Scrum

44
http://www.sdlc.ws/agile-vs-waterfall/

45
 Draw a Picture

Dataflow Diagrams Entity-Relationships

Preferences and Emplooyee Primary Travel
Available Flights Travel Destination
Passenger Agent Entity

1 1

0
Travel Ticketing Assigned to Can be
Request Airline Information Relationships Booked by
Reservation
System

Data
Passenger Process
Entities Flow Reservation 1 M

Secondary
Phone Passenger
Extensiion Entity

Airline

46
 References
• UMSL – Traditional Waterfall Approach
http://www.umsl.edu/~hugheyd/is6840/waterfall.html
• Select Business Solutions – What is the Waterfall Model?
http://www.selectbs.com/analysis-and-design/what-is-the-waterfall-
model
• Systems Design – Waterfall Model
http://en.wikipedia.org/wiki/Waterfall_model
• UMSL-Comparing Traditional SAD with Agile Methodologies
http://www.umsl.edu/~hugheyd/is6840/introduction.html
• Interesting Systems Analysis Web Sites
http://www.umsl.edu/~sauterv/analysis/analysis_links.html

47
Prototyping

48
 Approaches

• May be controversial
• No one correct definition/approach
• General approaches
– Patched-up
– Nonoperational
– First-of-a-series
– Selected features

49
 When to Prototype
• Straightforward,
structured,
predictable problem
• Novel, complex,
unstructured,
uncertain

50
 If You Prototype

• Manageable modules
• Build rapidly
• Iterative/Incremental development
• User interface

51
 Prototyping Information

• User Reactions
• User Suggestions
• Innovations
• Revision Plans

52
 Users’ Role:
Honest Involvement

• Interaction with analyst and prototype

• Expermentation
• Open reactions
• Suggest changes/modifications

53
 Pros and Cons
• Potential for early • Management of a
change - flexibility prototype within a
• Stop development if project
approach unworkable • Users may adopt as a
• Users’ needs and completed system
expectations

54
 Agile
• Alternative to traditional methods
• Dr. Winston Royce, 1970
• Incremental, iterative work cadences, sprints
• Scrum most popular method

55
http://computertrainingcenters.com/agile-development-meets-customer-needs/

56
http://upload.wikimedia.org/wikipedia/commons/6/6c/Agile_Software_Development_methodology.jpg

57
http://boxesandarrows.com/bringing-user-centered-design-to-the-agile-environment/

58
 References
• Agile Developments Influence on Systems Analysis
http://www.umsl.edu/~takz7c/default.htm
• Agile Methodology and Systems Analysis
http://www.umsl.edu/~sauterv/analysis/f06Papers/Iyer/
• Agiule Methodology
http://agilemethodology.org/

59
 Scrum
• Simplicity and flexibility
• Empirical feedback
• Team self-management
• 3 Scrum roles
• Scrum Meetings

60
http://www.inqbation.com/agile-methodology-of-web-development/

61
62
http://www.wilsisney.com/archive/2012/03/scrum/

63
 References
• UMSL-Scrum
http://www.umsl.edu/~hugheyd/is6840/scrum.html
• Scrum Overview
http://www.mountaingoatsoftware.com/scrum/overview
• What is Scrum Methodology?
http://www.mountaingoatsoftware.com/topics/scrum
• Scrum in Under 10 Minutes (video)
http://www.ontimenow.com/scrum/learn-
scrum?gclid=CJj52oyRxrkCFWQ6QgodKR4A_A
• A Reusable Scrum Presentation
http://www.mountaingoatsoftware.com/scrum/a-reusable-scrum-
presentation

64
Modeling the System

A Picture’s Worth 1,000 Words

65
 Data Flow Diagrams
• Picture of system centered on business activities
• Based on business events not a particular
technology, therefore more stable
• Communication with users
• Analysts’ business understanding
• Present and proposed system
• Basis for physical DFD

66
 DFD vs Narrative Descriptions
Advantages

• Prevents premature technical system

implementation
• Enhances system/subsystem interrelatedness
understanding
• Communicates analysts’ system understanding
to users
• Analysis of proposed system - necessary
data/processes defined

67
Symbology and Conventions

Entity Flow of Data Process Data Store

(Noun) (Noun) (Name of Whole System (Noun)
Name of Subsystem
Verb-Adjective-Noun)

68
 General to Specific
Exploding Diagrams

• Context Level (Environmental)

• Diagram 0
• Child Diagrams (Parent Process
Exploded)

69
 Context Level DFD
(Environmental Model)
• Entities - Process - Data Flow
• How do you buy a tent from REI?
Item Availability
Sales
Assoc.
0
Item Request Sales Info
Customer Sales
System
Customer
Order

Supplier

70
 Diagram 0
Context Level

External
Entity Input A
0 External
1 Output C Entity
System 3
Input B Name

External
Entity
2

1 2
External Input A Data Flow B Output C
Entity General General External
1 Process Process Entity
AAA BBB 3
Data Flow C
Diagram 0

Record A
Record E

D1 Data Store 1 D2 Data Store 2

Record A
Record E

3 4
External Input B General Data Flow D General
Entity Process Process
2 CCC DDD

71
Sound Health Context Level DFD
Ins
Companies Pharmacies

Pmt
Report Invoices Rpts
Correction
Prescription Order
0
Appointment
SH
Patients
Patient MIS Appt Rqst
Records Patient
Co-Payments
Reports
Bank Deposit
Bank
Hospitals Statements

Bank

72
 DFD Errors

• Data Flows - Omitted/Wrong Direction

• Data Flows and External Entities Connected
• Incorrect Labels - Processes/Data Flows
• Too Many Processes - Limit 9
• Unbalanced Decomposition - Child Diagrams

73
 References
• What are DFDs?
http://www.smartdraw.com/resources/tutorials/data-flow-diagrams/
• DFD Tutorial
http://www.visual-paradigm.com/product/lz/tutorials/dfd.jsp
• DFD for Dummies – Slideshare
http://www.slideshare.net/Cazoomi/data-flow-diagrams-for-dummies

74
 Entity-Relationship Diagrams

• Review from CIS260 “Database Management

Systems”
• Graphic depiction of system components
• Provides means for clarity

75
 The Entity Relationship(ER)
Model
• The ER model shows information to be collected in
the database (entity) and its relationship with other
information collected.

• Peter Chen, 1976, originator of the entity

relationship model
 Identify the “Entities”
Identify the “entities” – the nouns – the title of the information being collected
(patient, appointment, prescription, physician, etc.).

1. Draw a box for each entity and label with the entity name.
2. Label using the singular spelling of the noun and capitalize the noun.*

Figure 1: The design of the "box" will depend on

the software used to create it.
 Identify the “Relationships”
Identify the “relationships” – the verbs; how one piece of data or
information interacts/relates with another piece of information Draw a line
between entities to show relationship.
1.Label the line with verbs that describe the relationship.
2.The first verb is for reading left to right; the second verb is for
reading right to left.

Figure 2:
The Patient has an Appointment. The
Appointment is for a Patient.
 Identify the “Cardinality”
Identify the “cardinality” – the number of entities allowed in the
relationship.

1.A single line touching an entity means “ONE”.

2.A line ending with three small lines, referred to as “crow’s feet”,
means “Zero or more”. Once created, this can be set to a different
minimum such as “One or more” or “Three or more”.

Figure 3: Single point at line end means "ONE";

crow’s feet, means "many" or "one or more".
 Identify the “Optional/Optionality”
Identify “optional/optionality” – whether the relationship is required or
not.
1. Microsoft VISIO uses the “O” to show “optional” as seen by
the entity Appointment.
2. The “||” means one required.

Figure 4: The Patient may have "one or more“

Appointments; the Appointment must have one Patient.
 Add the “Attributes”
Add the “attributes” – descriptors of the entity.
1. Label the attributes as singular tense.
2. Don’t put spaces or symbols between words if more than one is
needed for clarity.
3. Type or write as “camel case” – first letter of each word is upper
case, all other letters are lower case.

Figure 5: We identify the Patient by his/her name;

we identify the Appointment by the date, time and Physician .
 Add “Primary Key (PK)” and “Foreign
Key (FK)”
Add “primary key (PK)” – use an attribute of the entity, or create a new
attribute, that uniquely identifies the entity.
1. A new attribute, primary key ID, is usually created for most entities
because none of the attributes identified are guaranteed to always be
“unique”.
2. Add “foreign key(FK)” –this is the Primary key of the parent table in a
relationship. The PK of the parent (in this case “Patient”) is added to
the child table (in this case “Appointment”) thereby becoming the FK.

Figure 6:
 Unique Identifiers (UID)
• A unique identifier/unique ID/UID is a number or
combination of numbers and letters that when used will
only identify one entity or record.
• Examples of ID’s we think uniquely identify us:
– Driver’s license
– Social Security Number
– Telephone number
• Why they might not be unique:
– http://www.idanalytics.com/news-and-events/news-
releases/2010/8-11-2010.php
• CustomerID, or PatientID, or AccountNumber are examples
of new identifiers created for the purpose of keeping the
information unique.
 Read the Data Models
Practice reading the diagrams.
1. Keep nouns singular when starting each sentence.
2. Read from left to right, then from right to left. The
sentences must make sense in both directions.

Noun A may/must have relationship(s) with some of Noun B.

number

** Bike must be sold with one or more Wheel(s)

*** A Wheel May Be sold with A Bike

Bike Wheel

is sold with / is part of

 References
• What are Entity Relationship Diagrams?
http://www.smartdraw.com/resources/tutorials/entity-relationship-
diagrams/
• Entity Relationship Diagrams – University of Missouri-St Louis
http://www.umsl.edu/~sauterv/analysis/er/er_intro.html
• Entity Relationship Modeler
http://www.aquafold.com/aquadatastudio/er_modeler.html?gclid=CODbp
4C2w7kCFQnhQgoduRcAQw

85
Creating Mr. Webster
a Dictionary for your Data

86
 The Data Dictionary
• Component of the Data Repository
• Reference work of data about data
• Compiled by Systems Analysts - Special Forms
• Consistent standard for for data elements
• Collects, coordinates, and confirms what a specific data term
means to different people in an organization
• Used to validate DFD accuracy and completeness
• Provides starting point for screen/report development
• Determine contents of data stored in files
• Develop logic for DFD processes
• 4 categories: flows, structures, elements, stores

87
 Defining and Describing Data
• Data flow definition: ID #, name, gen
description, source, destination, etc.
• Data structures: algebraic notation - “=”, “+”,
“{ }”, “[ ]”, “( )”
• Data elements
• Data stores: base and derived

88
 Special Forms
• Data Flow Description • Element Description
– ID – ID
– Name – Name
– Description – Aliases
– Source/destination – Description
– Type of data flow – Characteristics
– Volume/time – Validation Criteria

89
Transforming Processes
Documenting and Analyzing Decisions and Logic
Requires Good Analysis

90
 Why Develop Process Specs?
• Reduce ambiguity
• Precise description of what is to be
accomplished
• Validate system design

Note: Some processes do not require specs

91
Documenting Process
Specifications

What to capture?

92
Structured Decisions

• How do you make them?

• What do you need?
• how do you document?

93
How To Portray Processes
3 Techniques

• Structured English
• Decision Tables
• Decision Trees

94
 Process Specs
• Process Description documents details of
functional primitive
• Modular Design
– Sequence
– Selection
– Iteration

95
 Process Specs
• Structured English
– Like Pseudocode
– Use Keywords
• Decision Table
– 4 Quadrants – Conditions, Alternatives, Actions,
Rules
• Decision Tree – Graphic Decision Table

96
 Structured English
• Process involves formulas or iteration
• Use to clearly describe logical processes
• Sequence, selection, iteration
• Limit vocabulary, standard terms
• Indent for readability

97
 New Patient Billing
• When calculating billing for medical services, if a new patient, ask if
they have insurance. If married, ask if their spouse has separate
insurance. If there are two insurance policies check for birthdates of
patient and spouse to determine which policy is primary and which is
secondary. Check to determine if one or the other policy has
stipulations preventing being secondary payer. If both insurance
companies can be billed in this situation with one as primary and the
other as secondary, calculate patient co-pay/deductible (if any) for
services and invoice insurance companies.
• If the patient is not married or only one insurance policy is available,
calculate co-pay/deductible (if any) for services and invoice insurance
company. If patient does not have insurance, then invoice patient for
services.

98
 New Patient Billing Process
If patient has insurance
Then If patient has spouse with separate insurance
Then If separate policies allow primary/secondary status based on birthdates
Then Calculate co-pay/deductible for patient and invoice both insurance companies
Else calculate co-pay/deductible for patient based on primary insurance company
End If
Else Calculate co-pay/deductible for patient and invoice insurance company
End If
Else invoice patient for services
End IF

99
 Decision Tables
• Multiple conditions
• Multiple actions
• Depicts all possible combinations
• Provides means to simplify logic

100
 Decision Table Rules
• Determine Number of Conditions
• Determine Number of Possible Actions
• Determine Number of Condition Alternatives
• Calculate the Max Columns
• Fill in Condition Alternatives
• Complete Table with “X’s” in Rules as Appropriate
• Combine Rules
• Check for Impossible and Redundant
• Rearrange Conditions and Actions for Readability

101
 Decision Table
Construct a decision table to determine the logic for
automating awarding bonus airline frequent flyer miles
using the following criteria. Reservation must be made
online and either the ticket paid using the airline
branded credit card or departure and return flights do
not span a weekend (i.e. travel is sometime from
Monday through Friday).

102
 Decision Table
Conditions Condition Alternatives
1 2 3 4 5 6 7 8
1. Reservation Made Online Y Y Y Y N N N N
2. Airline Branded Credit Card Y Y N N Y Y N N
3. Monday – Friday Travel Y N Y N Y N Y N
Actions Action Entries (Rules)
1. Award Bonus Miles X X X
2. Do Not Award Bonus Miles X X X X X

103
 Decision Tree
• Graphic depiction of a decision table
• Linear progression of conditions
• Branches indicate true/false; yes/no
• Use the Decision Table information and create
a Decision Tree

104
 Decision Trees

Bonus Miles
Yes
Airline CC
Yes Bonus Miles
Reservation Online Yes
No M-F Travel

No No Bonus Miles No Bonus Miles

No

Think of a circle signifying IF while the square means THEN.

105
Decisions, Decisions

Supporting the Decisionmaker

The Role of the DSS

106
 When to Use . . .
• Structured English
– Many Repetitious Actions, or
– Communications to End Users Important
• Decision Tables
– Complex Combinations of Conditions, Actions, and
Rules
– Effectively Avoids Impossible Situations, Redundancies,
and Contradictions
• Decision Trees
– Sequence of Conditions and Actions Critical
– Not Every Condition is Relevant to Every Action

107
 Decisions
• Style - Analytic or Heuristic

• Phases - Intelligence, Design, Choice

• Involves risk and uncertainty

108
 Decision Support Systems
• Organize information
• Interaction with decisionmaker
• Add structure
• Uses decision-making database
• Does not replace decisionmaker
• Does not make decision
• Supports routine or one-time decisions

109
 Creating the DSS

• DSS generator (DSSG) s/w pkg

• Build from scratch

110
 Making Decisions

Uncertainty Certainty

Risk
Somewhat Knowledgeable:
- About alternatives (controllable variables)
- What we cannot control, must estimate (environmental variables)
- What the outcomes will be (dependent variables)

Certainty Increases with Information and Experience

111
 Decisions

Structured Unstructured

“Totally Programmed” Intuition

- Structured English and
- Decision Tables Judgment
- Decision Trees

Semi-structured

112
Preparing the Systems
Proposal

113
Analysts’ Synthesis of Information

• Systematically project future needs

• Weigh hardware and software

alternatives

114
Hardware and Software Needs

• Accurate inventory
• Workload
• New equipment
• Vendor support
• Software evaluation

115
 Cost/Benefit Analysis
• “What If?”
• Trend analysis
– Graphics
– Moving averages
• Tangible/intangible benefits
• Break-even analysis
• Payback
• Cash-flow analysis

116
Writing and Presenting the
Systems Proposal

117
 The Systems Proposal
• Cover letter • Systems study details
• Title page • Alternatives
• Contents • Recommendations
• Executive summary • Summary
• Systems study outline • Appendicies

118
 Writing Style

• Understandable but not

condescending
• Organizational preference
• Active vs. passive voice
• That, which, and there
• Make the bottom line the top line

119
 Tables and Graphs

• Tables - one per page, clearly titled,

labeled, and outlined

• Graphs - appropriate to data, e.g. pie chart

to show % of whole

120
Presenting the Proposal

• Objective: info or decision

• Key points and issues
• Attention grabber
• Visual aids
• Paper charts, overheads,
35mm, computer driven
• It’s the delivery

121
Designing Effective Output

122
Design Objectives

• Forms of output
• 6 objectives for output
– Designed to serve a purpose
– Fit the user
– Appropriate quantity
– Assure output where needed
– Timely
– Correct output method
– Keep it simple (KISS)

123
Designing Effective Input

Paper Forms and Video Screens

124
 Form Design:
Flow and Structure

• Heading
• Captioning
• ID and Access • Check-Off
• Instructions
• Body
• Signature and Verification
• Totals
• Comments

125
Input Forms/Screens Should Be:

• Effective
• Accurate
• Easy to use
• Consistent
• Simple
• Attractive

126
The User Interface

127
 Interface Objectives

• Effectiveness
– Appropriate Access
• Efficiency
– Increased Speed w/Reduced Errors
• User Consideration
– Feedback
• Productivity
– Ergonomic Design

128
 Types of Interfaces

• Two Components
– Presentation Language -- Computer-to-Human
– Action Language -- Human-to-Computer
• Natural Languages
• Q&A
• Menus
• Command Language
• GUI

129
 Interface Examples

Organization Information Support System

Select a letter and press ‘Enter’

A. Word Processing
B. Accounting
C. Presentation Graphics
D. Organization Data
E. E-Mail
F. Calendar
F. Internet

.SELECT NAMES FROM PHONE WHERE ZIP = “22032” C:\>_

Command Language Menu

130
 Interface Examples

Q&A GUI

131
Implementing the System

CAHIMS 5.1, 5.3

132
 Implementation
The process of assuring the information system
is operational
– allowing users to take over operation and use
– continue feedback and evaluation

133
 Implementation Components
Putting the System Into Operation

• Enabling users with an information center

• Enabling users with appropriate training
• Which Conversion Strategy?
• System Evaluation - How well does it work?

134
 Information Center

• Primary Objective: Support internal organization users in

accessing data so that they are empowered to formulate,
analyze, and sole their own business problems or
questions through the use of computers.

135
 Training Users

• Who to train?
• Who provides training?

136
 Conversion

• Direct Old System New System

• Pilot Old System New System

• Phased Old System

New System

• Parallel
Old System

New System

137
 Evaluation

• User involvement
• System utility
– Matrix
– Information system functions
– Modules - Forms, Times, Places, Etc.

138
 Module 3

Project Management
CAHIMS 3.5

139
 Project Management

Analysis
and • Resources
Design • Time
Activities

140
Project Fundamentals

• Project Initiation
• Determining Feasibility
• Scheduling
• Managing Activities and
Personnel

141
Management Tools

• Gantt charts
– Task Listing
– Task duration - length of bar
• PERT diagrams
– Shows relationships
– Critical path
• Computer-based

142
 Project Management Software
• Identifying tasks
• Identifying task relationships
• Estimating task duration
• Resourcing tasks
• Resource costs
• Project and task reports

143
 Using MS Project
• Adding tasks
• Creating task relationships
• The Gantt chart
• Establishing baseline
• Tracking Gantt chart
• Resources
• Sharing resources
• Reports

144
 References
• Microsoft Project 2010
http://office.microsoft.com/en-us/project-help/training-courses-for-
project-2010-HA104039046.aspx
• Getting started with Project 2010 – 30-40 minutes online
http://office.microsoft.com/en-us/project-help/getting-started-with-
project-2010-RZ101831071.aspx?CTT=5&origin=HA104039046
• Microsoft Project YouTube Video – 23 min
http://www.youtube.com/watch?v=q7MKU4pYb8I
• Comparison of Project Management Software
http://en.wikipedia.org/wiki/Comparison_of_project_management_s
oftware
• Open Project
http://sourceforge.net/projects/openproj/

145
 Module 4

Security and Privacy

CAHIMS 7.2

146
 Security
• Access to hardware
• Access to software
• Access to data and information

147
 Privacy
• Federal laws govern privacy issues
• Health information privacy laws
• Physical procedures

148
 References
• Health Information Privacy – HHS.gov
http://www.hhs.gov/ocr/privacy/index.html
• Family Educational Rights and Privacy Act (FERPA)
http://www.ed.gov/policy/gen/guid/fpco/ferpa/index.html
• Top Ten Sources of IT Security Best Practices
http://voices.yahoo.com/top-ten-sources-security-best-practices-
6038104.html

149
 Module 5

Information Technology Management

CAHIMS 8.2

150
Five Functions of Management

Planning
Directing Staffing

Controlling Organizing

151
 Critical Areas
• Communications
• Databases
• Programming
• Hardware
• Industry Standards

152
 References
• Information Systems Managers – BLS
http://www.bls.gov/ooh/management/computer-and-information-
systems-managers.htm
• Information Technology Management – Wikipedia
http://en.wikipedia.org/wiki/Information_technology_management

153
 Module 6

I-T Standards and Best Practices

CAHIMS 4.3, 8.3

154
 COBIT
(Control Objectives for Information and Related Technology)

• Created by ISACA in 1996

• Internationally adopted standard for governance
• Framework to govern planning, deployment,
control, and maintenance of IT systems and
applications
• Ensures industry-standard best practices and
methodologies are applied

155
 COBIT Domains
• Plan and Organize
• Acquire and Implement
• Deliver and Support
• Monitor and Evaluate

156
 COBIT Domains

http://www.isaca.org/knowledge-center/cobit/Pages/Overview.aspx

157
COBIT Framework

http://www.counterpoint.co.za/pages/cobit.htm

158
 References
• ISACA
https://www.isaca.org/Pages/default.aspx
• COBIT
http://www.isaca.org/cobit/pages/default.aspx
• HealthIT.gov Info
http://www.healthit.gov/
• HANC I-T Best Practice Standards
https://www.hanc.info/datamanagement/Documents/IT%20Best%20Practice
%20Standards%20at%20DAIDS%20CTU-CRSCM.pdf
• Becker’s Hospital Review – 7 Best Practices for Hospital Implementing Health
Information Exchanges
http://www.beckershospitalreview.com/healthcare-information-
technology/7-best-practices-for-hospitals-implementing-health-information-
exchanges.html
• Healthcare Information Technology Standards Panel
http://www.hitsp.org/

159
 Module 7

Careers and Certifications

160
 Top Jobs in IT
• #1 IT Consultant
• #2 Cloud Architect
• #3 Computer Forensic Investigator
• #4 Health IT Specialist
• #5 Mobile Application Developer

Reference www.experience.com

161
 Health IT Jobs
• Careerbuilder.com
• Quick search on “Health IT”
• 51,528 jobs

162
 CompTIA
• CompTIA Healthcare IT Technician
• Industry certification covering
– US Regulatory requirements
– Organizational behavior
– IT operations
– Medical business operations
– Security

163
 References
• Top 10 Jobs in IT - #4 is Health IT
http://www.experience.com/entry-level-jobs/news/top-10-jobs-in-
information-technology/
• I-T Manager Jobs – Careerbuilder.com
http://www.careerbuilder.com/Jobs/Keyword/Information-Technology-
Manager/
• CompTIA
http://www.comptia.org/home.aspx
• Get IT certified
http://certification.comptia.org/

164
Led by Bellevue College, the Health eWorkforce Consortium was formed to elevate Health Information Technology
workforce development locally and nationally and provide career paths into this promising field for veterans and others.
The nine-college consortium includes Bellevue College, Bellingham Technical College, Clark College, Clover Park
Technical College, Northern Virginia Community College, Pierce College, Renton Technical College, Spokane
Community College, and Whatcom Community College. The Health Information and Management Systems Society
(HIMSS) is also a primary partner.

This workforce solution is 100% funded by an $11.7m grant awarded by the U.S. Department of Labor's Employment
and Training Administration. The solution was created by the grantee and does not necessarily reflect the official
position of the U.S. Department of Labor. The Department of Labor makes no guarantees, warranties, or assurances of
any kind, express or implied, with respect to such information, including any information on linked sites and including,
but not limited to, accuracy of the information or its completeness, timeliness, usefulness, adequacy, continued
availability or ownership

This work is licensed under a Creative Commons Attribution 4.0 International License.
Exceptions: 1) Materials identified as copyrighted or derived from another source. 2) Materials extracted from the Office of the National
Coordinator (ONC) Health Information Technology Workforce Curriculum, which carries a more limited CC BY-NC-SA license.

165