Login is the portal all users use to access the platform.

Is there anything else that is important to include here?

QIO Connect is an interactive portal for all users to ask questions, interact with other users, and track popular discussion topics amongst users.

The Security Official Workspace allows Security Officials 

(I still do not have SO access to IMPL so I'm not able to see what the feature involves (I pinged Garvin / Vishnu yesterday so hopefully I will soon) - but I'm assuming it has to do with approving access?)

The Intake Workspace allows Super Users to submit two types of Quality Improvement Requests: 

• General Quality Improvement Request – for ALL requestors other than from BFCC.
• BFCC QII Request – to be completed by BFCC ONLY.

A Quality Improvement Request begins the process of deploying QINs by detailing the need for assistance. It allows Super Users to:

• Describe the request
• Provide substantiating data
• Request assistance dates
• Describe desired outcome measures
• Attach supporting documents

Once the request is submitted, CMS is notified. They determine whether the request is in-scope, and if it is, they will determine the priority and begin the activation process.

Once a Quality Improvement Request is approved, Super Users begin the FQS Activation Process, which defines the specific needs of the request, including:

• Tier Level
• Sprint Duration
• Inclusion Criteria
• Evaluation Metrics
• Outcomes Reporting
• Close-Out Criteria

Super Users also upload the FQS Provider List with baseline data that specifies which providers will be involved. 

CORS review the activation, estimate the workload, and approve the activation, which deploys the QINs to begin working on the Referrals based on the uploaded Provider List.

• Super Users create activations
• CORs approve activations

In FQS Referrals, QIN-QIO Super Users will reach out to all Providers in the uploaded Provider List to gather information and determine critical interventions to perform and data they need to complete the evaluation. 

QIN-QIO Super Users will put together a QAP (Quality Action Plan) to address all QI issues identified and perform and document all necessary interventions in the system. 

Once the interventions improve the necessary metrics, so the provider no longer falls within the inclusion criteria, the referral is closed out. 

CORs approve all referral packages.

• Basic Users create referrals
• CORs approve referral packages

A3C (Assess, Complement, Coordinate, Create) is created by an internal system admin for each state as preparation for the QINs. QIN Basic Users perform environmental scans to address the landscape of healthcare across each state, to identify areas where Quality Improvement Requests need to occur. 

The outcome of A3C will eventually be linked to subsequent FQS Activations but are not yet for MVP1.

I didn't think that anything from AIAN is included in the first MVP release? Is there anything I should include here for now?

The AIAN (American Indian / Alaskan Native) Workspace is an FQS Workspace that is focused on communities rather than states. It will largely be a duplicate of the FQS screens, tailored to the specific needs of AIAN users.

The AIAN Workspace is not complete for MVP1 and will be completed by October 2024.