Which interfaces does Probatix offer?

REST API for orders, status queries and result retrieval; webhooks for push notifications on status changes (currently in beta release); a FHIR R4 endpoint for interoperable results. Optional: the partner portal as a graphical alternative without your own development.

Are results delivered in FHIR-compliant form?

Yes. Results are delivered as a FHIR R4 bundle, with Observation resources for each parameter, a DiagnosticReport resource for the overall result and the corresponding Patient/Practitioner references. Values are LOINC-coded.

What are LOINC codes and why are they important?

LOINC (Logical Observation Identifiers Names and Codes) is the international standard for the unique identification of clinical measurement parameters. ‘Glucose in serum' has the LOINC code 2345-7 in every system — that makes results interoperable and avoids mapping effort on the receiving side.

How long does integration take?

For a standard REST API integration, typically a few days of development time. Add a test sandbox phase and compliance setup. Realistic time-to-live: 2–6 weeks from signing the contract, depending on programme depth.

Can it also work without your own development?

Yes. The partner portal covers all operational workflows — create orders, track status, retrieve results, view statistics. Ideal for programmes that don't want to tie up a dev team.

Integrating laboratory diagnostics via API: REST, FHIR results, LOINC and a flexible workflow

The API flow

At its core the integration consists of four steps:

1.  POST /v1/orders              → create order (panel, recipient, branding profile)
2.  Activation                   → end user activates the kit (link/QR from your system)
3.  Webhook: status_changed      → push notification on every status change
4.  GET /v1/orders/{id}/report   → retrieve result (JSON or FHIR R4)

Create an order

POST /v1/orders
Authorization: Bearer <token>
Content-Type: application/json

{
  "panel": "longevity-basic",
  "recipient": { ... },
  "branding_profile": "partner-xyz",
  "callback_url": "https://yourapp.example/webhook"
}

Response: order ID, estimated ETA until sample arrival.

Track status

Status transitions typically follow this pattern: created → shipped → delivered → sample_received → analyzed → report_ready. Via webhooks you are notified about every transition in real time — no polling required.

Retrieve the result

As soon as report_ready has fired, you fetch the result:

GET /v1/orders/{id}/report?format=fhir

→ a FHIR R4 bundle with DiagnosticReport + Observations for each parameter. Alternatively, format=json for a simplified Probatix-internal format.

Standardised result data

Standardisation is where the real leverage sits. Anyone working in health apps, telemedicine or care platforms should distinguish two levels in the result data format:

Structure — how the fields of a result are organised.
Coding — how an individual parameter is uniquely named.

Probatix delivers both to international standards:

FHIR R4 is the HL7 format for clinical data. A result arrives as a bundle in which you find, in structured form:

DiagnosticReport — the summarising result (status, analysis date, conclusion).
Observation per parameter — value, unit, reference range, LOINC code, flags (high/low/critical).
Patient / Practitioner — referential metadata.

LOINC codes identify every parameter uniquely. Example: ‘Glucose in serum or plasma’ is assigned the code LOINC 2345-7 — worldwide. Whichever system is on the receiving side, this code is understood. That applies to cholesterol (2093-3), HbA1c (4548-4) and thousands of other parameters.

The benefit for you: when you pass results on to a third-party system (insurer, EHR, FHIR server), you save the parameter mapping. Result ingestion works “out of the box”. That is the difference between a PDF someone has to map and a data object that can dock automatically.

Webhooks instead of polling

Instead of asking for the status repeatedly, we notify you — at your webhook URL, with a signed payload. That saves load and keeps your app synchronised in real time. Note: the webhook interface is currently in beta release; the specification, signature scheme and retry logic are provided directly to partners in the beta programme. Polling via the REST API is always possible in parallel.

Flexible workflow

The API is not the only integration pattern. You can combine:

API only — your app orchestrates the entire flow.
Partner portal — operational day-to-day work in the UI; API only for result data.
Webshop integration — kit ordering via ready-made modules in your shop.

The routing of the result is also configurable:

Result to your app — you show it in your UI.
Result to the end user — via the Probatix patient portal (white-label).
Result to telemedicine / contracted physician — direct handover into the practice system (especially for models under §116b/117).

Time-to-result

For most tests the result is available within 48 hours of the sample arriving at the laboratory. What influences the range:

Parameter specifics (some methods need incubation times).
Number of parameters (panel size).
Lab routing (capacity of the connected laboratories).

Status webhooks keep you up to date at every step.

Integration effort

Realistically:

Minimal use case (create order + poll status + retrieve result PDF): a few days of development time.
Deep FHIR integration (mapping into your own FHIR server, parameter logic in the UI): 1–3 weeks.
Full programme integration (UI, app flow, result routing, reporting): 4–8 weeks including test and compliance phases.

If you don’t have a dev team: the partner portal covers all workflows — you can start immediately and add API integration later.