Generated Narrative: StructureDefinition implementationguide-sourceFile Name Flags Card. Type Description & Constraints Extension 0..* Extension Additional files used in publication #xD; Slices for extension Content/Rules for all slices #xD; extension:file 1..1 Extension Location on server #xD; extension 0..0 Extension #xD; url 1..1 uri "file" #xD; value[x] 1..1 Reference() Value of extension #xD; extension:location 1..1 Extension Path for publisher #xD; extension 0..0 Extension #xD; url 1..1 uri "location" #xD; value[x] 1..1 string Value of extension #xD; extension:keepAsResource 0..1 Extension Use attachment or resource? #xD; extension 0..0 Extension #xD; url 1..1 uri "keepAsResource" #xD; value[x] 1..1 boolean Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/StructureDefinition/implementationguide-sourceFile" #xD; value[x] 0..0 Value of extension #xD; Documentation for this format
Identifies files used as part of the the publication process other than resources referenced in definition.resource.
When 'exporting' the referenced file for use in publication, if storing the content as a resource, the exported syntax (XML, JSON, or RDF) should be driven by the file extension of the specified location.
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
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.
The location of the file on a server used by the IG publication process
This will often be a DocumentReference or Media resource (depending on FHIR version) containing the relevant content.
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.
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).
The relative path (with respect to the IG base folder) and name of the file as it should be positioned prior to processing by the IG publisher
The default behavior if the Reference is to a Media or DocumentReference is for the 'attachment' to be what is persisted in the 'location'. If this flag is set to true, then the referenced resource will be persisted 'as is' - I.e. a Media or DocumentReference.