PARTNERS

One secure integration gives you quantitative, standardised point-of-care data for many LFA brands

Connect iaX data into EMR, LIS, LIMS, ERP, and custom analytics platforms. One secure integration gives you quantitative, standardised point-of-care data for many LFA brands — without building separate connectors for each test manufacturer.

Start integrating All partner types

WHO WE MEAN BY SYSTEM INTEGRATORS

Connect iaX data to the systems that matter

If you build, customise, or maintain healthcare IT, laboratory, enterprise, or analytics platforms, the iaX integration layer lets you add quantitative rapid-test data as a new input — from one API, covering many test brands.

EMR / EHR Vendors

Embed quantitative rapid-test results directly into electronic medical or health records, closing the loop between point-of-care testing and clinical documentation.

LIS / LIMS Providers

Route iaX test data into laboratory information systems for sample tracking, quality control, and compliance reporting — no manual transcription required.

ERP & Supply Chain Platforms

Connect diagnostic results to enterprise resource planning and supply chain systems for food safety, agriculture, and industrial quality workflows.

Analytics & BI Platforms

Feed standardised, quantitative test data into dashboards, trend analysis, and business intelligence tools for real-time operational insight.

Public Health & Surveillance Systems

Automate reporting of notifiable results to public health authorities and disease surveillance networks with structured, standards-compliant data.

Custom & Vertical Applications

Build bespoke integrations for telehealth, veterinary, environmental monitoring, or any workflow that benefits from connected rapid-test data.

THE FOUNDATION OF RELIABLE INTEGRATIONS

One data source, many destinations

The iaX platform normalises results from every qualified lateral flow assay into a single, structured data format — so you integrate once and receive data from many test brands.

One Data Source, Many Destinations

A single integration point delivers quantitative results from any iaX-qualified LFA — regardless of test brand or analyte — into your target system.

Standardised & Structured

Every result includes analyte, concentration, device ID, GPS, operator, timestamp, and QC metadata in a consistent, machine-readable format.

Secure by Design

TLS encryption in transit, AES-256 at rest, OAuth 2.0 authentication, role-based access control, and full audit logging as standard.

Multi-Tenant Ready

Serve multiple clients or sites from a single integration. Tenant isolation, per-client API keys, and configurable data routing are built in.

Scalable & Reliable

Cloud-native architecture with automatic scaling, 99.9% uptime SLA, and global edge delivery ensures your integration performs under load.

Developer-Friendly

Comprehensive API documentation, SDKs, a sandbox environment, and dedicated integration support make onboarding fast and predictable.

DATA DISTRIBUTION MODELS SUPPORTED

Choose the delivery model that fits your architecture

Modern deployments consume diagnostic data in different ways. Assaya supports two complementary distribution models designed to align with sector requirements and system architecture.

Automated Push Delivery

Healthcare & Public Health

HL7 FHIR and v2.x message delivery
Automated routing to EMR, LIS, and public health registries
Real-time or batched delivery with delivery confirmation
Standards-compliant structure for regulatory and audit trails

Reliable, real-time delivery into governed clinical ecosystems without integration bottlenecks.

Flexible API Access

Operational & Industry Systems

RESTful API with OAuth 2.0 authentication
Pull-based access for ERP, LIMS, analytics, and custom apps
Webhook notifications for new results and status changes
Comprehensive developer documentation and sandbox environment

Diagnostic data becomes part of operational decision systems without rigid delivery constraints.

CONNECTED BY DESIGN

Push quantitative results to the systems that run your workflows

Push quantitative results + metadata to EMR, LIS/LIMS, ePCR, analytics, command centres, alerts, dashboards, and compliance reports.

Hospitals / EMR

Results routing to clinical records, triage boards, alerting

Labs / LIS / LIMS

Result ingestion, QC status, lot/expiry traceability

EMS / ePCR

On-scene result push, incident linkage, response analytics

Public Health

De-identified feeds, geo tags, outbreak dashboards

Analytics / EDW

Batch/stream to BI; scheduled exports

Non-clinical (CSV/JSON)

Simple flat-file drops and SFTP/Webhook options

HOW IT WORKS

From test to integrated insight

01. Read & interpret

Assaya’s iaX converts rapid tests into calibrated quantitative digital records ready for downstream integration.

02. Secure structured data

AssayaDX is the cloud platform that structures, validates, and governs diagnostic data, providing traceability, exports, and integration endpoints.

03. Integrate & operationalise

AssayaDX portal access for dashboards and exports. Event-driven webhooks to push structured data in real time. API access to query and incorporate data into your applications and workflows.

LET’S BUILD SOMETHING SPECIAL TOGETHER

Build high-impact diagnostics solutions for your markets

Combine your domain expertise with Assaya’s quantitative rapid diagnostics platform, data architecture, and integration models to build differentiated, sector-specific solutions that deliver connected diagnostics without reinventing testing infrastructure.

Start the conversation

HAVE QUESTIONS?

System Integrator FAQs

These are some of the most common questions raised by integration partners. If you have others we are happy to answer them.

