search

untoldone / bloomapi

Create APIs out of public datasources
https://www.bloomapi.com/documentation/public-data
MIT License
89 stars 29 forks source link

Versioning of Provider data #58

Closed anatolyg closed 10 years ago

anatolyg commented 10 years ago

It would be great to enable the ability to track versions of NPI data, to create an audit trail of changes to individual provider records.

An easy way I was thinking about is to create a hash of the provider data (JSON.stringify() -> sha256?) and append it to the record.

This way, when a provider's info changes, downstream users of the bloom DB can use the version record to launch a process to version the provider info. Helpful for those tracking transitions of providers from one org to another, for example.

untoldone commented 10 years ago

Thanks for the suggestion, do you have any specifics of the scenarios in which this is useful?

anatolyg commented 10 years ago

it’s really useful to have an employment history for physicians, or to know when a resident becomes a physician, or when a nurse practitioner moves jobs. Also, this is the only way I see to know what physicians have been de-activated (right now, deactivations result in the clearing of all demographic data from the NPI table).

untoldone commented 10 years ago

I follow -- I had been thinking about this as well. I'll see if I can get it into my current work.

untoldone commented 10 years ago

This is now present in the most recent rewrite (v0.2.0). The postgres db tracks all NPI updates continually while the new elasticsearch instance only shows the most recent data. This will likely be more useful in the future if additional functionality is added to surface the NPI history. Let me know if you have any feedback or questions!