Send Channel CodeSystem Code system

Canonical	../CodeSystem/nexus-send-channel
Status	draft · 1.26.0
Content	complete
Source	FSH · JSON

The way out of the EMR an outbound artifact was prepared for. Carried as a tag on meta.tag, where this is the tag's system; attachment packets (nexus-attachment-packet) are the population that carries it today, stamped when the packet is assembled.

A tag, not an extension. The address identifies the system of a Coding in meta.tag, which is why it is declared as a code system. It is carried there rather than on an element of its own so that "every packet prepared for this channel" stays a _tag search, which every R4 server supports without a custom search parameter being registered first.

It records an assembly choice, not a transmission. The channel explains why a packet is shaped the way it is -- its page and size limits, and whether the render leads with a cover page (nexus-packet-cover-page) -- and asserts nothing about anything having been sent. It does not say the artifact went out, when, to whom, or whether it succeeded, and a packet re-sent by another route still carries the channel it was assembled under. What went out is the rendered document stored on send, which this specification does not model yet. Do not read a transmission out of this tag.

Absent means the producer did not record a channel, not that there is no channel. Read absence as unknown.

Seven codes; two have a writer today. referral and letter are written now. The other five are declared because the catalogue is a closed set whose members are wire-stable keys -- a reader has to handle each the day the feature behind it ships, and renaming one after the fact is a data migration rather than a rename.

Not sliced on any profile. meta.tag is open on every resource and this marker belongs to one producer rather than to the shape every conforming instance has, so nexus-attachment-packet names this vocabulary and constrains nothing.

MIGRATION. Nexus EMR writes this tag today at ../tags/attachment-packet/send-channel. That address is on this guide's own base but not at a published artifact path -- artifacts here are published at /[artifact-type]/[artifact-id], and tags is not an artifact type -- so it is a pre-migration address like any other, and is live in stored meta.tag codings and in client code. Write the canonical declared here; expect both until the migration completes, and match both addresses exactly rather than deriving one from the other.

Code	Display	Definition
referral	Outbound referral	The packet travels with a referral going to another provider or service. Written today.
letter	Clinical or consult letter	The packet travels with an authored letter. Written today, and the case the enclosures section of a letter Composition points at.
fax	Outbound fax	The packet is rendered to be faxed. Declared; no writer yet.
print	Print packet	The packet is rendered for printing, to be handed over or mailed on paper. Declared; no writer yet.
secure-message	Secure message to a provider	The packet travels with a secure message to another provider. Declared; no writer yet.
patient-share	Share to the patient portal	The packet is shared to the patient through a portal rather than sent to a provider. Declared; no writer yet.
form-submission	Form submission	The packet travels with a form submitted to a third party, such as a workers-compensation board. Declared; no writer yet.