|
    
    
Introduction
The InHCc System is an Integrated Application System. There is no "interface" between modules.
The system is designed for ease of integration of modules through a Centralized
Database.
Every User of the InHCc system see exactly the
same data.
All departmental modules use the same data but with
different views to perform their work. By having access to the same data, data
is available immediately to every other department for their use.
International
Standardized Coding systems
Microsoft Health Framework
InHCc's software products are built using
Microsoft's Visual Basic .NET and designed according to the Microsoft Health Framework.
-
Modular business applications
-
Business Rules easily changeable
-
Single database design
-
Analysis and Reporting common to all
applications
-
Enterprise level Security
-
Integration across systems
Updates, addition of functions, screen design
changes are easily made by anyone who has had a single course in Visual Basic
.net. The system is easily modifiable through adding or deleting tables in SQL.
No programming needs to be performed to change the work flow
InHCc HMIS is built around a three-tier
architecture design that provides for the system to be installed in locations
where there is No Internet (in one of our locations, 30% of the units do not
even have electricity!), or in a National Centralized data warehouse with access
through the Internet. We use Microsoft Business
Intelligent (BI) products extensively in our application products. These
products consists of the following:
-
Microsoft SQL Server©
-
Microsoft Data Warehouse©
-
Microsoft Integration
Services©
-
Microsoft Analysis Services©
-
Microsoft Data Mining©
-
Microsoft Reporting Services©
-
Microsoft
SharePoint© Portal
Applications
Using a single framework, allows the
institution to ensure compatibility between departments, reduces training
costs, and provides an centrally located monitoring system.
-
Using Windows standardized design format
provides a screen that is intuitive and easy to use. This reduces the
training time and training expense.
-
Easy to convert components to
internet protocols to enable remote access through the Internet to
centralized servers or other interested stakeholders.
-
Easy to distribute updates through
Microsoft's "One Click"
-
Environment settings allow for multiple
languages and area formatting of currencies, numbers and dates.
-
Web based distribution of data.
Before .NET, many
internal corporate applications were browser- based simply because of the cost
of installing and maintaining a client application on hundreds or thousands of
workstations. Windows Forms and the .NET Framework change the economics of these
decisions. A Windows Forms application is much easier to install and update.
With a simply XCOPY deployment and no registration issues, installing and
updating become much easier. Internet deployment via ClickOnce also makes
applications more available across a wide geographic area, with automatic
updating of changed modules on the client.
This means that “smart
client” applications with a rich user interface are more practical under .NET
even for a large number of users. It is not necessary to resort to browser-based
applications just to save on installation and deployment costs.
Now it is possible to
examine applications in .NET and explicitly decide what kind of interface makes
sense in a given scenario. In some cases, applications that you might have
assumed should be browser based can be smart-client based, which can improve
usability, security, and productivity.
In other cases, it might
be appropriate for parts of your system to expose a Windows Forms Interface, and
other parts to expose a browser-based system. Because logic for data access and
other system chores is compatible with both of those UI technologies, multiple
forms of user interface could easily work with the same server-based
functionality.
Work Flow
Screens are designed based on the data requirements of
"Evidence Based Medicine". The screens are designed such that all the data
requirements are featured on the screen as discrete atomic data fields.
Work Flow has been designed to present the needed data fields
to the healthcare professional in the most effective and efficient structure.
Steps in Design
The architect and design of a database system falls into several distinct steps. The
steps in the design depends on the Layer that is involved. Generally the
design of the system should be an iterative process; as we finish each
evaluation, we will then go back and look at all previous steps again.
The focus of this system will be
at the Service Delivery Level. It is here that the data is actually collected and
can be checked for quality assurance.
All data will be collected into the
Centralized Data Warehouse . This repository of data is located in a central
storage facility from which users can retrieve data whenever they need it
providing they have the permission to do so. Using
a single and centralized data warehouse as a data source increases the quality
and consistency of an organizations' data.
There would be no need for complication
applications or a large technical support team at the local site. Modifications
and new applications can be downloaded on demand over the Internet. After
collection, this data would then be sent by Internet to a Centralized Data
Warehouse that could be placed in a location anywhere in the world. It is here,
and only here, that a technical support team need be present. At this location,
data can be analysis and presented back to management at the required level
using OLAP on the users Web browser. Each manager and level of service would
have their own View. Since all data is collected and is present in one location,
Data Mining techniques can be used for research. Training and monitoring can be
easily done remotely. Costs are minimized since all data is collected only once.
There is minimal need for technical staff scattered throughout the system and
high priced computer system are not needed.
The user's interface is designed to integrate all functions
of an organization and is organized in a manner that mirrors
the business processes of the organization.
The processes have been designed in a way to force the user
to use good business and professional practices and has been designed in a way
that reinforces the use of these practices.
Functional Design
Although data
input would still occur at the lowest levels, there is no need to
require that the staff at this level learn how to use statistical methods to
analysis data. This
function can be centralized where the money and skills are available to
manage such a function. The presentation of the results of the statistical
analysis, however, can be
easily given to those who need the information in a timely manner. This gives
to the manager the ability to manage at all levels without losing control.
The most
important objective in any endeavor is Teaching. The ability of the
higher-level managers to drill down to the details of the lower levels enables
the higher-level managers to teach the lower level manages what they need to
do to manage. Priories can be reinforced. In the past, it was expected that
the lower level manager analyze and manage their data. The emphasis in health
care management was on having the managers at the clinical level be
responsible for managing this local data. With very few exceptions, the
lower level managers were “out there” by themselves. They had little
training and knew very little about what to look for. By being able to
"see" what the lower level managers are doing, the higher-level
manager can teach. This provides for improved communication between all levels
of management. It gives the lower level managers a sense of belonging
and a sense of not being along. He is now a part of the process.
Additional Projects can be easily combined with the existing system.
For Example, by incorporating simple questions for the clients into the clinical routine,
the need for surveys can be limited. Instead of using costly, one-time
surveys, information stored in the data warehouse, is cheap and routine.
Trends can be more easily identified and action taken quicker.
Lower-Level
Clinics
The Lower-Level Clinics will be located at the local neighborhood.
The Lower-Level
Clinic System will be designed to provide the functions that are generally
carried out at this level.
The Lower-Level Clinics are not excepted to be connected to the Network full
time. The health care information is collected through the local SQL database and uploaded to the
IT database at specified times through a Remote Dial-Up Connection. At the
same time data and information can be downloaded from the Centralized Database
to the clinic.
Mid-Level Clinics
The Mid-Level Clinics may be a regional clinical unit or a mid size clinic
that receives referrals from lower level clinics.
The Mid-Level Clinics are not excepted to be connected to the Network full
time but may be connected directly part of the times. Remote Dial-Up
Connection is used as a back up. The health care information is
collected through SQL server and uploaded to the IT database at specified times. At the same time
data and information can be downloaded from the Centralized Database to the
clinic.
Higher - Level Clinics
The
Highest Level Clinic will generally be part of a larger hospital unit. In many
cases, the hospital may have more than one location.
Each Level will make referrals to other levels
The
Higher-Level Clinic is excepted to be connected to the Network full time. The
health care information is collected and uploaded to the IT
database only at specified times. Data and Information can be downloaded from
the Centralized Database to the higher level clinic at all times.
Each management level will be completely responsible for the units and
population assigned to them from lower levels and catchments areas. For Example:
Mid Level Clinics will be responsible for the health care of the population
and the Lower Level Clinics in their assigned area.
Resource allocations, both staff and supplies, will be based on risk
factors and forecasted needs accessed at each unit.
A Data Mart may be located in the same location as the High
Level Unit.
DATA Transfers
In Microsoft SQL, all forms of data can be
transferred in and out of the database. SQL uses Integration Services
for all transfers. While Integration Services is a wonderful tool…it is not the
easiest to learn…Integration services can not only move data from one location
to the other but it can also transform the data while it is being done. The
system cannot be ran effectively or efficiently without this service.
http://www.microsoft.com/sqlserver/2008/en/us/integration.aspx
| 
