---
title: "PKB Production EDU (HL7)"
canonical: "https://wiki.patientsknowbest.com/space/api/4403658822/PKB%20Production%20EDU%20(HL7)"
format: markdown
---
> Macro (toc)

| **Status** | [Active] |
| --- | --- |
| **Last Updated** | 24. March, 2025 |
| **Version** | 2 |

# Available Endpoints on Port 443

- [no-mtls.hl7.edu.patientsknowbest.com](https://no-mtls.hl7.edu.patientsknowbest.com/)

## Deprecations

- [edu.patientsknowbest.com](https://edu.patientsknowbest.com/) [:7443](http://my.patientsknowbest.com:7443/) has been deprecated.

# Overview

The available endpoint will only accepts ciphers that are deemed as [recommeded] and [secure] by the industry, if you are unable to support the below listed ciphers, please contact our support desk (email: [help@patientsknowbest.com](mailto:help@patientsknowbest.com)).

## no-mTLS Endpoint

[no-](http://no-mtls.hl7.uk.patientsknowbest.com/)[mtls.hl7.edu.patientsknowbest.com](https://mtls.hl7.edu.patientsknowbest.com/) is for customers who have:

- up-to-date client software tools that support the state of the art cipher suites
- have static IPs that we can allow-list
- can’t allocate budget to implement mTLS in short term

Full URL: [https://no-mtls.hl7.edu.patientsknowbest.com/services/hl7](https://no-mtls.hl7.edu.patientsknowbest.com/services/hl7)

## Standard Ports

Using standard ports (443) allows us to consolidate our server certificate management and fully automate the renewal process for all our endpoints.

## Local Firewall

Please ensure your ruleset is added to/updated to reflect the above URL/s

- If you previously had a whitelisting by IP address this will need to be updated to the URL as the IPs addresses are dynamic and will change periodically.
- We recommend you remove the deprecated URL/IP from your ruleset when you have successfully tested with the new URL/s.

## WSDL

If you require a WSDL file please use one of the following path:

- [https://no-mtls.hl7.edu.patientsknowbest.com/hl7_wsdl.xml](https://no-mtls.hl7.edu.patientsknowbest.com/hl7_wsdl.xml)

## Root CA

If you previously relied on the use of the root certificate [ISRG Root CA](https://letsencrypt.org/certificates/) you will need to update to a suitable [Google Trust Services Root CA](https://pki.goog/repository/) certificate.

# Supported Ciphers

| **Name (OpenSSL)** |  | **no-mtls** |
| --- | --- | --- |
| <u>[TLS_AES_128_GCM_SHA256](https://ciphersuite.info/cs/TLS_AES_128_GCM_SHA256/)</u> | [recommended] | :check_mark: |
| <u>[TLS_AES_256_GCM_SHA384](https://ciphersuite.info/cs/TLS_AES_256_GCM_SHA384/)</u> | [recommended] | :check_mark: |
| <u>[TLS_CHACHA20_POLY1305_SHA256](https://ciphersuite.info/cs/TLS_CHACHA20_POLY1305_SHA256/)</u> | [recommended] | :check_mark: |
| <u>[ECDHE-ECDSA-AES128-GCM-SHA256](https://ciphersuite.info/cs/TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256/)</u> | [recommended] | :check_mark: |
| <u>[ECDHE-ECDSA-AES256-GCM-SHA384](https://ciphersuite.info/cs/TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384/)</u> | [recommended] | :check_mark: |
| <u>[ECDHE-ECDSA-CHACHA20-POLY1305](https://ciphersuite.info/cs/TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256/)</u> | [recommended] | :check_mark: |
| <u>[ECDHE-RSA-AES128-GCM-SHA256](https://ciphersuite.info/cs/TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256/)</u> | [secure] | :check_mark: |
| <u>[ECDHE-RSA-AES256-GCM-SHA384](https://ciphersuite.info/cs/TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384/)</u> | [secure] | :check_mark: |
| <u>[ECDHE-RSA-CHACHA20-POLY1305](https://ciphersuite.info/cs/TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256/)</u> | [secure] | :check_mark: |