A family of Microsoft relational database management systems designed for ease of use.
Patient information s.a. phone numbers are an important part of schedulers- they occasionally need to be called up to reschedule or to see if they are coming in at all! Anyhow, what makes a phone number less secure on a scheduler than on a form elsewhere in an EHR (electronic health record system)? I could see this being a problem if you post the scheduler on-line, though.
A lot of the large EHR ("electronic health record") companies make all sorts of excuses why a practice shouldn't make their own EHR in order to get providers to fork out tens of thousands of dollars for their proprietary EHR systems:
- the program is too insecure
- MS Access tables can't handle the volume of data
- there are nebulous laws for patient security that only the "big boys" could handle
- it's way too hard to make your own EMR/EHR
- then Medicare got into the game, penalizing physicians for not having an "approved" EHR. Medicare especially touted "interoperability" which has yet to be realized (if they post a set of standards, I'll meet them using Access).
My responses to these issues were:
1 & 2) it all depends on the environment you're programming for- small to medium sized clinic (OK) or a hospital (probably not as they have other rules and regulations set by the Joint Commission)? The MS Access back end tables are powerful enough to handle any small to moderate sized office with as many as 10 computers. My accounts table alone has over 40000 entries (I try to keep it trimmed to cover the past 4 years). It comes free with an Access subscription. That's a great deal...
- laws- think HIPAA, which is for medical transmission purposes. They don't want to have more red tape to EHRs than to paper records otherwise their use won't prosper. A lot of this are scare tactics. The Feds have much more on their hands than to destroy your practice.
- bogus- anyone can make their own EHR. In fact, to prove that point I made an
EHR using MS Word as a front end and MS Access as a back end to hold the patient tables. Here's a clip of the Word VB environment... not much different than Access.
- The loss of Medicare income pales to the cost of actually owning and up-keeping and "meaningfully using" a proprietary EHR system on a yearly basis.
My last presentation on the MS Office / EHR was in a grand rounds at a local large hospital (Inova Fairfax Hospital) where I presented a Powerpoint summary of all my efforts- "Meaningful Use Regulations and Your Practice- Surviving the Perfect Storm" (URL: https://app.box.com/s/urr0eux55neet8bmgsgr https://app.box.com/s/f3jicp7l86q2sgbth762).
While many of the medical offices around me continue to close, I've survived, a lot having to do with my MS Access EMR. The only 2 large hurdles were:
- When I had to switch to electronic billing- it's mandatory now if you wish to get paid. Many offices pay as much as 8% (or more) of their total gross billings yearly to an outside company to handle electronic billing. I contacted Office Ally (which is free) and was able to program an algorithm to transfer my daily MS Access billings at the end of the day to MS Excel using their spreadsheet, then up to the cloud- all with one click (I had to make it easy, as my secretary isn't all that bright). Cost: nothing. Took me 2 weeks to do.
- When I switched up to MS Access 2016 and lost the calendar control as well as other issues, all of which are pretty much fixed now. The switch was important to me as I want to finish the book that I started years ago on programming a MS Word EHR, but with the most current version of MS Office.
So as the controversial shoe company Nike advertises- "Just Do It" and get your EHR up and going...