Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Include Page | ||||
---|---|---|---|---|
|
RESOURCES
Job Aids
Navigating HCD Research and PRA - A job aid outlining basics about the PRA, common HCD research methods, and a decision tree.
Fast-Track Generic Checklist - Use this job aid to help determine if your ICR is appropriate for the CCSQ generic clearance with fast track process.
Guides
Guide to the Paperwork Reduction Act - A plain language guide that answers the most common questions to the PRA.
18F User Experience Design Guide - 18F, a government design agency, shares their understanding of the PRA and HCD methods.
CMS-10706 Generic Clearance
Generic Clearance Checklist - Use this job aid to help determine if your ICR is appropriate for the CCSQ generic clearance with fast track process.
Short form - ICR template. Use this form to capture the details of your ICR for OSORA and OMB review.
PRA Disclosure Statement - All collection instruments submitted under this generic fast track must include this statement.
Memos
FAQs About Fast Track - Published in 2012, this document answers common questions about the fast track process.
Flexibilities Under the PRA - A memo outlining many administrative flexibilities available to assist agencies in complying with their obligations under the PRA.
Exclusions to Regulatory Definition of Information - A summary table of exclusions to the PRA.
OSORA and OMB
OSORA - The Office of Strategic Operations and Regulatory Affairs includes PRA officers who coordinate PRA efforts for the agency. Note: the above link is for CMS employees to access information for Regulatory and Affairs Group.
OIRA - The Office of Information and Regulatory Affairs (OIRA) is a statutory part of the Office of Management and Budget within the Executive Office of the President.
Information Collection Inventory - OIRA listing of current collections, collections under review, and more.
Shared Services
Touchpoints - A GSA service that provides a standard feedback survey template that leverages an existing PRA clearance.
Tip | ||
---|---|---|
| ||
What you need to know:
Please visit the announcement page for more information, download the ICR template, and contact our team with any questions. |
What is the PRA?
The Paperwork Reduction Act (PRA) is a federal law intended to ease the data reporting burden imposed by the government. The law pertains to data collection regardless of form or format (including digital, paper-based, and standardized interviews). The PRA governs most research and feedback collection mechanisms done by or on behalf of the federal government. Any federal agency requesting responses from the public is required to estimate the time and cost burden for citizens to respond and the burden on the federal agency to compile and synthesize the data. Authorizations for PRA approval of data collection come from the Office of Management and Budget (OMB), and PRA officers in each agency coordinate the effort.
It is essential and mandatory that CCSQ comply with the PRA when applying human-centered design (HCD) processes and methodologies. However, the PRA should not limit HCD best practices to improve the customer experience. If the information you are collecting is subject to clearance, most agencies estimate six to nine months from agency development to approval. We encourage you to take advantage of the flexibilities and requirements that exist for compliance. You can learn more about the basic information related to the PRA at A Guide to the Paperwork Reduction Act.
About the PRA and HCD
HTML |
---|
<iframe width="490" height="275" src="https://www.youtube.com/embed/tQY7XSkuQ2o" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
PRA Flexibilities
Compliance requires an understanding of when the PRA applies. Generally, if you collect the same information from ten or more people or entities within 12 months, the PRA applies. Applicable members of the public governed by the PRA are vast. It includes individuals (including non-US citizens), businesses and associations, non-federal and foreign governments, and more. Ultimately, the only excluded individuals or groups are within the federal government and military (and even then, the PRA can sometimes be applicable).
However, there are many exclusions to when the PRA applies, such as:
- Generally, requesting the same information from fewer than ten people. There are some exceptions to this rule.
- Direct observation, such as qualitative usability tests and field studies.
- Open-ended requests for comments or feedback.
- Discussions and questions at public hearings or meetings (whether in person or online).
- Collecting information from federal employees related to their role or function.
Planning Research
Your research objectives, target users, protocols, and timeframes play an essential role in determining which research method(s) you will implement. That, in turn, determines whether the PRA applies. The number of people needed to complete a study for insight generation may be under the PRA threshold or because a technique is not subject to the PRA since it employs direct observation and non-standardized conversation.
For example, with HCD, the goal is to understand people (end-users and other stakeholders) and their interactions with everything or a particular product or service during their daily lives. If that is your goal, you may select observational and ethnographic research methods to learn about people to extract valuable insights from the research. The PRA may not apply since exclusions include direct observation and non-standard oral communication, which is the essence of ethnographic research.
Ultimately, the number of participants depends on what researchers need to know, the purpose of the inquiry, the business problem, what lends credibility to the study, and available resources. There are best practices you can apply as a rule of thumb to begin research in some instances. Some studies will require more individuals and some fewer.
Navigating HCD and PRA
Navigating HCD Research and PRA is a summary document that can help you determine if the PRA applies to your study. It includes high-level steps to get started, HCD research methods and PRA quick reference guide, and a decision tree to help you understand if you need clearance. The job aid is a general reference and should not be confused with official guidance from the Office of Strategic Operations and Regulatory Affairs (OSORA). Always follow your group’s guidelines about research and PRA guidelines.
Do I Need Clearance?
Common Methods
Method | PRA clearance needed? | Rationale |
---|---|---|
Qualitative | ||
Contextual Inquiry | No | Contextual interviews are often non-standardized, conversational, and based on observation. The PRA exempts direct observation and non-standardized conversation (5 CFR 1320.3(h)3). In a Flexibilities under the Paperwork Reduction Act memo it states that “OMB does not generally consider facts or opinions obtained through direct observation by an employee or agent of the sponsoring agency or through non-standardized oral communications in connection with such direct observations to be information under the PRA." |
Diary study | No | If nine or fewer participants the PRA does not apply. If ten or more participants and the diary is free-form, the PRA does not apply. If ten or more participants and the diary is structured, the PRA applies. |
Field study | No | Field studies are often non-standardized, conversational, and based on observation. If nine or fewer participants the PRA does not apply. If ten or more participants and uses non-standardized conversation and observation, the PRA does not apply. |
Focus group | Yes | Assumes 10 or more participants. |
Interview - scripted | Yes | Assumes 10 or more participants. |
Interview - non-standardized | No | Non-standardized questions. |
Listening sessions | No | PRA does not apply since discussion and questions at public hearings or meetings are excluded. |
Usability testing | No | Small sample size. (Does not require ten or more participants; generally, anything beyond five to eight participants does not yield new information.) |
Quantitative | ||
A/B testing | No | Evaluates potential improvements in comparison to a control version based on statistical analysis. |
Card sorting | No | PRA exempts direct observation and non-standardized conversations. |
Surveys, such as website satisfaction, customer satisfaction, or system usability scale | Yes | Large sample size. Consider the GSA shared service survey resource called Touchpoints that leverages an existing PRA clearance. |
Tree testing | No | Tree testing often has 50 or more participants however direct observation and non-standardized conversations are exempt. |
Usability testing | Yes | Large sample size. |
Generic Collections
Generic clearances go through the normal PRA process (such as the 60-day and 30-day notices to the Federal Register) but allow quicker clearance of future collections, which leverage it.
Some generic clearances also include the fast-track process, which means collections usually do not have to undergo additional public comment and involve less documentation and time to obtain approval. Instead, in most situations, OMB completes its review within five business days after receiving all required materials.
CCSQ Generic Clearance
In July 2021, CCSQ's Information Systems Group (ISG) obtained OMB approval for an information collection request (ICR) titled "Generic Clearance for the Center for Clinical Standards and Quality IT Product and Support Teams (CMS-10706)" (OMB Control Number: 0938-1397)." In July of 2024, this clearance was renewed and the capacity for respondents and hours was expanded. This clearance is for the Center for Clinical Standards and Quality IT Product and Support Teams (CIPST) to leverage for specific information collections and includes the Fast-Track approval process.
Fast-Track Requests
HTML |
---|
<iframe width="490" height="275" src="https://www.youtube.com/embed/N7XXSgYaxCc" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
Criteria
The generic fast-track requests are for teams that collect data on stakeholder awareness, understanding, attitudes, preferences, or experiences about existing or future products or services. An information collection may be eligible if it meets all the following criteria:
- The data collection focuses on improving existing or future services or products.
- The collection is voluntary.
- The collection is a low burden for respondents and low-cost for the Federal Government.
- The collection is non-controversial and does not raise issues of concern to other federal agencies.
- There is no dissemination of the findings to the public.
- Information gathered will not be used to inform policy decisions substantially.
Example Methods
HCD research methods that inform the utility, usability, and desirability of products or services are generally appropriate for the generic clearance. Examples include:
- Card Sorting
- Cognitive Testing
- Field Studies
- First Click Tests
- Focus Groups
- Participatory Design
- Surveys
- Tree Testing
- User Interviews
- Usability Testing
Fast Track Process
First, some quick tips:
- Give yourself sufficient lead time for approval, including up to a month after all materials are with OMB.
- If you are unsure if the collection is appropriate for the generic fast track, contact OSORA.
- You may also refer to the checklist job aid to help you understand if your collection is likely a good fit for the generic fast track.
- If you are a contractor, coordinate with your CMS point of contact to interface with OSORA, including any questions you may have and submission of the short-form ICR template.
Critical steps to follow and what to expect:
- Prepare: Submit the following to OSORA for a fast-track generic ICR clearance package:
- A completed short-form ICR template.
- A copy of the information collection instruments and research artifacts, e.g., research plan, survey, questions, etc.
- Include the PRA Disclosure Statement on all collection instruments.
- Submit the ICR package to OSORA; if you are a contractor, coordinate with your CMS point of contact to submit the package to OSORA.
- OSORA review: OSORA will review the ICR package and suggest changes if needed.
- Complete any requested changes and send revised documents to OSORA in collaboration with your CMS point of contact.
- OSORA will submit the ICR package to OMB.
- OMB review: OMB has five business days to respond; however, you should plan for a month before receiving approval.
- OSORA will contact you if OMB has a question or requires more information.
- If OMB inquires within those five days, they have an additional five days to respond after sending them your response via OSORA.
- Typically an ICR is assumed to be approved after 5 days with no response from OMB, however OSORA will allow additional time to receive OMB guidance.
- Information collection: OSORA will contact you with approval to proceed.
OSORA has indicated that generally, OMB will have a question, and in practice, it may take longer than five days. While approval will not take as long as a regular (non-generic, non-fast track) package, it may be longer than five days. A month is a reasonable amount of time to expect, so be sure to give yourself sufficient lead time.
Who to Contact
Please contact:
- Office of Strategic Operations and Regulatory Affairs (OSORA), who is the primary contact and subject matter expert for the PRA. If you are a contractor, coordinate your outreach with OSORA via your CMS point of contact. Note: the hyperlink is for CMS employees to access information for Regulatory and Affairs Group.
- CCSQ HCD Center of Excellence at who can answer questions about the generic clearance and provide general reference information.
Questions
Anchor | ||||
---|---|---|---|---|
|
Please reach out to the HCD Center of Excellence if you have any questions about the information on this page or general questions about the PRA and the CCSQ generic clearance.
Include Page | ||||
---|---|---|---|---|
|
How to Use this Information
This information is meant to be for general reference and should not be confused with official guidance from Office of Strategic Operations and Regulatory Affairs (OSORA). Always follow your group’s guidelines about research and PRA guidelines.
Div | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
HTML |
---|
<!-- Title: Floating Table of Contents Author: Wade Tracy URL: https://community.atlassian.com/t5/Boise-discussions/Widget-Wednesday-Floating-TOC-in-Confluence/td-p/1095431 This code sets up the floating table of contents - Formatting is configured for up to 3 levels of headings - Control your heading levels from the TOC macro How to use: 1. Use a page layout that puts at least one column on the right to reserve space for the TOC 2. Insert a TOC macro in the right column of the layout 3. Change the TOC settings and specify ts-toc-btf for the 'CSS Class Name' 4. Somewhere in the page (it won't be visible) insert an HTML macro and paste in this code 5. Feel free to modify css to get the styling you want --> <style> .ts-toc-btf { float: right; position: fixed; width: inherit; right: 3%; top: 33%; background: rgba(229, 232, 232, 0.5); overflow-wrap: normal; visibility: hidden; list-style-type: none; } .navigation ul { list-style-type: none; padding: 0px; } .navigation>ul { padding: 10px 0px10px 10px 10px; } .navigation ul li { white-space: nowrap; } .navigation ul li a { padding: 0 0 0 10px; } .navigation ul li ul li a { padding: 0 0 0 20px; } .navigation ul li ul li ul li a { padding: 0 0 0 30px; } .navigation ul li li { white-space: nowrap; } .navigation ul li span.active a { font-weight: bold; color: #222222; border-left: 2px solid #222222; } .navigation ul li a:link, .navigation ul li a:visited, .navigation ul li a:active, .navigation ul li a:hover, .navigation ul li a:focus { color: #4a72c2; text-decoration: none; } </style> <script type="text/javascript"> /*! * Scrollspy Plugin * Author: r3plica * Licensed under the MIT license */ ; (function ($, window, document, undefined) { // Add our plugin to fn $.fn.extend({ // Scrollspy is the name of the plugin scrollspy: function (options) { // Define our defaults var defaults = { namespace: 'scrollspy', activeClass: 'active', animate: false, duration: 1000, offset: 0, container: window, replaceState: false }; // Add any overriden options to a new object options = $.extend({}, defaults, options); var add = function (ex1, ex2) { return parseInt(ex1, 10) + parseInt(ex2, 10); }; // Find our elements var findElements = function (links) { var elements = []; // Loop through the links for (var i = 0; i < links.length; i++) { var link = links[i]; // Get our hash var hash = $(link).attr("href"); // Store our has as an element var element = $("[id='" + hash.replace('#','') + "']"); // If we have an element matching the hash if (element.length > 0) { // Get our offset var top = Math.floor(element.offset().top), bottom = top + Math.floor(element.outerHeight()); // Add to our array elements.push({ element: element, hash: hash, top: top, bottom: bottom }); } } return elements; }; // Find our link from a hash var findLink = function (links, hash) { for (var i = 0; i < links.length; i++) { var link = $(links[i]); // If our hash matches the link href if (link.attr("href") === hash) { // Return the link return link; } } }; // Reset classes on our elements var resetClasses = function (links) { // For each link for (var i = 0; i < links.length; i++) { // Get our current link var link = $(links[i]); // Remove the active class link.parent().removeClass(options.activeClass); } }; // Find the nearest heading whether at the top of the screen or off the screen var getActiveHeadingHash = function (elements) { // Get the position and store in an object var position = { top: add($(this).scrollTop(), Math.abs(options.offset)), left: $(this).scrollLeft() }; // Store the nearest heading off the top of the page var nearest = null; // Loop through our elements for (var i = 0; i < elements.length; i++) { // Get our current item var current = elements[i]; // If we are within the boundaries of our element return that link if (position.top >= current.top && position.top <= current.bottom) return current.hash; // Otherwise, return the closest of the top of the screen--they are in order else if (position.top > current.bottom) { nearest = current.hash; } } return nearest; }; // Store last fired scroll event var scrollArea = ''; // For each scrollspy instance return this.each(function () { // Declare our global variables var element = this, container = $(options.container); // Get our objects var links = $(element).find('a'); // Loop through our links for (var i = 0; i < links.length; i++) { // Get our current link var link = links[i]; // Bind the click event $(link).on("click", function (e) { // Get our target var target = $(this).attr("href"), $target = $(target); // If we have the element if ($target.length > 0) { // Get it's scroll position var top = add($target.offset().top, options.offset); // If animation is on if (options.animate) { // Animate our scroll $('html, body').animate({ scrollTop: top }, options.duration); } else { // Scroll to our position window.scrollTo(0, top); } location.hash = target; // Prevent our link e.preventDefault(); } }); } // Set links resetClasses(links); // Get our elements (targets of the navigation links) var elements = findElements(links); var trackChanged = function() { // Create a variable for our link var link; // get our element var hash = getActiveHeadingHash(elements); // Get the link link = findLink(links, hash); // If we have a link if (link) { // If we have an onChange function if (options.onChange && (scrollArea !== hash)) { // Fire our onChange function options.onChange(current.element, $(element), position); // set scrollArea scrollArea = hash; } // Update url if (options.replaceState) { history.replaceState( {}, '', '/' + hash ); } // Reset the classes on all other link resetClasses(links); // Add our active link to our parent link.parent().addClass(options.activeClass); } // If we don't have a link and we have a exit function if (!link && (scrollArea !== 'exit') && options.onExit) { // Fire our onChange function options.onExit($(element), position); // Reset the classes on all other link resetClasses(links); // set scrollArea scrollArea = 'exit'; // Update url if (options.replaceState) { history.replaceState( {}, '', '/' ); } } }; // Add a listener to the window container.bind('scroll.' + options.namespace, function () { trackChanged(); }); $(document).ready(function (e) { trackChanged(); }); }); } }); })(jQuery, window, document, undefined); var getMenuWidth = function() { // Need to get the padding of the main window since menu goes to edge of window var mainPadding = ($('#main').innerWidth() - $('#main').width()) / 2; var parentWidth = AJS.$(".ts-toc-btf").parent().parent().outerWidth(); return parentWidth + mainPadding; }; AJS.$(window).load(function(){ var content_top = AJS.$('#content').offset().top; var menu_width = getMenuWidth(); var max_width = AJS.$('.ts-toc-btf').width(); AJS.$(".ts-toc-btf") .addClass('navigation') .attr('id', 'nav') .css({'top': content_top, 'visibility': 'visible', 'width': menu_width, 'max-width': max_width}); AJS.$("#nav").scrollspy(); }); AJS.$(window).resize(function() { var menu_width = getMenuWidth(); AJS.$(".ts-toc-btf") .css({'width': menu_width}); }); </script> |