Null

CAD DATA SHARING AGREEMENT
BETWEEN
THE DEPARTMENT OF FIRE AND EMERGENCY MEDICAL SERVICES

OF THE DISTRICT OF COLUMBIA,
THE METROPOLITAN POLICE DEPARTMENT

OF THE DISTRICT OF COLUMBIA,
THE OFFICE OF UNIFIED COMMUNICATIONS

OF THE DISTRICT OF COLUMBIA
AND
THE OFFICE OF THE CHIEF TECHNOLOGY OFFICER

OF THE DISTRICT OF COLUMBIA
I INTRODUCTION
This Data Sharing Agreement (“Agreement”) is entered into between the Department of
Fire and Emergency Medical Services (“DC Fire & EMS”), the Metropolitan Police
Department (“MPD”), the Office of Unified Communications (“OUC”) and the Office
of the Chief Technology Officer (“OCTO”) in order to permit the Citywide Data
Warehouse (“CityDW”) to access and use Computer Aided Dispatch (“CAD”) system
data for the purpose of supporting the CapStat program. The execution of this
Agreement will assist the District and DC Fire & EMS with improvement activities,
including outcomes evaluation. It is understood that patients’ rights under The Health
Insurance Portability and Accountability Act (HIPAA) still attach (are not forfeited)
through this sharing activity.
II PROGRAM GOALS AND OBJECTIVES

CityDW is a program operated by OCTO for the purpose of data collection, integration,
and analysis. CityDW enters into agreements with District agencies to collect their
operational data, store the data in a centralized location, and make the data available to
other District of Columbia staff via reporting and other tools.
The CAD data is currently owned and managed in a combined effort by three agencies:
DC Fire & EMS, MPD and OUC. Live data relating to both MPD and DC Fire & EMS
communications resides at the OUC. Per the Memorandum of Understanding between
MPD and OUC dated November 10, 2004, OUC maintains custody and control of
communications tape recordings. MPD owns all police-related data, and DC Fire &
EMS owns all fire-related data.
CapStat is a performance-based accountability program led by the Office of the City

Administrator (“OCA”). CapStat aims to increase government transparency and support
DEPARTMENT OF FIRE AND EMERGENCY MEDICAL SERVICES, METROPOLITAN POLICE DEPARTMENT, OFFICE OF UNIFIED
COMMUNICATIONS AND OFFICE OF THE CHIEF TECHNOLOGY OFFICER
accountability in the government of the District of Columbia through data-driven

“Accountability Sessions.” Effective execution of these sessions requires that CAD
system data be accessible to all OCA CapStat analyst staff.
Page 2 of 13
III SCOPE OF SERVICES

A Obligations of OCTO
1. OCTO will use the CAD data only as described below:
a. CityDW will use the CAD data for the purpose of information and analysis
supporting the CapStat program of the Office of the City Administrator. All data
specified in the Exhibit B Figure 1 and Figure 2 will be available to CapStat
analysts. Fields listed in the Exhibit B Figure 3 will be used by CityDW to
generalize addresses to a block level. Only block-level addresses and
coordinates will be made available to CapStat analysts. Any addressing
information must not reflect exact addresses. To avoid potential risk to citizens,
complainants, and witnesses, CityDW will not publish exact addresses.
b. If requested, CityDW can provide additional data extracts and summary reports
based on the CAD data. Each extract or report containing MPD data should be
approved by either the Director of the Research and Analysis Branch or their
designee or the Director of the Crime Data Quality Branch (MPD) or their
designee. Each extract or report containing DC Fire & EMS data should be
approved by the Information and Privacy Officer for DC Fire & EMS (DC Fire
& EMS) or their designee and by either the Chief Information Officer or his
designee or the Assistant Fire Chief or their designee (DC Fire and EMS). For
each extract or report containing DC Fire & EMS data appropriate steps should
be taken to ensure compliance with Health Insurance Portability and
Accountability Act regulations. A specific extract or report is considered
approved after an identified above agency representative signs the Data Release
Form found in Exhibit C. CityDW will provide DC Fire & EMS and MPD at
least 3 business days lead time to approve the extract or report prior to releasing
it.
c. CityDW will provide DC Fire & EMS, OUC and MPD with access and the
ability to query the corresponding agency CAD data through the Business
Objects toolset in use now by CapStat analysts. Up to five (5) named user
accounts will be created for DC Fire & EMS and (5) named user accounts for
MPD.
2. OCTO will ensure the requested DC Fire & EMS, MPD, and OUC disclaimers are
included with CAD data, regardless of distribution format.
3. CityDW will require any company that provides staff who have access to CAD data
to sign the OUC Non-Disclosure Agreement (Exhibit A). CityDW will provide to
OUC copies of all such non-disclosure agreements, and make them available to
MPD and DC Fire & EMS upon request. CityDW will require any staff that have
access to CAD data to sign the MPD Non-Disclosure Agreement (Exhibit D).
Page 3 of 13
CityDW will provide to MPD copies of all such non-disclosure agreements, and
make the signed agreements available to OUC and DC Fire & EMS upon request.
4. CityDW will provide to DC Fire & EMS, MPD, and OUC a list of all CityDW
employee and contract staff that have access to CAD data, and will update this list
whenever there is a change.
5. CityDW will ensure that the data provided through its applications matches CAD
source data. CityDW disclaims all responsibility for the completeness or accuracy
of CAD source data.
6. CityDW will conduct the transfer of CAD using the process described in Exhibit B.
7. All employees and contractors that have access to the data, and have signed the
Non-Disclosure Agreements required by Section III A 3, must also be certified as
having HIPAA Awareness Training and must have a current fingerprint and
background check in order to access MPD and DC Fire & EMS data streams. MPD
will conduct and fund the background and fingerprint checks, and all background
checks will go back a minimum of 10 years.
B Obligations of DC Fire & EMS and MPD

