{"resourceType":"StructureDefinition","id":"CapabilityStatement.rest.resource.supportedProfile","meta":{"lastUpdated":"2021-01-17T07:06:13.533+11:00"},"url":"http://hl7.org/fhir/StructureDefinition/CapabilityStatement.rest.resource.supportedProfile","version":"4.0.1","name":"CapabilityStatement.rest.resource.supportedProfile","title":"CapabilityStatement.rest.resource.supportedProfile","status":"draft","experimental":true,"date":"2021-01-17T07:06:13+11:00","publisher":"HL7 FHIR Standard","contact":[{"telecom":[{"system":"url","value":"http://hl7.org/fhir"}]}],"description":"Data Element for CapabilityStatement.rest.resource.supportedProfile","purpose":"Data Elements are defined for each element to assist in questionnaire construction etc","fhirVersion":"4.0.1","mapping":[{"identity":"rim","uri":"http://hl7.org/v3","name":"RIM Mapping"},{"identity":"w5","uri":"http://hl7.org/fhir/fivews","name":"FiveWs Pattern Mapping"},{"identity":"workflow","uri":"http://hl7.org/fhir/workflow","name":"Workflow Pattern"},{"identity":"objimpl","uri":"http://hl7.org/fhir/object-implementation","name":"Object Implementation Information"}],"kind":"logical","abstract":false,"type":"CapabilityStatement.rest.resource.supportedProfile","baseDefinition":"http://hl7.org/fhir/StructureDefinition/Element","derivation":"specialization","snapshot":{"element":[{"id":"CapabilityStatement.rest.resource.supportedProfile","extension":[{"url":"http://hl7.org/fhir/StructureDefinition/structuredefinition-standards-status","valueCode":"trial-use"}],"path":"CapabilityStatement.rest.resource.supportedProfile","short":"Profiles for use cases supported","definition":"A list of profiles that represent different use cases supported by the system. For a server, \"supported by the system\" means the system hosts/produces a set of resources that are conformant to a particular profile, and allows clients that use its services to search using this profile and to find appropriate data. For a client, it means the system will search by this profile and process data according to the guidance implicit in the profile. See further discussion in [Using Profiles](profiling.html#profile-uses).","comment":"Supported profiles are different than the profile that applies to a particular resource in .rest.resource.profile. The resource profile is a general statement of what features of the resource are supported overall by the system - the sum total of the facilities it supports. A supported profile is a deeper statement about the functionality of the data and services provided by the server (or used by the client). A typical case is a laboratory system that produces a set of different reports - this is the list of types of data that it publishes. A key aspect of declaring profiles here is the question of how the client converts knowledge that the server publishes this data into working with the data; the client can inspect individual resources to determine whether they conform to a particular profile, but how does it find the ones that do? It does so by searching using the _profile parameter, so any resources listed here must be valid values for the _profile resource (using the identifier in the target profile).","min":0,"max":"*","base":{"path":"CapabilityStatement.rest.resource.supportedProfile","min":0,"max":"*"},"type":[{"code":"canonical","targetProfile":["http://hl7.org/fhir/StructureDefinition/StructureDefinition"]}],"isModifier":false,"isSummary":true}]}}