Difference between revisions of "Test Guidelines"

From Galen Healthcare Solutions - Allscripts TouchWorks EHR Wiki
Jump to navigation Jump to search
Line 17: Line 17:
For more information, please see: [[Enterprise Test Strategy]]
For more information, please see: [[Enterprise EHR Test Strategy]]

Revision as of 21:39, 18 November 2010

Application Change Management Protocol for Testing Phase

Superuser and Physician Resource Requirements for Testing

1) Minimum Number of Providers: 1 assuming standardization plus 1 for each specialty or practice that has workflow(s) specific to that specialty or practice. An alternative would be to have a core team member demonstrate the workflow for the provider but that would probably take almost as much of the provider’s time.

2) Minimum Number of other users: 1 per role. Each role must be tested by a user who performs that role. Otherwise the benefit of user testing is lost. 1 per role plus if there is a specialty or practice that has workflow(s) specific to that specialty or practice they should send a superuser to test them.

  • For 1 and 2 above: These minimums are absolutely critical in order to ensure that the documented workflows actually cover all the critical details of all practices and specialties. The superusers and providers should be asked not to just test the documented workflow but to try anything they do that is not covered by the documented workflow.

3) Total duration they will be needed for: 4 hours per day for 2-3 days total

4) Typical number of hours per day: Superuser and provider testers do not have to test every day, the number of hours will depend on how many roles and workflows they test. Typically 4 hours on the days they are needed for testing. Generally they would test for 1 or 2 days near the beginning of the testing period as part of the 1st or 2nd testing cycle and then possibly be asked back a week or so later to retest if significant changes are made to the configuration or workflow.

This testing time will also provide additional training for those involved and increase organizational acceptance.

For more information, please see: Enterprise EHR Test Strategy