# NEMS or MNS for Patient Demographic Changes

**URL:** <https://developer.community.nhs.uk/t/nems-or-mns-for-patient-demographic-changes/15778>\
**Category:** Personal Demographics Service FHIR API\
**Created:** [14 October 2026 10:59 UTC](https://developer.community.nhs.uk/t/nems-or-mns-for-patient-demographic-changes/15778 "2026-10-14T10:59:45Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Mayfield](https://dub1.discourse-cdn.com/nhsdigitaldeveloper/user_avatar/developer.community.nhs.uk/kevin_mayfield/32/473_2.png) [@Kevin\_Mayfield](https://developer.community.nhs.uk/u/Kevin_Mayfield)\
**Post date:** [14 October 2026 10:59 UTC](https://developer.community.nhs.uk/t/nems-or-mns-for-patient-demographic-changes/15778/1 "2026-10-14T10:59:45Z")

</div>

I’m looking into using either to support a Shared Care Record system (long term this may be several Shared Care Record systems).

Can we use NEMS still. we had looked at this in the past and code may be done but is now marked as **deprecated**

 ![Screenshot 2026-10-14 at 11.55.33](https://europe1.discourse-cdn.com/nhsdigitaldeveloper/original/2X/9/912fb8b2640b4d97db6b087d2a04dfba4c7b837e.jpeg)

---

<div class="post-metadata">

**Author:** ![Paul\_Murphy](https://avatars.discourse-cdn.com/v4/letter/p/e0b2c6/32.png) [@Paul\_Murphy](https://developer.community.nhs.uk/u/Paul_Murphy)\
**Post date:** [15 October 2026 13:15 UTC](https://developer.community.nhs.uk/t/nems-or-mns-for-patient-demographic-changes/15778/2 "2026-10-15T13:15:03Z")

</div>

Hi Kevin,

Your diagram looks to match the MNS pattern: lightweight PDS record change notification followed by retrieving the record via the PDS FHIR API.

As NEMS is deprecated, that team are no longer supporting new onboarding requests. Building the event subscription and notification leg on MNS aligns with current national standards and avoids introducing legacy technical debt into the solution