Hi
The other day,while giving a demo, one of the doctors asked if our openEMR comes with pre-loaded list of pharmacies and providers: it seems the other EMR he saw come with this feature.
Is there a way we can do this? Where can we find such a list?
Thank you very much.
Is it wise for us to preload this info into the database while hosting for the? Is there any collateral damage that I should be aware of?
It is 350 MB in zip. SO should we store in a utilities page in wiki or include it with the original downloads?
The icd9 is also not included in the downloads.
These are things that average users would like to have when they download and install openEMR. Not every one is a programmer.
Personally, I lost an account yesterday because these were not there in the demo version too. When we tell them that these are all configurable they are very uneasy.
Or is it already somewhere and I am just missing it?
It’s better to follow the strategy that’s used for ICD9 codes. Download most recent version (in this case the most recent CMS list). Then import it into the database as a table (analogous to what is done in the icd9/cpt/etc. scripts in contrib/util ). Then when a new version comes out can run the script again (drop old and add new).
Having this stuff on install seems overkill, but I definitely agree we need easier to use scripts for all this reference table loading, and would be nice to be able to do all this within openemr via php loader scripts (now, the loader scripts are all in perl). Would be nice to have a gui that will allow downloading and loading of most recent module (icd9/pharmacies/docs/etc.); all this project is waiting for is a developer…
Brady
I understand and we are trying to work on these. Right now we are working on the payments and EOB section which needs major work. . If no one else takes it up in the meanwhile we hope to get to the one above.
Hi,
We tried this and the feed back was that it was overwhelming. Way too many for the average. What we ended up doing was sorting out only those for our region and even so it was annoyingly large. We now provide it only if they request it. Those providers who only refer to a handful just don’t need that many.
Any GUI should parse by serveral parameters (Specialty, State, Zip etc).
FYI: We processed in foxpro to get it into a CVS and then upload into OEMR.
That’s what I thought. Maybe we should include it in the demo versions so that the providers know that it is there, and when they install it we can give them a choice. The reason is that when we tell them we can add it they are very skeptical. Any comments?
Yup, Sounds good to me…but how much to put in the demo?
That referral pull-down is gonna look real ugly. That GUI will need to be updated to something more manageable and help providers drill down to the right one.
Ah and any tool used to import needs to mark them all as external and exclude (Using NPI) the local (Working in Clinic) Provider. This will avoid duplication.