STU 3 Candidate

This page is part of the FHIR Specification (v1.4.0: STU 3 Ballot 3). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

1.30.1.11.94 Code System http://hl7.org/fhir/conformance-statement-kind

This is a value set defined by the FHIR project.

Summary

Defining URL:http://hl7.org/fhir/conformance-statement-kind
Name:ConformanceStatementKind
Definition:How a conformance statement is intended to be used.
Committee:FHIR Infrastructure Work Group
OID:2.16.840.1.113883.4.642.1.94 (for OID based terminology systems)
Source ResourceXML / JSON

This Code system is used in the following value sets:

1.30.1.11.94.1 Content

1.30.1.11.94.2 ConformanceStatementKind

How a conformance statement is intended to be used.

This code system http://hl7.org/fhir/conformance-statement-kind defines the following codes:

CodeDisplayDefinitionComments
instance InstanceThe Conformance instance represents the present capabilities of a specific system instance. This is the kind returned by OPTIONS for a FHIR server end-point.
capability CapabilityThe Conformance instance represents the capabilities of a system or piece of software, independent of a particular installation.Elements marked as 'optional' represent configurable capabilities
requirements RequirementsThe Conformance instance represents a set of requirements for other systems to meet; e.g. as part of an implementation guide or 'request for proposal'.

 

See the full registry of value sets 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. In this scheme, some codes are under other codes, and imply that the code they are under also applies
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)
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