Release Date: 2015-07-31

OID for code system: 2.16.840.1.113883.5.1116

OID for value set: 2.16.840.1.113883.1.11.20276 (this is the value set that includes the entire code system)

Description

Description: 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.


Level Code Display Definition
1 BUSN Business Identifier Description: 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.
1 OBJ Object Identifier Description: The identifier associated with a particular object. It remains consistent as the object undergoes state transitions.
1 VER Version Identifier Description: 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.
1 VW View Specific Identifier Description: 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.