When reviewing and reporting on data for projects that serve more than one CoC, currently primary site needs to be inferred when the CoC != the Selected CoC as there can only be one primary site in the Clarity UI. This impacts the LSA, HIC, and CSV Export.
The Data Dictionary states that "There must be a one-to-one relationship to 2.02 Project Information if the project only serves one CoC (most common). … It must be possible to associate a project with the CoC code for every geographic area in which the project operates and for which it will be entering data into an HMIS.”
Although it is not the most common situation, there are many projects that serve multiple CoCs especially when reviewing Balance of State workflows and it is listed as a requirement in the System Logic and Other System Issues section of the Data Dictionary.
System Administrators should be able to identify 1 Primary Site per CoC a project serves, so that the data can be pulled from the database as opposed to creating logic inferring the relevant admin site information for Data Element 2.03 Continuum of Care Information