Binding-conformance.xml

Definition for Value SetBindingConformance

{
  "resourceType": "ValueSet",
  "text": {
    "status": "generated",
    "div": "<div><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>"
  },
  "identifier": "http://hl7.org/fhir/vs/binding-conformance",
  "name": "BindingConformance",
  "publisher": "HL7 (FHIR Project)",
  "telecom": [
    {
      "system": "url",
      "value": "http://hl7.org/fhir"
    },
    {
      "system": "email",
      "value": "fhir@lists.hl7.org"
    }
  ],
  "description": "Binding conformance for applications",
  "status": "draft",
  "date": "2014-09-30T18:09:16.976+10:00",
  "define": {
    "system": "http://hl7.org/fhir/binding-conformance",
    "caseSensitive": true,
    "concept": [
      {
        "code": "required",
        "definition": "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."
      },
      {
        "code": "preferred",
        "definition": "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."
      },
      {
        "code": "example",
        "definition": "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."
      }
    ]
  }
}