SOFTWARE ENGINEERING | |||||
Bachelor | TR-NQF-HE: Level 6 | QF-EHEA: First Cycle | EQF-LLL: Level 6 |
Course Code | Course Name | Semester | Theoretical | Practical | Credit | ECTS |
HEM3065 | Palliative Care | Fall | 2 | 0 | 2 | 6 |
This catalog is for information purposes. Course status is determined by the relevant department at the beginning of semester. |
Language of instruction: | Turkish |
Type of course: | Non-Departmental Elective |
Course Level: | Bachelor’s Degree (First Cycle) |
Mode of Delivery: | Face to face |
Course Coordinator : | Dr. Öğr. Üyesi EVİN KORKMAZ |
Course Lecturer(s): |
Assoc. Prof. İSMAİL TOYĞAR Instructor EMİNE ÖZDEMİR ASLAN |
Recommended Optional Program Components: | None |
Course Objectives: | To know the aim, philosophy and principles of palliative care and the role and responsibilities of a palliative care team, to identify the palliative care requirements of a patient and their family, and to gain the knowledge and skill required for practicing within the care period and in effectively coping with mourning period. |
The students who have succeeded in this course; 1. Knows the aim, philosophy and principles of palliative care. 2. Knows the ethical and legal issues regarding palliative care. 3. Identifies the role and responsibilities of the palliative care team. 4. Identifies pain and other symptoms in a patient who needs palliative care and being able to plan the nursing interventions for these symptoms. 5. Being able to determine the requirements of patient and their family for palliative care. 6. Being able to communicate with patient and their family. 7. Identifies the requirements for the end of life, being able to plan and apply care. 8. Being able to plan care for the family who is within the mourning period. |
To know the aim, philosophy and principles of palliative care and the role and responsibilities of a palliative care team, to identify the palliative care requirements of a patient and their family, and to gain the knowledge and skill required for practicing within the care period and in effectively coping with mourning period. |
Week | Subject | Related Preparation |
1) | Introduction of the Course | |
2) | Aim, philosophy and principles of palliative care. Diseases that require palliative care | |
3) | Palliative care in our country and in the world Palliative care nursing in our country; legal arrangements, role and responsibilities | |
4) | Palliative Care and Ethics | |
5) | Institutions that provide palliative care Palliative care at home and problems experienced; care burden | |
6) | Symptom management - Pain | |
7) | Symptom management-Nausea-Vomiting, Constipation, Diarrhea | |
8) | Nutrition | |
9) | Symptom management-Dyspnea, Fatigue | |
9) | Midterm Exam | |
11) | Symptom management-Psychosocial Symptoms | |
12) | End-of-life care | |
13) | Loss and Mourning Period; Communication and Cultural Applications | |
14) | Evaluation of the Course |
Course Notes / Textbooks: | Ders notları haftalık olarak verilecektir. |
References: | 1. Özçelik H, Fadıloğlu Ç, Uyar M, Karabulut B. (2010). Kanser Hastaları ve Aileleri için Palyatif Bakım, İzmir. 2. Cimete G., (2002). Ölümcül Hastalarda Yaşam sonu Bakım, Nobel Tıp Kitabevleri, Ankara. 3. Foley K.M., Gelband H. (2001). Improving Palliative Care For Cancer, National Academy Press. 4. Palyatif Bakım Programı (2009) içinde: Ulusal Kanser Kontrol Programı 2009-2015 (Editör: Tuncer, M). T.C. Sağlık Bakanlığı Kanserle Savaş Dairesi Başkanlığı, Bakanlık Yayın No:760; ss:92-110. 5. Kömürcü, Ş. (2009). Türkiye'de Palyatif Bakım. içinde Türkiye'de Kanser Kontrolü. (Editör: Tuncer, A.M). Kanserle Savaş Dairesi Başkanlığı, Yayın No: 777, Ankara; ss: 299-304 6. Erel, S (2009). Dünya da Palyatif Bakımın Durumu ve Hospis Sistemleri içinde Türkiye'de Kanser Kontrolü. (Editör: Tuncer, A.M). Kanserle Savaş Dairesi Başkanlığı, Yayın No: 777, Ankara; ss: 287-298 7. Tuncer A. M.(Ed) (2009). Türkiye'de Kanser Kontrolü, "Palyatif Bakım", Sağlık Bakanlığı, Yayın No:777, Ankara. |
Semester Requirements | Number of Activities | Level of Contribution |
Midterms | 1 | % 40 |
Final | 1 | % 60 |
Total | % 100 | |
PERCENTAGE OF SEMESTER WORK | % 40 | |
PERCENTAGE OF FINAL WORK | % 60 | |
Total | % 100 |
Activities | Number of Activities | Duration (Hours) | Workload |
Course Hours | 14 | 2 | 28 |
Presentations / Seminar | 2 | 20 | 40 |
Homework Assignments | 2 | 20 | 40 |
Midterms | 1 | 20 | 20 |
Final | 1 | 20 | 20 |
Total Workload | 148 |
No Effect | 1 Lowest | 2 Low | 3 Average | 4 High | 5 Highest |
Program Outcomes | Level of Contribution | |
1) | Be able to specify functional and non-functional attributes of software projects, processes and products. | |
2) | Be able to design software architecture, components, interfaces and subcomponents of a system for complex engineering problems. | |
3) | Be able to develop a complex software system with in terms of code development, verification, testing and debugging. | |
4) | Be able to verify software by testing its program behavior through expected results for a complex engineering problem. | |
5) | Be able to maintain a complex software system due to working environment changes, new user demands and software errors that occur during operation. | |
6) | Be able to monitor and control changes in the complex software system, to integrate the software with other systems, and to plan and manage new releases systematically. | |
7) | Be able to identify, evaluate, measure, manage and apply complex software system life cycle processes in software development by working within and interdisciplinary teams. | |
8) | Be able to use various tools and methods to collect software requirements, design, develop, test and maintain software under realistic constraints and conditions in complex engineering problems. | |
9) | Be able to define basic quality metrics, apply software life cycle processes, measure software quality, identify quality model characteristics, apply standards and be able to use them to analyze, design, develop, verify and test complex software system. | |
10) | Be able to gain technical information about other disciplines such as sustainable development that have common boundaries with software engineering such as mathematics, science, computer engineering, industrial engineering, systems engineering, economics, management and be able to create innovative ideas in entrepreneurship activities. | |
11) | Be able to grasp software engineering culture and concept of ethics and have the basic information of applying them in the software engineering and learn and successfully apply necessary technical skills through professional life. | |
12) | Be able to write active reports using foreign languages and Turkish, understand written reports, prepare design and production reports, make effective presentations, give clear and understandable instructions. | |
13) | Be able to have knowledge about the effects of engineering applications on health, environment and security in universal and societal dimensions and the problems of engineering in the era and the legal consequences of engineering solutions. |