“Designing” an IHIA Health Information Systems; Integration and Interoperability.

Slides:



Advertisements
Similar presentations
An Essential Component of Health Systems Strengthening Presented on: May 23, 2011 Akiko Maeda Health, Nutrition & Population Network The World Bank.
Advertisements

Intelligence Step 5 - Capacity Analysis Capacity Analysis Without capacity, the most innovative and brilliant interventions will not be implemented, wont.
Supporting National e-Health Roadmaps WHO-ITU-WB joint effort WSIS C7 e-Health Facilitation Meeting 13 th May 2010 Hani Eskandar ICT Applications, ITU.
Quality Education for a Healthier Scotland Getting Knowledge into Action for Person-Centred Care Bibliotherapy in NHSScotland 23 rd September 2013.
Health Information Network The Challenges & Building the Foundation Delivering a Healthy WA Richard McFadden, CIO.
DISTRICT HEALTH INFORMATION MANAGEMENT
HealthConnect: Sharing information to improve health care 29 July 2005 Dr Brian Richards National Director, e-Health Implementation Department of Health.
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
Health Informatics Series
What is H(M)IS?. Purpose of HIS “is to produce relevant information that health system stakeholders can use for making transparent and evidence-based.
Developing a target ‘future state’ in social care informatics Andrew Fenton DH.
Strengthening Public Finance Management Through Computerization of Procurement Management System High Level Forum on Procurement Reforms in Africa Tunisia.
MANAGING INFORMATION SYSTEM IN HIS IN DEVELOPING COUNTRIES.
Software Based Systems for ART Program and Patient Monitoring.
“Designing” an IHIA Health Information Systems; Integration and Scaling.
DHIS2 Interoperability
MHealth. 2 Aggregate Clinical Use Patient Centered Program tracking Medical Sensors Diagnostic tool Smartphone Routine reporting SMS-reminders Treatment.
Integrated Health Information Architecture (IHIA).
1 There are a number of organization designs, including many combinations or hybrids of models. Seven designs are shown below: Process Centered Front End.
ICAP Tanzania’s Experiences Implementing an Aggregate Database: District Health Information System (DHIS) Joshua Chale, Data Manager July 28, 2010.
Support Systems for Indigenous Primary Health Care Services Alister Thorpe, Kate Silburn #, Ian Anderson 23 March 2010 # La Trobe University.
© 2003 East Collaborative e ast COLLABORATIVE ® eC SoftwareProducts TrackeCHealth.
Race To The Top (RttT) MSDE Division of Accountability and Assessment Data Systems (DAADS) Maryland Public Schools: #1 in the Nation Three Years in a Row.
INF5761 Health Management Information Systems. What this course is about: HMIS 2 decision making (the use) statistics & aggregate data ( the evidence)
Nationally Significant Databases and Collections Providers’ Group Emma Kelly Environmental Information Advisor Environmental Monitoring and Reporting Team.
This material was developed by Duke University, funded by the Department of Health and Human Services, Office of the National Coordinator for Health Information.
Jara Project: the interoperability in the healthcare enterprise. Juan P. Alejo González Subdirector Sistemas de Información - CIO Servicio Extremeño de.
Uganda Health Information Strategy Eddie Mukooyo, MD, MSc Assistant Commissioner Health Services Dublin, Ireland 13 th September 2010.
HIS country experiences. Overview Cuba Botswana Tajikistan Sierra Leone West Africa Others… Evolution of the international HIS scene, and HISP.
Dr. Mwendwa Eunice Mwenesi, Tanzania Ministry of Health and Social Welfare, Presentation to the mHealth Working Group, Washington DC, December 1 st, 2011.
Seite 1 Bringing data into common place through use of appropriate database software Muhammad Abdul Hannan Khan Senior Advisor HMIS GIZ Health.
W HAT IS I NTEROPERABILITY ? ( AND HOW DO WE MEASURE IT ?) INSPIRE Conference 2011 Edinburgh, UK.
1 Incorporating Data Mining Applications into Clinical Guidelines Reza Sherafat Dr. Kamran Sartipi Department of Computing and Software McMaster University,
The Practical Challenges of Implementing a Terminology on a National Scale Professor Martin Severs.
Andrew Howard Chief Executive OfficerClinical Advisor Mukesh Haikerwal.
Walsall Health Economy “ Using LIVE data to improve the patient journey ” Walsall Health Partnership Improving Care with e- technology “Making IT Real”
Promoting excellence in social security Building on sector wide commonalities to enhance the benefits of Information.
Enterprise Solutions Chapter 10 – Enterprise Content Management.
Tanzania Health Facility Registry
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Networking and Health Information Exchange Unit 6a EHR Functional Model Standards.
Providing web services to mobile users: The architecture design of an m-service portal Minder Chen - Dongsong Zhang - Lina Zhou Presented by: Juan M. Cubillos.
Some Political Struggles HISP is engaged with Sundeep Sahay.
Shaun Grannis, MD, MS, FAAFP FACMI Biomedical Informatics Scientist Regenstrief Institute / Indiana University The Impact of Interoperability / HIE to.
CDA Overview HL7 CDA IHE Meeting, February 5, 2002 Slides from Liora Alschuler, alschuler.spinosa Co-chair HL7.
EHealth Development Vision. eHealth ojectives Healthcare systems and network focused on the patient: Not patient runs between institutions but the patients’
Integration of HRH in MNCH and HIV services Director of Human resources development.
1 CDC Health Information Exchange (HIE) Accelerating State-wide Public Health Situational Awareness in New York Through Health Information Exchanges August.
District hospitals provide a significant proportion of health services in a district District hospitals consume a high % of the district health budget.
Adult Social Care informatics. 2 Context for Informatics in ASC Paucity of data collected – compared with health – 9 v 160 plus HES plus GPES plus Medicines.
Health Management Information Systems Unit 3 Electronic Health Records Component 6/Unit31 Health IT Workforce Curriculum Version 1.0/Fall 2010.
Burden of Disease Research Unit (BOD) Towards a National Procedure Coding Standard for South Africa Lyn Hanmer Health Informatics R&D Co-ordination (HIRD)
1 The information contained in this presentation is based on proposed and working documents. Health Information Exchange Interoperability Minnesota Department.
Improving health for the underserved
New WHO Guidelines on Person centred monitoring
eHealth Standards and Profiles in Action for Europe and Beyond
Unit 5 Systems Integration and Interoperability
Data Summit, Johannesburg
Guidelines on Integrated Economic Statistics
Electronic Health Information Systems
Enhancement of study programs in Public Health Law, Health
Balanced Scorecards in
Health Information Exchange Interoperability
Guidelines on Integrated Economic Statistics
Introduction to the PRISM Framework
Getting Knowledge into Action for Person-Centred Care
Guidelines on Integrated Economic Statistics
Managing International Information Systems
University of Washington, Autumn 2018
University of Washington, Autumn 2018
Presentation transcript:

“Designing” an IHIA Health Information Systems; Integration and Interoperability

Conceptualizing Architecture Architectures are not end-solutions, but approaches to manage complexity (e.g. city planning / regulation) -Tension between short term solution and long term goal -HIS architectures provide road maps or compass for “good design” 3 Standards Prerequisite for integration and interoperability. Without shared “understanding” and meaning, no interoperability or integration

IHIA/HIS: Three Challenges Fragmentation of data sources –Different sub-systems, owned by different stakeholders Data-led, not action-led –Focus is on collecting and reporting data, rather than using if for decision making Centralization vs decentralization –Difficult to strike a balance (social & technical) 4

An example of fragmentation: Mozambique 5

Some social causes of fragmentation -Statisticians/managers (data people) vs health workers (action people) -Medical (point of care) vs Public health (aggregate) -Proprietary systems vs Open source -Quick fixes vs Long term Strategy -Isolated systems vs IHIA -Donor Politics vs National Strategy

Statisticians vs Public Health “data represents an event” More is better vs Minimum Data Set & information pyramid Treatment of outliers Upward reporting bias (performance)

Medical vs public health Medical focus on patient record systems Disease based coding & classification – ICD10 Isolated (e.g. Excel) systems that do not talk with others Doctors as informaticians not as users Systems of limited scope and scale

Quick fixes vs long term strategy Ideal: long term, build local capacity / sustainability / maintainability – linked with education process BUT Vendors promise short term utopias Government officials typically short term – want to be remembered for reforms Aid projects often short term – pilots Hardware/software emphasized, not people and knowledge

Donor politics vs national HMIS restructuring -Donors promoting own systems -Expatriates/experts -Not adopting integrated health systems framework HISP/DHIS2 from activists to regulators?

HIS/HIA: Integration –Involves data, organizational behavior, workforce, and policies –Must be sustained over time through routine processes, and is not a one off technical process Example (DHIS2) District HIS designed to enable collection, collation, and analysis of HMIS & disease surveillance data across different subsystems but it does not have to be so… “The process of making multiple subsystems appear as one single system”

Some benefits of integration Value added to data –New indicators possible –Enables cross-comparison –Ease of access Cost efficient –Professionalizing information management (e.g. cloud computing) –Pooling of resources (financial, human) –Economies of scale (training, hardware, software) –Centralized supporting activities (technical maintenance) –Decentralized core activities (public health decision making) Example Integrated Human Resource & Health service data

14 Increasing differences between views Three Levels of Standards --Organisational/ Political /pragmatic --Semantic --Syntactic /technical Compared to a telephone conversation Shared interests? Interested in talking? Shared language and shared understanding? Compatible telephones & networks? Interoperability and integration require standards For each level; “solutions” based on solutions at level below, and rely on agreement at level above SDMX-HD, etc. Shared / agreed indicators & meta data Programs / donors /agencies Agree to standardisation Unique id. Standardisation may be seen as going on at three levels of increasing complexity

Organisational /political level of integration (information needs & usage) Horizontal integration: Information from across sectors & health programs available at “one point” Vertical Integration: “Seamless” flow of information from peripheral to central levels, from patient encounters in clinics to national M&E Software applications & Information Systems Horizontal integration: Data warehouse, such as DHIS, integrating & managing data from different health programs and sectors Vertical Integration: Extracting aggregate data from Human Resource system, and patient record systems into one data warehouse (e.g. DHIS2) Data exchange, interoperability & standardisation Horizontal integration: Shared data & indicator standards prerequisite for sharing data across health programs & sectors, whether from paper or computer sources. SDMX-HD data exchange format enable transfer of indicator definitions and dataSDMX-HD Vertical Integration: Shared data standards also prerequisite for aggregating from individual human resource records in iHRIS to data according to standard loaded in DHIS using SDMX-HDSDMX-HD

The application level of IHIA 16

Data Interoperability Data Interoperability / syntactic/ technical –Essential component to achieve integration –Interoperability; standardized data definitions for data exchange among sub systems Example –Shared data definitions among data collections tools (paper or software) across different subsystems, and standards for exchanging these data (e.g. XML, HL7, SDMX-HD)HL7SDMX-HD Shared data standards and indicators, are the primary building block of the IHIA

Four (uneven) processes of change in the IHIA From paper to computer / mobile phone From stand-alone to networked computers From paper registers to electronic patient records From offline to online (web-based HMIS) 18 Scaling in uneven contexts: Do we need to cover all forms? Do we need to cover all reproting units? If not, useless?

Centralization, decentralization and hybrid models –Who makes decisions? –Who controls budget? –Where does the data reside? (political/technical/managerial) –Does implementation start at top, or bottom? These questions have implications on: –User involvement (not always empowering) –Use of information for decision making