Tips and Tricks for the ConMan Scenario Builder

In the previous page we described the basic use of the Scenario Builder in ConMan (which is part of clinFHIR). In this page we’ll describe a number of useability features – in no particular order.

Adjusting the table view

The table view has a number of ways that the displayed rows can be changed to make it easier when editing. These are accessed as links at the top of the table:

Screen Shot 2018-09-02 at 2.56.03 PM

The options are:

  • Show Notes. This will display another row to the right where notes about each element can be recorded. These are then visible in the other tabs: Summary of Scenarios and All scenario notes
  • References only / Show all. Hides all elements that are not reference types (or their parents)
  • Hide without data / Show all. Only displays the elements that have data entered against
  • Collapse. Hides all the elements that are not directly off the root. This is particularly handy when you have duplicated rows with children (like List.entry) to get back to a ‘clean’ display

Using the Tree view

The tree view is very similar to that in the original clinFHIR scenario builder.

Screen Shot 2018-09-02 at 3.03.11 PM

Elements that have data recorded against it (whether through the table or the tree) is bolded, and is displayed when that element is selected. Selecting an element also shows the permitted datatypes, and will display the data entry dialog when selected.

Elements that are multiple can also be duplicated from here.

Looking and validating the Resource instances

Given that the purpose of the Scenario Builder is to make resource instances, it is logical that they can be easily viewed (they are automatically constructed as the resources are updated either via the table or the tree).

There are 2 views available – the actual JSON (which is the format that it is exchanged in) and a tree view (but the tree will only show elements that have data.

As shown in the screenshot below, it is possible to have the server validate the resource instance. This will tell if there is missing data for example. For the technically inclined – this uses the conformance server (defined in the track definition). And – currently there is an issue with the HAPI validator – second error is not correct.

Screen Shot 2018-09-02 at 3.26.41 PM

 

Importing an existing graph

It’s also possible to copy someone else’s graph into your own workspace, and then modify that. To do this, click the import button that is just below the dropdown list of scenarios to the upper left. This will display a dialog containing all the graphs that other users have made for any track in this scenario.

Select the one you want, and a copy will be imported into your workspace. After that, you can modify it at will (it won’t effect the original). You could also use this to create a graphs in one scenario, them import and modify it in another.

Screen Shot 2018-09-02 at 3.33.20 PM

%d bloggers like this: