Skip to content

Attachment Packet Profile

Canonical../StructureDefinition/nexus-attachment-packet
Statusdraft · 1.26.0
BaseList (constraint)
SourceFSH · JSON

An attachment packet: the ordered set of chart items assembled to travel with an outbound artifact -- a letter today, an eReferral next, and forms, emails and chart prints after that.

TypedFhir API / Python

The typed accessor surface List exposes for List — generated from this IG's compiled profile; each typed accessor has a validating raw-FHIR twin (xRaw) where marked. The three ports are parity-enforced.

class List(ClinicalResource)generated source

Accessor Type Access Notes
effective_date FuzzyDate | None read-only The resource's effective date — the first present of this profile's date elements (precedence), normalized to the canonical FuzzyDatetime f…
display str | None read-only The resource's human headline — a coded concept's label, else a title / name, else undefined.
status str | None read/write current (live assembly) | retired (superseded) | entered-in-error
mode str | None read/write working | snapshot | changes
title str | None read/write The packet's name, as shown where it is assembled and reviewed
code Concept | None read/write · raw twin What the purpose of this list is
subject Reference | None read/write · raw twin The patient whose chart these items came from
ordered_by Concept | None read/write · raw twin What order the list has
entry dict[] | None read/write The members, in order
empty_reason Concept | None read/write · raw twin Why list is empty