Nid ydym yn gwybod a yw'r ymateb mwyaf diweddar i'r cais hwn yn cynnwys gwybodaeth neuai peidio - os chi ywCarolyn Tuson mewngofnodwch a gadael i bawb wybod.

Policy information request

We're waiting for Carolyn Tuson to read a recent response and update the status.

Dear Somerset Integrated Care System,

I would like to request the following information under the Freedom of Information Act in relation to the research I am completing.

Having reviewed your website and policies, I am unable to obtain the relevant documents, which is why I have made this request. I would like to know which documents are used for the review and approval of new medical devices within your NHS Trust/entity.

The exact naming of the documents may differ, but the context is the same, so we ask for judgement to be used, and please let us know if you require further clarification.

1. Could you please provide a copy of the Trusts/entity“New Medical Device policy?”
2. Could you please provide a copy of the Trusts/entity“Medical Devices and Procurement Review Group policy?”
3. Could you please provide a copy of the Trusts/entity“Business case template for new medical devices or technology” for new medical/diagnostic device approval?
4. Could you please provide a list of all approved medical devices in your Trusts/entity? Excel format, word or PDF is fine.
5. Could you please provide a copy of the policy which supports “medical devices on trial requirements”.
6. Could you please provide the policy for including a new pathology test within the Trusts/entity?
7. Could you please provide the policy for the “New medical Product Selection Group”
8. Could you please confirm how often new medical device review meetings take place?
9. Could you please provide me the name of the staff member responsible for finances of new medical devices and their email address.
10. Could you please provide me the name of the staff member responsible for procurement of new medical devices and their email address.
11. Lastly, could you please supply a copy of the last 3 ‘New Medical Device meeting’ minutes and also the location of where they are published on your website?

All documents can be provide in word, PDF or a readable format.

Thank you for your help on this matter and look forward to hearing from you. Any questions please do let me know.

Yours faithfully,

Carolyn Tuson

Somerset Integrated Care System

2 Atodiad

Your message to [email address] couldn't be delivered.
stp.team1 wasn't found at nhs.net.
request-829551-1822d. . . Office 365 stp.team1
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: 2/2/2022 11:33:30 AM
Sender Address: [FOI #829551 email]
Recipient [email address]
Address:
Subject: Freedom of Information request - Policy information
request
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address lookup
DSN generated by: CWLP265MB4995.GBRP265.PROD.OUTLOOK.COM

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
2/2/2022 local (Exim 4.89) (envelope-from
1 11:33:30 foi owl.ukcod.org.uk <[FOI #829551 email]>) *
AM
2/2/2022 esmtps
2 11:33:30 owl.ukcod.org.uk bittern.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) *
AM (Exim 4.89) (envelope-from
<[FOI #829551 email]>)
2/2/2022
3 11:33:30 mailer103.ukcod.org.uk prefilter-p-premta4.muc1 ESMTPS *
AM
2/2/2022
4 11:33:31 hes.trendmicro.com Prefilter-postMTA13.emailsecurity.trendmicro.eu SMTP 1 sec
AM
2/2/2022
5 11:33:31 Prefilter-postMTA13.emailsecurity.trendmicro.eu smtp1.e.amses.net ESMTPS *
AM
2/2/2022
6 11:33:31 smtp1.e.amses.net IMSVA ESMTP *
AM
2/2/2022
7 11:33:31 smtp1.e.amses.net IMSVA ESMTP *
AM
2/2/2022 Microsoft SMTP Server (version=TLS1_2,
8 11:33:41 smtp1.e.amses.net LO2GBR01FT038.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 10 sec
AM
2/2/2022 Microsoft SMTP Server (version=TLS1_2,
9 11:33:41 LO2GBR01FT038.eop-gbr01.prod.protection.outlook.com LO2P265CA0451.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
AM
2/2/2022 Microsoft SMTP Server (version=TLS1_2,
10 11:33:46 LO2P265CA0451.GBRP265.PROD.OUTLOOK.COM CWLP265MB4995.GBRP265.PROD.OUTLOOK.COM cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 5 sec
AM

Original Message Headers

Received: from LO2P265CA0451.GBRP265.PROD.OUTLOOK.COM (2603:10a6:600:e::31) by
CWLP265MB4995.GBRP265.PROD.OUTLOOK.COM (2603:10a6:400:13e::9) with Microsoft
SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4951.11; Wed, 2 Feb 2022 11:33:46 +0000
Received: from LO2GBR01FT038.eop-gbr01.prod.protection.outlook.com
(2603:10a6:600:e:cafe::7c) by LO2P265CA0451.outlook.office365.com
(2603:10a6:600:e::31) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4951.12 via Frontend
Transport; Wed, 2 Feb 2022 11:33:41 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.103)
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 46.43.39.103 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.103; helo=mailer103.ukcod.org.uk;
Received: from smtp1.e.amses.net (213.161.89.71) by
LO2GBR01FT038.mail.protection.outlook.com (10.152.42.165) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.4951.12 via Frontend Transport; Wed, 2 Feb 2022 11:33:41 +0000
Received: from smtp1.e.amses.net (OP-SLPIMS07.ops.amses.net [127.0.0.1])
by IMSVA (Postfix) with ESMTP id A292E2107E3
for <[email address]>; Wed, 2 Feb 2022 11:33:31 +0000 (GMT)
Received: from smtp1.e.amses.net (OP-SLPIMS07.ops.amses.net [127.0.0.1])
by IMSVA (Postfix) with ESMTP id 94BB121075A
for <[email address]>; Wed, 2 Feb 2022 11:33:31 +0000 (GMT)
Received: from Prefilter-postMTA13.emailsecurity.trendmicro.eu (prefilter-postmta13.emailsecurity.trendmicro.eu [150.70.236.149])
by smtp1.e.amses.net (Postfix) with ESMTPS
for <[email address]>; Wed, 2 Feb 2022 11:33:31 +0000 (GMT)
Received: from hes.trendmicro.com (unknown [10.36.141.178])
by Prefilter-postMTA13.emailsecurity.trendmicro.eu (Postfix) with SMTP id 5224D14AC56
for <[email address]>; Wed, 2 Feb 2022 11:33:31 +0000 (UTC)
Received: from mailer103.ukcod.org.uk (unknown [46.43.39.103])
by prefilter-p-premta4.muc1 (Postfix) with ESMTPS id 5EAF8C40031
for <[email address]>; Wed, 2 Feb 2022 11:33:30 +0000 (UTC)
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=lNh5YJgmZ3iz25NRzGddBqpvNUsYZ93p03/U5BM4Fck=; b=F8Qss+DOhLF/idgBkATy3zMGR
s4ixmlW3nw73pmM767Zj9V0L91+ugn/OihjmRrk6lPhd1PHn5CdurAscwkmQ+cEFnRnXacUDYOzdc
33D3G1wrqkhmtP3LgHtOAfaW3xG2om6vAwx0LRD+eHL+b57/eputGZCDZwkcTub5WgqMCbzeptn4/
cWM06m41xUTPoTs1hg9LjlmNegChRbWw5CBBVd7BPXuMAqd2oZJnxiDWRo/CJ0Uxh2+wKRit/H57k
1fvKcIZUBB95GcuYbnFEBf12kHDLarBihNOD5rg/+vJUCd71OYghwba6t3D+aoURbStOikCizamU5
ZIrM+Fg5Q==;
Received: from owl.ukcod.org.uk ([2001:41c8:20:60e::6c:10]:38970)
by bittern.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[FOI #829551 email]>)
id 1nFDtC-0006Fp-3h
for [email address]; Wed, 02 Feb 2022 11:33:30 +0000
Received: from foi by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[FOI #829551 email]>)
id 1nFDtC-0007Xb-0z
for [email address]; Wed, 02 Feb 2022 11:33:30 +0000
Date: Wed, 02 Feb 2022 11:33:30 +0000
From: Carolyn Tuson <[FOI #829551 email]>
To: FOI requests at Somerset ICS <[email address]>
Message-ID: <[email address]>
Subject: Freedom of Information request - Policy information request
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-TMASE-Version: IMSVA-9.1.0.2090-8.6.1018-26690.007
X-TMASE-Result: 10--12.523900-10.000000
X-TMASE-MatchedRID: n/2IWTG9XlVDPWr5e5soN5KLzY5ZrthjgZWhKWBme63mTInKzpSFSd5Q
ZVAH5Zt2w/ioXBhFM62AmNq8Y5gGYN4I0odpCiDTLbjXqdzdtCXzZKDA1/pIrjUQfiU3MhlI2zM
lMhmuHAhUyI3VVq1S4BEnT8ijtFbxqCDSMLWLu8xBDn6Fjq77jpQ4LE+5P7U+dgBJkhmmhrAPLc
PxOcmG5/Y07a8yfiA/oWgxcVvasO+W1YDLrjyT/NqLN7nigLBUOhJ9m53n4aAfyMkN7e89A05IN
N8m06bIb9KbVRNhKMVZO+ygKNx8vEuOR6SoiPT4VEOlvmojTIeiEW/g7VoQPjn6oRg4Qu89FM2n
TT67p4eGlWN2xO9eqAJyijPAxkgMC3yg2ThKfOZrhU4hH36WS2vaomg0i4KNjs8grGEcDWlkyH0
v/Y9eUk648XifV9tVtzx3yJL2seFaR9JRSDqGLcgBm5BlOGUuAajW+EL+laMZnvrX9WYNYtcgs1
mki97drJbaAKE/Hh2HDL+kkY7KzOpT+6c6+qYhrERPfxjVBmFlRzZAkKRGDXtTo0P1ssT+kihrQ
TO/6s35Ds2b9S5L6s5yw/YC8uhntdhQOw8FLoxaC03arbLUeLTrV2IG143XbsHtQ0J95tSJh0X4
TiKr8Cek7Lbqges1t+TAqtIrD1iv32t0t0cTKGj110VUgQaLDAX+3WB+CtfLkl8e9W70iz+/Hfb
61zqnG9OTPTG3Vshjao5Xkzd8pwDlNH+CjAWKngIgpj8eDcBZDL1gLmoa/Cll8/FxmxP8KrauXd
3MZDXwMUUgHNDhDfb/jTTlUnX/XMjBaNr299U99c+KJUjAflvdNkEPiMvTPGlPgp8wD2OxT50sw
s/Ung==
X-TM-AS-URLRatingInfo: 81-34-=?us-ascii?B?aHR0cHM6Ly93d3cud2hhdGRvdGhleWtub3
cuY29tL2NoYW5nZV9yZXF1ZXN0L25ldz9ib2R5PXNvbWVyc2V0X2ljcw==?=
X-TM-AS-URLRatingAct: 65-
X-TM-AS-GCONF: 00
X-EXTERNAL-HEADER: TRUE
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-8.6.0.1018-26690.007
X-TM-AS-Result: No--12.524-5.0-31-10
X-imss-scan-details: No--12.524-5.0-31-10;No--12.524-5.0-31-10;No--12.524-3.0-31-10
X-TMASE-SNAP-Result: 1.821001.0001-0-2-1:0,12:0,22:0,33:0,34:0-0
Return-Path: [FOI #829551 email]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 37c354b2-85b0-47f5-b222-07b48d774ee3:0
X-MS-Exchange-SkipListedInternetSender: ip=[46.43.39.103];domain=mailer103.ukcod.org.uk
X-MS-Exchange-ExternalOriginalInternetSender: ip=[46.43.39.103];domain=mailer103.ukcod.org.uk
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 1b973dee-79bb-4de6-417b-08d9e63fdd24
X-MS-TrafficTypeDiagnostic: CWLP265MB4995:EE_

References

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

Nid ydym yn gwybod a yw'r ymateb mwyaf diweddar i'r cais hwn yn cynnwys gwybodaeth neuai peidio - os chi ywCarolyn Tuson mewngofnodwch a gadael i bawb wybod.