Goodbye and a big good luck to Tom Moreton who worked for us during Rashmi’s maternity leave. We wish him all the best with his round-the-world trip!
And welcome back to Rashmi, returning from maternity leave and keen to get back into work, welcome!
Feb 282012
Roll-up of multiple internal versions including:
- Fixed reports sent via HL7 where they would go Forward Failed if not a re-send.
- Fixed an issue where associations weren’t properly closed for Query Retrieves
- Code re-use – fixed an issue getting properties that were related to other products.
- Fixed query retrieve date format in query phase
- Fixed calling of GPG encryption for Linux builds
- Study Details are now updated on a re-Accept, which ensures studies requested by eMDT don’t keep a patient name of “eMDT”
- Fixed an issue where gateways with large databases (i.e. slow auto-update) could fail to pick up a change in Admin Console filter. This made the Admin Console auto-update seem unresponsive.
- Changed DICOM configuration to make sure SCU (Forward) can negotiate both Compressed and Uncompressed transfer syntaxes
- Improved support for switching patient identifier DICOM tags; no longer implemented on a per site basis.
See wiki entry for full details.
Feb 092012
Changes in Version 2.13.11 include:
- Improved MAC address fetching. bbRad gateways can now run on more types of virtual machine, including VirtualBox and VMware.
Feb 092012
Changes in Version 2.13.10 include:
- Fixed a bug where columns on the List Studies screen would sometimes show the wrong field. This bug only affected the display of study data, not the actual studies, so would not affect them once Forwarded into PACS.
Feb 092012
Changes in Version 2.13.09 include:
- Improved handling of re-sent studies. Studies where images have been changed since first sending will no longer go “Take Failed”.
- Other minor bug-fixes.
We have been rolling out bbRad version 2.13 across all our installed base, and have scheduled with our users 13th, 14th, and 21st December out of hours to batch a large number of sites, targeting the oldest versions installed.
These updates will also include our latest auto-update mechanism, so from now on, all sites will be automatically kept up-to-date.
We have also asked sites to configure firewalls to enable access to a new backup bbRad.net service, which will come on-line in early 2012.
Dec 072011
Please come and visit Tom and Opey!
Cypher IT’s 2013 Transition Service, comprising full Data Migration and exoPACS Vendor Neutral Archive are being exhibited at the NHS South of England PACS/RIS Showcase Event today and tomorrow, 7th & 8th December.
The event, held at the Arora Hotel near Gatwick Airport, allows us to showcase to a wider audience how NHS Trusts save money by starting their 2013 Transition early, running concurrently with their OJEU procurements.
If you’re unable to make the event, please email Opey on pacs2013@cypherit.co.uk
NHS South of England comprises South Central, South East Coast and South West Strategic Health Authorities.
Dec 062011
The main features of note in version 2.13.08 are:
- Auto-Refresh – the Admin Console updates automatically whenever the status of a study changes.
- Filters and column memory – each user’s filters and column sorting/sizing are remembered between sessions.
- Improved support for multiple filters – combining multiple filters works in more intuitive way and the most recently updated results are shown first.
- Messages – a message can now be attached to studies to explain why the study was sent.
- Support for lossy compressed studies.
- Many other bug fixes and improvements
Forward thinking NHS Trusts are already gaining first-mover advantage by starting with Cypher IT’s 2013 Transition Service.
Orders coming in for our Proof of Concept vindicates that there is real demand for the unique advantages that our service brings to NHS hospitals.
Other interested Trusts please contact me for more information.
It has been asked “Why use a VNA for an intermediate archive?” This is a good question, because at first sight it would seem sensible to keep the VNA once the data is transferred to it.
There are two answers to this question:
First, procurement – our Transition Service means NHS Trusts regain local ownership of their data, moving themselves from a weak negotiating position into a strong one, thus saving money. Even if staying with the existing vendor, there are ‘migration’ costs to move data out of the DataCentre onto local storage. As committing to a VNA architecture for a long contract means going to OJEU, that decision cannot be made ahead of time. So our transition service delivers cash savings, irrespective of whether Trusts procure a new PACS or extend the existing vendor’s contract. This is further explained here.
Second, clinical usability – in order to be able to ‘switch off’ the Data Centre contract as soon as possible (and start saving money), historical data must be kept clinically usable, i.e. up to date. This is achieved through standard interfacing of demographic updates, a feature not available is the data in just a basic DICOM archive (or off-line). An outline schematic is here.