Skip to content

Packet Cover Page Extension

Canonical../StructureDefinition/nexus-packet-cover-page
Statusdraft · 1.26.0
BaseExtension (constraint)
ContextList (element)
SourceFSH · JSON

Whether this attachment packet leads with a generated cover page in the outbound render.

Elements / Details

Every element this profile touches, with its full definition. Element names in the tables link here.

Extension

Short Does this packet lead with a generated cover page? (absent = not stated, NOT false)
Definition Whether this attachment packet leads with a generated cover page in the outbound render. Absent does not mean false. The value a packet starts with is decided per send channel, so an absent extension records no choice at all -- neither that a cover page was wanted nor that it was declined. Writers SHOULD state it explicitly in both directions; readers SHOULD treat absence as "not stated" and fall back to their own channel default rather than to false. The cover page is not a packet member. It is generated at render time from what the packet already carries and never appears in List.entry, so a consumer counting members counts chart items only. Meaningful on an attachment packet (nexus-attachment-packet), and constrained to one: the extension's contextInvariant requires the List it rides to carry an identifier under the attachment-packet naming system, so it cannot legally be stamped on a template List or on any other kind. It asserts nothing about any other kind of List because it cannot appear on one.
Cardinality 0..*
Invariants ele-1, ext-1

Extension.id

Short Unique id for inter-element referencing
Definition Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Cardinality 0..1
Type http://hl7.org/fhirpath/System.String

Extension.extension

Short Additional content defined by implementations
Definition May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.
Comments There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Cardinality 0..0
Type Extension
Invariants ele-1, ext-1
Also called extensions, user content

Extension.url

Short identifies the meaning of the extension
Definition Source of the definition for the extension code - a logical name or a URL.
Comments The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension.
Cardinality 1..1
Type http://hl7.org/fhirpath/System.String
Fixed value ../StructureDefinition/nexus-packet-cover-page

Extension.value[x]

Short true: the render leads with a generated cover page; false: it does not
Definition Whether the outbound render of this packet begins with a generated cover page. Present-and-false is a recorded decision not to lead with one, and is distinct from the extension being absent, which records no decision.
Cardinality 1..1
Type boolean
Must Support yes
Invariants ele-1