Home Forums Discussions General Discussion User's Manual

Hi All,

Just got back from the Alaska HIT conference; AC is one of the final five products under consideration by the Alaska EHR alliance which aims to make a recommendation to small offices. Unfortunately, AC's presentation was not particularly well attended. AllScripts seems to be garnering the most interest.

Anyway, there was lots of discussion on how an office goes about implementing EMR's and I came away with a few tasks to complete for our 5 provider/20 user office.

One is to put together a user's manual for how our office uses AC.

Do any of you have one that you have compliled? Would you be interested in sharing at least the outline?

Thanks,

Sky

Not sure, but there should be a good user's manual anyway put out by AC. And there is not.

My opinion is that AC should put a lot of time and effort into support with the usual FAQs, Knowledge Base and User Guide, etc.

Thanks Bert,

What I'm trying to do is get a manual together that is specific to our operation/implementation. Some of it will be boilerplate stuff from the AC Wiki or FAQ's, but some will be procedures that we use for in-house messaging, lab orders, superbill creation, scanning, etc. I was just hoping someone else has a start on one.

Tim

I agree on Bert's share -- AC should put out a comprehensive User Guide and there really is none. I still, after 2 years, do not use or know many of the features of AC. It is unbelievable to me that JB et al have been too busy to take the time to have someone write up a comprehensive user manual and task someone to keep it updated, and makes me worried about the future of the company in general.

"Coming Soon"

Agreed. For instance, one of the first sections should be on installation. I could see talking about the install of the main computer or server with AC and SQL Server Express.

During that section one would want to have something such as:

UNDER NO CIRCUMSTANCES should one move the AC folder from one location to another without first detaching the databases from SQL Server. Failing to do so can cause database corruption or other issues. Moving the Amazing Charts folder with the databases should be moved as little as possible.