Difference between revisions of "Scan Set Up Validation"
Jump to navigation
Jump to search
Line 5: | Line 5: | ||
'''Environment Tested:''' EHR TEST | '''Environment Tested:''' EHR TEST | ||
− | '''Products Tested:''' EHR, ADM | + | '''Products Tested:''' EHR, ADM |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
Data Confirmed: | Data Confirmed: |
Revision as of 17:50, 5 June 2012
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
Data Confirmed:
- Document types in TW
- Chart Section assignments in TW
- Scan Chart Group Set Up in TC
- Scan Chart Links
- Filer Set Up
- User Group rights and chart group access
- Scan Functionality works in TC
- 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 mult pages)
- 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)