Make neighbourhood care work across organisations.
Connect NHS teams and community providers to coordinate care, manage regional networks and reduce administration.
| PATIENT | NEXT TASK | CARE PLANS |
|---|
Example data for illustration · Real access depends on Workspace and user permissions.
REGIONAL NETWORK
Network performance
Actual activity against agreed network targets
For a community worker
See the visit. Do the work. Report back.
The worker sees only their assigned activities and relevant information. A visit update or reported change reaches the appropriate coordination workflow, without another round of calls and spreadsheets.
Mary Wilson · Home wellbeing visit
Assigned by community coordinator
Check wellbeing, confirm support and report any change.
Open visitSupport delivered · Follow-up call requested
Ready for reviewThe work that needs fixing
Three problems. One connected way to work.
Care crosses organisational boundaries. The work, responsibility and information often do not. Freddie Med connects the daily work with the network that delivers it.
Keep responsibility clear between services.
Hospitals, GPs, community teams and charities can coordinate referrals, accepted responsibilities, tasks and follow-up without losing track of who does what.
Know who owns the next action.Help people deliver care, not chase updates.
Coordinators manage work from one desktop view. Frontline workers see assigned activities on mobile and report what happened in a few steps.
Less duplication and fewer status enquiries.Make community networks visible and manageable.
ICBs and LIOs use appropriate network-level views to understand participating providers, service coverage, delivery activity and gaps in support.
Better network management without more reporting work.Regional voluntary, community and social enterprise (VCSE) networks
Spot what is slowing the network down. Improve it.
As participating services record visits, referrals and follow-up, Freddie Med brings that activity into one current operational view. ICBs and local infrastructure organisations (LIOs) compare performance with agreed targets, find where work is getting stuck and support the organisations that need attention.
Compare operational results with shared targets and identify where commissioning or service improvement attention is needed.
Illustrative regional VCSE network · Example reporting period| MEASURE | TARGET | ACTUAL | STATUS |
|---|---|---|---|
| Care plan actions completed on time Share completed by agreed due date | 80% | 75% | Review |
| Referral to first contact Median days from accepted referral | ≤ 3 days | 2.4 days | On track |
| Workspaces with no activity Last 30 days | 0 | 6 | At risk |
| Overdue actions across the network Outstanding past agreed date | ≤ 100 | 951 | At risk |
| Unmet patient needs flagged Needs without an assigned service | ≤ 50 | 142 | At risk |
| Estimated coverage Of the defined eligible population | ≥ 65% | 58% | Review |
| WORKSPACE | ON TIME | OVERDUE | LAST ACTIVITY | STATUS |
|---|---|---|---|---|
| 38% | 29 | 18 days ago | At risk | |
| 47% | 26 | 12 days ago | At risk | |
| 69% | 15 | 3 days ago | Review | |
| 91% | 2 | Today | On track |
ICBs oversee priorities and targets; LIOs, including councils for voluntary service (CVSs), support participation, service coverage and improvements with providers. Views are permissioned and use appropriate network aggregates—not unrestricted access to individual patient records.
How it works
From referral to delivered support.
An ordinary care journey connects the referrer, receiving organisation, coordinator and community worker. The same work provides the network with appropriate information about delivery.
The patient is part of the care team
Keep patients and authorised carers involved.
Through the Patient Portal, patients and their authorised proxies can see relevant care information, follow their care plans and stay involved in decisions and follow-up. The same coordinated care, not a separate process.
Care plan · Home support, wellbeing and follow-up
For your organisation
Different responsibilities. Connected work.
Each participant gets a view designed for their job. Network management never means unrestricted access to another organisation's patient records.
Easy to introduce
Work with the systems you already have.
Freddie Med works alongside the clinical systems organisations already use. It also provides clinical care capabilities for teams that choose to use Freddie Med directly.
Bring together the coordinator and providers already involved in frailty, discharge support or another shared service.
Desktop tools for coordinators, simple mobile work for community staff, and appropriate oversight for regional managers.
Existing systems retain their authority where they remain in use. Document workflows and authorised interfaces support information exchange under each organisation's arrangements.
A basic professional account is free forever. Collaboration for teams and organisations extends the individual account.
How Freddie Med fits
What makes it work
One architecture across independent organisations.
The system supports cross-organisation work while keeping identity, access, patient information and organisational responsibility governed separately.
Independent Workspaces and governed access
Each organisation retains its own Workspace. Identity, care relationships and role-specific permissions control what people can see and do.
AI for routine administration
Source-linked document intake helps prepare information for review. People verify, correct and authorise consequential actions; AI does not act independently as a clinician.
Patient and carer access
The Patient Portal gives patients and their authorised carers a view of relevant care information, plans and follow-up, with appropriate controls on sharing.
Clinical care, built in.
Freddie Med includes clinical records, documentation, care plans and clinician-led workflows. Practices, community services and hospital teams can use these capabilities directly while staying connected to care beyond their own organisation.
NHS integration and data standards
Freddie Med uses a structured clinical data model and API-based boundaries. Its interoperability approach uses FHIR R4 and UK Core mapping, SNOMED CT terminology, UK dm+d medication coding and governed external patient identifiers. Specific NHS connections are established through approved interfaces and individual integration and assurance agreements; standards alignment does not itself constitute an NHS connection.
How AI permissions work
AI suggestions remain separate from the authority to accept, authorise or execute an action. The IAM architecture distinguishes identity, Workspace, role, resource permissions and the human review needed for consequential changes. Agents do not independently obtain clinical authority.
How organisations retain control
Organisations participate through their own Workspaces. The network-level patient record and Care Plans support appropriately authorised collaboration without automatically exposing information to every network participant. Network managers work with governed aggregate information rather than unrestricted clinical records.
From Systems to Networks: Governing Community Care in the NHS
An essay by Daniel Klusmann on why effective community care depends on the connections between independent organisations, not just the systems within them.
Bring your network together
Tell us which care pathway or regional network you need to connect.
Start with the NHS teams, community providers and VCSE organisations already delivering the service. We'll discuss how Freddie Med fits the work and existing systems.
Want to use Freddie Med?
Register your interest in professional access or participation in a care or regional network. No pricing commitment is required.
Join the waiting list to register your interest. Newsletter updates are optional.