Clarity Tech Ltd

Electronic Document and Records Management (EDRM)

Clarity Tech has experience with public sector patient record systems. Electronic document and records management is a programme or set of programmes which is designed to store and track records. An EDRM captures a record as well as any associated metadata, which is then categorised within a classification scheme.


  • Aligns to information management policies and principles
  • Full interaction history and audit logging
  • Data analysis, reporting and user dashboards
  • Enterprise search functionality
  • Integration with Word, Exchange, Active Directory and common applications
  • Delivered using agile methodologies across full project lifecycle
  • Ongoing support and maintenance of the delivered solution


  • Consistent and measurable improvement in everyday business processes
  • Full integration with Microsoft Office and 3rd party applications
  • Clear product roadmap incorporating OpenText and Sharepoint
  • Agile product which scales as an organisation changes
  • Flexible hosting model
  • Supports information management policies
  • Strong Social and Collaboration features
  • Provide value for money


£550 to £1250 per person

Service documents


G-Cloud 11

Service ID

8 0 8 9 6 9 0 5 6 0 7 3 7 5 8


Clarity Tech Ltd

Faiz Ahmad


Service scope

Software add-on or extension
Cloud deployment model
  • Public cloud
  • Private cloud
  • Hybrid cloud
Service constraints
All Microsoft Azure constraints and limits will be applicable e.g. Virtual Machine Scale Sets limits, Networking limits, DNS limits, Storage limits etc
System requirements
  • May need software licences
  • May need anti-virus software
  • Reliable Internet connection in place
  • Computer meets the minimum system requirements for the product

User support

Email or online ticketing support
Email or online ticketing
Support response times
Clarity Tech JIRA Service Tool

Priority 1
We will acknowledge the issue within 4 working hour and provide a response including an action plan for resolution or cause within 8 working hours.

Priority 2
We will acknowledge the issue within 6 working hours and provide a response including an action plan for resolution or cause within 10 working hours.

Priority 3
We will respond within 1 working day and will aim to provide a fix within 5 working days of the incident being reported.

Priority 4
Where applicable, we will provide a solution as part of the next release.
User can manage status and priority of support tickets
Phone support
Phone support availability
9 to 5 (UK time), Monday to Friday
Web chat support
Onsite support
Yes, at extra cost
Support levels
We provide 1st, 2nd and 3rd Level support.
1st Line: £120/day
2nd Line: £280/day
3rd Line: £400/day
We will provide technical account manager
Support available to third parties

Onboarding and offboarding

Getting started
Will provide user documentation.
Service documentation
Documentation formats
  • HTML
  • PDF
  • Other
Other documentation formats
MS Word
End-of-contract data extraction
All Virtual Machine Images and Data Storage are available in a Azure Data Warehouse, which cab be downloaded from these storage account. It depends upon user's retention policy.
End-of-contract process
End-of-contract will be dependent on the specific requirements of the solution provided. All the necessary Data ready for export, extraction, or deletion will be provided and included in the price of contract. Any additional requirements will be charged according to our SIFA rate card.

Using the service

Web browser interface
Supported browsers
  • Internet Explorer 9
  • Internet Explorer 10
  • Internet Explorer 11
  • Microsoft Edge
  • Firefox
  • Chrome
  • Safari 9+
Application to install
Designed for use on mobile devices
Differences between the mobile and desktop service
Operating systems, design and types of devices may impact display and features.
Service interface
What users can and can't do using the API
Users can perform basic create, read, update, and delete (CRUD) operations by using the Representational State Transfer (REST) interface provided by SharePoint 2013. The REST interface exposes all of the SharePoint entities and operations that are available in the other SharePoint client APIs. One advantage of using REST is that you don’t have to add references to any SharePoint 2013 libraries or client assemblies. Instead, you make HTTP requests to the appropriate endpoints to retrieve or update SharePoint entities, such as webs, lists, and list items. SharePoint Client API will depend on following three factors; The type of application, Your existing skills and The device on which the code runs. Note: Role-based access control (RBAC) will be applied, which will enables access management for Azure resources. Using RBAC, you can segregate duties within your team and grant only the amount of access to users, groups and applications that they need to perform their jobs. Role-based access can be granted to users using the Azure portal, Azure Command-Line tools or Azure Management APIs.
API documentation
API documentation formats
  • HTML
  • PDF
API sandbox or test environment
Customisation available
Description of customisation
Depending upon the requirements some functionality can be customised.


Independence of resources
Using Azure Resource Manager and Monitoring within Azure Portal, which will enables us to keep track of demand.


Service usage metrics


Supplier type
Not a reseller

Staff security

Staff security clearance
Other security clearance
Government security clearance
Up to Developed Vetting (DV)

