Nexus makes it possible to group users in communities so they can share information and perform actions in the name of their community(ies), such as send cases to request advice and reply to requests. A community is an individual entity that groups users who log into Nexus using their own user account, thus making it possible to trace actions performed by each user.
When Nexus is accessible from the Nexus Platform, community management is delegated in part to Runtime through the management of Services.
To access service management, click on Administration from Runtime navigation menu, then on Directory and Services tab.
Create a community
Initialize a community
To create a Nexus community, you must first create a service in the Runtime directory and activate the Nexus application for this service. You can associate Users with it at any time.
For more information on service management, refer to the user manual Runtime > Services management.
If your establishment uses a shared Nexus with other establishments, the community name will have a prefix identifying the establisment.
You can complete other information.
Define visibility for cases
You can define the community’s level of visibility so that it is chosen as the recipient of a case. If the community is not visible, it is not possible to send it cases.
Add case templates
In the Case templates section add the case template(s) that address the community’s needs.
Configure other parameters
If needed, edit the default AE Title, instead of the suggested default, to refer to the community.
If needed, in the QA/QC templates section, add the reconciliation template(s) that specify the rights to edit DICOM attributes when a member of the community sends studies to a local server or to the PACS
In the DICOM applications section, add the DICOM applications from which the community members will be allowed to add studies to Nexus or to which they will be allowed to send studies from Nexus.
In the Notifications for cases section, specify if you want Nexus to send an email notification to all the members of the community and/or to other persons for each case sent or received in its name. Then, the members will not have to log into Nexus to check if cases created in the name of the community were sent successfully or if the community has received new cases.
In the Study routing section you can specify to which local server(s) studies contained in cases should be automatically routed. Also, specify for each server if routing applies to cases sent and/or received by the community.
Remove a community
The removal of a community will have the effect that all cases of which the community was the recipient or author will no longer be visible to members of the community.
Removal o the community can be achieved by deleting the service or deactivating the Nexus application on that service.
Disable Nexus application
Disabling the Nexus application will delete the community on the Nexus but will keep the service in the directory.