1 / 26

i-focus process and achievements to date

i-focus process and achievements to date. 3 June 2013 end Year 1. i-focus Year 1 Review. The Interoperability Challenge i-focus Process Prioritisation Requirements Gathering Profiles Compliance. The Interoperability Challenge. ?. Public Policy. ?. Human behaviours. ?.

raven-simmons
Download Presentation

i-focus process and achievements to date

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. i-focus process and achievements to date 3 June 2013 end Year 1

  2. i-focus Year 1 Review • The Interoperability Challenge • i-focus Process • Prioritisation • Requirements Gathering • Profiles • Compliance

  3. The Interoperability Challenge ? • Public Policy ? • Human behaviours ? • Legacy systems Interoperability ? • Business interests • Institutional behaviours Standards all pulling in their own directions usually AWAY FROM interoperability ? ? Not just about technology or standards

  4. The Interoperability Challenge • Public Policy • Legacy systems • Human behaviours I Interoperability Standards • Business interests • Institutional behaviours these elements need to be turned around

  5. Interoperability ?

  6. Interoperability Crime Investigation Standards & Technology Service Value Business Models Interoperability • Means • Motive • Opportunity Advanced Digital Institute

  7. Advanced Digital Institute Interoperability components Motive Means New workflows Technical Standards Service Benefit I Technology NewServices NewProducts Clinical Benefit Connectivity Business value Market growth Economic value Opportunity

  8. The i-focus Process • The Interoperability Challenge • i-focus Process • Prioritisation • Requirements Gathering • Profiles • Compliance

  9. i-Focus- supporting interoperability across dallas More Independent Advanced Digital Institute

  10. Prioritisation intendedi-Focus / i3i work flow Stakeholder Mapping & User Scenarios Stakeholder Requirements Top-level Technical Requirements Workshop and consultation with experts Technical Working Group Technical Working Group Technical Working Group Technical Working Group Workshop Workshop Workshop Workshop profile profile profile profile

  11. Prioritisation actuali-Focus / i3i work flow Stakeholder Mapping & User Scenarios Stakeholder Requirements Top-level Technical Requirements Workshop and consultation with experts Technical Consultation(s) Technical Consultation(s) Technical Consultation(s) Technical Consultation(s) Technical Consultation(s) Architecture profile profile profile profile

  12. Details of progress per phase Q1 Q2 Q3 Q4 Q5 dallas Start Year 1 priorities agreed with communities Community presentation of profile requirements Interoperability conference 21-22 November 2012 Common solution architectures and Profiles published Compliance reports published NOW Year 2 priorities agreed with communities 2012 2013

  13. Q1 Prioritisation Phase – Year 1 Summary • Engagement with the four dallas Communities in four stages: • 1) Bid documents analysed • Understanding of aims and objectives • 2) Engagement meetings • Agreements to collaborate • 3) “Theme” discussions held • Exploration of the main aims and objectives of each Community • Identification of areas of interest and importance • 4) Prioritisation • Prioritisation consultation began with the results of the above scored against a set of values for the purposes of prioritising the work of the first year of i-focus.

  14. Cross Programme Interoperability • Approach to profiling

  15. Results so far • Notes: • Opportunity still open for further input, until next week; decisions by end Sept. • Final decision will not be enforced by these results but supported by them • Final decision may group adjacent areas • Actual Interoperability Profiles will be developed within these areas, but may be more specific in nature

  16. Q2 Requirements Phase – Year 1 Summary • Engagement with the four dallas Communities in Three stages: • Communication of Prioritisation results • Core Team Meetings • Development of User Scenarios for i-focus • Development of Stakeholder Mapping • 2) Heartbeat Meetings • Sharing of i-focus User Scenarios and Stakeholder Mapping • Gathering of Community User Scenarios and feedback • 3) Community Interviews (in conjunction with i3i) • On each of the priority areas, gathering Community views • 4) Requirements • Based on all inputs, generation of High Level Stakeholder Requirements • Validation at the Interoperability Conference in Leeds

  17. Q3 Profile Phase – Year 1 Summary • Generation of dallas Reference Architecture • As recommended by Expert Panel • Developed in Core Team and reviewed with community architects • Core Team Meetings • Research of Profile technical background • Expert Consultations • In each Profile area, experts identified to provide considered views • Face to face discussions with experts • Drafting of profiles • One document per Profile • Reviewed in Core Team and with relevant experts • Publication of Profiles

  18. dallas interoperability profiles • The implications of the Medical Devices Directive for Consumer Devices • Multiplatform Service Delivery • The dallas Framework for Identity and Consent • Connection of Personal Health Records to statutory systems • dallas Reference Architecture (dRA) - a framework for discussion of vertical and horizontal interoperability within dallas Advanced Digital Institute

  19. dallas Reference Architecture http://architecture.ifocus-dallas.com dallas User Component dallas User Component Other Online Resource dallas User Component dallas Interoperability Layer dallas Service Component Component Authentication Service User Authentication Service User Preferences Service dallas Service Component dallas Service Component

  20. Consumer Devices and the Medical Devices Directive mobile device 135/95  display App measurement device Person-HeldRecord 135/95 channel channel Bluetooth egWiFi/ADSL/IP Colour changes according either to user-defined thresholds, or according to thresholds hard-coded or automatically-defined within App eg BP cuff, blood glucose monitor eg smartphone Software “App” or “Service” Database system: storage of data Channel: transport of data Consumer computing device What is, or is not, a Medical Device? Medical device with data generating or clinical diagnostic value

  21. Multiplatform Service Delivery Tablets Smartphones Television PC Set-top box Featurephones SMS Voice-only phones Games Consoles Challenges: delivering services to a wide range of devices for accessibility, user preference, legacy, scale, economics of multi-platform development Topics: Web vs native applicationsHTML5 Development Frameworks Language Individualisation Maintenance Choices of platform Web Applications

  22. PHR connectivity to statutory systems • Key topics: • Value of connecting PHR to statutory services • Impact on Workflows (+ve and –ve) • Information Governance

  23. Framework for Identity & Consent

  24. Interoperability profiles: http://profiles.ifocus-dallas.com Advanced Digital Institute

  25. Q4 Compliance Phase – Year 1 Summary • Communities and i-focus not mature enough this year for formal Compliance Audits • Instead: alignment reviews • Alignment Review • With each Community, one or two face-to-face review meetings • Aimed to compare each Profile area with actual Community plans and progress • Looking for common ground • Looking for good practice to propagate around dallas • Looking for clear gaps or shortcomings in Community approaches • One report generated per Community (confidential unless agreed with Community Lead). • External Body networking • crossover into i3i

More Related