Xero What Needs Doing?

This page lists some areas that could be worked on to improve Xero generally, or to add specific feature areas to Xero. This is just some of the ideas that have been suggested, but there are lots of other things that could be done to improve Xero generally. If you are interested in becoming a contributer, please read the page Contributing to Xero.

General

• Implement a pluggable help system to allow components to define their own documentation, and to allow a site to define customizations and information specific to their site (for example, how to change a password.)

Search and List Areas

There are likely to be more items added here, but the bulk of the work is expected to be done in the display areas.

• Modify the search and list areas to use AJAX rather than refreshing the pages all the time.
• Add column sorting (Both AJAX and HTML only)
• Add column organization (add/remove column, add search criteria from column)
• Implement integrations with XDS IIS to allow searching the XDS repository instead of using a DICOM C-Find.

Display Area Interface

There are a number of smaller projects in the display area, as well as some quite large ones.

• Add support for DICOM Hanging Protocols to define the layout
• Add a waveform display
• Add TCE Selector publishing
• Add KO selection and display

Performance and Concurrency

• Make the caching systems add an in-progress indicator and make anything wanting the cached value wait for whatever thread is currently trying to get that value. Have a time out so if it takes forever (thread dies), a new thread can start, or monitor the thread for liveness.
• Allow multiple image readers to be created/used for multi-frames so that two or more images can be decoded from the same multiframe at once.

Security

• Adding basic login support using the same login id as is used in the dcm4chee administrator modules would be quite helpful as an initial start at security.
• The ability to transmit a URL with embedded security information in it over a short-range wireless or IR link to allow a clinician to select a study in a device like a Palm or RIM, and cause a large screen device fixed in the room to view that page would be quite helpful. In fact, a hospital could allow a monitor to be used as both a large screen view device and a regular TV for patients - that cuts down on the space requirements for having a large monitor in addition to a television, and would mean that a cart with a monitor would not need to be moved around to show patient information.

Infrastructure

• WAR files don't have any way to include warlets, a component that would extend the set of pages available in a WAR file, but is packaged separately. This would be very helpful to add, as it would mean that a site could add CSS pages and other related data, and just deploy the WARlet independently of the primary WAR, without modifying the base WAR file. That also means that projects could be developed much more distributed by allowing each warlet to contain a portion of the total functionality.