{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "complete",
  "name": "DiagnosticReportAcdrSentCS",
  "id": "diagnostic-report-acdr-sent",
  "title": "Diagnostic Report ACDR Sent Tag CodeSystem",
  "description": "Records that a diagnostic report has been sent to Ontario Health's ACDR. Carried as a tag on\n`DiagnosticReport.meta.tag`, where this is the tag's `system`.\n\n**A tag, not an extension.** The address identifies the `system` of a `Coding` in `meta.tag`, which\nis why it is declared as a code system. The vocabulary is the unusual part: the codes are the\nliteral strings `true` and `false`, the writer's rendering of a boolean.\n\n**Absent means not sent -- and nothing more.** It does not distinguish \"not yet sent\" from \"will\nnever be sent\": a report carries no tag when its site is not configured to send, when its status is\nnot one that is sent, or when its code is not one that is sent. The tag is a record of delivery and\nnot of eligibility or of intent.\n\n**`true` means the receiver acknowledged the report.** It is written only after an accepting\nacknowledgement comes back; a rejected or failed send leaves the report untagged so it can be\nretried. It records nothing about WHICH version was accepted, or when -- it is a fact about the\nreport rather than about one version of it, and nothing clears it, so a report revised after a send\nstill carries it. A consumer that needs the timing, the version, or the acknowledgement itself\nshould read `AuditEvent`.\n\n**`false` is representable but is not written.** The vocabulary is closed by the boolean it is\nrendered from, so both codes are listed; only `true` is emitted. Read `false` exactly as an absent\ntag, compare case-insensitively, and treat anything that is not `true` as not sent rather than as\nan error.\n\n**One tag per system, and this system carries one fact.** A writer replaces any existing tag with\nthis system rather than adding a second. The parallel record of delivery downstream is a separate\nsystem, `https://fhir.apps.health/CodeSystem/diagnostic-report-sent-downstream`, precisely so that\nthe two can be held at once.\n\n**Nexus EMR writes this today at\n`http://services.well.com/fhir/tags/diagnostic-reports/acdr-sent` (FHIR-371)**: it is live in\nstored `DiagnosticReport.meta.tag` codings and in code, and is under migration to the canonical\ndeclared here. Write the canonical; expect both until the migration completes, and match both\naddresses exactly rather than deriving one from the other.",
  "url": "https://fhir.apps.health/CodeSystem/diagnostic-report-acdr-sent",
  "concept": [
    {
      "code": "true",
      "display": "Sent",
      "definition": "The report has been sent to Ontario Health's ACDR and the receiver acknowledged it. Records the delivery, not which version was delivered or when."
    },
    {
      "code": "false",
      "display": "Not sent",
      "definition": "The report has not been sent. Representable but not written by Nexus EMR; a reader should treat it exactly as an absent tag."
    }
  ],
  "experimental": false,
  "caseSensitive": false,
  "count": 2
}