1. DC Fire & EMS and MPD will grant CityDW access to all CAD data specified in
Exhibit B.
C Obligations of OUC
1. OUC will provide CityDW access to CAD data as described in Exhibit B.
2. OUC will assist in the maintenance of the CAD data load process as described in
Exhibit C.
3. OUC will assist in data quality assurance efforts as required.
IV DURATION OF THE AGREEMENT

The period of this Agreement shall be from one year after the execution of the last signatory to
the Agreement by all parties. The Agreement shall automatically renew each year unless
terminated in writing by the Parties 60 calendar days prior to the expiration.
V CONFIDENTIAL INFORMATION
The Parties to this Agreement will use, restrict, safeguard and dispose of all information related
to services provided by this Agreement, in accordance with all relevant federal and local statutes,
and Health Insurance Portability and Accountability Act regulations.
VI TERMINATION
Any Party may terminate this Agreement in whole or in part by giving 60 calendar days advance
written notice to the other Party.
VII NOTICE
Page 4 of 13
The following individuals are the contact persons for each Party under this Agreement (at the
time of signing).
Party Name Title Phone Email

DC Fire & Demetrios Chief Information (202) 673-3256 demetrios.vlassopo
EMS Vlassopoulos Officer (office) ulos@dc.gov
(202) 673-2848
(fax)
DC Fire & Tisa Smith Information and 202-673-3297 tisa.smith@dc.gov
EMS Privacy Officer for (office)
FEMS 202-462-0807
(Fax)
MPD Travis Hudnall Chief Information (202) 727-8599 Travis.Hudnall@dc
Officer (office) .gov
(202) 727-3896
(fax)
OCTO David Strigel CityDW Program (202) 478-5958 David.Strigel@dc.g
Manager (office) ov
(202) 478-
5844 (fax)
OUC James Callahan CAD Technology (202) 230-6034 James.Callahan@d

Manager (office) c.gov
VIII SPECIFIC INFORMATION TO BE PROVIDED AND MODIFICATIONS

