Acceptable latency

[jkiddo]

Whats considered acceptable latency between sending and reciving MedCom messages in general?

[tmsMedcom]

As a sender you are allowed to resend a message after 30 min, if you haven't received an Acknowledgement. https://medcomdk.github.io/MedCom-FHIR-Communication/assets/documents/020_Governance-for-Reliable-Messaging-in-general.html#11-generic-ruleset-governing-the-principles-of-reliable-messaging.

[jkiddo]

Since the acknowledgement are sent on business level (medcomdk/dk-medcom-acknowledgement#33 (comment)) why would it ever make sense to resend it from business sender perspective? No state will change due to the retransmission. Why wouldn't VANS automatically produce a NACK or do the retry itself?

[jkiddo]

As a sender you are allowed to resend a message after 30 min, if you haven't received an Acknowledgement. https://medcomdk.github.io/MedCom-FHIR-Communication/assets/documents/020_Governance-for-Reliable-Messaging-in-general.html#11-generic-ruleset-governing-the-principles-of-reliable-messaging.

Would you mind making numbered bullets to those rules?

[jkiddo]

And is the VANS vendor considered part of the 'Eco system' in those rules?

[ovi-medcom]

No, VANS reacts, when a message arrives from the sender. VANS has only a certain power in EHMI, where edelivery rules exists.

[ovi-medcom]

As a sender you are allowed to resend a message after 30 min, if you haven't received an Acknowledgement. https://medcomdk.github.io/MedCom-FHIR-Communication/assets/documents/020_Governance-for-Reliable-Messaging-in-general.html#11-generic-ruleset-governing-the-principles-of-reliable-messaging.

Would you mind making numbered bullets to those rules?

Created an issue :-)

[jkiddo]

But VANS still is responsible for transmission of content, correct? And since VANS already knows what is sent and replied to, why doesn't VANS do the retransmission after 30 mins automatically or provide a NACK to the sender?