Page tree

This clinic outcomes page will be posted in a confluence space available to all Federal and contractor employees in the CCSQ Community

Story1

Original Story:

Author: Joshua Skillington 


As an automated access management system

I want the IQIES request role flow to support ADO users

So that CGI Federal ADO could get access to use the PECOS API Functionality

 Acceptance Criteria:

  1. User has valid IQIES login with the correct role/privilege
  2. User will navigate to Request Role access
  3. User will select ADO
  4. User will select organization related to their ADO
  5. User will select user role associated with ADO
  6. After user submits request, a security official will need to review and approve the request, which may take a few hours.
  7. Once API access is approved, user will click the 'Administration' menu and then 'Manage API tokens'.Saviynt is sending request notifications for role requests via e-mail to appropriate CMS approvers.

ADO's will have an IQIES API solution per feature solution documentation located at: iQIES API Integration Guide

Dev effort is to package the previously collected QIES Daily Lockbox Check Records information into a report with previously collected IQIES Daily Lockbox Check Records.

Revised Story(s):


Story 1

As a CGI Federal ADO employee, I want to be able to log into IQIES environment with the correct role/privilege using my HARP credentials so that I use the PECOS API Functionality

Acceptance Criteria:

  1. Verify that all CGI Federal ADO employees that need to login has a HARP credential
  2. Verify that  the right roles an privileges are granted to all CGI Federal ADO employees that want access


Story 2

As a CGI Federal ADO employee, I want to be able to click the button tap "Request Role Access" so that I can submit a request to use the PECOS API Functionality

Acceptance Criteria:

  1. Verify that all CGI Federal ADO employees with the right role/privilege when logged into IQIES environment can click the "Request Role Access" Tab 
  2. Verify that when a CGI Federal ADO employee clicks the  "Request Role Access" tab, they are directed to a page to select a user category


Story 3

As a CGI Federal ADO employee, I want to be able to select "ADO" from a user category list so that I can submit a request to use the PECOS API Functionality

Acceptance Criteria:

  1. Verify that all CGI Federal employees with the right role/privilege can select "ADO" from the user category list 


Story 4

As a CGI Federal ADO employee, I want to be able to select an organization related to my ADO so that I can submit a request to use the PECOS API Functionality

Acceptance Criteria:

  1. Verify that all CGI Federal ADO organizations are listed
  2. Verify that all CGI Federal ADO employees that want access can select their organization 


Story 5

As a CGI Federal ADO employee, I want to be able to select a user role I need and submit so that I have access to use the PECOS API Functionality

Acceptance Criteria:

  1. Verify that all user roles needed by a CGI Federal ADO employee are listed
  2. Verify that a CGI Federal employee has the option to a select user role
  3. Verify that a CGI Federal employee can submit a request after selecting a user role


 Story 6

As a Security Official, I want to be able to review all requests submitted so that I can approve or deny a request 

Acceptance Criteria:

  1. Verify that a Security Official can view all request submitted
  2. Verify that they have the option to approve or deny a request
  3. Verify that authorization to the approval mechanism is automated


NOTES:

There would be additional stories to represent the positive and negative results of approval

Story2

Original Story:


As a CLIA Administrator (DUNE team by proxy)

I want to be able to have an IQIES Daily Lockbox Check Records Report

So that I can compare QIES to IQIES

Assumption:

This effort will not need to go behind a feature flag.

HCD does not need to provide design

The IQIES Lockbox Collection will need to account for five processing days of results.

Acceptance Criteria:

QIES/IQIES Daily Lockbox Check Records Report is created.

The report has QIES and IQIES process date and lockbox id noted:

QIES Lockbox Process Date 08/17/2012 05:00; lockbox id = 1780

IQIES Lockbox Process Date 08/17/2012 06:00; lockbox id = 1

There is a QIES section each individual 3000 check record containing the information of check number, Process Date, 3000 batch id and Item number:
Creating check = 5204582, Process Date 08/17/2012, Batch # 3000, Item # 01
Creating check = 1433558, Process Date 08/17/2012, Batch # 3000, Item # 02
Creating check = 21463373, Process Date 08/17/2012, Batch # 3000, Item # 03
Creating check = 193263, Process Date 08/17/2012, Batch # 3001, Item # 01

There is an IQIES section each individual 3000 check record containing the information of check number, Process Date, 3000 batch id and Item number:
Creating check = 5204582, Process Date 08/17/2012, Batch # 3000, Item # 01
Creating check = 1433558, Process Date 08/17/2012, Batch # 3000, Item # 02
Creating check = 21463373, Process Date 08/17/2012, Batch # 3000, Item # 03
Creating check = 193263, Process Date 08/17/2012, Batch # 3001, Item # 01

There is a QIES section where each Batch type check records are summarized PER batch id:

Batch 1000 Check Records Summary Amount $1800 

Batch 1001 Check Records Summary Amount $800 

Batch 1002 Check Records Summary Amount $900 

