Managing Digital Student Document Quality Assurance

Managing Digital Student Document Quality Assurance is one of the functional areas to consider when Integrating with PASI.

Services

Architectural Considerations

The following questions should be considered when Managing Digital Student Document Quality Assurance in addition to the general considerations when Managing Data within PASI.

What is the software application approach used to flag Digital Student Documents requiring quality assurance review?

Digital Student Documents will be flagged by an organization and/or by PASI as requiring quality assurance review.

A software application must provide functionality to allow software application users to flag Digital Student Documents as requiring quality assurance review by setting QualityAssuranceStatus to Pending. Software application functionality to flag Digital Student Documents as requiring quality assurance review must have search, list, and filtering criteria to allow software application users to search and find Digital Student Documents that should be flagged as requiring quality assurance review. Filtering criteria such as:

  • Created by Organization/School
  • Document Category
  • Document Type
  • Relevant
  • Uploaded Start Date
  • Uploaded End Date
  • Digitized
  • Exempt from QA
  • QA Status (No Pending QA)
  • No QA History

What is the software application approach used to report Digital Student Documents requiring quality assurance review?

Digital Student Documents flagged as requiring quality assurance review must be reviewed by the organization that created the Digital Student Document.

PASI and the organization that created the Digital Student Document are the only organizations that can flag the Digital Student Document as requiring quality assurance review (Pending QualityAssuranceStatus). Regardless who flagged a Digital Student Document as requiring quality assurance review, it must be reviewed. A software application may provide functionality to report all Digital Student Documents created by the software application organization requiring quality assurance review. Software application functionality to report Digital Student Documents requiring quality assurance review may have list and filtering criteria to allow software application users to search and find such Digital Student Documents. Filtering criteria such as:

  • Created by Organization/School
  • Document Category
  • Document Type
  • Is Relevant

What is the software application approach used to record Digital Student Documents quality assurance review results?

Results of a Digital Student Document quality assurance review must be recorded.

A software application may provide functionality to record a Digital Student Document quality assurance review Pass or Fail result. In the case of a quality assurance review failure, the software application may also provide functionality to record failure details including:

  • Failed Quality Assurance Comments
  • Problem Type
  • Failure Details
  • Reporting User Email

Recording a Digital Student Document quality assurance Failure will trigger creation of a Digital Student Document Problem Report. A software application may provide functionality to report Digital Student Document problem reports for all Digital Student Documents created by the software application organization.

What is the software application approach used to ensure Digital Student Document quality assurance data is set correctly?

There are numerous factors that determine how Digital Student Document quality assurance data must be set when flagging a Digital Student Document as requiring quantity assurance review and/or when recording Digital Student Document quantity assurance results.

A software application must enforce and/or or allow application software user to specify the following when flagging a Digital Student Document as requiring quantity assurance review and/or when recording Digital Student Document quantity assurance details:

Data Element Format Required Recommendations
Quality Assurance Status String Yes
  • Quality Assurance Status must be set to a valid PASI Document QA Status code (Pending, Pass, Fail)
  • PASI Document QA Status codes must be obtained using the Get PASI Code Values service. Software application must use PASI Code Values data to populate document QA status codes available for use/selection.
  • QualityAssuranceStatus must be set to Pending when a document requires QA review.
  • QualityAssuranceStatus must be set to Pass when a document QA review has successfully completed and no issues were identified.
  • QualityAssuranceStatus must be set to Fail when a document QA review identified issues.
Failure Details Object No
  • Must be provided when quality assurance activities determine there are quality issues (i.e. setting Quality Assurance Status to Fail)
Failed Quality Assurance Comments String Yes
  • If and when Digital Student Document quality assurance activities determine there are quality issues (Quality Assurance Status set to Fail), such issues must be describe in detail (free form text) and captured in FailedQualityAssuranceComments.
Problem Type String Yes
  • If and when Digital Student Document quality assurance activities determine there are quality issues (Quality Assurance Status set to Fail), Problem Type must be an appropriate Digital Student Document Problem Type code value
  • PASI Digital Student Document Problem Type codes must be obtained using the Get PASI Code Values service Software application must use PASI Code Values data to populate Digital Student Document Problem Type available for use/selection.
Student Document Problem Reported By User Email String No
  • If and when Digital Student Document quality assurance activities determine there are quality issues (Quality Assurance Status set to Fail), ReportingUserEmail must be the email address of the person reporting the Digital Student Document QA failure.