Atención Habitantes de Calle en los Hospitales de Bogotá

Isabela Granados Arocha made this Freedom of Information request to Secretaria Distrital De Salud

This request has been closed to new correspondence. Contact us if you think it should be reopened.

There was a delivery error or similar, which needs fixing by the Queremosdatos.co team.

Isabela Granados Arocha

Estimado Secretaria Distrital De Salud,

Haciendo uso del derecho de acceso a la información establecido en la Ley 1712 de 2014, solicito un archivo en formato abierto y reutilizable (xls o csv) con la siguiente información en el periodo 2017-2018:

* Número de Hospitales en Bogotá
* Cifras de atención a habitantes de calle por hospital
* Género y edad
* Estado del paciente (fallecido o vivo)
* Causa de ingreso
* Duración de estancia
* Localidad

Un saludo,

Isabela Granados Arocha

Secretaria Distrital De Salud

2 Attachments

  • Attachment

    attachment.delivery status

    0K Download

  • Attachment

    solicitud acceso a la informaci n Atenci n Habitantes de Calle en los Hospitales de Bogot.txt

    1K Download View as HTML

Your message to [Dirección de correo del organismo Secretaria Distrital De Salud] couldn't be delivered.
webmaster wasn't found at saludcapital.gov.co.
request-475-70a35397 Office 365 webmaster
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: 7/30/2018 1:01:59 PM
Sender Address: [Dirección de correo de la solicitud #475]
Recipient [Dirección de correo del organismo Secretaria Distrital De Salud]
Address:
Subject: solicitud acceso a la información - Atención Habitantes de
Calle en los Hospitales de Bogotá
Error Details
Reported error: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient
[Dirección de correo del organismo Secretaria Distrital De Salud] not found by SMTP address
lookup
DSN generated by: BY2PR15MB0453.namprd15.prod.outlook.com

Message Hops
HOP TIME FROM TO WITH RELAY
(UTC) TIME
7/30/2018 local (Exim 4.80) (envelope-from
1 1:01:59 foicolombia mastodon.ukcod.org.uk <[Dirección de correo de la solicitud #475]>) *
PM
7/30/2018 esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
2 1:01:59 mastodon.ukcod.org.uk starling.ukcod.org.uk (Exim 4.89) (envelope-from *
PM <[Dirección de correo de la solicitud #475]>)
7/30/2018 Microsoft SMTP Server (version=TLS1_2,
3 1:02:01 starling.ukcod.org.uk SN1NAM01FT007.mail.protection.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 sec
PM
7/30/2018 Microsoft SMTP Server (version=TLS1_2,
4 1:02:03 SN1NAM01FT007.eop-nam01.prod.protection.outlook.com CY1PR15CA0026.outlook.office365.com cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) 2 sec
PM
7/30/2018 Microsoft SMTP Server (version=TLS1_2,
5 1:02:04 CY1PR15CA0026.namprd15.prod.outlook.com BY2PR15MB0453.namprd15.prod.outlook.com cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) 1 sec
PM

Original Message Headers

Received: from CY1PR15CA0026.namprd15.prod.outlook.com
(2a01:111:e400:5283::36) by BY2PR15MB0453.namprd15.prod.outlook.com
(2a01:111:e400:52d9::14) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.995.19; Mon, 30 Jul
2018 13:02:04 +0000
Received: from SN1NAM01FT007.eop-nam01.prod.protection.outlook.com
(2a01:111:f400:7e40::208) by CY1PR15CA0026.outlook.office365.com
(2a01:111:e400:5283::36) with Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.995.16 via Frontend
Transport; Mon, 30 Jul 2018 13:02:03 +0000
Authentication-Results: spf=none (sender IP is 46.43.39.112)
smtp.mailfrom=queremosdatos.co; saludcapital.gov.co; dkim=none (message not
signed) header.d=none;saludcapital.gov.co; dmarc=none action=none
header.from=queremosdatos.co;
Received-SPF: None (protection.outlook.com: queremosdatos.co does not
designate permitted sender hosts)
Received: from starling.ukcod.org.uk (46.43.39.112) by
SN1NAM01FT007.mail.protection.outlook.com (10.152.65.101) with Microsoft SMTP
Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id
15.20.1038.3 via Frontend Transport; Mon, 30 Jul 2018 13:02:01 +0000
Received: from mastodon.ukcod.org.uk ([46.43.39.83]:50858)
by starling.ukcod.org.uk with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
(Exim 4.89)
(envelope-from <[Dirección de correo de la solicitud #475]>)
id 1fk7oF-0005KK-VC
for [Dirección de correo del organismo Secretaria Distrital De Salud]; Mon, 30 Jul 2018 14:01:59 +0100
Received: from foicolombia by mastodon.ukcod.org.uk with local (Exim 4.80)
(envelope-from <[Dirección de correo de la solicitud #475]>)
id 1fk7oF-0000Pq-R4; Mon, 30 Jul 2018 14:01:59 +0100
Date: Mon, 30 Jul 2018 14:01:59 +0100
From: Isabela Granados Arocha <[Dirección de correo de la solicitud #475]>
To: =?UTF-8?B?U29saWNpdHVkZXMgZGUgaW5mb3JtYWNpw7NuIGEgU2VjcmV0YXJpYSBEaXN0?=
=?UTF-8?B?cml0YWwgRGUgU2FsdWQ=?= <[Dirección de correo del organismo Secretaria Distrital De Salud]>
Message-ID: <[correo electrónico]>
Subject: =?UTF-8?Q?solicitud_acceso_a_la_informaci=C3=B3n_-_Atenci=C3=B3n?=
=?UTF-8?Q?_Habitantes_de_Calle_en_los_Hospitales_de_Bogot=C3=A1?=
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Return-Path: [Dirección de correo de la solicitud #475]
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: 4ab1183e-75d6-4b87-b4b5-bfcb968c1d57:0
X-Forefront-Antispam-Report: CIP:46.43.39.112;IPV:NLI;CTRY:GB;EFV:NLI;
X-Microsoft-Exchange-Diagnostics: 1;SN1NAM01FT007;1:GlV1QJ9wOBs/Ffip3sH3VnR6KCHEpiHOrjNfeCBB4F3Yqb1KL+m8rGKwuBevKvUcPD7s6976VO0jkHEGxO4A22QtCtZbkunr3s6QEqWAkZ5qQvKprfukQPszvdo6uD6y
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: d409a3f2-a03c-4aac-38d4-08d5f61ca495
X-Microsoft-Antispam:
BCL:0;PCL:0;RULEID:(7020095)(4652040)(5600074)(711020)(4605076)(1401180)(1404068)(71702078);SRVR:BY2PR15MB0453;
X-Microsoft-Exchange-Diagnostics:
1;BY2PR15MB0453;3:zoyGpDtKz2cjjteMqn4vWXTYQKOhYZQPQetINfcRygihwpuLFMs4qYO5C8sz1OWba7puwc27DDHVhHgD5tjgadwDmHlFuaIBVx9Wa/2eBUuiVM46wEA2V2PlLMRdAfWj20nsK1RoKqmAB9+msW6xfvwPzTxfluyj+JK5c3+fu+DB6vJA9mHx0oAd2QufW0l6zxtML/n5CUNdxKEbbjAdkFqxRniw/eMbkMISbywyG6nxX1VwfP+3gyeF0Q7fgt7yoSSU5xvztWm6N3uWmD7IxHyyx+HPCFl++TGmL/zNe+BUQfTHC1ptjmLQXEQMY2fRoIUPTrVSRekyP/jQy2JRHhyeEMIC2xdyxBVcMIg0iF0=;25:EzGGadGQyevCE755rG3nHviU83uDWySKWJ0rnIOmFfOsx+q29BgkluwWwm9QhSTfAFs4F4jUvEgwNtmbBV6+AxqBgfBmsUvEmrcPYUFoKSkV5V1S6vM17R1t+V3NvGrER5OSifAKr1blXGvPQxx8RiS+/zN2BjdyXY3KlMnWAyBEP/mVcAB3ZdX6kDy+GVfgplK48g1J7GtgUnh7cSxh31D0Nn9934ZmlE6Oo1LU09aAQYWWjgArLsYwW6y2Q0s6LCwoZ+abRTdyEeAwwqQ8TMSCeMr7fNz6t93P0g1pxph5dHrryzkgS3ZN09mAZrI5IyngIp9jnl9H/Rd7Mk7Jaw==
X-MS-TrafficTypeDiagnostic: BY2PR15MB0453:

References

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