UI that ensures users have performed a relevant code search

Example of how a UI can be designed to encourage capture of coded clinical data rather than free text.

In this example the user is required to perform a relevant search before being able to enter and record a free-text alternative.

To do this, the "coded diagnosis" field is the only field that is enabled, and the user can search for a code. If they find a match, then the Done button is enabled. If not, then the free-text field is enabled and the user can enter an uncoded diagnosis. If the free-text version is sufficiently similar to the text that was searched for as a coded diagnosis, then the Done button is enabled.

To illustrate what is happening "behind the scenes", a FHRI CodeableConcept, the basis of the similarity metric, is displayed to show what would be recorded when the Done button is clicked. Additionally, the Levenshtein distance, the basis of the similarity metric, is displayed.

{{'Coding:'}} {{result | json}}
Levenshtein Distance: {{ distance }}