1. An Overview of Contracts to Develop an NHIN Nationwide Health Information Network Architecture Prototype The Northrop Grumman Consortium Robert M. Cothren, PhD Chief Scientist, Health Solutions Northrop Grumman This presentation discusses an NHIN Architecture Prototype project made possible by a contract from the Office of the National Coordinator for Health Information Technology (ONC), DHHS. The content is solely the responsibility of the authors and does not necessarily represent the official view of ONC.

2. © 2006 NORTHROP GRUMMAN CORPORATION 1 Our Fundamental Goals  Leverage success at the local level & “lower the barrier” for entry.  Develop / enforce nationwide standards to facilitate interoperability. Architectural Solution: Gateways  Each entity connects through a gateway servicing one or more entities.  Gateways connect to each other using nationwide standards.  Gateways provide essential services needed for interoperability: 1)Canonical Data Model Translation 2)Data Location 3)Message Routing 4)Security Principals of Our NHIN Architecture (Optional) NHIN Services 1)Data Translation 2)Data Location 3)Message Routing 4)Security NHIN Gateway RHIO / SNO eg, Santa Cruz, VHA via FHIE EHR eg, DoD, Cleveland Portal eg, PHR, NHIN Portal Data Sources eg, meds, labs, public health, prescribing, payers, etc. NHIN Gateway Canonical Data Model

3. © 2006 NORTHROP GRUMMAN CORPORATION 2 Where We Are and Where We’re Going Exchanges We Support Biosurveillance Dataanonymized demographics, lab / radiology orders & results, resource utilization Entitypublic health agencies Consumer Empowerment Datademographics, eligibility, basic history & med history Entityproviders & consumers (PHRs) EHR Interoperability Datalab results, historical labs Entityprovider to provider (EHRs) Mid-Point Progress Establishing Gateway Services  Exchanging information between 2 of 3 Health Care Markets.  Obtaining med history from RxHub.  Providing basic PHR exchange functionality. Participating in parallel efforts in standards, requirements, etc. We are not… …obsolescing existing exchanges; …requiring nor replacing RHIOs; …limiting to physician exchanges; or …ignoring need for confidentiality.