---
title: Information governance
keywords: foundations ig
tags: [ig,foundations]
sidebar: foundations_sidebar
permalink: foundations_ig.html
summary: "Information Governance controls applicable to the Foundations capability pack"
---


## Patient dissent to share flag ##

When Foundations APIs are used to support the Appointment Management capability, the above flag SHALL NOT be applied by provider systems.

## PDS S-flagged patients ##

If, in response to the Find or Read a Patient API, the provider system determines that a patient has a PDS 'S-Flag', then the patient's location and contact details are to be replaced by those of the target GP practice.



---
title: Information governance
keywords: foundations ig
tags: [ig,foundations]
sidebar: foundations_sidebar
permalink: foundations_ig.html
summary: "Information Governance controls applicable to the Foundations capability pack"
---


## Patient dissent to share flag ##

When Foundations APIs are used to support the Appointment Management capability, the above flag SHALL NOT be applied by provider systems.

## PDS S-flagged patients ##

If, in response to the Find or Read a Patient API, the provider system determines that a patient has a PDS 'S-Flag', then the patient's location and contact details are to be replaced by those of the target GP practice.

When these APIs are used as part of the Appointment Management Capability, then the Provider system SHALL NOT process requests for Patients it recognises as being S-flagged.



Update to Foundations IG page - S-Flagged Patients
Update to Foundations IG page - S-Flagged Patients

The current Core specification requires provider systems to replace S-Flagged patient contact details with those of the registered GP practice, but the Appt Management capability has excluded from scope the processing of requests for such patients.  This change calls this distinction out.