- This version of the UK Core is a development copy.
- This contains BREAKING CHANGES as a result of the C&TA Sprint 7 Review, and STU2 Sequence ballot reconciliation.
- This version is not yet reviewed for implementation. Other versions are available on the UK Core Version History Guide
- Please follow the guidance on the Contact Us page if you need any assistance.
- A summary of changes is available on the STU3 Sequence Change Log
HumanName
A name of a human with text, parts and usage information.
Names may be changed or repudiated. People may have different names in different contexts. Names may be divided into parts of different types that have variable significance depending on context, though the division into parts is not always significant. With personal names, the different parts might or might not be imbued with some implicit meaning; various cultures associate different importance with the name parts and the degree to which systems do care about name parts around the world varies widely.
The HumanName datatype has the following elements and this is an overview of the datatype with additional UK Core guidance. The full definition is available from the FHIR standard.
Element | Type | Usage Guidance | Description |
---|---|---|---|
use |
code | SHOULD be present | Identifies the purpose for this name. Allows the appropriate name for a particular context of use to be selected from among a set of names. Applications can assume that a name is current unless it explicitly says that it is temporary or old. | text |
string | MAY be present | Text representation of the full name. Specifies the entire name as it SHOULD be displayed e.g. on an application UI. This MAY be provided instead of or as well as the specific parts. Applications updating a name SHALL ensure that when both text and parts are present, no content is included in the text that isn't found in a part. |
family |
string | SHOULD be present | Family name (often called 'Surname') |
given |
string | SHOULD be present | Given names (not always 'first'). Includes middle names. This repeating element order: Given Names appear in the correct order for presenting the name |
prefix |
string | MAY be present | Parts that come before the name. This repeating element order: Prefixes appear in the correct order for presenting the name |
suffix |
string | MAY be present | Parts that come after the name. This repeating element order: Suffixes appear in the correct order for presenting the name |
period |
Period | MAY be present | Time period when name was/is in use |
Unstructured Names
text
Text representation of the name. This can be used if a structured name as detailed below cannot be supported. It MAY be present in addition to a structured name.
Structured Names
Structured names SHOULD be used whenever possible as detailed below.
The following elements SHOULD be used to construct structured names:
Element | Example |
---|---|
family |
smith |
given |
John |
prefix |
Mr |
suffix |
MBE |