Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-settings.php on line 512

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-settings.php on line 527

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-settings.php on line 534

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-settings.php on line 570

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_Page::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1199

Strict Standards: Declaration of Walker_PageDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1244

Strict Standards: Declaration of Walker_Category::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_Category::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1391

Strict Standards: Declaration of Walker_CategoryDropdown::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/classes.php on line 1442

Strict Standards: Redefining already defined constructor for class wpdb in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/wp-db.php on line 306

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/cache.php on line 103

Strict Standards: Redefining already defined constructor for class WP_Object_Cache in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/cache.php on line 431

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/query.php on line 61

Deprecated: Assigning the return value of new by reference is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/theme.php on line 1109

Strict Standards: Declaration of Walker_Comment::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/comment-template.php on line 1266

Strict Standards: Declaration of Walker_Comment::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/comment-template.php on line 1266

Strict Standards: Redefining already defined constructor for class WP_Dependencies in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/class.wp-dependencies.php on line 31

Strict Standards: Redefining already defined constructor for class WP_Http in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/http.php on line 61

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-content/plugins/wp-db-backup/wp-db-backup.php on line 106

Strict Standards: Redefining already defined constructor for class remix_advanced_editor in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-content/themes/AdoptionDashboard2.3/editor/remix_advanced_editor.php on line 27

Strict Standards: Declaration of Walker_Category_Checklist::start_lvl() should be compatible with Walker::start_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-admin/includes/template.php on line 430

Strict Standards: Declaration of Walker_Category_Checklist::end_lvl() should be compatible with Walker::end_lvl(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-admin/includes/template.php on line 430

Strict Standards: Declaration of Walker_Category_Checklist::start_el() should be compatible with Walker::start_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-admin/includes/template.php on line 430

Strict Standards: Declaration of Walker_Category_Checklist::end_el() should be compatible with Walker::end_el(&$output) in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-admin/includes/template.php on line 430

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method Add_to_Any_Subscribe_Widget::init() should not be called statically in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/plugin.php on line 339

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method cformsRSS::vars() should not be called statically in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/plugin.php on line 166

Deprecated: Function eregi() is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-content/plugins/statpress/statpress.php on line 1138

Deprecated: Function eregi() is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-content/plugins/statpress/statpress.php on line 1139

Deprecated: Function eregi() is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-content/plugins/statpress/statpress.php on line 1140

Deprecated: Function eregi() is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-content/plugins/statpress/statpress.php on line 1141

Deprecated: Function ereg() is deprecated in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-content/plugins/statpress/statpress.php on line 978

Strict Standards: Only variables should be assigned by reference in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/query.php on line 1465

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method cformsRSS::outputRSS() should not be called statically in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/plugin.php on line 339

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 55

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 41

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 50

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 52

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 54

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CEST/2.0/DST' instead in /homepages/45/d156462669/htdocs/adoptiondashboard/wp-includes/functions.php on line 55
Haiti - Earthquake | Adoption Dashboard

Haiti - Earthquake

FROM THE U.S. DEPARTMENT OF STATE

January 22, 2010

The Department of State is receiving inquiries from American citizens deeply touched by the plight of children in Haiti in the aftermath of the January 12 earthquake.

As Secretary of State Clinton said on January 20, “Children are especially vulnerable in any disaster, especially those without parents or other guardians to look after them.  This devastating earthquake has left many in need of assistance, and their welfare is of paramount concern as we move forward with our rescue and relief efforts.”

Together with the Department of Homeland Security, the State Department is processing and evacuating as quickly as possible those orphans who were identified for adoption by American citizens before the earthquake.

We understand that other Americans, moved by images of children in need, want to open their homes and adopt other Haitian children who had not been identified for adoption before the earthquake.  The State Department advises against this course of action at this time.  Intercountry adoption involves strict safeguards and legal requirements that must be met to protect children from illegal adoptions, abduction, sale and child-trafficking as well as to ensure that any adoption is in the best interests of the child.

Before a child can be legally taken to the United States for adoption, the Governments of both the United States and the child’s country of origin must first determine that the child is indeed an orphan.  It can be extremely difficult during the aftermath of a natural disaster to ascertain whether children who appear to be orphans truly are eligible for adoption.  Children may be temporarily separated from their parents or other family members, and their parents or family members may be looking for them.  Moreover, it is not uncommon in an emergency or unsettled situation for parents to send their children out of the area, or for families to become separated during an evacuation.  Efforts to reunite such children with relatives or extended family should be given priority.

In addition, some children who had been residing in orphanages before the earthquake were placed there temporarily by parents who could not care for them.  In most of these cases the parents did not intend to permanently give up their parental rights.  Even when it can be demonstrated that children have indeed lost their parents or have been abandoned, reunification with other relatives in the extended family should be the first option.

During times of crisis, it can also be exceptionally difficult to fulfill the legal requirements for adoption of both the United States and the child’s country of origin.  This is especially true when civil authority breaks down or temporarily ceases to function.   It can also be difficult to gather documents necessary to fulfill the legal requirements of U.S. immigration law.

The United States is cooperating directly with UNICEF and other relief organizations in Haiti to deliver needed supplies to Haiti’s orphanages and to provide assistance to other unaccompanied children.  UNICEF is starting the process of registering unaccompanied children and will seek to unite children with relatives.

There are many ways in which U.S. citizens can help the children of Haiti now.   For example, individuals who wish to assist can make a financial contribution to a reputable relief or humanitarian organization working in that country.

More Information

http://www.state.gov/

http://blogs.state.gov/index.php/site/entry/disaster_haiti#C1817

United States Agency for International Development (USAID)

International Committee of the Red Cross (ICRC)

Interaction

http://www.unicef.org/media/media_52519.html