Getting Started with Vanya Client

01

Download and install the Vanya Client desktop app

Version 0.2.9 of Vanya Client was released on May 20th, 2022. This first version is a Windows build. Mac and Linux builds should be ready later in the month. Download here.

System requirements are few. We’ve tested the app on Windows 10 and Windows 8 PCs. It should also run without issue on older Windows 7 machines. The app is built using Electron and .Net 6. As Electron is resource heavy, you would benefit from a comfortably high spec machine.

After installing, Vanya Client should launch for the first time on its own.

02

Test the connection to one of the default test servers

The start page is simple, showing a drop down of available servers in the middle and a list of resources that can be accessed on the left.

Start Page

There are two test servers configured for use. The first is a server on Azure that we manage and have populated with Patient test data generated by Syntea and hosted by Mitre. It's incomplete but we’re growing it slowly.

The second is a Fhir.org test server that is used by devs all around the world to test their code. It contains millions of records entered by users as they built their own apps. Much of this data is 'junk data', so be wary when using it.

Both of these servers provide a good testing ground to get a feel for Vanya Client before trying it out on your own FHIR servers and your own data.

If you click the Connect button next to the drop down, the Capability Statement for the server will be loaded and some general info about the server displayed. This validates your connection, and you can now start clicking on some Resource links to see data.

Capability Statement
03

Click on a Resource and browse the results

As an example, click on the MedicationRequest link in the sidebar of Vanya Client. You should see data for the first 40 records, sorted by last updated date, as well as links at the top of the page to browse to the next 20 results.

The Previous Page button will always return you to the previously cached page of results, so you can jump around between Resources, drill down into the data and easily return to the initial results set you were looking at.

Medication Requests

Not all fields and data for each record appear in the results grid. We’re currently only showing some of the most common fields. The data displayed will be expanded on in future releases. For more information take a look at the Roadmap.

Click on the arrow icon to the left of any record to populate the full data display for that record. This contains every value for the record, inlcuding all extensions, identifiers and references.

A word of caution. The data in the FHIR.org test server is not good and often contains Resource links that do not have corresponding records. This means you will often see blank records for linked Resources. You may also encounter error messages when the format of the data is incorrect, leading to pages of results not loading. A common example is incorrectly formatted dates or invalid data in Enumerated value fields.

This is the nature of the beast when dealing with test data servers, and in theory should not happen with production data. We’ll be expanding on the error management and handling in future releases.

04

Click on some Resource links

Resource links are clickable if we’re handling that particular Resource. At the moment we’re only handling 21 FHIR Resources out of 140+. We’ll improve on this over the next couple of months.

Observation

In the above screenshot clicking on the highlighted Subject will open a new results page with data for that patient. Resource links may or may not show the name of the entity. If the user who created the data filled the Display value for the resource with a name, that value will be shown, otherwise we default to showing the Resource type, as shown in the above screenshot for some of the other patients.

05

Now try accessing your own test server

If you have a publicly accessible test server of your own, go back to the app’s home page and copy the URL into the Server drop down list. See if you can connect using the Connect button, and if you can, start looking at your own data using the links on the left.

If your test servers are only accessible using a bearer token or an api key, you’ll have to wait for a release later in the month to access them. Likewise if you’re using a Mac or Linux machine.

Feedback is welcome. Please let us know what you think of the app, what works for you and what doesn’t, and what you’d like to see it do. The Roadmap provides a list of the improvements we’ll be making over the next few months. Suggestions on this are also welcome.