| Name | Description | MRO | Cardinality | Implementation Guidance | Data Type | Value Sets | Information Type | Derived From |
|---|---|---|---|---|---|---|---|---|
|
Label Concept
|
The Label Concept IPS data type describes data items that are containers for other data items, as defined in BS EN ISO 27269:2025 section 6.2.2. |
… |
|
Any
|
|
|
|
|
|
List
|
The List IPS data type describes an implementation agnostic representation of data items that are containers for lists of other data items (e.g. problem list), as defined in BS EN ISO 27269:2025 section 6.2.3. In PRSB standards lists will usually be represented by record entries with a cardinality of 0 to many or 1 to many. Where there are mandatory data items of the type List in a clinical record, the reason for an empty list must be explicitly stated (e.g. No Known Drug Allergies or Not asked). |
… |
|
Any
|
|
|
|
|
|
Reference
|
The Reference IPS data type provides a representation of an implementation independent directional link from a source data item to an internal (i.e. within the clinical record) or external target object (e.g. URL), as defined in BS EN ISO 27269:2025 section 6.2.4. In PRSB standards references are also defined by specific complex data types indicating the target component, which may be an entire information model (e.g. About Me), section or record entry (e.g. Procedures and therapies) or fewer data items such as clusters or individual elements. |
… |
|
Any
|
|
|
|
|
|
Person Name
|
The Person Name IPS data type represents the name of a person structured as a sequence of name parts (e.g. first name, family name, title, suffix), as defined in BS EN ISO 27269:2025 section 6.2.5. PRSB recommends use of NHS Data Dictionary elements for name parts (e.g. PERSON GIVEN NAME for first name). |
… |
|
Any
|
|
|
|
|
|
Person first name
|
The first name(s) of the person. This includes middle names. |
M | 1…* |
|
String
|
NHS Data Dictionary
—
PERSON GIVEN NAME
(Recommended)
|
|
|
|
Person family name
|
The family name or surname of the person. |
M | 1…* |
|
String
|
NHS Data Dictionary
—
PERSON FAMILY NAME
(Recommended)
|
|
|
|
Person preferred name
|
The name by which a person wishes to be addressed. The preferred name volunteered by the person or a preferred name given by PDS that the person has asked to be called by. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
PERSON FULL NAME
(Recommended)
|
|
|
|
Title
|
Person's title. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
PERSON TITLE
(Recommended)
|
|
|
|
Person name suffix
|
A textual suffix that may be added to the end of a person's name, for example, OBE, MBE, BSc, JP, GM. |
R | 0…* |
|
String
|
NHS Data Dictionary
—
PERSON NAME SUFFIX
(Recommended)
|
|
|
|
Coded Element
|
The Coded Element IPS data type describes elements holding a single concept from a defined code system (e.g. SNOMED CT) as defined in BS EN ISO 27269:2025 section 6.2.6. PRSB recommends the exceptional use of free text in circumstances where no appropriate coded concept is available. |
… |
|
Any
|
|
|
|
|
|
Date Time
|
The Date Time IPS data type supports representation of a full or partial date and/or time as defined in BS EN ISO 27269:2025 section 6.2.7. |
… |
|
Any
|
|
|
|
|
|
Identifier
|
The Identifier IPS data type defines a unique name for a thing or object, as defined in BS EN ISO 27269:2025 section 6.2.8. For example, NHS number. |
… |
|
Any
|
|
|
|
|
|
Address
|
The Address IPS data type represents the address of a person or organisation structured as a sequence of address parts (e.g. Address line 1, Address line 2, Postcode etc), as defined in BS EN ISO 27269:2025 section 6.2.9. PRSB recommends use of:
|
… |
|
Any
|
|
|
|
|
|
Address line 1
|
First line of the address. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
ADDRESS LINE 1
(Recommended)
|
|
|
|
Address line 2
|
Second line of the address. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
ADDRESS LINE 2
(Recommended)
|
|
|
|
Address line 3
|
Third line of the address. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
ADDRESS LINE 3
(Recommended)
|
|
|
|
Address line 4
|
Fourth line of the address. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
ADDRESS LINE 4
(Recommended)
|
|
|
|
Address line 5
|
Fifth line of the address. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
ADDRESS LINE 5
(Recommended)
|
|
|
|
Postcode
|
Postcode of the address. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
POSTCODE
(Recommended)
NHS Data Dictionary
—
POSTCODE OF USUAL ADDRESS
(Recommended)
|
|
|
|
Address type
|
The type of address e.g. main permanent residence or temporary residence. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
ADDRESS ASSOCIATION TYPE
(Recommended)
|
|
|
|
Address start date
|
The date when the address became valid for the person or organisation. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Address end date
|
The date when the address was no longer valid for the person or organisation. |
R | 0…1 |
|
Date Time
|
|
|
|
|
Unique Property Reference Number (UPRN)
|
Unique Property Reference Number (UPRN) is the unique numeric identifier (up to 12 digits) for every addressable location across the UK. |
R | 0…1 |
|
Identifier
|
Unique Property Reference Number
—
https://www.geoplace.co.uk/addresses-streets/location-data/the-uprn
(Recommended)
|
|
|
|
Telecom
|
The Telecom IPS data type provides the telecommunication contact details of a person or organisation (e.g. contact telephone number, email address), as defined in BS EN ISO 27269:2025 section 6.2.10. PRSB recommends use of:
|
… |
|
Any
|
|
|
|
|
|
Telecom contact method
|
The telecommunications system or contact method. e.g. phone, email, other. |
R | 0…1 |
|
Coded Element
|
NHS Data Dictionary
—
COMMUNICATION CONTACT METHOD
(Recommended)
FHIR
—
ContactPointSystem
|
|
|
|
Telecom value
|
The telecom value e.g. UK telephone number, email address or other communication contact string. |
R | 0…1 |
|
String
|
NHS Data Dictionary
—
COMMUNICATION CONTACT STRING
(Recommended)
NHS Data Dictionary
—
UK TELEPHONE NUMBER
(Recommended)
NHS Data Dictionary
—
CONTACT EMAIL ADDRESS (PATIENT OR LEAD CONTACT)
(Recommended)
|
|
|
|
Telecom type
|
The telecom contact type or use e.g. home, work, mobile etc. |
R | 0…1 |
|
Coded Element
|
FHIR
—
ContactPointUse
(Recommended)
|
|
|
|
Preference of telecom value
|
The preferred order of use for the telecom value. |
R | 0…1 |
|
String
|
(Recommended)
|
|
|
|
Organisation Name
|
This aligns to the IPS data type Organization Name and represents the name for an organisation as a simple string, as defined in BS EN ISO 27269:2025 section 6.2.11. PRSB recommends use of Organisation Data Service (ODS) codes to retrieve organisation names, where available. |
… |
|
Any
|
|
|
|
|
|
Text
|
The Text IPS data type supports human readable text (e.g. for clinical narrative or a person's About Me responses), as defined in BS EN ISO 27269:2025 section 6.2.12. |
… |
|
Any
|
|
|
|
|
|
Any
|
The Any IPS data type is an abstract data type of which all other data types are concrete specialisations, as defined in BS EN ISO 27269:2025 section 6.2.13. This data type is not generally used for PRSB data items, which must usually use concrete IPS (i.e. Label Concept, List, Reference (PRSB equivalent), Person Name, Coded Element, Date Time, Identifier, Address, Telecom, Organisation Name (PRSB equivalent), Text, Range, Quantity, Period, General Time Specification (abstract type), String, and Ratio) or PRSB (Code No Text, Timestamp, Document, MultiMedia, Lower Limit Range and Upper Limit Range) data types. Occasionally, Any may be used in draft specifications as a placeholder for another data type. |
… |
|
|
|
|
|
|
|
Range
|
The Range IPS data type represents an ordered set of quantities usually expressed as lower and upper limit values with units of measure, as defined in BS EN ISO 27269:2025 section 6.2.14. Exceptionally the lower or upper limit value may be omitted (e.g. < 3.0 mmol/ L). PRSB recommends use of UCUM (Unified Code for Units of Measure) for representing units. The PRSB data types Lower Limit Range and Upper Limit Range constrain this data type. |
… |
|
Any
|
|
|
|
|
|
Quantity
|
The Quantity IPS data type defines dimensioned quantities that are usually the result of measuring and expressed as values with units of measure (e.g. 120 mmHg), as defined in BS EN ISO 27269:2025 section 6.2.15. PRSB recommends use of UCUM (Unified Code for Units of Measure) for representing units. |
… |
|
Any
|
|
|
|
|
|
Period
|
The Period IPS data type defines an ordered set of time stamps for start and end date times (e.g. from 1 Aug 2024 to 31 July 2025) or start date time and width (e.g. from 1 Aug 2024 for one year), as defined in BS EN ISO 27269:2025 section 6.2.16. |
… |
|
Any
|
|
|
|
|
|
General Timing Specification
|
This aligns to the IPS data type General Time Specification (GTS) and is an abstract data type that defines an unordered set of distinct values that are time quantities used for specifying the timing of certain events and actions that may be cyclical (e.g. every other Wednesday morning from 1 Aug 2024 to 31 July 2025), as defined in BS EN ISO 27269:2025 section 6.2.17. |
… |
|
Any
|
|
|
|
|
|
String
|
The String IPS data type supports machine readable text (i.e. character string), as defined in BS EN ISO 27269:2025 section 6.2.18. |
… |
|
Any
|
|
|
|
|
|
Ratio
|
The Ratio IPS data type broadly defines a quotient quantity with a numerator and denominator (e.g. an insulin to carbohydrate ratio (ICR) of 1:10), as defined in BS EN ISO 27269:2025 section 6.2.19. |
… |
|
Any
|
|
|
|