Read one manufacturing sample through the MES–LIMS exchange. Seal’s LabWare binding is read-only: it reads approved REST resources through Scripts and does not write to the LIMS. The request, collection and result exchanges below pass between the MES and LabWare; Seal reads and reconciles them. Use one disposable batch/sample in the test environment, with two required tests and known result units. The aim is to establish when a request becomes a collected sample, when results arrive and when those results are eligible for the batch review. Run each transition separately so missing events are visible. FIRST RUN 1. Write down the four events and where Seal reads them With the LabWare owner, identify the approved REST read resources that expose the MES sample request, the returned sample identity, the collection information and the results/status. For every resource, record the fields, success evidence and a supported way to query the outcome. LabWare’s public integration overview does not supply a universal endpoint or authentication recipe. Check: The implementation note names the actual environment and configured resources. It also states which system owns the sample ID, collection record, test assignment and review state. Resolve an unavailable resource before relying on it in the batch workflow. LabWare: Integration Platform: https://www.labware.com/lims/integration LabWare: the sample request, confirmation and result exchange: https://www.labware.com/blog/k%C3%B6rber-and-labware-lead-the-way-with-seamless-mes-lims-integration 2. Link the returned sample to the original request Have the MES raise one request for B-820 in the test environment. Read REQ-820 as the originating request identity and the returned LabWare sample identity as LW-S820 in this fictional example. Capture the assigned test list and the source evidence for the association. Check: A second lookup of REQ-820 resolves to the same intended sample. If the MES loses the first response, establish whether that sample already exists before it creates another one. A matching batch name alone is not enough when several samples are planned. 3. Record collection as its own event Record the test collection and its source time, location and collector in the MES using the agreed workflow. Read the resulting collection confirmation and connect it to LW-S820. Retain request time, collection time and laboratory receipt time as different fields when all are needed. Check: The receiving record can identify the physical collection represented by COL-820. Temporarily omit the confirmation in a test copy: the sample identity may still be present, but the batch review must show the missing collection evidence. LabWare: the sample request, confirmation and result exchange: https://www.labware.com/blog/k%C3%B6rber-and-labware-lead-the-way-with-seamless-mes-lims-integration 4. Compare result identity, units and review eligibility Read the two worked results below. Confirm the destination field definitions before conversion: on an unchanged sample basis, g/L to mg/L multiplies the number by 1000. Separately map the actual LabWare review-state codes to the states used in Seal’s review view. Check: The glucose comparison is 1200 mg/L and lactate is 800 mg/L. Both original values remain available. The review has two received values but only one approved result; a unit conversion must not change that count. 5. Receive a status update without inventing a new measurement Complete the lactate review through the authorised laboratory workflow in the test environment, then retrieve the updated source evidence. The expected update concerns the existing LAC result. Capture a source revision or observation time so the change can be explained. Check: The proposed review moves from one to two eligible results while preserving the same two measurement identities and their values. A later status observation is not a third laboratory measurement, and laboratory approval alone does not automatically dispose the manufacturing batch. LabWare: lot management and review: https://www.labware.com/lims/self-hosted Define what each exchange proves Use this checklist to inspect the configured interface with its owner. The field labels are proposed mapping concepts; substitute the actual LabWare schema and state codes. Exchange: Sample request acknowledgement Evidence to retain: Originating request, returned sample, batch and assigned tests Conclusion it supports: The request is associated with the intended laboratory work; collection is still a separate fact. Exchange: Collection confirmation Evidence to retain: Sample identity, collection event and time, relevant location and collector Conclusion it supports: The identified sample was collected under the agreed workflow. Exchange: Numeric or qualified result Evidence to retain: Test/result instance, original text, unit, sample basis and source revision Conclusion it supports: The selected measurement was received. Text such as <0.05 retains its qualifier; it is not converted into an exact 0.05. Exchange: Review-state update Evidence to retain: Result identity, source state and source observation/revision Conclusion it supports: The result has reached the mapped review state. An unknown code remains unresolved. Exchange: Lot disposition or report Evidence to retain: Lot identity, disposition/report reference and applicable state Conclusion it supports: A separately identified lot or report decision exists; result arrival is not that decision. LabWare: the sample request, confirmation and result exchange: https://www.labware.com/blog/k%C3%B6rber-and-labware-lead-the-way-with-seamless-mes-lims-integration LabWare: lot management and review: https://www.labware.com/lims/self-hosted A four-event specimen for B-820 Fictional event worksheet for discussing the configured mapping. Empty cells mean the field is not supplied by that event. This is not a default LabWare export or a sequence of vendor API commands. event,request,sample,collection,test,result,value,unit,review request_ack,REQ-820,LW-S820,,,,,, collection,REQ-820,LW-S820,COL-820,,,,, result,REQ-820,LW-S820,,GLU,LW-R820G,1.20,g/L,Approved result,REQ-820,LW-S820,,LAC,LW-R820L,0.80,g/L,Awaiting review The expected population is one originating request, one laboratory sample, one collection event and two result instances. The first event establishes identity, the second establishes collection and the last two carry measurements. Counting four events as four samples or four scientific results would be incorrect. PROPOSED RECEIVING CHECKS—NOT EXECUTED CUSTOMER VALIDATION Receive results before collection evidence Input: Read the two result events while the collection confirmation is absent, then read COL-820 later. Expected: The values remain linked to LW-S820. The missing collection evidence is visible until COL-820 arrives; adding it does not create another sample or another result. Read the same result versions twice Input: Read the identical GLU and LAC source result versions a second time. Expected: The receiving view still has two scientific results and can trace both reads. The expected-test population remains two. Change review state only Input: Provide a later source observation that approves LW-R820L without changing 0.80 g/L. Expected: The eligibility count changes from one of two to two of two. The original quantity, comparison quantity and result identity stay intact, with the review update traceable. Read a qualified value or unknown status Input: In separate test copies, replace the result text with <0.05 g/L, or use a source review code not yet in the mapping. Expected: The qualified quantity retains its less-than meaning; any converted representation is <50 mg/L on the same basis. The unmapped status does not become Approved. Each exception identifies the affected result. HANDOFF Bring response specimens for all four events, the sample-to-request association, assigned tests, destination unit definitions and the approved source-status mapping. Seal can then make missing collection, missing testing and pending review separate, actionable items in a batch evidence review.