1. Enhancement of study programs in Public Health Law, Health
ERASMUS+ KA2 PROJECT:
Enhancement of study programs in Public Health Law, Health
Management, Health Economics and Health Informatics in Montenegro
Consortium Meeting
19-20th April, Germany
Project web site:

2. WP2: Human Capacity Building in Public Health Education in Montenegro
PH-ELIM
Activity 2.2: Teaching Competencies Development of academic staff from Montenegro – Report from 8th training event
WP2: Human Capacity Building in Public Health Education in Montenegro .

3. Project web site: www.ph-elim.net
Conducted Trainings
Participants
UDG: 1 person  mathematics and informatics
UCG: 2 persons  physicians
IMTM: 1 person  software engineer
IPHMNE: 1 person  physician, statistician
UMIT: 1 person  nursing sciences
Project web site:

4. Interoperability in Medicine
Petra Knaup
Institute of Medical Biometry and Informatics
University of Heidelberg

5. Interoperability in Medicine
technical interoperability
 physical transmission
semantic interoperability
 unambiguous meaning for sender and receiver
process interoperability
 Integration of systems into work processes
there are further classifications and terms, e.g. procedural, social, organisational, user interoperability…
HL7 Interoperability Work Group. Coming To Terms - Scoping Interoperability for Health Care. 2007; Available from:
Project web site:

6. Introduction to openEHR and
Modelling Clinical Guidelines for Decision Support with openEHR
Blanca Flores
Institute of Medical Biometry and Informatics
Section Medical Informatics

7. Introduction to openEHR
openEHR is an open specification for a health information model
Aims:
Specifications to turn health data from the physical form into electronic form 
Ensure universal interoperability among all forms of electronic data.
Primary focus is electronic health records (EHR) and related systems.
Two level modelling
Reference information model: how health data is represented in a patient record
Archetype object model: how clinical content definitions are represented in the form or archetypes and templates
Archetypes: a data specification for a single clinical concept
Templates: an aggregation of archetypes to carry out a particular clinical purpose.
Modelling tools:
Clinical Knowledge Manager, Archetype Editor, Template Designer, Guideline Definition Language
Project web site:

8. Modelling Clinical Guidelines with openEHR
Clinical practice guidelines: Systematically developed statements to assist clinical and patient decisions about appropriate health care for specific clinical circumstances
Decision support is necessary in different clinical contexts
openEHR provides flexibility and interoperability for the use of health data in decision support systems
CPG can be modelled with archetypes and the Guideline Definition Language
Clinical concepts can be mapped to existing and new openEHR archetypes
Examples of clinical applications:
Lynch Syndrome
Stroke
Multiple Myeloma
Project web site:

9. Radiology information systems (RIS)
and Picture Archiving and Communication Systems (PACS)
Dr. Urs Eisenmann
Institute of Medical Biometry and Informatics
University of Heidelberg

10. Project web site: www.ph-elim.net
RIS and PACS
Definitions
Workflow in the Radiology Department
PACS Components
Legal Aspects
DICOM Fundamentals
DICOM Services
Image Processing and PACS
image: Rainer Sturm / pixelio.de
Project web site:

11. Hospital Information Systems (HIS)
Max Seitz, Petra Knaup
Institute of Medical Biometry and Informatics
University of Heidelberg

12. Hospital Informations Systems (HIS)
support the functions of a hospital by recording and providing information  good information logistics
support achievement of hospital goals taking into account cost effectiveness and quality
contain a variety of application systems, which are integrated and communicate with each other
complexity and heterogeneity of modern HIS can only be mastered by systematic information management.
Project web site:

13. Project web site: www.ph-elim.net
HL7 standards to improve interoperability
Resource Oriented Architectures (ROA)
Implementation guideline
Practical examples
In FHIR everything is on resources and linking resources
Project web site:

14. Clinical registries and Technical Solutions
Chris: Teaching Experience MTA, Course in Chile; Matthias: medical students, PhD students
Christian Haux, Dr. Matthias Ganzinger
Institute of Medical Biometry and Informatics
University of Heidelberg

15. Clinical Registries and Technical Solutions
Introduction to clinical registries
Structured data collection
Databases
EDC systems
Data integration with Talend Open Studio (TOS)
Hands-on lab for
Electronic data capture for registries with REDCap
Management of data in relational databases
Extract-Transform-Load processes with TOS
Obere 4 sind von Chris die unteren von Matthias
Project web site: