Stream: fhir-messages
Topic: Consequence or notification
Kevin Mayfield (Jun 16 2021 at 12:55):
I'm looking at a prescription tracking system and we are using FHIR Messaging for exhchanging orders and dispense notifications. We have three core message types:
Kevin Mayfield (Jun 16 2021 at 12:58):
- prescription-order (consequence)
- dispense-notification (notification)
- dispense-claim (consequence)
Question is: it is intended some of the messages e.g. prescription-order are also going to be used as an event notification.
I'm wondering if I need a new version of this message e.g. prescription-notification or should somehow mark the original order as being a notification.
It is a probably a new message type anyway (as the Provence resource can be dropped).
Lloyd McKenzie (Jun 24 2021 at 17:08):
The event says "what is the receiver supposed to do". You can't use the same event to say "please fill" and "for your information"
Kevin Mayfield (Jun 24 2021 at 17:20):
thanks was wondering if that was the solution.
I presume if the structure is the same, I can use base to indicate base MessageDefinition (and just change the eventCoding and category). Inheritence works like profiles?
Lloyd McKenzie (Jun 24 2021 at 17:31):
I would think it would be a completely distinct MessageDefinition. The responses would probably be different. The documentation would be different. basedOn is more for "My system defines this message interface which is derived from such-and-such a standard message definition, but I constrain a few things or have additional documentation about how mine works". I would expect the event to be the same for all derived message definitions. That said, MessageDefinition is rather under-documented, so feel free to submit a change request asking for clarification.
Last updated: Apr 12 2022 at 19:14 UTC
