3rd party updating of NPPES

[dportnoy]

Specifications: https://github.com/demand-driven-open-data/ddod-intake/wiki/Use-Case-16
Created page for full use case specifications and solution: http://hhs.ddod.us/wiki/Use_Case_16

[dportnoy]

Adding questions directed to NPPES organization to use case (http://hhs.ddod.us/wiki/Use_Case_16).

These questions are intended for 3rd party surrogate organizations to keep provider information up to date in the NPPES system.

1. Is there specific paperwork we need our clients to sign that give us authorization to jointly update their NPPES listing?
2. Is there any specific paperwork that would be required for them to revoke that authority in the case that we part ways?
3. Have there ever been any issues of liability that have arisen from a relationship like this?
4. What are the various ways that we can streamline the process of claiming and updating the listings (ie. Can we have a single login connected to all of the clients? Is there a standard fax form we can use? etc.)
5. How can we get an end-to-end walkthrough of the process?

[dportnoy]

Update: Original requestor, @doctor.com has been successful in their first batch submission via I&A. Updated instructions are here: http://hhs.ddod.us/wiki/Use_Case_16:_3rd_party_updating_of_NPPES#Update_via_I.26A

[betshsu]

Some further clarifying information added to the I&A instructions in the wiki.

[dportnoy]

Update: Waiting on confirmation of planned release from data owner. Once we can document it, this use case can be closed.

[doctorcom-reed]

@dportnoy -- we've managed to make updates, BUT, this method only works for individual NPIs that are NOT marked as "Y" in the 'sole_proprietor' field ..... so about 50% of the listings (and the ones most likely to be inaccurate). So, waiting on CMS to resolve.

[betshsu]

@doctorcom-reed CMS is aware of this issue and is looking to address it with future NPPES updates. However, they cannot confirm a date for this change, and don't anticipate anything prior to late 2016. Given this info, are you okay with closing this use case for now? Thanks.

[betshsu]

@doctorcom-reed Wanted to check in again and see if you had any objections to closing this use case. Thanks.