The useful question is what the evidence covers.
A customer needs evidence matched to the proposed use. Functionality, setting, responsibilities and jurisdiction affect that question. This page helps medicines leaders, evaluators and investors identify the evidence needed before committing further resources, rather than rely on a general badge or readiness phrase.
Start with the intended use
Describe who would use the proposed capability, the task it supports, its output and what happens afterwards. A document-preparation tool, a clinical recommendation and a workflow tracker can raise different questions even when all are described as medicines software. The task must be defined before deciding which assessment route, expertise and evidence are appropriate. A public marketing description is not a substitute for that scoped examination.
MHRA (2023), intended-purpose guidance explains the role of a clear intended purpose in software development. MHRA (2025), software and AI guidance provides wider context on software and AI as medical devices. These are primary references for assessing potential requirements; they do not establish a regulatory classification or approval for PHARMORIS. Any future capability and proposed use would need to be examined on its own terms by appropriately qualified people.
Keep different assurance questions distinct
Clinical safety, data protection, technical security, interoperability and usability address different parts of a technology and its use. A positive answer in one area does not settle the others. An organisation may need information about the supplier, a specific product version and its local implementation. Those are related but separate subjects, with responsibilities that should be clear to the people deciding whether an evaluation is appropriate.
NHS England (2026), DTAC guidance describes the NHS assessment framework and its relationship with other processes. Its current guidance states that the previous form should not be used from 6 April 2026. The practical lesson is to use the applicable current materials when an assessment is undertaken, rather than treat an old completed template as a permanent statement of readiness. DTAC does not replace other required approvals.
Read a certificate or assessment in context
A useful public claim should identify the issuing body, subject, scope and date of its supporting record. A management-system certificate does not automatically certify every product function. An assessment for one version or environment may not address a later change. If evidence is relevant to a potential purchase, the buyer should be able to understand what was assessed and whether that matches the proposed use.
Current programme descriptions do not establish production certification, NHS deployment or regulatory approval. The product-status page and trust centre provide the portfolio context for examining a proposed use.
Match an evaluation to the evidence it can produce
A bounded evaluation might examine source traceability, preparation quality, review effort or the clarity of an organisational handover. Those questions can be valuable without making the activity a clinical deployment. The proposal should identify its scope, comparator, reviewers, information requirements and stop conditions. If the use changes during the work, the evidence and applicable responsibilities need to be reconsidered rather than quietly broadened.
Access, processing and implementation need their own agreements and relevant assessment. A demonstration or funded project does not establish readiness in another organisation. Assurance work creates value by exposing an unresolved dependency before it becomes a larger investment problem.
Make effectiveness and economic value their own questions
NICE (2022), evidence standards framework provides a separate reference for evaluating digital-health evidence. It distinguishes the evaluation of benefit and value from a claim of NICE endorsement or regulatory approval. For a buyer, the important comparison remains the task and setting in which the technology could be useful. A clear assurance response does not by itself show that people should change their existing workflow.
Include verification, training, support and implementation effort in the commercial account. Staff time released, additional service income and cash savings are different outcomes. An assessment should be able to explain the assumptions required for each. This gives a customer or investor an intelligible reason to continue, narrow the proposal or ask for a stronger comparison before committing further resources.
Bring the requirement that matters to your organisation
Tell us the proposed task, the decision you need to take and which assurance colleagues should be involved. We can discuss the current programme stage, the evidence relevant to that question and whether a scoped next step is practical. Any commissioned review, data access or delivery commitment would be agreed separately. The objective is a transparent path from an interesting capability to the evidence an accountable organisation needs to judge it.
