Generated Narrative: StructureDefinition SushiConfigLogicalModel Name Flags Card. Type Description & Constraints SushiConfigLogicalModel 0..* Base SUSHI Configuration Logical Model #xD; id 1..1 string IG Identifier #xD; canonical 1..1 url Canonical URL #xD; name 1..1 string IG Name #xD; title 1..1 string IG Title #xD; description 1..1 string IG Description #xD; version 1..1 string IG Version #xD; status 1..1 code IG Status Binding: PublicationStatus (required) #xD; license 1..1 code License Binding: SPDXLicense (required) #xD; copyrightYear 0..1 string Copyright Year #xD; experimental 0..1 boolean Experimental #xD; releaseLabel 0..1 string Release Label #xD; publisher 1..1 BackboneElement Publisher #xD; name 1..1 string Publisher Name #xD; url 0..1 url Publisher URL #xD; email 0..1 string Publisher Email #xD; fhirVersion 1..1 code FHIR Version Binding: FHIRVersion (required) #xD; dependencies 0..* BackboneElement Dependencies #xD; @id 1..1 string Dependency Package ID #xD; version 1..1 string Dependency Version #xD; reason 0..1 string Dependency Reason #xD; pages 0..* BackboneElement Pages #xD; filename 1..1 string Page Filename #xD; title 1..1 string Page Title #xD; menu 0..* BackboneElement Menu Structure #xD; title 1..1 string Menu Title #xD; url 1..1 string Menu URL #xD; subItems 0..* BackboneElement Sub Menu Items #xD; title 1..1 string Sub-item Title #xD; url 1..1 string Sub-item URL #xD; resources 0..* BackboneElement Resource Definitions #xD; reference 1..1 string Resource Reference #xD; name 0..1 string Resource Name #xD; description 0..1 string Resource Description #xD; exampleBoolean 0..1 boolean Is Example #xD; exampleCanonical 0..1 canonical() Example Canonical #xD; groupingId 0..1 string Grouping ID #xD; groups 0..* BackboneElement Resource Groups #xD; @id 1..1 string Group ID #xD; name 1..1 string Group Name #xD; description 1..1 string Group Description #xD; resources 0..* string Group Resources #xD; global 0..* BackboneElement Global Profiles #xD; type 1..1 string Resource Type #xD; profile 1..1 canonical() Profile URL #xD; meta 0..1 BackboneElement IG Metadata #xD; profile 0..* canonical() Meta Profiles #xD; contact 0..* ContactDetail Contact Information #xD; useContext 0..* UsageContext Use Context #xD; jurisdiction 0..* CodeableConcept Jurisdiction #xD; FSHOnly 0..1 boolean FSH Only #xD; applyExtensionMetadataToRoot 0..1 boolean Apply Extension Metadata #xD; instanceOptions 0..1 BackboneElement Instance Options #xD; setMetaProfile 0..1 code Set Meta Profile #xD; setId 0..1 code Set ID #xD; Documentation for this format
Logical model defining the structure of sushi-config.yaml files used for FHIR Implementation Guide configuration. This model captures the essential metadata and configuration parameters needed for IG publishing.
Unique identifier for the IG, should match DAK id (e.g., smart.who.int.trust)
Canonical URL for the IG, should match DAK publicationUrl (e.g., http://smart.who.int/trust)
Short name for the IG, should derive from DAK name (e.g., Trust)
Full title of the IG, should match DAK title (e.g., WHO SMART Trust)
Description of the IG, should match DAK description
Version of the IG, should match DAK version
License under which the IG is published, should match DAK license
Year or year range for copyright, should match DAK
Whether this IG is experimental, should match DAK
Label for this release (e.g., ci-build, draft, ballot)
Organization responsible for publishing the IG
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
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
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 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.
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.
Must have either extensions or value[x], not both
exists(f:extension)!=exists(f:*[starts-with(local-name(.), "value")])
Extensions that cannot be ignored even if unrecognized
May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R4/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Name of the publishing organization, should match DAK publisher name
URL of the publishing organization, should match DAK publisher URL
Other IGs or packages this IG depends on
Explicit resource definitions for the IG
Reference to the resource (used as YAML key)
Canonical URL this resource is an example of
ID of the group this resource belongs to
Logical groupings of resources in the IG
Context where this IG is intended to be used
Whether to export only FSH resources without IG content
Whether to apply extension metadata to root elements