Asset protection

Knowledge of data storage and processing locations
Data storage and processing locations
United Kingdom
User control over data storage and processing locations
Datacentre security standards
Complies with a recognised standard (for example CSA CCM version 3.0)
Penetration testing frequency
At least every 6 months
Penetration testing approach
Protecting data at rest
  • Physical access control, complying with CSA CCM v3.0
  • Physical access control, complying with SSAE-16 / ISAE 3402
Data sanitisation process
Data sanitisation type
  • Explicit overwriting of storage before reallocation
  • Deleted data can’t be directly accessed
Equipment disposal approach
A third-party destruction service

Data importing and exporting

Data export approach
Azure Import/Export service enables you to transfer large amounts of data to and from Azure using hard disk drives. Import/Export is faster and more cost-effective for moving big data sets compared to transferring the data over the Internet. It enables users to transfer data to Azure using secure transport of hard disk drives to the data centres and using high-speed secure internal network.
Data export formats
  • CSV
  • ODF
Data import formats
  • CSV
  • ODF

Data-in-transit protection

Data protection between buyer and supplier networks
  • Private network or public sector network
  • Legacy SSL and TLS (under version 1.2)
Data protection within supplier network
Legacy SSL and TLS (under version 1.2)

Availability and resilience

Guaranteed availability
99.9% - Will be covered by Microsoft SLA
Approach to resilience
Using Azure
Outage reporting
Email alerts

Identity and authentication

User authentication needed
User authentication
  • 2-factor authentication
  • Dedicated link (for example VPN)
  • Username or password
Access restrictions in management interfaces and support channels
Will use Azure identity management and access control security best practices include: Centralize your identity management Enable Single Sign-On (SSO) Deploy password management Enforce multi-factor authentication (MFA) for users Use role based access control (RBAC) Control locations where resources are created using resource manager
Access restriction testing frequency
At least every 6 months
Management access authentication
  • 2-factor authentication
  • Dedicated link (for example VPN)
  • Username or password

Audit information for users

Access to user activity audit information
Users have access to real-time audit information
How long user audit data is stored for
Access to supplier activity audit information
Users contact the support team to get audit information
How long supplier audit data is stored for
How long system logs are stored for

Standards and certifications

ISO/IEC 27001 certification
ISO 28000:2007 certification
CSA STAR certification
PCI certification
Other security certifications
Any other security certifications
Cyber Security Essential

Security governance

Named board-level person responsible for service security
Security governance certified
Security governance standards
  • CSA CCM version 3.0
  • ISO/IEC 27001
Information security policies and processes
CSA CCM v3.0
ISO/IEC 27001

Operational security

Configuration and change management standard
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Configuration and change management approach
We use Microsoft Visual Services tool as well as Azure Monitoring dashboard to track components of our services.
We use Azure Cloud to simulate testing environment which is similar to the operating environment. Testing including performance and security is carried out prior to release.
Vulnerability management type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Vulnerability management approach
Will use Azure Security Center which offers integrated vulnerability assessment with Qualys cloud agents as part of the Virtual Machine. The solution can be deployed to multiple VMs at one time and once deployed, the Qualys agent will start reporting vulnerability data to the Qualys management platform, which in turn provides vulnerability and health monitoring data back to Security Center. Users can quickly identify vulnerable VMs from the Security Center dashboard. Additional reports and information are available in the Qualys management console, which is linked directly from Security Center.
Protective monitoring type
Conforms to a recognised standard, for example CSA CCM v3.0 or SSAE-16 / ISAE 3402
Protective monitoring approach
Using Microsoft global 24x7 incident response service that works to mitigate the effects of attacks and malicious activity. The incident response team follows established procedures for incident management, communication, and recovery, and uses discoverable and predictable interfaces with internal and external partners alike.
Incident management type
Conforms to a recognised standard, for example, CSA CCM v3.0 or ISO/IEC 27035:2011 or SSAE-16 / ISAE 3402
Incident management approach
Will use following process phases: • Identification – Events will be investigated and will be assigned a severity classification. • Containment – The escalation team will evaluates the scope and impact of an incident. • Eradication – After the situation is contained, the escalation team moves toward eradicating any damage caused by the security breach, and identifies the root cause for why the security issue occurred. • Recovery – System and services will be returned to a full working capacity. • Customer’s notified if data breaches or unauthorized access.

Secure development

Approach to secure software development best practice
Supplier-defined process

Public sector networks

Connection to public sector networks
Connected networks
  • Public Services Network (PSN)
  • NHS Network (N3)
  • Joint Academic Network (JANET)
  • Health and Social Care Network (HSCN)


£550 to £1250 per person
Discount for educational organisations
Free trial available

Service documents

Return to top ↑