{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "complete",
  "name": "NexusCdsContentStatusCS",
  "id": "nexus-cds-content-status",
  "title": "CDS Content Status Tag CodeSystem",
  "description": "The state of the decision-support CONTENT a suggestion task was projected from, carried as a tag on\n`Task.meta.tag` where this is the tag's `system`. Distinct from `Task.status`, which describes the\nWORK rather than the rule content behind it.\n\n**Presence is the assertion; absence is not.** A task carrying `unsigned-draft` was raised from\ncontent loaded without requiring clinical sign-off, and a consumer should surface it as such. A task\ncarrying no tag under this system asserts nothing: it may come from a producer that requires\nsign-off, or from one that does not write this system at all, and the two are indistinguishable.\nNever read an absent tag as \"the content was signed\".\n\n**It records the check, not the pack.** The tag says what the loading instance verified. Content\nthat happens to carry a sign-off record is still tagged when the instance that loaded it had the\nsign-off requirement switched off.\n\n**Not a security label, and not a substitute for one.** Machine-authored tasks carry `AIAST` in\n`meta.security`; that says who wrote the suggestion. This says what state the rule behind it was in.\nThe two are orthogonal and neither can be inferred from the other.\n\n**At most one coding under this system.** Writers set `meta.tag` whole rather than appending; a\nreader should take the first and not reconcile two.\n\n**Not bound from any profile.** `meta.tag` is open on every resource and is not sliced in this\nguide. This system is declared so the tag's `Coding.system` resolves, not to add an element to the\nTask profile.",
  "url": "https://fhir.apps.health/CodeSystem/nexus-cds-content-status",
  "concept": [
    {
      "code": "unsigned-draft",
      "display": "Unsigned draft CDS content",
      "definition": "The decision-support content this task was projected from was loaded WITHOUT requiring clinical sign-off. It says the loading instance did not check for a sign-off, not that the content lacks one. A consumer should badge the suggestion as draft and may withdraw the tagged set once signed content is in place; it does not by itself make the suggestion wrong, and it does not change how the task is worked."
    }
  ],
  "experimental": false,
  "caseSensitive": true,
  "count": 1
}