.png)
LabVantage Integration Guide
LabVantage LIMS can be integrated with enterprise systems through deployment-specific APIs, web services, callbacks, files, and approved database or reporting interfaces.
LabVantage integration options at a glance
LabVantage integration capabilities vary by version, licensed modules, deployment architecture, and customer configuration. A target environment may expose REST or SOAP services, outbound notifications, structured file exchanges, or read-only database and reporting access, but these mechanisms require confirmation with the LabVantage administrator. Martini can consume approved REST or SOAP interfaces, receive callback-style requests, schedule polling workflows, transform JSON or XML, validate Samples, Tests, and Results, and route data to enterprise applications. Where files are approved, Martini can orchestrate controlled imports and exports. Credentials and connection details can be stored in Martini secrets and environment configuration while workflows provide monitoring, retries, and duplicate prevention.
| Integration point | Supported by LabVantage? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Not confirmed | A deployment may expose services for Samples, Tests, Results, or other laboratory objects. Confirm the API catalog, version, licensing, and pagination behavior with LabVantage. | Martini can consume confirmed REST endpoints, transform JSON, validate data, apply business rules, and expose a normalized API to downstream systems. |
| SOAP APIs | Not confirmed | Existing customer integrations may use vendor-provided web services for laboratory transactions, although current SOAP availability and recommendation were not publicly verified. | Martini can consume confirmed SOAP services, map XML payloads, handle service faults, and orchestrate the response into enterprise workflows. |
| Webhooks / outbound callbacks | Not confirmed | Notifications or outbound integration services may exist for selected processes, but no general-purpose LabVantage webhook catalog was verified. | If callbacks are enabled, Martini can expose an API endpoint, receive the notification, retrieve the current object when possible, and trigger a workflow. |
| Bulk / async / batch APIs | Not confirmed | Batch processing may be available through configured services or files, but a public bulk API specification was not found. | Martini can schedule controlled batches, partition payloads, track correlation identifiers, and handle partial failures when the deployment provides a supported interface. |
| File / attachment APIs | Not confirmed | Laboratory and instrument exchanges may use CSV, XML, spreadsheets, SFTP, or other files, but formats and attachment endpoints require confirmation. | Martini can orchestrate approved file flows, parse supported formats, validate content, map laboratory data, and record processing outcomes. |
| Database / analytics access | Not confirmed | Self-managed deployments may permit read-only reporting or database access. Direct application-table writes should not be assumed to be supported. | Martini can use approved JDBC or reporting access for controlled reads, with schema, engine, permissions, and vendor support policy confirmed first. |
| Authentication | Not confirmed | Potential mechanisms include Basic or username-password authentication, sessions, LDAP, SSO, API keys, or client credentials, depending on deployment configuration. | Martini can store confirmed credentials in secrets and environment configuration and apply the authentication model required by the approved LabVantage interface. |
| Scheduled synchronization | Limited | Polling or scheduled exchanges may be practical where the deployment exposes updated-since filters, revision identifiers, files, or reporting views. | Martini can run scheduled workflows, maintain watermarks, compare controlled data sets, and apply bounded concurrency and retry policies. |
How LabVantage exposes data and business events
LabVantage REST APIs
A LabVantage deployment may provide REST services for laboratory objects, but a current public API catalog was not verified. Availability, endpoints, schemas, authentication, and licensing must be confirmed for the installed version.
Martini implementation pattern
Martini implementation pattern: Martini consumes the confirmed REST endpoint, validates the response, maps JSON to a canonical laboratory model, applies business rules, and writes the result to the target system. A workflow can maintain watermarks and correlation identifiers for polling flows.
Implementation sequence
LabVantage SOAP and web services
Some LabVantage customer environments may use web-service integrations, but current SOAP support was not publicly verified. Existing service contracts and XML schemas must be obtained from the administrator or vendor.
Martini implementation pattern
Martini implementation pattern: Martini consumes the approved SOAP operation, handles XML namespaces and service faults, transforms the response, and routes successful transactions through a workflow. Business and transport failures are classified separately for safe retry.
Implementation sequence
LabVantage callbacks and notifications
No general-purpose LabVantage webhook catalog was verified. A deployment may provide outbound notifications or callbacks for selected processes, but coverage for Samples, Tests, and Results must be confirmed.
Martini implementation pattern
Martini implementation pattern: Martini exposes a protected API endpoint for a confirmed callback, acknowledges only after appropriate validation, and starts a workflow that retrieves the current resource where possible. The workflow should not assume that a notification contains the complete business object.
Implementation sequence
LabVantage file exchange
Structured files may be used for laboratory orders, instrument results, reference data, or approved exports, but supported formats and transport must be confirmed for the target environment.
Martini implementation pattern
Martini implementation pattern: Martini receives or retrieves an approved file, validates its name, format, schema, and business content, maps rows or documents into LabVantage or downstream objects, and archives processing status for audit and replay.
Implementation sequence
LabVantage database and reporting access
Self-managed deployments may expose read-only database or reporting access, but the database engine, schema, views, permissions, and vendor support policy require confirmation. Direct writes to application tables should not be assumed.
Martini implementation pattern
Martini implementation pattern: Martini reads approved reporting views or integration schemas through controlled database access, transforms the result, and sends it to downstream systems. The workflow uses watermarks or comparison logic and avoids bypassing LabVantage application validation.
Implementation sequence
Common LabVantage integration patterns
Pattern 1: Synchronize sample orders to LabVantage
When to use this pattern
Use this pattern when an enterprise application creates sample requests or test orders that must be registered in LabVantage. The target interface may be a confirmed REST or SOAP service, approved file exchange, or another configured integration service.
Integration direction
Example Mapping
| LabVantage Field | Canonical Field | Target Field |
|---|---|---|
| externalOrderId | sourceOrderId | Sample.externalIdentifier |
| sampleType | sampleType | Sample.sampleType |
| requestedTests | testRequests | Tests |
| priority | priority | Test.priority |
Martini implementation pattern
Martini receives the order through an API or scheduled workflow, validates required identifiers and requested Tests, maps the payload to the confirmed LabVantage model, and submits it through the approved interface. It stores the source-to-LabVantage identifier relationship and returns a controlled status. Validation failures are quarantined, while transient failures are retried without creating a second Sample.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- validation
- error handling
Pattern 2: Distribute approved test results
When to use this pattern
Use this pattern when released LabVantage Results must be sent to an ERP, customer-facing application, data warehouse, or analytics platform. The design must account for corrections, revisions, units, and approval state.
Integration direction
Example Mapping
| LabVantage Field | Canonical Field | Target Field |
|---|---|---|
| sampleIdentifier | sampleId | QualityInspection.sampleReference |
| testIdentifier | testId | QualityInspection.testReference |
| resultValue | value | InspectionResult.value |
| approvalState | resultStatus | InspectionResult.status |
Martini implementation pattern
A scheduled workflow or confirmed callback starts retrieval of current Results. Martini filters for approved or otherwise eligible states, preserves units and reference metadata, maps revisions to the target model, and records the delivered version. Duplicate deliveries are suppressed using a stable result key, and corrected Results are handled as revisions rather than new unrelated results.
Martini capabilities used
- scheduled workflows
- API consumption
- mapping and transformation
- business rules
- idempotency
- monitoring
Pattern 3: Normalize instrument result exchanges
When to use this pattern
Use this pattern when instruments or instrument middleware exchange data with LabVantage and enterprise systems use different result formats or identifiers. The deployment must provide an approved instrument or laboratory integration interface.
Integration direction
Example Mapping
| LabVantage Field | Canonical Field | Target Field |
|---|---|---|
| instrumentId | instrumentIdentifier | Instrument.identifier |
| specimenId | sampleId | Sample.externalIdentifier |
| analyteCode | testCode | Tests.code |
| measurement | resultValue | Results.value |
Martini implementation pattern
Martini receives the supported instrument payload or file, validates instrument and Sample identifiers, normalizes formats and units, applies routing and acceptance rules, and submits the result through the approved LabVantage interface. Failed transmissions are isolated for reprocessing, while malformed or unknown identifiers are sent to a quarantine path.
Martini capabilities used
- workflows
- file and API processing
- data transformation
- validation
- conditional routing
- error handling
Pattern 4: Synchronize laboratory master data
When to use this pattern
Use this pattern when Products, Instruments, Users, or selected test configuration must be synchronized between LabVantage and an enterprise source system. Ownership and the supported retrieval mechanism must be established before implementation.
Integration direction
Example Mapping
| LabVantage Field | Canonical Field | Target Field |
|---|---|---|
| productCode | productId | Products.externalIdentifier |
| productDescription | productName | Products.name |
| instrumentCode | instrumentIdentifier | Instruments.identifier |
| userExternalId | userId | Users.externalIdentifier |
Martini implementation pattern
A scheduler retrieves changed master data through a confirmed API, reporting view, or file exchange. Martini applies ownership, validation, normalization, and cross-reference rules before writing changes to LabVantage. A watermark or reconciliation comparison controls incremental processing, and rejected records are reported without advancing the checkpoint for unprocessed data.
Martini capabilities used
- scheduler triggers
- workflow orchestration
- mapping
- business rules
- database or API consumption
- reconciliation
Applications commonly integrated with LabVantage
LabVantage is commonly positioned alongside enterprise applications that provide laboratory master data, consume released results, support operational workflows, or store approved analytical exports. These relationships are architecture patterns rather than confirmation of universal LabVantage connectors; the enabled interface must be confirmed for each deployment.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Exchange materials, batches, vendors, purchasing information, laboratory results, and quality data. | SAP S/4HANA → Martini → LabVantage | Use an approved LabVantage service, file interface, or reporting interface to synchronize SAP master data into LabVantage and return quality or release results. Apply identifier cross-references, validation, idempotency, and controlled retries. |
| Salesforce | Send sample requests, customer-facing testing status, and released results to commercial or customer-service teams. | Salesforce → Martini → LabVantage | Expose or consume APIs for sample requests, map Salesforce identifiers to LabVantage Samples and Tests, and publish approved status or Results back to Salesforce through a workflow with audit logging. |
| ServiceNow | Create and update incidents, service requests, or equipment-related work associated with laboratory operations. | LabVantage → Martini → ServiceNow | Trigger workflows from approved LabVantage notifications, polling, or file inputs, then map instrument or laboratory issues to ServiceNow records. Store correlation identifiers and retry only transient failures. |
| Microsoft Power BI | Analyze laboratory throughput, turnaround time, instrument utilization, and result trends. | LabVantage → Martini → Microsoft Power BI | Retrieve approved reporting data or exports, normalize laboratory dimensions and timestamps, and deliver controlled datasets to the analytics environment. Preserve result status and revision information. |
| Oracle E-Business Suite | Exchange inventory, product, purchasing, quality, and batch information in regulated manufacturing environments. | Oracle E-Business Suite → Martini → LabVantage | Orchestrate scheduled master-data and result flows through confirmed LabVantage interfaces, applying ownership rules, field mappings, unit handling, and duplicate prevention. |
| Jira | Track laboratory system defects, integration failures, validation tasks, and change requests. | LabVantage → Martini → Jira | Route classified workflow failures or laboratory change events to Jira, include correlation and environment metadata, and prevent duplicate issue creation through a stored external key. |
| AWS S3 | Store approved exports, instrument files, reports, or analytical data for downstream processing. | LabVantage → Martini → AWS S3 | Receive or retrieve approved LabVantage files, validate naming and content, and write encrypted or access-controlled objects to S3 while recording processing status and checksums. |
| Microsoft Entra ID | Provide centralized identity and access management for laboratory users and administrators. | Microsoft Entra ID → Martini → LabVantage | Coordinate deployment-approved identity flows and keep credentials outside workflows. Martini can protect its own APIs and workflows while LabVantage administrators confirm the LIMS SSO or directory configuration. |
How to build a LabVantage integration in Martini
Objective
Confirm the LabVantage version, modules, deployment model, approved interface, and authentication mechanism before building the workflow.
Instructions in Martini
- Obtain the target interface contract and object schemas from the LabVantage administrator.
- Store credentials, certificates, and environment-specific values in Martini secrets or configuration.
- Use least-privilege access and confirm whether laboratory data contains regulated or sensitive information.
Objective
Select an event, callback, API-led, file, database, or scheduled trigger based on the capabilities confirmed in the deployment.
Instructions in Martini
- Use a callback or API endpoint only when LabVantage provides and authorizes it.
- Use a scheduler for polling or batch synchronization where no event mechanism is confirmed.
- Define the expected delivery, polling, and checkpoint behavior.
Objective
Receive or retrieve the current LabVantage object and establish a reliable correlation identifier before transformation.
Instructions in Martini
- Retrieve the complete Samples, Tests, Results, Instruments, Products, or Users payload when the interface supports it.
- Use pagination, updated-since filters, file manifests, or bounded database queries only when confirmed.
- Preserve source identifiers, revision values, approval state, units, and timestamps.
Objective
Implement the end-to-end Martini workflow that controls routing, enrichment, validation, target writes, and operational outcomes.
Instructions in Martini
- Separate transport, validation, business-rule, and target-system failures.
- Use reusable services or workflow components for common authentication, mapping, and error handling.
- Record correlation identifiers and processing status for audit and replay.
Objective
Convert LabVantage-specific structures into the canonical and target models without losing laboratory meaning.
Instructions in Martini
- Map actual LabVantage object fields rather than generic record names.
- Preserve units, reference ranges, result revisions, approval states, and external identifiers.
- Transform JSON, XML, files, or approved database results according to the confirmed schema.
Objective
Enforce laboratory and enterprise business rules before creating or updating downstream data.
Instructions in Martini
- Validate required Sample, Test, Result, Instrument, Product, and User values.
- Apply ownership, approval, status, duplicate, and identifier rules.
- Quarantine invalid data and avoid advancing checkpoints for records that were not safely processed.
Common LabVantage data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Samples | Register specimens or laboratory items for analysis and associate them with external orders and identifiers. | Salesforce, SAP S/4HANA, Oracle E-Business Suite, clinical applications | Martini validates required identifiers and sample attributes, maps source fields, stores cross-system identifiers, and uses idempotency to prevent duplicate registration. |
| Tests | Represent analytical or procedural work requested or performed for a Sample. | SAP S/4HANA, Salesforce, instrument middleware, customer portals | Martini maps requested test definitions and priorities, validates ownership and status values, and routes accepted requests through the confirmed LabVantage interface. |
| Results | Store measurements, observations, calculations, approvals, corrections, units, and reference information produced by Tests. | SAP S/4HANA, Oracle E-Business Suite, Microsoft Power BI, customer portals | Martini distinguishes preliminary, approved, corrected, rejected, and canceled states where available and preserves units, revisions, identifiers, and audit data. |
| Instruments | Identify laboratory equipment used to perform or support testing. | ServiceNow, instrument middleware, Microsoft Power BI, asset systems | Martini normalizes instrument identifiers and routes equipment or transmission events to approved enterprise endpoints while handling failed transmissions and reprocessing. |
| Products | Manage materials, formulations, or laboratory products associated with laboratory operations. | SAP S/4HANA, Oracle E-Business Suite, inventory systems | Martini applies system-of-record rules, maps product and batch identifiers, validates units and status values, and synchronizes only approved changes. |
| Users | Represent laboratory personnel and other authenticated LabVantage users. | Microsoft Entra ID, LDAP-backed directories, ServiceNow | Martini can coordinate approved identity-related exchanges, but the target deployment must confirm directory, SSO, and user-provisioning capabilities before implementation. |
Authentication and security considerations
Deployment-specific authentication
LabVantage authentication options were not publicly confirmed for a specific deployment. Potential mechanisms include username and password, Basic Authentication, sessions, LDAP, single sign-on, API keys, or client credentials.
Confirm the installed version, licensed modules, endpoint permissions, and identity architecture with the LabVantage administrator. Martini credentials, certificates, and environment values should be stored in secrets or secure configuration rather than embedded in workflows.
Least privilege and data protection
- Use the minimum permissions required for Samples, Tests, Results, Instruments, Products, or Users.
- Use TLS and protect regulated, personal, or confidential laboratory data.
- Audit access, transformations, approvals, corrections, and downstream deliveries.
- Prefer read-only reporting access for database integrations and avoid unsupported direct writes.
Operational considerations for LabVantage integrations
Version and interface validation
Confirm the LabVantage version, modules, deployment model, API or service contract, schemas, and support policy before implementation. Public material does not establish a universal endpoint or event catalog.
Reliability controls
- Confirm pagination, updated-since filtering, response limits, quotas, and concurrency guidance.
- Use bounded concurrency and exponential backoff for transient failures.
- Use stable external identifiers and idempotency keys to prevent duplicate Samples or Results.
- Distinguish validation, authentication, throttling, network, duplicate, and business-rule errors.
- Preserve result approval, correction, revision, unit, and reference-range information.
- Test against representative payloads and monitor workflow logs, checkpoints, and quarantined records.
Why use Martini instead of scripts or point-to-point integrations?
Centralized orchestration
Martini provides a controlled workflow layer between LabVantage and enterprise applications. It can consume approved APIs, receive callbacks, process files, or read approved reporting data, then apply consistent mappings and business rules.
Maintainable integration assets
Instead of duplicating logic across scripts and point-to-point interfaces, teams can centralize authentication, transformations, validation, retries, correlation, and monitoring in reusable Martini workflows and APIs.
- Support API-led, scheduled, file-based, and event-style patterns where the deployment permits them.
- Keep LabVantage-specific schemas behind normalized APIs when useful.
- Handle corrected Results, duplicate prevention, partial failures, and replay consistently.
- Separate environment configuration and secrets from implementation logic.
Frequently asked questions
LabVantage can be integrated through interfaces enabled by the specific deployment, such as approved REST or SOAP services, outbound notifications or callbacks, structured file exchanges, and read-only database or reporting access. The available mechanisms, schemas, authentication, and licensing must be confirmed for the installed version and modules.
Yes. Martini can integrate with LabVantage through the deployment's confirmed native interfaces, including REST or SOAP services, callback-style notifications, files, or approved database and reporting access. Martini can orchestrate workflows, transform JSON or XML, validate laboratory data, and connect the result to enterprise applications.
No. A dedicated LabVantage connector is not required. Martini can use LabVantage's confirmed native integration mechanisms, such as approved APIs, web services, callbacks, files, or read-only database interfaces. No native Martini LabVantage connector is documented in the supplied materials.
Lonti does not charge an additional per-connector or per-vendor fee to integrate LabVantage. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from LabVantage, cloud infrastructure, database hosting, or other third-party systems based on subscriptions, usage, and deployment model.
Use the current, vendor-approved interface for the target deployment. REST may be appropriate if enabled, while existing environments may use SOAP, files, callbacks, or reporting access. Confirm the API catalog, schemas, authentication, licensing, pagination, and support policy before selecting an approach.
A general-purpose LabVantage webhook catalog was not publicly verified. A deployment may provide outbound notifications or callbacks for selected processes, but event coverage should be confirmed. If available, Martini can receive the notification through an API endpoint and trigger a workflow.
Synchronization can be event-driven, API-led, file-based, database-based, or scheduled, depending on the confirmed deployment interfaces. Martini can maintain watermarks or correlation identifiers, map Samples, Tests, Results, Instruments, Products, and Users, and distinguish approved, corrected, rejected, or canceled result states where available.
Yes. Martini can transform confirmed LabVantage JSON or XML payloads, apply validation and business rules, and expose a controlled REST API for downstream applications. This can shield consumers from deployment-specific schemas while preserving identifiers, units, approval states, revisions, and audit information.
Related Martini documentation
Workflows
Data
Connect LabVantage with your enterprise systems
Use Martini to design, orchestrate, and operate LabVantage integrations through the interfaces enabled by your deployment.