Iteration 3 Test Specification

This wiki page covers the outline of how the system and components for SCOOP Iteration 3 will be tested.

Introduction

This project supports practitioners and groups of practitioners to engage in reflective practice. it does so by leveraging the use of standardized EMR data across multiple practices while the patient data stays in the control of the practice. A secure network hub can ask questions of the practices with sufficient rigor to support quality improvement and research.

This project will develop the infrastructure needed for networking EMR practices together to robustly answer a range of clinical questions without data leaving the control of the provider.

Goals and Objectives

• Reusable set of components that can be used to connect EMR practices into a question answering network.
• Infrastructure can support multiple sub-networks asking different questions.
• Infrastructure will work with existing standards.
• Infrastructure will be secure and trustworthy.

Statement of Scope

The scope of iteration 3 is to add support in OSCAR for exporting template-based documents. This feature will be the primary target of testing activities outlined in this document.

Major Constraints

• Testing can only be performed in a non-production environment

Test Plan

Testing is outlined in accordance with the requirements. Testing is oriented by two different kinds of analysis:

Validation - Are we building the right system? Validation is concerned with checking that the system will meet the customer’s actual needs.

Verification - Are we building the system right? Verification is concerned with whether the system is well-engineered, error-free, and so on.

"Verification will help to determine whether the software is of high quality, but it will not ensure that the system is useful."

See this article for more explanation.

Software to be Tested

OSCAR

Testing Strategy

Verification - Unit Testing

Verification - Integration Testing

Validation Testing

Test Procedure