English Generated Narrative: StructureDefinition profile-mapping Name Flags Card. Type Description & Constraints <a href="StructureDefinition-profile-mapping-definitions.html#Extension" title="Extension definition for Mapping between API and Profile. CapabilityStatement.rest.reosurce.profile has two different profile statements:#xA;#xA;* profile - the overall system profile for a resource#xA;* supportedProfile 0..* - a particular profile that the system supports#xA;#xA;What is missing from this picture is defining which resources conform to#xA;which profile. Sometimes, of course, it's impossible to define this, but#xA;quite often, there's an algorithmic relationship that a server or client#xA;could use to know that resources with a particular set of values will or should#xA;conform to a given profile.#xA;#xA;This extension defines a relationship between a search string and a profile.#xA;Any resource that meets a given search string will be expected to conform to the#xA;particular profile.#xA;#xA;#xA;This extension repeats, and order is important - once a match is found, this profile is the one that applies.">Extension 0..* Extension profile-mapping #xD; Slices for extension Content/Rules for all slices #xD; extension:search 1..1 Extension The search string for this mapping #xD; extension 0..0 Extension #xD; url 1..1 uri "search" #xD; value[x] 0..1 string Value of extension #xD; extension:profile 1..* Extension The profile that must match this search string #xD; extension 0..0 Extension #xD; url 1..1 uri "profile" #xD; value[x] 1..1 canonical(StructureDefinition) Value of extension #xD; extension:documentation 0..1 Extension Documentation about this particular profile-mapping #xD; extension 0..0 Extension #xD; url 1..1 uri "documentation" #xD; value[x] 1..1 markdown Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/tools/StructureDefinition/profile-mapping" #xD; Documentation for this format Spanish Generated Narrative: StructureDefinition profile-mapping Name Flags Card. Type Description & Constraints <a href="StructureDefinition-profile-mapping-definitions.html#Extension" title="Extension definition for Mapping between API and Profile. CapabilityStatement.rest.reosurce.profile has two different profile statements:#xA;#xA;* profile - the overall system profile for a resource#xA;* supportedProfile 0..* - a particular profile that the system supports#xA;#xA;What is missing from this picture is defining which resources conform to#xA;which profile. Sometimes, of course, it's impossible to define this, but#xA;quite often, there's an algorithmic relationship that a server or client#xA;could use to know that resources with a particular set of values will or should#xA;conform to a given profile.#xA;#xA;This extension defines a relationship between a search string and a profile.#xA;Any resource that meets a given search string will be expected to conform to the#xA;particular profile.#xA;#xA;#xA;This extension repeats, and order is important - once a match is found, this profile is the one that applies.">Extension 0..* Extension profile-mapping #xD; Slices for extension Content/Rules for all slices #xD; extension:search 1..1 Extension The search string for this mapping #xD; extension 0..0 Extension #xD; url 1..1 uri "search" #xD; value[x] 0..1 string Value of extension #xD; Slices for extension Content/Rules for all slices #xD; extension:profile 1..* Extension The profile that must match this search string #xD; extension 0..0 Extension #xD; url 1..1 uri "profile" #xD; value[x] 1..1 canonical(StructureDefinition) Value of extension #xD; Slices for extension Content/Rules for all slices #xD; extension:documentation 0..1 Extension Documentation about this particular profile-mapping #xD; extension 0..0 Extension #xD; url 1..1 uri "documentation" #xD; value[x] 1..1 markdown Value of extension #xD; url 1..1 uri "http://hl7.org/fhir/tools/StructureDefinition/profile-mapping" #xD; Documentation for this format
This extension has been replaced by the http://hl7.org/fhir/StructureDefinition/profile-mapping extension in the Extensions Pack
Extension definition for Mapping between ```API``` and ```Profile```. CapabilityStatement.rest.resource.profile has two different profile statements: * profile - the overall system profile for a resource * supportedProfile 0..* - a particular profile that the system supports What is missing from this picture is defining which resources conform to which profile. Sometimes, of course, it's impossible to define this, but quite often, there's an algorithmic relationship that a server or client could use to know that resources with a particular set of values will or should conform to a given profile. This extension defines a relationship between a search string and a profile. Any resource that meets a given search string will be expected to conform to the particular profile. If more than one profile is nominated for a search string, resources SHALL conform to all the listed profiles. The last extension can be without a search matches and remaining resources This extension repeats, and order is important - once a match is found, this profile is the one that applies. Todo: If this extension is useful, it will be moved to the core extensions pack
Extension definition for Mapping between API and Profile. CapabilityStatement.rest.reosurce.profile has two different profile statements: * profile - the overall system profile for a resource * supportedProfile 0..* - a particular profile that the system supports What is missing from this picture is defining which resources conform to which profile. Sometimes, of course, it's impossible to define this, but quite often, there's an algorithmic relationship that a server or client could use to know that resources with a particular set of values will or should conform to a given profile. This extension defines a relationship between a search string and a profile. Any resource that meets a given search string will be expected to conform to the particular profile. This extension repeats, and order is important - once a match is found, this profile is the one that applies.
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.
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 profile that must match this search string
Documentation about this particular profile-mapping