Release 5 FHIR CI-Build

This page is part of the Continuous Integration Build of FHIR Specification (v5.0.0: R5 - STU ). This is the current published version in it's permanent home (it will always (will be available incorrect/inconsistent at this URL). For a full list of available versions, see times).
See the Directory of published versions icon

4.3.2.15 CodeSystem http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope

  Maturity Level : 0
Responsible Owner: FHIR Infrastructure icon Work Group Informative Use Context : Country: World
Official URL : http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope Version : 5.0.0 6.0.0-ballot3
draft as of 2023-03-26 2025-11-24 Computable Name : UsageContextAgreementScope
Flags : CaseSensitive, Complete. All codes ValueSet: Usage Context Agreement Scope OID : 2.16.840.1.113883.4.642.4.1798

This Code system is used in the following FHIR core-defined or referenced value sets:


This codesystem defines codes describing the type of agreement represented by an artifact, for example for use in CanonicalResource.usageContext.

Generated Narrative: CodeSystem usage-context-agreement-scope

Last updated: 2025-11-24T20:46:00.1Z

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

Code Display Definition Copy
realm-base Realm 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. btn   btn
knowledge Knowledge Defines use-case-specific information or guidance that is relevant to a specific business or health domain but is not mandated for particular use. btn   btn
domain Domain 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. btn   btn
community Community Sets contractual or business expectations for systems participating in a particular exchange community. btn   btn
system-design System 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. btn   btn
system-implementation System 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'. btn   btn

 

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


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. See Code System for further information.
Source 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). If the code is in italics, this indicates that the code is not selectable ('Abstract')
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