Skip to content

Nexus Composition Type CodeSystem Code system

Canonicalhttps://fhir.apps.health/CodeSystem/nexus-composition-type
Statusdraft · 1.33.0
Contentcomplete
SourceFSH · JSON

Summary kinds this estate produces for which LOINC has no concept.

Used on Composition.category, alongside LOINC, as a refinement of the class Composition.type carries. Despite this system's name, its codes are not written to Composition.type -- that element carries one of three LOINC class codes, see nexus-emr-composition-classification. The name is historical and is kept because renaming a published code system breaks stored codings.

A generated day-sheet summary is type = LOINC 34133-9 "Summary of episode note" and category = nexus-daysheet-summary.

CodeDisplayDefinition
nexus-daysheet-summaryDay-sheet summaryA summary generated ahead of a clinic day for a booked patient, covering what a provider should know before the visit. Class: LOINC 34133-9. Regenerated when its inputs change, so it is a current view rather than a record of a moment.
nexus-interval-summaryInterval summaryA summary of what happened to a patient between two points in time -- typically since the last visit. Class: LOINC 34133-9. Distinguished from a day-sheet summary by covering an INTERVAL rather than preparing for an appointment; there may be no upcoming visit at all.
nexus-encounter-recapEncounter recapA summary of a SINGLE encounter, generated after it. Class: LOINC 34133-9. Not interchangeable with the other two: a recap asserts that the encounter it covers took place, which neither of the others does.
nexus-letter-templateLetter templateA stored template a letter is composed from, rather than a letter sent about a patient. Minted so that the retired `http://services.well.com/fhir/categories/letter-template` category has a home on this guide's own base if one turns out to still be needed. Templates are modelled as `List` as of 1.21.0, so a producer should check whether it needs this code at all before using it.