subdepartment extension, not where it belongs

The subdepartment extension has this description. "An additional element that provides the subdepartment that created the authorization request."

However it's described on an identifier, which has broader utilization that just an authorization request. As this extension extends "authorization request" then it belongs on the resource that is an authorization request. (Claim?)

Jurisdiction extension is weird. The description is, put data here so you don't have to lookup data where it belongs. (This is called de-normalization, "Put the patient data on the condition resource so we don't have to fetch the patient resource." Typically the wrong thing to do.)

The example is "state dl". My DL issued by NC is good in all 50 states, even though NC has no "jurisdiction" in SC. Is it jurisdiction of the issuing authority or jurisdiction of "where valid at". Also shouldn't the jurisdiction be on "the thing" (like a qualification, or a license) not an identifier on "the thing". As technically, every issued identifier, has global identifier jurisdiction, even if the thing it identifies does not.