FHIR Chat · syntax for specifying profiling a parameter · shorthand

Stream: shorthand

Topic: syntax for specifying profiling a parameter


view this post on Zulip Sean Muir (Aug 06 2020 at 18:02):

I am attempting to add a profile to the an out parameter to a operation definition

  • parameter[4].name = #VeteranStatus "VeteranStatus"
  • parameter[4].use = #out "out"
  • parameter[4].min = 1
  • parameter[4].max = "1"
  • parameter[4].type = #Observation "Observation"

what is the proper way to add the profile to the return observation

view this post on Zulip Nick Freiter (Aug 10 2020 at 11:47):

Do you know how you would want to represent this in FHIR? I'm unsure how it would look, so I don't know how to translate to FSH. If you have an idea of how this would look on the JSON/XML OperationDefinition, we can then look to translate that into FSH.

view this post on Zulip Mark Kramer (Aug 10 2020 at 13:08):

The profile would go into the parameter[n].targetProfile element. The type is 0..* canonical(StructureDefinition). So in FSH, it would be something like this:

* parameter[4].targetProfile[0] = Canonical(ProfileNameDefinedInTheCurrentIG)

or this:

* parameter[4].targetProfile[0] = http://theCanonicalURLofExternalProfile

view this post on Zulip Nick Freiter (Aug 10 2020 at 13:10):

Adding to @Mark Kramer 's suggestion, you would also have to change the parameter[4].type to either Reference or Canonical, according to https://www.hl7.org/fhir/operationdefinition.html#invs


Last updated: Apr 12 2022 at 19:14 UTC