Skip to content

Document Type CodeSystem Code system

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

Marks a DocumentReference this EMR generated and filed, and says which kind of document it is.

Written as a Coding on both DocumentReference.type and DocumentReference.category: the category copy is what a server-side search filters on, the type copy is the check a reader applies to a document already in hand. They are the same coding.

It rides alongside the classification, it does not replace it. The LOINC document categories this guide describes for category remain the classification axis. This marker answers the narrower question of whether the EMR produced and filed the document, which no LOINC code answers.

Distinct from nexus-composition-type, which names summary kinds on Composition.category. A code from one system says nothing on the other.

Content is fragment: one code is established in the writing code today, and a producer may file a document under a code not listed here. Do not treat this list as exhaustive, and do not reject an unrecognized code under this system.

Nexus EMR now writes the canonical declared here. The retired address, http://services.well.com/fhir/CodeSystem/document-type, persists only on DocumentReference.type and DocumentReference.category codings filed before the move; a reader must still recognize it there. A comma-joined category-token search covers both addresses in one search, which is how a reader finds documents filed under either.

CodeDisplayDefinition
lab-requisitionLab requisitionA laboratory requisition sheet this EMR filled, rendered and filed against the order it prints. The document is the paper that went out, not a re-render of the order: a reprint of a placed order serves the stored sheet rather than rebuilding one, because a rebuild depends on the template asset and the fill code still being what they were. An order printed at two versions holds two sheets.
terms-and-conditionsTerms and conditionsThe terms and conditions every user accepts at sign-in, one version per document. Held once with no subject, so it is never a patient's document; it is found by its identifier under the nexus-terms-and-conditions naming system, not by this type.