The SUT edition page shall be reworked in order to make it clearer, and more complete, so that the participants to not have to jump in multiple locations to manage their systems.
Avoid using tabs and use a navigation bar instead.
Centralize the information about the SUT for the participant
Reduce the number of pages to maintain
Ease the work of the SUT operator
As a SUT operator, I want to set the name of my SUT.
As a SUT operator, I want to give a type for my SUT (Gateway, Workstation, PACS).
As a SUT operator, I want to communicate to my partners the links to my capability statements (HL7, IHE, DICOM, FHIR).
Do we really need a keyword ? It brings confusion because there is no consistency in the tool (names and keywords are used in several places)
As a SUT operator, I want to list the capabilities of my SUT that I want to test.
As a SUT operator, I want to be aware of the testing status of each AIPO (testable, not testable, at risk) when it has already been decided by the test session manager.
As a SUT operator, I want to know when a profile is not testable:
- If it is already selected for my system, I need to be warned so that I am free to remove it from the list of capabilities;
- If it is not selected, I shall not be allowed to select it (but the reason why I cannot select shall be clearly stated)
As a SUT operator, I want to ask the test session manager to allow me to test a capability as supportive.
As a SUT operator, I want to filter out the list of capabilities my system is registered for (filter on actor, profile, domain, option, supportive, result).
As a SUT operator, I want to see the result for each capability.
As a SUT operator, I want to see the notes from the domain manager on a given capability (if any).
As a SUT operator, I want to see where I have to sit in the room.
As a SUT operator, I want to access the communication channel dedicated to my system.