Examples on reply messages

[jkiddo]

I don't see any examples on a MedCom message where the contents is a reply to a previous MedCom message (where the https://www.hl7.org/fhir/R4/messageheader-definitions.html#MessageHeader.response is used).

[jkiddo]

@tmsMedcom / @ovi-medcom

[tmsMedcom]

More examples - including reply - can be found under each standard (HospitalNotification, Acknowledgement... see https://medcomfhir.dk/ig/) Use of MessageHeader.response can be found in here: https://medcomfhir.dk/ig/acknowledgement/StructureDefinition-medcom-messaging-acknowledgementHeader.html

[jkiddo]

Hmmm ... looking at e.g. https://medcomfhir.dk/ig/carecommunication/Bundle-b56549f7-ed10-422d-8088-f7222b686e46.json.html I don't see that the https://build.fhir.org/messageheader-definitions.html#MessageHeader.response is populated

[tmsMedcom]

Indicating that a message is a reply (and other activities) to another message, is handled in the Provenance profile https://medcomfhir.dk/ig/messaging/StructureDefinition-medcom-messaging-provenance.html

[jkiddo]

@tmsMedcom I don’t think that aligns with the standard, AFAIK.

[tmsMedcom]

You might have a point. The MessageHeader.response element is chosen to be used for the Acknowledgement of messages, where the Provenance is chosen to connect the stream of messages .

[jkiddo]

So are you going to change it?

[tmsMedcom]

Not for the messaging standards that has already been published (HospitalNotification and CareCommunication), but we will take your input into consideration for the next once.

[jkiddo]

@tmsMedcom so you are not going to correct existing messages?

[tmsMedcom]

Not for now. If the standards are being updated for some other reason, we will take it into account but it is not in the in the scope right now.

[jkiddo]

And this issue list is the backlog?