Stream: conformance
Topic: Extension Context
David Hay (Aug 07 2019 at 21:41):
The extension http://hl7.org/fhir/extension-iso21090-preferred.html has a context value of 'Resource' - so forge won't allow it to be added to an element (patient.address in this case). Shouldn't the context be 'Element' ?
Grahame Grieve (Aug 07 2019 at 21:41):
should be Address
Lloyd McKenzie (Aug 07 2019 at 21:42):
Address or ContactPoint I think...
Grahame Grieve (Aug 07 2019 at 21:42):
make a task for the technical correction
David Hay (Aug 07 2019 at 21:42):
But that would constrain it for address only wouldn't it? What if you wanted to use it for, say, Telecom?
David Hay (Aug 07 2019 at 21:50):
Or 2 contexts - Address and ContactPoint ?
Grahame Grieve (Aug 07 2019 at 21:50):
yes
David Hay (Aug 07 2019 at 21:55):
Grahame Grieve (Feb 01 2020 at 04:38):
The extension at http://hl7.org/fhir/extension-capabilitystatement-expectation.html has the following context:
CapabilityStatement.rest.operation
What's intended here? Is it supposed to work for CapabilityStatement.rest.resource.operation?
Lloyd McKenzie (Feb 01 2020 at 04:58):
Yeah, it should be allowed there too. Intent is to be able to put a SHALL/SHOULD/MAY/SHALL NOT beside each assertion of support for an operation
Lloyd McKenzie (Feb 01 2020 at 04:58):
(along with a bunch of other things)
Grahame Grieve (Feb 01 2020 at 05:01):
what I'm not sure about is the point of referring to the wrong context , and how that should be interpreted
Lloyd McKenzie (Feb 01 2020 at 05:09):
What do you meen by 'wrong context' - CapabilityStatement.rest.operation looks valid to me?
Lloyd McKenzie (Feb 01 2020 at 05:09):
It should also be CapabilityStatement.rest.resource.operation too though.
Last updated: Apr 12 2022 at 19:14 UTC