The list of data that will be used by CityDW is attached as Exhibit B, and may be amended from
time to time. Any such request by CityDW to amend Exhibit B shall be provided to MPD and
DC Fire & EMS in writing in the form of amended Exhibit B. The request(s) will be deemed
approved if the approval lines of the amended Exhibit B contain the signatures of the Chief
Information Officer or their designee or the Assistant Fire Chief or their designee (DC Fire &
EMS) and either of the Directors mentioned in Section III.A.1.b (MPD) or their designee.
IX MISCELLANEOUS
The Parties shall comply with all applicable laws, rules, and regulations whether now in force or
hereafter enacted or promulgated.
X EFFECTIVE DATE
This Agreement shall be effective immediately upon execution of the last signatory to this
Agreement.
IN WITNESS WHEREOF, the individuals named below warrant that they have the authority to
and do bind their respective agencies to the terms of this Agreement.
Page 5 of 13
For the Metropolitan Police Department:
________________________________________ ________________________
Cathy Lanier Date
Chief of Metropolitan Police Department
For the Office of the Unified Communications:
________________________________________ _______________________
Janice Quintana, Date
Director, Office of Unified Communications
For the Fire and Emergency Medical Services:
________________________________________ ________________________
Dennis L. Rubin Date
Chief of Fire and Emergency Medical Services
For the Office of the Chief Technology Officer:
________________________________________ ________________________
Vivek Kundra Date
Chief Technology Officer
Page 6 of 13
EXHIBIT A
NONDISCLOSURE AGREEMENT
This Agreement is entered into this ___ day of ________, 2008 by and among
_____________________ (hereinafter "Recipient") and the Office of Unified Communications,
Government of the District of Columbia (hereinafter “OUC”), with the office at 2720 Martin
Luther King Jr. Avenue, S.E., Washington, DC 20032.
RECITALS
A. The OUC possesses confidential and proprietary Data (hereinafter collectively “Data”)
pertaining to OUC Call Center Operations Data.
B. The OUC wishes to disclose to Recipient the Data for the purpose of gathering requirements
and support of OUC and Citywide Data Warehouse projects. This disclosure includes all
communication of Data between the parties in any form whatsoever, including oral, written,
and machine readable form, pertaining to the above.
C. The OUC is willing to disclose the Data, and Recipient is willing to receive the Data on the
terms and conditions set forth herein.
Therefore, the OUC and Recipient agree as follows:
1. The disclosure of Data by the OUC is in strictest confidence and thus Recipient will:
a. Take all steps reasonably necessary to protect the secrecy of the Data, and to prevent the
Data from falling into the possession of unauthorized persons;
b. Use the Data only for the purpose of gathering requirements and support of OUC and
Citywide Data Warehouse projects;
c. Report any disclaimers standard to reporting the Data, to be provided by DC Fire &
EMS, MPD, OCTO and OUC personnel.
d. Restrict disclosure of the Data solely to those employees of Recipient having a need to
access such Data in order to accomplish the purpose stated above; and,
e. Advise each such employee, before he or she receives access to the Data, of the
obligations of Recipient under this Agreement, and require each such employee to
maintain those obligations.
2. This Agreement imposes no obligation on Recipient with respect to any portion of the Data
received from the OUC which (a) was known to Recipient prior to disclosure by OUC, (b) is
lawfully obtained by Recipient from a third party under no obligation of confidentiality, (c) is
or becomes generally known or publicly available other than by unauthorized disclosure, (d)
is independently developed by Recipient or (e) is disclosed by OUC to a third party without a
duty of confidentiality on the third party.
Page 7 of 13
3. The obligations of this Agreement shall be continuing until the OUC notifies Recipient the
obligations are no longer in effect or a Data Sharing Agreement regulating the use of Data is
signed by the Office of Unified Communications and the Office of the Chief Technology
Officer. Recipient’s obligations of confidentiality of the Information disclosed by the District
shall survive termination of this Agreement and the contract under which they have been
engaged.
4. In the event of a breach or threatened breach or intended breach of this Agreement by

Recipient, the disclosing party is entitled to terminate the agreement and to have the recipient
immediately return all data disclosed in any form.
5. The validity, construction, and performance of this Agreement are governed by the laws of
the District of Columbia.
6. The rights and obligations of the parties under this Agreement may not be sold, assigned, or
otherwise transferred.
IN WITNESS WHEREOF, the parties have executed this Agreement effective as of the date
first written above.
Office of Unified Communications

District of Columbia Government
2720 Martin Luther King Jr. Ave, S.E.
Washington, DC 20032
Signed: ___________________________
Print Name:________________________
Title: _____________________________
Date: _____________________________
[Recipient’s name and address]

_________________________
_________________________
_________________________
_________________________
Signed: ______________________________
Print Name: ___________________________

Title: ________________________________
Page 8 of 13
EXHIBIT B
ATTACHMENT
TO THE DATA SHARING AGREEMENT BETWEEN
THE DEPARTMENT OF FIRE AND EMERGENCY MEDICAL SERVICES OF THE
DISTRICT OF COLUMBIA, THE METROPOLITAN POLICE DEPARTMENT OF THE
DISTRICT OF COLUMBIA, THE OFFICE OF UNIFIED COMMUNICATIONS
OF THE DISTRICT OF COLUMBIA AND THE OFFICE OF THE CHIEF
TECHNOLOGY OFFICER OF THE DISTRICT OF COLUMBIA
DATA ITEMS REQUESTED BY CITYDW, APPROVED BY DC FIRE & EMS AND

