A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals.

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

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

Can be a urn:uuid: or a urn:oid: but real http: addresses are preferred. Multiple instances may share the same 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.

A formal identifier that is used to identify this Requirements when it is represented in other formats, or referenced in a specification, model, design or an instance.

Allows externally provided and/or usable business identifiers to be easily associated with the module.

The identifier that is used to identify this version of the Requirements when it is referenced in a specification, model, design or instance. This is an arbitrary value managed by the Requirements 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 Requirements 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 Requirements 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 Requirements. 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 alphanumeric type name to ensure that it is machine-processing friendly.

A short, descriptive, user-friendly title for the Requirements.

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

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

Allows filtering of Requirements that are appropriate for use versus not.

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

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

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

Allows filtering of Requirements that are appropriate for use versus not.. Experimental resources might include example instances in implementation guides, instances created solely for testing purposes, etc

The date (and optionally time) when the Requirements was published. The date must change 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 Requirements changes.

Note that this is not the same as the resource last-modified-date, since the resource may be a secondary representation of the Requirements. 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 organization or individual responsible for the release and ongoing maintenance of the Requirements.

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

Usually an organization but may be an individual. The publisher (or steward) of the Requirements is the organization or individual primarily responsible for the maintenance and upkeep of the Requirements. 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 Requirements. 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 requirements.

This description can be used for a general description of the requirements, and which covers why it was defined.

The content was developed with a focus and intent of supporting the contexts that are listed. These 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 Requirements instances.

Assist in searching for appropriate content.

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

A legal or geographic region in which the Requirements is intended to be used.

It may be possible for the Requirements to be used in jurisdictions other than those for which it was originally designed or intended

DEPRECATION NOTE: For consistency, implementations are encouraged to migrate to using the new 'jurisdiction' code in the useContext element. (I.e. useContext.code indicating http://terminology.hl7.org/CodeSystem/usage-context-type#jurisdiction and useContext.valueCodeableConcept indicating the jurisdiction.).

Explanation of why this Requirements is needed and why it has been designed as it has.

This element does not describe the usage of the Requirements. Instead, it provides traceability of ''why'' the resource is either needed or ''why'' it is defined as it is. This may be used to point to source materials or specifications that drove the structure of this Requirements.

A copyright statement relating to the Requirements and/or its contents. Copyright statements are generally legal restrictions on the use and publishing of the Requirements.

Consumers must be able to determine any legal restrictions on the use of the Requirements.

...

A short string (<50 characters), suitable for inclusion in a page footer that identifies the copyright holder, effective period, and optionally whether rights are resctricted. (e.g. 'All rights reserved', 'Some rights reserved').

Defines the content expected to be rendered in all representations of the artifact.

The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element.

Another set of Requirements that this set of Requirements builds on and updates.

Existing statements (by key) may be narrowed or clarified, and additional statements added.

Points to requirements defined elsewhere that have the same force as if they were defined in this instance.

A given requirement should either appear here OR be listed as a derivedFrom in a statement, but not both. I.e. you either include the referenced requirement unchanged or you include it in a qualified manner.

The canonical for the Requirements resource to import statements from.

The key of a statement to treat as part of the set of requirements defined in this instance.

If no keys are specified, then the interpretation is that all statements in the referenced Requirements instance apply to this instance.

A reference to another artifact that created this set of requirements. This could be a profile, etc., or external regulation, or business requirements expressed elsewhere. This URI is intended to point to a specific web page for an artifact, not a canonical URL. If pointing to HL7 specifications, it is best to point to the version-specific URL.

An actor these requirements are in regard to.

If more than one actor is specified, then it's up to the statements to explicitly identify the actors that are relevant if the statement doesn't apply to all actors.

The canonical for an actor relevant to some of the requirements.

A unique string used to reference the actor from specific requirements.

The actual statement of requirement, in markdown format.

Key that identifies this statement (unique within this resource).

Refer directly to the statement by {url}#{key}

A short human usable label for this statement.

The key is intended for computers, while this is intended for humans. In its absence, the key should be convenient for a human to say (e.g. not a UUID)

A short human usable label for this statement.

This element is allowed to repeat because a single requirements statement might contain multiple conformance words and thus need to be indexed under multiple conformance categories.

The conformance code is extracted from the requirement to make indexing and display easier. The requirement needs to express the conformance verbs directly in the markdown content. It's not unusual to mix verbs in a single sentence (e.g. System SHALL do X and SHOULD do Y)

This boolean flag is set to true of the text of the requirement is conditional on something e.g. it includes lanauage like 'if x then y'. This conditionality flag is introduced for purposes of filtering and colour highlighting etc.

There is no intent that the conditional statement by evaluatable

The actual requirement for human consumption.

Indicates that this statement is refining, tightening, or establishing more context for the referenced requirement/statement.

With derivedFrom, the scope of what is being accomplished is the same (as opposed to partOf, where the scope of what is being accomplished by the part is narrower). If only the key is populated, this means the statement derives from another sibling statement in the same Requirements resource. If both key and canonical are populated, this indicates the statement derives from an external Requirements resource. The canonical must point to one of the Requirements.derivedFrom values present in the current resource.

The canonical of the Requirements instance this statement is derivedFrom.

The key, either within this resource or the specified Requirements resource this statement is derivedFrom.

Identifies a higher-level requirement or statement which this referencing statement is a logical sub-requirement of. I.e. This statement is a necessary step to achieving the referenced requirement/statement.

Allows requirements to be organized compositionally. E.g. Epic/Story/Task.

If only the key is populated, this is partOf a statement within the same Requirements resource. If both key and canonical are populated, this is partOf a statement in an external Requirements resource.

The canonical of the Requirements instance this statement is a part of.

The key, either within this resource or the specified Requirements resource this statement is a part of.

A reference to another artifact that satisfies this requirement. This could be a profile, extension, or an element in one of those, or a CapabilityStatement, OperationDefinition, SearchParameter, CodeSystem(/code), ValueSet, Libary etc.

This is for use when the requirement is met be a pre-existing artifact e.g. a rule that's met by the base FHIR spec, or a national implementation guide. It is more typical to point from the FHIR artifact satisfying the requirement to the requirement (using the satisfies-requirement extension) to the Requirements resource. However, in some cases the author of the Requirements and satisfying resource(s) won't be coordinated in that manner and this element allows assertion of satisfaction without involvement from those managing the implementing artifacts.

A reference to another artifact that created this requirement. This could be a profile, etc., or external regulation, or business requirements expressed elsewhere. This URI is intended to point to a specific web page for an artifact, not a canonical URL. If pointing to HL7 specifications, it is best to point to the version-specific URL.

Who asked for this statement to be a requirement. By default, it's assumed that the publisher knows who it is if it matters.

A reference to the key of an actor listed in Requirements.actor that is relevant to this requirement statement.

If not specified, all actors listed on the Requirements is presumed to be relevant to the statement.