# \#e-rs

**URL:** https://developer.community.nhs.uk/tag/e-rs/83.md

[Latest](https://developer.community.nhs.uk/latest.md) · [Categories](https://developer.community.nhs.uk/categories.md) · [Tags](https://developer.community.nhs.uk/tags.md)

---

## [e-RS FHIR API - Response received no relationship](https://developer.community.nhs.uk/t/e-rs-fhir-api-response-received-no-relationship/8161)

<div class="topic-metadata">

**Author:** [@Satyam\_Gehani](https://developer.community.nhs.uk/u/Satyam_Gehani)\
**Replies:** 5\
**Last updated:** [5 January 2026 14:38 UTC](https://developer.community.nhs.uk/t/e-rs-fhir-api-response-received-no-relationship/8161 "2026-01-05T14:38:23Z")

</div>

Facing an issue in the INT eRS environment for the eRS FHIR API when posting the below request, where we are receiving an error response with the message “NO\_RELATIONSHIP”. Request: { "meta": { "profile": \[ …

---

## [Formal change communication for the e-RS FHIR API - Format of the binary file ID](https://developer.community.nhs.uk/t/formal-change-communication-for-the-e-rs-fhir-api-format-of-the-binary-file-id/956)

<div class="topic-metadata">

**Author:** [@LucyK](https://developer.community.nhs.uk/u/LucyK)\
**Replies:** 1\
**Last updated:** [1 October 2024 10:49 UTC](https://developer.community.nhs.uk/t/formal-change-communication-for-the-e-rs-fhir-api-format-of-the-binary-file-id/956 "2024-10-01T10:49:11Z")

</div>

We are changing the way we represent the binary file ID for uploaded and maintained attachments in e-RS. This new approach will create a more secure reference for the ID of clinical referral attachments. This change was…