Independent research and innovation platform. Not an NHS organisation or NHS-endorsed service.
Medicine Loop Core · fictional workflow, real problem

One medication change. Every affected service aligned.

A hospital has stopped amlodipine. The clinical decision is correct, but the loop is still open because GP, pharmacy and care workflows have not all caught up. CareGrid tracks the change from signed decision to confirmed downstream reconciliation.

Demo patientDEMO-2048Amlodipine 10 mg stopped in hospital1/5 services reconciled
1Authorise
2Notify
3Reconcile
4Acknowledge
5Close
Signed medication changeSource: acute discharge

Amlodipine 10 mg → STOP

Authorised by: hospital prescriber

Reason: fictional adverse-effect review

Effective: today, 14:30

Follow-up: GP medication review within 7 days

Loop still open

4 service workflow(s) still need action. A notification alone is not closure.

Conflict detectedRepeat list owner

GP / PCN

Current local stateAmlodipine 10 mg still active on repeatBefore reconciliation
Required stateRepeat list reconciledAfter authorised change is actioned
Why this matters

The hospital record says STOPPED while this service still has the medicine active. CareGrid shows both sources and requires an accountable reconciliation rather than silently overwriting one with the other.

Accountable next action

Reconcile this workflow

Workflow status

Conflict detected

CareGrid keeps this action visible and owned until the responsible service resolves it.

Closed-loop record

Visibility is not enough. The action has to close.

Every service has its own role and permissions. CareGrid records provenance, ownership, acknowledgement and resolution.

Affected5

Service workflows

Different settings, one medication-change event.
Reconciled1

Confirmed complete

Local workflow now reflects the authorised change.
Conflict1

Unresolved discrepancies

Conflicting medication states remain visible until resolved.
LoopOpen

Overall status

The loop closes only when all required downstream actions are complete.
ChangeSTOP amlodipine 10 mg
SourceHospital discharge
AccountabilityOutstanding actions remain
Silent overwriteNever
Evidence → product → proof

Separate what is already established from what Sitora still has to prove.

The published evidence supports the problem or intervention mechanism. A Sitora pilot must establish the local effect.

Proven already

What existing evidence establishes

An England-wide study covering 1,454 patients and 10,038 medicines across 43 CCGs found that 12.5% of patients still had medicine changes not acted on within 7 days of discharge information arriving. Reasons were documented for only 57% of stopped medicines and 39% of dose changes. A UK randomised trial also found fewer post-discharge discrepancies when community pharmacists received discharge medication information as well as GPs.

What Sitora adds

The product layer

A cross-organisation medication-change event with provenance, an accountable recipient, explicit acknowledgement, visible conflict and a defined closed state across GP, pharmacy, hospital, care-home and community workflows.

Pilot must prove

No assumption allowed

Whether CareGrid reduces unresolved discrepancies and time-to-reconciliation; prevents obsolete or duplicate supply; improves downstream acknowledgement; avoids missed essential medicines; and does so without creating disproportionate workload.

Evidence used in this demo
One medication view. Every change signed. Every service notified. Every action acknowledged. Every loop closed.