This clinic outcomes page will be posted in a confluence space available to all Federal and contractor employees in the CCSQ Community
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:
- User has valid IQIES login with the correct role/privilege
- User will navigate to Request Role access
- User will select ADO
- User will select organization related to their ADO
- User will select user role associated with ADO
- After user submits request, a security official will need to review and approve the request, which may take a few hours.
- 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.
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..**
Notes:
Revised Story(s):
Original Story:
Author
Notes:
Revised Story(s):
A a medicare recipient user can log into our website so they can view claim information