Extensions for Using Data Elements from FHIR R5 in FHIR R4
0.1.0 - STU International flag

Extensions for Using Data Elements from FHIR R5 in FHIR R4 - Downloaded Version null See the Directory of published versions

ValueSet: R5UsageContextAgreementScopeForR4

Official URL: http://hl7.org/fhir/uv/xver/ValueSet/R5-usage-context-agreement-scope-for-R4 Version: 0.1.0
Standards status: Trial-use Maturity Level: 0 Computable Name: R5UsageContextAgreementScopeForR4

This cross-version ValueSet represents content from http://hl7.org/fhir/ValueSet/usage-context-agreement-scope|5.0.0 for use in FHIR R4.

This value set is part of the cross-version definitions generated to enable use of the value set http://hl7.org/fhir/ValueSet/usage-context-agreement-scope|5.0.0 as defined in FHIR R5 in FHIR R4.

The source value set is bound to the following FHIR R5 elements:

Note that all concepts are included in this cross-version definition because no concepts have compatible representations

Following are the generation technical comments:

FHIR ValueSet http://hl7.org/fhir/ValueSet/usage-context-agreement-scope|5.0.0, defined in FHIR R5 does not have any mapping to FHIR 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://hl7.org/fhir/CodeSystem/usage-context-agreement-scope version 📍5.0.0
    CodeDisplayDefinition
    communityCommunitySets contractual or business expectations for systems participating in a particular exchange community.
    domainDomainDefines use-case-specific requirements for a specific business or health domain. May vary in jurisdictional scope from international to small region and in business scope from broad to narrow.
    knowledgeKnowledgeDefines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use.
    realm-baseRealm BaseDefines use-case independent foundational expectations for exchange within a particular country or jurisdiction. Should be accompanied by a jurisdiction. Commonly used as a 'base' for more restrictive artifacts.
    system-designSystem DesignDocuments the specific capabilities of a single system as 'available' for purchase or use. May have some variability reflecting options that can be configured.
    system-implementationSystem ImplementationDocuments the specific points of a single production system or endpoint. This may be time-specific - i.e. reflecting the system 'as it is now' or 'as it was at some point in the past'.

 

Expansion

This value set expansion contains 6 concepts.

SystemVersionCodeDisplayDefinitionJSONXML
http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope5.0.0  communityCommunitySets contractual or business expectations for systems participating in a particular exchange community.
http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope5.0.0  domainDomainDefines use-case-specific requirements for a specific business or health domain. May vary in jurisdictional scope from international to small region and in business scope from broad to narrow.
http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope5.0.0  knowledgeKnowledgeDefines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use.
http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope5.0.0  realm-baseRealm BaseDefines use-case independent foundational expectations for exchange within a particular country or jurisdiction. Should be accompanied by a jurisdiction. Commonly used as a 'base' for more restrictive artifacts.
http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope5.0.0  system-designSystem DesignDocuments the specific capabilities of a single system as 'available' for purchase or use. May have some variability reflecting options that can be configured.
http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope5.0.0  system-implementationSystem ImplementationDocuments the specific points of a single production system or endpoint. This may be time-specific - i.e. reflecting the system 'as it is now' or 'as it was at some point in the past'.

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