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

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

This cross-version ValueSet represents concepts from http://terminology.hl7.org/ValueSet/v3-ActRelationshipHasOption 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
    OPTNhas optionA relationship between a source Act that provides more detailed properties to the target Act.

    The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements.

    The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements.

    Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options.

 

Expansion

This value set expansion contains 1 concepts.

CodeSystemDisplayDefinition
  OPTNhttp://terminology.hl7.org/CodeSystem/v3-ActRelationshipTypehas option

A relationship between a source Act that provides more detailed properties to the target Act.

The source act thus is a specialization of the target act, but instead of mentioning all the inherited properties it only mentions new property bindings or refinements.

The typical use case is to specify certain alternative variants of one kind of Act. The priorityNumber attribute is used to weigh refinements as preferred over other alternative refinements.

Example: several routing options for a drug are specified as one SubstanceAdministration for the general treatment with attached refinements for the various routing options.

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