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 / Snapshot

The full effective definition: base List with this profile's constraints applied.

Element Flags Card. Type Description & Constraints
List 0..* Nexus EMR Attachment Packet
Invariants: dom-2, dom-3, dom-4, dom-5, dom-6, lst-1, lst-2, lst-3, nexus-note-extension-not-where-native, nexus-packet-has-identity, nexus-packet-members-distinct, nexus-packet-excluded-pages-are-positive
id 0..1 http://hl7.org/fhirpath/System.String Logical id of this artifact i
meta 0..1 Meta Metadata about the resource
Invariants: ele-1
implicitRules ?! 0..1 uri A set of rules under which this content was created i
Invariants: ele-1
language 0..1 code Language of the resource content i
Binding: languages (preferred)
Invariants: ele-1
text 0..1 Narrative Text summary of the resource, for human interpretation i
Invariants: ele-1
contained 0..* Resource Contained, inline Resources i
extension 0..* Extension Additional content defined by implementations i
Slicing: value:url (open)
Invariants: ele-1, ext-1
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
Invariants: ele-1, ext-1
modifierExtension ?! 0..* Extension Extensions that cannot be ignored i
Invariants: ele-1, ext-1
identifier S 1..* Identifier Stable identity of this packet, and the marker that this List is one
Invariants: ele-1
status S ?! 1..1 code current (live assembly) | retired (superseded) | entered-in-error i
Binding: list-status (required)
Invariants: ele-1
mode ?! 1..1 code working | snapshot | changes i
Fixed: working
Binding: list-mode (required)
Invariants: ele-1
title S 1..1 string The packet's name, as shown where it is assembled and reviewed
Invariants: ele-1
code 0..1 CodeableConcept What the purpose of this list is i
Binding: list-example-codes (example)
Invariants: ele-1
subject S 1..1 Reference(Patient Profile) The patient whose chart these items came from i
Invariants: ele-1
encounter 0..1 Reference(Encounter) Context in which list created
Invariants: ele-1
date 0..1 dateTime When the list was prepared i
Invariants: ele-1
source 0..1 Reference(Practitioner | PractitionerRole | Patient | Device) Who and/or what defined the list contents (aka Author) i
Invariants: ele-1
orderedBy 0..1 CodeableConcept What order the list has i
Binding: list-order (preferred)
Invariants: ele-1
note 0..* Annotation Comments about the list
Invariants: ele-1
entry S 1..* BackboneElement The members, in order i
Invariants: ele-1
id 0..1 http://hl7.org/fhirpath/System.String Unique id for inter-element referencing
extension 0..* Extension Additional content defined by implementations i
Slicing: value:url (open)
Invariants: ele-1, ext-1
extension:excludedPage 0..* Extension(Packet Entry Excluded Page Extension) A page of this member excluded from the render (1-based; repeats) i
Invariants: ele-1, ext-1
modifierExtension ?! 0..* Extension Extensions that cannot be ignored even if unrecognized i
Invariants: ele-1, ext-1
flag 0..1 CodeableConcept Status/Workflow information about this item i
Binding: list-item-flag (example)
Invariants: ele-1
deleted ?! 0..1 boolean If this item is actually marked as deleted i
Invariants: ele-1
date 0..1 dateTime When item added to list
Invariants: ele-1
item S 1..1 Reference(Resource) The chart item -- a document, note, result or form; SHALL be about this packet's subject i
Invariants: ele-1
emptyReason 0..1 CodeableConcept Why list is empty i
Binding: list-empty-reason (preferred)
Invariants: ele-1