Patient
Laboratory data
Named panels, individual results, and their recorded units.
Format definition
Model orders, specimens, panels, analytes, and serial results separately.
Scenario standard · Execution capabilities
Parameters
resources[].diagnostic
object
Optional; omitted means unspecified
A named request with explicit result references. Laboratory requests require an authored specimen description.
resources[].results[].panelName
string
Optional; omitted means unspecified
Human-readable panel grouping; does not inject assumed analytes.
observations[].referenceInterval
object
Optional; omitted means unspecified
At least one bound or text description; numeric bounds require the observation's unit and low must not exceed high. Context describes the authored population/method.
observations[].flag
"low" | "high" | "critical" | "none" | "not-interpreted"
Optional; omitted means unspecified
Explicit authored flag, never inferred from a generic source default.
resources[].results[].specimenStatus
"adequate" | "inadequate" | "not-collected"
Optional; omitted means unspecified
Allows rejected or unavailable specimens to drive a repeat-collection branch.
Behavior and validation
- Results are numeric, qualitative text, or boolean observations according to the concept definition. Preserve decimals. Collection and release are distinct events.
- Suite stores editable laboratory rows in events.objects[].labResults with name, value and unit strings, optional referenceRange text and an optional low/high flag. It preserves authored intervals and flags through export and import; changing a result does not recalculate its flag. Omission leaves reporting metadata unspecified. This is the Suite profile mapping, not an implementation of the richer portable observation structure.
- Laboratory panels are reusable catalog resources, not part of the format specification. Import selected panels as explicit authored observations, preserving values, units, and provenance. Missing results remain unspecified; never inject normal results during playback.
- Each repeated collection creates a runtime request/result instance; serial authored result templates have distinct IDs. Do not overwrite previous results or use numeric zero for pending results.
Shared format conventions · All format elements · Download specification