Capital and Coast District Health Board is seeking software for several functions including a patient management system and electronic health records.
IS project office manager Robert Campbell says the aim is to replace a suite from SMS that has been in use since the late 1990s. The organisation is using SMS’s Allegra for patient management and ordering and scheduling and its clinical record module for the electronic health records.
The present system “doesn’t cover the full scope” of what is wanted, Campbell says.
“We know we don’t do some things, such as ordering and scheduling, very well and we’re seeking to replace the full-blown system and do some extra things.”
It will be more than a year before any new system is likely to be implemented, because as well as the formal tender process, consultation within Capital and Coast Health is needed, he says.
“We need to make sure we have all the ticks in the boxes.”
The new system may be from one vendor or a combination of suppliers. “If we end up with multiple vendors, we may need to phase implementation.”
The board has requested expressions of interest from vendors. “The RFI is looking to [allow us to] schedule everything to do with a patient, and the present system can’t do that.”
Capital and Coast, along with several other district health boards, is also seeking to replace its clinical case mix and costing systems.
The board has issued an RFI for new systems for itself and possibly other district health boards.
Information and planning director Andre Snoxall says the organisation is working collectively with a couple of boards, and Capital and Coast Health is working with the Taranaki district health board on HealthIntelligence, an IT resource sharing project.
The new system is to be based on a data warehouse using SQL Server environment. It will consist of a module to extract, clean and load data, a metadata library and costing engine.
Capital and Coast Health’s expressions of interest document, initially issued for the costing engine only, says the engine must be based on open systems architecture and accessible through a thin client. It must also be ODBC-compliant.
The ability to run multiple costing scenarios and a proven track record in Australasia, with adequate support available in this part of the world, are also requirements.
The board has asked for information from potential suppliers because, says Snoxall, “we’re considering the future of all systems for the board and want to ensure we’re aware of all the options that are currently in the marketplace. We don’t want to make a decision and then find we’ve missed something.”