Stream: implementers
Topic: extension from client
Yunwei Wang (May 17 2019 at 01:26):
Can client declare a profile which contains extension? If so, what server should act when receive a resource when unknown extension?
Grahame Grieve (May 17 2019 at 01:31):
our advice is that the server should ignore unknown extensions and either keep or drop them as it's able to do. Not everyone can get agreement to do that
Lloyd McKenzie (May 17 2019 at 01:37):
ModifierExtensions are different. You need to be quite cautious about doing any processing of an instance that contains an unrecognized modifierExtension.
Yunwei Wang (May 17 2019 at 01:39):
Ha, that is exactly what I am going to ask. How about modifier and mustSupport extension.
Grahame Grieve (May 17 2019 at 01:40):
yes, in my code that processes resources, I have a .noModifiers() that throws an exception. e.g.
var import = valueset.compose.include.noModifiers()
Lloyd McKenzie (May 17 2019 at 01:42):
If an element you don't care about or process contains a modifier, you could theoretically persist and ignore it (e.g. something on Patient.contact when you do no processing on contacts). In a document, you might just render the narrative.
Lloyd McKenzie (May 17 2019 at 01:44):
For things marked as mustSupport in a profile, the answer depends on whether your system claims to comply with the profile. (Just putting a profile declaration in your instance doesn't mean that all recipients will magically support your stuff - though that would be pretty cool :>)
Last updated: Apr 12 2022 at 19:14 UTC
