Orion Health adds FHIR to Rhapsody 6.1

Orion Health has launched version 6.1 of its Rhapsody integration engine, becoming what it says is the first to implement the new Fast Healthcare Interoperability Resources (FHIR) standard.

V 6.1 also includes new JavaScript capabilities and application programming interface (API) enhancements that Orion Health says provides a comprehensive set of tools to simplify complex healthcare interoperability.

Rhapsody 6.1 now includes support for the JSON data interchange format and the REST architecture approach, meaning organisations will be able to start implementing FHIR-based interfaces.

Orion Health announced it was planning to support FHIR back in February, and its product specialist, David Hay, has written a white paper on why he believes FHIR will become the lingua franca of healthcare data exchange.

Dr Hay believes FHIR is set to become the common language used globally to exchange healthcare data between disparate systems. “It is likely that FHIR will become like the internet: ubiquitous and largely invisible – it’s just there,” he said.

In addition to FHIR capability, Orion Health has introduced a new concept called Lockers, which contain parts of Rhapsody’s configuration that can only be accessed by nominated users or groups.

The idea is to allow organisations to have a greater level of control over users’ access to configuration, messages and personal health information.

There are also new shared JavaScript functions, providing the ability to create, edit, import and export custom shared JavaScript functions that can be invoked by any JavaScript filter.

Newly appointed vice president for Orion Health's Australian operations, Darren Jones, said FHIR was one of the most promising advances in healthcare data integration this decade.

“[We] are proud to be helping to lead the industry with the first-ever integration engine support for this groundbreaking new standard,” Mr Jones said.

“In addition to FHIR support, our work on this latest version of Rhapsody has focused on delivering tools to support the power-users and developers in healthcare organisations who are constantly challenged to bring together data from more systems, devices, facilities and organisations every day.”

Posted in Australian eHealth

Comments   

# Richard Medlicott 2015-04-28 13:05
So when we get a discharge summary with metadata to populate our GP systems?
We have the GP2GP cda sent as an HL7. Do we need to rewrite the NZ standards?

You need to log in to post comments. If you don't have a Pulse+IT website account, click here to subscribe.

Sign up for Pulse+IT eNewsletters

Sign up for Pulse+IT website access

For more information, click here.

Copyright © 2017 Pulse+IT Magazine
No content published on this website can be reproduced by any person for any reason without the prior written permission of the publisher.