I recently did a presentation on electronic medical record content design for a customer group. As part of the presentation I gave some tips on dictionary design. The participants found these useful, so I decided to share them in a blog.
#1 Don’t go beyond your degree of certainty.
When you are capturing data based on direct observation, “Yes/No” formats are appropriate.
![]()
But when you are capturing information based on what the client reports, then you cannot use a” Yes/No” format since “No” is unconfirmed. Use “Denied” instead.
#2 Provide for clinical judgment.
When the client denies something crucial, include a choice that supports a different clinical impression. Use “Suspected.”
![]()
When the client says “Yes” to something, provide for clinician doubts.

#3 Think twice before giving an opt-out on required items.
Our clinical design team members felt strongly that access to firearms was essential information for the assessment of intentional and accidental risk. We all felt that to include a “N/A” choice would invite clinicians to dodge the question. So despite protests from the geriatric representatives, we made it required without an opt-out choice.
![]()
In other situations, however, the balance between importance and exceptions tips towards the latter and opt-outs simply make sense.
For example, a history of abuse is crucial to treatment, but such information may not be acknowledged or even be appropriate for initial inquiry, so an “Unknown” choice makes sense.
![]()
In an earlier blog I described our design of an integrated assessment. As part of the design, this Functional Assessment was to be used by the child clinicians. In order for the integrated approach to work, we had to adjust the responses to be appropriate for younger children. Hence the “N/A” choice.

#4 Be sure to include a way-out on required pick lists when none of the selections may apply.
Dictionaries are one of the most useful tools in your design kit. They are vital to capturing structured data in your EMR. They contribute to efficiency and consistency and facilitate robust, aggregated reporting. But use them thoughtfully.
Now it's your turn. Have you got any tips to share with us?




