UML Assignment Group D - BMI 3

Assignment in UML

Application of UML in understanding

National Health System in Sri Lanka

MSc – Biomedical Informatics 3rd Batch – Group 4

Postgraduate Institute of Medicine University of Colombo

Semester 1 December 2011

UML Assignment Group 4 – Biomedical Informatics 3rd Batch

Postgraduate Institute of Medicine, University of Colombo Page 1

Title Page

Batch Co-ord./Lecturer: Dr.Roshan Hewapathirana OFFICE USE ONLY Assignment received:

Tutor/Lecturer: Ms. Anchala Ishani Kuruppu

Student Group: Group 4

Names of Students:

1. M. T. Galagangodage 2. S. P. C. Kantha 3. J. A. Y. R. Perera 4. R. M. M. I. Rajapaksha 5. S. D. P. S. Senanayake

Assignment Title: Assignment in UML: Application of UML in understanding National Health System in Sri Lanka

We declare that all material in this assignment are our own work except where there is clear acknowledgement or reference to the work of others and we have complied and agreed to the university statement on plagiarism and academic integrity Signed : 1. Date :

2.

3.

4.

5.

Assessor’s feedback:

Assessor’s Signature (optional) : Date:



Content

Page

1. Introduction 3

2. Unified Modelling Language and Object Oriented Analysis 4

3. Introduction to National Health System 6

4. Why National Health System needs to reform 7

5. Using UML in understanding National Health System 9

6. An example from Sri Lankan Healthcare System 10

7. Use Case Diagrams 11

8. Class Diagrams 13

9. Activity Diagrams 15

10. Sequence Diagrams 17

11. Conclusion 20

12. References 21

13. Our Team 22

14. Acknowledgement 22



1. Introduction

Most of the existing traditional methods and customs of health care domain have been

upgraded with the modern information technology.

Object-oriented analysis and design (OOAD) is a software engineering approach that

models a system as a group of interacting objects. Each object represents some entity of

interest in the system being modelled, and is characterized by its class, its state (data

elements), and its behaviour. Various models can be created to show the static structure,

dynamic behaviour, and run-time deployment of these collaborating objects. There are a

number of different notations for representing these models, such as the Unified Modelling

Language (UML)i

Object-oriented analysis (OOA) is the process of analysing a task (also known as a problem

domain), to develop a conceptual model that can then be used to complete the task. ii Object

Oriented Analysis(OOA) by means of Unified Modelling Language(UML) can be utilized in

this context as a tool which can improve the existing methods and practices and built a

better system. OOA analyse a problem and define the requirements for an information

system as functional requirement and data requirement. These requirements can be

represented by UML.

The current Sri Lankan health care system is a typically slow traditional system which

brings most of its user dissatisfaction. This is a typical system where OOA and UML can be

deploying in problem analysis and designing tangible solutions. Keeping in mind of this we

have deployed the UML concepts to describe our local health care system to identify problems

and solutions for them.



2. Unified Modelling Language and Object Oriented Analysis

Unified Modelling Language (UML) is a standardized general-purpose modelling language

in the field of object-oriented software engineering.iii It is one of the most useful tools in

software development as it is a visual modelling language that enables system builders to

create blueprints that capture their visions in a standard, easy-to understand way, and

provides a mechanism to effectively share and communicate these visions with others.iv

UML is used for visualizing, specifying, constructing, and documenting the problem

domain.

It also models conceptual things such as business processes and system functions as well

as concrete things such as programming language statements, database schemas, and

reusable software components.

UML improves communication and understanding between the user and system analyst. It

provides better tools to document user requirements. It consists of a rich graphical notation,

and comprehensive set of diagrams and elements.

UML 2.0 defines thirteen types of diagrams and they are categorized in to three main

groups.v Categorization of thirteen UML diagrams is as follows.

1. Structure Diagrams:

Class Diagram

Object Diagram

Component Diagram

Composite Structure Diagram

Package Diagram

Deployment Diagram.

2. Behaviour Diagrams:

Use Case Diagram

Activity Diagram

State Machine (State Chart) Diagram

3. Interaction Diagrams:

Sequence Diagram

Communication Diagram

Timing Diagram

Interaction Overview Diagram.

Among above Class Diagram, Use Case diagram, Activity Diagram and Sequence Diagram

are more frequently used.

http://en.wikipedia.org/wiki/Modeling_language

http://en.wikipedia.org/wiki/Object-oriented

http://en.wikipedia.org/wiki/Software_engineering



Like in any other information system, development life cycle of a health information

system can be divided in to four main stages. They are,

1. Analysis Phase

2. Design Phase

3. Implementation Phase

4. Evaluation Phase

Analysis phase is the key to success of an information system. Gathering of user

requirements and functional requirements of the system will be identified in this phase.

Depending on gathered information, analyst provides direction for information system

development and it determines whether the information system will be appropriate to user’s

requirements. Improvement of productivity by using an information system greatly depends

on proper understanding and fulfilment of user requirements at the analysis phase.

Misunderstood or poorly prioritized user requirement are among the top causes of project

failure, budget overruns and user dissatisfaction.vi

Model driven analysis of information systems uses graphical notation to document current

or proposed systems. Model driven analysis consists of three main strategies. They are,

1. Structured Analysis

2. Information Engineering

3. Object Oriented Analysis

Object oriented analysis in a new advancement of model driven analytic techniques. In

object oriented analysis, software system is considered as a collection of objects, each of

which is the instance of a class within s hierarchy of classes.vii For this more than sixty object

oriented methods have been described and UML is the most accepted and widely used object

oriented method.



3. Introduction to National Health System

Health care is defined as multitude of services provided to individuals, families and

communities by agents of health services or professions for the purpose of promoting

maintaining, monitoring or restoring health.viii

Such services might be staffed, organized, administered and financed in every imaginable

way. But they all have one thing in common; people are being “served”, that is diagnosed,

helped, cured, educated and rehabilitated by health personnel.

For many decades the health services of Sri Lanka has developed more or less as two

distinct and parallel components; the curative (or medical) services and the preventive (or

public health) services with varying degree of integration at different levels.ix

According to this health care is provided through;

a. A network of medical institutions providing various levels of health services.

b. A network of health units (MOH areas, now corresponding to divisional secretariat

areas) providing public health services covering the entire extend of the island.

The overall objective of patient medical care services is to either cure the patient or

ameliorate the illness to an extent which would enable the patient to continue treatment at

home. In Sri-Lanka patient care services are deliver through three levels of institution namely;

Primary

Secondary

Tertiary care institutions

Public health care units are designed to provide preventive and rehabilitation services

which include;

Maternal and child care services

School health services

Prevention of communicable and non- communicable disease

Epidemiological surveillance

Environmental and occupational health services

Health education etc.

Information provides from these two components help for the basis of decision making in

the managerial process for health development in Sri Lanka.



4. Why National Health System needs to Reform

In Sri Lanka, both preventive and curative health systems existing information system is

mainly paper based. Each of the above health services i.e. in-patient, out-patient and fields

have their own data recording forms. Each patient contact is given a separate number. There is

no unique patient number linking different episodes. For example a patient will have different

in-patient record numbers for each disease conditions and as well as each admission. Paper

based records are stored for a maximum of 5 years. The data entered is not structured and can

vary depending on the clinician recording details.x

Identification of previous episodes or diseases is difficult as there is no unique number

linking different health events in a particular patient. Identification of past records is done

manually based on contact dates. When patients are discharged from the in-patient unit a

diagnosis card with a brief summary of the hospital admission is given to the patient. Many

patients in fields (e.g. Chicken pox, Mums, etc.), have no such card except they admitted to the

word.

It is difficult to identify such patients with the paper based recording system. Although

much clinical detail is recorded in the paper records, conducting research is difficult as the

records have to be manually reviewed to elicit data. Similarly statistics regarding service

provision is difficult to generate. Due to limitation of storage space records are maintained

only for a period of 5 years leading to loss of valuable data.

Health information technology provides the umbrella framework to describe the

comprehensive management of health information and its secure exchange between

consumers, providers, government and quality entities, and insurers.

While implementing Health Information Technology; the healthcare system of the country

should consider the model to achieve better acceptability and sustainability of the system. The

managers and policy maker should formulate the important policies, allocate adequate

resource and design processes where the end user down the line can get maximum benefit

from the system.

There are many health related issue arises due to the lack of health information support

and prompt reporting in the existing National health system.

1. Problems in providing critical supply continuously due to lack of accurate and timely

stock inventory reports.

2. Inadequate detection and control of communicable diseases due to failure of receive

reports of notifiable communicable diseases from Govt. sector and private sector.

3. Inadequate planning and scheduling of critical activities and services due to certain

facility types or service levels not regularly submitting routine operation plans and

monitoring reports.



4. Due to patient and clinic records fail to identify high-risk patients, families and

communities, inadequate attention is given to finding and serving high risk and

underserved populations in the island.

5. Lack of up-to-date population data which identifies less advantaged population groups.

Hence inadequate health protection and service provided to poor populations.

6. Staff at facility and district level does not maintain records and present data in a

manner which enable monitoring of coverage and quality of their services.

Healthcare system of the country should look forward in implementing this business

process with the technology in providing quality healthcare to the individual and the

community but before that it is required to understand the health information technology, its

application, reason to use and its impact.

The ultimate aim of health information technology in healthcare is to provide optimal

information support to the healthcare professionals, managers and policy makers for quality

decision making, care and treatment. The health information technology provides highly

secure, economical, easy to use, always available, point of care application.



5. Using UML in understanding National Health System

The Unified Modelling Language (UML) is one of the most exciting and useful tools in the

world of system development.

Communicating the vision is of utmost importance. Before the advent of the UML, system

development was often a hit-or-miss proposition. System analysts would try to assess the

needs of their clients, generate a requirements analysis in some notation that the analyst

understood (but not always the client), give that analysis to a programmer or team of

programmers, and hope that the final product was the system the client wanted.xi

The UML consists of a number of graphical elements that combine to form diagrams.

Because the UML is a language, it has rules for combining these elements.

The existing National Health system can be developed in business process modelling using

UML and can be achieve the following privileges.

Improving program efficiency by collecting, processing and analysing a large amount of

data quickly. As the manual systems are by nature paper-heavy, managers are often

buried under the mountain of data result in which they are unable to navigate the

information for quality decision making.

Producing a wide variety of output and feedback reports targeted for many level of the

health system from a single data set or by combining data sets.

Reducing the duplication of work where the data can be entered once and will be

available to at any point of to the care providers, mangers and policymakers.

Automatic validation helps the care providers to improving the quality of data

collection through automatic validation during data entry and automatic preparation of

immediate feedback reports on error for individual health facilities.

Improving analysis and information presentation to facilities data interpretation and

use for decision making.

Managing the data for monitoring the attainment of health program targets and

objectives.

Developing decision support tools for planning increased service coverage and logistics

(e.g. target cost from future group)

Helping the primary health centres, district and national health team in healthcare

resource determinations.

All the above represent the reason to use business process model to health care setup and

as well as required to understand the types of application at each level of healthcare setting

for various clinical and administrative activities.



6. An example from Sri Lankan Healthcare System

Our example is a Medical Clinic running in a tertiary care hospital. This clinic is held at clinic

complex at outpatient department. It serves its services to the patients with medical

problems.

It feeds the patients from,

Referred from the outpatient department

Referred by other consultants in same Hospital

Referred by consultants from some other secondary care hospitals/primary care

Hospitals

Inward patients who discharged and ask to attend to the clinic

Direct referral by the physician

This clinic composed with,

Doctors

Physician

Senior Registrar

Registrars

Senior house officers

House officers

Nurses

Nursing sister

Nurses

Medical Laboratory Technician

Dispenser

Once patient comes to the clinic, he is given the token first come first serve methodology

.Two types of tokens are given.

a. Red-first comers

b. blue-second and follow up patients

According to the token number patient is registered by the receptionist nurse. Then he/she

is directed to the next vacant doctor.

Red numbers to the House Officers

Blue numbers to the one of senior house officers.

Red numbers then seen by the one of the registrars and directed to the physician. Problematic

blue numbers are also seen by the registrar/ senior register. Once who need the

investigations, supply the request forms and directed to the relevant department. The drugs

prescribed to the patient, is issued by the Pharmacy.



7. Use Case Diagrams

An important part of the Unified Modelling Language (UML) is the facilities for drawing use case diagrams. Use cases are used during the analysis phase of a project to identify and partition system functionality. They separate the system into actors and use cases.

Actors represent roles that can are played by users of the system. Those users can be humans, other computers, pieces of hardware, or even other software systems. The only criterion is that they must be external to the part of the system being partitioned into use cases. They must supply stimuli to that part of the system, and the must receive outputs from it.

Use cases describe the behaviour of the system when one of these actors sends one

particular stimulus. This behaviour is described textually. It describes the nature of the stimulus that triggers the use case; the inputs from and outputs to other actors, and the behaviours that convert the inputs to the outputs. The text of the use case also usually describes everything that can go wrong during the course of the specified behaviour, and what remedial action the system will take. (1).

Regarding our local health care system of Sri Lanka most of its users are unaware about the exact servicers provided by the system and unsatisfied as their requirements are not fulfilled by it. Use cases can be utilized effectively to identify the main actors of the system and their requirements and how a proper system should be built and functioning. So we can deploy use case diagrams as an initiative of improvement in our local health care system. The example we took the medical clinic has main actors namely patient, doctor, clerk, dispenser and technician. Fig-1 show the use case diagram of our system and depict all the actors and possible use case scenarios.

Table1: Use case - Course of Events

Use case name Register in the Clinic

Actors Patient, Clerk

Description This use case describes the procedure of registering a patient in the medical clinic by a clerk

Typical course of events The Register in the Clinic use case begins when a patient comes to the medical clinic for the first time and registration process is carried out by a clerk. The patient comes with the referral form and the clerk checks it and assigns a number generated by register order.

Alternative courses None

Preconditions The patient should have a valid request for clinic registration

Postconditions Every registered patient should be having a Clinic number



As use case should be described in fully by means of documentation of the actor, the typical and alternative course of events, pre and post conditions, we considered “Register in the Clinic” use case as an example and Table-1 represent the narrative of the “Register in the Clinic” use case.

Figure 1: Use Case Diagram

The main limitations in applying the use cases in to our Clinic system is the lack of properly

trained staff and organized record system this leads to errors like assigning same number to different patients which will create confusion, misdistribution of resources.

Establishing an organized system will eliminate this which can be initiated with UML Use

cases.



8. Class Diagrams

The next most important area of UML is the Class and Class diagrams. Once the objects are

identified from use cases the similar objects with similar operations are grouped and the

semantic relationships among deferent objects are identified.

A Class is defined as a blue print or a set of specifications for a collection or group of

objects that have similar attributes and operations. The attributes are the properties of the

objects which help to identify them uniquely. Operations are the things that objects can

perform.

A class diagram in the Unified Modelling Language (UML) is a type of static structure

diagram that describes the structure of a system by showing the system's classes, their

attributes, operations (or methods), and the relationships among the classes.(2)

During system analysis Class diagrams are used to demonstrate the common roles and

static relationships among Objects.

The relationships are static and demonstrate the connections among classes and they are

of five types namely, Dependency in which describe a relationship between two objects when

changes takes place in one object brings changes of the other object.

Association is a structural relationship type between two similar classes or its objects and it

is bidirectional and description of it should include the multiplicity or the degree of the

association. The degree of this relationship shows how many object instances from one class

can have an association relationship with one object instance of the other class.

Generalization show how parent classes are formed from the merging of daughter classes

based on some similar characters. Specialization is the reverse of generalization in which a

class is further divided into daughter classes which are having more special characters. In this

manner a parent class attributes will be inherited by daughter classes which are having more

specialized attributes as well.

Aggregation and Composition are relationships which demonstrate how objects are

composed of simpler objects. Aggregation also called IS-A relationship and is a special type of

association relationship which depict as one object/class is composed of several small

objects/classes. Composition is a strong type aggregation relationship which demonstrates

how a whole object is composed of simpler objects which alone is meaningless in real world.

These fundamentals play a vital role in the Object Oriented Programming which is based on

Objects.



So when we consider our medical clinic example we identified the under mentioned

classes namely Patient, Doctor, Nurse, Clerk, Technician, Dispenser, Prescription, Drug,

InvestigationRequest, InvestigationResult, ClinicSession, Appointment and their relationships.

Once a patient comes to the Clinic with the clinic request a Clerk register the patient by

assigning a specific number and an appointment will be given. Then the patient is directed to a

doctor who interacts with the patient in a clinic session which may generate a prescription,

investigation request. The investigation request will be send to technician and who will return

investigation results. The prescription will be send to dispenser who will issue drugs

accordingly. The main relationship type here is association type as demonstrated in Figure 2

with the degree of relationships.

Figure 2: Class Diagram

This class diagrams with their relationships clearly depict how we can use UML and OOP to

improve the common short comings which are existing in the current system for example the

investigation results may be delayed or even misplaced as they are paper based and if we can

generate an automated feeding system we can retrieve the results in a timely manner.

The main limitations are the lack of, patient and staff education about such system, IT

infrastructure and capable operators of such automated system and so on.



9. Activity Diagrams

Activity diagrams describe the workflow behaviour of a system and state of activities by

showing the sequence of activities performed. It visually represents the process and process-

related collaborations of individuals, organizations, and systems.xii

Table 1: Activity Diagram Concepts

Concept Description

Activity on going

Ongoing non-atomic execution within a state machine. Activities ultimately results in some actions

Action An executable atomic computation that results in a change in state of the system or the return of a value.

Transition Represents the flow of control between two activities.

Object [State] A condition or situation during the life of the object.

Event Reception A state that represents the execution of an atomic action, typically the invocation of an operation.

Swim Lane A partition of organizing responsibilities for activities. They often correspond to organizational units in a business-model

Stereotypes UML extension mechanism that allows the creation of new kind of building blocks and are specific for a particular problem

Advantages of using Activity diagram.

Activity diagrams are to model the workflow behind the system being designed, to analyse

a use case by describing what actions need to take place and when they should occur. It

describes a complicated sequential algorithm, to model applications with parallel processes.

One strategy for modelling the function of the system begins with identifying the actors,

i.e., objects or persons outside the system that interact directly with it and initiate an input to

the system (in our example medical Clinic) .Actors could be users of the system or other

system such as health care providers (doctors ,nurses ,technical staff), patients.

Use case is a representation of the actors that initiate events in the system and how the

system responds to the events. Each use case yields an observable result of value to a

particular actor.



Figure 3: Activity Diagram



In our example we have identified the actors and further clarify user–system interactions

in a sequential manner by our real world experience.

The strategy for the development process, i.e. the order of, and the allocation of

responsibility for, development of modules of the system can be easily managed with activity

diagrams. In our example we can allocate responsibility for each and every actor in the system

the benefit of this is no one can escape from the responsibility, because it is clearly allocated

and defined.

10. Sequence Diagrams

Sequence diagrams represent dynamic behaviour of the system. A sequence diagram

focuses on the time ordering of the messages that go back and forth of the system. Basically

there are two elements involve in a sequence diagram,

1. Objects

2. Messages

It consists of sequence of interactions among different objects over a period of time. The

interactions between different objects in a sequence diagram are represented as messages.

There are three types of messages

1. Synchronized messages

2. Asynchronized messages (simple)

3. Return messages

Sequence diagrams show a detailed flow for a specific use case or even just part of a

specific use case. They are almost self-explanatory; they show the calls between the different

objects in their sequence and can show, at a detailed level, different calls to different objects.

A sequence diagram has two dimensions: The vertical dimension shows the sequence of

messages/calls in the time order that they occur; the horizontal dimension shows the object

instances to which the messages are sent.



Figure 4: Sequence Diagram

In this example we describe the process of admitting a new patient. Bystander or patient

him/herself provides information to an admissions clerk. An appointment is given to the

patient. Patient participates to the particular clinic session and a patient record is created.

Now the patient is forwarded to a doctor. A medical history is created by the doctor,

Examination done, then the doctor order investigation to laboratory including biochemistry,

pathology, radiology etc.

Doctor may request patient to attend new clinic session and patient receive re-visit

appointment. Now a laboratory report is generated and returned to the doctor. Then the



doctor comes to a diagnosis and generates a drug prescription. Drug prescription directly goes

to outdoor dispensary and pharmacist issue drug to the patient.

This pattern has the following advantages:

a. All information about a patient is recorded and documented even if there are re-

examinations during that stay.

b. When a patient is admitted and discharged, the treatment history is added to the

medical history and all treatments within the medical group will be kept for future

reference.

c. If a patient discontinues treatment for any reason this information will be on record.

d. All the assignments of personnel or physical resources are explicitly described.

Role based access control can be used to protect this information. The access to patient

treatment information can be controlled based on the role of the individuals.

Limitations of sequence diagrams:

a. Since there are snap shots of what happens in a given period of time, sequence

diagram do not show a complete sequence-they are incomplete.

b. Number of sequence diagram required in a given design is not clearly known. It

depends on the experience of the designer as to when to stop developing them.

Theoretically number of sequence diagram can be drawn within a given design.

c. The way in which system designers use these diagrams(technical level) is different to

the way system analysts use them(business process level).Inappropriate types of usage

of these diagrams can be counterproductive in practice.



11. Conclusion

Health care system in Sri Lanka is about to step a great leap forward by reforming its

structure and functionality. Health informatics plays an enormous role in this revolution as one

of the key areas of development well be health information systems.

Poor understanding and prioritization of user requirements will be a main drawback in

development of health information systems. Failure to understand user requirements results

in unsuccessful implementation and inefficient functioning of healthcare information

system.xiii

Object oriented analysis of health care system facilitate the proper communication and

comprehensive documentation of user requirements. It considers both the process and data

together, resembling real world objects. This enhances communicating, understanding and

modelling of user requirements comprehensively.

Unified Modelling Language is an object oriented modelling tool with a set of graphical

notations which can be used to model user requirements as well as system behaviour.

In this report we have discussed how Unified Modelling Language can be used in

understanding information systems related to health care system in Sri Lanka with some real

world examples.



12. References

i Infrastructure/PDF/http://www.omg.org/spec/UML/2.4.1/

ii Object-oriented_analysis_and_design /http://en.wikipedia.org/wiki/

iii Unified Modeling Language, Reviewed December 7, 2011, from

http://en.wikipedia.org/wiki/Unified_Modeling_Language

iv Schmuller, J., Sams Teach Yourself UML in 24 Hours, 3rd edn., Sams Publishing, 2004.

v Introduction to OMG's Unified Modeling Language™ (UML®), Reviewed December 7, 2011 from

http://www.omg.org/gettingstarted/what_is_uml.htm

vi Lee, F., Teich, J. M., Spurr, C. D., and Bates, D. W., Implementation of physician order entry: User satisfaction and

self-reported usage patterns. J. Am. Med. Inf. Assoc. 3:43–55, 1995.

vii Booch, G., Object-Oriented Analysis and Design With Applications, 2nd edn., Benjamin/Cummings, Redwood City,

CA, 1994.

viii Manual of management for Provincial Directors Ministry of health – Sri Lanka, 1996.

ix Manual of management for Divisional Directors of Ministry of health – Sri Lanka, 1996.

x Sinha,R.K., Impact of Health Information Technology in Public Health: Sri Lanka Journal of Bio-Medical Informatics

2010;1(4)223-36.

xi Dahanayake,S.P.K.,Fernando,N..,De Silva,V.A., Electronic Patient Record System for a Psychiatry Unit in Sri Lanka: Sri

Lanka Journal of Bio-Medical Informatics 2010;1(4) 214-21.

xii Spyrou,S.,Bamidis,P.,Pappas,K.,Maglaveras,N., Extending UML Activity Diagrams for Workflow Modelling with

Clinical Documents in Regional Health Information Systems: Connecting Medical Informatics and Bio-

Informatics,2005.

xiiiAggarwal, V., The Application of the Unified Modelling Language in Object-Oriented Analysis of Healthcare

Information Systems



13. Our Team

Name PGIM No.

1 Dr. M. T. Galagangodage MSc/BMI/SM/I – 07

2 Dr. S. P. C. Kantha MSc/BMI/SM/I – 12

3 Dr. J. A. Y. R. Perera MSc/BMI/SM/I – 16

4 Dr. R. M. M. I. Rajapaksa MSc/BMI/SM/I – 19

5 Dr. S. D. P. S. Senanayake MSc/BMI/SM/I – 20

14. Acknowledgement

Prof. Vajira H. W. Dissanayake MBBS (Colombo), PhD (Nottingham)

Chairperson, Specialty Board in Biomedical Informatics, Postgraduate Institute of Medicine,

University of Colombo

For the valuable guidance, encouragement and advice

Dr. Roshan Hewapathirana MBBS (Colombo), MSc in IT (Moratuwa)

Project Manager, MSc Biomedical Informatics Course

For guidance and constant supervision as well as for providing necessary

information

Ms. Anchala Ishani Kuruppu BSc, MSc

Visiting Lecturer, MSc Biomedical Informatics Course

Who extend her valuable knowledge on Web Designing to us and created us

capable of doing this assignment, as well as her simple and comprehensive teaching which

made a fun to do this assignment

Mrs. Harshya and NOMA office

For their kind co-operation, help and skillful coordination

PGIM Colombo For rendering their services, support and help

Date post:	23-Sep-2014
Category:	Documents
Upload:	manju-galagangodage
View:	222 times
Download:	1 times