arrow-left

All pages
gitbookPowered by GitBook
1 of 6

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

IDEA Agreement

This is the final agreement between agency secretaries, including appendices. Note that this public version is unsigned. Additional signatories were added via addendum.

State employees can find the signed agreement in the .

file-pdf
262KB
Final_IDEA.pdf
PDF
arrow-up-right-from-squareOpen
teams channelarrow-up-right

Resources and References

In this section you will find key templates and other information to execute and understand the IDEA process. These materials are linked throughout the guide.

This section includes:

  • IDEA agreement

  • List of signatories

BUCP template
Notice, Email and Disclosure templates
Background materials

Background

IDEA was borne out of a need to improve sharing infrastructure within the state. Learn more about its history, benefits and implementation in the material below.

hashtag
IDEA Briefing Deck

This presentation introduces the IDEA process, including the background, rationale, process to develop, and scope.

file-pdf
3MB
BriefingDeck-IDEA.pdf
PDF
arrow-up-right-from-squareOpen

List of Signatories

This is a list of all state entities that have signed the agreement. This list is updated whenever a new signatory is added.

Please if you note any errors.

contact usarrow-up-right

Notice, Email and Disclosure Templates

hashtag
Template: Email to initiate a data exchange under IDEA

Subject: Request to exchange data under IDEA

Dear <insert Data Provider contact name>,

We are both Signatory Entities under the State of California’s Interagency Data Exchange Agreement (IDEA), the umbrella memorandum of understanding that is intended to facilitate data exchange between state entities. If you are unfamiliar with IDEA, you can learn more in the attached FAQ.

We are interested in exchanging the following information with your department and have drafted an initial Business Use Case Proposal (BUCP) as required by IDEA.

<Insert brief description of data and purpose>

At your convenience, we would like to meet and discuss this request with you. If you feel another contact is more appropriate, please feel free to let us know.

Best,

<insert Data Recipient name>

hashtag
Template: Planning for a BUCP Kickoff Meeting

Use this template to plan for your BUCP Kickoff Meeting.

Suggested attendees:

  • Data Recipient. Program contacts that are responsible for the business use case.

  • Data Providers. Program contacts that have a deep understanding of the data to exchange and can inform and even advise on the business use case needs.

Inputs to meeting:

  • Draft of BUCP (provided by Data Recipient)

  • List of available data fields to review and discuss (provided by Data Provider)

Meeting objective: Refine business use case needs and develop preliminary list of data fields

Meeting agenda:

  1. Introductions (All parties)

  2. Background on business use case purpose and importance (Data Recipient)

  3. Discussion of data needs in support of use case (All parties). Use this time to list and start to refine the list of data fields that would meet business use case. Flag (but don’t attempt to resolve) issues that would require legal or security input.

hashtag
Template: Notice of unauthorized access (provision 8.5)

Subject: Notice of unauthorized access to data exchanged under IDEA

Dear <insert Data Provider contact name>,

We are both Signatory Entities under the State of California’s Interagency Data Exchange Agreement (IDEA), the umbrella memorandum of understanding that is intended to facilitate data exchange between state entities.

Under IDEA, we negotiated a Business Use Case Proposal (BUCP), attached, in which you provided us with the following data: <insert brief description of data>.

Under provision 8.5 of IDEA, we are required to notify you that we experienced an instance of unauthorized access as follows:

<insert brief description of unauthorized access>.

Please let us know if you need any additional information to assess this instance of unauthorized access. We are able to meet at a time of your convenience. Further, our team is reviewing this instance of unauthorized access and identifying any remediations and future mitigation measures to prevent any future unauthorized access.

Best,

<insert Data Recipient name>

hashtag
Template: Notice of security incident (provision 8.6)

Subject: Notice of security incident involving data exchanged under IDEA

Dear <insert Data Provider contact name>,

We are both Signatory Entities under the State of California’s Interagency Data Exchange Agreement (IDEA), the umbrella memo of understanding that is intended to facilitate data exchange between state entities.

Under IDEA, we negotiated a Business Use Case Proposal (BUCP), attached, in which you provided us with the following data: <insert brief description of data>.

Under provision 8.6 of IDEA, we are required to notify you that we experienced a security incident relating to this data:

<insert brief description of unauthorized access and consider attaching a more detailed report>.

Please let us know if you need any additional information to assess this incident. We are able to meet at a time of your convenience. Further, our team is reviewing this incident and identifying any remediations and future mitigation measures to prevent any future security incidents.

Best,

<insert Data Recipient name>

hashtag
Template: Data disclosure language (provision 5.11)

Under IDEA, a Data Recipient may modify data and disclose it consistent with the signed BUCP. If disclosed, the Data Recipient must indicate that the data is modified and not original. We suggest including a footnote as follows:

