v3 Code System IdentifierScope

v3 Code System IdentifierScope

activeFHIR R3 package : Core3.0.2complete4 concepts

Codes to specify the scope in which the identifier applies to the object with which it is associated, and used in the datatype property II.

Metadata

hl7.org/fhir
Canonical URL
http://hl7.org/fhir/v3/IdentifierScope
ID
v3-IdentifierScope
Version
2016-11-11
Publisher
HL7, Inc
Case Sensitive
Yes
Hierarchy
is-a

Concepts (4)

CodeDisplayDefinition
BUSNBusiness IdentifierDescription: An identifier whose scope is defined by the business practices associated with the object. In contrast to the other scope identifiers, the scope of the use of the id is not necessarily restricted to a single object, but may be reused for other objects closely associated with the object due to business practice.
OBJObject IdentifierDescription: The identifier associated with a particular object. It remains consistent as the object undergoes state transitions.
VERVersion IdentifierDescription: An identifier that references a particular object as it existed at a given point in time. The identifier SHALL change with each state transition on the object. I.e. The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being (though the control act may never be instantiated). NOTE: Applications that do not support versioning of objects must ignore and not persist these ids to avoid confusion resulting from leaving the same identifier on an object that undergoes changes.
VWView Specific IdentifierDescription: An identifier that references a particular object as it existed at a given point in time. The identifier SHALL change with each state transition on the object. Example The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being (though the control act may never be instantiated). NOTE: Applications that do not support versioning of objects must ignore and not persist these ids to avoid confusion resulting from leaving the same identifier on an object that undergoes changes.