R4 Ballot #2 (Mixed Normative/Trial use)

This page is part of the FHIR Specification (v3.5.0: R4 Ballot #2). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R5 R4 R3 R2

4.4.1.514 Value Set http://hl7.org/fhir/ValueSet/conformance-expectation

FHIR Infrastructure Work Group Maturity Level: 0Informative Use Context: Any

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/ValueSet/conformance-expectation
Version:3.5.0
Name:ConformanceExpectation
Title:ConformanceExpectation
Definition:

Indicates the degree of adherence to a specified behavior or capability expected for a system to be deemed conformant with a specification.

Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.3.919 (for OID based terminology systems)
Source ResourceXML / JSON

This value set is used in the following places:

4.4.1.514.1 Content Logical Definition

This value set includes codes from the following code systems:

 

4.4.1.514.2 Expansion

This expansion generated 19 Aug 2018

This value set contains 4 concepts

Expansion based on http://terminology.hl7.org/CodeSystem/conformance-expectation version 3.5.0

All codes from system http://terminology.hl7.org/CodeSystem/conformance-expectation

CodeDisplayDefinition
SHALLSHALLSupport for the specified capability is required to be considered conformant.
SHOULDSHOULDSupport for the specified capability is strongly encouraged, and failure to support it should only occur after careful consideration.
MAYMAYSupport for the specified capability is not necessary to be considered conformant, and the requirement should be considered strictly optional.
SHOULD-NOTSHOULD-NOTSupport for the specified capability is strongly discouraged and should occur only after careful consideration.

 

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