{
  "resourceType": "CodeSystem",
  "status": "draft",
  "content": "complete",
  "name": "AppointmentAcdrArrivedCS",
  "id": "appointment-acdr-arrived",
  "title": "Appointment ACDR Arrived Tag CodeSystem",
  "description": "Records that an appointment's arrival notification has been sent to Ontario Health's ACDR. Carried\nas a tag on `Appointment.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.** A missing tag and the code `false` mean the same\nthing to a reader. Neither distinguishes \"not yet sent\" from \"will never be sent\": an appointment\ncarries no tag when its clinic has no ACDR endpoint configured, when its patient is not in scope for\nthe provincial record, or when the arrival has not happened. The tag records a send, not eligibility\nor intent. Compare case-insensitively and treat anything that is not `true` as not sent rather than\nas an error.\n\n**It is a send marker, not a delivery receipt.** It is written once the message has been sent and\nwas not refused. It does not say the receiving system processed or accepted the record, and it\ncarries no time. A consumer that needs the timing or the message itself should read `AuditEvent`.\n\n**It says nothing about the appointment.** No clinical or scheduling fact follows from it, and the\nappointment's own status is unaffected by whether a send has happened.\n\n**One of two sibling systems, one per outbound integration.** The other is\n`https://fhir.apps.health/CodeSystem/appointment-ocean-sent`, which carries this same `true` /\n`false` vocabulary under its own address; a third integration would be a third system. They are\nseparate because a writer keeps a single tag per system, replacing rather than adding, so two send\nmarkers sharing one system would erase each other. Read one for the state of one integration only:\nneither implies anything about the other.\n\n**Nexus EMR writes this today at\n`http://services.well.com/fhir/tags/appointment/acdr-arrived` (FHIR-378)**: it is live in stored\n`Appointment.meta.tag` codings and in code, and is under migration to the canonical declared here.\nWrite the canonical; expect both until the migration completes, and match both addresses exactly\nrather than deriving one from the other -- the final segment differs between them, not only the\nhost.",
  "url": "https://fhir.apps.health/CodeSystem/appointment-acdr-arrived",
  "concept": [
    {
      "code": "true",
      "display": "Sent",
      "definition": "The appointment's arrival notification has been sent to Ontario Health's ACDR and was not refused. Read on the sending side so that a second arrival notification is not sent for the same appointment."
    },
    {
      "code": "false",
      "display": "Not sent",
      "definition": "The arrival notification has not been sent. Carries nothing an absent tag does not -- a reader should treat it exactly as an absent tag."
    }
  ],
  "experimental": false,
  "caseSensitive": false,
  "count": 2
}