Batch 2000 Check Records Summary Amount $1200 

Batch 2001 Check Records Summary Amount $1900 

Batch 8000 Check Records Summary Amount $2500 

There is an IQIES section where each Batch type check records are summarized PER batch id:

Batch 1000 Check Records Summary Amount $1800 

Batch 1001 Check Records Summary Amount $800 

Batch 1002 Check Records Summary Amount $900 

Batch 2000 Check Records Summary Amount $1200 

Batch 2001 Check Records Summary Amount $1900 

Batch 8000 Check Records Summary Amount $2500 

There is a comparison column that compares QIES to IQIES row and shows a value of Yes/No if the QIES and IQIES value is different.

There is a Reasons column that attempts to outline the reason for a discrepancy.  Eg:  Check record does not exist on QIES..**


Revised Story(s):


 Story 1

As a CLIA Administrator (DUNE team by proxy), I want to be able to have an IQIES Daily Lockbox Check Records Report So that I can compare QIES to IQIES

Acceptance Criteria:

  1. Verify that QIES/IQIES Daily Lockbox Check Records Report is created.
  2. Verify that all CLIA Administrator (DUNE Team by proxy) has access to IQIES Daily Lockbox Check Records Report


Story 2

As a CLIA Administrator (DUNE team by proxy), I want to be able to have an IQIES Daily Lockbox Check Records Report on QIES and IQIES process date and lockbox id So that I can compare QIES to IQIES

Acceptance Criteria:

  1.  Verify that the report has QIES and IQIES process date and lockbox id noted:
  •            QIES Lockbox Process Date 08/17/2012 05:00; lockbox id = 1780
  •            IQIES Lockbox Process Date 08/17/2012 06:00; lockbox id = 1


Story 3

As a CLIA Administrator (DUNE team by proxy), I want to be able to have an IQIES Daily Lockbox Check Records Report containing QIES information of check number, Process Date, 3000 batch id and Item number so that I can compare QIES to IQIES

Acceptance Criteria:

  1. Verify that there is a QIES section each individual 3000 check record containing the information of check number, Process Date, 3000 batch id and Item number:
Creating check = 5204582, Process Date 08/17/2012, Batch # 3000, Item # 01
Creating check = 1433558, Process Date 08/17/2012, Batch # 3000, Item # 02
Creating check = 21463373, Process Date 08/17/2012, Batch # 3000, Item # 03
Creating check = 193263, Process Date 08/17/2012, Batch # 3001, Item # 01


Story 4

As a CLIA Administrator (DUNE team by proxy), I want to be able to have an IQIES Daily Lockbox Check Records Report containing IQIES information of check number, Process Date, 3000 batch id and Item number so that I can compare QIES to IQIES

Acceptance Criteria:

  1. Verify that there is an IQIES section each individual 3000 check record containing the information of check number, Process Date, 3000 batch id and Item number:
Creating check = 5204582, Process Date 08/17/2012, Batch # 3000, Item # 01
Creating check = 1433558, Process Date 08/17/2012, Batch # 3000, Item # 02
Creating check = 21463373, Process Date 08/17/2012, Batch # 3000, Item # 03
Creating check = 193263, Process Date 08/17/2012, Batch # 3001, Item # 01


Story 5

As a CLIA Administrator (DUNE team by proxy), I want to be able to have an IQIES Daily Lockbox Check Records Report with a QIES section where each Batch type check records are summarized PER batch id so that I can compare QIES to IQIES

Acceptance Criteria:

  1. Verify that there is a QIES section where each Batch type check records are summarized PER batch id:
  • Batch 1000 Check Records Summary Amount $1800 
  • Batch 1001 Check Records Summary Amount $800 
  • Batch 1002 Check Records Summary Amount $900 
  • Batch 2000 Check Records Summary Amount $1200 
  • Batch 2001 Check Records Summary Amount $1900 
  • Batch 8000 Check Records Summary Amount $2500 


Story 6

As a CLIA Administrator (DUNE team by proxy), I want to be able to have an IQIES Daily Lockbox Check Records Report with a IQIES section where each Batch type check records are summarized PER batch id so that I can compare QIES to IQIES

Acceptance Criteria:

  1. There is an IQIES section where each Batch type check records are summarized PER batch id:
  • Batch 1000 Check Records Summary Amount $1800 
  • Batch 1001 Check Records Summary Amount $800 
  • Batch 1002 Check Records Summary Amount $900 
  • Batch 2000 Check Records Summary Amount $1200 
  • Batch 2001 Check Records Summary Amount $1900 
  • Batch 8000 Check Records Summary Amount $2500 


Story 7

As a CLIA Administrator (DUNE team by proxy), I want to be able to download QIES and IQIES daily records report via IQIES Daily Lockbox so that I can compare QIES to IQIES

Acceptance Criteria:

  1. Verify that CLIA administrator has the option to down reports
  2. Verify the type of format to be download??































  • No labels