Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Page Properties


true 
IDS56
Version12.0.0
TypeInteroperability Standard
StatusEffective
Effective Date
Insert excerpt
Day One Effective DateDay One Effective Datenopanel
Framework(s)


Table of Contents

Introduction

The Personal Demographics Service (PDS) is the national electronic database of NHS patient details such as name, address, date of birth and NHS Number (known as demographic information).

Requirements 


Applicable Suppliers
Requirement
Level
Suppliers of
new
services
or applications (i.e. those which are NOT
which ARE currently deployed into an operational environment
)2018
, and have existing PDS compliance.

PDS Integration Requirements 2006-B, or a later version (e.g. 2018 PDS Integration Requirements – v1.0

.

See below for supporting documents.

StatuscolourYellowtitleSHOULD

or PDS FHIR API).

MUST
Suppliers of new services
which ARE
or applications (i.e. those which are NOT currently deployed into an operational environment
, and have an
with existing PDS compliance).
PDS Integration Requirements 2006-B, or a later
Implement and maintain the Personal Demographics Service (PDS) FHIR API inline with the latest specification version.
statustitle
MUST
colourRed
All Suppliers Implement and maintain PDS Record Change Event in line with the latest version specification. See National Event Management Service (NEMS) for further information.MUST

All suppliers are encouraged to work towards compliance with the latest

...

version as above.

Compliance, Assurance and Testing

PDS FHIR API

For Suppliers of new services or applications, see the Personal Demographics Service (PDS) section on Onboarding Overview of the Digital Services for Integrated Care (DSIC) Interoperability Standards and Requirements.

2018 PDS Integration Requirements – v1.0

...

or older

For Suppliers of services which ARE currently deployed into an operational environment:


Expand
titleClick here to view historical assurance approach

To gain access to PDS suppliers

...

previously will have followed the Common Assurance Process (CAP). CAP is an end-to-end assurance process, which involves a tailored (CAP) approach being developed which states what deliverable and compliance activities are conducted.

As part of the CAP suppliers will be asked to demonstrate adherence to the following specifications:

  • CAP Information Governance Compliance Requirements

...

These specifications contain a set of generic requirements applicable to all systems seeking compliance to a business domain. Compliance with these specifications is mandatory and established through the CAP.

The documents that define and support the compliance assurance and testing activity for the PDS compliance module are detailed within the above mentioned Foundation Module - Baseline Index V1.0.

For advice and support from the NHS Business Partners

...

Programme, please

...

...


Supporting Documentation

PDS FHIR API

For Suppliers of new services or applications:

It is recommended to read GP software developer guide in conjunction with the API documentation.

2018 PDS Integration Requirements – v1.0

For Suppliers of services which ARE currently deployed into an operational environment:


Expand
titleClick here to view previous PDS requirements documentation

The following documents form the PDS integration baseline for local systems wishing to integrate with PDS. This new set of requirements apply to all new system suppliers wishing to complete PDS integration. Existing suppliers are not expected to implement the full scope of new requirements until '2018 PDS Integration Requirements – v1.0' is mandated for all suppliers.

...

...

...

...

...

...

The two documents below are listed in the 2018 PDS Integration Foundation Module - Baseline Index - v1.0 document as Guidance documents. They are of a historic nature but contain important information that is still relevant today.

The following document tells supplier which RBAC is relevant to PDS-related activities and enables suppliers to focus their approach accordingly. Suppliers are advised to focus their attention on sections 1, 3 and 4.

...

...

The following document provides useful background information on how a supplier might support business processes relating to BUS Sensitive patient records.

...

...

...


DependenciesDependencies

Excerpt

PDS FHIR API

For Suppliers of new services or applications:

Creating a compliant implementation requires implementing the following dependent interface standards:

...

excerpt

2018 PDS Integration Requirements – v1.0 or older

For Suppliers of services which ARE currently deployed into an operational environment:


Expand
titleClick here to view historical dependencies

Creating a compliant implementation previously required implementing the following dependent interface standards:


Roadmap

Page Properties Report
headingsStandards and Capabilities, Status, Effective Date, Description, Change Type, Change Route
pageSize300
sortByEffective Date
cqllabel = "S56" and space = in ( currentSpace ( ) , "DCSDR" , "DCSDCS" )