This page is part of the FHIR Specification (v1.6.0: STU 3 Ballot 4). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions
Definition for Code System ConformanceStatementKind
<CodeSystem xmlns="http://hl7.org/fhir"> <id value="conformance-statement-kind"/> <meta> <lastUpdated value="2016-08-11T17:02:54.322+10:00"/> </meta> <text> <status value="extensions"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2>ConformanceStatementKind</h2> <div> <p>How a conformance statement is intended to be used.</p> </div> <p>This code system http://hl7.org/fhir/conformance-statement-kind defines the following codes:</p> <table class="codes"> <tr> <td> <b>Code</b> </td> <td> <b>Display</b> </td> <td> <b>Definition</b> </td> <td> <b>Comments</b> </td> </tr> <tr> <td>instance <a name="conformance-statement-kind-instance"> </a> </td> <td>Instance</td> <td>The Conformance instance represents the present capabilities of a specific system instance. This is the kind returned by OPTIONS for a FHIR server end-point.</td> <td/> </tr> <tr> <td>capability <a name="conformance-statement-kind-capability"> </a> </td> <td>Capability</td> <td>The Conformance instance represents the capabilities of a system or piece of software, independent of a particular installation.</td> <td>Elements marked as 'optional' represent configurable capabilities</td> </tr> <tr> <td>requirements <a name="conformance-statement-kind-requirements"> </a> </td> <td>Requirements</td> <td>The Conformance instance represents a set of requirements for other systems to meet; e.g. as part of an implementation guide or 'request for proposal'.</td> <td/> </tr> </table> </div> </text> <url value="http://hl7.org/fhir/conformance-statement-kind"/> <identifier> <system value="urn:ietf:rfc:3986"/> <value value="urn:oid:2.16.840.1.113883.4.642.1.94"/> </identifier> <version value="1.6.0"/> <name value="ConformanceStatementKind"/> <status value="draft"/> <experimental value="false"/> <publisher value="HL7 (FHIR Project)"/> <contact> <telecom> <system value="other"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> </contact> <date value="2016-08-11T17:02:54+10:00"/> <description value="How a conformance statement is intended to be used."/> <caseSensitive value="true"/> <valueSet value="http://hl7.org/fhir/ValueSet/conformance-statement-kind"/> <content value="complete"/> <concept> <code value="instance"/> <display value="Instance"/> <definition value="The Conformance instance represents the present capabilities of a specific system instance. This is the kind returned by OPTIONS for a FHIR server end-point."/> </concept> <concept> <extension url="http://hl7.org/fhir/StructureDefinition/valueset-comments"> <valueString value="Elements marked as 'optional' represent configurable capabilities"/> </extension> <code value="capability"/> <display value="Capability"/> <definition value="The Conformance instance represents the capabilities of a system or piece of software, independent of a particular installation."/> </concept> <concept> <code value="requirements"/> <display value="Requirements"/> <definition value="The Conformance instance represents a set of requirements for other systems to meet; e.g. as part of an implementation guide or 'request for proposal'."/> </concept> </CodeSystem>
Usage note: every effort has been made to ensure that the examples are correct and useful, but they are not a normative part of the specification.