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

Official URL: http://hl7.org/fhir/5.0/ValueSet/R5-usage-context-agreement-scope-for-R4 Version: 0.0.1-snapshot-2
Standards status: Informative Maturity Level: 0 Computable Name: R5_usage_context_agreement_scope_for_R4

This cross-version ValueSet represents concepts from http://hl7.org/fhir/ValueSet/usage-context-agreement-scope 5.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://hl7.org/fhir/CodeSystem/usage-context-agreement-scope version 5.0.0
    CodeDisplayDefinition
    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.
    knowledgeKnowledgeDefines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use.
    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.
    communityCommunitySets contractual or business expectations for systems participating in a particular exchange community.
    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.

CodeSystemDisplayDefinition
  realm-basehttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeRealm 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.
  knowledgehttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeKnowledgeDefines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use.
  domainhttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeDomainDefines 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.
  communityhttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeCommunitySets contractual or business expectations for systems participating in a particular exchange community.
  system-designhttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeSystem 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-implementationhttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeSystem 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