+What does AssayaDX provide for data integration?

We provide a secure cloud platform (AssayaDX) featuring a push-based webhook architecture, REST APIs, and scheduled export options. This is paired with our iaX readers, which convert multi-brand Lateral Flow Assays (LFAs) into quantitative, standardised digital results with rich metadata.

+Why does Assaya use a ‘push’ (webhook) model instead of ‘pull’ (polling)?

The push model eliminates the inefficiency and latency of polling. Instead of your system constantly asking “Is there new data yet?”, our platform notifies you in real-time the instant an event occurs. This enables faster clinical decisions and provides a scalable foundation for high-throughput environments.

+Do we need to build our own application to start using the data?

No. You can begin immediately by using the dashboards and scheduled CSV/JSON export features in the AssayaDX portal. When you are ready for real-time integration, you can implement webhooks to push data directly into your target systems.

+Do you support HL7 v2 or FHIR standards?

We provide a standardised, richly detailed JSON payload that serves as the “source of truth,” decoupling our platform from specific standard complexities. We provide mapping guides and reference connectors (e.g., for Mirth/NextGen) to help you perform the “last-mile” transformation into the specific HL7 or FHIR format required by your EMR, LIS, or national health system.

+What key information comes with each test result payload?

Every result includes calibrated quantitative values, units, timestamps, operator/device IDs, site information, lot/expiry traceability, and QC/validity flags. The payload also contains a unique event ID, a Universal Test ID (UTID), the full test profile name, and the critical scandata object.

+How do we link results to patient identifiers (the scandata object)?

We utilise a scandata object which is critical for linking a test result to a patient or sample. This object contains the raw, unaltered data from any QR code or barcode scanned by the operator. We pass this through our system untouched, giving you full control over your own identification formats without requiring Assaya firmware changes.

+How should we interpret the quantitative values in the payload?

You should almost always use the ev (equivalent value) object for display. It contains the final numeric result rounded to the correct decimals and the appropriate display unit (e.g., ng/mL). The val field represents the raw internal intensity used for internal logic.

+How do we handle new test types (assays) in the integration?

The webhook payload schema remains consistent. When a new assay is used, you will simply see a new string in the profile field (Manufacturer: Test Name). Your code can dynamically categorise results based on this string without requiring changes to your integration’s core logic.

+How do we verify that webhooks are actually from AssayaDX?

Every webhook request includes an X-Assaya-Signature header created using HMAC-SHA256 with a unique signing secret provided in the portal. Your server must re-calculate this signature and compare it to the header to verify authenticity and integrity. You should also check the timestamp in the header to prevent replay attacks.

+Can we support clients with strict data sovereignty rules (e.g., Government/CDC)?

Yes. We support a “Push-and-Purge” workflow designed for data sovereignty. In this model, the iaX device sends the result to our cloud, we immediately push it to the client’s secure endpoint, and upon receiving a 200 OK success response, we automatically and permanently delete the record from our systems.

+Do you support IP whitelisting?

While we can provide egress IP ranges, we consider IP whitelisting a secondary control. Cryptographic verification via HMAC is the primary and most robust proof of identity. We also support Mutual TLS (mTLS) for high-security environments.

+What happens if our endpoint is down or returns an error?

If your endpoint returns a 5xx server error or times out, we automatically retry delivery using an exponential backoff strategy with jitter. This prevents “thundering herd” issues and gives your system time to recover.

+What happens if delivery fails after all retries?

If an event fails all automated retries (typically over 72 hours), it is moved to a Dead Letter Queue (DLQ) so no data is silently lost. You can inspect the error in the portal’s “Failed Deliveries” log and click “Replay Event” to re-inject it once your endpoint is fixed.

+How should we handle duplicate events?

Our system provides “at-least-once” delivery, so your system should be idempotent. Use the unique event ID provided in the payload to check if you have already processed that specific event.

+How do we monitor the integration and debug issues?

The AssayaDX portal provides live, searchable event logs where you can inspect the full payload, headers, and the exact HTTP error response your server returned for every delivery attempt.

+How do we configure endpoints? Do we need to contact support?

Configuration is a fully self-service process in the AssayaDX portal. You can add and manage multiple HTTPS endpoints for different environments (dev, staging, production) without contacting our engineering team.

+Can we filter which events we receive?

Yes. The portal provides granular control, allowing you to subscribe only to specific event types. For example, a LIMS might subscribe to test.completed, while a maintenance dashboard subscribes only to device.online and device.error.

+Does the system work in locations with intermittent internet?

Yes. The iaX devices support store-and-forward functionality. They buffer results offline and automatically sync all records to the cloud once connectivity is restored, retaining accurate original timestamps.

+What developer tools are available?

We offer a complete developer toolkit including OpenAPI 3.0 (Swagger) specifications, a full sandbox environment, Postman collections for API testing, live event logs, and a test console to trigger mock webhooks.

GET IN TOUCH

Start the conversation

Tell us about the systems you build or manage, and how iaX data could add value. Our integration team will follow up with technical documentation and next steps.