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.
...
Externally defined
FHIR® curates a list of officially supported systems, along with the system value which should be used.
...
Note: The equivalent information for our HL7 API can be found here.
Identifier Name | Country | FHIR Identifier system |
NHS Number * | GB-ENG, GB-WLS | |
CHI Number * | GB-SCT | urn:oid:2.16.840.1.113883.2.1.3.2.4.16.53 |
Health and Care Number * | GB-NIR | urn:uuid:1479257a-ce8f-482a-89fa-429ac066c158 |
Individual Health Identifier | IE | |
SSN | US | |
SIN | CA | https://fhir.infoway-inforoute.ca/NamingSystem/ca-social-insurance-number |
HKID | HK | http://fhir.patientsknowbest.com/id/hong-kong-identity-card-number |
BSN | NL | |
Krankenversichertennummer | DE | |
Civil ID | KW |
...
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.
...