30 likes | 187 Views
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.
E N D
An Overview of Contracts to Develop an NHIN Nationwide Health Information Network Architecture PrototypeThe Northrop Grumman ConsortiumRobert M. Cothren, PhDChief Scientist, Health SolutionsNorthrop 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.
RHIO / SNO eg, Santa Cruz,VHA via FHIE Portal eg, PHR,NHIN Portal EHR eg, DoD,Cleveland Principals of Our NHIN Architecture • 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: • Canonical Data Model Translation • Data Location • Message Routing • Security DataSources eg, meds, labs, public health, prescribing, payers, etc. NHINGateway NHINGateway NHINGateway CanonicalData Model • (Optional)NHIN Services • Data Translation • Data Location • Message Routing • Security
Exchanges We Support Biosurveillance Data anonymized demographics, lab / radiology orders & results, resource utilization Entity public health agencies Consumer Empowerment Data demographics, eligibility, basic history & med history Entity providers & consumers (PHRs) EHR Interoperability Data lab results, historical labs Entity provider 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. Where We Are and Where We’re Going