Skip to content

Packet Entry Excluded Page Extension

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

A page of this packet member that the assembler excluded from the outbound render. Repeats: one occurrence per excluded page, 1-based, counting pages of the member's rendered form as produced at assembly time. Page numbering is meaningful only relative to that render -- a different renderer may paginate the same member differently -- so these values record what the assembler chose rather than a durable re-rendering instruction. What the recipient actually received is the rendered document stored on send.

Elements / Details

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

Extension

Short A page of this member excluded from the outbound render (1-based; repeats)
Definition A page of this packet member that the assembler excluded from the outbound render. Repeats: one occurrence per excluded page, 1-based, counting pages of the member's rendered form as produced at assembly time. Page numbering is meaningful only relative to that render -- a different renderer may paginate the same member differently -- so these values record what the assembler chose rather than a durable re-rendering instruction. What the recipient actually received is the rendered document stored on send.
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-attachment-packet-excluded-page

Extension.value[x]

Short 1-based page number, in the member's rendered form at assembly time
Definition Value of extension - must be one of a constrained set of the data types (see Extensibility for a list).
Cardinality 1..1
Type integer
Must Support yes
Invariants ele-1