Implement the US Core DiagnosticReport (Laboratory) and Laboratory Result Observation profiles for lab data exchange
domain: hl7.org · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
In-depth guide
FHIR Bulk Data $export gotchas — the full failure-mode walkthrough related to hl7.org, checked against official docs, with linked verified routes.
Verified steps
Conform report-level resources to the US Core DiagnosticReport Profile for Laboratory Results Reporting (us-core-diagnosticreport-lab) in the current US Core IG (v8.0.0, STU8)
Conform each individual result to the US Core Laboratory Result Observation Profile (us-core-observation-lab), which extends the US Core Observation Clinical Result Profile
Reference component Observations from the DiagnosticReport rather than duplicating result data, and support nested panel structures via Observation.hasMember/component
Populate DiagnosticReport.category with the required laboratory category coding and Observation.code with LOINC per the profiles' terminology bindings
Implement the required search parameters (e.g., patient, category, code, date) documented in each profile's Quick Start section
Known gotchas
US Core publishes an annual release tied to USCDI updates and must-support elements/bindings change between versions -- pin to a specific US Core version and re-validate on upgrade rather than assuming backward compatibility
US Core has separate DiagnosticReport profiles for laboratory results versus clinical notes/reports -- they have different required elements and must not be conflated
A report-level 'final' status does not guarantee every referenced Observation is final -- check each component Observation's own status, since individual results can be amended or corrected independently
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?