Introduction to Capabilities and Standards
What are Capabilities?
The requirements to deliver the Digital Care Services Cloud Telephony Solutions are grouped into Capabilities. Each Capability describes the business need at the highest level. For example, ‘Office Telephony’ describes the need for the Practice to receive inbound and make outbound calls.
Capabilities will be used :
To express the business needs during the procurement
For the initial assessment of Solutions
Suppliers to categorise their products and to see market opportunities
What are Epics and Acceptance Criteria?
Epics are individual high level business requirements and describe features relevant to the Capabilities they belong to. All Epics together define the full scope of a Capability.
The Acceptance Criteria associated with an Epic define the minimum expected functions a Supplier’s Solution must deliver and are test scenarios that will be used during Capability Assessment stage of Onboarding to establish whether a Supplier’s Solution meets the Epic or not. In order to pass any Epic, all associated Acceptance Criteria for that Epic must pass the assessment.
Epics are classified as either MUST or MAY Epics and all Epics will be assessed during the Capability Assessment stage of Onboarding. It is recommended that Suppliers consider all Epics as part of User Research to understand what the Minimal Viable Product (MVP) is for their users.
Each Epic has a unique identifier which allows for the identification of Epics in a consistent manner, e.g. ‘E00267’.
Must Epics
MUST Epics are mandatory and used to confirm during Capability Assessment stage of Onboarding that a Solution delivers the minimum required for a Capability. A Supplier Solution needs to meet all MUST Epics in order to pass Capability Assessment for a Capability.
May Epics
These Epics are not mandatory, however it is recommended a Supplier considers all MAY Epics. Which MAY Epics a Supplier chooses to implement should be determined by their User Research. All MAY Epics and Acceptance Criteria will be evaluated during the Capability Assessment Stage of On-boarding. Any MAY Epics that are assessed as met will be available to buyers.
What are Additional Implementation Details?
Additional Implementation Details are mandatory details related to a specific Epic and are assessed during the Assurance stage of Onboarding.
These details can include references to other Standards and Suppliers will need to complete assurance activities related to those Standards.
What is Supporting Information?
This information may be useful to Suppliers when implementing the related Epic, but is not mandatory and is for guidance only.
What are Standards?
Standards describe the technical or operating conditions required to achieve Catalogue Compliance.
Standards will be used :
To express any technical and non-functional requirements
By Suppliers to understand what is expected of them in order to be compliant
By Catalogue Authority to assess Supplier Solutions against in order to award compliance
Capabilities and Standards Model
The Capabilities and Standards are structured in the model below.
There are a set of Overarching Standards that are applicable to all Supplier Solutions (e.g. Commercial Standard)
There are Capabilities to describe the business needs at the highest level
There are Interoperability Standards which contain requirements applicable to all Solutions and some that are only applicable to certain Capabilities
