Use casesHigh-stakes industries

Clinical trial supply deviation review

Coordinate shipment exceptions, site impact and quality review with a traceable decision record.

Example coordination workflow only. It is not a validated GxP system and does not make product-release decisions.

  1. In transit
  2. Exception raised
  3. Evidence gathered
  4. Quality reviewApproval
  5. Decision recordedApproval
  6. Follow-up closedDone
PassedWaits for a personEvery move is kept in the record's history

The problem

What goes wrong today

Today
A shipment temperature alert or site delivery exception can involve a batch, several trial sites and multiple teams. Operations need to gather the evidence, understand what is affected and route a documented decision to the right reviewers.
Who feels it: Clinical supply operations, quality teams and distribution coordinators

How It Works

How this use case runs, step by step

Amber steps wait for a person's decision; everything else moves on its own.

  1. An exception is receivedA coordinator records a shipment alert and links it to the batch, destination site and available evidence.
  2. Site impact is checkedOperations records which sites and kits may be affected and assigns each follow-up check.
  3. Evidence is assembledCarrier documents and event readings are linked to a single exception record.
  4. Quality reviews the case Quality reviewThe assigned reviewer records a decision under the organisation’s own validated procedure.
  5. Follow-up is visibleA queue and report show the decision, owner and remaining actions for the supply team.
The organisation and people are invented.

Product Capabilities

What you configure in this app

Mostly configuration. Rules that configuration cannot express are written in C#.

Records 5

  • Shipment4 fields + history, files, comments
  • Trial supply batch4 fields + history, files, comments
  • Temperature event4 fields + history, files, comments
  • Site impact review3 fields + history, files, comments
  • Quality decision4 fields + history, files, comments

Stages 6

  1. In transit
  2. Exception raised
  3. Evidence gathered
  4. Quality reviewdecides
  5. Decision recordeddecides
  6. Follow-up closed

Automatic 3

  • NotifyA shipment exception opens a review and notifies supply operations and quality
  • WorkflowUnassigned site-impact checks are added to the operations work queue
  • ScheduleA daily report lists open shipment exceptions by age, batch and destination

Screens and reports 5

  • Shipment exception queue with batch, site and current review owner
  • Evidence form linked to event readings and carrier documents
  • Site impact and quality decision review with comment history
  • Open shipment exceptions and outstanding site checks
  • Internal review pack linking event evidence to recorded decisions
Who approves, in detail

Supply operations gathers the shipment evidence and site impact. A quality reviewer records the decision and any follow-up. The page shows coordination only; the organisation’s validated procedures govern the regulated record and release decision.

When the rules change

See TechAppForce on your own use case

Bring your own version of “Clinical trial supply deviation review” and we will model its records, stages and approvals with you. A change a few months in is a reviewed release, not a rebuild.

Release: Shipment: exception review

Evidence
Added: + Event reading and timestamp
Added: + Carrier documents linked
Site impact
Unchanged: Destination site check
Added: + Quality decision and follow-up
  1. Developmentmake the change
  2. QAreview the diff, test it
  3. Productionpromote the release