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.

Elements / Differential

What this profile constrains beyond List. Anything not listed is unchanged from the base; muted type/cardinality values are the base's, shown for context.

Element Flags Card. Type Description & Constraints
List Nexus EMR Attachment Packet
Invariants: nexus-note-extension-not-where-native, nexus-packet-has-identity, nexus-packet-members-distinct, nexus-packet-excluded-pages-are-positive
extension 0..* Extension i
Slicing: value:url (open)
extension:coverPage S 0..1 Extension(Packet Cover Page Extension) Does the render lead with a generated cover page? (absent = not stated, NOT false) i
identifier S 1..* Identifier Stable identity of this packet, and the marker that this List is one
status S 1..1 code current (live assembly) | retired (superseded) | entered-in-error i
mode 1..1 code i
Fixed: working
title S 1..1 string The packet's name, as shown where it is assembled and reviewed
subject S 1..1 Reference(Patient Profile) The patient whose chart these items came from i
entry S 1..* BackboneElement The members, in order i
extension 0..* Extension i
Slicing: value:url (open)
extension:excludedPage 0..* Extension(Packet Entry Excluded Page Extension) A page of this member excluded from the render (1-based; repeats) i
item S 1..1 Reference(Resource) The chart item -- a document, note, result or form; SHALL be about this packet's subject i