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

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

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ActRelationshipOutcome 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
    OUTChas outcomeAn observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called "post-conditional".) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link is often inverted to describe an outcome assessment.
    OBJChas continuing objectiveA desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood.
    OBJFhas final objectiveA desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood.
    GOALhas goalA goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood.
    RISKhas riskA noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed.

 

Expansion

This value set expansion contains 5 concepts.

CodeSystemDisplayDefinition
  OUTChttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas outcome

An observation that should follow or does actually follow as a result or consequence of a condition or action (sometimes called "post-conditional".) Target must be an observation as a goal, risk or any criterion. For complex outcomes a conjunction attribute (AND, OR, XOR) can be used. An outcome link is often inverted to describe an outcome assessment.

  OBJChttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas continuing objective

A desired state that a service action aims to maintain. E.g., keep systolic blood pressure between 90 and 110 mm Hg. Source is an intervention service. Target must be an observation in criterion mood.

  OBJFhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas final objective

A desired outcome that a service action aims to meet finally. Source is any service (typically an intervention). Target must be an observation in criterion mood.

  GOALhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas goal

A goal that one defines given a patient's health condition. Subsequently planned actions aim to meet that goal. Source is an observation or condition node, target must be an observation in goal mood.

  RISKhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas risk

A noteworthy undesired outcome of a patient's condition that is either likely enough to become an issue or is less likely but dangerous enough to be addressed.

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