Encounter Visit Types Value set

Canonical	../ValueSet/encounter-visit-types
Status	draft · 1.26.0
Source	FSH · JSON

The visit types a note may declare it was opened on, bound extensible from the composition-note-setup extension on Composition.

Extensible rather than required. The set is closed in the application -- every writer is typed against the same eight codes, and no producer emits anything outside them -- so a required binding would have been additive. It is still not the right strength: required would make this guide a release gate on the note editor, so that shipping a new visit type makes every note carrying one nonconformant until the guide cuts a release. The catalogue has a known gap today (it offers no paediatric visit type), so the set is expected to grow on the product's cadence.

This set is how a visit type becomes named, not a fence around what may exist. A writer whose visit type is listed here uses this code; a writer shipping one the guide has not named yet is conformant carrying its own. A reader meeting an unfamiliar code writes it back unchanged: this is editor state, and normalising an unknown visit type to a familiar one changes which templates the next provider is offered.

Codes from Encounter Visit Type CodeSystem

All 8 codes from this system, defined by this specification.

Code	Display
prenatal-checkup	Prenatal checkup
annual-physical	Annual physical
diabetes-follow-up	Diabetes follow-up
same-day-urgent	Same-day urgent
phone-call	Phone call
mental-health	Mental health
procedure	Procedure
form-visit	Form visit