1. Research & Evaluation
  2. Title X Services Research
  3. Family Planning Annual Report (FPAR) 2.0
  4. FPAR 2.0 Frequently Asked Questions

FPAR 2.0 Frequently Asked Questions

Last updated in January 2025

Jump to questions about:

Data Elements

OPA considers the data elements final. The Office of Management and Budget (OMB) approved the FPAR 2.0 data collection under OMB control number 0990-0479.

Every encounter record MUST contain the data corresponding to data elements required to upload encounter-level data: (1) Facility Identifier, (4) Patient Identifier, (5) Visit Date, (6) Birth Date, and (7) Sex. Files with missing values on any of these five data elements will not be accepted. 

All other data elements should be reported on each encounter if the data are collected and when clinically appropriate. The system accepts files with missing values on these data elements, and missing data are included in data quality reviews.

Please refer to the FPAR 2.0 Valid Values file for additional information about expected data. 

Grantees must report response options as described in the FPAR 2.0 Valid Values spreadsheet. Please refer to the FPAR 2.0 Valid Values for reportable response options and for additional information about expected data.

Grantees can build their systems to collect any data elements they deem necessary and appropriate. For FPAR encounter-level reporting, grantees should submit only the data elements and FPAR 2.0 Valid Values.

Starting with calendar year 2022 data (2023 submission), CBE is no longer collected in FPAR 2.0 due to changes in clinical guidance.

Grantees should provider their Type 2 National Provider Identifier (NPI2), which identifies a hospital or clinic for this data element, when possible. Grantees can also choose to create a facility identifier. If grantees choose to create a facility identifier, grantees must ensure that the facility identifier is unique for each facility and is consistent across all records provided. OPA does not assign facility identifiers.

The Attending Physician NPI should be that of the provider giving 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, whether or not they are a physician, the NPI should be reported. If the person who provided the family planning services does not have an NPI, the field should be left empty.

Grantees should report the role of the clinician providing care to the client on the encounter date. The current response options include a pre-existing list of provider roles that is also used for purposes other than FPAR reporting.

Currently, other types of providers cannot be reported in the expected answer list for the Provider Role. Please submit one of the FPAR 2.0 Valid Values listed for Provider Role. Updates to the list of allowable responses may be considered in the future.

The codes “LA46-8” (Other) and 74964007 [Other (qualifier value)] are available for grantees to use when they wish to account for a provider role that is not currently listed specifically in the current version of the FPAR 2.0 Valid Values file. We welcome suggestions for additional response options grantees feel would be useful for the Provider Role data element in the future. 

If grantees are concerned that the patient identifiers used by subrecipients are duplicated across subrecipients, they should append a forward slash (/) and the subrecipient name to the patient identifier. This modification enables the FPAR contractor to determine whether an encounter descries the same client or a different client. Grantees should use the same modified identifier each year to ensure consistency in the records across years.

There are no requirements for the format of the patient identifier. The patient identifier, which is assigned by a specific organization (the assigning authority), is a unique alphanumeric string that identifies a specific client.

At this time, OPA allows for the use of a pseudo number/ID for the patient identifier. If grantees choose to use a pseudo ID for the patient identifier, they must ensure that:

  1. Pseudo IDs are unique for each individual.
  2. They assign the same pseudo ID to the same individual across encounters each year to enable analysis of encounters over time.

Yes. Grantees must report Facility Identifier (Data Element 1), Patient Identifier (Data Element 4), Visit Date (Data Element 5), Birth Date (Data Element 6), and Sex (Data Element 7) for every family planning encounter. If an encounter-level file does not include any of these five data elements, the FPAR system will reject the submission. 

OPA does not have access to birth dates. The contractor maintaining the FPAR system retains the date of birth and other elements for one year after submission and then they are destroyed. The FPAR system converts dates of birth to an age. It also assigns age 50 to all clients age 50 and older. OPA has access only to summarized, de-identified data (such as age instead of date of birth).

The FPAR data elements and response options were designed to align with Interoperability Standards and EHR Certification requirements (United States Core Data for Interoperability (USCDI) standards; ISA Standard Terminology). FPAR 2.0 is currently accepting only male and female as responses for Data Element 7 (“Sex”). At this time, OPA’s FPAR National Summary presents analyses of certain family planning care variables based on sex. OPA will review the response options, value sets, and interoperability standards on an ongoing basis to identify opportunities to enhance the allowable reporting options. 

Grantees can report options other than male and female using Data Element 43 (Gender Identity) to represent the client’s gender identity. For FPAR reporting, please map all data to the appropriate FPAR 2.0 valid value. 

If it is unclear whether the person is proficient in English and “Other” is listed as the primary language, grantees should not report a value for Data Element 8 (Limited English Proficiency). An individual may have a primary language other than English and may also be proficient in English. If it is known that the individual is not proficient in English, grantees should report the valid value that corresponds to “Not proficient in English” for Data Element 8 (Limited English Proficiency).

Response options for this data element are “Hispanic or Latino” or “Not Hispanic or Latino”. This term is used for reporting the ethnicity based on classifications provided by OMB, Revisions to the Standards for the Classification of Federal Data on Race and Ethnicity.

Race is the only multi-selection data element. The comma-separated values (CSV) file should contain one column for each of the race categories, which can each take a value of LA33-6 (for yes) or LA32-8 (for no). Please review the FPAR 2.0 Implementation Guide, FPAR 2.0 Valid Values, and Sample Files for additional guidance on reporting.

If clients select ‘multiracial’ AND indicate specific race selections (for example, Asian, Black or African American, White) for race (Data Element 10), then please indicate “Yes” (LA33-6) for the identified race selections. However, if a client selects ‘multiracial’ but does not indicate specific race selections, then please report “Yes” (LA-33-6) for ‘Race – Unknown’, and “No” for all other specific race categories.

Grantees can leave the field blank for all clients who do not know or who are unwilling to report their income. However, grantees should report a non-negative integer if they are able to report annual household income for the client.

When reporting household size, grantees should ask clients to include themselves in the total number of people living in their household.

Please report only one insurance coverage type per encounter. The Insurance Coverage Type element is intended to determine clients’ access to comprehensive primary medical care. If a client has access to comprehensive primary medical care, please report one option that is most applicable to the clients’ insurance from the list of response options provided. For further guidance on reporting Insurance Coverage Type, please see the Insurance Coverage Mapping Guidance document.

Grantees do not need to offer all response options as a selection option for subrecipients if response options are not applicable.

Grantees should report the appropriate FPAR 2.0 Valid Values file for each client in their encounter-level data. If a client is uninsured, select the response option that best applies to the client (for example pay, health spending account). If the insurance coverage type of the client is unknown, then leave the data element blank for the client.

When grantees submit their encounter-level data, the FPAR system automatically categorizes the response options for Insurance Coverage Type under four categories (public, private, uninsured, or unknown/not reported) to populate Table 5 (Unduplicated Number of Family Planning Users by Principal Health Insurance Coverage Status). Further information on how response options are categorized can be found in the Insurance Coverage Mapping Guidance.

If a client has more than one form of insurance listed, grantees should report the insurance used to cover family planning-related activities. If both are used, grantees should report the primary insurance.

For all clients who are uninsured, grantees should report the valid value that corresponds to “pay” for Data Element 13 (Insurance coverage type). However, if clients are being subsidized through a government program, then report the valid value that corresponds to a safety net clinic program.

For more information on each of the response options for Data Element 13 (Insurance coverage type), refer to the coverage type value set.

Grantees should determine the response option that best fits the client’s insurance. Definitions for each response option can be found on the HL7 website. For example, if a client has a Medicaid MCO, please report the valid value that corresponds to a subsidized managed care program.

MCPOL should be used only for private managed care plans.

If Medicare is considered the client’s principal insurance, whether they attained Medicare due to a disability or not, the valid value that corresponds to a subsidized managed care program should be reported as the insurance coverage type.

The purpose of the Insurance Coverage Type data element is to capture a high-level description of a patient’s access to broad primary medical care health coverage type, including various categories of insurance (i.e., public, private, and so on) and self-pay. For Insurance Coverage Type codes, please report the FPAR 2.0 valid value most applicable to the family planning client. 

For the Payer for Visit data element, the payer source charged by the organization for Title X services should be reported. If this information cannot be determined, the Payer for Visit data element contains a response option of 'None (no charge for current services)’ and ‘Other (specify).’ For Payer for Visit, grantees should report the respective FPAR 2.0 Valid Values.

The grantees' EHR should include a distinct question to capture pregnancy status. Pregnancy Status is a separate data element and should be reported as a separate field. Please refer to the FPAR 2.0 Valid Values for the pregnancy status data element.

Grantees may leave this field blank for family planning clients who are male at birth.

The purpose of the pregnancy intention data element is to capture a client’s intention in the next year to either become pregnant or prevent a future pregnancy. This includes male clients seeking pregnancy with a female partner. In addition, pregnancy intention may be used to help improve preconception health screenings and decisions based on client needs. However, grantees may leave this field blank for family planning clients who are male at birth. 

Grantees' EHR should include a distinct question to capture both Contraception At Intake and Reason for No Contraceptive Method at Intake. Contraceptive Method at Intake shall be reported as a separate field from Reason for No Contraceptive Method at Intake, as each field is mapped to different LOINC codes.

Grantees should report only the most effective contraceptive method used by the client and how the most effective contraceptive method was provided: https://opa.hhs.gov/research-evaluation/title-x-services-research/family-planning-annual-report-fpar.

Grantees should report the most effective method reported by the client at the time of each family planning encounter.

Grantees should report Contraceptive Method at Exit shall be reported as a separate field from Reason for No Contraceptive Method Use Reported at Exit, as each field is mapped to different LOINC codes.

Contraceptive counseling is an interaction in which a provider spends time (5–10 minutes) during an encounter discussing the client's choice of contraceptive method and available options.

Counseling to achieve pregnancy is an interaction in which a provider spends time during an encounter discussing any services or provides counseling related to achieving pregnancy or addressing infertility.

For telehealth, it is up to the reporting organization and clinical judgment of their providers to determine when self-reported values are acceptable.

Grantees can report body height in either inches (in) or centimeters (cm). Please see the FPAR 2.0 Valid Values to reference acceptable response options.

Grantees should report body weight as pounds (lbs), grams (g), or kilograms (kg). Please see the FPAR 2.0 Valid Values to reference acceptable response options.

According to the Centers for Disease Control and Prevention’s Tobacco Glossary, a current every day smoker is someone who smokes daily, specifically “an adult who has smoked 100 cigarettes in his or her lifetime and who currently smokes cigarettes.” Further refinement specific to what constitutes a current every day smoker comes from the National Cancer Institute (NCI). Specifically, a current every day smoker may be designated as either a heavy tobacco smoker – “a smoker who smokes more than 10 cigarettes per day, or an equivalent quantity of cigar or pipe smoke” or a light tobacco smoker – “a smoker who smokes less than 10 cigarettes per day, or an equivalent quantity of cigar or pipe smoke”.

Conversely, a current some day smoker refers to an occasional smoker, or “a person who has smoked at least 100 cigarettes in his or her lifetime, who smokes now, but does not smoke every day”.

For these data elements, grantees should report whether the respective tests were performed during the visit, rather than the actual result of the lab test. Please review the FPAR 2.0 Valid Values.

Grantees submitting a combined CSV file (encounter and lab data) should submit all data elements (including multiple lab tests ordered or performed during the encounter) on the same row. Grantees submitting a separate lab results CSV file should submit lab data elements on separate rows, even if the test was performed on the same day. For examples on how to report multiple tests from one encounter, please refer to the sample file.

For grantees that can submit encounter-level data for all data elements except lab results, we recommend first submitting an encounter-level file without lab data and then manually updating the FPAR tables to reflect lab results data.

We recommend that grantees implement plans to adopt or upgrade EHRs to submit encounter-level lab data for future submissions. Grantees should map tests and results available in their EHR to the most appropriate tests and FPAR 2.0 Valid Values responses.

OPA expects grantees following the preferred approach to provide both encounter-level and lab results data. There are two options for submitting lab results. In the first option, grantees can submit the encounter-level data and lab results data in one file. In the second option, grantees can submit their lab results data and encounter-level data separately. For further guidance on these options, please reference the sample file document.

For these data elements, grantees should report the actual result of the lab test. Please see FPAR 2.0 Valid Values for potential result options.

Grantees should report the result that aligns with the provider’s clinical care decision. For example, if the clinician decides to treat for the STI, then report the positive result. Grantees can find further instructions on how to report lab results by referring to FPAR 2.0 Valid Values. A sample file is also available on the website.

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.

Data Element 41 is the self-identified need for contraception, part of the eCQM under development at UCSF under grant funding from OPA. Because it is not yet an endorsed measure, it is to be reported only if (a) it is already included in the grantees’ EHR and (b) it is part of the clinical visit.

For Data Elements 42 and 43, “Unknown” would be reported if the family planning client was not asked about their sexual orientation or gender identity, respectively, while “Asked, but unknown” would be used if the family planning client was asked about their sexual orientation or gender identity but the family planning client declined to answer.

The FPAR data elements and response options were designed to align with Interoperability Standards and EHR Certification requirements (USCDI standards; ISA Standard Terminology). Thus, OPA does not determine the wording in the descriptions of codes used in FPAR reporting. The descriptions are formulated by the standards body creating the codes. Additional updates to the response options may be considered in the future.

back to top

Data Privacy

If a grantee is prohibited from sharing an exact date of birth, please submit the actual birth year and June 30, for example 2000-06-30 or 1992-06-30. The FPAR system converts dates of birth to an age. It also assigns age 50 to all clients 50 years and older. 

Additionally, OPA only has access to summarized, de-identified data (such as age instead of date of birth). OPA does not have access to birth dates. The contractor maintaining the FPAR system retains date of birth and other elements for one year after submission before they are destroyed.

Data are anonymized and all raw data, including personally identifiable information, are destroyed within a year of submission. For details on the data anonymization process for FPAR, please refer to the Integrating the Healthcare Enterprise 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.

The FPAR system complies with applicable U.S. Department of Health and Human Services (HHS) and federal regulations through completion of the HHS Enterprise Performance Life Cycle Framework, including the Authority to Operate process with cybersecurity and privacy review controls.

For more information, please review the brief, “How are FPAR Data Kept Safe?”

back to top

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. OPA strongly encourages grantees to develop a process based upon the grantee's organizational capacity and need for assessing the data from direct service sites 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 technical assistance (TA) development. OPA encourages all grantees and subrecipients to work directly with their EHR partners.

back to top

Data Submission/File Format

Data can be submitted in CSV (UTF-8 flat-file) format. A Sample File is available on the FPAR 2.0 section of the OPA website. The file provides an example of how to format a CSV file of Title X encounter and lab result data for submission to the FPAR system.

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 CSV file.

Grantees should submit a file containing all relevant encounters for the 12-month reporting period. Each encounter (that is, each row in the file) should contain encounter-level FPAR 2.0 data elements. Submissions are due annually. A Sample File is available on the FPAR 2.0 section of the OPA website.

Grantees are responsible for submitting encounter-level data to the FPAR system after collecting the data from their subrecipients.

Grantees are responsible for submitting encounter-level data to the FPAR system. Therefore, grantees are encouraged to assess data quality from subrecipients prior to submission. Grantees may need to work with subrecipients to resolve data quality issues identified with the FPAR system and by OPA after data are submitted. Please review the FPAR 2.0 Implementation Guide, FPAR 2.0 Valid Values, and Sample File.

Grantees will continue to submit FPAR data annually. OPA started collecting encounter-level data from grantees for the 2022 FPAR (submission in 2023). 

No, grantees should report using a single approach for a reporting cycle. Grantees who, for any reason, cannot submit FPAR 2.0 encounter-level data, should apply for a waiver so they can avail themselves of the alternate reporting option. Alternate reporting consists of grantee-level aggregate reporting. 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.

Grantees should submit a file containing all relevant encounters for the 12-month reporting period. Each encounter (that is, each row in the file) should contain encounter-level FPAR 2.0 data elements. A sample file is on the FPAR 2.0 section of the OPA website.

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.

The FPAR system allows grantees to submit their data electronically. The FPAR system automates 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. Grantees should review — and edit if necessary — the aggregate level data tables produced for them by the system, before they are considered final. Please review the FPAR 2.0 Implementation Guide.

Grantees can print a summary of their submission in the FPAR system. This PDF includes the date printed and the submission status in the header.

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.

A Data Quality Checklist can be found on the FPAR 2.0 section of the OPA website. The document describes the automatic checks conducted by the system.

We have published sample CSV file-layouts and other supplementary TA materials on the FPAR 2.0 section of the OPA website.

OPA holds the FPAR Data Portal Opening Webinar for grantees each year, which includes live demonstrations of the file upload process. These webinars are recorded and can be accessed through Connect.gov. Please reach out to your Project Officer on how to access Connect.gov.

Grantees should use the Data Validation Explorer to validate encounter-level data files before the submission period opens, without saving any data to the system (for example, to check for formatting issues, invalid values, and missing values). These validation checks are identical to the validation checks for encounter-level data files submitted during the main submission period. The Data Validation Explorer is available each fall to all FPAR system Grant Admin and Grant User account holders, including those reporting aggregate data.

back to top

Reporting

Grantees should continue to use FPAR numbers used in the past. New grantees should have been assigned new FPAR numbers. Grantees should check with their Project Officers if they do not know the FPAR number associated with their grant.

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 that Title X grantees provide in their communities. Grantees and OPA will have the ability to use dashboards and performance metrics for quality improvement projects, conduct data validation, produce custom analyses, and improve engagement and collaboration with OPA.

For Tables 7 and 8, users should be included in the row that corresponds to their most recent, nonmissing value for contraceptive method at exit (data element 19) during the reporting period. Users who do not report contraceptive method at exit on any encounter, either because they had STI-only encounters or for any other reason, should be included in “Unknown/unreported” row in Table 7 or Table 8.

The “Other (specify)” fields in Table 14 (Revenue Report), under the “Other Revenue” section do not have a character limit and all character types are accepted.

OPA will compare reporting rates for FPAR 2.0 data elements to FPAR 1.0 reporting rates at the grantee level, as well as historical trends across all grantees, to help assess data quality and data validity. Grantees should review and can edit the aggregate-level data tables produced for them by the FPAR system before the tables are considered final.

The FPAR system will be hosted in a secure, cloud-computing environment with robust capacity.

For the FPAR submission, all grantees are responsible for submitting sufficient data to produce the 14 FPAR tables (except for Table 10, which is discontinued). For grantees submitting encounter-level data, the FPAR system aggregates the encounter-level data and uses that to automatically populate the FPAR tables. Please note that grantees must manually enter data for Table 13 (Number of Full-Time Equivalent Clinical Services Providers and Family Planning Encounters by Type of Provider) and Table 14 (Revenue Report). 

After all encounters have been submitted, grantees should review the pre-populated tables. If the encounter-level data are complete and the pre-populated tables look accurate, then grantees will move directly to the data quality review step of the submission. Historically, these are the data quality checks that OPA performed after grantees provided the initial submission. For example, on Table 2 (Unduplicated Number of Female Family Planning Users by Race and Ethnicity), the FPAR system will note a data quality issue if race is unknown or not reported for 10 percent or more of female users.

We recognize that the encounter-level data may not be complete for all variables. For example, some of the grantees submitting encounter-level data may not be able to provide all data elements or may be missing encounter-level data from some of their service sites. In these cases, the pre-populated tables would not be complete and accurately reflect all services provided. Grantees can edit the pre-populated tables to fully reflect all services before moving on to the data quality review step of the submission.

A general comment feature was added to FPAR 2.0 on March 15, 2023. The general comment feature appears below the list of fourteen tables. Grantees can use it to provide additional context about their annual submission. Use of the general comment feature is optional. To provide notes about data quality issues, grantees should use the comment section that appears after the data quality issue within each table.

To resolve this issue, grantees will have to explicitly set the formatting of the date columns. When viewing the file in Excel, highlight all values in the two date columns. On the Home menu at the top is a submenu related to formatting. Look for the icons with the dollar sign, percent sign, and comma. At the bottom right of that submenu, there is a small button with an arrow. Select that button to expand the formatting menu.

Grantees should see a title that says “Category.” In the box underneath, select “Date.” In the menu that appears, select the example date value that is formatted as YYYY-MM-DD. 

Select OK. The date values should be updated to the correct format. Then select save. 

To confirm that the format of the dates is correct, grantees should open the file in Notepad or another plain text editor. 

Grantees may also see similar issues with long numbers. For example, Excel will automatically convert some of the valid values for Data Element 43 (Gender Identity) into scientific notation. Grantees must convert these values into text, or the file will trigger a data validation warning in the system. To convert these values into text, follow the steps noted above, and instead of selecting “Date” in the formatting menu, select “Text.” 

These reformatting steps need to be performed and grantees must save the file every time, whether changes were made to the file or not. 

A video demonstrating how to perform the steps for reformatting the data is available on Connect.gov, along with the transcript for the video.

For grantees uploading encounter-level data that include Data Element 43 – Gender Identity, CSV files may convert some of the valid LOINC values into scientific notation and create validation errors in FPAR 2.0. To avoid this validation error, we ask that you convert values to a text format and then save the file before uploading the data in the portal.

Follow these steps in your CSV file to format the values correctly:

  1. Select the entire column containing Data Element 43 – Gender Identity.
  2. Right-click once the column is selected, and select "Format Cells."
  3. Select “Text” from the options listed under "Category."
  4. Click “OK” and save your file.

A video demonstrating how to perform the steps for reformatting the data is available on Connect.gov, along with the transcript for the video. Please reach out to your Project Officer on how to access Connect.gov.

back to top

2024 Valid Values

No data elements have been added or deleted. The 2024 Valid Values File is a reference file listing all FPAR 2.0 data elements and acceptable values that may be used for the 2024 FPAR (to be submitted in 2025). The updated Valid Values file contains updated response options that may be easier to report (for example, insurance coverage type, payer for visit) and have more precise definitions. Moreover, newly added response options are responsive to requests to provide client-centered care. We are also beginning a transition to use SNOMED codes, which better align with industry standards for data interoperability. Response options for data elements will be updated to follow advancements of EHR standards for data interoperability. 

Response options were updated for 28 data elements in the Valid Values file. In addition, codes representing clinical tests now provide more specificity.

The Valid Values file indicates codes that will eventually be replaced to better align with data exchange standards HHS is adopting. 

During the transition period, the system will continue to accept Valid Values that grantees used prior to the 2024 edition of the Valid Values file. OPA has not determined a final date for accepting the transition values.

In December 2024, “LA46-8” (Other) and 74964007 (Other [qualifier value]) were added for Provider role (data element 3)

No other changes were made between the November 2024 and the December 2024 versions. Grant recipients should reference the latest version of the file (December 2024) for FPAR 2.0 data collection and reporting.

One of the key differences in the updated Valid Values file is a column with descriptions for each data element. The updated Valid Values file contains a README tab, DE Change Log tab, and Column Change Log tab, which provide a detailed list of updates to columns and Valid Values.

A transition value is a valid value (response option code) that OPA intends to retire in the future for any given FPAR element. Grantees can continue to report transition values until a transition date is finalized. Otherwise, grantees can start using new response options as soon as they are able.

OPA has not determined a final date for accepting the transition values.

OPA is initiating the transition to additional codes in order to keep FPAR 2.0 aligned with industry standards for health data exchange. We expect data standards to continue to evolve and encourage grantees to migrate to updated codes when feasible. Grantees can continue to submit previously released Valid Values until further notice. These new options can be used in place of, or in conjunction with, previously released codes.

Grantees can submit any valid value (new codes and previously published codes) contained in the 2024 Valid Values file for the 2024 FPAR (submitted in 2025).

back to top

The FPAR system can be accessed through https://fpar.opa.hhs.gov/.

A Grant Admin account will be created for the project director of your grant. The project director will then create additional Grant Admin or Grant User accounts. If an account has been created for you, you will receive an email with instructions on how to activate your account. If you have not received that email, please contact your Project Officer.

Grant Admins and Grant Users can view data upload and status, enter FPAR and grant data, run data quality checks, and access the reporting dashboard and Table Archive. A Grant Admin can also create a new Grant Admin or Grant User account for others, remove an existing account, and submit data for OPA review.

All passwords must contain at least eight characters, one number, one capital letter, and one special character—for example, a dollar sign ($), an exclamation point (!), or an ampersand (&). A green check mark appears to next to each criterion that the password meets. The system may also reject a password if the reentered password does not match the first password entry. Please ensure that there are no extra spaces for both password entries. A green check mark will indicate when the reentered password matches the first password entry.

Please make sure that the password was entered correctly. Capitalization and spaces matter, so please ensure that the capitalization is correct and that there are no extra spaces. If that does not work, you can reset your password by selecting “Forgot your password?” on the log-in page.

First, log into FPAR 2.0. In the navigation menu at the left, select “Users.” Then, select “Add user” on the page. Fill out the information requested in the pop-up that appears, then select “Save.” If you are a Grant Admin for multiple grants, please ensure that you are adding accounts in the right grant. The grant is displayed in the static banner at the top of the page.

First, navigate to the “Users” menu tab in the left navigation menu of FPAR 2.0. To remove a user account, select the “Remove” button next to the user’s name and confirm removal of the user. If you are a Grant Admin for multiple grants, please ensure that you are removing accounts in the right grant. The grant is displayed in the static banner at the top of the page.

If you receive verification codes through text message (SMS, or short message service) and your mobile phone number has not changed, there is nothing you need to do.

If you receive verification codes through SMS and your mobile phone number has changed OR you receive verification codes through Google Authenticator, you will need to update your MFA method.

First, log in to the FPAR system. Then, select your profile icon at the top right corner of the static banner and select “My Account.” Once you are on the User Profile page, select “Change MFA.” Finally, select the MFA method you prefer. If you select the text message method, you will be prompted to enter the new mobile phone number. If you select the Google Authenticator method, you must first download the Google Authenticator app on your new device and follow the steps outlined in the system.

The FPAR Dashboard is always available to grantees. New FPAR data will be made available once the FPAR National Summary Report is published. 

back to top

Waivers

Annual submissions allow Project Officers to check progress toward FPAR 2.0 transition and evaluate reporting-readiness. OPA will provide instructions for requesting a waiver for forthcoming FPAR submissions. If you have questions about requesting a waiver, please contact your Project Officer.

back to top

Clinic Locator Database

The Clinic Locator Database can still be accessed at https://reproductivehealthservices.gov, but the ability to edit your network has been moved to the FPAR system: https://fpar.opa.hhs.gov/. Users can edit information about subrecipients or service sites within the FPAR system. Log-in credentials for users with an existing FPAR 2.0 account remain the same. Individuals who do not currently have an FPAR 2.0 account can reach out to their Grant Admin or Project Officer to request an account. 

Yes, grantees can create Subrecipient User accounts to allow subrecipients to view and edit information about their service sites. Subrecipient users have the most restricted access and can access only features pertinent to the Clinic Locator Database and only for their subrecipient site or related service sites. They will not be able to access or edit anything related to a grantee’s FPAR data or submission or at the grantee’s level of Clinic Locator Database information.

Subrecipient Users only have access to the Clinic Locator Database features within the FPAR system. Subrecipient Users can view and edit their own information as well as the information for their service sites, but nothing at the grantee level or in the FPAR menus. 

Grant Admins and Grant Users can view and edit information for all subrecipients and service sites associated with their grant. 

In addition, Grant Admins will receive email notifications whenever a subrecipient or service site is added or removed or the address is updated. 

Grant Admins can create and remove Subrecipient User accounts for their grant. A Subrecipient User can create and remove other Subrecipient Users for their own subrecipients. Subrecipient User accounts can be created or removed by navigating to the “Users” menu tab in the navigation menu at the left. Further details on how to create a Subrecipient User account for the FPAR system can be found in the Clinic Locator Database User Guide, which can be accessed by navigating to the “Help” menu tab in the left navigation menu of the FPAR system.

If the information saved to the FPAR system indicates that the subrecipient does not provide any services at that location, the subrecipient will not be visible on the public facing website.

To link a service site to a subrecipient, the subrecipient must be created first. Once the subrecipient exists within the Clinic Locator Database, select the subrecipient from the “Associated Subrecipient” drop-down field when adding a new service site. Further details on how to link a service site to its associated subrecipient can be found in the Clinic Locator Database User Guide, which can be accessed by navigating to the “Help” menu tab in the left navigation menu of the FPAR system.

back to top

Technical Working Groups

OPA and their contractors used Title X program data to identify candidates for the TWGs to ensure they represented a range of experience in submitting FPAR data, number of subrecipients and service sites, geographic location, and EHR systems in use. The TWGs convened in 2020–2021. Grantee organizations who have participated in the TWGs are:

  • ABCD (Action for Boston Community Development) (Region 1)
  • University of Puerto Rico Medical Sciences Campus (Region 2)
  • New Jersey Family Planning League (Region 2)
  • AccessMatters (Region 3)
  • Georgia Family Planning System (Region 4)
  • Neighborhood Improvement Project, Inc. (Region 4)
  • Primary Care Medical Services of Poinciana, Inc. (Region 4)
  • Indiana Family Health Council, Inc. (Region 5)
  • Every Body Texas (Region 6)
  • Oklahoma State Department of Health (Region 6)
  • Colorado Department of Public Health and Environment (Region 8)
  • Montana State Department of Public Health (Region 8)
  • Essential Access Health (Region 9)
  • Idaho Department of Health and Welfare Family Planning Program (Region 10)

back to top