Identifier Systems
When assigning a business identifier to a resource, by way of an Identifier, it is important to identify the namespace ("system") from which that identifier was drawn. The system is indicated by setting the relevant value into Identifier.system.
So what is the relevant value? Well, it depends on where the identifier came from.
Externally defined
FHIR® curates a list of officially supported systems, along with the system value which should be used.
...
CHI Number (Scotland): 010 101 0000 to 311 299 9999
Health and Care Number (Northern Ireland): 320 000 0010 to 399 999 9999
NHS Number (England and Wales): 400 000 0000 to 999 999 9999
Externally defined, PKB hosted
PKB allows customers to define their own local identifier types at the level of both a PKB Organisation and also a PKB Team. In these cases, PKB is hosting information about the identifier types, but is not responsible for the identifiers. Note: this is not to say all the attributes of the identifier type are meaningful outside of PKB. For example, whilst a customer might configure a display name for the identifier type to match that used in their own internal systems, it is possible that they might have configured an Assigning Authority / Type Code for use in HL7 messages which is only correct for messages sent to PKB.
...
PKB does not expose information about a customer's local identifier types to anyone other than the customer. As such, there is no plan to replace the UUID-based URIs with resolvable URLs, since anyone who needs to understand the system will already do so.
PKB defined
Identifiers assigned by PKB are typically exposed directly through resource IDs.
...
Identifier Name | FHIR Identifier system |
PKB Public ID |
|