Difference between revisions of "Enterprise EHR Test Strategy"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
* Plan and schedule the testing cycle | * Plan and schedule the testing cycle | ||
* Testers | * Testers | ||
| − | * | + | * Test Patients |
| − | * | + | * Role Based Testing |
| − | * | + | * Issue Tracking |
| − | * | + | * End of day meetings and recap |
| − | * | + | * Retesting Workflows |
'''Clinical Workflow Documentation''' | '''Clinical Workflow Documentation''' | ||
| − | + | * Document | |
| − | + | * Make the Certified your own | |
| − | + | * Level of Detail | |
| − | + | * Review | |
| − | + | * Change Control | |
| + | * Build a living document | ||
'''Testing Cycle''' | '''Testing Cycle''' | ||
| − | + | * | |
| − | + | * | |
| − | + | * | |
| − | + | * | |
| − | + | * | |
Revision as of 20:16, 17 November 2010
Overview
The Application Project Team is most often responsible for ensuring the application is properly setup and configured in a way that supports the application's end users. With some structure and planning, this team should be able to quickly and thoroughly validate the system.
General Preparation and Planning
- Plan and schedule the testing cycle
- Testers
- Test Patients
- Role Based Testing
- Issue Tracking
- End of day meetings and recap
- Retesting Workflows
Clinical Workflow Documentation
- Document
- Make the Certified your own
- Level of Detail
- Review
- Change Control
- Build a living document
Testing Cycle