Stream: implementers
Topic: Search Parameter Status
Richard Kavanagh (Dec 14 2017 at 08:15):
Looking through the resources that are normative candidates, I see that CapabilityStatement is a candidate. This references StructureDefinition and OperationDefinition which are also normative candidates. It does also reference SearchParameter which is not.
|We know that for systems that do not implement the whole of the FHIR search mechanism we need to use SearchParameter to describe aspects of search that are not directly present in the CapabilityStatement.
So, for this (and other resources) is there any way to find out the rationale for resources not becoming normative? I'm not challenging the decision not to make resources normative, just asking if we can see why this is the case so we can make risk assessments on whether to use them or not.
Lloyd McKenzie (Dec 14 2017 at 15:36):
@Grahame Grieve I'm actually not sure why SearchParameter isn't a candidate...
Last updated: Apr 12 2022 at 19:14 UTC
