Scan Set Up Validation
Revision as of 18:13, 5 June 2012 by David.Burkhead (talk | contribs)
Description
Coming up with validation plans and test scripts are almost always environment specific and important to validating any type of build and configuration work. Below is a straw model for an Allscripts Document Management (Scan) Validation.
Scan Build Validation
Environment Tested: EHR TEST
Products Tested: EHR, ADM
- Scan Chart Links
- scanned every document type into each folder (direct, filer and batch)
- Advanced Directives to Misc Insurance – direct
- Med Rec Requests to OB/GYN report – filer
- GI Endo Report to Encounter form – batch using owner: Allscripts, Provider3 (single page and multi-page)
- scanned every document type into each folder (direct, filer and batch)
- Scanned documents show up in the appropriate place in TW
- Log in as a user from each group and verify they can function
- Twfront desk . . . Allscripts, Front Desk . . . go forward scanning
- Twmedrec . . . Allscripts, Medical Records…historical scanning
- Scan test different documents from chart, for resolution testing (using samples from actual charts, with patient’s name blacked out)
Data Confirmed | Description | Date Tested | Tester Initials | Status | Issues | Comments |
---|---|---|---|---|---|---|
Document Types | 1/2/12 | D.B. | FAIL | |||
Chart Sections/Folders | 1/2/12 | J.N. | PASS | |||
Scan Chart Groups | 1/2/12 | J.N. | FAIL | |||
Scan User Groups/Security | 1/4/12 | J.N. | PASS | |||
Filer Setup | 1/4/12 | D.B. | N/A | |||
Scan Functionality | 1/5/12 | D.B. | PASS | |||
Images in EHR | 1/5/12 | D.B. | PASS |