{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "fragment",
  "name": "NexusDocumentTypeCS",
  "id": "nexus-document-type",
  "title": "Document Type CodeSystem",
  "description": "Marks a `DocumentReference` this EMR generated and filed, and says which kind of document it is.\n\nWritten as a `Coding` on both `DocumentReference.type` and `DocumentReference.category`: the\ncategory copy is what a server-side search filters on, the type copy is the check a reader applies\nto a document already in hand. They are the same coding.\n\n**It rides alongside the classification, it does not replace it.** The LOINC document categories\nthis guide describes for `category` remain the classification axis. This marker answers the\nnarrower question of whether the EMR produced and filed the document, which no LOINC code answers.\n\n**Distinct from `nexus-composition-type`**, which names summary kinds on `Composition.category`. A\ncode from one system says nothing on the other.\n\nContent is `fragment`: one code is established in the writing code today, and a producer may file a\ndocument under a code not listed here. Do not treat this list as exhaustive, and do not reject an\nunrecognized code under this system.\n\n**Nexus EMR writes this today at `http://services.well.com/fhir/CodeSystem/document-type`\n(FHIR-380)**: it is live in stored `DocumentReference.type` and `DocumentReference.category`\ncodings and in code, and is under migration to the canonical declared here. Write the canonical;\nexpect both until the migration completes, and note that a search by category token matches one\naddress or the other but never both at once.",
  "url": "https://fhir.apps.health/CodeSystem/nexus-document-type",
  "concept": [
    {
      "code": "lab-requisition",
      "display": "Lab requisition",
      "definition": "A 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."
    }
  ],
  "experimental": false,
  "caseSensitive": true
}