In the Definition section it states "The display name is intended to enable physicians, clinicians, and patients to quickly find the information they are looking for by browsing a list of documents." One issue is to be able to quickly zero in on a desired document from a long list. When you have someone who has been a patient for many years who has multiple conditions there could be a 100 documents. Besides having consistent names there is a need to quickly and easily filter for a specific type of document. Limiting the search to the name of the document will not be that helpful if there are multiple documents in the same domain which will be a typical situation. There is a need to be able to filter or sort on a variety of metadata in addition to the name of the document. There can be the official long name, the official short name, the display name and there should be a local name. Having a search that includes metadata can be extremely useful for users.
There could be a predefined local name but the actual end user should be able to define their own name. The enduser application could make this local name the display name. When a document type arrives that does not have a local name the user could be prompted to enter a name. The next time that document type arrives the previously defined local name could be automaticall attached to that document. This would solve the problem of the official name being too long to fit the user's name field. Some health authoraties have had to be very creative with naming documents because of a very small name field with different departments using different names for the same forms.
At one point Kaiser Permanente had up to 4 local names for an official SNOMED perferred name. These local names would be used internally but the SNOMED preferred name would be used when documents were sent outside of Kaiser.