Stream: implementers
Topic: AllergyIntolerance example
Joel Francis (Jul 19 2017 at 16:42):
Looking at the example of @Grahame Grieve that extends the AllergyIntolerance resource found here: http://www.healthintersections.com.au/?p=2656
Is the notion of a "context" and "contextType" not required? i.e, how is it communicated that this extension is performed on the AllergyIntolerance resource.
Lloyd McKenzie (Jul 20 2017 at 01:48):
Yes, that example is missing context and contextType which should be required in that case. @Grahame Grieve - are you able to correct the blog post?
Joel Francis (Jul 20 2017 at 14:41):
Thanks @Lloyd McKenzie . You mentioned that in this case it is required - I am under the impression that a context and contextType will be required in all extension cases. Can you please clarify. Thanks
Lloyd McKenzie (Jul 20 2017 at 14:55):
If a StructureDefinition is defining an extension, then yes, I believe context and contexttype is required. In theory you might profile the Extension data type for general use and wouldn't be creating an extension and in that case, I guess context/contextType could be omitted.
Grahame Grieve (Jul 21 2017 at 20:38):
fixed my blog post
Last updated: Apr 12 2022 at 19:14 UTC
