130 likes | 225 Views
NC HIE Strategy Technical Infrastructure Work Group agenda Thursday , December 03, 2009 10:00 am -12:00 PM 1100 Navaho Drive Raleigh 1-866-427-0083 Room #: *8041709* (don’t forget the asterisks before and after the room #). Today’s Objectives Arlo Jennings, Datalink
E N D
NC HIE StrategyTechnical Infrastructure Work GroupagendaThursday, December 03, 200910:00 am -12:00 PM1100 Navaho DriveRaleigh1-866-427-0083Room #: *8041709* (don’t forget the asterisks before and after the room #) Today’s Objectives Arlo Jennings, Datalink Review of HIT Collaborative Decision Points Vandana Shah, HWTF Work Group Deliverables Arlo Jennings, Datalink Deliverable Dependencies Melanie Allison, HWTF NC HIE Challenges Melanie Allison, HWTF NC HIE Strategy Submitted to ONC Arlo Jennings, Datalink & Melanie Allison, HWTF Role of Technical Infrastructure Work Group Arlo Jennings, Datalink & Melanie Allison, HWTF
Today’s Objectives • Discuss dependencies of Technical Workgroup Deliverables on Community HIE Deliverables • Functional requirements • Review architecture design proposed in Strategic Plan submitted to ONC on October 16th • Shared Services Environment • Service Oriented Architecture • Discuss role of Technical Infrastructure Work Group • Working from the same “playbook” • Service Design Process
Review: Technical Infrastructure Work Group Deliverables Deliverable One: • Define HIE Services & functional requirements • Core services • Additional services Deliverable Two: • Deployment Roadmap • What is being developed for whom? • How and when will it be deployed?
Deliverable Dependency on Community HIE Work Group Deliverables • Community HIE Work Group Status: • In process of defining NC HIE services at high level of abstraction • Exploring “tiered approach”: functional requirements of existing RHIO vs. new RHIO • Community HIE Work Group Status: • Consensus on RHIO vs. CHIO • Consensus on Defining a region based-HIE (RHIO) & Domain-based HIE • Consensus on recognition of 3 RHIOs in NC & leveraging CCNC for organizing/convening other potential RHIO initiatives
NC HIE Challenges • Limited Funding: $12.9M • HIE Capacity Needs: CMS/Supporting MU Requirements & building capacity in other sectors • Currently working in vacuum: MU final ruling due in December 2009 & could be delayed until Q1 2010 • Varying technical and resource capabilities across healthcare organizations • Variability in HIE value propositions across stakeholders • Privacy Issues: Delicate balance of protecting a patient’s privacy & allowing access to needed clinical information • Non-defined consent management strategy • Sustaining HIE over time post ONC funding
BUILDING HIE SERVICE AND E.H.R. CAPABILITIES SIMULTANEOUSLY TO RAPIDLY EXPAND CAPACITY
Role of Technical Infrastructure Workgroup • Tight alignment with Community HIE Work • NC HIE adoption of HIE terms/concepts • Working from the same “playbook” • Fundamentals of SOA • Basic Terms & Concepts/Architecture Fundamentals • Architecture of Service-Orientation • SOA Design Pattern • Fundamentals • Pattern Notation & Profiles • Service Inventory Design Patterns • Service Design Patterns • Service Implementation Patterns • Service Composition Design Patterns • Service Design Process • Creation of Service Design Team: Developing service inventory functional requirements