-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is changing the sender within an existing thread allowed? #37
Comments
Is this in relation to the CareCommunication message? In that case, a correspondance with replies is between two communicating parties, not three. If B wants C to answer, 'm1' should be forwarded to C. |
Right - but is it allowed? |
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? |
Acknowledgements are on technical not on business level. Advanced handling of transmission scenarios like in email messages if acks were turned on in emails, has very firmly been rejected from the business organizations. The staff is often in critical scenarios with real world patients and don't want to figure out, whar the heck is going on in a carecommunication exchange. We tried to go The "email"-metaphor way, but it has been rejected, and therefore also strict rules around the exchange.. |
Sorry #37 (comment) should have gone into #38 |
So - to reiterate: is it allowed or should a NACK be sent in this case? |
Taking over someone else's communication is allowed in a new message thread, not as a continuation of an existing. |
Is that a yes or a no? |
No |
What should happen in an existing correspondance flow if recipient A sends a message 'm1' to B and then C responds to A with a message 'm2' that references 'm1' using Provenance.what.reference. Is that allowed?
The text was updated successfully, but these errors were encountered: