Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the fl-builder domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpdiscuz domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the restrict-user-access domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the google-analytics-for-wordpress domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the tribe-events-calendar-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the the-events-calendar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the gravityforms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /www/aspnephorg_573/public/wp-includes/functions.php on line 6121

Warning: Cannot modify header information - headers already sent by (output started at /www/aspnephorg_573/public/wp-includes/functions.php:6121) in /www/aspnephorg_573/public/wp-includes/rest-api/class-wp-rest-server.php on line 1896
{"id":14421,"date":"2024-06-12T17:14:00","date_gmt":"2024-06-12T21:14:00","guid":{"rendered":"https:\/\/aspneph.org\/?post_type=committee&p=14421"},"modified":"2025-04-10T10:26:52","modified_gmt":"2025-04-10T14:26:52","slug":"pfena","status":"publish","type":"committee","link":"https:\/\/aspneph.org\/committee\/pfena\/","title":{"rendered":"pFeNa"},"content":{"rendered":"","protected":false},"template":"","meta":{"_acf_changed":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0},"categories":[340],"class_list":["post-14421","committee","type-committee","status-publish","hentry","category-committee"],"acf":{"Committee_info":"The Pediatric Fellows in Nephrology Association (pFeNa) is an informal group that includes all pediatric nephrology fellows throughout the duration of their fellowship. An established component of the American Society of Pediatric Nephrology (ASPN), pFeNa meets at the national conferences of the ASPN and American Society of Nephrology (ASN). They participate in ASPN activities on an ongoing basis. pFeNa has reaffirmed the following goals:\r\n\r\nTo expand the information for nephrology fellows on the ASPN website.\r\n\r\nTo arrange social events at the national meetings for fellows and prospective fellows (residents) to meet each other and \u2018network.\r\n\r\nTo work with the ASPN Training and Certification Committee to enhance fellowship recruitment and training outcomes.\r\n\r\nAs such, pFeNa representatives are encouraged to participate on a number of ASPN committees, in particular those areas related to training, research, workforce, and website development.","co_chair1":[2128,2307],"chair1":2127,"restricted_content1":"[wpcode id=\"16541\"]\r\n\r\nNeed to communicate with your committee?\r\n