MES for pharma: electronic batch records signed step by step

What the module does

• Master batch records per product: code, kind, presentation, standard batch size, version, site and the bill of materials, with steps in phases from weigh and dispense through compounding, transfer to fill-finish, fill-finish, packaging and labelling, or the phases of the client's own outline.
• AI drafting from the client's batch record outline (the paper batch record or an export, the procedure, the bill of materials, specifications, artwork) in the client's wording; it never invents a limit or a code the outline does not give, and returns questions for what is missing.
• Step entries: numbers with units and limits, lot numbers, equipment IDs, yes/no checks with the expected answer, choices, dates and times, attached printouts; critical steps always verified by a second person.
• Execution with credential signatures: the operator saves entries as the work is done and signs Executed with email and password; the signature is refused while a required entry is missing, an earlier step is incomplete, the batch is on hold, or a lot is not among the released, unexpired lots the ERP sent.
• Verification by a second person who signs Verified or returns the step with what must change; every return stays on the record, and a step marked not applicable carries a signed reason. A critical step is never skipped.
• Entries outside their limits flagged at once and never corrected to pass; deviations raised on the batch, tied to the step and naming the investigation that handles them.
• Review by exception: the record lists every exception (entries outside limits, deviations, returned steps, steps not applicable, holds, comments on signed steps, QC samples out of specification) and QA reviews each one, with a written conclusion on those of high severity.
• ERP integration through the API: manufacturing orders in, the production schedule and material consumption per batch and step out, and the released, quarantined, rejected or consumed lots that dispensing accepts.
• Batch release: disposition as approved for release, approved with conditions or rejected; review and release with electronic signatures; the executed batch record exported as a locked PDF, every export logged.

How it fits the platform

A deviation on a batch names its investigation in the quality system, and the batch cannot be released while a flagged entry has no deviation or a deviation has no investigation; release without conditions waits until every investigation the batch raised is closed. In-process and release samples are registered in the LIMS against the specification in force for the product at that stage, linked both ways, and release testing must be approved in the LIMS before the disposition.

With an API key carrying the MES scope, the ERP creates batches from manufacturing orders, reads the schedule and the consumption, and sends the lots on file, so the lot an operator enters for a material is checked against what the ERP has released. A change to the process is a new version of the master; batches already started keep the version they were made from.

Where people decide

The AI drafts the master batch record; the engineer edits every phase, step and entry, and QA approves it with signatures. Operators execute and sign each step, a second person verifies it, and the supervisor can hold and resume the batch. QA reviews each exception, records the disposition with a reason and signs the release; the system flags and refuses, but never dispositions a batch.