Makes sense. In that case, we will prob need 1 additional attribute “locationCode” which can have codes from the FHIR valueset, although I do not assume such details are needed. Another option is to use the “location tags” - and once you select. that, only the locations tagged with a specific tag can be shown.
this imo, will be closer to OMRS ref model.
If you would use concepts to indicate the locationCode, then we will have to have some other mapping or convention to show the list of locations that can entered in “servicerequest.locationreference”