NexusEmrAppDeviceIdentifier Naming system

Status: draft · 1.26.0 · JSON

Identifies a registered application -- an AI scribe, a patient portal, a research tool -- by its registration slug. The namespace carries no instance segment, deliberately: a registered application is the same application in every tenant, so an AI scribe deployed to forty practices is one registration rather than forty. This is how an application is named wherever it appears as a logical reference, an identifier with no resolvable reference, which is the case a declared namespace exists to make resolvable. Three profiles depend on it: an item consent's provision actor, naming which application a patient granted or denied; a Composition author, naming which application drafted a note; and a Provenance agent, naming which application produced or cited content. A reader that cannot resolve this system cannot distinguish one application from another, and on a consent decision that is the difference between honouring the patient's choice and misattributing it. The same value appears on the application's own Device registration, where a writer is additionally asked to carry the OAuth client_id; the two are not required to be equal and a reader must not assume it, since the slug names the registration while the client_id names an OAuth client and one registration may be issued several credentials over its life. Values are assigned once at registration and are stable for its life; they are never minted per record.

Type	Value	Preferred
uri	../NamingSystem/nexus-emr-appdevice-identifier	true