The ORCHID project Dr Ian Gaywood, NUH Dr Ira Pande, NUH Professor John Chelsom, City University London.

Slides:



Advertisements
Similar presentations
Connected Health Framework
Advertisements

1 Using Ontologies in Clinical Decision Support Applications Samson W. Tu Stanford Medical Informatics Stanford University.
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.
NMAHP – Readiness for eHealth Heather Strachan NMAHP eHealth Lead eHealth Directorate Scottish Government.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 32 Slide 1 Aspect-oriented Software Development.
Informatics And The New Healthcare System Information Technology Will Provide the Platform for Quality Improvement in Healthcare for the 21 st Century.
Data collection, integration and normalization presented to DIMACS Gil Delgado October 17, 2002.
Organizing Data & Information
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
FREMA: e-Learning Framework Reference Model for Assessment Design Patterns for Wrapping Similar Legacy Systems with Common Service Interfaces Yvonne Howard.
7M822 Software Engineering: System Models 14 September 2009.
Software Issues Derived from Dr. Fawcett’s Slides Phil Pratt-Szeliga Fall 2009.
Course Instructor: Aisha Azeem
Promoting Excellence in Family Medicine Enabling Patients to Access Electronic Health Records Guidance for Health Professionals.
Computer Science 240 Principles of Software Design.
LEVERAGING THE ENTERPRISE INFORMATION ENVIRONMENT Louise Edmonds Senior Manager Information Management ACT Health.
PRD_codes_KS_ ppx. UK Renal SNOMED CT subset incorporating the new ERA-EDTA PRDs and how we can use them in Rare Disease Groups Keith Simpson.
THEORIES, MODELS, AND FRAMEWORKS
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Software Engineering Muhammad Fahad Khan
Software Reuse Prof. Ian Sommerville
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
1 Betsy L. Humphreys, MLS Betsy L. Humphreys, MLS National Library of Medicine National Library of Medicine National Institutes of Health National Institutes.
Object Oriented Programming Development
Executable UML The Models are the Code - Executable UML CS387 Paul Krause.
SWE 316: Software Design and Architecture – Dr. Khalid Aljasser Objectives Lecture 11 : Frameworks SWE 316: Software Design and Architecture  To understand.
Ceg860 (Prasad)L6MR1 Modularity Extendibility Reusability.
Chapter 6: Foundations of Business Intelligence - Databases and Information Management Dr. Andrew P. Ciganek, Ph.D.
©Ian Sommerville 2000 Software Engineering, 6th edition. Slide 1 Component-based development l Building software from reusable components l Objectives.
3rd Country Training, K.Subieta: System Engineering and Databases. Lecture 3, Slide 1 February 20, 2004 Lecture 3: Introduction to Software Analysis and.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse.
Creational Patterns CSE301 University of Sunderland Harry R Erwin, PhD.
Evaluation of routine data sources for ascertainment of hypospadias cases Congenital Anomaly Register for Oxfordshire, Berkshire, and Buckinghamshire (CAROBB)
University of Southern California Center for Systems and Software Engineering Model-Based Software Engineering Supannika Koolmanojwong Spring 2013.
L8 - March 28, 2006copyright Thomas Pole , all rights reserved 1 Lecture 8: Software Asset Management and Text Ch. 5: Software Factories, (Review)
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
System Changes and Interventions: Registry as a Clinical Practice Tool Mike Hindmarsh Improving Chronic Illness Care, a national program of the Robert.
6.1 © 2010 by Prentice Hall 6 Chapter Foundations of Business Intelligence: Databases and Information Management.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 18 Slide 1 Software Reuse.
Database Management Systems (DBMS)
Copyright ©2004 Virtusa Corporation | CONFIDENTIAL Requirement Engineering Virtusa Training Group 2004 Trainer: Ojitha Kumanayaka Duration : 1 hour.
Is the conscientious explicit and judicious use of current best evidence in making decision about the care of the individual patient (Dr. David Sackett)
Software Quality Assurance and Testing Fazal Rehman Shamil.
Guidelines Recommandations. Role Ideal mediator for bridging between research findings and actual clinical practice Ideal tool for professionals, managers,
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
SAGE Nick Beard Vice President, IDX Systems Corp..
Fundamentals of Information Systems, Sixth Edition Chapter 3 Database Systems, Data Centers, and Business Intelligence.
1 Acquisition Automation – Challenges and Pitfalls Breakout Session # E11 Name: Jim Hargrove and Allen Edgar Date: Tuesday, July 31, 2012 Time: 2:30 pm-3:45.
1 Software Requirements Descriptions and specifications of a system.
Chapter 5 – System Modeling Lecture 1 1Chapter 5 System modeling.
Getting the detail right Standardisation and SNOMED CT © Nottingham University Hospitals NHS Trust.
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
Software Reuse ©Ian Sommerville 2006.
The Five Year Forward View (NE Essex) Collaborative:
Chapter 16 – Software Reuse
Synthetic Data Working Group
Automating Profitable Growth™
X-DIS/XBRL Phase 2 Kick-Off
Welcome. Supporting Realistic Medicine through the delivery of a Single National Formulary.
Applying Use Cases (Chapters 25,26)
Informatics 121 Software Design I
Chapter 16 – Software Reuse
Software Requirements
Automating Profitable Growth
Risk Stratification for Care Management
Software Requirements
Realistic Prescribing Pathways
Presentation transcript:

The ORCHID project Dr Ian Gaywood, NUH Dr Ira Pande, NUH Professor John Chelsom, City University London

So much information……so little use Clinical care generates enormous amounts of information which is difficult to use when caring for the individual and impossible to use for any secondary purpose

The origins of ORCHID Better organised information has the potential to provide an enormously valuable resource but must be achieved without additional onerous burden at the clinical coalface The greatest impediment to extended uses of clinical records, including research, is not lack of data. It is lack of useable data It should be possible to organise data in ways which allow any plausible question to be answered

Stratified medicine Treatment decisions in all but the simplest conditions increasingly rely on knowledge of the patients disease phenotype in several domains Current methods of gathering and organising data dont place information in its correct context The relationships among pieces of information are at least as important as the information itself. It is no longer enough to simply name the beast

What clinicians want …. A way of organising data which: –Identifies patient phenotypes to any degree of detail –Produces untainted cohorts –Is multidisciplinary –Can include or exclude individual disease characteristics –Can include or exclude treatment details –Records and assesses outcomes –Can be searched in real time –Maps to existing coding systems

The ORCHID information model The two central tools of ORCHID are hierarchies and core data sets Together they provide a rich data architecture which can be applied to all data sets across all specialties ORCHID hierarchies cross-map to existing coding systems but overcame many of their limitations ORCHID hierarchies can be rapidly amended to reflect changes in knowledge and understanding without compromising the value of existing data Existing data sets can be embedded in ORCHID hierarchies and will inherit the richness of those structures

An ORCHID hierarchy Rheumatoid arthritis Rheumatoid arthritis - seropositive Rheumatoid arthritis - seronegative Rheumatoid arthritis - NOS Inflammatory arthritis Autoimmune disease Bespoke cohort SLE, PBC etc Psoriatic arthropathy Other conditions of interest

An ORCHID hierarchy

Core data sets ORCHID hierarchies place individual diseases, events etc in their correct relationships with other entities They do not capture the finer details of complex diseases which say something about subtype, severity, prognosis, treatment choices Core data sets capture these data items in a searchable form and provide a very detailed patient phenotype Can be either static or dynamic

An ORCHID Core Data Set

ICD-10 and patient phenotyping Requires separate codes for each manifestation Contains misclassifications –Adult Stills disease as type of rheumatoid arthritis Contains detailed codes of no clinical value –M Rheumatoid arthritis of right wrist with involvement of other organs and systems Does not reflect recent developments

SNOMED and patient phenotyping SNOMED contains almost all of the codes required to capture diagnostic data to the required level But…. It also contains a very large number of redundant codes, duplications and non-existent entities Coding detailed phenotypes requires the use of multiple codes – usually one code for each disease manifestation Clinicians should agree a subset of SNOMED with careful moderation of additions and amendments

Implemented using Open Health Informatics principles Open standards Open source software Open systems interfaces Open development processes Builds upon work in the Open Health Informatics research programme at City University Maximises the potential for reuse and wider roll out Implementation

ORCHID Architecture Standards based Ontology driven Clinician led

ORCHID Platform Open source Standards based Enterprise Java No compiled code

Deployment of ORCHID A web based application with a common look and feel across specialties but specialty and disease specific forms and summaries Linked to Trust information systems for automatic download of demographics, laboratory data…. Custom search engine allowing any finding within the ORCHID ontology to be used as a search term Can be deployed in modular form with all modules moderated for consistency allowing easy combining of modules and sharing of data among modules Moderated updates to take account of new knowledge, terminologies and classifications

Uses of ORCHID Routine clinical care Automated HES / SUS reporting Feasibility testing – research ideas, trial design Phenotype pattern analysis Registry data including possibility of cross-registry data sharing Generation of combined primary and secondary care data sets