Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Your time is valuable and so we’ve prepared this guide to help you get organized well in working with us.

This guide is intended to help customers to prepare the way for the smoothest transition to Iguana X that we can. To do this will mean sharing some of your channels with us. Of course be very careful not to send us any real Patient Health Information (PHI). If you have time to do these steps before we meet it will really help.

 Install Iguana X

You can go here:

https://downloads.interfaceware.com/iguanax/

And follow the instructions to install IguanaX.

 Make sure you have access to a cloud accessible GIT repo account provider like bitbucket or github.

If you do not have one then you can set up a free account on either platform. If you have a choice bitbitbucket is not a bad choice since we know it and can help you. Github also works well.

Some customers have tried to share git repos with gitlabs - but unfortunately it has not worked so far although you can import IguanaX components from any git repository - it just has not be the smoothest platform to work with in our experience.

 Export your channels to a Git repo in your cloud repo provider.

If you have not done this before, then we prepared this guide for how to do it. Let us know if you need additional help!

 Give us access to this git repository in the cloud with your channels

This step entails copying the SSH link (ex. git@bitbucket.org:johndoe/iguanaxrepo.git) and sending it to us. Please ensure that your repository is public so that we may pull the channels into IguanaX for testing (this change is made on Bitbucket or Github).

Of course be super careful not to put any PHI in this repo. But making your channels available means we can move a lot faster to help make sure your interfaces will port over to IguanaX easily.

We’re happy to use github or Bitbucket or any other git cloud provider that we can access.

If you need some help getting this configured let us know.

 Make sure every translator that needs sample data has at least one good sample message

It is important in order to be able to run channels that we have a least one good sample data message with each translator. Without it we cannot run your code in Iguana 6 to see how it is meant to run.

We’re happy to brainstorm with you on how to achieve this if you need advice on it - really we are happy with just one message - that is plenty.

Just remember no real PHI please!

 Document the list of environmental variables your channels require so we can set them up in our environment

One of the best practices is document these variables in your translator components. It’s really helpful.

 Try running the channel converter in IguanaX to convert your channels.

Here’s the page explaining how to go about trying to do this, do your best to give it a try.

Iguana 6 Channel Importer

It’s guaranteed to be not 100% successfully convert your channels the first time you run it but this is an important step for us to identify what the problems are and get moving on addressing them. Every time we go through this process with a customer we found we have been able to improve our process. We are trying to move quickly to identify and solve problems.

 Overwhelmed? Could not make one of the steps work? We can help.

Breathe deeply.

It’s okay.

We are here to help. When we go through the first zoom call with you, we’ll help you with all the above steps if you haven’t managed to find the time or stumbled on any of the steps.

Looking forward to working with you! Together we make our lives better by making to possible to transition to a cleaner simpler and more reliable way of building and maintaining interfaces.

  • No labels