This page is part of the FHIR Specification v6.0.0-ballot1: Release 6 Ballot (1st Draft) (see Ballot Notes). The current version is 5.0.0. For a full list of available versions, see the Directory of published versions
FHIR Infrastructure Work Group | Maturity Level: 0 | Informative | Use Context: Country: World, Not Intended for Production use |
Official URL: http://hl7.org/fhir/ValueSet/usage-context-agreement-scope
|
Version: 6.0.0-ballot1 | |||
draft as of 2023-12-18 | 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:
Codes for use in UsageContext.valueCodeableConcept when UsageContext.code is agreement-scope
http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope
This expansion generated 18 Dec 2023
Expansion based on codesystem Usage Context Agreement Scope v6.0.0-ballot1 (CodeSystem)
This value set contains 6 concepts
Code | System | Display | Definition |
realm-base | http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope | 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. |
knowledge | http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope | 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. |
domain | http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope | 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. |
community | http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope | Community | Sets contractual or business expectations for systems participating in a particular exchange community. |
system-design | http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope | 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. |
system-implementation | http://hl7.org/fhir/CodeSystem/usage-context-agreement-scope | 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'. |
See the full registry of value sets defined as part of FHIR.
Explanation of the columns that may appear on this page:
Lvl | A 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 |
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 |