One shortage coordination record
Context, ownership and history together.
Source and update dateVisible
Current operational ownerAssigned
Due state and follow-upTrackable
Shared activity historyReviewable
For GP, pharmacy and medicines optimisation teams
Give every medicine-shortage signal a clear owner and next step.
Prosper Shortage Manager gives authorised GP, pharmacy, specialist and medicines-optimisation teams a shared, non-patient operational workflow for dated source context, ownership, follow-up and operational closure.
Timestamped source context
Role-based ownership
Shared non-patient history
The local execution gap
The information exists. The shared record often does not.
Official intelligence and professional judgement remain essential. Local teams still need to see what was checked, who owns the next step and what remains unresolved.
Supplier emailSource update received
Pharmacy callAvailability context shared
Team spreadsheetFollow-up noted locally
- Keep source context, ownership and follow-up in one operational record.
- Make current ownership visible across authorised participating teams.
- Give system leads a clearer view of unresolved operational pressure.
Five product views
See the Medication Shortage Hub in action
Explore five real product screens covering the case journey, local availability, frontline decisions and system oversight.
6 product screens rotate automatically. Use the previous and next buttons, the slide buttons, or the left and right arrow keys to change screen. Use pause to stop automatic rotation.
Captured from the authenticated test environment using synthetic operational data. Select any screen to open the complete product view.
Built for shortage coordination
More than a list. A working view of the response.
Each record keeps the medicine signal, dated context, operational owner and follow-up history connected.
Operational response in progress
Last context update and source date remain visible.
SignalAvailability context updatedMedicine and service context only
ProvenanceSupplier update recordedSource label and date preserved
OwnershipGP practice follow-upCurrent role and due state visible
HistoryThree operational eventsReviewable across authorised teams
Capture the signal with its context
Record the medicine, operational status, source, provenance and update date without creating a patient record.
Coordinate the next operational step
Keep the current owner, due state, hand-off and communication history visible instead of restarting the story.
Review pressure and evidence
See unresolved ageing, source freshness and audit history through role-appropriate operational views.
One workflow, different views
Built around the people doing the work.
Frontline teams start with what they can act on. Medicines optimisation leaders see the exceptions and evidence needed to manage the service.
Likely evaluation sponsor
Medicines optimisation lead or chief pharmacist
Community pharmacy
Keep the signal current.
Update once. Make the next hand-off clear.
Review focused medicines, add a time-stamped availability signal and return to unresolved work without recreating the context.
GP practice and PCN
See what needs your team.
Start with assigned operational follow-up.
See medicine context, source date, current owner and due state together, without patient-identifiable information.
ICB and system leads
Manage the exceptions.
Prioritise aged and unresolved coordination.
Review cross-organisation activity, source freshness and recurring operational pressure rather than inspecting every row.
Digital and transformation
Information governance and security
Commissioning and procurement
Evidence before scale
A bounded way to prove—or reject—the fit.
An evaluation should test whether the workflow improves operational clarity without adding avoidable burden. It should not start with a promise of savings.
The structure below is an example 12-week evaluation path. Measures and approval gates must be agreed with each participating organisation.
- Weeks 1–2
Baseline and scope
Choose the use case, teams, definitions, baseline and stop/continue criteria.
- Weeks 3–4
Configure and prepare
Confirm roles, access, guidance, onboarding and the no-patient-data boundary.
- Weeks 5–10
Run and review
Use the bounded workflow, monitor adoption and resolve operating-model issues.
- Weeks 11–12
Report and decide
Review evidence, burden and gaps, then make a documented go, change or stop decision.
Clear public scope
Coordinate the work without creating a patient record.
This overview describes the generic, non-patient-specific shortage information and coordination workflow only.
Within the described workflow
- Dated shortage and availability source context.
- Generic operational status, ownership and follow-up.
- Role-based access, provenance and audit history.
- Aggregated non-patient operational reporting.
Outside this public scope
- Patient records, identifiers or named-patient cases, tasks and messages.
- Patient-specific alternatives, clinical ranking, dose calculation or AI-generated clinical output.
- Prescribing or dispensing instructions, diagnosis, triage or automatic substitution.
- Patient-record matching, reading or writing through EPR, PDS, GP Connect, IM1 or FHIR.
Available nowProduct demo
Review the role views and workflow using synthetic non-patient information.
Organisation decisionControlled evaluation
Subject to local review, agreed scope, governance and authorised access.
Not represented hereClinical decision modules
Alternative review and cost-comparison functions sit outside this public overview.
Start with workflow fit
Bring one current shortage workflow. Leave with a clearer pilot-fit map.
Use a synthetic non-patient example to explore the product, map your hand-offs and decide whether a bounded evaluation is worth taking further.
Do not include patient information in booking or registration forms.