Building healthcare software - prescriptions
A non-technical guide to building software that deals with prescriptions within the NHS in England.
This guide is a work in progress
To tell us what you think, please use the feedback widget or contact us.
Overview
This guide explains how to build software that deals with prescriptions within the NHS in England.
It is a non-technical guide, aimed at people building healthcare software, including:
- product owners
- architects
- business analysts
- delivery managers
- software engineers
It covers the following topics:
- what prescriptions are
- the end-to-end business process
- integration and APIs
- the software delivery process
- getting started
This guide is part of our series of domain-specific guides on building healthcare software.
For more context, also see our introduction to healthcare technology.
Prescriptions
This guide is under construction.
In the meantime, see our Electronic Prescription Service (EPS) prescribing developer guide.
End-to-end business process
This guide is under construction.
In the meantime, see our Electronic Prescription Service (EPS) prescribing developer guide.
Integration and APIs
This guide is under construction.
In the meantime, see our Electronic Prescription Service (EPS) prescribing developer guide.
The software delivery process
How you deliver your software is up to you. But there are some important things you need to plan in when building software for the NHS in England, such as clinical safety, security and information governance.
For more details, read our introduction to healthcare technology.
Getting started
To get started with building your software and using our API services and standards, see getting started.
Last edited: 16 December 2022 1:51 pm