MPD
1. The data used by CityDW shall be as follows:
A subset of the current CAD data will be used by CityDW (OCTO) for the purposes of this Data
Sharing Agreement. Figure 1 shows a detailed specification of the data to be provided for DC
Fire & EMS. Figure 2 shows a detailed specification of the data to be provided for MPD. Figure
3 shows the fields from CAD table EVENT that will be used by CityDW to generalize addresses
to a block level. Only block-level addresses and coordinates will be made available to CapStat
analysts. In addition, Figure 4 shows a detailed specification of the response time summary
extract to be provided to CapStat by MPD on a monthly basis.
FIGURE 1
Specific fields to be provided for DC Fire & EMS data
From CAD table AEVEN

Field Description
sub_tycod The sub-type of the event type.
tycod Agency specified event type used to describe the event which has occurred
typ_eng Verbose description of the event type
From CAD table EVENT

Field Description
eid Unique Event Id Number generated by the system
FIGURE 3
The following fields from CAD table EVENT will be used by CityDW to generalize addresses to
a block level. Only block-level addresses and coordinates will be made available to CapStat
analysts.
Page 9 of 13
Fields from CAD table EVENT that will be used to generalize addresses to a block level. These
fields will not be available to CapStat analysts
Field Description
x_cord X map coordinate for the event's location
FIGURE 4
The following extract will be provided to CapStat analysts by MPD on a monthly basis. MPD
reserve the right to publish any disclaimer as it relates to the accuracy and authorization of the
response times.
Response time extract provided to CapStat analysts

Field Description
SDTS DATE AND TIME CALL CAME IN
EID UNIQUE IDENTIFIER
2. The technical means of transfer of data between OUC and CityDW systems shall be in
accordance with the following specifications:
OUC will push data to a mirror database in the Citywide Data Warehouse.
Data transfers will occur every thirty minutes.
If for any reason a reload of CAD data is required, initial notice will be provided to
OUC Primary Technical Contact; such a reload will, to the extent possible, occur on a
weekend or after normal business hours.
The CityDW Program Manager and Primary Technical Contact will be notified 4
(four) weeks in advance of any changes in CAD data schema.
The Primary OUC Contact Person to resolve any technical issues is Ethan Goldberg;
The Secondary OUC Contact Person is Stephen Williams; unresolved issues shall be
referred to James Callahan.
The Primary CityDW Contact Person to resolve any technical issues is Aleksey
Bykov; unresolved issues shall be referred to David Strigel.
EXHIBIT C
ATTACHMENT
TO THE DATA SHARING AGREEMENT BETWEEN
THE DEPARTMENT OF FIRE AND EMERGENCY MEDICAL SERVICES OF THE
DISTRICT OF COLUMBIA, THE METROPOLITAN POLICE DEPARTMENT OF THE
DISTRICT OF COLUMBIA, THE OFFICE OF UNIFIED COMMUNICATIONS
OF THE DISTRICT OF COLUMBIA AND THE OFFICE OF THE CHIEF
TECHNOLOGY OFFICER OF THE DISTRICT OF COLUMBIA
Page 10 of 13
DATA RELEASE FORM
CAD DATA RELEASE
I, [name/title], approve the release of the report/data identified below to the [identify reports/data
recipients] by the DC Government Citywide Data Warehouse for the purpose of [identify the
purpose of release].
_______________ ______________
[name] [date]
Reports/Data to be released to [identify reports/data recipients]:

