Generated Narrative: StructureDefinition ext-R2-ImplementationGuide.page Name Flags Card. Type Description & Constraints Extension 1..1 Extension(5.0.0) DSTU2: Page/Section in the Guide #xD; Slices for extension 3..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:source 1..1 Extension DSTU2: Where to find that page #xD; url 1..1 uri "source" #xD; value[x] 1..1 uri Where to find that page #xD; extension:name 1..1 Extension DSTU2: Short name shown for navigational assistance #xD; url 1..1 uri "name" #xD; value[x] 1..1 string Short name shown for navigational assistance #xD; extension:kind 1..1 Extension DSTU2: page | example | list | include | directory | dictionary | toc | resource (new) #xD; url 1..1 uri "kind" #xD; value[x] 1..1 code page | example | list | include | directory | dictionary | toc | resource Binding: R2GuidePageKindForR5 (0.1.0) (required): The kind of an included page. #xD; extension:type 0..* Extension DSTU2: Kind of resource to include in the list (new) #xD; url 1..1 uri "type" #xD; value[x] 0..1 code Kind of resource to include in the list Binding: R2ResourceTypesForR5 (0.1.0) (required): One of the resource types defined as part of FHIR. #xD; extension:package 0..* Extension DSTU2: Name of package to include (new) #xD; url 1..1 uri "package" #xD; value[x] 0..1 string Name of package to include #xD; extension:format 0..1 Extension DSTU2: Format of the page (e.g. html, markdown, etc.) (new) #xD; url 1..1 uri "format" #xD; value[x] 0..1 code Format of the page (e.g. html, markdown, etc.) #xD; extension:page 0..* Extension DSTU2: Nested Pages / Sections (new) #xD; url 1..1 uri "http://hl7.org/fhir/1.0/StructureDefinition/extension-ImplementationGuide.page" #xD; value[x] 0..0 Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/1.0/StructureDefinition/extension-ImplementationGuide.page" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
This extension is part of the cross-version definitions generated to enable use of the element `ImplementationGuide.page` as defined in FHIR DSTU2 in FHIR R5. The source element is defined as: `ImplementationGuide.page` 1..1 `BackboneElement` Across FHIR versions, the element set has been mapped as: * DSTU2: `ImplementationGuide.page` 1..1 `BackboneElement` * STU3: `ImplementationGuide.page` 0..1 `BackboneElement` * R4: `ImplementationGuide.manifest.page` 0..* `BackboneElement` * R4B: `ImplementationGuide.manifest.page` 0..* `BackboneElement` * R5: `ImplementationGuide.manifest.page` 0..* `BackboneElement` Following are the generation technical comments: Element `ImplementationGuide.page` is mapped to FHIR R5 element `ImplementationGuide.manifest.page` as `SourceIsNarrowerThanTarget`. Creating extension because element `ImplementationGuide.page` is a content reference and requires an extesion definition.
Element `ImplementationGuide.page` is mapped to FHIR R5 element `ImplementationGuide.manifest.page` as `SourceIsNarrowerThanTarget`. Pages automatically become sections if they have sub-pages. By convention, the home page is called index.html.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
Must have either extensions or value[x], not both
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
DSTU2: `ImplementationGuide.page.source`
Element `ImplementationGuide.page.source` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.name` as `SourceIsNarrowerThanTarget`. The publishing tool will autogenerate source for list (source = n/a), and inject included implementations for include (source = uri of guide to include).
Element `ImplementationGuide.page.source` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.name` as `SourceIsNarrowerThanTarget`.
Additional content defined by implementations
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 managable, 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.
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.
Source of the definition for the extension code - a logical name or a URL.
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.
The publishing tool will autogenerate source for list (source = n/a), and inject included implementations for include (source = uri of guide to include).
DSTU2: Short name shown for navigational assistance
Element `ImplementationGuide.page.name` is mapped to FHIR R5 element `ImplementationGuide.manifest.page.title` as `Equivalent`.
Short name shown for navigational assistance
A short name used to represent this page in navigational structures such as table of contents, bread crumbs, etc.
DSTU2: page | example | list | include | directory | dictionary | toc | resource (new)
DSTU2: `ImplementationGuide.page.kind` (new:code)
Element `ImplementationGuide.page.kind` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.kind` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
page | example | list | include | directory | dictionary | toc | resource
The kind of page that this is. Some pages are autogenerated (list, example), and other kinds are of interest so that tools can navigate the user to the page of interest.
DSTU2: Kind of resource to include in the list (new)
DSTU2: `ImplementationGuide.page.type` (new:code)
Element `ImplementationGuide.page.type` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.type` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
For constructed pages, what kind of resources to include in the list.
One of the resource types defined as part of FHIR.
DSTU2: `ImplementationGuide.page.package` (new:string)
Element `ImplementationGuide.page.package` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.package` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
For constructed pages, a list of packages to include in the page (or else empty for everything).
DSTU2: Format of the page (e.g. html, markdown, etc.) (new)
DSTU2: `ImplementationGuide.page.format` (new:code)
Element `ImplementationGuide.page.format` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.format` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). This is primarily for the publishing tool, that will convert all pages to html format. HTML pages are pre-processed, see xxxx.
Element `ImplementationGuide.page.format` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.format` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Format of the page (e.g. html, markdown, etc.)
This is primarily for the publishing tool, that will convert all pages to html format. HTML pages are pre-processed, see xxxx.
DSTU2: `ImplementationGuide.page.page` (new:ImplementationGuide.page)
Element `ImplementationGuide.page.page` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.page` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element). The implementation guide breadcrumbs are generated from this structure.
Element `ImplementationGuide.page.page` has a context of ImplementationGuide.manifest.page based on following the parent source element upwards and mapping to `ImplementationGuide`. Element `ImplementationGuide.page.page` has no mapping targets in FHIR R5. Typically, this is because the element has been added (is a new element).
Value of extension - must be one of a constrained set of the data types (see [Extensibility](http://hl7.org/fhir/R5/extensibility.html) for a list).