1 / 16

NPPES Modernization Project

NPPES Modernization Project. Provider Directories Meeting. Presented By Alan Viars and Richard Gilbert. June 1 9 , 2014. What is NPPES ?. NPPES Provides Individuals and Healthcare Organization a unique identifier for healthcare transactions - an NPI

hayden
Download Presentation

NPPES Modernization Project

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. NPPES Modernization Project Provider Directories Meeting Presented By Alan Viars and Richard Gilbert June 19, 2014

  2. What is NPPES? NPPES Provides Individuals and Healthcare Organization a unique identifier for healthcare transactions - an NPI NPI records are based on self reported (unverified), information. Nearly all payers require providers and suppliers to have an NPI. NPPES manages over 4 Million NPIs, and tens of thousands of updates per month.

  3. HHS Entrepreneurs Program Goal: Attract entrepreneurial talent to work with HHS staff on high-risk, high-reward projects for 13 months To Date: 9 Projects (from 2 cohorts), 6 Operating and Staff Divisions (ASPA, ASPR, ONC, ACF, CMS, HRSA), 12 External Entrepreneurs , and 29 Internal Entrepreneurs

  4. NPPES Modernization - Goal The goal for NPPES Modernization Project is to improve provider data quality, consistency, and usability for CMS, HHS, and the public.

  5. Problem Primary information in NPPES, such as provider’s practice addresses and telephone numbers are out of date. Providers have little to no incentive to update his or her record. The result is “staleness” of the data. Data accessibility and consistency issues exist amongst CMS systems.

  6. Project Objectives Collect input and feedback from internal stakeholders, providers, data consumers. Improve data quality in existing system Develop a web service for internal and external users. Develop a new fully-functional system of NPPES that makes providers want to keep their data current.

  7. High -Level Architecture Web Site – The new prototype system based on modern web stack using a 3-tier architecture where database access, control logic, and display logic are separated. Develop a framework for managing all provider-like enumerations (NPI, HPID, OEID, etc.). Create a series of “micro-services” that can be used for reporting and as well as data feeds for other applications. (e.g. a way for PECOS to fetch addresses, taxonomies, identifiers, and other information from NPESS).

  8. Existing System Snapshot • A circa 2000 technology stack • No major technology refresh or user interface overhaul since inception. • Tied to outdated web technology. • Complicated, expensive, and difficult to change. • No simple method for system to system connectivity.

  9. New Website and Data Service Snapshot • A contemporary open source technology stack • Mobile ready – Uses a responsive design to adapt to smartphone, tablet, or desktop computers. • Designed on technology used to run some of the webs largest sites. • A RESTFul API • Streamlined interface functionality to maintain large numbers of provider records.

  10. Challenges and Obstacles Access to server space for development, testing, and production within CMS. Interfacing with existing systems (e.g. I&A, PECOS). Network and system constraints slowing and complicating the development process.

  11. RESTFul API Using a GeoJSON-like approach Based around a JSON document that contains all necessary provider info. Can be expanded and contain extra information as needed.

  12. Pseudo JSON Example {    number: 123456789,    type:  "NPI-1",          basic: {first_name: "Ada", last_name:"Lovelace",            ...            },     addresses:[...],     taxonomies[...],     licenses:[...],     identifiers:[...],direct_addresses:[...]}

  13. Timeline Community / Stakeholder Feedback Concept Prototype Prototype Updates Launch Plan Transition Plan January 2014 April 2014 July 2014 October 2014 December 2014

  14. Prototype Screenshots (Draft Images / Work In Progress)

  15. More Information Check out http://npi.io We are conducting stakeholder interviews by phone to collect requirements. The project is open source. We will accept pull requests.

  16. Questions

More Related