Release 5 Ballot

This page is part of the FHIR Specification (v5.0.0-ballot: FHIR R5 Ballot Preview). 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.3.2.18 CodeSystem http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope

FHIR Infrastructure Work Group Maturity Level: 0Informative Use Context: Not Intended for Production use, Not Intended for Production use

This is a code system defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope
Version:5.0.0-ballot
Name:Usage Context Agreement Scope
Title:
Status:draft
Definition:

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

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.4.1798 (for OID based terminology systems)
Flags:Experimental, CaseSensitive, Complete
All codes ValueSet:Usage Context Agreement Scope

This Code system is used in the following value sets:

  • ValueSet: UsageContextAgreementScope (Codes for use in UsageContext.valueCodeableConcept when UsageContext.code is agreement-scope)

4.3.2.18.1 Content

This code system http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope defines the following codes:

CodeDisplayDefinitionCopy
realm-base Realm 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. 
knowledge KnowledgeDefines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use. 
domain DomainDefines 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. 
community CommunitySets contractual or business expectations for systems participating in a particular exchange community. 
system-design System 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-implementation System 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'. 

 

See the full registry of code systems defined as part of FHIR.

Explanation of the columns that may appear on this page:

LevelA few code lists that FHIR defines are hierarchical - each code is assigned a level. 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