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.

Often called a clinical template.

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 systems.

So you can say, in a profile, what the full extensions URLs should be. This is required to allow hosting profiles on multiple different servers, and to allow for the editorial process.

A 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).

This is for use if it's not possible to use the literal URI - such as in a CDA template ID.

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.

There may be multiple resource versions of the profile that have this same identifier. The resource version id will change for technical reasons, whereas the stated version number needs to be under the author's control.

N/A.

A free text natural language name identifying the Profile.

Not expected to be globally unique.

The name of the individual or organization that published the profile.

Helps establish the "authority/credibility" of the profile. May also allow for contact.

Usually an organization, but may be an individual. This item SHOULD be populated unless the information is available from context.

Contacts to assist a user in finding and communicating with the publisher.

May be a web site, an email address, a telephone number (tel:), etc.

The name of an individual to contact regarding the profile.

If there is no named individual, the telecom is for the organization as a whole.

Contact details for individual (if a name was provided) or the publisher.

A free text natural language description of the profile and its use.

This field can be used for things such as why the profile was written, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the profile as conveyed in Profile.text. This item SHOULD be populated unless the information is available from context.

A set of terms from external terminologies that may be used to assist with indexing and searching of templates.

Assist in searching for appropriate profiles.

The status of the profile.

Allows filtering of profiles that are appropriate for use vs. not.

This profile was authored for testing purposes (or education/evaluation/marketing), and is not intended to be used for genuine usage.

Allows filtering of profiles that are appropriate for use vs. not.

The date that this version of the profile was published.

The Scope and Usage that this profile was created to meet.

The 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 version.

A profile does not need to specify the target it applies to,as profiles will often be valid across multiple versions of FHIR. FHIR tooling can determine whether a profile is consistent with a particular profile if desired.

An external specification that the content is mapped to.

An Internal id that is used to identify this mapping set when specific mappings are made.

The specification is described once, with general comments, and then specific mappings are made that reference this declaration.

A URI that identifies the specification that this mapping is expressed to.

A formal identity for the specification being mapped to helps with identifying maps consistently.

A name for the specification that is being mapped to.

Comments about this mapping, including version notes, issues, scope limitations, and other important notes for usage.

The Resource or Data type being described.

Only complex types can be constrained, not primitive types such as string etc.

The structure that is the base on which this set of constraints is derived from.

If differential constraints are specified in this structure, they are applied to the base in a "differential" fashion. If there is no base, then the differential constraints cannot be provided (snapshot only). Differential structures are useful for the editing perspective, and snapshot structures are suitable for operational use. The FHIR Project provides a number of tools/services to populate snaphots from differential constraints.

A snapshot view is expressed in a stand alone form that can be used and interpreted without considering the base profile.

Captures constraints on each element within the resource.

A differential view is expressed relative to the base profile - a statement of differences that it applies.