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.ActRelationshipActProvenance for use in FHIR R4

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

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ActRelationshipActProvenance 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-ActRelationshipType version 3.1.0
    CodeDisplayDefinition
    COMPhas componentThe target act is a component of the source act, with no semantics regarding composition or aggregation implied.
    SUBJhas subjectRelates an Act to its subject Act that the first Act is primarily concerned with.

    Examples

    1. The first Act may be a ControlAct manipulating the subject Act
    2. The first act is a region of interest (ROI) that defines a region within the subject Act.
    3. The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.

    Constraints

    An Act may have multiple subject acts.

    Rationale

    The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship.
    SUCCsucceeds**Definition:** A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act.
    UPDTupdates (condition)A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread.
    XCRPTExcerptsThe source is an excerpt from the target.

 

Expansion

This value set expansion contains 5 concepts.

CodeSystemDisplayDefinition
  COMPhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas component

The target act is a component of the source act, with no semantics regarding composition or aggregation implied.

  SUBJhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas subject

Relates an Act to its subject Act that the first Act is primarily concerned with.

Examples

  1. The first Act may be a ControlAct manipulating the subject Act
  2. The first act is a region of interest (ROI) that defines a region within the subject Act.
  3. The first act is a reporting or notification Act, that echos the subject Act for a specific new purpose.

Constraints

An Act may have multiple subject acts.

Rationale

The ActRelationshipType "has subject" is similar to the ParticipationType "subject", Acts that primarily operate on physical subjects use the Participation, those Acts that primarily operate on other Acts (other information) use the ActRelationship.

  SUCChttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypesucceeds

Definition: A new act that carries forward the intention of the original act, but does not completely replace it. The status of the predecessor act must be 'completed'. The original act is the target act and the successor is the source act.

  UPDThttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeupdates (condition)

A condition thread relationship specifically links condition nodes together to form a condition thread. The source is the new condition node and the target links to the most recent node of the existing condition thread.

  XCRPThttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypeExcerpts

The source is an excerpt from the target.

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