Right now the valueset change isn't working correctly. Will fix soon.
As described elsewhere, coded elements generally have a ValueSet associated with them which defines the supported values for that element. The association of a ValueSet to a resource property is termed 'Binding'.
To change a binding, first select the element in the navigator by clicking on it's path. On the right pane appears both a summary of that element, and the formal definition. The summary lists the current valueset, and also displays a link 'Examine/Change valueSet'.
Clicking the link will display the ValueSet browser.
The ValueSet browser (which is also available from the Resource Builder) allows you to examine a ValueSet, and in the Profile Builder to change it.
It has the following tabs.
- Search. This displays a serch form to find and select a new ValueSet (we'll look at the shortly).
- Description. A summary of the ValueSet currently selected
- Define. When the ValueSet is one that defines it's own opions, then this tab will list those options. This is most commonly used when there is a small set of options that are specific to this eement, rather then being derived from some external terminology.
- Compose. This is when the ValueSet is composed of options from an external terminology - eg a subset of SNOMED codes. The compose can be quite complex!
- JSON. shows the actual ValueSet resource in JSON format
- Expand. Allows you to perform searches on the ValueSet. Useful for some the larger ValueSets - like Condition.code. This is the same filtering used by the Resource Builder.
The search tab is where you can select a new ValueSet to bind to the selected element.
It displays a simple form containing search boxes for name and description, and then performs a search against the registry for matching ValueSets, which are displayed in a list.
The image opposite shows a search for ValueSet's with the word 'LOINC' in the description.
Selecting any of the ValueSet's will place it 'into context', meaning that you can view the description, expand it and so forth.
Once you have found the ValueSet you want, clicking the Select button will close the dialog and associate the new ValueSet with the selected element.
At the moment, the search facility can only work against a single server - currently Health Intersections (Grahames) server. Once the HL7 registry is established, then that will become a more obvious choice. The FHIR specification supports the notion of distributed registries - so it's likely that this search functionality will become more comprehensive in the future.
Add Comment