Brian, I understand and share your concerns. If Jon's development with the next version of AC is to MODULARIZE it then the users will be served well. This is what I mean:
Build the core module of AC to be the best at what it does now. Polish the rough edges.
Add new modules, whose code interacts with the database but the code is a separate and distinct application.
So you would have:
The Health Maintenance Module
The Practice Management Module
The Document Management Module
The Vaccine Tracking Module
The Web-Schedule Module
The Hospital Charge Capture Module
The SmartDevice Module
The Online Medical History Module
The ECG/Holter Module
The Data Visualization/Graphs Module
The QuickBooks Integration Module
The Peachtree Integration Module
The HealthVault Integration Module
The GoogleHealth Integration Module
To name a few...
BTW, all of these modules DO NOT HAVE TO BE DEVELOPED BY JON. They can be developed following GUIDELINES which are MANAGED by Jon. In essence Jon would develop an Amazing Charts SDK (Software Developer's Kit) which would allow developers to EXTEND THE PRODUCT and add features.
This would also increase the number of features of AC while allowing users to only purchse the modules they need!!!
It also allows Jon to have a community of developers who have a vested interest in the success of AC, but not the overhead of having to hire them.
