1 / 11

NHIN Direct Project ONC State HIE Retreat

NHIN Direct Project ONC State HIE Retreat. September 1 st , 2010. What is the NHIN Direct Project?.

selena
Download Presentation

NHIN Direct Project ONC State HIE Retreat

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. NHIN Direct Project ONC State HIE Retreat September 1st, 2010

  2. What is the NHIN Direct Project? A project to create the set ofstandardsand services that with a policy framework enable simple, directed, routed, scalable transport over the Internet to be used for secure and meaningful exchange between known participants in support of meaningful use

  3. NHIN Direct Project • Open, transparent collaborative process, • Includes use of wikis, blogs, open source and open content • http://nhindirect.org • First phase grounded in real-world implementation in 2010 • Follow key rules of HIT Standards Committee Implementation Workgroup

  4. Close to 200 Implementation Group Participants • Alere • Allscripts • American Academy of Family Physicians • Argonne National Laboratory • Atlas Development • Axolotl • CareSpark/MobileMD/Serendipity Health • Cautious Patient • Cerner • Clinical Groupware Collaborative • CSC • eClinicalWorks • EHR Doctors • Emdeon • FEI • GE • Google • Greenway Medical Technologies • Harris Corporation, • High Pine Associates • HLN Consulting • ICA, • Inpriva • Intel • Kryptiq • LabCorp • Massachusetts eHealth Collaborative • MedAllies • Medical University of SC, • Medicity • MedNet • MedPlus/Quest Diagnostics • Microsoft • Mirth Corporation • MOSS • Nationwide Health Information Technology • NIH NCI • NIST • NYC Dept. of Health and Mental Hygiene’s PCIP • Oregon HIE Planning Team • Redwood MedNet • RelayHealth • Secure Exchange Solutions • Siemens • South Carolina SDE • SureScripts • Techsant Technologies • TN State HIE • VA • VisionShare

  5. State Participation • SDE participation from • CA, OR, RI, TN, SC (new) • Other states participate with observer roles • Strong participation from TA team, current and legacy (Noam Artz and Tim Andrews) • HIO participation sub-state from • NY (HIXNY, Hudson Valley) • TN (CareSpark) • CA (Redwood Mednet) • CT pilot has some coordination with CT SDE • Much dialog with individual states

  6. NHIN Direct High-Level Project Plan Aug 2010 Sept 2010 Immediate Next 90 Days Short Term 3 to 9 months Long Term 9 to 36 months Draft Specification Complete Transition to an SDO Ongoing Maintenance Initial Pilot Implementation Expansion of Pilots Wide-Scale Deployment Evaluation for inclusion by NHIN and ONC Endorsement Evaluation by HITSC HITPC Tiger Team Framework and Policy Review Feedback to NHIN Governance Feedback on initial lessons learned Ongoing Review and Feedback Immediate Initiatives Short Term Initiatives Long Term Initiatives

  7. Overview of the Specification • Consistent Health Internet Addressing, based on familiar concepts • E.g., drjones@exchange.sunnyfamilypractice.com • Can manage your own exchange domain, assign to a HISP or HIO, and reassign at a later time • Provides universal cross-HIO addresses and reduces lock-in and interoperability islands. • Two transport models • Universal transport uses secure SMTP + S/MIME as the transport • Can be broadly deployed to reach the widest variety of providers and patients • Still allows for highly structured health care content • SOAP transport based on IHE/NHIN specifications (XDR AKA NHIN Document Submission • Includes ability to “step-up/step-down” to the universal secure SMTP transport

  8. Functional Status

  9. Lines of Code • Rapid and consistent growth on the C# side • C# team had to write much more code (DNS, MIME) than Java team due to better libraries on the Java side • Unit test and API documentation lagging behind • Java team has excellent progress on engineering quality (unit tests, documentation)

  10. States and NHIN Direct Specifications

  11. Q&A

More Related