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 no version of this resource will ever be intended 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 authority that maintains the resource is operating. In general, the jurisdiction is also found in the useContext. The useContext may reference additional jurisdictions because the defining jurisdiction does not necessarily limit the jurisdictions of use. 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 notices of intellectual property ownership and can include 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 restricted. (e.g. 'All rights reserved', 'Some rights reserved'). Another set of Requirements that this set of Requirements builds on and updates. Points to requirements defined elsewhere that have the same force as if they were defined in 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. The actual statement of conformance requirement. A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals. 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. A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals. The canonical for an actor relevant to some of the requirements. A unique string used to reference the actor from specific requirements. 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 language like 'if x then y'. This conditionality flag is introduced for purposes of filtering and colour highlighting etc. The actual requirement for human consumption. Categorization might be done automatically (inferred by code) or manually by user assertion. The absence of a category may limit the ability to determine when the element should be handled, so strong consideration should be given to how systems will be able to determine category values for legacy data and how data that cannot be categorized will be handled. As well, some categories might not be mutually exclusive, so systems should prepare for multiple declared categories - even within a single category 'axis'. Indicates that this statement is refining, tightening, or establishing more context for the referenced requirement/statement. 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. 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, Library etc. 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. A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals. 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. A set of requirements - a list of features or behaviors of designed systems that are necessary to achieve organizational or regulatory goals. 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. SHALL SHOULD MAY SHOULD-NOT SHALL-NOT If the element is present, it must have either a @value, an @id, or extensions