| ■ System Components
The development methodology used is the Component Ware
methodology.
What are components?
Components are simply building blocks that are grouped
together according to an application’s specific
requirements. They are binary programs that expose their
functions to other programs through a standard protocol.
The standard protocol used for inter-component
communication is the Microsoft ActiveX.
By nature, any component has to be developed using
Object Oriented Programming. Which means that we are
object oriented as well.
The Rx Cane is actually a number of components that we
developed to perform the common functions in the various
hospital activities.
The benefits of utilizing the Component Ware methodology
for the Rx Cane development is to be able to add any
new functions or applications, or to reorganize an
application in a different way. All of this can be done
with minimal effort and more importantly, without
disturbing the rest of the system
Another benefit is that Rx Cane advanced component
based architecture allows for seamless integration
between system components. Hence, integrating the
functionality of any component within any system module
is done seamlessly. So we can add registration functions
to the medical record or nursing according to the needs
of the hospital with minimal changes and in minimal
time.
■ Modularity
Based upon the Component Ware methodology that we
implemented, the Rx Cane is extremely modular, since
almost all of its functions are distributed among
different components.
■ Phased Implementation
Implementations can start with the minimal functionality
then add new functions as needed utilizing existing or
new components as required.
■
Database Independency
Our goal from day one was to enable our clients to fit
their needs and budgets. So we intended to be completely
database independent. This was an ambitious goal because
we wanted our clients to be able to use any desktop
database such as Access, FoxPro, etc…, as well as any
enterprise scale database such as Oracle, DB2, Informix,
SQL Server, Sybase, etc… .
However, utilizing both the Component Ware methodology
and the Microsoft Open Database Connectivity standards
we were able to do this.
Lightweight ODBC Database Connection components were
developed that were designed to connect once to the
database then pass that connection to any other system
component that requires database access. This technique
has increased the database access time dramatically.
On the other hand, we developed business components that
map all the database tables within the system. Such
components hold all the business logic pertaining to
such tables that would usually reside on the database
server.
Combining those techniques together, the Rx Cane has
achieved complete database independency out of the box
without any need for new versions or support modules or
even program recompilation.
■ Scalability
The Rx Cane goal as mentioned before is to offer each
and every client his exact requirements and to range in
implementation from a small uni-clinic where only a
doctor and a nurse are present, to a large busy hospital
exceeding 1000 beds with all the activities involved in
its running.
Again, both the Component Ware methodology and the
Database Independency have been key factors in achieving
this goal. Any implementation can start as small or as
big as the client requires, then it can grow over time
as the client’s requirements grow adding more components
to the system.
■ Integration
Utilizing the Component Ware methodology, the Rx Cane
can integrate any required functions or applications
that are currently not present in the system, given that
that applications that include functions support the
Microsoft ActiveX standard.
On the other hand, such functionality as DICOM support
and laboratory equipment data acquisition is achieved
through components. This makes it very simple to add say
a new laboratory analyser as soon as it becomes
available by integrating a component that specifically
communicates with it.
■ Active Medical Sheet Framework ©
The Active Medical Sheet Framework was the component of
choice to be the cornerstone of the Rx Cane. It is
licensed for use in Rx Cane’ various applications. It
is a general component that is extremely customisable.
It includes all the types of information that can be
needed at any point of care location at the hospital. It
includes a formatted free text area, a general data
fields area, an image area and multiple specific fields
areas that can include diagrams, data fields and images.
This framework consolidates all the information that a
care provider needs within one context, thus reducing
the time required to access information and increasing
the focus of the care provider. Beside that, the
framework is highly customisable to accommodate almost
all the changing requirements of a hospital clinical
need.
And based upon the Component Ware methodology, the
Active Medical Sheet Framework can call and utilize any
external components that are developed for specific use.
Due to the extreme flexibility of this component, it
will be referred to many times within the context of
many Rx Cane modules such as the Outpatient, the
Inpatient, the Radiology, the Endoscopy, Cardiac
Catheterisation, etc…
From the above brief description it is obvious that the
Rx Cane system is superior by design, flexible by
nature and advanced by functionality. It is your
hospital information management system for the future.
■ International Standards
ICD9/10-CM (International Code of Diseases, Clinically
Modified) with options of localization to national or
hospital standards.
ICSP 9/10 (International Code of Surgical Procedures)
with options of localization to national or hospital
standards.
■ Bilingual System
Rx Cane is a fully bilingual system. Where the use of
Local and Latin languages is supported through out the
system.
Rx Cane is completely localizable according to the
users needs. The authorized user will have the ability
–where applicable- to change the wording of all displays
according to the hospital policies.
Rx Cane Supports Arabic language and all the special
cases of Arabic. Like, Hamza, Alf Layena…etc
■ Rx Cane Reports & Statistics
Rx Cane is supplied containing a large set of
predefined reports serving most of the needs of the
hospital.
For purpose of generation of other reports, Rx Cane
supplies its users with an AD-HOC queries and report
generator subsystem to facilitate the process of
defining new sets of reports on demand to satisfy the
user’s requirements. The user can use this subsystem to
create, save, modify, and run new and existing reports.
New reports can be Also created in a generic report
designer such as Crystal reports then attached to the
Rx Cane © system using this module.
Users can create reports with listings, graphs and
images.
The system also has a generic Report Organizer
application that categorizes all the system reports into
meaningful groups.
■ Bar Code
Rx Cane supports barcode generation and reading
through its various subsystems. In the registration
process barcode is used for issuing patient ID cards. It
is used through all the pharmacy and stock control
functions for purpose of smooth and easy workflow and to
minimize data entry as much as possible. Barcode is also
used in the lab facilities for purpose of marking test
tubes, trays…etc
■ Archiving
Rx Cane supports image processing and storing
technology. Archiving of images, X-rays, voice, video
and images from PACs systems. They are all integrated
into the patients’ medical records. Thus keeping a
complete file for every patient including all images and
investigation results performed for him. This ensures
easy retrieval of data concerning the patient instantly
and re-viewing of any video or plane images by the
physician simply and smoothly.
■ Rx Cane Interfaces
Rx Cane can support virtually any interface
requirements for various types of equipments and various
software. This is due to the Open Standards and
Components Based Design of the system. Which allows Rx
Cane
to be integrated and to add more functionality as the
required.
Rx Cane fully supports DICOM 3.0 and HL7 standards.
And hence, communicates with any devices that uses any
of these standards.
Among the devices Rx Cane communicates with are;
Beckman - Synchronic Devices, Hitachi Devices, ACE
Devices, Etc…
■ Rx Cane Flexibility and Ease of use
Rx Cane is a very user friendly and flexible system.
“Making it easy for the user” was –and still- one of the
core ideas we had while designing and developing Rx Cane.
Rx Cane uses simple to use windows controls. With a
very easy to use graphical interface. Yet the system is
very powerful and diversified, the user has to worry
only about his/her own job. Rx Cane will handle all
inter-relations between various modules automatically
and on real time basis. Allowing for ease of use yet
strongly integrated system.
■ Security
- Rx Cane is secured against intrusion, hacking,
unauthenticated access and all other ways of accessing
unauthorized data.
- The tools used to maintain security:
- Login names and passwords to each user of the system.
- Different authorization levels to perform different
functions according to permitted access to the requested
information and actions.
- Classification of system functions according to user
levels.
- Centralized control is only permitted by system
administrator.
- Enabling and disabling devices and workstations from
accessing the system by the administrator.
- Recording history and log file of the attempts to
access unauthorized data and break security.
- Every activity done through Rx Cane is logged by
date/time stamp as well as the user name that performed
this activity and the workstation number from where it
was performed.
■ Client Server Deployment Architecture
The chosen deployment architecture is a client-server
architecture, utilizing a server as a dedicated RDBMS
server, an Intel based MS Windows 2000 workstations.
■ Identification (ID) Technology:
- The system support Barcode, smart and magnetic cards
technology, in several modules such as:
- Medication and consumables bar-coding.
- Patient ID: barcode, smart\magnetic card writer and
readers and two dimensional bar-coding (in progress).
|