+1 253 200 5860
Digital Clinical Documentation Software
"It's time for more efficient and accurate clinical notes"
from Oncology Information Capture System (OnICS Ltd)
6.0) Advantages, Endorsements and Performance
The Elekta software, MOSAIQ, has been updated (v 2.9.1) to enhance interoperability and CCDA (Continuity of Care Document Architecture) export abilities that can communicate with 3rd party vendor software. OnICS Ltd. is now one such vendor (as of December 2019) that have developed its own HL7 based interface (called autom8) for iNOTZ to communicate with MOSAIQ as well as being compliant with other software systems such as those from Epic, Meditech and Cerner.
6.2) Oncology Franchises
Three (3) franchises, apart for Elekta, have evaluated and endorsed the iNOTZ clinical annotation system. These include;
Capital medical (currently evaluating paperless operation)
6.3) System Performance
iNOTZ is deployed in 6 centres and many others await MOSAIQ updates.
Over 1,000,000 patient encounters are recorded in the OnICS iNOTZ data base.
There have been no complaints due to iNOTZ content but, problems have arisen from two sources following deployment.
Networks. Some obsolete local area networks (LAN) have had to be updated due to the increased traffic density from using iNOTZ.
Legacy software. Elekta acquired software from IMPAC some 15 years ago which formed the basis of MOSAIQ. The interfacing process with MOSAIQ has been a prolonged exercise due to evolving HL7 standards which only recently have enabled interoperability between iNOTZ and MOSAIQ. Due to limitations of interfaces available from Elekta for MOSAIQ for connectivity with the iNOTZ product, OnICS staff have worked together with Elekta technical representatives to identify problems in terms of interoperability with MOSAIQ. This was resolved by a combination of OnICS and Elekta programmers working together.
Legacy software, written in a previous version that has not been updated can often fail to meet modern HL7 standards, this can give rise to problems when communicating with code written in a very much later, and more advanced, version of the same language. Often, the previous version will work well for the “environment” in which it was written and a vendor, quite reasonably, will adhere to the maxim “if it’s working don’t fix it”. However, introduction of new more advanced code can “stress” the older code that must be updated.