Administrative Applications Flashcards
(60 cards)
is a measure of the extent to which a system
can justifiably be relied on to deliver the services
expected from it
Dependability
Six (6) Attributes
System Reliability
Service Availability
Confidentiality
Data Integrity
Responsiveness
Safety
the system consistently behaves the same way. (there is continuity of correct service.)
System Reliability
required services are present and usable when they are needed. (correct readiness of availability)
Service Availability
sensitive information is disclosed only to those who authorized to see it. (ex. yung mga may mga stigma sa community; HIV, AIDS, Cancer, & etc. must be protected)
Confidentiality
data are not corrupted or destroyed.
Data Integrity
the system responds to user input within an expected and acceptable time period.
Responsiveness
the system does not cause harm.
Safety
Five (5) Fundamental Guidelines
Architect for Dependability
Anticipate Failures
Anticipate Success
Hire Meticulous Managers
Don’t be Adventurous
an enterprise system architecture should be
developed from the bottom up so that no critical component is dependent on a component less trustworthy that itself.
Architect for Dependability
features that are transparent to software applications should be implemented to detect faults, to fail over to redundant components when faults are detected, and to recover from failures before they become catastrophic. (threats or failures of the system)
Anticipate Failures
the systems planning process should anticipate business success and the consequential need for larger networks, more systems, new applications and additional integration. (kakayahan mag accept and expand ng mga new applications)
Anticipate Success
good system administrators should meticulously monitor and manage system and network performance.
Hire Meticulous Managers
An organization must use only proven methods, tools, technologies and products that have been in production, under conditions, at a scale similar to the intended environment. (reduce the numbers of failure to the intended users)
Don’t be Adventurous
is designed to bring the management of patient data into the information age. It is intended to replace the Medical Records Department of a medical institution, supporting the acquisition, storage, manipulation, and distribution of clinical
information throughout the organization.
consist of information technology that is
applied at the point of clinical care
Clinical Information System Revisited (CIS)
Eight (8) Phases
The Planning Phase
The System Analysis Phase
The System Design Phase
The Development Phase
The Testing Phase
The Training Phase
The Implementation Phase
The Evaluation Phase
begins once an organization has determined that an existing need or problem may be filled or solved by the development or implementation of a CIS or application. Establishing the committee framework to research and make recommendations for the project is an important first step and is variable based on the needs of the organization.
The Planning Phase
includes a description
of the how the system will be evaluated.
Definition of the Problem
is a preliminary analysis to determine if the proposed problem can be solved by the implementation of a CIS or component application.
Feasibility Study
drafted by the
project team and submitted to the project’s
steering committee for acceptance.
project scope agreement
A firm commitment of resources for the
development of the entire CIS project scope
agreement is needed before the system can
fulfill its stated objectives.
Allocation of Resources
The 5M’s of management
(manpower,
materials, machine, minutes, money;
micro¯o costing, methods)
fact finding phase
The System Analysis Phase
reflecting the existing
problem or goal is the first step in the system
analysis phase
Data Collection
