-
Notifications
You must be signed in to change notification settings - Fork 1
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
SOMDS ACM gateway Actor definition comments #323
Comments
SDPi Friday 2024.10.18 Review -
NOTE: Planned but still missing from the 1:12.1.1.3 SOMDS ACM Gateway section is a sequence diagram that makes it clear how the SDC alerting "events" trigger PCD-04 transactions. Adding this content (diagram + explanation) should make the interactions much clearer. DECISION: Update the specification (for 2.0 release) to include clear explanation of the functioning of the ACM Gateway and how it seamlessly integrates the SDC and ACM ecosystems. |
Thanks for the team review and comments Todd. The responses above make sense and I agree with the decision on actions to take. I think the sequence diagram will go a long way toward helping with confusion on that subject. Looking forward to seeing that when added. |
IHE ALL DEV Review 23.10.204 - |
Workshop #4 Discussion - |
Section 1:12.1.1
Medium Priority
Issue
ACM alert communication is unsolicited by the AM actor and requires no prior subscription by the AR actor. A subscribe model (which is described as part of the SOMDS ACM gateway Actor in section 1:12.1.1)would presume either all AMs would know all ARs or all ARs would know all AMs. This seems an impractical goal.
Proposed Change
Rather than polling/query, unsolicited communication provides the most near real time responsive approach to communicating medical device alarms and is the current method used in DEV ACM transactions.
The text was updated successfully, but these errors were encountered: