Ethnography and Evaluation Dr. K. Neil Jenkings DuDEHR.

Slides:



Advertisements
Similar presentations
Nursing Diagnosis: Definition
Advertisements

Med Ed : Making sense of medication. Todays presentation Background and context Resource development Description Using Med Ed Training Evaluation Next.
Primary Care College – Tees Valley & Durham Teaching PCTs ; All you ever wanted to know….. Stephanie Carson Head of College.
Supporting further and higher education Future Activities Sarah Knight Helen Beetham.
©2003 Sowerby Centre for Health Informatics at Newcastle Problems Encountered in Electronic Health Record Research K. Neil Jenkings Sowerby Centre for.
Leadership in Clinical Practice Quality of Care Rounds Improving Quality Programme and Ward Accreditations Deborah Carter Deputy Director of Nursing (Quality)
Knowledge Management at the Gordon – Staff Portal Project Presented by Deirdre Carmichael 12 September 2008.
Introduction to Monitoring and Evaluation
Project Rationale Dr Nick Booth Aims of the project Create a grounded framework for a federated information service for the NHS in England Create an.
Where to from here in Assessment in Medical Education? Dr Heather Alexander 5 November 2010.
Building the capacity of Community Health Centers to collect occupational health data Letitia Davis, ScD, EdM Occupational Health Surveillance Program.
PHASE 1 Facilitating discussion on treatment preferences and advance care planning in cancer patients using the vignette technique Funding: Department.
SWE Introduction to Software Engineering
1 THE HEALTH iNNOVATOR An Integrated Care Record Service The Durham & Darlington Approach The Simulator.
Advances research methods and proposal writing Ronan Fitzpatrick School of Computing, Dublin Institute of Technology. September 2008.
The ISABEL user survey Dr Jim Briggs Dr Tineke Fitch Healthcare Computing Group University of Portsmouth
ISABEL: the use of a web-based clinical support system Dr Jim Briggs Dr Tineke Fitch University of Portsmouth, UK
A Student Guide to Object- Orientated Development Chapter 2 Requirements for the Wheels case study system.
Copyright © 2014 Wolters Kluwer Health | Lippincott Williams & Wilkins Chapter 1 Overview of Nursing Process, Clinical Reasoning, and Nursing Practice.
socio-organizational issues and stakeholder requirements
A professional development tool for experiential placement students *graduated = stepped, incremental Pharmacy Competencies Graduated* Descriptors :
Tutorial Introduction Fidelity NTSConnect is an innovative Web-based software solution designed for use by customers of Fidelity National Title Insurance.
Joy Hamerman Matsumoto.  St Jude Medical Cardiac Rhythm Management Division manufactures implantable cardiac devices ◦ Pacemakers ◦ Implanted defibrillators.
Making patients’ views count Frequent Feedback Service Regula Dent Marketing Manager Picker Institute 21 April 2009.
Data Analysis in the Water Industry: A Good-Practice Guide with application to SW Deborah Gee, Efthalia Anagnostou Water Statistics User Group - Scottish.
Use of OCAN in Crisis Intervention Webinar October, 2014.
ICT 1 Towards an Integrated Approach to Access Control to Health Information Presented by: Inger Anne Tøndel SINTEF Co-authors: Per Håkon Meland SINTEF.
Group HR Sukanya Patwardhan – 12th December 2012 Welcome Good Morning Good Afternoon.
Advanced Topics in Requirement Engineering. Requirements Elicitation Elicit means to gather, acquire, extract, and obtain, etc. Requirements elicitation.
Medical Audit.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Chapter 5: Requirement Engineering Process Omar Meqdadi SE 2730 Lecture 5 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.
Component 4: Introduction to Information and Computer Science Unit 2: Internet and the World Wide Web 1 Component 4/Unit 2Health IT Workforce Curriculum.
System Analysis and Design Dr. Taysir Hassan Abdel Hamid Lecture 5: Analysis Chapter 3: Requirements Determination November 10, 2013.
Steps for Success in EHR Planning Bill French, VP eHealth Strategies Wisconsin Office of Rural Health HIT Implementation Workshop Stevens Point, WI August.
PUBLIC RELATIONS RESEARCH AND PLANNING
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 7 Slide 1 Requirements Engineering Processes.
RIDE ConsortiumRIDE Workshop, December 8, 2006, Brussels 1 The RIDE Roadmap Methodology and the Current Progress Prof. Dr. Asuman Dogac, Turkey Dr. Jos.
1 Women Entrepreneurs in Rural Tourism Evaluation Indicators Bristol, November 2010 RG EVANS ASSOCIATES November 2010.
 What is Public Relations Research? Research is important and thus it is the key to a successful Public Relations programme. Research assists in gathering.
Technology Use Plan Presented by: Bob Santi. Rationale A technology plan is a current guideline for the appropriate and effective use of technology a.
Lecture 7: Requirements Engineering
Mrs. V. Kirkley, RN, MEd..  Medical Records Technicians work in all types of medical facilities from local hospitals, physicians offices, clinics and.
© 2001 Change Function Ltd USER ACCEPTANCE TESTING Is user acceptance testing of technology and / or processes a task within the project? If ‘Yes’: Will.
Opportunistically discovering usability requirements for a clinical handover system David Kaufmann a, David Parry b, Victoria Carlsen c, Philip Carter.
Action Research Action Research Juma Lungo University of Oslo 29 th December
The Nursing Process ASSESSMENT. Nursing Process Dynamic, ongoing Facilitates delivery of organized plan of nursing care Involves 5 parts –Assessment –Diagnosis.
The educational supervisor’s interview Preparing the ground for the educational supervisors report.
Inf-Qual November Elisabeth Jakobsen. “All I want is a system that works” Evaluation of the health information system in Cape Town, South Africa.
Strategic Research. 6-2 Chapter Outline I.Chapter Key Points II.Research: The Quest for Intelligence and Insight III.The Uses of Research IV.Research.
Project Management Cross lifecycle Activity
Identifying needs and establishing requirements Data gathering for requirements.
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
F UTURE VISION FOR HEALTH INFORMATICS APPLICATIONS.
Care Transitions: Challenges and Opportunities for Medication Reconciliation Kaija Saranto, Professor, PhD, RN, Eija Kivekäs Doctoral –student, MHSc Department.
Requirements Engineering Processes. Syllabus l Definition of Requirement engineering process (REP) l Phases of Requirements Engineering Process: Requirements.
Data gathering (Chapter 7 Interaction Design Text)
Strategic Research Part 2: Planning and Strategy Chapter 6.
CCS Information for Mental Health John Turp Clinical Systems Project Manager.
Name of presentation Improving health in Greenwich: Linking integrated health & social care with primary care.
The Electronic Health Record Lab: A Comprehensive Educational Intervention for Outpatient Electronic Records Bruce Britton M.D. Cy Cedar MS4 Christine.
Analyzing Ethnographic Data UrbP 298. Beyond interviews What are the different kinds of qualitative data? Interviews (unstructured to highly structured)
DEVELOPING A PERSONALLY CONTROLLED HEALTH RECORD (PCHR) USING MICROSOFT VISUAL C# SESSION 9 SUMMARY.
Recording Care – The Challenge PACE Pilot January 2016.
Systems Analysis Lecture 5 Requirements Investigation and Analysis 1 BTEC HNC Systems Support Castle College 2007/8.
Action Research Action Research Juma Lungo PhD Candidate University of Oslo 15 th September
Title of the Change Project
EKT 421 SOFTWARE ENGINEERING
Evaluating the Use of Patient Experience Data to Improve the Quality of Inpatient Mental Health Care (EURIPIDES) Professor Scott Weich.
Presentation transcript:

Ethnography and Evaluation Dr. K. Neil Jenkings DuDEHR

Ethnography and Systems Design in DuDEHR Project Workplace studies and socio-technics based approach to technology design “Optimal utilization of IT applications… is dependant on the meticulous interrelation of the system’s functioning with the skilled and pragmatically orientated work of health care professionals.” (Berg 1999) Non-participant observation of situated workplace activities Descriptions of practices, vignettes and informal interviews The communication of this information to the rest of the team – facilitating architectural modelling and planning grounded in situated practices User centred design – problem of end users lack of knowledge of what would constitute an EHR Development of animators (based upon field work & future vision)

Evaluation of Animators Pilot the usefulness of both the animators (non- technical and technical versions) for the elicitation of Durham & Darlington EHR design information Collect information for the iterative development of the animator and technical animator Collect procurement specific information Continuous evaluation as part of the design process Involve healthcare professionals in the research process

Evaluation Methodology - Animator Animator target Audience - general Animator - Focus groups –11 Groups size of 1-16 (Various Healthcare Professional) –Audio recordings of discussions –Content analysis of recordings (NVivo) –Questionnaire

Structure of focus groups Baseline discussion Presentation of the Animator Post Presentation Discussion – Questionnaires Post Presentation Discussion resulted in rich data (see WP5.2 document on CD)

Animator Results Animator Questionnaire –Overwhelmingly Positive –Good Mean Score All Questions. –Little Deviation Across Respondents. Animator Focus Groups –Positive Response to Animator –Provoked Discussion (Animated Audience) –Engendered Further Data for Iterative Development

Evaluation Methodology – Technical Animator Target Audience – IM&T Technical Animator – Workshop –Recording of following discussion –Questionnaire – 29 questions with comments boxes under each question for additional comments –17 Responding Attendees (IM&T professionals working in D&D and Tees Valley)

Technical Animator Results Overall Positive Response Positive Evaluation of Production Quality Positive view of Durham & Darlington EHR vision Non-committal about early versions’ use in procurement Positive response for liaison with users N.B. Iterative design process has allowed these issues to be addressed – as seen in version shown today. Detailed findings (see WP5.2 document on CD)

Ethnographic Research Primary Care – Various Types –Urban, Rural, Single Practitioner, Multi-Practitioner, Dispensing and Non-Dispensing Secondary Care – Various Departments –A&E, CCU, Emergency Ward, Medical Records, Out- patients etc. Mental Health and Social Services –Community Mental Health Teams

General Findings Healthcare professionals work is interdependent Activities centre around treatment and the production, recording, use, filing and transmission of information Information recorded and used electronically and on paper based systems with varying overlap Different access to information by various personnel Informal and formal work practices need supporting Importance of interpersonal communication

Communicating Ethnography The project has collected detailed information on actual working practices and processes, including vignettes, collections of screen shots from computer software, copies of paper documentation, information faxed and the use of telecommunications at various not just systems information This information is not usually available to architectural modellers, system designers and change management personnel Used Software to organise and make them useful Demo of the software

To Conclude Ethnographic investigations provide key information regarding existing processes and practices Animators show future scenarios grounded in ethnographic research Animators evaluated: successful in gathering information from healthcare professionals; getting user involvement; craeting a sense of ownership and facilitating user centred design The use of control to embed information, ethnographic description, focus group reports, system screen shots and copies of paper documents into process models allowing rich descriptions of processes Rich description allowing verification of processes and practices with users, access to this information by design teams and change managers to check designs against user needs and organisational change requirements The procurement of well-designed user orientated systems