Note: Our department is not the original source of this data. We have modified this data to support our own business needs. Any inconsistency with the original data is our responsibility.

hashtag
Template: Notice to terminate data exchange under IDEA (provision 5.14 - rule change)

Subject: Notice to terminate data exchange under IDEA

CC: Agency Chief Data Officer or the Agency Information Officer

Dear <insert Data Recipient contact name>,

We are both Signatory Entities under the State of California’s Interagency Data Exchange Agreement (IDEA), the umbrella memorandum of understanding that is intended to facilitate data exchange between state entities.

Under IDEA, we negotiated a Business Use Case Proposal (BUCP), attached, in which we provided you with the following data: <insert brief description of data>.

Under provision 5.14 of IDEA, we are terminating this agreement due to the following statutory, regulatory, or contractual change which now prohibits our ability to share the data under our BUCP:

<insert brief description of change and why this requires a termination and any time constraints or requirements for deletion/removal; consider attaching a more detailed report>.

We request to meet and discuss the steps involved in this termination.

Best,

<insert Data Provider name>

hashtag
Template: Notice to terminate data exchange under IDEA (provision 5.14 - Data Recipient’s Acts)

Subject: Notice to terminate data exchange under IDEA

CC: Agency Chief Data Officer or the Agency Information Officer

Dear <insert Data Recipient contact name>,

We are both Signatory Entities under the State of California’s Interagency Data Exchange Agreement (IDEA), the umbrella memorandum of understanding that is intended to facilitate data exchange between state entities.

Under IDEA, we negotiated a Business Use Case Proposal (BUCP), attached, in which we provided you with the following data: <insert brief description of data>.

Under provision 5.14 of IDEA, we are terminating this agreement due to your act as described below:

<insert brief description of Data Recipeint’s act that prompted this termination and why that act should lead to a termination. Describe time constraints or requirements for deletion/removal; consider attaching a more detailed report>.

We request to meet and discuss the steps involved in this termination.

Best,

<insert Data Provider name>

hashtag
Template: Notice to terminate data exchange under IDEA (provision 7.4)

Subject: Notice to terminate data exchange under IDEA due to cause

CC: Statewide Chief Data Officer and Agency Chief Data Officer or the Agency Information Officer

Dear <insert Data Recipient contact name>,

We are both Signatory Entities under the State of California’s Interagency Data Exchange Agreement (IDEA), the umbrella memorandum of understanding that is intended to facilitate data exchange between state entities.

Under IDEA, we negotiated a Business Use Case Proposal (BUCP), attached, in which we provided you with the following data: <insert brief description of data>.

Under provision 7.4 of IDEA, we request to terminate this agreement as we believe you, the Data Recipient has violated a material term of our agreement:

<insert brief description of violation and why this requires a termination and any time constraints or requirements for deletion/removal; consider attaching a more detailed report>.

We request to meet and discuss the steps involved in this termination.

Best,

<insert Data Provider name>

BUCP Template

This page contains both the BUCP template itself as well as a template for defining the data elements that may be used or adapted as the BUCP is developed.

hashtag
Template: BUCP

Use this Word document to draft your BUCPs. If needed, we will periodically update this based on feedback and include version notes.

circle-info

Identify next steps. Next steps should include at a minimum the following:

  1. How to finalize list of data elements that are in scope

  2. Legal and security input needed

Remember when you complete your BUCP to submit to the Statewide Chief Data Officerarrow-up-right

hashtag
Template: Data Field Definitions Template

One of the best ways to improve data use is to provide data that is well-documented. The data field definitions table below will help both the Data Provider and Recipient develop a shared understanding of the data to be exchanged.

Field

Description

Field Name

What is a brief human readable name for the field? This should be unique and stated in the singular. Don't use abbreviations or acronyms.

Type

What is the format of the data? Numeric, text, data and time, currency, boolean, coordinates, other.

Definition

Define the field. State it as a descriptive phrase or sentence. Be precise, unambiguous and concise. Make it unique and state it in the singular. State what it is, not what it is not. Can it stand alone? Define units of measure (e.g. miles or meters or feet).

hashtag

file-download
37KB
BUCP-Template-V1.0.docx
arrow-up-right-from-squareOpen

Required

Yes or No. Is this field required or optional?

Valid inputs

For categories, what is the list of allowable values? For date and numbers, what is the allowable range?

Source

Defines how the data enters the system.

Notes

Describe any known data quality issues or concerns.

Guide for use

Provide advice on how the field can be used.

https://www.youtube.com/watch?v=hbiMrH2H_pMwww.youtube.comchevron-right