Snapshot 3: Connectathon 32 Base

This page is part of the FHIR Specification (v5.0.0-snapshot3: R5 Snapshot #3, to support Connectathon 32). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

4.4.1.709 ValueSet http://hl7.org/fhir/ValueSet/usage-context-agreement-scope

FHIR Infrastructure icon Work Group Maturity Level: 0Informative Use Context: Country: World, Not Intended for Production use, Not Intended for Production use
Official URL: http://hl7.org/fhir/ValueSet/usage-context-agreement-scope Version: 5.0.0-snapshot3
draft as of 2022-12-14 Computable Name: UsageContextAgreementScope
Flags: Experimental, Immutable OID: 2.16.840.1.113883.4.642.3.3302

This value set is used in the following places:

4.4.1.709.1 Definition

Codes for use in UsageContext.valueCodeableConcept when UsageContext.code is agreement-scope

4.4.1.709.2 Content Logical Definition

 

4.4.1.709.3 Expansion

This expansion generated 14 Dec 2022

This value set contains 6 concepts

Expansion based on Usage Context Agreement Scope v5.0.0-snapshot3 (CodeSystem)

CodeSystemDisplayDefinition
  realm-basehttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeRealm Base

Defines 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-scopeKnowledge

Defines 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-scopeDomain

Defines 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-scopeCommunity

Sets contractual or business expectations for systems participating in a particular exchange community.

  system-designhttp://hl7.org/fhir/CodeSystem/usage-context-agreement-scopeSystem Design

Documents 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 Implementation

Documents 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'.

 

See the full registry of value sets defined as part of FHIR.

Explanation of the columns that may appear on this page:

LvlA few code lists that FHIR defines are hierarchical - each code is assigned a level. For value sets, levels are mostly used to organize codes for user convenience, but may follow code system hierarchy - see Code System for further information
SourceThe source of the definition of the code (when the value set draws in codes defined elsewhere)
CodeThe code (used as the code in the resource instance). If the code is in italics, this indicates that the code is not selectable ('Abstract')
DisplayThe 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
DefinitionAn explanation of the meaning of the concept
CommentsAdditional notes about how to use the code