Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated to v2.1.0
Page Properties

ID

S77

Version

2.1.0

.1

Type

Interoperability Standard

Status

Effective

Effective Date

11 Apr

 
Excerpt
hiddentrue

Supports sharing of data held within GP IT solutions across health and social care organisations.

Table of Contents
minLevel1
maxLevel1
outlinefalse
typelist
printablefalse

Introduction

The Digital Medicines initiative aims to positively transform the way that

Patients manage

Patients manage their medicines, promote new models of care as well as improve the medicines supply chain and the provision of medicines data. At a high-level, this all involves the adoption of digital prescriptions to replace inefficient and cumbersome paper versions, utilising appropriate technologies to fully engage in the end-to-end Patient pathway, alongside supporting the adoption of technology to deliver a fully digitised medicines supply chain. 

The Digital Medicines Specification utilises

the 

the Generic FHIR Receiver and supports the following requirements as part of its MVP.

Requirements

ID

Requirement

Level

DMPF1

Pharmacy Immunisation Administration

A FHIR Document used to notify a

Patient’s registered

Patient’s registered GP Practice on the administration of immunisations to a Patient at a Pharmacy.

Status
colourRed
titleMUST

DMPF2

Pharmacy Emergency Medication Supply 

A FHIR Document used to notify a

Patient’s registered

Patient’s registered GP Practice of emergency medication(s) supplied

to a Patient at a Pharmacy.
Status
colourRed
titleMUST
DMPF3

Pharmacy Minor Illnesses

A FHIR Document used

to

notify

a

Patient’s registered GP Practice of a minor illness consultation a

Patient

has received

at a Pharmacy.

Status
colourRed
titleMUST

Compliance, Assurance and Testing

Summary of Recommendations

The understanding that clinical risk and assurance responsibilities are formally acknowledged by system

Suppliers and

Suppliers and based on the knowledge that appropriate functional assurance will be performed by the

NHS Digital

Solutions Assurance team which is crucial to mitigating many of the clinical risks identified,

 the

 the following clinical assurance approach is recommended:

1. Clinical
  1. Clinical Safety

All system

Suppliers will

Suppliers will be required to submit the required clinical safety documentation and sign off by their Clinical Safety Officer as per the

NHS Digital

Authority Clinical Safety Group (CSG) requirements

2.

 Test

 Test in Test

A Digital Medicines clinician will, in the test environment via Webex, witness test the following scenarios to ensure the systems are behaving as expected from a clinical perspective. The scenarios covered will be:

a.
  1. The end to end process including the recording of a Patient consultation for a flu vaccination, where a vaccination has been administered and the subsequent transfer of that information to a GP Practice where it is acted upon.

b.
  1. The end to end process including the recording of a NUMSAS consultation for a Patient where a supply is made, the subsequent transfer of that information to a GP Practice where it is acted upon.

3.
  1. Test in Live

Using test Patients, a Digital Medicines clinician will, in the live environment via Webex or in person, witness test the following scenarios to ensure the systems are behaving as expected from a clinical perspective. The scenarios covered will be:

a.
  1. The end to end process including the recording of a Patient consultation for a flu vaccination, where a vaccination has been administered and the subsequent transfer of that information to a GP Practice where it is acted upon.

b.
  1. The end to end process including the recording of a NUMSAS consultation for a Patient where a supply is made, the subsequent transfer of that information to a GP Practice where it is acted upon.

The focus of the witness testing will be on the user workflow ensuring the positive and negative messages are prominent to the user and to provide a “sense check” of the PDF transformation of the message received by the GP system.

Documentation

The latest version of Digital Medicines specifications can be accessed here: https://digital.nhs.uk/developer/api-catalogue/digital-medicine-fhir  (Reference links: https://developer.nhs.uk/apis/). 

The  and

 and details the information that should be recorded for vaccinations administered and emergency medicines supplied by community pharmacists.

The MVP states that

Suppliers are

Suppliers are expected to process the unstructured messages upon entry to the framework in order to compliantly implement any use cases. However, there will be a future requirement for

Suppliers to

Suppliers to further enhance their

Solutions to

Solutions to ensure the messages are processed in a structured format.

Dependencies

Creating a compliant implementation requires implementing the following dependent interface standards:

Roadmap

Page Properties Report
firstcolumnRoadmap Item
headingsStandards and Capabilities, Status, Effective Date, Description, Change Type, Change Route
pageSize300
sortByEffective Date
cqllabel = "s77" and space in ( currentSpace ( ) , "DCSDR" , "DCSDCS" )