This page is part of the FHIR Specification (v0.0.82: DSTU 1). 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 Value SetBindingConformance
<ValueSet xmlns="http://hl7.org/fhir"> <text> <status value="generated"/> <div xmlns="http://www.w3.org/1999/xhtml"> <h2>BindingConformance</h2> <p>Binding conformance for applications</p> <p>This value set defines its own terms in the system http://hl7.org/fhir/binding-conformance</p> <table> <tr> <td> <b>Code</b> </td> <td> <b>Display</b> </td> <td> <b>Definition</b> </td> </tr> <tr> <td>required <a name="required"> </a> </td> <td/> <td>Only codes in the specified set are allowed. If the binding is extensible, other codes may be used for concepts not covered by the bound set of codes.</td> </tr> <tr> <td>preferred <a name="preferred"> </a> </td> <td/> <td>For greater interoperability, implementers are strongly encouraged to use the bound set of codes, however alternate codes may be used in derived profiles and implementations if necessary without being considered non-conformant.</td> </tr> <tr> <td>example <a name="example"> </a> </td> <td/> <td>The codes in the set are an example to illustrate the meaning of the field. There is no particular preference for its use nor any assertion that the provided values are sufficient to meet implementation needs.</td> </tr> </table> </div> </text> <identifier value="http://hl7.org/fhir/vs/binding-conformance"/> <name value="BindingConformance"/> <publisher value="HL7 (FHIR Project)"/> <telecom> <system value="url"/> <value value="http://hl7.org/fhir"/> </telecom> <telecom> <system value="email"/> <value value="fhir@lists.hl7.org"/> </telecom> <description value="Binding conformance for applications"/> <status value="draft"/> <date value="2014-09-30T18:09:16.976+10:00"/> <define> <system value="http://hl7.org/fhir/binding-conformance"/> <caseSensitive value="true"/> <concept> <code value="required"/> <definition value="Only codes in the specified set are allowed. If the binding is extensible, other codes may be used for concepts not covered by the bound set of codes."/> </concept> <concept> <code value="preferred"/> <definition value="For greater interoperability, implementers are strongly encouraged to use the bound set of codes, however alternate codes may be used in derived profiles and implementations if necessary without being considered non-conformant."/> </concept> <concept> <code value="example"/> <definition value="The codes in the set are an example to illustrate the meaning of the field. There is no particular preference for its use nor any assertion that the provided values are sufficient to meet implementation needs."/> </concept> </define> </ValueSet>