Capita Integration with ContactPoint

1
Capita Integration with ContactPoint

• Simon Pike One Product Manager

2
Glossary of terms

• DIS Detailed Integration Specification
• DSI Domain Specific Identifiers
• IDP Identity Provider
• RAO Reporting and Administration Organisation
• SAML Assertion Security Access Mark Up
• UID Unique Identifier

3
Overview

• What is ContactPoint?

Police
Education
Functionally, ContactPoint can be seen as a form
of centrally held telephone directory which
provides a view of children living in England and
the contact details of Practitioners working with
each child
PCT/Health
Social Care
Youth Justice
4
Timeline level of integration

• Revised timeline for delivery
• Release to Greenwich for User Acceptance Testing
  (UAT) March 2009
• Type Accreditation of eStart April 2009
• Instance Accreditation of eStart by Rochdale May
  2009
• Release to all eStart users June 2009
• Full integration including
• Data Feed
• Full Query
• Search and Retrieve in the software

5
How will data be sent?

• Initially information will come from 4 sources
• National Pupil Database
• NHS Spine
• Department for Work and Pensions (DWP)
• General Registrars Office (GRO)
• LAs are then responsible for
• Keeping the information as close to real time as
  practicable
• Ensuring that the data on ContactPoint is
  accurate
• Updating ContactPoint

6
What will be sent?

• Basic information on young people under 25
• Names
• DOB (will become mandatory)
• Gender
• Address
• Parent/Carer details - if available
• Involvement is registration at, or affiliation
  to, a Childrens Centre
• Name of the Children's Centre
• Name of Centre Manager
• Contact information for Children's Centre

7
Architecture
IdP
Messaging Queue
Children's Centre A
Microsoft SQL Server
Children's Centre B
Load Balancing Web Servers
8
GetConfig

• The GetConfig service provides eStart with
  information including
• Number of records (fragments) that can be
  included in each data load package
• Minimum time between data loads
• Error and Help information
• Lookup information
• This must be retrieved from ContactPoint at least
  once a day.
• Scheduled tasks to obtain GetConfig

9
SAML Assertions

• eStart must have valid system SAML Assertion
  (Certificate)
• System SAML Assertion expires every 3 days
  (7days)
• Access to ContactPoint will be denied if the
  system SAML Assertion has expired
• Expiration details for the system SAML Assertion
  is visible in eStart
• Obtaining system Assertion is a manual process

10
ContactPoint Management

• There will be a central management area to manage
  integration with ContactPoint
• Data Load queue management
• Error Warning management
• Assertion control
• Full Refresh
• GetConfig

11
(No Transcript)
12
Data Load

• Three different types of Data Load
• First Data Load
• Involvement information for the last year
• eStart involvement is registration at, or
  affiliation to, a Childrens Centre
• Childrens Centre is therefore classed as the
  involvement
• All young people under the age of 18 only
• Changes
• All information on that young person every time a
  change is made
• Full Refresh
• Once a year send a full refresh of current
  information and involvements
• Details of those who have died in the last 12
  months

13
Data Load

• DCSF have asked for as close to real time data
  load
• This means a batch process from eStart
• Creation of a queue of fragments to be sent
• All data for that record will be sent when a
  change is made
• eStart must have a valid system assertion in
  order to do Data Load
• An open session will be persisted whilst
  ContactPoint receives and responds
• Success
• Success and Match
• Error
• No Match or Multiple Match
• Stop Notices
• Warnings

14
Data Load

• Capture of data to be sent is done through a
  series of steps
• New triggers to capture the change
• Full record is added to the Microsoft Messaging
  queue
• Scheduled task uploads fragments to ContactPoint

15
Data Load
Messaging Queue
ContactPoint
16
Recording Consent

• Sending of information for under 18s does not
  require consent
• Consent to hold information on ContactPoint
• When the member is over 18

17
(No Transcript)
18
(No Transcript)
19
(No Transcript)
20
Search and Retrieve
21
Authentication

• Each user of ContactPoint will need to be
  authenticated with an Identity Provider (IdP)
• Each user must obtain a SAML Assertion to access
  ContactPoint
• This will have an expiration period
• If this expires that user wont be able to search
  ContactPoint
• Valid for ½ - 1 hour (controlled by IdP)
• No need to re-enter credentials for approx 2
  hours (controlled by IdP)
• If the system SAML Assertion has expired access
  to ContactPoint from the eStart will be denied

22
Search

• User must first obtain authentication against an
  IdP

First Search
IdP
23
Search
Subsequent Search
IdP
24
Search

• Search Type will be defaulted to Best View
• User can choose the search type
• Pre-defined list provided in the GetConfig
• Users must specify the reason for the search
• Pre-defined list provided in the GetConfig
• Once a search has been made list of matches will
  be shown

25
Retrieve

• View Type will be defaulted to Best View
• User can choose the view type
• Pre-defined list provided in the GetConfig
• Users must specify the reason for the retrieve
• Pre-defined list provided in the GetConfig

26
(No Transcript)
27
(No Transcript)
28
(No Transcript)
29
(No Transcript)
30
(No Transcript)
31
(No Transcript)
32
(No Transcript)
33
(No Transcript)
34
Simon PikeOne Product ManagerSimon.Pike_at_Capita.c
o.ukMobile 07795 827458 Paul MincherData and
Monitoring Officer Greenwich Council paul.mincher_at_
greenwich.gov.uk T 0208 921 3721