OrganizationIdentifier Naming system

Status: draft · 1.26.0 · JSON

Anchors a compartment to the product instance it was read from. The Organization standing for a source deployment carries one identifier under this system, whose value is the product-instance slug -- the registrable label of the source base URL's host, lowercased, so that https://oscar.example.ca/ws yields 'oscar'. The value is derived rather than assigned, and deterministic, so re-ingesting a source converges on the same instance instead of minting a second identity for it. This namespace is WELL-scoped and carries NO instance segment, which is the reason it exists while the instance-scoped identifier family retired in 1.21.0 does not: those namespaces encoded the instance into the URI, so every deployment minted its own namespace and readers had to parse a system URI to learn whose data they held. Here the instance is the VALUE, so one namespace serves every deployment and a reader compares values without ever parsing the system. A compartment may carry several Organizations -- a payer, a receiving practice, and the anchoring one -- and only the anchoring Organization carries this system, so a consumer seeking the product instance scans for this system rather than assuming the first Organization is the anchor. Consumers should expect it on the anchoring Organization: the reference validator treats its absence as an error, since a compartment with no anchor cannot be attributed to a source. Not to be confused with NamingSystem/clinic-service-organization-identifier, whose value is a tenant id identifying the practice as a party in a store provisioned by WELL; this system's value identifies the deployment a record was ingested from, and one Organization may carry both.

Type	Value	Preferred
uri	../NamingSystem/organization-identifier	true