{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "complete",
  "name": "ContactByFaxCS",
  "id": "contact-by-fax",
  "title": "Contact by Fax Tag CodeSystem",
  "description": "Records whether outbound correspondence to a practitioner should be sent by fax. Carried as a tag\non `Practitioner.meta.tag`, where this is the tag's `system`.\n\n**A tag, not an extension.** The address identifies the `system` of a `Coding` in `meta.tag`, which\nis why it is declared as a code system. The vocabulary is the unusual part: the codes are the\nliteral strings `true` and `false`.\n\n**Absent means not enabled.** A missing tag and the code `false` mean the same thing; `false` exists\nso a writer can clear the preference in place rather than remove the coding. Compare\ncase-insensitively, and treat anything that is not `true` as not enabled rather than as an error.\n\n**One of five sibling systems, one per contact method.** The other four are\n`https://fhir.apps.health/CodeSystem/contact-by-email`,\n`https://fhir.apps.health/CodeSystem/contact-by-hrm`,\n`https://fhir.apps.health/CodeSystem/contact-by-mail` and\n`https://fhir.apps.health/CodeSystem/contact-by-phone`, each carrying this same `true` / `false`\nvocabulary under its own address. They are independent: any combination may be enabled, the set\ndoes not rank them, and the state of one says nothing about the others. They are separate systems\nbecause a writer keeps a single tag per system, replacing rather than adding, so five methods\nsharing one system would clear each other.\n\n**A routing preference, not a `ContactPoint`.** `Practitioner.telecom` says what a practitioner's\naddresses are; this says which of them outbound correspondence should use. It does not assert that\na fax number is recorded, and it is not a consent.\n\n**Nexus EMR writes this today at\n`http://services.well.com/fhir/CodeSystem/contact-by-fax` (FHIR-376)**: it is live in stored\n`Practitioner.meta.tag` codings and in code, and is under migration to the canonical declared here.\nWrite the canonical; expect both until the migration completes. The two addresses share their final\nsegment, but the scheme, the host and the `/fhir` path prefix differ, so match each exactly rather\nthan deriving one from the other.",
  "url": "https://fhir.apps.health/CodeSystem/contact-by-fax",
  "concept": [
    {
      "code": "true",
      "display": "Enabled",
      "definition": "Outbound correspondence to this practitioner should be sent by fax."
    },
    {
      "code": "false",
      "display": "Not enabled",
      "definition": "Outbound correspondence to this practitioner should not be sent by fax. Carries nothing an absent tag does not -- it exists so the preference can be cleared in place."
    }
  ],
  "experimental": false,
  "caseSensitive": false,
  "count": 2
}