Virginity testing/hymen inspections

Claire Hubble made this Freedom of Information request to Old Swinford Hospital, Stourbridge as part of a batch sent to 262 authorities

Automatic anti-spam measures are in place for this older request. Please let us know if a further response is expected or if you are having trouble responding.

Response to this request is long overdue. By law, under all circumstances, Old Swinford Hospital, Stourbridge should have responded by now (details). You can complain by requesting an internal review.

Dear NHS trusts,

I would like to request the following information under the Freedom Information Act 2000:

I am investigating requests for the inspection of a person's hymen for the purpose of verifying whether they have had sexual intercourse.

1. How many people have received a hymen inspection for this purpose since 2015?
2. How many people have requested to have a hymen inspection for this purpose since 2015?

Please provide the information electronically in a spreadsheet format.

Yours faithfully,
Claire Hubble

Old Swinford Hospital, Stourbridge

2 Attachments

Your message to [email address] couldn't be delivered.
hoakes wasn't found at oshsch.com.
request-703816-a39c7. . . Office 365 hoakes
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: 11/4/2020 12:12:42 PM
Sender Address: [email address]
Recipient [email address]
Address:
Subject: Freedom of Information request - Virginity testing/hymen
inspections
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[email address] not found by SMTP address lookup
DSN generated by: VE1PR03MB5648.eurprd03.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
11/4/2020 local (Exim 4.89) (envelope-from
1 12:12:42 foi owl.ukcod.org.uk <[email address]>) *
PM
11/4/2020 esmtps
2 12:12:42 owl.ukcod.org.uk starling.ukcod.org.uk (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) *
PM (Exim 4.89) (envelope-from
<[email address]>)
11/4/2020 Microsoft SMTP Server (version=TLS1_2,
3 12:12:43 mailer102.ukcod.org.uk VE1EUR03FT047.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
11/4/2020 Microsoft SMTP Server (version=TLS1_2,
4 12:12:44 VE1EUR03FT047.eop-EUR03.prod.protection.outlook.com MR2P264CA0054.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM
11/4/2020 Microsoft SMTP Server (version=TLS1_2,
5 12:12:44 MR2P264CA0054.FRAP264.PROD.OUTLOOK.COM VE1PR03MB5648.eurprd03.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) *
PM

Original Message Headers

Received: from MR2P264CA0054.FRAP264.PROD.OUTLOOK.COM (2603:10a6:500:31::18)
by VE1PR03MB5648.eurprd03.prod.outlook.com (2603:10a6:803:11d::32) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.27; Wed, 4 Nov
2020 12:12:44 +0000
Received: from VE1EUR03FT047.eop-EUR03.prod.protection.outlook.com
(2603:10a6:500:31:cafe::c0) by MR2P264CA0054.outlook.office365.com
(2603:10a6:500:31::18) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend
Transport; Wed, 4 Nov 2020 12:12:44 +0000
Authentication-Results: spf=pass (sender IP is 46.43.39.102)
smtp.mailfrom=whatdotheyknow.com; oshsch.com; dkim=pass (signature was
verified) header.d=whatdotheyknow.com;oshsch.com; dmarc=pass action=none
header.from=whatdotheyknow.com;
Received-SPF: Pass (protection.outlook.com: domain of whatdotheyknow.com
designates 46.43.39.102 as permitted sender) receiver=protection.outlook.com;
client-ip=46.43.39.102; helo=mailer102.ukcod.org.uk;
Received: from mailer102.ukcod.org.uk (46.43.39.102) by
VE1EUR03FT047.mail.protection.outlook.com (10.152.19.218) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
15.20.3520.15 via Frontend Transport; Wed, 4 Nov 2020 12:12:43 +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=3+hWShAZvFD/Ab3Z4YBKJWY4ASvNIWkdT22sCig8wMA=; b=V4QTOhMYSqSr9ndjyJocuDPAq
Dg6PcDNL5VY4JtMwaZpoW/uJpr/jScb+S8yysHuKiAegOqIQgpz0FxjaN393nnMNBNyWhCbqfuc9y
YFqIPpf1XiwzO7y0V4YLEnI+aUMAwc4+3HtUR/8+nwTHApftPpYgmOMpLil1Jn56tJPO5OJElMvNj
Ovjh1BZ8i7rwhcEWNjpYuqUThdyAwQ1nTdnQskzyk2feb0T0BJD78be6O1gyxzVwYhRV90I7Qaeae
Eg9SwyvO0CGsLF5vQTVzBMnTbrqkPNrt4Z8Tv6MF6MjPA4jyXAa+jLLWfpjNHUMGsW+MlIhGg3mNa
si91x5d7w==;
Received: from owl.ukcod.org.uk ([46.43.39.108]:60659)
by starling.ukcod.org.uk with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
(Exim 4.89)
(envelope-from <[email address]>)
id 1kaHec-00038g-Na
for [email address]; Wed, 04 Nov 2020 12:12:42 +0000
Received: from foi by owl.ukcod.org.uk with local (Exim 4.89)
(envelope-from <[email address]>)
id 1kaHec-0000xW-J4
for [email address]; Wed, 04 Nov 2020 12:12:42 +0000
Date: Wed, 04 Nov 2020 12:12:42 +0000
From: Claire Hubble <[email address]>
To: "FOI requests at Old Swinford Hospital, Stourbridge" <[email address]>
Message-ID: <[email address]>
Subject: Freedom of Information request - Virginity testing/hymen inspections
MIME-Version: 1.0
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Return-Path: [email address]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 9d7ff979-82dc-4fac-8dca-9595e78f2d71:0
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f8f4c730-a357-4602-d516-08d880baef00
X-MS-TrafficTypeDiagnostic: VE1PR03MB5648:

References

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

Sent request to Old Swinford Hospital, Stourbridge again, using a new contact address.