FHIR Chat · Operation parameter types · implementers

Stream: implementers

Topic: Operation parameter types


view this post on Zulip Michele Mottini (Apr 03 2017 at 23:07):

token and composite are valid types for operation parameters (http://hl7.org/fhir/DSTU2/valueset-operation-parameter-type.html) but what is the corresponding value[x] to use in the Parameters resource?

view this post on Zulip Sunanda Veeraganti (Apr 04 2017 at 21:10):

@Michele Mottini Token is Search parameter. Value of x would be either a string or pair of name spaces. and value. seperated by the character |

view this post on Zulip Michele Mottini (Apr 04 2017 at 21:21):

Mhh... 'x' must be a data type (http://hl7.org/fhir/DSTU2/datatypes.html) - see http://hl7.org/fhir/DSTU2/parameters-definitions.html#Parameters.parameter.value_x_, are you saying it should always be 'String' ?

view this post on Zulip Sunanda Veeraganti (Apr 05 2017 at 10:12):

@Michele Mottini No it is not always a string. It is a pair of namespace and value, depends on the modifier used.

view this post on Zulip Michele Mottini (Apr 05 2017 at 18:18):

value[x] is the name of a field - so x cannot possibly be a pair of namespace and value, it must be the name of a data type - e.g. String or Coding or CodebleConcept etc etc.

view this post on Zulip Michele Mottini (Apr 05 2017 at 18:40):

...I just noticed that the issue has been solved in STU3: token and composite are no longer valid types for operation parameters - http://hl7.org/fhir/valueset-all-types.html

view this post on Zulip Grahame Grieve (Apr 06 2017 at 04:07):

no we split the search parameters out to reoslve this question. The search parameters are always a 'string' type

view this post on Zulip Michele Mottini (Apr 06 2017 at 18:17):

Got it, thanks


Last updated: Apr 12 2022 at 19:14 UTC