FHIR Chat · Observation Composition search parameters · implementers

Stream: implementers

Topic: Observation Composition search parameters

Eric Haas (Jan 05 2017 at 23:17):

As a follow up to https://chat.fhir.org/#narrow/near/50397/stream/implementers/topic/R3.20Draft I have a tracker GF#11087 to keep search parameters for only code and only component code. So as a result there will be search parameters for:

• code only
• component-code only
• both code + component-code

This will makes the code-value search explode and this is generally confusing so I have a couple of questions and seek opinions

Proposed search parameter names:

( same for 'value-[type]' too )

• 'code' = Observation.code only ( same as DSTU2 )
• 'component-code' = Observation.component.code only ( same as DSTU2 )
• 'combo-code' = Observation.code|Observation.component.code` (currently is code in STU3)

The composite code-value search will then become...

• so the code-value-[type] composite searches will be for Observation.code and Observation.value only
• so component-code-value-[type] composite searches will be for Observation.component.code and Observation.component.value only
• and so combo-code-value-[type] composite searches will be for so component-code-value-[type] composite searches will be for Observation.component.code|Observation.component.code and Observation.value|Observation.component.value

Grahame Grieve (Jan 05 2017 at 23:22):

sounds reasonable to me

Last updated: Apr 12 2022 at 19:14 UTC