How S3 supply records and history work

An S3 encounter records a purchaser, a selected product, the date and the outcome. Supplies, refusals and other outcomes appear together in the recording history.

Separate from customer services

S3 Supply Recording has its own purchaser records and encounters. Recording an S3 encounter does not require an existing customer profile and does not create a row in Customers or Services.

The Encounters tab contains records created at the current site. It is the place to find and correct an individual S3 record. These records remain separate even when the purchaser also has a customer profile in Light.

Two stages of purchaser matching

The identification lookup can recall a purchaser's name and address when that identification has already been used for an encounter at the current site. This prefill saves re-entering familiar details. It does not search other sites for purchaser details from an ID alone.

The subsequent Look Up Person search uses the identification type and number together with the purchaser's name and address. Matching details can bring together encounters from other sites using Light/Checkpoint.

This depends on the details supplied. A different ID document, changed address or misspelt name can leave earlier records unmatched. An empty history therefore means no matching encounters were found – it does not establish that the purchaser has never obtained the product before.

What shared history includes

The purchaser-history panel shows matching encounters held in Light/Checkpoint, including the product, date, recording site, supplier and outcome. It can include sites in other jurisdictions. Its scope is the records available in Light/Checkpoint; it is not a complete history of purchases at every pharmacy.

This history appears during purchaser lookup on the new-record page. Opening a saved encounter instead opens that site's individual record for editing.

Corrections and retained records

Saved encounters can be edited or deleted from the site's encounters list. Editing can change the supply details and outcome, while the purchaser remains fixed. Deletion removes an encounter from the normal history views and retains the deletion reason, time and person who deleted it.

The available actions and limits are covered in Correcting an S3 record.