You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A NamingSystem: Defines a specific code system or identifier system, so that it can be noted in a registry for other systems to find and understand an identifier.
The data for any NamingSystem comes from decor.nictiz.nl by consulting any of the available OID registries. The OID registries are - for now - maintained by a single person (me) through automated conversion and sometimes a manual tweak.
Generically speaking it helps implementers to know what "2.16.840.1.113883.2.4.4.1.361" means when deemed relevant in a profile. You could do that through documentation inside the profile obviously as well. A NamingSystem could offer single point of reference for that.
I would only consider a NamingSystem when applying OIDs in FHIR. URIs are normally self-explanatory.
On main we have 4 NamingSystems living in the terminology folder, added by this commit:
a7e942a
These are the only 4 NamingSystems we have at the moment, which raises questions:
The text was updated successfully, but these errors were encountered: