CHIPRA Performance Requirements Summary.doc

PAGE

ATTACHMENT 6- PERFORMANCE REQUIREMENTS SUMMARY

1. Reports and Planning Documents: Quality of Products Delivered.

Reports and planning documents in the following tasks are covered by this factor:

· Final project plan (Task 1) Summaries of semi-monthly conference calls with COTR (Task 1)

· Summary of kick-off meeting (Task 1)

· Agendas and preparatory materials for monthly calls with COES/grantee States, AHRQ, CMS (Task 3.1)

· Summaries of monthly calls with COES/grantee States, AHRQ, CMS (Task 3.2)

· Quarterly reports summarizing COEs/grantee States’ progress using measure criteria)

· Yearly summary reports describing barriers encountered and progress by COEs/grantee States (Task 3.3)

· List of proposed experts (Task 4.1)

· Agendas and other preparatory materials for public meetings

· Draft Federal Register Notice for public meetings (Task 4.3)

· Analyses of discussions in public meetings (Task 4.4)

· Any and all other products required by this SOW.

a. Products and services delivered effectively reflect the identified needs of the target audience(s) and the recommendations of the subject matter experts.

b. Products are effective for communications among COEs, Grantee States, experts, AHRQ and CMS.

c. Products and services demonstrate a thorough search for evidence-based research, expert knowledge, best practices and best presenters, as available

d. Writing and editing of products (hard copy and electronic) reflect sound editorial accuracy and attention to detail. Products require a limited amount of time for AHRQ staff in re-editing.

e. Products appropriately reflect AHRQ and CMS as initiative leaders.

f. Products appropriately credit input of AHRQ, CMS, COEs, grantee States, and other experts.

f. Products are timely (i.e., adhere to the deliverable schedule).

g. Products are technically accurate (i.e., comprehensive, and do not misrepresent evidence-based research, expert knowledge, and discussions among any of the parties).

Review of products and services by COTR, other AHRQ staff, COEs, Grantee States, experts, and CMS as appropriate.

Review of products and services by COTR, other AHRQ staff, and appropriate experts in the field.

2. Technical Assistance to COEs/grantee States, AHRQ and, thru AHRQ, CMS

a. Technical assistance, however provided, is technically accurate (i.e., comprehensive, and does not misrepresent evidence-based research, expert knowledge, and discussions among any of the parties).

b. Technical assistance is provided in a timely manner.

c. Technical assistance is provided in a professional and user-friendly manner.

Review of products and services by COTR, CMS, COEs, and grantee States, and other AHRQ staff as needed.

3. SEQ CHAPTER \h \r 1Public meetings

a. Lists of proposed experts meet criteria outlined in the SOW for inclusion and include experts who can help the overall initiative meet CHIPRA criteria, expanded as required thru this initiative (e.g., criteria for evidence-based measures).

b. All agendas and other preparatory products (including briefing materials) are provided in a timely manner to allow for review by AHRQ COTR and CMS.

c. All agendas and other preparatory products are provided in a timely manner to all public meeting participants.

d. The public meetings are summarized in a timely and appropriate manner (e.g., useful for allowing AHRQ and CMS to make recommendations about improved core sets).

Review of products and services by COTR, CMS, COEs, grantee States, invited experts, and other AHRQ staff as needed.

4. Web-based environment

a. The draft plan for the web-based environment(s) are presented to the COTR according to the schedule of deliverables.

b. The multi-directional web-based environment (or two web-based environments) are implemented in a timely manner (see deliverables schedule).

c. The web-based environment(s) meet all criteria established by AHRQ’s IT enterprise director and all 508 requirements in the AHRQ publishing guidelines. (Exclusion: in the collaborative space, documents need not be 508 compliant while they are in development as drafts, within a 6-month window).

d. The web-based environment is user-friendly.

e. The web-based environment is updated in a timely fashion with essential documents.

f. The collaborative web-based environment is deemed suitable as one way to provide technical assistance in the context of all technical assistance activities.

g. Materials on the web environments are accurate and comprehensive relevant to their intended purposes.

Review of products and services by COTR, other AHRQ staff, CMS staff, COEs, grantee States, experts, and the public, as appropriate.

5. Measure criteria enhancement

a. The final plan for measure criteria enhancement must be submitted to AHRQ in a timely manner.

b. The plan for measure criteria shall reflect input from national standards for such criteria, CHIPRA criteria for measures, input from COEs, grantee States, and knowledgeable AHRQ and other HHS staff.

c. Measure criteria shall be made available in a format that is understandable and user-friendly by COEs, grantee States, individual experts, and the public.

d. Measure criteria are currently in flux. Updates must reflect important developments in HHS and elsewhere, as directed by AHRQ.

Review of performance by COTR, other AHRQ staff, CMS, COEs, grantee States, individual experts, and the public.

b. Required assessments must reflect the current version of measure criteria.

c. Required assessments must be presented in a format and manner that is understandable and usable by AHRQ, CMS, and the public.

d. Required assessments must be comprehensive, technically accurate, and explicit about the basis of decisions made. Where judgment is applied (in combination or separately from evidence), that must be made explicit Review by AHRQ COTR, CMS, COEs, grantee States, other experts, and the public.

7. Draft public notices.

Draft public notices include:

· Notices of public meetings.

· Postings of improved core sets

· Call for measures

a. Draft public notices must use the appropriate official public notice format(s).

b. Draft public notices must accurately reflect the purpose of the public notice.

c. Draft public notices must be technically accurate.

d. Draft public notices must be user-friendly (i.e., readable, understandable).

e. Draft public notices shall require minimal editing by AHRQ COTR and other staff.

Review by AHRQ COTR, CMS, other AHRQ staff, and other technical experts as needed. .

PAGE