FPAR 2.0 Frequently Asked Questions

This page will be updated regularly with answers to frequently asked questions regarding FPAR 2.0.

Jump to questions about:


Data Elements

OPA considers the data elements final. OMB approved FPAR 2.0 data collection under OMB control number 0990-0479. It expires September 30, 2024.

For general questions on the Paperwork Reduction Act and the OMB approval process, more information can be found at Digital.gov.

All data elements are to be collected as required by the clinical encounter. Data collection should not drive the clinical encounter. Review Business Rules - XLS for further guidance. (Excel content in this section is undergoing Section 508 review and will be updated pending remediation. For immediate assistance, please contact: opa@hhs.gov.)

Grantees who can report some (but not all) FPAR 2.0 data elements are asked to submit any encounter-level FPAR 2.0 data available. The FPAR 2.0 system will calculate site-level and grantee-level aggregate level tables similar to those currently produced for FPAR 1.0. Grantees will then have the option to edit these summary tables to ensure totals per each table accurately represent services provided.

Yes, OPA is exploring multiple opportunities to reduce reporting burden, including providing a crosswalk for FPAR 2.0 and HRSA’s UDS data elements.

Many FPAR 1.0 data elements are also included in FPAR 2.0. OPA will compare reporting rates for FPAR 2.0 data elements to FPAR 1.0 reporting rates at a grantee level, as well as historical trends across all grantees, to help assess data quality and data validity. An implementation guide, listing required, and optional data has been published and can be found on the OPA website. In addition, grantees will have the ability to review and edit the aggregate level data tables produced for them by the FPAR 2.0 system before they are considered final.

Electronic clinical quality measures (eCQMs) are instruments used to collect electronic data for the purpose of measuring care and outcomes. See the description of the claims-based Contraceptive Care Measures (CCM).

Self-Identified Need for Contraception (SINC) is an electronic clinical quality measure (eCQM) under development at the University of California San Francisco (UCSF). Reporting this data element is optional. If a grantee does not currently collect it, SINC does not need to be reported.

A select number of data elements will be required on every encounter-level record (row) to identify unique encounters, or to capture routine quality family planning care. Most data elements will be optional or only collected at some encounters. An implementation guide, listing required, and optional data has been published and can be found on the OPA website.

The contractor developing the FPAR 2.0 system will access date of birth and other elements for a period of time before it is destroyed. OPA will only have access to summarized, de-identified data (such as age instead of date of birth).

The “Attending Physician NPI” should be that of the provider providing care to the client on the encounter date. The LOINC term is, “Attending Physician NPI”. OPA cannot modify this but recognizes that other providers besides physicians have NPI numbers. If the person providing family planning services has an NPI, regardless of if they’re a physician or not, it should be reported. If the person who provided the family planning services does not have an NPI, the field should be left empty.

The STI and lab panels include codes both for tests performed as well as the actual results.

Contraceptive Method at Intake/Exit shall be reported as a separate field from Reason for No Contraceptive Method at Intake/Exit since each field is mapped to different LOINC codes.

Contraceptive Method at Intake/Exit shall be reported as a separate field from Reason for No Contraceptive Method at Intake/Exit since each field is mapped to different LOINC codes.

CBE will no longer be collected in FPAR 2.0 due to changes in clinical guidance starting with calendar year 2022 data.


Data Privacy

While personally identifiable information (PII), such as date of birth, will be collected about clients, the PII will not include client names or other direct personal identifiers. The FPAR 2.0 system will apply rules to date of birth and other identifiers submitted by grantees, then de-identify records to ensure uniformity in the approach to securing patient confidentiality. Each client will receive a unique identifying number for data integrity purposes to ensure the system does not double-count individuals when compiling aggregate data covering more than one encounter. The unique identifying number will not be a direct personal identifier and cannot be used to link PII with an individual.

Data will be anonymized and all raw data, including PII, will be destroyed within a year of submission. For details on the data anonymization process for FPAR, please refer to the IHE IT Infrastructure White Paper, “Analysis of Optimal De-Identification Algorithms for Family Planning Data Elements,” published in December 2016. Appendix A of the white paper shows how specific data elements are de-identified from the original file submitted by grantees.

Additionally, the FPAR 2.0 system will comply with applicable HHS and federal regulations through completion of the HHS Enterprise Performance Life Cycle Framework, including the Authority to Operate process and included cybersecurity and privacy review processes.

