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

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

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasValue 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
    VALUEhas value**Description:**Indicates that the target Act represents the result of the source observation Act.

    **FormalConstraint:** Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified

    **UsageNote:** This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute. For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation.

    The valueNegationInd attribute on the source Act has the same semantics of "negated finding" when it applies to the target of a VALUE ActRelationship as it does to the value attribute. On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding. Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd.

    **OpenIssue:** The implications of negationInd on ActRelationship and the valueNegationind on Observation.

 

Expansion

This value set expansion contains 1 concepts.

CodeSystemDisplayDefinition
  VALUEhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas value

**Description:**Indicates that the target Act represents the result of the source observation Act.

FormalConstraint: Source Act must be an Observation or specialization there-of. Source Act must not have the value attribute specified

UsageNote: This relationship allows the result of an observation to be fully expressed as RIM acts as opposed to being embedded in the value attribute. For example, sending a Document act as the result of an imaging observation, sending a list of Procedures and/or other acts as the result of a medical history observation.

The valueNegationInd attribute on the source Act has the same semantics of "negated finding" when it applies to the target of a VALUE ActRelationship as it does to the value attribute. On the other hand, if the ActRelationship.negationInd is true for a VALUE ActRelationship, that means the specified observation does not have the indicated value but does not imply a negated finding. Because the semantics are extremely close, it is recommended that Observation.valueNegationInd be used, not ActRelationship.negationInd.

OpenIssue: The implications of negationInd on ActRelationship and the valueNegationind on Observation.

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