Data Inclusions and Exclusions

This page is about data inclusion and exclusion. There is another page about patient registration inclusion and exclusion.

PKB strongly encourages the sending of as much patient data as possible via our APIs. There are specific circumstances when it is appropriate to limit what is sent for a specific patient or patient cohort.

It is therefore important to understand that PKB will process the data that is sent in via our APIs by our customers and partners, which will then be added to patient records. If there is a requirement for data not to be added to a patient record, for example the sending of appointments to a patient being detained in prison, then this needs to be excluded by the customer or partner at source. This could for example be achieved by applying a lookup in the TIE (Trust Integration Engine) that identifies such patient records and restricts the messages sent to PKB via our APIs.

It is the responsibility of the integrating customer or partner to establish how such records are identified and subsequently how the sending of data to PKB is restricted. PKB does not provide any processing logic once we have been sent data to then exclude it from a patient record, other than the support for delaying data display for observations (pathology and radiology) and documents.

As explained above, whilst PKB cannot exclude data from being added to patient records on behalf our customers and partners, we would request that you discuss any such considerations with us before applying data exclusions.


ADT A28 / ADT A31 HL7 feed


  • Create a record for every patient that has had activity in your trust in the past 2 years.

  • All messages require a verified NHS number. This is commonly via the SPINE but other trusts have their own data quality assurance processes.

  • Confirm the local identifier you want to send in (optional).

  • Name

  • DOB

  • Gender

  • Address

  • Postcode

  • Phone number: We only support 1 phone number. If you have the mobile, send that. If you don’t have the mobile, send the home number.

  • Email:

    • An email can only exist in one PKB record.

    • Only send this if you are confident the email in the record belongs to the patient.

    • For example, you may wish to exclude emails of children since they may have their parents’ email.

  • Language: keep default (EN) because upon registration the patient can change their own default language.


  • Deceased

  • Prisoners


Hospitals often do not implement this during the first phase of integration

  • Allergies

  • Diagnosis

  • Medications

  • Assigning to specialty teams



All appointments you want the patient to attend.



  • Deceased

  • Prisoners

  • Safeguarding flags

Appointment types:

  • Any appointment the patient does not need to attend (ex, MDT)

  • Silent appointments (those scheduled after a diagnostic test but before the patient has been told their diagnosis)

  • ‘Dummy’ or ‘holding’ appointments (don’t exist and the patient shouldn’t attend)



  • Identify the correct type of document to send from our code set

    • Start with appointment letters, discharge summaries, and clinic letters.

  • Base64 encoded PDF document

Lab results


  • Apply a delay only to those results with text, as those may include distressing information

  • Apply the delay for no more than 2 weeks, as this allows time for the medical team to counsel the patient. After 2 weeks, the danger of the patient not knowing is greater than the harm of receiving bad news without counselling.

Review our recommended delays spreadsheet and ensure it is signed off at an ICS level.