For details on the data anonymization process for FPAR, please refer to the IHE IT Infrastructure White Paper, “Analysis of Optimal De-Identification Algorithms for Family Planning Data Elements,” published in December 2016. Appendix A of the white paper shows how specific data elements are de-identified from the original file submitted by grantees. Further documentation is in development.


Data Collection

OPA does not have a recommendation for how often grantees should review the encounter-level data from direct service sites and/or subrecipients. As grantees are required to use Family Planning data to monitor performance and improve family planning services, OPA strongly encourages grantees develop a process based upon your organizational capacity and need for assessing the data from direct service sites and/or subrecipients prior to submission.

No, there is not a designated FPAR 2.0 EHR vendor. OPA is working to gather information from some of the largest vendors nationwide to inform implementation planning and TA development. OPA encourages all grantees and subrecipients to work directly with their EHR partners.


Data Submission/File Format

Data can be submitted in either C-CDA or Flat-file format, further guidance is being developed.

A flat file is a simple data file that typically has one row per record, and each row follows a uniform format. One of the most common flat file examples is a comma-separated values (CSV) file.

Grantees should report a file containing all relevant encounters for the 12-month reporting period. Each encounter (that is, each row in the file) should contain the FPAR 2.0 data elements. Submissions will be due each February (once per year), similar to current requirements for reporting FPAR 1.0.

Grantees will continue to submit FPAR aggregate data in the beginning of 2022. The grantees following the preferred approach will start collecting FPAR 2.0 data beginning January 2022 for reporting in February 2023.

A template record review tool is not available at this time. OPA and the development contractor will take this suggestion into consideration as design work continues.

No, grantees should report using a single approach for a reporting cycle. For grantees starting out on the alternate approach, they should move to the preferred approach for the next reporting cycle as soon as they are in a position to provide FPAR 2.0 encounter- level data.

The FPAR 2.0 system will be hosted in a secure, cloud-computing environment with robust capacity. Submissions will be due each February (once per year), similar to current requirements for reporting FPAR 1.0. Further data submission guidance is in development.

OPA is exploring opportunities to reduce reporting burden, including providing a crosswalk for FPAR 2.0 and UDS data elements. We will explore opportunities to align FPAR reporting requirements with other reporting systems in the future.


Data Validation

Grantees are responsible for submitting encounter-level data to the FPAR 2.0 system. As such, grantees are encouraged to assess data quality from subrecipients prior to submission. OPA has posted an FPAR 2.0 implementation guide with further guidance on data submission.

Many FPAR 1.0 data elements are also included in FPAR 2.0. We will compare reporting rates for FPAR 2.0 data elements to FPAR 1.0 reporting rates at a grantee level, as well as historical trends across all grantees, to help assess data quality and data validity. In addition, grantees will have the ability to review and edit the aggregate level data tables produced for them by the FPAR 2.0 system, before they are considered final.


FPAR 2.0 System

The FPAR 2.0 system will allow grantees to submit their data electronically. The system will also automate some procedures that are currently done manually, such as tabulating and checking basic counts of the number of clients served and types of services provided. The FPAR 2.0 implementation guide has further guidance on data submission.


Reporting

The FPAR 2.0 data collection builds on data already reported in FPAR 1.0 and adds additional detail that will allow OPA to report to HHS leadership and Congress more completely on the services provided by Title X grantees in their communities. The system will also provide grantees with reporting tools and interactive dashboards to analyze their data, communicate with stakeholders, and identify areas for improvement.


Technical Working Groups (TWG)

OPA and their contractors used Title X program data to identify candidates for one of two Technical Work Groups (TWG) that vary in experience submitting FPAR data, number of subrecipients and service sites, geographic location, and EHR systems in use. Grantee organizations participating in the TWGs include: ABCD (Action for Boston Community Development), Georgia Family Planning System, Every Body Texas, Essential Access Health, New Jersey Family Planning League, Neighborhood Improvement Project (Medical Associates Plus), Indiana Family Health Council, Inc., Colorado Dept. of Public Health and Environment, Access Matters, the Family Health Centers of Georgia, Inc., Idaho Dept. of Health and Welfare Family Planning Program, Oklahoma State Department of Health, Montana State Department of Public Health and University of Puerto Rico Medical Sciences Campus.