Social Care Systems And Subject Access Requests

There was a delivery error or similar, which needs fixing by the WhatDoTheyKnow team. Can you help by finding updated contact details?

Dear North Lincolnshire Council,

1. Who is the supplier of your current Adults social care case management system?

2. Do you have any plans to replace this system in the next 3 years?

3. Who is the supplier of your current Adults social care finance system?

4. Do you have any plans to replace this system in the next 3 years?

5. Who is the supplier of your current Children's social care case management system?

6. Do you have any plans to replace this system in the next 3 years?

7. Who is the supplier of your current Children's social care finance system?

8. Do you have any plans to replace this system in the next 3 years?

9. Who is the supplier of your current Education system?

10. Do you have any plans to replace this system in the next 3 years?

11. Do you have a backlog of Children's social care Subject Access Requests?

12. If so, approximately how many and what is the estimated date that this backlog will be cleared?

13. Do you use eLearning tools to support the use of your Children's and / or Adults Social Care case management systems?

14. If so, please specify. If not, do you have any plans to procure such tools in the next three years?

Yours faithfully,

Sarah Tomslin

Information Governance Team,

Dear Sarah Tomslin,

Thank you for your request which was received on 9th May. The estimate
response date for your request is the 7th June.

Should you have any queries, amendments or additions relating to this
request, please remember to quote the reference number above in any future
communications.

Yours Faithfully

Information Governance Team
North Lincolnshire Council

Information Governance Team,

1 Attachment

  • Attachment

    Information Disclosure FOI2023 00698.odt

    641K Download

Dear Sarah Tomslin,

I am writing in response to your request for information, that was
received on the 9th May. Please find our Information Disclosure letter
attached.

If we can be of any further assistance with regard to this request please
let us know quoting the above reference number.

Yours sincerely,

Information Governance Team
North Lincolnshire Council

Dear Information Governance Team,

Hi there the word document does not open could you please send your response again. Thankyou

Yours sincerely,

Sarah Tomslin

North Lincolnshire Council

2 Attachments

Your message to [email address] couldn't be delivered.
request wasn't found at ig.northlincs.gov.uk.
request-979204-8ca64. . . Office 365 request
Action Required Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the
following:
• Send the message again following these steps: In Outlook, open this
non-delivery report (NDR) and choose Send Again from the Report
ribbon. In Outlook on the web, select this NDR, then select the link
"To send this message again, click here." Then delete and retype the
entire recipient address. If prompted with an Auto-Complete List
suggestion don't select it. After typing the complete address, click
Send.
• Contact the recipient (by phone, for example) to check that the
address exists and is correct.
• The recipient may have set up email forwarding to an incorrect
address. Ask them to check that any forwarding they've set up is
working correctly.
• Clear the recipient Auto-Complete List in Outlook or Outlook on the
web by following the steps in this article: [1]Fix email delivery
issues for error code 5.1.10 in Office 365, and then send the message
again. Retype the entire recipient address before selecting Send.
If the problem continues, forward this message to your email admin. If
you're an email admin, refer to the More Info for Email Admins section
below.
Was this helpful? [2]Send feedback to Microsoft.
══════════════════════════════════════════════════════════════════════════
More Info for Email Admins
Status code: 550 5.1.10

This error occurs because the sender sent a message to an email address
hosted by Office 365 but the address is incorrect or doesn't exist at the
destination domain. The error is reported by the recipient domain's email
server, but most often it must be fixed by the person who sent the
message. If the steps in the How to Fix It section above don't fix the
problem, and you're the email admin for the recipient, try one or more of
the following:

The email address exists and is correct - Confirm that the recipient
address exists, is correct, and is accepting messages.

Synchronize your directories - If you have a hybrid environment and are
using directory synchronization make sure the recipient's email address is
synced correctly in both Office 365 and in your on-premises directory.

Errant forwarding rule - Check for forwarding rules that aren't behaving
as expected. Forwarding can be set up by an admin via mail flow rules or
mailbox forwarding address settings, or by the recipient via the Inbox
Rules feature.

Recipient has a valid license - Make sure the recipient has an Office 365
license assigned to them. The recipient's email admin can use the Office
365 admin center to assign a license (Users > Active Users > select the
recipient > Assigned License > Edit).

Mail flow settings and MX records are not correct - Misconfigured mail
flow or MX record settings can cause this error. Check your Office 365
mail flow settings to make sure your domain and any mail flow connectors
are set up correctly. Also, work with your domain registrar to make sure
the MX records for your domain are configured correctly.

For more information and additional tips to fix this issue, see [3]Fix
email delivery issues for error code 5.1.10 in Office 365.
Original Message Details
Created Date: 5/30/2023 9:53:22 AM
Sender Address: [FOI #979204 email]
Recipient Address: [email address]
Subject: Re: Freedom of Information - Ref: FOI2023/00698
Error Details
Error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address
lookup
Message rejected LO4P265MB6997.GBRP265.PROD.OUTLOOK.COM
by:
Notification Details
Sent by: LO4P265MB6997.GBRP265.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
5/30/2023 local (Exim 4.94.2) (envelope-from
1 9:53:22 foi mstrwdtkhexa.srv.mysociety.org <[FOI #979204 email]>) *
AM
5/30/2023 esmtps (TLS1.3) tls
2 9:53:23 mstrwdtkhexa.srv.mysociety.org mslb001hexa.srv.mysociety.org TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 1 sec
AM 4.94.2) (envelope-from
<[FOI #979204 email]>)
5/30/2023 Microsoft SMTP Server (version=TLS1_2,
3 9:53:23 mslb001hexa.srv.mysociety.org LO2GBR01FT006.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
5/30/2023 Microsoft SMTP Server (version=TLS1_2,
4 9:53:23 LO2GBR01FT006.eop-gbr01.prod.protection.outlook.com LO3P123CA0019.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
5/30/2023 Microsoft SMTP Server (version=TLS1_2,
5 9:53:23 LO3P123CA0019.GBRP123.PROD.OUTLOOK.COM LO4P265MB6997.GBRP265.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM

Original Message Headers

Received: from LO3P123CA0019.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:388::15)
by LO4P265MB6997.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:34e::11) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6455.21; Tue, 30 May
2023 09:53:23 +0000
Received: from LO2GBR01FT006.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:388:cafe::63) by LO3P123CA0019.outlook.office365.com
(2603:10a6:600:388::15) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6433.23 via Frontend
Transport; Tue, 30 May 2023 09:53:23 +0000
Authentication-Results: spf=pass (sender IP is 93.93.130.118)
smtp.mailfrom=whatdotheyknow.com; dkim=pass (signature was verified)
header.d=whatdotheyknow.com;dmarc=pass action=none
header.from=whatdotheyknow.com;
Received-SPF: Pass (protection.outlook.com: domain of whatdotheyknow.com
designates 93.93.130.118 as permitted sender)
receiver=protection.outlook.com; client-ip=93.93.130.118;
helo=mslb001hexa.srv.mysociety.org; pr=C
Received: from mslb001hexa.srv.mysociety.org (93.93.130.118) by
LO2GBR01FT006.mail.protection.outlook.com (10.152.42.92) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.6455.22 via Frontend Transport; Tue, 30 May 2023 09:53:23 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
d=whatdotheyknow.com; s=2020a.mysociety; h=Content-Transfer-Encoding:
Content-Type:Mime-Version:Subject:Message-ID:To:From:Date:Sender:Reply-To:Cc:
Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:
Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:
List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
bh=2URGhEObFXYHKsLhrM2Xdp3S2AZ456gSPjJEspMjdfo=; b=QFhEF6haJnVbJWzHHFJ/ZFowH+
h9m2EC63CxR2ghKjetlX9uNaYWvuXqO6Mr1KhVC0NwSzxmeUX2jVaSxrqax+yAB5LZUU9WHAN7RfU
JAMZkVYNyFhjNARKKd/P4g3iu4u6zBAyWo7JdkcZCu7/EWDf6MzxhxIqvC+8oGY3O9D9YEOrUmzs6
SVdz/9CtBSgZH9fNI0ECPCrhPGYKkNmrOpFD8CjX/x4L1d6165hInCZnl5OS6RZg5vyX+uGW9aGBo
bzRfuJZkykcGgfdumR1fsPUbshCYrjn8hC3pMsSHPpYtxTJfDyuVBOzxELDnix5dQRZTzJzsp68Jj
BMtUDoIQ==;
Received: from mstrwdtkhexa.srv.mysociety.org ([2a00:1098:82:dd::10:1]:41968)
by mslb001hexa.srv.mysociety.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
(Exim 4.94.2)
(envelope-from <[FOI #979204 email]>)
id 1q3w2d-00BNf8-5y
for [email address]; Tue, 30 May 2023 09:53:23 +0000
Received: from foi by mstrwdtkhexa.srv.mysociety.org with local (Exim 4.94.2)
(envelope-from <[FOI #979204 email]>)
id 1q3w2c-00Bg7d-NN
for [email address]; Tue, 30 May 2023 10:53:22 +0100
Date: Tue, 30 May 2023 10:53:22 +0100
From: Sarah Tomslin <[FOI #979204 email]>
To: Information Governance Team <[email address]>
Message-ID: <[email address]>
Subject: Re: Freedom of Information - Ref: FOI2023/00698
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-Path: [FOI #979204 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 586655ed-2cff-4089-8197-b4c10b7b3da3:0
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: LO2GBR01FT006:EE_|LO4P265MB6997:EE_
X-MS-Office365-Filtering-Correlation-Id: 937e9f4b-35a7-4a32-b695-08db60f3b532

References

Visible links
1. https://go.microsoft.com/fwlink/?LinkId=...
2. https://go.microsoft.com/fwlink/?LinkId=...
3. https://go.microsoft.com/fwlink/?LinkId=...