HTSI ExecutiveSummary_OCT2015_V5

3
http://solutions-network.org/site-htsi/ Human Trafficking Data Standards A basis from which to build better numbers on human trafficking The Problem Q: “How many victims are we talking about, just here in the US?” A: “Somewhere between 1,400 and 2.2 million.” The estimated number of humans trafficked in the United States alone varies by more than an order of magnitude. In any industry, achieving a measure of effectiveness within such a wide range would be impossible. Under such circumstances, sound policy decision-making gives way to emotional responses lacking fact-based evidence, funding requests to prevent trafficking and provide victim care appear dubious, and resources and efforts are easily misused when adequate measures of the problem remain so vague. Exhibit A: In 2000, activists estimated that 50,000 victims of forced labor and prostitution were trafficked into the United States every year. President Bush then authorized 42 Justice Department task forces and spent more than $150 million to find and help the estimated hundreds of thousands of victims. Between 2000 to 2007, they identified exactly 1,362 victims and filed fewer than 15 federal cases against traffickers. Exhibit B: After 10 years of publishing the annual Trafficking in Persons Report, the U.S. Department of State acknowledges that every figure in every chart pertaining to victims and cases of trafficking on every continent are “estimates only, given the lack of uniformity in national reporting structures.” The reasons behind the lack of quality data are real and challenging, including: security concerns, bendable and misunderstood definitions, mixed criminal elements, gray areas especially within labor trafficking definitions, lack of harmony among existing data sources, over and undercounting of participants, and simple unwillingness to share data. These challenges have been documented since 2002, and yet, the problem remains largely the same in 2015. The Envisioned Solution Clear data standards and standardized security protocols are the beginning of a solution - a groundwork that can help deliver better numbers and efficient continuity of care for survivors. Affected sectors and likely stakeholders include: agencies in the chain of care funding organizations interested in accurate reporting technology providers (e.g. IBM, Oracle, EMC) interested in security and transmission of data industries (e.g. mining, cocoa, shipping, fishing) wanting to eradicate nefarious acts in their logistics path the numbers on trafficking

Transcript of HTSI ExecutiveSummary_OCT2015_V5

Page 1: HTSI ExecutiveSummary_OCT2015_V5

http://solutions-network.org/site-htsi/

Human Trafficking Data Standards A basis from which to build better numbers on human trafficking

The Problem Q: “How many victims are we talking about, just here in the US?”

A: “Somewhere between 1,400 and 2.2 million.”

The estimated number of humans trafficked in the United States alone

varies by more than an order of magnitude. In any industry, achieving a

measure of effectiveness within such a wide range would be impossible.

Under such circumstances, sound policy decision-making gives way to

emotional responses lacking fact-based evidence, funding requests to

prevent trafficking and provide victim care appear dubious, and resources

and efforts are easily misused when adequate measures of the problem

remain so vague.

Exhibit A: In 2000, activists estimated that 50,000 victims of forced labor and prostitution were

trafficked into the United States every year. President Bush then authorized 42 Justice Department

task forces and spent more than $150 million to find and help the estimated hundreds of thousands of

victims. Between 2000 to 2007, they identified exactly 1,362 victims and filed fewer than 15 federal

cases against traffickers.

Exhibit B: After 10 years of publishing the annual Trafficking in Persons Report, the U.S. Department of

State acknowledges that every figure in every chart pertaining to victims and cases of trafficking on

every continent are “estimates only, given the lack of uniformity in national reporting structures.”

The reasons behind the lack of quality data are real and challenging, including: security concerns,

bendable and misunderstood definitions, mixed criminal elements, gray areas especially within labor

trafficking definitions, lack of harmony among existing data sources, over and undercounting of

participants, and simple unwillingness to share data. These challenges have been documented since

2002, and yet, the problem remains largely the same in 2015.

The Envisioned Solution Clear data standards and standardized security protocols are the beginning of a solution - a

groundwork that can help deliver better numbers and efficient continuity of care for survivors. Affected

sectors and likely stakeholders include:

