Digital Medicines and Pharmacy FHIR Payload v3.0.0

ID

S77

Version

3.0.0

Type

Interoperability Standard

Status

Published

Effective Date

Oct 18, 2024

Contracting Vehicle(s)

 

Introduction

The Digital Medicines initiative aims to positively transform the way that 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 Generic FHIR Receiver and supports the following requirements as part of its MVP.

Requirements

ID

Requirement

Level

ID

Requirement

Level

DMPF1

Vaccination Administration

Implement and maintain the vaccination Digital Medicines and Pharmacy FHIR Payload inline with the latest specification version to receive notifications of the administration of vaccinations to a Patient at another Health or Care Organisation.

The following vaccinations to be supported:

  • COVID-19

  • Influenza

  • Pertussis

  • Respiratory Syncytial Virus (RSV)

MUST

DMPF2

Pharmacy Emergency Medication Supply 

Implement and maintain the Pharmacy Emergency Medication Supply Digital Medicines and Pharmacy FHIR Payload inline with the latest specification version to receive notifications of emergency medication(s) supplied to a Patient at a Pharmacy.

MUST

Compliance, Assurance and Testing

Summary of Recommendations

The understanding that clinical risk and assurance responsibilities are formally acknowledged by system Suppliers and based on the knowledge that appropriate functional assurance will be performed by the Solutions Assurance team which is crucial to mitigating many of the clinical risks identified, the following clinical assurance approach is recommended:

  1. Clinical Safety

All system Suppliers will be required to submit the required clinical safety documentation and sign off by their Clinical Safety Officer as per the Authority Clinical Safety Group (CSG) requirements.

  1. 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. 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. 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.

  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. 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. 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

Dependencies

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

Roadmap