{
  "resourceType": "ValueSet",
  "status": "draft",
  "name": "NoteBlockTypesVS",
  "id": "note-block-types",
  "title": "Note Block Types",
  "description": "The render kinds a structured section may declare, bound `extensible` from the\nblock-type extension on `Composition.section`.\n\nThe kinds named today are those with a block some stream composes. Four arrive declared on the\nwire, all from the note editor: `text`, `heading-1`, `heading-2` and the chronic-care review's\n`fields-diabetes`. Three are named ahead of the declaration -- the letter composer's\n`merge-field-body` and `enclosures`, and the summary graphs' `cited-claims` -- because those\nstreams file their sections without stamping the kind. Identify those three by their other markers\nas well: the enclosures section by its LOINC `28562-7` code, a cited summary by the citation trail\non its Provenance, a merge-field body by the letter that holds it.\n\n**This set is how a kind becomes named, not a fence around what may exist**: a writer whose kind is\nlisted here uses this code, and a writer shipping a kind the guide has not named yet is conformant\ncarrying its own. Adding a kind is an edit to this set, to its code system, and to the EMR's block\nregistry together. A section declaring no kind at all predates the extension and reads as `text`.",
  "url": "https://fhir.apps.health/ValueSet/note-block-types",
  "experimental": false,
  "compose": {
    "include": [
      {
        "system": "https://fhir.apps.health/CodeSystem/note-block-type"
      }
    ]
  }
}