❏ agencies in the chain of care

❏ funding organizations interested in accurate reporting

❏ technology providers (e.g. IBM, Oracle, EMC) interested in security and transmission of data

❏ industries (e.g. mining, cocoa, shipping, fishing) wanting to eradicate nefarious acts in their

logistics path

the numbers on trafficking

Page 2: HTSI ExecutiveSummary_OCT2015_V5

HTSI: the numbers on trafficking : http://solutions-network.org/site-htsi/

A standard:

❏ uses definitions to lessen confusion

❏ has well-defined sets of structured data (specific labels, names and values)

❏ can be the backbone for cooperation

❏ can be used to derive meaningful statistics

❏ is constantly reviewed for applicability and efficacy, can be pruned or expanded

❏ can be the basis for auditing agencies’ processes, both internally and externally

Some relevant historical examples of both international and private standards:

802.11 Internet Protocol After 9 years of negotiation, the 802.11

committee finally agreed on definitions

and drew up a standard acceptable to

75% of the committee members. Now,

this standard enjoys global adoption

by all companies wishing to support

the seamless transfer of data,

wirelessly.

Healthcare HL7 (CCD) The Consolidation Project team analyzed

and compiled several competing forms and

tools, finally creating a fully compliant CCD

document, then layering in the additional

HITSP, IHE and Stage 1 Meaningful Use

constraints. It provides a means for one

healthcare practitioner, system, or setting

to aggregate all of the pertinent data about

a patient and forward it to another user to

support the continuity of care.

CARFAX

In 1984, Edwin Barnett III started

selling CARFAX reports based on

10,000 vehicle records he obtained. To

grow, Barnett knew his company would

need far greater access to vehicle

records. In nine years' time, CARFAX

was receiving automobile records from

all 50 states. Within 20 years, 3 billion

records were generated by dealers

and shops feeding standardized data

into the system.

The Project and Deliverables Resolve/HTSI envision a three-phase project to develop and solidify data standards, standardized

security protocols, and form an independent Standards Committee.

Phase One Phase Two Phase Three

1. Preliminary Standard to be

Prototyped

2. Preliminary Standards

Committee Formed

3. Results of Prototype Data

Transfer between Agencies

Available

1. Results of Data Transfer

between Agencies

2. Refined Standard

3. Stable Standards

Committee

4. Better numbers achievable

in testing areas

1. Widespread Global Adoption

in public and private sectors

2. Robust Standards Committee

3. Ongoing Evangelization

4. Better global numbers

achievable

Months 1-8 Months 9-33 Month 34 onward

Page 3: HTSI ExecutiveSummary_OCT2015_V5

HTSI: the numbers on trafficking : http://solutions-network.org/site-htsi/

Phase One (months 1 - 8)

➔ Observation of how data is used between agencies at least 12 agencies (4 agencies in 3

countries), uncovering points of agreement and negotiation. On-the-ground observation

identifies and assesses how data is captured and read in each participating agency, identifies a

minimum set of data, finds sets of values that make sense, and determines what data creates

the most understanding and least confusion.

➔ Develop alliances with the public sector, research and think tanks, commercial tech firms and

other stakeholders (e.g. funders, advocates).

➔ Normalize data for preliminary standard to include common attributes, minimum sets, and

boundary conditions.

➔ Develop preliminary Standards Committee that will eventually mature to independence over

the course of the project.

Phase Two (2 years / months 9 - 33)

➔ Refine and solidify Standards Committee, including bi-annual meetings, committee reporting,

and committee-lead monitoring and evaluation of preliminary standard.

➔ Expand research to include additional agencies to increase breadth and scope of input.

➔ Expand research with legacy agencies to hone definitions and troubleshoot protocols.

➔ Begin evangelizing the standards through conferences, stakeholders, and other forums.

Phase Three (5 years / months 34++)

➔ Standards Committee evangelizes the product globally.

➔ Standard is refined at an international context level.

➔ Standards Committee takes over 100% of product evolution.

➔ Standard becomes promoted as a basis for compliance in grant funding.