FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5
0.0.1-snapshot-2 - informative International flag

FHIR Cross-Version Extensions package for FHIR R4 from FHIR R5 - Version 0.0.1-snapshot-2. See the Directory of published versions

ValueSet: Cross-version VS for R5.IdentifierScope for use in FHIR R4

Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-v3-IdentifierScope-for-R4 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 0 Computable Name: R5_v3_IdentifierScope_for_R4

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-IdentifierScope 2.0.0 for use in FHIR R4. Concepts not present here have direct equivalent mappings crossing all versions from R5 to R4.

References

This value set is not used here; it may be used elsewhere (e.g. specifications and/or implementations that use this content)

Logical Definition (CLD)

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-IdentifierScope version 2.1.0
    CodeDisplayDefinition
    BUSNBusiness 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.
    OBJObject Identifier**Description:** The identifier associated with a particular object. It remains consistent as the object undergoes state transitions.
    VERVersion 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.
    VWView 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.

 

Expansion

This value set expansion contains 4 concepts.

CodeSystemDisplayDefinition
  BUSNhttp://terminology.hl7.org/CodeSystem/v3-IdentifierScopeBusiness 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.

  OBJhttp://terminology.hl7.org/CodeSystem/v3-IdentifierScopeObject Identifier

Description: The identifier associated with a particular object. It remains consistent as the object undergoes state transitions.

  VERhttp://terminology.hl7.org/CodeSystem/v3-IdentifierScopeVersion 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.

  VWhttp://terminology.hl7.org/CodeSystem/v3-IdentifierScopeView 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.

Explanation of the columns that may appear on this page:

Level A few code lists that FHIR defines are hierarchical - each code is assigned a level. In this scheme, some codes are under other codes, and imply that the code they are under also applies
System The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code The code (used as the code in the resource instance)
Display The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition An explanation of the meaning of the concept
Comments Additional notes about how to use the code