Stream: implementers
Topic: Invalid Meta datatypes in OperationDefinition parameters
Zach Smith (Jul 01 2019 at 21:58):
Some of the OperationDefinitions for resource metadata (e.g. https://www.hl7.org/fhir/operation-resource-meta.json.html), include a parameter with type Meta. However, according to the StructureDefinition for Parameters does not include Meta as an allowed datatype for the value typechoice. Should Meta be included in the structure definition?
Lloyd McKenzie (Jul 02 2019 at 01:29):
Hi Zach,
Good catch. Can you please submit a change request for us to address this?
Zach Smith (Jul 02 2019 at 01:45):
Sure thing! I just submitted a request for a gforge account
Lloyd McKenzie (Jul 02 2019 at 02:18):
Request granted :)
Zach Smith (Jul 02 2019 at 02:24):
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=22787&start=0
Zach Smith (Jul 05 2019 at 16:39):
@Lloyd McKenzie I think I may have found another issue similar to this. The FHIR docs for CodeSystem$lookup define the property.value field as a type-choice. However, when you look at the formal JSON definition, it's defined as code. Should I create a ticket for this as well?
Lloyd McKenzie (Jul 05 2019 at 17:58):
Yes
Zach Smith (Jul 05 2019 at 18:26):
https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=22807&start=0
Last updated: Apr 12 2022 at 19:14 UTC
