RHAPSODY WORKSHOP:BEST PRACTICES

JAMES HARDACRE & BRENDON MCALEVEY

Page 2 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices

▸ Naming conventions– Communication points & filters– Routes

▸ Use of no-ops▸ Route layout and uses▸ ‘Design’ links▸ Global properties – with migration and overrides▸ Multiple users▸ Housekeeping

Page 3 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - Naming conventions

▸ Communication points - filters▸ Routes

▸ No spaces - underscores▸ Prefix code▸ Suffix type

▸ Numbering▸ Folders & lockers

Page 4 • 2016 © Orion Health™ group of companies

Rhapsody | Best Practices - Use of no-ops

▸ Comments▸ Organise▸ ALL input links▸ ALL output links

Page 5 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - Route layout and uses

▸ Spiders web▸ One thing at a time

RHAPSODY

Page 7 • 2016 © Orion Health™ group of companies

Rhapsody | Best Practices -‘Design’ links

▸ DB/Dir store & polling▸ Where do they link?

Page 8 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - Global properties, with migration and overrides

▸ Using global variables▸ Using override

Page 9 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - Global properties, with migration and overrides

Page 10 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - Global properties, with migration and overrides

▸ Migration to other server▸ Overrides are NOT migrated

Page 11 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - Multiple users

▸ “administrator”▸ Lock down anything above TEST.

(maybe even above DEV)

Page 12 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - House keeping

▸ Space saving▸ Keep it clean

Page 13 • 2016 © Orion Health™ group of companies

Rhapsody | Best practices - AOB

▸ Examples in Rhapsody▸ Questions….?

Rhapsody™ Integration Engine is intended only for the electronic transfer, storage, or display of medical device data, or the electronic conversion of such data from one format to another in accordance with a preset specification as specified in the product manual and/or related documentation. Rhapsody Integration Engine is not intended to be used for active patient monitoring, controlling or altering the functions or

parameters of any medical device, or any other purpose relating to data obtained directly or indirectly from a medical device other than the transfer, storage, and conversion of such data from one format to another in accordance with preset specifications. Orion Health makes no warranties and the functionality described within may change without notice.

Rhapsody™ is a registered trademark of Orion Health™ Limited, manufactured in New Zealand, by Orion Health Limited. All other trademarks displayed in this document are the property of Orion Health or their respective owners, and may not be used without written permission of the owner. Rhapsody Integration Engine is not intended to be used for diagnostic purposes, or to replace clinical judgment or responsibilities.

All patient information shown in any imagery is for representation and demonstration purposes only and is not related to a real patient.

Copyright © 2016 Orion Health™ group of companies | All rights reserved | www.orionhealth.com