Read one sample’s data items and match them on full identity. Seal’s LabVantage binding is read-only: it issues GET requests to approved REST web services and does not write to the LIMS. Use a test sample with one parameter list, two replicates and, if practical, a second dataset. The aim is a read whose values your Script places on the right data item every time. FIRST RUN 1. Obtain the web-service contract With the LabVantage owner, identify the installed release, the REST service that returns the intended data items and a read-only service account. Confirm the authentication header it needs: Authorization, X-API-Key or apikey. SOAP, cookies, multiple headers and request signing need an approved gateway or additional native support. Check: The contract names the resource path and the fields it returns, including the identity fields in the map below. Do not substitute a guessed /samples endpoint or a direct database query. LabVantage: LIMS web services and business logic: https://www.labvantage.com/a-quick-guide-to-lims-web-services/ 2. Connect and test in Seal Open Settings → Integrations → LabVantage. Enter the narrowest approved HTTPS API prefix and a relative test resource path, then choose Test and connect. Select the resources the Script needs and grant its Seal API key access. Check: The test issues a GET and requires a bounded JSON object or array. Choose a test resource that reveals no unintended laboratory data. A successful test shows connectivity and readable JSON, not analytical correctness. 3. Compare the returned identities with LabVantage Read the resource for LV-S910 in a Script with integrations.get and inspect fields.response. Compare each value with the LIMS view: record keys, parameter list, version, variant, dataset, parameter, type and replicate. Check: Every value can be placed on exactly one data item. If the response lacks dataset or replicate, stop and ask for a contract that returns them rather than matching on sample and analyte. LabVantage: data-item qualifying properties (EnterDataItem reference): https://vantagecare.labvantage.com/labvantagedoc/Content/actions/sapphire/action/EnterDataItem.html 4. Record status and unit with each value Confirm whether the service returns draft, authorised or corrected values, and which custom fields it exposes. Record the unit configured for the measurement with the LabVantage owner. Check: The Script stores the returned status beside each value. Seal does not interpret laboratory approval, so an unfamiliar status stays visible instead of being mapped to Approved. LabVantage: sample lifecycle and review: https://www.labvantage.com/services/customer-success/training/end-user-lims-training-course-syllabus/ 5. Read every page before counting results The complete response, including any pagination envelope, is in fields.response. The binding does not follow pagination or fetch linked records, so the Script must request each page the contract describes. Check: The number of data items in Seal matches the LIMS for the test sample. A partial page is not treated as a missing result, and a JSON response carrying an application error is not treated as data. Decide what each read outcome means These are proposed decisions for the worked sample. Seal’s version for each read is a content hash and its time is the read time; neither is a LIMS revision or approval. Read evidence: Same value on the exact data item as the last read Decision: Keep the existing Seal result Recorded outcome: Unchanged; the read is another observation. Read evidence: Different value on the exact data item Decision: Record the change against the same identity Recorded outcome: Changed, with both values and read times kept for review. Read evidence: Value on a new dataset Decision: Create a separate result Recorded outcome: A remeasurement, not a correction to the earlier dataset. Read evidence: Value with incomplete identity Decision: Do not match on sample and analyte alone Recorded outcome: Unresolved until the service returns the full identity. Read evidence: Read fails or returns something other than JSON Decision: Do not treat it as an empty result Recorded outcome: Failed read. The binding never returns an older capture as current data. LabVantage: LIMS web services and business logic: https://www.labvantage.com/a-quick-guide-to-lims-web-services/ Three glucose data items for one sample Fictional worksheet using the documented identity concepts. The shared test definition is GLUCOSE, version 3, variant Routine, parameter Glucose, type Standard; the confirmed unit is mg/L. These are not the output of a live LabVantage read. sample,dataset,replicate,value,unit LV-S910,1,1,1200,mg/L LV-S910,1,2,1190,mg/L LV-S910,2,1,1180,mg/L Three values, three data items. Two are replicates in dataset 1; the third is a remeasurement in dataset 2. A match on sample and parameter alone would find three candidates for each row. PROPOSED RECEIVING CHECKS, NOT EXECUTED CUSTOMER VALIDATION Read the same resource twice Input: Repeat the read with no change in LabVantage. Expected: Seal still holds three results. The second read is recorded as another observation and creates nothing new. Correct one value in the source Input: In the test system, correct dataset 1, replicate 2 from 1190 to 1185 mg/L through the normal laboratory workflow, then read again. Expected: The same Seal result records the change from 1190 to 1185 with both read times. There is no fourth result. Remove the replicate field Input: In a saved test response, remove replicateid from the dataset 1 values. Expected: The Script leaves both values unresolved instead of matching them on sample and analyte, and names the missing field. Return an unmapped status Input: Use a status code in a test response that the mapping does not yet recognise. Expected: The value keeps the source status and stays out of any approved count until the source owner defines it. HANDOFF Provide the web-service contract, the identity map, the configured unit and status codes, and the comparison between the LIMS view and the Script’s read. Seal can then keep each LabVantage value on its own data item, with a source link Neil can cite.