A compartment definition that defines how resources are accessed on a server.

In FHIR, search is not performed directly on a resource (by XML or JSON path), but on a named parameter that maps into the resource content.

An absolute URI that is used to identify this compartment definition when it is referenced in a specification, model, design or an instance. instance; also called its canonical identifier. This SHALL be a URL, SHOULD be globally unique, unique and SHOULD be an a literal address at which an authoritative instance of this compartment definition is (or will be) published. The This URL SHOULD include can be the major version target of a canonical reference. It SHALL remain the same when the compartment definition. For more information see Technical and Business Versions . definition is stored on different servers.

Allows the compartment definition to be referenced by a single globally unique identifier.

Can be a urn:uuid: or a urn:oid:, urn:oid: but real http: addresses are preferred. Multiple instances may share the same url URL if they have a distinct version.

The determination of when to create a new version of a resource (same url, new version) vs. defining a new artifact is up to the author. Considerations for making this decision are found in Technical and Business Versions .

In some cases, the resource can no longer be found at the stated url, but the url itself cannot change. Implementations can use the meta.source element to indicate where the current master source of the resource can be found.

The identifier that is used to identify this version of the compartment definition when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the compartment definition author and is not expected to be globally unique. For example, it might be a timestamp (e.g. yyyymmdd) if a managed version is not available. There is also no expectation that versions can be placed in a lexicographical sequence.

There may be different compartment definition instances that have the same identifier but different versions. The version can be appended to the url in a reference to allow a reference to a particular business version of the compartment definition with the format [url]|[version]. The version SHOULD NOT contain a '#' - see Business Version .

Indicates the mechanism used to compare versions to determine which is more current.

If set as a string, this is a FHIRPath expression that has two additional context variables passed in - %version1 and %version2 and will return a negative number if version1 is newer, a positive number if version2 and a 0 if the version ordering can't be successfully be determined.

A natural language name identifying the compartment definition. This name should be usable as an identifier for the module by machine processing applications such as code generation.

Support human navigation and code generation.

The name is not expected to be globally unique. The name should be a simple alpha-numeric alphanumeric type name to ensure that it is computable friendly. This machine-processing friendly.This is often the same as the code for the parameter, but does not need to be.

A short, descriptive, user-friendly title for the compartment definition. capability statement.

This name does not need to be machine-processing friendly and may contain punctuation, white-space, etc.

The status of this compartment definition. Enables tracking the life-cycle of the content.

Allows filtering of compartment definitions that are appropriate for use vs. versus not. This is labeled as "Is Modifier" because applications should not use a retired compartment definition without due consideration.

See guidance around (not) making local changes to elements here .

A boolean Boolean value to indicate that this compartment definition is authored for testing purposes (or education/evaluation/marketing), education/evaluation/marketing) and is not intended to no version of this resource will ever be used intended for genuine usage.

Enables experimental content to be developed following the same lifecycle that would be used for a production-level compartment definition.

Allows filtering of compartment definition definitions that are appropriate for use vs. not. This versus not.. Experimental resources might include example instances in implementation guides, instances created solely for testing purposes, etc. If experimental is labeled as "Is Modifier" because applications 'true' for any version of a resource, it should not use an be true for all versions of the resource. (If experimental compartment definition in production. changes, then it is being misused or a resource that was never intended for real-world use has unexpectedly changed its purpose.).

Experimental resources are not expected to be stable and may well have breaking changes without a corresponding change to the 'version' element.

The date (and optionally time) when the compartment definition was published. last significantly changed. The date must change if and when the business version changes and it must change if the status code changes. In addition, it should change when the substantive content of the compartment definition changes.

The date is often not tracked until the resource is published, but may be present on draft content. Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the compartment definition. Additional specific dates may be added as extensions or be found by consulting Provenances associated with past versions of the resource.

See guidance around (not) making local changes to elements here .

The name of the individual or organization that published or individual responsible for the release and ongoing maintenance of the compartment definition.

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

Usually an organization, organization but may be an individual. The publisher (or steward) of the compartment definition is the organization or individual primarily responsible for the maintenance and upkeep of the compartment definition. This is not necessarily the same individual or organization that developed and initially authored the content. The publisher is the primary point of contact for questions or issues with the compartment definition. This item SHOULD be populated unless the information is available from context.

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

May be a web site, an email address, a telephone number, etc.

See guidance around (not) making local changes to elements here .

A free text natural language description of the compartment definition from a consumer's perspective.

This description can be used to capture details such as why the compartment definition was built, comments about misuse, instructions for clinical use and interpretation, literature references, examples from the paper world, etc. It is not a rendering of the compartment definition as conveyed in the 'text' field of the resource itself. This item SHOULD be populated unless the information is available from context (e.g. the language of the profile compartment definition is presumed to be the predominant language in the place the profile compartment definition was created).

The content was developed with a focus and intent of supporting the contexts that are listed. These terms contexts may be general categories (gender, age, ...) or may be references to specific programs (insurance plans, studies, ...) and may be used to assist with indexing and searching for appropriate compartment definition instances.

Assist in searching for appropriate content.

When multiple useContexts are specified, there is no expectation whether that all or any of the contexts apply.

A legal or geographic region in which the Explanation of why this compartment definition is intended to be used. needed and why it has been designed as it has.

It may be possible for This element does not describe the usage of the compartment definition to definition. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used in jurisdictions other than those for which it was originally designed to point to source materials or intended. specifications that drove the structure of this compartment definition.

Which compartment this definition describes.

Only the specification can define the compartments that can exist. Servers can choose to support them.

Whether the search syntax is supported,.

Servers may define and use compartments to manage logical access without implementing the compartment related syntax.

Information about how a resource is related to the compartment.

The name of a resource supported by the server.

The name of a search parameter 'code' as defined in the core specification that represents the link to the compartment. More than one may be listed because a resource may be linked to a compartment in more than one way,.

More than one may be listed because a resource may be linked to a compartment in more than one way. Note that a given server might use a different 'code' for the SearchParameter in their CapabilityStatement. The inclusion rules are based on the 'base' HL7 search parameter code value, not the server-specific code value. E.g. if a server uses code 'doc' instead of 'performer' for their Procedure performer search performer, the 'doc' search would still apply when determining membership in the Practitioner compartment. If no search parameters are listed, then the resource is not linked to the compartment.

Additional documentation about the resource and compartment. Search Parameter for mapping requests made with $everything.start (e.g. on Patient.$everything ).

Search Parameter for mapping requests made with $everything.end (e.g. on Patient.$everything ).