Connectathon-Process-Kudu

From IHEWiki

Jump to: navigation, search

Connectathon-Process-Kudu

  1. Moore: Develop a 30-45 training exercise/test of Kudu for participants to run in advance. Run these 10 exercises to make sure you understand the tool for the Connectathon.
  2. Gabe: Have a way to enter PatientID and Registry for submitted documents. It was nice to have it in Wiki this year but it didn't get used much which made it difficult to find documents in registries for testing a consumer.
  3. Vassil: Make the Yes/No radio buttons for the steps in each test either required or optional, and don't allow a test to be completed if the required radio buttons are not marked as Yes. If there is a requirement to support at least one of several optional steps, do not allow none of these steps to be marked as Yes.
  4. Vassil: Allow the Yes/No radio buttons to be set with setting the test to complete, instead of requiring a separate step of "Update" to record their settings.
  5. Vassil: Enable Kudu to upload attachments; in particular network trace files demonstrating successful TLS negotiation. Ehtereal is a free tool, and examining .cap files will cut down on ATNA security verification. Monitors should still preferably observe the TLS negotiation live, but then let the vendor upload the saved .cap file for detailed review.
  6. Murray: Remove non-required tests (e.g. PIX/ATNA; PDQ/ATNA) completely from the results matrix, rather than display that the test is not required once it has been opened.
  7. Murray: Relax the requirement that only one test can be active at a time. Server systems are often testing multiple consumers at once and constant 'pausing' was required to open new tests.
  8. Murray: Show optionality of test in the test description and/or Results Matrix (e.g. PDQ Continuation is optional for consumers, but required for suppliers)
  9. Max: Make the work list sortable by heading, vendor specifically. It's much easier to pass off the simple tests in one foul swoop.
  10. Mony: Allow the Monitors to pick test off the work-lists and assign to specific monitor, prevents double reads. Show monitor name on vendors test page. Working printer to print work-lists would also be nice. additional computer for monitors.
  11. Clark: Strongly concur with Mony. Showing which worklist tests are being worked by which monitor will save much monitor walking and checking with other monitors processing the same worklist.
  12. Levy: Concur with number 2. Everything we need should be in Kudu.
  13. Witting: Allow a way to say "yes" to all steps with one mouse click
  14. Witting: Opening a test always scrolled me down too far, start at the top or use very smart program to figure out where I left off
  15. Witting: Document the move up feature, I had no clue what that was about until Eric explained it.
  16. seknoop: There was no single table that included the company, profile, actor, hostname, IP, system name, digital certificate and table location. This made system configuration preparation for Connectathon difficult. It would be great to have this all consolodated into a single table.
  17. Oosterwijk: It would be nice to structure the test procedures to make it easy to record results: add three columns, one for each actor they have to play with and number each individual test item.
  18. Oosterwijk: have a single log-in to kudu to verify tests instead of having to specify your password every time. I spent more than one hour each nite to update the results, this could be done more easily.
  19. Felhofer: One vendor representative suggested using 3 different shapes in the Result Matrix, as well as colors (red, yellow, green), to show profile status. Those who are color-blind cannot distiguish between the colors.
  20. Alkire: Suggest entering data for partner Universal Id's, host, ports, actors, application, facility, etc in a single xml file. That file can then be used by participants to load their DBs programatically, or by Kudo to display as html tables.
Personal tools