Open dportnoy opened 9 years ago
Created page for full use case specifications and solution: http://hhs.ddod.us/wiki/Use_Case_20
I fully support this initiative, but this analysis is possible now. Generally, Physician compare provides an OK mapping between doctors and practices, and then the new MU data release is coded by NPI.
However, a TIN association in the MU data directly is entirely appropriate if that was part of the data that was submitted as part of attestation. The provider compare data set is not comprehensive and relies on doctors to be participating in a second program...
I would verify that this data was submitted during attestation and if it was not table this request.
Updates made from notes to http://hhs.ddod.us/wiki/Use_Case_20
Hospital TIN would also be valuable, although I'm not sure where that data should ultimately "reside". Perhaps Hospital Compare's General Hospital Information table (data.medicare.gov view xubh-q36u)? Org-level value also pertinent at the hospital level since Physician Compare lists doc-to-hospital affiliations.
@ftrotter, Thanks for your input. The original requester explained that the NPI-TIN mapping data definitely exists within the context of MU attestation, but unfortunately they can't see it to do meaningful analytics. Also, from talking with CMS/CCSQ, I believe the TIN-to-NPI matching is used for the "payment adjustment file" being generated internally.
@loranstefani, Thanks for your input. I added your comments to the specifications.
@ftrotter @dportnoy resurrecting this a bit, but I'm looking to find TIN to NPI to EMR Deployment for a very specific health plan/provider data exchange initiative and I'm curious if a solution ever emerged from this conversation?
Specifications:
https://github.com/demand-driven-open-data/ddod-intake/wiki/Use-Case-20(Moved to http://hhs.ddod.us/wiki/Use_Case_20)