You are here

Ed-Fi Integration Overview

WISEdata Logo

Ed-Fi Alliance Logo

 

 

Overview

The Wisconsin Department of Public Instruction (DPI) has adopted the Ed-Fi interoperability framework to streamline the collection of Local Education Agency (LEA) information and enhance the gathering of required state and federal data. LEAs must implement this framework within their certified student information system (SIS), financial data system, and other technology providers if they haven't already. The vendor's system will transmit data to DPI through an application programming interface (API) defined by the Ed-Fi framework, which is certified annually.

Integrating Your System
If you're working with an LEA and are not on the existing vendor list, integrating your system with the WI DPI Ed-Fi REST API is straightforward but does take some time. DPI aims to certify vendors, enabling school districts, charter schools, and private schools participating in a parental Choice program to submit data to DPI. Our goal is to make this process as easy as possible to minimize development costs and reduce time to market.

Becoming a Certified Vendor

At the DPI, we value our vendor relationships and strive to make onboarding as straightforward as possible.

Get Started!

Onboard. During this phase, we will meet with you to discuss your application and prepare for next steps. In addition, we’ll share resources and guidance on establishing a sandbox and coordinate check-ins to support your development progress.

Start by review the Ed-Fi and WISEdata Ed-Fi Documents to familiarize yourself with API technology, consider obtaining an Ed-Fi license (recommended), and ensuring programmers are familiar with RESTful services and basic HTTP authentication prior to filling out the application. DPI uses the Ed-FI API Framework.

Vendor Development and Verification. In this phase, your development team ensures that your product meets all specifications and successfully integrates with the WISEdata Ed-Fi API/ODS using the provided data values, descriptors and use cases. 

Integration Testing and Certification. The last phase is earning your certification status and being added to the certified Vendor List. Once vendors are DPI certified, they will be eligible to receive production credentials after an LEA adds them as an authorized vendor. Certification is an annual process going forward.

Vendor Certification Timeline and Process

 

If you are looking to become a newly certified vendor referred by an LEA, here’s a Vendor Certification Timeline Summary:

  • Application Period: July 1st - October 31st
  • Follow-Up and Interviews: Completed by December 1st
  • Selection Announcement: January 10th
  • Planning and Training: By February 28th
  • Integration Testing: April - July
  • Certification Announcement: By July 31st

Preparation Checklist

Once you have completed the “Getting Started” phase, DPI will provide the necessary support to ensure you have the tools needed for integration.

  • Access to the 'Sandbox'/User Acceptance Test Environment: A Wisconsin Access Management System (WAMS) ID is required to access the Ed-Fi Credential Application. This credential application is required to obtain the Key, Secret, and URLs needed to connect to the API UAT 'Sandbox' and use Swagger.
  • Resources: Available on the Vendor Resources page, you’ll find development resources including the use cases to support your efforts.

Integration Testing and Certification

Once your development is complete, we recommend executing unit testing and system testing to detect and resolve errors before proceeding with integration testing. When you are confident in your code, schedule a certification session. DPI conducts live testing sessions with vendors to evaluate service integration, data interpretation, and UI-specific error conditions.

Lastly, once vendors are DPI certified, they are added to the certified Vendor List and will be eligible to receive production credentials after an LEA adds them as an authorized vendor. Our certification process is required annually, with requirements for the next year being shared at a Vendor Conference in March and a testing window between April and July (subject to change).

Please visit the Vendor Resources page for further helpful information.

Got questions? Vendors can reach out to us using the Vendor Access and Inquiry form.