Long Range

Information System
Plan

Rahisha Harlalka
Rahul Nigam
Phase 1 - Initiate Project
Phase 2 - Analyze Situation
Phase 3 - Design Solutions
Phase 4 - Develop Plans
Benefits
Strategic benefits are necessary for gaining a niche in
the marketplace
operational advantages, or efficiency benefits, such as
lower costs and shorter schedules
 Long-range planning for information systems - community hospitals

follows of attempting to anticipate and resolve potential

difficulties
Changes in technology, vendors, or the hospital
environment all can prompt a reality test to verify the
correctness of the initial direction chosen
Why plan?
Senior hospital management usually acknowledges the
need to link IS requirements to institutional business
objectives
designed to assist in identifying and prioritizing the
projects that will provide the hospital with an organized
framework within which to work.
Review any existing hospital strategic business plan and
verify that it is current, well understood, and has been
adopted by the organization.
Briefly describe the services offered by the hospital, the
hospital's primary market, and any pertinent information
on the local environment and demographics.
Highlight the organization's strategic opportunities to
expand services as well as any significant anticipated
concerns.
Generally describe the impact of information technology
on each opportunity and concern.
To identify opportunities for enhancing the hospital's
current investment in information technology to
realize additional benefits through the automation of
additional applications and technologies.
The action plan prioritizes all recommendations based
on hospital needs, available resources, and
prerequisites.
After the business plan has been completed, the
technological impact of strategic goals and objectives
should be determined
User Interface for
Financial System
Enter virtually any business and you’ll find the same
types of software: word processors, spreadsheets, e-
mail and a financial system, such as Oracle, SAP,
Lawson, Great Plains or QuickBooks, depending on the
size and scope of the company. The first financial
systems were simple ledgers for tracking debits and
credits and producing basic financial reports. Over
time, they grew to include systems for accounts
payable, accounts receivable, payroll, cash receipts,
purchasing and other business functions. Some
systems — typically those labeled “enterprise resource
planning” systems — offer hundreds of components
including customer management, human resources
and warehousing.
Financial systems can be notoriously difficult to use.
One of the reasons is because they attempt to use a
similar user interface from module to module (and will
often use this as a selling point).
The problem is that a user interface that is ideal for a
general ledger system probably won’t work as an
interface for a purchasing system.
The result is low user adoption.
Types of user interfaces
Command interface
Menu interface
Object oriented interface
Expert system interface
Web form Interface