Since the inception in DK Core 1.1.0, provider identifier (Da: ydernummer) exists as an identifier on DK Core's Organization, https://hl7.dk/fhir/core/StructureDefinition-dk-core-organization.html .
Although specification of how a provider identifier looks like (system and all) is valuable, the role as identifier on Organization is misleading. In the national health organization register, SOR, multiple organizations can share the same provider identifier. This sharing can come and go. As multiple Organization can be associated with the same provider identifier, it cannot be an identifier for Organization.
Even an initial situation where an Organization can uniquely be identified by a provider identifier, can change to a shared, non-uniquely identifying situation.
It would seem that provider identifier is an identifier of something else than organization and that, at best, Organization can be related to it.
Since the inception in DK Core 1.1.0, provider identifier (Da: ydernummer) exists as an identifier on DK Core's Organization, https://hl7.dk/fhir/core/StructureDefinition-dk-core-organization.html .
Although specification of how a provider identifier looks like (system and all) is valuable, the role as identifier on Organization is misleading. In the national health organization register, SOR, multiple organizations can share the same provider identifier. This sharing can come and go. As multiple Organization can be associated with the same provider identifier, it cannot be an identifier for Organization.
Even an initial situation where an Organization can uniquely be identified by a provider identifier, can change to a shared, non-uniquely identifying situation.
It would seem that provider identifier is an identifier of something else than organization and that, at best, Organization can be related to it.