1 / 2

- 1 -

Implications of Direct for Stakeholder. Why use Direct?. Healthcare Delivery Systems and the Direct Project. NHIN Direct is available for use by physicians in owned, highly affiliated, and loosely affiliated practices

karlyn
Download Presentation

- 1 -

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. Implications of Direct for Stakeholder Why use Direct? Healthcare Delivery Systems and the Direct Project • NHIN Direct is available for use by physicians in owned, highly affiliated, and loosely affiliated practices • Can serve as a bridge for connectivity solutions across and to the edges of the delivery system’s service area • Easy to implement and use by practices with or without EHR technology in place • Offers clinical partners a wide range of options for communications within and external to your network • Simple, easy to implement, use and maintain services • Can “bootstrap” physicians’ practices toward adoption of health IT • Will help enterprise and affiliated physicians meet Meaningful Use criteria for data exchange • A low cost alternative to fax machines and paper for many kinds of data and document exchange - 1 -

  2. What do you need to implement Direct? Call to Action How does Direct differ? Healthcare Delivery System and the Direct Project • Simple and easy to set up and use: addresses secure point-to-point transport only, not interfaces • Flexible and extensible: requires only email and Internet connection to start, but works with many EHRs, too • Vendor and operating system neutral, compatible with a broad range of health IT products and services • Does not require physicians to all use the same EHR technology or subscribe to membership in a single Health Information Exchange or RHIO • Email client software, e.g. Outlook • Connection to the Internet • Account with a Health Internet Service Provider or HISP, who will help you get your NHIN Direct Address and manage HIPAA level security • Most health care delivery services will set up their own HISPs to serve area physicians . • It’s easy! • Get involved! • Look for NHIN Direct pilot projects and participate, or start your own • Encourage your affiliated health care organizations, e.g practices, hospitals, long term care facilities, to use NHIN Direct • Demand that your EHR technology vendors are NHIN Direct compliant and on the network

More Related