2nd DSTU Draft For Comment

This page is part of the FHIR Specification (v0.4.0: DSTU 2 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions . Page versions: R3 R2

6.17 Resource Profile - Content

This resource maintained by the FHIR Management Group Work Group

A Resource Profile - a statement of use of one or more FHIR Resources. It may include constraints on Resources and Data Types, Terminology Binding Statements and Extension Definitions.

6.17.1 Scope and Usage

The Profile resource describes a set of rules about how a resource is used to meet a general use case, so that the rules can be shared and published through repositories of profile definitions, compared with each other, and used as the basis for code, report and UI generation.

Profile resources have a metadata section that describes the profile, and supports registry searching and they define and describe how a Resource or Data Type is used.

Note that as part of the specification itself, a full set of profiles for all resources and data types is published. A FHIR RESTful server serving the profile resource is also a profile repository. HL7 hosts one for public registration of FHIR profiles at (yet to be done).

6.17.2 Boundaries and Relationships

  • Profiles are used by Conformance instances for specifying how resources are used
  • Profiles use Value Sets to specify the content of coded elements
  • Profiles can use Extension Definitions when specifying how a resource is used

6.17.3 Background and Context

Implementers should be familiar with with the background and concepts described in Profiling FHIR before working with this resource.

6.17.3.1 Metadata

The profile resource has a set of metadata that is mostly shared with the Value Set, Conformance and other infrastructure resources. The metadata describes the profile, and helps find the profile when registered in profile repositories.

urlThe identifier that is used to identify this profile when it is referenced in a specification, model, design or an instance. This URL is where the profile can be accessed
identifierOther identifiers that are used to identify this profile
version

The identifier that is used to identify this version of the profile when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the profile author manually and the value should be a timestamp.

Note that there may be multiple resource versions of the profile that have this same identifier. The resource will have updates that create new versions for technical reasons, whereas the stated version number needs to be under the author's control

nameA free text natural language name identifying the Profile
publisherDetails of the individual or organization who accepts responsibility for publishing the profile. This helps establish the "authority/credibility" of the profile.
telecomContact details to assist a user in finding and communicating with the publisher
descriptionA free text natural language description of the profile and its use
requirementsThe Scope and Usage that this profile was created to meet
codeA set of terms from external terminologies that may be used to assist with indexing and searching of profiles
statusThe status of the profile allows filtering of profiles that are appropriate for use vs. not. See the Status Codes
experimentalThis profile was authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage
dateThe date that this version of the profile was published
fhirVersionThe version of the FHIR specification on which this profile is based. It is not necessary to specify the version, as most profiles are valid across multiple versions, and the validity of a profile against a particular version of FHIR can easily be checked by tooling.

Notes:

  • The name of the profile is not required to be globally unique, but the name should have some scoping information (i.e. Acme Inc. (USA), Allergy List)
  • Multiple codes may be assigned to the profile. These may either describe the profile, the focus of the profile or both. They are solely to help find the profile by searching for structured concepts
  • The 3 status codes (draft, active, and retired) are the codes that are relevant to profile consumers. Authors may wish to use the authoring-status extension to track the life cycle of a profile as it is prepared

This resource is referenced by ConceptMap, Conformance and OperationDefinition

6.17.4 Resource Content

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Profile IDomainResourceResource Profile
Parameter names must be unique within structure
... url 1..1uriLiteral URL used to reference this profile
... identifier Σ0..1IdentifierAdditional identifier for the profile
... version Σ0..1stringLogical id for this version of the profile
... name Σ1..1stringInformal name for this profile
... publisher Σ0..1stringName of the publisher (Organization or individual)
... contact Σ0..*ElementContact details of the publisher
.... name Σ0..1stringName of a individual to contact
.... telecom Σ0..*ContactPointContact details for individual or publisher
... description Σ0..1stringNatural language description of the profile
... code Σ0..*CodingAssist with indexing and finding
... status M Σ1..1codedraft | active | retired
ResourceProfileStatus (Required)
... experimental Σ0..1booleanIf for testing purposes, not real usage
... date Σ0..1dateTimeDate for this version of the profile
... requirements 0..1stringScope and Usage this profile is for
... fhirVersion Σ0..1idFHIR Version this profile targets
... mapping I0..*ElementExternal specification that the content is mapped to
Must have at a name or a uri (or both)
.... identity 1..1idInternal id when this mapping is used
.... uri I0..1uriIdentifies what this mapping refers to
.... name I0..1stringNames what this mapping refers to
.... comments 0..1stringVersions, Issues, Scope limitations etc
... type 1..1codeThe Resource or Data Type being described
FHIRDefinedType (Required)
... base 0..1uriStructure that this set of constraints applies to
... snapshot I0..1ElementSnapshot view of the structure
Element paths must be unique - or not (LM)
If a structure is a snapshot, then each element definition must have a formal definition, and cardinalities
.... element 0..*ElementDefinitionDefinition of elements in the resource (if no profile)
... differential 0..1see snapshotDifferential view of the structure

UML Diagram

Profile (DomainResource)The URL at which this profile is (or will be) published, and which is used to reference this profile in extension urls and tag values in operational FHIR systemsurl : uri 1..1A formal identifier that is used to identify this profile when it is represented in other formats, or referenced in a specification, model, design or an instance (should be globally unique uri)identifier : Identifier 0..1The identifier that is used to identify this version of the profile when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the profile author manuallyversion : string 0..1A free text natural language name identifying the Profilename : string 1..1The name of the individual or organization that published the profilepublisher : string 0..1A free text natural language description of the profile and its usedescription : string 0..1A set of terms from external terminologies that may be used to assist with indexing and searching of templatescode : Coding 0..*The status of the profile (this element modifies the meaning of other elements)status : code 1..1 « The lifecycle status of a Resource ProfileResourceProfileStatus »This profile was authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usageexperimental : boolean 0..1The date that this version of the profile was publisheddate : dateTime 0..1The Scope and Usage that this profile was created to meetrequirements : string 0..1The version of the FHIR specification on which this profile is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 0.4.0 for this versionfhirVersion : id 0..1The Resource or Data type being describedtype : code 1..1 « Either a resource or a data typeFHIRDefinedType »The structure that is the base on which this set of constraints is derived frombase : uri 0..1ContactThe name of an individual to contact regarding the profilename : string 0..1Contact details for individual (if a name was provided) or the publishertelecom : ContactPoint 0..*MappingAn Internal id that is used to identify this mapping set when specific mappings are madeidentity : id 1..1A URI that identifies the specification that this mapping is expressed touri : uri 0..1A name for the specification that is being mapped toname : string 0..1Comments about this mapping, including version notes, issues, scope limitations, and other important notes for usagecomments : string 0..1ConstraintCaptures constraints on each element within the resourceelement : ElementDefinition 0..*Contacts to assist a user in finding and communicating with the publishercontact0..*An external specification that the content is mapped tomapping0..*A snapshot view is expressed in a stand alone form that can be used and interpreted without considering the base profilesnapshot0..1A differential view is expressed relative to the base profile - a statement of differences that it appliesdifferential0..1

XML Template

<Profile xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <url value="[uri]"/><!-- 1..1 Literal URL used to reference this profile -->
 <identifier><!-- 0..1 Identifier Additional identifier for the profile --></identifier>
 <version value="[string]"/><!-- 0..1 Logical id for this version of the profile -->
 <name value="[string]"/><!-- 1..1 Informal name for this profile -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (Organization or individual) -->
 <contact>  <!-- 0..* Contact details of the publisher -->
  <name value="[string]"/><!-- 0..1 Name of a individual to contact -->
  <telecom><!-- 0..* ContactPoint Contact details for individual or publisher --></telecom>
 </contact>
 <description value="[string]"/><!-- 0..1 Natural language description of the profile -->
 <code><!-- 0..* Coding Assist with indexing and finding --></code>
 <status value="[code]"/><!-- 1..1 draft | active | retired -->
 <experimental value="[boolean]"/><!-- 0..1 If for testing purposes, not real usage -->
 <date value="[dateTime]"/><!-- 0..1 Date for this version of the profile -->
 <requirements value="[string]"/><!-- 0..1 Scope and Usage this profile is for -->
 <fhirVersion value="[id]"/><!-- 0..1 FHIR Version this profile targets -->
 <mapping>  <!-- 0..* External specification that the content is mapped to -->
  <identity value="[id]"/><!-- 1..1 Internal id when this mapping is used -->
  <uri value="[uri]"/><!-- ?? 0..1 Identifies what this mapping refers to -->
  <name value="[string]"/><!-- ?? 0..1 Names what this mapping refers to -->
  <comments value="[string]"/><!-- 0..1 Versions, Issues, Scope limitations etc -->
 </mapping>
 <type value="[code]"/><!-- 1..1 The Resource or Data Type being described -->
 <base value="[uri]"/><!-- 0..1 Structure that this set of constraints applies to -->
 <snapshot>  <!-- 0..1 Snapshot view of the structure -->
  <element><!-- 0..* ElementDefinition 
      Definition of elements in the resource (if no profile) --></element>
 </snapshot>
 <differential><!-- 0..1 Content as for Profile.snapshot Differential view of the structure --></differential>
</Profile>

JSON Template

{doco
  "resourceType" : "Profile",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "url" : "<uri>", // R! Literal URL used to reference this profile
  "identifier" : { Identifier }, // Additional identifier for the profile
  "version" : "<string>", // Logical id for this version of the profile
  "name" : "<string>", // R! Informal name for this profile
  "publisher" : "<string>", // Name of the publisher (Organization or individual)
  "contact" : [{ // Contact details of the publisher
    "name" : "<string>", // Name of a individual to contact
    "telecom" : [{ ContactPoint }] // Contact details for individual or publisher
  }],
  "description" : "<string>", // Natural language description of the profile
  "code" : [{ Coding }], // Assist with indexing and finding
  "status" : "<code>", // R! draft | active | retired
  "experimental" : <boolean>, // If for testing purposes, not real usage
  "date" : "<dateTime>", // Date for this version of the profile
  "requirements" : "<string>", // Scope and Usage this profile is for
  "fhirVersion" : "<id>", // FHIR Version this profile targets
  "mapping" : [{ // External specification that the content is mapped to
    "identity" : "<id>", // R! Internal id when this mapping is used
    "uri" : "<uri>", // C? Identifies what this mapping refers to
    "name" : "<string>", // C? Names what this mapping refers to
    "comments" : "<string>" // Versions, Issues, Scope limitations etc
  }],
  "type" : "<code>", // R! The Resource or Data Type being described
  "base" : "<uri>", // Structure that this set of constraints applies to
  "snapshot" : { // Snapshot view of the structure
    "element" : [{ ElementDefinition }] // 
      Definition of elements in the resource (if no profile)
  },
  "differential" : { Content as for Profile.snapshot } // Differential view of the structure
}

Structure

NameFlagsCard.TypeDescription & Constraintsdoco
.. Profile IDomainResourceResource Profile
Parameter names must be unique within structure
... url 1..1uriLiteral URL used to reference this profile
... identifier Σ0..1IdentifierAdditional identifier for the profile
... version Σ0..1stringLogical id for this version of the profile
... name Σ1..1stringInformal name for this profile
... publisher Σ0..1stringName of the publisher (Organization or individual)
... contact Σ0..*ElementContact details of the publisher
.... name Σ0..1stringName of a individual to contact
.... telecom Σ0..*ContactPointContact details for individual or publisher
... description Σ0..1stringNatural language description of the profile
... code Σ0..*CodingAssist with indexing and finding
... status M Σ1..1codedraft | active | retired
ResourceProfileStatus (Required)
... experimental Σ0..1booleanIf for testing purposes, not real usage
... date Σ0..1dateTimeDate for this version of the profile
... requirements 0..1stringScope and Usage this profile is for
... fhirVersion Σ0..1idFHIR Version this profile targets
... mapping I0..*ElementExternal specification that the content is mapped to
Must have at a name or a uri (or both)
.... identity 1..1idInternal id when this mapping is used
.... uri I0..1uriIdentifies what this mapping refers to
.... name I0..1stringNames what this mapping refers to
.... comments 0..1stringVersions, Issues, Scope limitations etc
... type 1..1codeThe Resource or Data Type being described
FHIRDefinedType (Required)
... base 0..1uriStructure that this set of constraints applies to
... snapshot I0..1ElementSnapshot view of the structure
Element paths must be unique - or not (LM)
If a structure is a snapshot, then each element definition must have a formal definition, and cardinalities
.... element 0..*ElementDefinitionDefinition of elements in the resource (if no profile)
... differential 0..1see snapshotDifferential view of the structure

UML Diagram

Profile (DomainResource)The URL at which this profile is (or will be) published, and which is used to reference this profile in extension urls and tag values in operational FHIR systemsurl : uri 1..1A formal identifier that is used to identify this profile when it is represented in other formats, or referenced in a specification, model, design or an instance (should be globally unique uri)identifier : Identifier 0..1The identifier that is used to identify this version of the profile when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the profile author manuallyversion : string 0..1A free text natural language name identifying the Profilename : string 1..1The name of the individual or organization that published the profilepublisher : string 0..1A free text natural language description of the profile and its usedescription : string 0..1A set of terms from external terminologies that may be used to assist with indexing and searching of templatescode : Coding 0..*The status of the profile (this element modifies the meaning of other elements)status : code 1..1 « The lifecycle status of a Resource ProfileResourceProfileStatus »This profile was authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usageexperimental : boolean 0..1The date that this version of the profile was publisheddate : dateTime 0..1The Scope and Usage that this profile was created to meetrequirements : string 0..1The version of the FHIR specification on which this profile is based - this is the formal version of the specification, without the revision number, e.g. [publication].[major].[minor], which is 0.4.0 for this versionfhirVersion : id 0..1The Resource or Data type being describedtype : code 1..1 « Either a resource or a data typeFHIRDefinedType »The structure that is the base on which this set of constraints is derived frombase : uri 0..1ContactThe name of an individual to contact regarding the profilename : string 0..1Contact details for individual (if a name was provided) or the publishertelecom : ContactPoint 0..*MappingAn Internal id that is used to identify this mapping set when specific mappings are madeidentity : id 1..1A URI that identifies the specification that this mapping is expressed touri : uri 0..1A name for the specification that is being mapped toname : string 0..1Comments about this mapping, including version notes, issues, scope limitations, and other important notes for usagecomments : string 0..1ConstraintCaptures constraints on each element within the resourceelement : ElementDefinition 0..*Contacts to assist a user in finding and communicating with the publishercontact0..*An external specification that the content is mapped tomapping0..*A snapshot view is expressed in a stand alone form that can be used and interpreted without considering the base profilesnapshot0..1A differential view is expressed relative to the base profile - a statement of differences that it appliesdifferential0..1

XML Template

<Profile xmlns="http://hl7.org/fhir"> doco
 <!-- from Resource: id, meta, implicitRules, and language -->
 <!-- from DomainResource: text, contained, extension, and modifierExtension -->
 <url value="[uri]"/><!-- 1..1 Literal URL used to reference this profile -->
 <identifier><!-- 0..1 Identifier Additional identifier for the profile --></identifier>
 <version value="[string]"/><!-- 0..1 Logical id for this version of the profile -->
 <name value="[string]"/><!-- 1..1 Informal name for this profile -->
 <publisher value="[string]"/><!-- 0..1 Name of the publisher (Organization or individual) -->
 <contact>  <!-- 0..* Contact details of the publisher -->
  <name value="[string]"/><!-- 0..1 Name of a individual to contact -->
  <telecom><!-- 0..* ContactPoint Contact details for individual or publisher --></telecom>
 </contact>
 <description value="[string]"/><!-- 0..1 Natural language description of the profile -->
 <code><!-- 0..* Coding Assist with indexing and finding --></code>
 <status value="[code]"/><!-- 1..1 draft | active | retired -->
 <experimental value="[boolean]"/><!-- 0..1 If for testing purposes, not real usage -->
 <date value="[dateTime]"/><!-- 0..1 Date for this version of the profile -->
 <requirements value="[string]"/><!-- 0..1 Scope and Usage this profile is for -->
 <fhirVersion value="[id]"/><!-- 0..1 FHIR Version this profile targets -->
 <mapping>  <!-- 0..* External specification that the content is mapped to -->
  <identity value="[id]"/><!-- 1..1 Internal id when this mapping is used -->
  <uri value="[uri]"/><!-- ?? 0..1 Identifies what this mapping refers to -->
  <name value="[string]"/><!-- ?? 0..1 Names what this mapping refers to -->
  <comments value="[string]"/><!-- 0..1 Versions, Issues, Scope limitations etc -->
 </mapping>
 <type value="[code]"/><!-- 1..1 The Resource or Data Type being described -->
 <base value="[uri]"/><!-- 0..1 Structure that this set of constraints applies to -->
 <snapshot>  <!-- 0..1 Snapshot view of the structure -->
  <element><!-- 0..* ElementDefinition 
      Definition of elements in the resource (if no profile) --></element>
 </snapshot>
 <differential><!-- 0..1 Content as for Profile.snapshot Differential view of the structure --></differential>
</Profile>

JSON Template

{doco
  "resourceType" : "Profile",
  // from Resource: id, meta, implicitRules, and language
  // from DomainResource: text, contained, extension, and modifierExtension
  "url" : "<uri>", // R! Literal URL used to reference this profile
  "identifier" : { Identifier }, // Additional identifier for the profile
  "version" : "<string>", // Logical id for this version of the profile
  "name" : "<string>", // R! Informal name for this profile
  "publisher" : "<string>", // Name of the publisher (Organization or individual)
  "contact" : [{ // Contact details of the publisher
    "name" : "<string>", // Name of a individual to contact
    "telecom" : [{ ContactPoint }] // Contact details for individual or publisher
  }],
  "description" : "<string>", // Natural language description of the profile
  "code" : [{ Coding }], // Assist with indexing and finding
  "status" : "<code>", // R! draft | active | retired
  "experimental" : <boolean>, // If for testing purposes, not real usage
  "date" : "<dateTime>", // Date for this version of the profile
  "requirements" : "<string>", // Scope and Usage this profile is for
  "fhirVersion" : "<id>", // FHIR Version this profile targets
  "mapping" : [{ // External specification that the content is mapped to
    "identity" : "<id>", // R! Internal id when this mapping is used
    "uri" : "<uri>", // C? Identifies what this mapping refers to
    "name" : "<string>", // C? Names what this mapping refers to
    "comments" : "<string>" // Versions, Issues, Scope limitations etc
  }],
  "type" : "<code>", // R! The Resource or Data Type being described
  "base" : "<uri>", // Structure that this set of constraints applies to
  "snapshot" : { // Snapshot view of the structure
    "element" : [{ ElementDefinition }] // 
      Definition of elements in the resource (if no profile)
  },
  "differential" : { Content as for Profile.snapshot } // Differential view of the structure
}

 

Alternate definitions: Schema/Schematron, Resource Profile (XML, JSON), Questionnaire

6.17.4.1 Terminology Bindings

PathDefinitionTypeReference
Profile.status The lifecycle status of a Resource ProfileFixedhttp://hl7.org/fhir/resource-profile-status
Profile.type Either a resource or a data typeFixedhttp://hl7.org/fhir/valueset/defined-types

6.17.4.2 Constraints

  • prf-1: On Profile.snapshot: Element paths must be unique - or not (LM) (xpath on f:Profile/f:snapshot: count(f:element) >= count(distinct-values(f:element/f:path/@value)))
  • prf-2: On Profile.mapping: Must have at a name or a uri (or both) (xpath on f:Profile/f:mapping: exists(f:uri) or exists(f:name))
  • prf-3: Parameter names must be unique within structure (xpath: count(distinct-values(f:searchParam/f:name/@value)) =count(f:searchParam/f:name))
  • prf-4: On Profile.snapshot: If a structure is a snapshot, then each element definition must have a formal definition, and cardinalities (xpath on f:Profile/f:snapshot: exists(f:base) or (count(f:element) = count(f:element[exists(f:formal) and exists(f:min) and exists(f:max)])))

6.17.5 Interpretation Notes:

  • The profile has a flat list of elements. The path element provides the overall structure and it SHALL match the structure and names in the resource structure exactly.
  • The condition element is used to assert that a constraint defined on another element affects the allowed cardinality of this element.
  • The type is used to specify which types apply when the underlying resource allows a choice of types. When the type of the element is fixed in the underlying resource definitions, it should still be stated in the profile. The type is optional because repeating groups of elements do not have a type.
  • The definition (short, formal, comments and the mappings) for an element is provided so that the resource profile can provide a more specific definition for the field in a specific context. For instance, the underlying resource definition might be "Result value" and the more specific resource definition could be "Plasma Cholesterol Test Value". The meaning needs to be consistent with the underlying definition, but can be narrower - a constraint on it.
  • For an element with a maximum cardinality of 1, there can only be one entry in the value list, which is either a literal fixed type (with an element name matching the type of the fixed value) or a name, which is a reference to a named constraint pattern. If the element has a maximum cardinality of >1, then there can be multiple values - again, either fixed values with a type or a named constraint. Each of these appears in the list with the order and cardinality specified. By this means, a list may be "sliced" into a series of different components.
  • There can be more than one entry for each element path. The constraint specification can define multiple different constraints for any element and then use them in different places. In practice, this is useful when slicing a list and the differently named constraint profiles are differentiated using the value[x] element. The name of the element constraint SHALL be unique within the constraint specification for that resource. If a constraint does not have a name, it applies to the base resource and SHALL be found in the correct place in the structure.
  • Closed is only relevant if the underlying element has a max cardinality > 1.
  • For an extension definition, the cardinality constraints are limits on the constraints of any reference to the extension in a profile. For example, if the minimum cardinality of an extension is 1 when it is defined, then any profile that includes that extension in the instance SHALL include it with a minimum cardinality of 1 and therefore any instance that conforms to the profile SHALL include the extension. Note, however, that if the extension is directly referenced in an instance rather than applied through a profile, the minimum cardinality doesn't apply, though the maximum one still does.
  • For xpath constraints, the prefix "f" should be used for "http://hl7.org/fhir", and "h" for "http://www.w3.org/1999/xhtml". XPath constraints are written against the XML representation, but SHALL be true in any other representation as well
  • When using xpath to make constraints about the relationship between the contents of the narrative and the contents of the data elements, the element against which the rule is expressed is the one against which the error or warning will be reported.

6.17.5.1 Common Mapping Targets

Profiles are able to map resource elements to concepts in other definition systems. Generally these are used to map the elements to local implementation models, data paths, and concepts. However they are also used to map to other standards and published terminologies. These are the standard URIs used for common targets of the mapping:

http://loinc.orgLOINC code for the element
http://snomed.infoSNOMED CT code for the element
http://hl7.org/v3RIM mapping
http://hl7.org/v2v2 mapping
http://nema.org/dicomDICOM tag mapping
http://w3.org/vcardvCard equivalent field
http://ihe.net/xdsXDS metadata equivalent

6.17.6 Profiled FHIR

If a profile is unambiguous, then the FHIR profile tooling (ref to be provided when the tooling exists) is able to generate reference implementation based object models that express the profiled model natively, where the object interface does not include prohibited elements, treats declared extensions as primary properties and slices lists according to the profile. This eases the burden on an implementer, though this object model can only be used with a sub-set of the possible resources.

The tooling is also able to generate bi-directional transforms between the normal XML format and an XML representation of this profiled object model and schema for this profiled XML representation. This XML form has extensions promoted into the primary XML form by using the extension code as the XML name and sliced lists are renamed to use the Profile.resource.element.name as the XML element name. Profiles are only suitable for this use if they ensure that there are no clashing extension names when the extension definition spaces are ignored and that the sliced list names are appropriate.

Implementations are allowed to exchange this profiled XML format. Implementations that do so are not fully conformant to FHIR; instead they can claim to be conformant to "Profiled FHIR". Implementations should consider carefully before adopting this approach; while it will reduce the amount of work required to initially implement particular profiles, it will increase the amount of work required to exchange this data with other communities or to re-use tooling and applications that are also used in other contexts. This cost should particularly be considered in light of the fact that the previously discussed tooling allows applications to be written as though they are dealing with "Profiled FHIR" instances when they are in fact sending and receiving fully conformant FHIR instances.

6.17.7 Search Parameters

Search parameters for this resource. The common parameters also apply. See Searching for more information about searching in REST, messaging, and services.

NameTypeDescriptionPaths
codetokenA code for the profileProfile.code
datedateThe profile publication dateProfile.date
descriptionstringText search in the description of the profileProfile.description
identifiertokenThe identifier of the profileProfile.identifier
namestringName of the profileProfile.name
publisherstringName of the publisher of the profileProfile.publisher
statustokenThe current status of the profileProfile.status
typetokenType of resource that is constrained in the profileProfile.type
urltokenLiteral URL used to reference this profileProfile.url
valuesetreferenceA vocabulary binding codeProfile.snapshot.element.binding.reference[x]
(ValueSet)
versiontokenThe version identifier of the profileProfile.version