Capabilities and Standards will be structured to have the following:
|ID||Each Capability and Standard has a unique identifier composed of one letter followed by a number. The letter "C" indicates a Capability and an "S" indicates a Standard. The number is arbitrary and does not have any additional meaning such as priority, sequence or inter-relationships. This allows for the of Capabilities and standards in a consistent manner.|
|Version||Each Capability and Standard has a number. Each Capability and Standard can change independently and its 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.|
defines the type of Standard:
- Capability Specific Standard
- Context Specific Standard
- Overarching Standard
Each Capability and Standard will have one of five statuses:
Those Standards that are mandated under the Catalogue Agreement will have an Effective Date by which suppliers must comply with the Standard.
Suppliers will need to have achieved compliance against all Effective Standards (see Status above) in order to onboard on to the Catalogue and be awarded a place on the first GP IT Futures Framework
Standards will also have the following:
|Requirement ID||Each requirement within a Standard will have a unique 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|
|Requirement Level||Each requirement within a Standard will have a level as defined in RFC 2119.1, the Change Management and Roadmap Content ancillary document and the Master Glossary|
Each requirement within a Standard will be mapped to one or more Epics (Capability Specific Standards only)
This describes the main users of the Capability and the outcomes they want to achieve from using the Solution.
Epics and Acceptance Criteria
These describe the requirements of the Capability at a high level and will be used to assess the suitability of Solutions from suppliers at the Capabilities Assessment stage of . In order to pass any Epic, all associated Acceptance Criteria for that Epic must pass the assessment.
Must Epics will always be assessed.
All May Epics and Acceptance Criteria will be evaluated during the Capability Assessment Stage of On-boarding. However, these Epics are not mandatory and will not be used as part of the overall assessment of whether the Capability is fully met. Any May Epics that are assessed as met will be available to buyers via the Buying Catalogue.
For each Capability, it will state on Confluence whether they are only to be offered as a Full Capability or whether they can be offered as either a Full or Partial Capability.
- If the Capability is identified as a Capability that can only be offered as a Full Capability, all Must Epics must be passed for that Capability to be accepted. These types of Capabilities can only ever be Full Capabilities; they will not be accepted as Partial Capabilities.
- If the Capability is identified as a Capability that can either be offered as Full or Partial Capability, at least one Must Epic must be passed for that Capability to be accepted. If all Must Epics of this type of Capability are accepted the Capability will be accepted as a Full Capability; if at least one but not all Must Epics are accepted the Capability will be accepted as a Partial Capability.
Each Epic has a unique identifier composed of the associated Capability ID followed by the letter “E” and a further number, for example, C1E1. C1E2 etc. This allows for the identification of Epics in a consistent manner.
Standards which apply to all Suppliers irrespective of the Capabilities their Solutions support.
Suppliers will be assured against Overarching Standards.
Where present, Associated Standards will have to be fulfilled in addition to the Overarching Standards to deliver the Capability.
Capabilities can have the following Associated Standards:
- Context Specific Standards which include:
- Common Reporting Standard
- Management Information Reporting
- Citizen Access Standard
- Interoperability Standard(s)
- Capability Specific Standards, which are only applicable to Supplier Solutions delivering a particular Capability
With regards to the terminology, it is acknowledged that there are formal publishing Standards bodies like ISO, PRSB and NHS Digital. Where possible we will always refer out to existing national and international Standards, but as a Programme will be using the word Standard(s) to refer more broadly to a collection of requirements that ensure a level of safety, security, quality and interoperability that Suppliers will be mandated to comply with in order to maintain compliance with the Catalogue Agreement.
We will stay closely aligned to the Standards publishing bodies and flag the development of new Standards via the Roadmap.
Supplier Solutions will be assured against all requirements in these associated Standards.
If the is identified as a 'Discretionary Capability' then a subset of the 'MUST' Level requirements in the Capability Specific Standards which are provided by the Supplier may be assessed as suitable to provide the Capability.
Summarises future changes and opportunities for Suppliers in relation to the Capability or Standard. These are linked to the individual Roadmap pages which provide further information on the Roadmap item.