A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals.
A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals.
If the element is present, it must have either a @value, an @id, or extensions
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.
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.
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.
Indicates the mechanism used to compare versions to determine which is more current.
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.
A short, descriptive, user-friendly title for the Requirements.
The status of this Requirements. Enables tracking the life-cycle of the content.
A Boolean value to indicate that this Requirements is authored for testing purposes (or education/evaluation/marketing) and is not intended to be used for genuine usage.
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.
The name of the organization or individual responsible for the release and ongoing maintenance of the Requirements.
Contact details to assist a user in finding and communicating with the publisher.
A free text natural language description of the requirements.
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.
A legal or geographic region in which the Requirements is intended to be used.
Explanation of why this Requirements is needed and why it has been designed as it has.
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.
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').
Another set of Requirements that this set of Requirements builds on and updates.
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.
An actor these requirements are in regard to.
The actual statement of requirement, in markdown format.
A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals.
Key that identifies this statement (unique within this resource).
A short human usable label for this statement.
A short human usable label for this statement.
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.
The actual requirement for human consumption.
Another statement on one of the requirements that this requirement clarifies or restricts.
A larger requirement that this requirement helps to refine and enable.
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.
A reference to another artifact that created this requirement. This could be a Profile, etc., or external regulation, or business requirements expressed elsewhere.
Who asked for this statement to be a requirement. By default, it's assumed that the publisher knows who it is if it matters.
SHALL
SHOULD
MAY
SHOULD-NOT
If the element is present, it must have either a @value, an @id, or extensions