The services a provider offers look like an arbitrary listing of values and as such are good candidates for some form of tagging. The acts-as-taggable-on plugin provides "context" tagging wherein different attributes can be tagged in their own context. So we could have one tag context for "Dental," another for "Optometry" and so on.
This would allow a Stack Overflow-style UI in the Admin area; the admin/Lindsay would start typing in values and in return would get autocomplete suggestions from existing tags in that context. This Stack Overflow post describes one implementation.
The services a provider offers look like an arbitrary listing of values and as such are good candidates for some form of tagging. The acts-as-taggable-on plugin provides "context" tagging wherein different attributes can be tagged in their own context. So we could have one tag context for "Dental," another for "Optometry" and so on.
This would allow a Stack Overflow-style UI in the Admin area; the admin/Lindsay would start typing in values and in return would get autocomplete suggestions from existing tags in that context. This Stack Overflow post describes one implementation.