0.1.0 - ci-build
SENAITEFHIRImplementationGuide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions
Integrations with SENAITE are best initially considered in terms of workflows. Workflows avoid becoming mired in technical domain language too early, require almost no tech literacy and focus on what flows goes where. Also if a manual (paper-based) workflow exists, the automated version can mirror it and hence its digital equivalent is quickly comprehensible by lab staff with no experience in API design.
The two main workflows for SENAITE are:
SenaiteClient extension.ServiceRequest and Specimen are always present — exactly one of each, since one request is one sample, and both are created afresh for every request. Patient, Practitioner and Organization are included only when they may not yet exist in SENAITE; once created, a consumer can reference them by logical id in later requests and omit the entries entirely.
An order spanning several sample types (tubes) is submitted as one Bundle per tube, tied together by a shared ServiceRequest.requisition — see Multi-tube orders. Results come back as one DiagnosticReport per sample, and optionally as a single combined report covering the whole requisition — see Combined reports.
The supported workflows are split into dedicated pages:
Use the links above to view each workflow in detail.