...
ID | Each Capability and Standard has a unique alphanumeric identifier. The letter "C" indicates a Capability, an "S" indicates a Standard and “SCS” indicates a Supplementary Care Standard. The number is arbitrary and does not have any additional meaning such as priority, sequence or inter-relationships. This allows for the identification of Capabilities and Standards in a consistent manner. |
---|---|
Version | Each Capability and Standard has a version number. Each Capability and Standard can change independently and it's version number will change accordingly. Version numbers are subject to change depending on the nature of the change (e.g. major, minor, patch). There is no relationship between the version numbers of different Capabilities and Standards. |
Type | Indicates a Capability or a Standard and where applicable, defines the type of Standard:
|
Category | Only Capabilities have the Category field. Category is used to group related Capabilities on the Buying Catalogue. |
Status | Each Capability and Standard will have one of five statuses:
|
Effective Date | Capabilities and Standards that are mandated under the Catalogue Agreement will have an Effective Date by which Suppliers must comply with the Capability or Standard. Suppliers will need to have achieved compliance against relevant Effective Capabilities and Standards (see Status above) in order to onboard on to the Buying Catalogue. There may be other Capabilities and Standards that Suppliers need to achieve compliance with as part of the Contracting Vehicle Agreement in order to be awarded a place on a Contracting Vehicle. |
Contracting Vehicle(s) | Indicates the commercial Contracting Vehicle a Capability or Standard is applicable to. |
...
Description | A concise description of the purpose of the Standard covering the mandatory scope. |
---|---|
Contracting Vehicle(s) | Specifies which Contracting Vehicle the requirement applies to (i.e. some requirements may only apply to certain Contracting Vehicles and not all). |
Requirement ID | Each requirement within a Standard will have a unique Requirement ID so it can be recognised during compliance. |
Requirement Text | The description of each requirement within a Standard that will be used to determine compliance of a Solution with the Standard. |
Level | Each requirement within a Standard will have a level as defined in the RFC 2119.1 and Ancillary Document (Change Management Process and Roadmap Content). |
Structure of
...
Non-Overarching Standards
Technical and non-functional requirements for a specific interface or integration.
...