FHIR REST APIs
Orders, results, and the chart payload — the lattice as versioned endpoints.
Developers
The lattice, as an API
Integrate Diagnostics and Clinical Record with FHIR REST APIs, a sandbox tenant, and production-shaped examples.
Sandbox
A non-production tenant for development and testing.
Sample code
Node and Python examples for the order and result paths.
Versioned changes
API changes ship with versions, not surprises.
Workflow diagrams
Order, result, file — documented as they run.
HL7 under the hood
Partners who still speak v2 do not force your product off FHIR.
Example
Place an order over FHIR
Base URL https://api.lattix.co/fhir. OAuth 2.0 bearer tokens. Resources you already know: Patient, ServiceRequest, Observation, DiagnosticReport, ImagingStudy, Subscription.
Legacy interop is handled under the hood: HL7 v2, SFTP, MLLP.
POST /fhir/ServiceRequest
const res = await fetch("https://api.lattix.co/fhir/ServiceRequest", {
method: "POST",
headers: {
Authorization: "Bearer <token>",
"Content-Type": "application/fhir+json",
},
body: JSON.stringify(order),
});
const created = await res.json();
// Electronic order on the lattice
console.log(created.id);Common resources
| Resource | Used for |
|---|---|
| Patient | Identity and match |
| ServiceRequest | Lab and imaging orders |
| DiagnosticReport / Observation | Structured results |
| ImagingStudy | Imaging context alongside the report |
| DocumentReference | Clinical documents on the payload |
| Subscription | Result delivery when the lab files |
Request a sandbox tenant
Talk with us about labs, imaging, and putting the chart on one interchange.