[identify reports/data]
Page 11 of 13
EXHIBIT D
NONDISCLOSURE AGREEMENT
This Agreement is entered into this ___ day of ________, 2008 by and among
_____________________ (hereinafter "Recipient") and the Metropolitan Police Department ,
Government of the District of Columbia (hereinafter “MPD”), with the office at 300 Indiana
Avenue, NW , Washington, DC 20001.
RECITALS
D. The MPD possesses confidential and proprietary Data (hereinafter collectively “Data”)
pertaining to the Computer Aided Dispatch System Data.
E. The MPD wishes to disclose to Recipient the Data for the purpose of gathering requirements
and support of MPD and Citywide Data Warehouse projects. This disclosure includes all
communication of Data between the parties in any form whatsoever, including oral, written,
and machine readable form, pertaining to the above.
F. The MPD is willing to disclose the Data, and Recipient is willing to receive the Data on the
terms and conditions set forth herein.
Therefore, the MPD and Recipient agree as follows:
1. The disclosure of Data by the MPD is in strictest confidence and thus Recipient will:
f. Collect, receive, store and use the Data in strict compliance with federal and District laws
and regulations, and all rules, procedures and policies of MPD that are in force and
applicable during the period in which the Recipient has access to the Data;
g. Acknowledge the confidential nature of the Data and use the Data only for the purpose
of gathering requirements and support of MPD and Citywide Data Warehouse projects;
h. The Data although available to the Citywide Data Warehouse still remains the property of
MPD and must be treated with care and sensitivity. Any unauthorized sharing will result
in penalties.
i. Report any disclaimers standard to reporting the Data, to be provided by MPD personnel.
j. Restrict disclosure of the Data solely to those employees of Recipient having a need to
access such Data in order to accomplish the purpose stated above; and,
k. Advise each such employee, before he or she receives access to the Data, of the
obligations of Recipient under this Agreement, and require each such employee to
maintain those obligations.
2. This Agreement imposes no obligation on Recipient with respect to any portion of the Data
which (a) was known to Recipient prior to disclosure by MPD, (b) is lawfully obtained by
Recipient from a third party under no obligation of confidentiality, (c) is or becomes
generally known or publicly available other than by unauthorized disclosure, (d) is
Page 12 of 13
independently developed by Recipient or (e) is disclosed by MPD to a third party without a

duty of confidentiality on the third party.
3. The obligations of this Agreement shall be continuing until the MPD notifies Recipient the
obligations are no longer in effect or a Data Sharing Agreement regulating the use of Data is
signed by the Metropolitan Police Department and the Office of the Chief Technology
Officer. Recipient’s obligations of confidentiality of the Information disclosed by the District
shall survive termination of this Agreement and the contract under which they have been
engaged.
4. In the event of a breach or threatened breach or intended breach of this Agreement by

Recipient, the disclosing party is entitled to terminate the agreement and to have the recipient
immediately return all data disclosed in any form.
5. The validity, construction, and performance of this Agreement are governed by the laws of
the District of Columbia.
6. The rights and obligations of the parties under this Agreement may not be sold, assigned, or
otherwise transferred.
IN WITNESS WHEREOF, the parties have executed this Agreement effective as of the date
first written above.
Metropolitan Police Department

District of Columbia Government
300 Indiana Ave, NW.
Washington, DC 20001
Signed: ___________________________
Print Name:________________________
Title: _____________________________
Date: _____________________________
[Recipient’s name and address]
_________________________
_________________________
_________________________
Signed: ______________________________
Print Name: ___________________________

Title: ________________________________
Page 13 of 13

Null

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Null

Enviado por

Direitos autorais:

Formatos disponíveis

CAD DATA SHARING AGREEMENT

THE DEPARTMENT OF FIRE AND EMERGENCY MEDICAL SERVICES

THE METROPOLITAN POLICE DEPARTMENT

THE OFFICE OF UNIFIED COMMUNICATIONS

THE OFFICE OF THE CHIEF TECHNOLOGY OFFICER

II PROGRAM GOALS AND OBJECTIVES

CapStat is a performance-based accountability program led by the Office of the City

accountability in the government of the District of Columbia through data-driven

III SCOPE OF SERVICES

1. OCTO will use the CAD data only as described below:

B Obligations of DC Fire & EMS and MPD

IV DURATION OF THE AGREEMENT

Party Name Title Phone Email

OUC James Callahan CAD Technology (202) 230-6034 James.Callahan@d

VIII SPECIFIC INFORMATION TO BE PROVIDED AND MODIFICATIONS

For the Metropolitan Police Department:

For the Office of the Unified Communications:

For the Fire and Emergency Medical Services:

For the Office of the Chief Technology Officer:

Therefore, the OUC and Recipient agree as follows:

4. In the event of a breach or threatened breach or intended breach of this Agreement by

Office of Unified Communications

[Recipient’s name and address]

Print Name: ___________________________

DATA ITEMS REQUESTED BY CITYDW, APPROVED BY DC FIRE & EMS AND

1. The data used by CityDW shall be as follows:

From CAD table AEVEN

From CAD table EVENT

Response time extract provided to CapStat analysts

DATA RELEASE FORM

CAD DATA RELEASE

Reports/Data to be released to [identify reports/data recipients]:

Therefore, the MPD and Recipient agree as follows:

independently developed by Recipient or (e) is disclosed by MPD to a third party without a

4. In the event of a breach or threatened breach or intended breach of this Agreement by

Metropolitan Police Department

Print Name: ___________________________

Você também pode gostar