This page is part of the US Core (v3.1.0: STU3) based on FHIR R4. The current version which supercedes this version is 5.0.1. For a full list of available versions, see the Directory of published versions
StructureDefinition-us-core-observation-lab
Laboratory results are grouped and summarized using the DiagnosticReport resource which reference Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) which references other observations, or rarely a laboratory test with component result values. This profile sets minimum expectations for the Observation resource resource to record, search, and fetch laboratory test results associated with a patient. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile.
Example Usage Scenarios:
The following are example usage scenarios for the US Core-Results profile:
- Query for lab results belonging to a Patient
- Record or update lab results belonging to a Patient
Mandatory and Must Support Data Elements
The following data-elements are mandatory (i.e data MUST be present) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.
Each Observation must have:
- a status
- a category code of ‘laboratory’
- a LOINC code, if available, which tells you what is being measured
- a patient
Each Observation must support:
- a time indicating when the measurement was taken
- a result value or a reason why the data is absent
- if the result value is a numeric quantity, a standard UCUM unit
Profile specific implementation guidance:
- Additional codes that translate or map to the Observation code or category codes are allowed. For example:
- providing both a local code and LOINC code
- providing a more specific category codes such as ‘chemistry’, SNOMED CT concept, or system specific codes in addition to the ‘laboratory’ category code.
- An Observation without a value, SHALL include a reason why the data is absent unless there are component observations, or references to other Observations that are grouped within it .
- For Further guidance see the Observation Grouping section in FHIR Specification.
- See the General Guidance Section for further guidance on using UCUM
Examples
Formal Views of Profile Content
Description of Profiles, Differentials, and Snapshots.
The official URL for this profile is:
http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab
Published on Mon Aug 19 00:00:00 AEST 2019 as active by the HL7 US Realm Steering Committee.
This profile builds on Observation
Observation
Summary of the Mandatory Requirements
- A code in
Observation.status
with a required binding to ObservationStatus - One or more CodeableConcepts in
Observation.category
- which must have at least a Observation.category = {“coding”: [{“code”: “laboratory”, “system”: “ http://terminology.hl7.org/CodeSystem/observation-category”}]}
- A CodeableConcept in
Observation.code
with an extensible binding to LOINC Codes - A Patient Reference in
Observation.subject
Summary of the Must Support Requirements
- A dateTime in
Observation.effective[x]
with the following constraints: Datetime must be at least to day. - A Quantity in
Observation.value[x]
with the following constraints: SHOULD use Snomed CT for coded Results, SHALL use UCUM for coded quantity units. - A CodeableConcept in
Observation.dataAbsentReason
with an extensible binding to DataAbsentReason
Summary of Constraints
- If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
- dataAbsentReason SHALL only be present if Observation.value[x] is not present
- If there is no component or related element then either a value[x] or a data absent reason must be present
- Datetime must be at least to day.
- SHOULD use Snomed CT for coded Results
- SHALL use UCUM for coded quantity units.
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
Observation | I | 0..* | us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present | |
status | S | 1..1 | code | Binding: ObservationStatus (required) |
category | S | 1..* | (Slice Definition) | Slice: Unordered, Open by pattern:$this |
category:Laboratory | S | 1..1 | CodeableConcept | Required Pattern: At least the following |
coding | 1..* | Coding | Code defined by a terminology system Fixed Value: (complex) | |
system | 1..1 | uri | Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/observation-category | |
code | 1..1 | code | Symbol in syntax defined by the system Fixed Value: laboratory | |
code | S | 1..1 | CodeableConcept | Laboratory Test Name Binding: LOINCCodes (extensible) |
subject | S | 1..1 | Reference(US Core Patient Profile) | |
effective[x] | SI | 0..1 | us-core-1: Datetime must be at least to day. | |
effectiveDateTime | dateTime | |||
effectivePeriod | Period | |||
value[x] | SI | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Result Value us-core-4: SHOULD use Snomed CT for coded Results us-core-3: SHALL use UCUM for coded quantity units. |
dataAbsentReason | SI | 0..1 | CodeableConcept | Binding: DataAbsentReason (extensible) |
Documentation for this format |
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
Observation | I | 0..* | Measurements and simple assertions us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present | |
id | Σ | 0..1 | string | Logical id of this artifact |
meta | ΣI | 0..1 | Meta | Metadata about the resource |
implicitRules | ?!ΣI | 0..1 | uri | A set of rules under which this content was created |
language | I | 0..1 | code | Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages |
text | I | 0..1 | Narrative | Text summary of the resource, for human interpretation |
contained | 0..* | Resource | Contained, inline Resources | |
extension | I | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!I | 0..* | Extension | Extensions that cannot be ignored |
identifier | ΣI | 0..* | Identifier | Business Identifier for observation |
basedOn | ΣI | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | Fulfills plan, proposal or order |
partOf | ΣI | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Part of referenced event |
status | ?!SΣI | 1..1 | code | registered | preliminary | final | amended + Binding: ObservationStatus (required) |
category | SI | 1..* | (Slice Definition) | Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ObservationCategoryCodes (preferred) |
category:Laboratory | SI | 1..1 | CodeableConcept | Classification of type of observation Binding: ObservationCategoryCodes (preferred) Required Pattern: At least the following |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | 0..* | Extension | Additional content defined by implementations | |
coding | 1..* | Coding | Code defined by a terminology system Fixed Value: (complex) | |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | 0..* | Extension | Additional content defined by implementations | |
system | 1..1 | uri | Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/observation-category | |
version | 0..1 | string | Version of the system - if relevant | |
code | 1..1 | code | Symbol in syntax defined by the system Fixed Value: laboratory | |
display | 0..1 | string | Representation defined by the system | |
userSelected | 0..1 | boolean | If this coding was chosen directly by the user | |
text | 0..1 | string | Plain text representation of the concept | |
code | SΣI | 1..1 | CodeableConcept | Laboratory Test Name Binding: LOINCCodes (extensible) |
subject | SΣI | 1..1 | Reference(US Core Patient Profile) | Who and/or what the observation is about |
focus | ΣI | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record |
encounter | ΣI | 0..1 | Reference(Encounter) | Healthcare event during which this observation is made |
effective[x] | SΣI | 0..1 | Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day. | |
effectiveDateTime | dateTime | |||
effectivePeriod | Period | |||
issued | ΣI | 0..1 | instant | Date/Time this version was made available |
performer | ΣI | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Who is responsible for the observation |
value[x] | SΣI | 0..1 | Result Value us-core-4: SHOULD use Snomed CT for coded Results us-core-3: SHALL use UCUM for coded quantity units. | |
valueQuantity | Quantity | |||
valueCodeableConcept | CodeableConcept | |||
valueString | string | |||
valueBoolean | boolean | |||
valueInteger | integer | |||
valueRange | Range | |||
valueRatio | Ratio | |||
valueSampledData | SampledData | |||
valueTime | time | |||
valueDateTime | dateTime | |||
valuePeriod | Period | |||
dataAbsentReason | SI | 0..1 | CodeableConcept | Why the result is missing Binding: DataAbsentReason (extensible) |
interpretation | I | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible) |
note | I | 0..* | Annotation | Comments about the observation |
bodySite | I | 0..1 | CodeableConcept | Observed body part Binding: SNOMEDCTBodyStructures (example) |
method | I | 0..1 | CodeableConcept | How it was done Binding: ObservationMethods (example) |
specimen | I | 0..1 | Reference(Specimen) | Specimen used for this observation |
device | I | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device |
referenceRange | I | 0..* | BackboneElement | Provides guide for interpretation obs-3: Must have at least a low or a high or text |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | I | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!ΣI | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
low | I | 0..1 | SimpleQuantity | Low Range, if relevant |
high | I | 0..1 | SimpleQuantity | High Range, if relevant |
type | I | 0..1 | CodeableConcept | Reference range qualifier Binding: ObservationReferenceRangeMeaningCodes (preferred) |
appliesTo | I | 0..* | CodeableConcept | Reference range population Binding: ObservationReferenceRangeAppliesToCodes (example) |
age | I | 0..1 | Range | Applicable age range, if relevant |
text | I | 0..1 | string | Text based reference range in an observation |
hasMember | ΣI | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | Related resource that belongs to the Observation group |
derivedFrom | ΣI | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | Related measurements the observation is made from |
component | ΣI | 0..* | BackboneElement | Component results |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | I | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!ΣI | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
code | ΣI | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: LOINCCodes (example) |
value[x] | ΣI | 0..1 | Actual component result | |
valueQuantity | Quantity | |||
valueCodeableConcept | CodeableConcept | |||
valueString | string | |||
valueBoolean | boolean | |||
valueInteger | integer | |||
valueRange | Range | |||
valueRatio | Ratio | |||
valueSampledData | SampledData | |||
valueTime | time | |||
valueDateTime | dateTime | |||
valuePeriod | Period | |||
dataAbsentReason | I | 0..1 | CodeableConcept | Why the component result is missing Binding: DataAbsentReason (extensible) |
interpretation | I | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible) |
referenceRange | I | 0..* | Unknown reference to #Observation.referenceRange Provides guide for interpretation of component result | |
Documentation for this format |
Observation
Summary of the Mandatory Requirements
- A code in
Observation.status
with a required binding to ObservationStatus - One or more CodeableConcepts in
Observation.category
- which must have at least a Observation.category = {“coding”: [{“code”: “laboratory”, “system”: “ http://terminology.hl7.org/CodeSystem/observation-category”}]}
- A CodeableConcept in
Observation.code
with an extensible binding to LOINC Codes - A Patient Reference in
Observation.subject
Summary of the Must Support Requirements
- A dateTime in
Observation.effective[x]
with the following constraints: Datetime must be at least to day. - A Quantity in
Observation.value[x]
with the following constraints: SHOULD use Snomed CT for coded Results, SHALL use UCUM for coded quantity units. - A CodeableConcept in
Observation.dataAbsentReason
with an extensible binding to DataAbsentReason
Summary of Constraints
- If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present
- dataAbsentReason SHALL only be present if Observation.value[x] is not present
- If there is no component or related element then either a value[x] or a data absent reason must be present
- Datetime must be at least to day.
- SHOULD use Snomed CT for coded Results
- SHALL use UCUM for coded quantity units.
Differential View
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
Observation | I | 0..* | us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present | |
status | S | 1..1 | code | Binding: ObservationStatus (required) |
category | S | 1..* | (Slice Definition) | Slice: Unordered, Open by pattern:$this |
category:Laboratory | S | 1..1 | CodeableConcept | Required Pattern: At least the following |
coding | 1..* | Coding | Code defined by a terminology system Fixed Value: (complex) | |
system | 1..1 | uri | Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/observation-category | |
code | 1..1 | code | Symbol in syntax defined by the system Fixed Value: laboratory | |
code | S | 1..1 | CodeableConcept | Laboratory Test Name Binding: LOINCCodes (extensible) |
subject | S | 1..1 | Reference(US Core Patient Profile) | |
effective[x] | SI | 0..1 | us-core-1: Datetime must be at least to day. | |
effectiveDateTime | dateTime | |||
effectivePeriod | Period | |||
value[x] | SI | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Result Value us-core-4: SHOULD use Snomed CT for coded Results us-core-3: SHALL use UCUM for coded quantity units. |
dataAbsentReason | SI | 0..1 | CodeableConcept | Binding: DataAbsentReason (extensible) |
Documentation for this format |
Snapshot View
Name | Flags | Card. | Type | Description & Constraints |
---|---|---|---|---|
Observation | I | 0..* | Measurements and simple assertions us-core-2: If there is no component or related element then either a value[x] or a data absent reason must be present | |
id | Σ | 0..1 | string | Logical id of this artifact |
meta | ΣI | 0..1 | Meta | Metadata about the resource |
implicitRules | ?!ΣI | 0..1 | uri | A set of rules under which this content was created |
language | I | 0..1 | code | Language of the resource content Binding: CommonLanguages (preferred) Max Binding: AllLanguages |
text | I | 0..1 | Narrative | Text summary of the resource, for human interpretation |
contained | 0..* | Resource | Contained, inline Resources | |
extension | I | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!I | 0..* | Extension | Extensions that cannot be ignored |
identifier | ΣI | 0..* | Identifier | Business Identifier for observation |
basedOn | ΣI | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | Fulfills plan, proposal or order |
partOf | ΣI | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Part of referenced event |
status | ?!SΣI | 1..1 | code | registered | preliminary | final | amended + Binding: ObservationStatus (required) |
category | SI | 1..* | (Slice Definition) | Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ObservationCategoryCodes (preferred) |
category:Laboratory | SI | 1..1 | CodeableConcept | Classification of type of observation Binding: ObservationCategoryCodes (preferred) Required Pattern: At least the following |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | 0..* | Extension | Additional content defined by implementations | |
coding | 1..* | Coding | Code defined by a terminology system Fixed Value: (complex) | |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | 0..* | Extension | Additional content defined by implementations | |
system | 1..1 | uri | Identity of the terminology system Fixed Value: http://terminology.hl7.org/CodeSystem/observation-category | |
version | 0..1 | string | Version of the system - if relevant | |
code | 1..1 | code | Symbol in syntax defined by the system Fixed Value: laboratory | |
display | 0..1 | string | Representation defined by the system | |
userSelected | 0..1 | boolean | If this coding was chosen directly by the user | |
text | 0..1 | string | Plain text representation of the concept | |
code | SΣI | 1..1 | CodeableConcept | Laboratory Test Name Binding: LOINCCodes (extensible) |
subject | SΣI | 1..1 | Reference(US Core Patient Profile) | Who and/or what the observation is about |
focus | ΣI | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record |
encounter | ΣI | 0..1 | Reference(Encounter) | Healthcare event during which this observation is made |
effective[x] | SΣI | 0..1 | Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day. | |
effectiveDateTime | dateTime | |||
effectivePeriod | Period | |||
issued | ΣI | 0..1 | instant | Date/Time this version was made available |
performer | ΣI | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Who is responsible for the observation |
value[x] | SΣI | 0..1 | Result Value us-core-4: SHOULD use Snomed CT for coded Results us-core-3: SHALL use UCUM for coded quantity units. | |
valueQuantity | Quantity | |||
valueCodeableConcept | CodeableConcept | |||
valueString | string | |||
valueBoolean | boolean | |||
valueInteger | integer | |||
valueRange | Range | |||
valueRatio | Ratio | |||
valueSampledData | SampledData | |||
valueTime | time | |||
valueDateTime | dateTime | |||
valuePeriod | Period | |||
dataAbsentReason | SI | 0..1 | CodeableConcept | Why the result is missing Binding: DataAbsentReason (extensible) |
interpretation | I | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible) |
note | I | 0..* | Annotation | Comments about the observation |
bodySite | I | 0..1 | CodeableConcept | Observed body part Binding: SNOMEDCTBodyStructures (example) |
method | I | 0..1 | CodeableConcept | How it was done Binding: ObservationMethods (example) |
specimen | I | 0..1 | Reference(Specimen) | Specimen used for this observation |
device | I | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device |
referenceRange | I | 0..* | BackboneElement | Provides guide for interpretation obs-3: Must have at least a low or a high or text |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | I | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!ΣI | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
low | I | 0..1 | SimpleQuantity | Low Range, if relevant |
high | I | 0..1 | SimpleQuantity | High Range, if relevant |
type | I | 0..1 | CodeableConcept | Reference range qualifier Binding: ObservationReferenceRangeMeaningCodes (preferred) |
appliesTo | I | 0..* | CodeableConcept | Reference range population Binding: ObservationReferenceRangeAppliesToCodes (example) |
age | I | 0..1 | Range | Applicable age range, if relevant |
text | I | 0..1 | string | Text based reference range in an observation |
hasMember | ΣI | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | Related resource that belongs to the Observation group |
derivedFrom | ΣI | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | Related measurements the observation is made from |
component | ΣI | 0..* | BackboneElement | Component results |
id | 0..1 | string | Unique id for inter-element referencing | |
extension | I | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!ΣI | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
code | ΣI | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: LOINCCodes (example) |
value[x] | ΣI | 0..1 | Actual component result | |
valueQuantity | Quantity | |||
valueCodeableConcept | CodeableConcept | |||
valueString | string | |||
valueBoolean | boolean | |||
valueInteger | integer | |||
valueRange | Range | |||
valueRatio | Ratio | |||
valueSampledData | SampledData | |||
valueTime | time | |||
valueDateTime | dateTime | |||
valuePeriod | Period | |||
dataAbsentReason | I | 0..1 | CodeableConcept | Why the component result is missing Binding: DataAbsentReason (extensible) |
interpretation | I | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible) |
referenceRange | I | 0..* | Unknown reference to #Observation.referenceRange Provides guide for interpretation of component result | |
Documentation for this format |
Downloads: StructureDefinition: (XML, JSON), Schema: XML Schematron
Quick Start
Below is an overview of the required set of RESTful FHIR interactions - for example, search and read operations - for this profile. See the Conformance requirements for a complete list of supported RESTful interactions for this IG.
- See the General Guidance section for additional rules and expectations when a server requires status parameters.
- See the General Guidance section for additional guidance on searching for multiple patients.
Mandatory Search Parameters:
The following search parameters and search parameter combinations SHALL be supported.:
-
SHALL support searching using the combination of the
patient
andcategory
search parameters:GET [base]/Observation?patient=[reference]&category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory
Example:
- GET [base]/Observation?patient=1134281&category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and a category code =
laboratory
(how to search by reference and how to search by token) - SHALL support searching using the combination of the
patient
andcode
search parameters:- including optional support for composite OR search on
code
(e.g.code={[system]}|[code],{[system]}|[code],...
)
GET [base]/Observation?patient=[reference]&code={[system]}|[code]{,{[system]}|[code],...}
Example:
- GET [base]/Observation?patient=1134281&code=http://loinc.org|2339-0
- GET [base]/Observation?patient=1134281&code=http://loinc.org|2339-0,http://loinc.org|25428-4,2514-8
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and observation code(s). SHOULD support search by multiple report codes. The Observation
code
parameter searches `Observation.code only. (how to search by reference and how to search by token) - including optional support for composite OR search on
- SHALL support searching using the combination of the
patient
andcategory
anddate
search parameters:- including support for these
date
comparators:gt,lt,ge,le
- including optional support for composite AND search on
date
(e.g.date=[date]&date=[date]]&...
)
GET [base]/Observation?patient=[reference]&category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}
Example:
- GET [base]Observation?patient=555580&category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory&date=ge2018-03-14
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and date and a category code =
laboratory
(how to search by reference and how to search by token and how to search by date) - including support for these
Optional Search Parameters:
The following search parameter combinations SHOULD be supported.:
- SHOULD support searching using the combination of the
patient
andcategory
andstatus
search parameters:- including support for composite OR search on
status
(e.g.status={[system]}|[code],{[system]}|[code],...
)
GET [base]/Observation?patient=[reference]&category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory&status={[system]}|[code]{,{[system]}|[code],...}
Example:
- GET [base]/Observation?patient=1134281&category=http://terminology.hl7.org/CodeSystem/observation-category|laboratory&status=final
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and category =
laboratory
and status (how to search by reference and how to search by token) - including support for composite OR search on
- SHOULD support searching using the combination of the
patient
andcode
anddate
search parameters:- including optional support for composite OR search on
code
(e.g.code={[system]}|[code],{[system]}|[code],...
) - including support for these
date
comparators:gt,lt,ge,le
- including optional support for composite AND search on
date
(e.g.date=[date]&date=[date]]&...
)
GET [base]/Observation?patient=[reference]&code={[system]}|[code]{,{[system]}|[code],...}&date={gt|lt|ge|le}[date]{&date={gt|lt|ge|le}[date]&...}
Example:
- GET [base]Observation?patient=555580&code=http://loinc.org|2339-0&date=ge2019
Implementation Notes: Fetches a bundle of all Observation resources for the specified patient and date and report code(s). SHOULD support search by multiple report codes. (how to search by reference and how to search by token and how to search by date)
- including optional support for composite OR search on