Scan Set Up Validation

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

1. 1. 1. Advanced Directives to Misc Insurance – direct
      2. Med Rec Requests to OB/GYN report – filer
      3. GI Endo Report to Encounter form – batch using owner: Allscripts, Provider3 (single page and multi-page)
2. Scanned documents show up in the appropriate place in TW
3. Log in as a user from each group and verify they can function
   1. Twfront desk . . . Allscripts, Front Desk . . . go forward scanning
   2. Twmedrec . . . Allscripts, Medical Records…historical scanning
4. Scan test different documents from chart, for resolution testing (using samples from actual charts, with patient’s name blacked out)

Example ADM (Scan) Validation Script

Data Confirmed	Description	Date Tested	Tester Initials	Status	Issues	Comments
Document Types	Supporting document types are properly build in EHR	1/2/12	D.B.	FAIL	EKG document type was not built/available to link to ADM chart folder	Submitted update request to EHR build team to build
Chart Sections/Folders	Supporting ChartViewer folders/hierarchy exist in EHR	1/2/12	J.N.	PASS
Scan Chart Groups	Supporting Chart Groups exist in ADM	1/2/12	J.N.	FAIL
Scan User Groups/Security	Supporting ADM access groups and ADM security defined	1/4/12	J.N.	PASS
Filer Setup	Supporting filer configurations and button/doc type mappings exist	1/4/12	D.B.	N/A
Scan Functionality	Documents can be physically scanned into ADM (direct, batch, filer)	1/5/12	D.B.	PASS
Images in EHR	Document scanned into ADM are properly visible in EHR ChartViewer	1/5/12	D.B.	PASS