Composition Classification Value set

Canonical	../ValueSet/nexus-emr-composition-classification
Status	draft · 1.26.0
Source	FSH · JSON

What kind of document a Composition is, at the coarsest useful level: an authored note, a generated summary, or a letter. Three LOINC codes, and they enumerate the axis.

This is the element a consumer switches on. Bound extensible to Composition.type only. type is 1..1 in base R4, so it is the only element guaranteed present on every Composition, which is why the one distinction every consumer needs lives there.

The refinement underneath is Composition.category, which uses nexus-composition-kind: which kind of note, which kind of summary. That set is a superset of this one, so a producer with no finer kind than the class may simply repeat the type code on category, or leave it absent. A section is a third question again, and uses nexus-composition-section.

Extensible. A code outside these three is nearly always a refinement written into the class slot, and warns. Nothing is rejected, so a document that genuinely is none of the three stays conformant.

Supersedes nexus-emr-note-classification, which named and enumerated only notes.

Codes from LOINC -- all codes

Code	Display
34109-9	Note
34133-9	Summary of Episode Note
51852-2	Letter