Stream: implementers
Topic: CapabilityStatement.messaging.supportedMessage.definition
Adam (May 24 2020 at 17:05):
Hi all,
I'm now using the fragment reference like '#patient-create-event' in CapabilityStatement.messaging.supportedMessage.definition. Just wondering is this the right way? And also got a question: url fragment is only a part a url. So which url the fragment refers to?
Any suggestion is welcome.
Lloyd McKenzie (May 24 2020 at 18:08):
Is patient-create-event a contained MessageDefinition
Adam (May 25 2020 at 02:15):
Lloyd McKenzie said:
Is patient-create-event a contained MessageDefinition
Yes, it's a contained message event implemented by the server
Lloyd McKenzie (May 25 2020 at 05:14):
A 'contained' MessageDefinition would be unusual - that would mean it didn't have independent identity and couldn't stand on its own. I can't think of a situation where that would really make sense. (Remember, 'contained' is not used as a convenience way of sending multiple things at once, it's only used if something can't exist independently.)
When you refer to url fragment, can you explain what you mean? What fragment? Where?
Adam (May 27 2020 at 07:42):
Lloyd McKenzie said:
A 'contained' MessageDefinition would be unusual - that would mean it didn't have independent identity and couldn't stand on its own. I can't think of a situation where that would really make sense. (Remember, 'contained' is not used as a convenience way of sending multiple things at once, it's only used if something can't exist independently.)
When you refer to url fragment, can you explain what you mean? What fragment? Where?
Thank you for your reply. So it is supposed to replace this fragment reference with an absolute url address?
Lloyd McKenzie (May 27 2020 at 13:56):
MessageDefinition is referenced by a canonical URL. So it should be the same value as found in the MessageDefinition.url element.
Last updated: Apr 12 2022 at 19:14 UTC
