Nexus EMR profile for Specimen -- the physical sample a lab result was produced from. Currently a pass-through type: the platform resolves ServiceRequest.specimen references and traverses into Specimen from DiagnosticReport, but reads none of its own fields. First pass; the heritage-EMR reconciliation is unresolved.
Salient fields
The profile's synthesized-accessor contract: fields TypedFhir surfaces as first-class typed properties, each computed from the instance by a restricted FHIRPath expression. See Salient Fields for what they are, how they shape LLM contexts, and how to declare them.
⚠ FIRST PASS -- no binding. The SNOMED specimen hierarchy is large and no agreed subset exists for this EMR. Readers MUST tolerate text-only. Heritage-EMR data typically supplies at most a free-text specimen-source string from the HL7 v2 OBR segment, so text-only is the expected shape, not the exception. Where this code was mapped from a source system's own vocabulary, carry the raw coding alongside the mapped one, flagged userSelected = true. See Carrying the raw code.
available | unavailable | unsatisfactory | entered-in-error
Definition
The availability of the specimen.
Comments
unsatisfactory is clinically meaningful -- a rejected sample means the test was NOT performed, and a consumer treating the linked result as pending rather than failed will wait forever. 0..1 in R4, so absence must be tolerated and must NOT be read as available. Heritage-EMR-derived specimens usually carry no status at all.
Time when specimen was collected from subject - the physiologically relevant time.
Comments
THE effective date for this profile, preferred over receivedTime. A choice of dateTime or Period in R4 -- handle both. Heritage-EMR lab messages often carry only the received/report time, in which case this is absent and the effective date falls through to receivedTime.