{
  "resourceType": "ValueSet",
  "status": "draft",
  "name": "EncounterVisitTypesVS",
  "id": "encounter-visit-types",
  "title": "Encounter Visit Types",
  "description": "The visit types a note may declare it was opened on, bound `extensible` from the\n`composition-note-setup` extension on `Composition`.\n\n**Extensible rather than required.** The set is closed in the application -- every writer is typed\nagainst the same eight codes, and no producer emits anything outside them -- so a required binding\nwould have been additive. It is still not the right strength: required would make this guide a\nrelease gate on the note editor, so that shipping a new visit type makes every note carrying one\nnonconformant until the guide cuts a release. The catalogue has a known gap today (it offers no\npaediatric visit type), so the set is expected to grow on the product's cadence.\n\n**This set is how a visit type becomes named, not a fence around what may exist.** A writer whose\nvisit type is listed here uses this code; a writer shipping one the guide has not named yet is\nconformant carrying its own. A reader meeting an unfamiliar code writes it back unchanged: this is\neditor state, and normalising an unknown visit type to a familiar one changes which templates the\nnext provider is offered.",
  "url": "https://fhir.apps.health/ValueSet/encounter-visit-types",
  "experimental": false,
  "date": "2026-09-07",
  "compose": {
    "include": [
      {
        "system": "https://fhir.apps.health/CodeSystem/encounter-visit-type"
      }
    ]
  }
}