Just as I had finished posting yesterday’s blog I had the following come in via e-Mail.
Complete health identifier service still months away
Software vendors to come online in Q1 2011 as NeHTA rolls out "evolutionary process"
- James Hutchinson (Computerworld)
- 07 June, 2010 16:41
Despite efforts to have the healthcare identifier (HI) service up and running by 1 July, the National eHealth Transition Authority (NeHTA) believes the service could take years to fully implement.
A spokesperson for the authority behind the implementation of the identifier service told Computerworld Australia that the system required additional software vendors, live testing and education for healthcare providers before the system was rolled out nationwide.
Recent amendments made to the Healthcare Identifiers Bill - the legislation that will enable the service to be implemented - has pushed back its reintroduction into Parliament to 17 June, and potentially pushed back the service's starting date back from its original July timeframe.
However, the spokesperson said that, even if the service was ready to go by the intended date, it would only be at reduced capacity.
"The timelines are starting to look a little tight, but if all that happens by 1 July, the numbers will be populated into the system in or around 1 July," the spokesperson said. Once populated, the numbers would be cross-checked by Medicare Australia and subsequently be made for use by both the public and healthcare providers.
The HI service is eventually intended to serve unique identifiers for patients through three different portals; by telephone, through a web portal or through business-to-business connections via clinical software. The most basic method - by telephone - will likely be available once identifier numbers are assigned but, with no secure method for healthcare providers to store those numbers, this is designed a backup channel rather than an e-health solution.
Much more in the way of disclosure here:
It is quite clear we will are going to have a protracted, patchy and very fragmented.
The final paragraph of the article says it all!
“Implementation papers released by NeHTA concede that implementing a secure business-to-business connection through existing clinical software would only be possible when providers' "systems are able to support them and if they see value in making the change".
Without this done and working it just won’t be a goer in my view and that ignores all the user authentication issues.
With the following one really does wonder what is going on with NASH.
HealthSMART to roll out e-health smartcards
Part of $360 million Victorian e-health initiative
- Tim Lohman (Computerworld)
- 08 June, 2010 12:02
Victoria's Department of Health will shortly commence implementing an e-health smartcard to manage access to key Victorian public health sector (VPHS) applications via a new single sign-on portal, as part of its whole-of-health ICT strategy, HealthSMART.
The two-factor authentication system will consist of a smartcard management system card printers, contact smartcard readers, a hardware security module, middleware and mini-driver for network authentication, and an application for performing certificate and PIN management functions.
The smartcard management system will be hosted and supported by HealthSMART at its own data centres. The smartcards themselves will be rolled out in a phased process across the VPHS which will see 5000 cards issued in year one, 30,000 in year two and 50,000 in year three for a total of 85,000 cards.
The project will begin with an initial deployment of smartcards at 10 health agencies, followed by deployment at up to 25 metropolitan and five regional VPHS agencies.
The Victorian Department of Health (DH) will also deploy smartcards for two-factor authentication. Once authenticated, DH users will be given access to the HealthSMART network and Clinical System.
If NASH really was underway, and not just a twinkle in NEHTA’s eye, we can be sure the HealthSMART Project would know about it and would be waiting / contributing.
More messiness I reckon. Reminds one of the ‘arranging a booze up in a brewery’ type capability comments!