Connector Details
Type
Virtual machines, Single VM , BYOL
Runs on
Google Compute Engine
Last Update
24 October, 2024
Category
NHS OpenPrescribing
Connector Details
Type
Virtual machines, Single VM , BYOL
Runs on
Google Compute Engine
Last Update
24 October, 2024
Category
Overview
The NHS OpenPrescribing Connector facilitates seamless integration with the OpenPrescribing API, providing access to prescribing spending data and related information for the NHS in England. This includes total spending, quantity, items, drug details, organization codes, list sizes, ASTRO-PUs, and geographical boundaries specific to NHS England’s healthcare system. The connector acts as a proxy to streamline data retrieval, supporting actions for spending by code, spending by organization, drug details, organization codes, list size and ASTRO-PUs, and location data. Tailored for Google Cloud Platform (GCP), this connector enables efficient data processing and analysis for UK healthcare data.
Integration Overview
This document provides a detailed guide for each integration point, its purpose, configuration, and workflow support using the NHS OpenPrescribing Connector on GCP. The connector simplifies access to prescribing data, enabling applications to retrieve spending, drug, and organizational information for analytics, reporting, or academic research. Data can be retrieved in CSV or JSON format by appending &format=csv or &format=json to the URL. For academic use, please cite: OpenPrescribing.net, Bennett Institute for Applied Data Science, University of Oxford, 2025.
Supported Integration Action Points
Detailed Integration Documentation
Spending by Code Retrieval
Action | getSpendingByCode |
Purpose | Retrieves a comprehensive list of total prescribing spending, quantity, and items by month for specified BNF codes over the last five years. This serves as the primary entry point for accessing aggregated prescribing data. |
Parameters |
|
Configuration | Ensure the connector is configured with the base URL via CONNECTOR_ENV_OPENPRESCRIBING_BASE_URL environment variable set to https://openprescribing.net/api/1.0. Deploy on GCP using Cloud Functions or App Engine, and configure the environment variable in the GCP Console. |
Output |
JSON array of objects with:
|
Workflow Example |
|
Spending by Organization Retrieval
Action | getSpendingByOrg |
Purpose | Retrieves spending and items by organization (Sub-ICB Location, practice, PCN, ICB, or Regional Team) by month over the last five years. Helps users obtain targeted organizational prescribing data for analysis. |
Parameters |
|
Configuration | Ensure the connector is configured with the base URL via CONNECTOR_ENV_OPENPRESCRIBING_BASE_URL. Use GCP Secret Manager to securely store sensitive parameters if needed. Deploy on GCP Cloud Run for scalability. |
Output |
JSON array of objects with:
|
Workflow Example |
|
Drug Details Retrieval
Action | getBnfCode |
Purpose | Searches for BNF sections, chemicals, or presentations by name or code (case-insensitive). Allows tailored searches for drug information to support prescribing analysis. |
Parameters |
|
Configuration | Configure the connector with the base URL via CONNECTOR_ENV_OPENPRESCRIBING_BASE_URL. Deploy on GCP App Engine for reliable API access. |
Output |
JSON array of objects with:
|
Workflow Example |
|
Organization Codes Retrieval
Action | getOrgCode |
Purpose | Searches for Sub-ICB Locations or practices by code or name. Helps users validate organization codes or build selection interfaces for applications. |
Parameters |
|
Configuration | Configure the connector with the base URL via CONNECTOR_ENV_OPENPRESCRIBING_BASE_URL. Use GCP Cloud Functions for serverless execution. |
Output |
JSON array of objects with:
|
Workflow Example |
|
2.5 List Size and ASTRO-PUs Retrieval
Action | getOrgDetails |
Purpose | Retrieves list size or ASTRO-PU details for Sub-ICB Locations or practices by code or name for all available months. This enables detailed organizational metrics for analysis. |
Parameters |
|
Configuration | Configure the connector with the base URL via CONNECTOR_ENV_OPENPRESCRIBING_BASE_URL. Deploy on GCP Cloud Run for scalability and use Secret Manager for secure parameter storage. |
Output |
|
Workflow Example |
|
2.6 Location Data Retrieval
Action | getOrgLocation |
Purpose | Retrieves GeoJSON boundaries for Sub-ICB Locations or approximate locations for practices. This enables geographical integration for mapping or visualization in GCP-hosted applications. |
Parameters |
|
Configuration | Configure the connector with the base URL via CONNECTOR_ENV_OPENPRESCRIBING_BASE_URL. Deploy on GCP Cloud Functions and integrate with Google Maps API for visualization. |
Output |
|
Workflow Example |
|
Workflow Creation with the Connector
Example Workflow: Prescribing Spending and Organizational Analysis
Retrieve Drug Details |
|
Query Spending by Code |
|
Perform Spending by Organization |
|
Explore Organizational Details |
|
Enhance with Location Data |
|
Assumptions Made
Pricing
iSolution logo - white - transparent 250 px
Register To Palo Alto & iSolution Event
[forminator_form id=”14485″]
[forminator_form id=”14419″]
[forminator_form id=”14298″]
[forminator_form id=”13094″]